You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ci(ci-gate): re-pin the cicd-suite gate to 09878f2 (emoji-safe status descriptions) - #116
Stacked on #112 (claude/ci-gate-pr-start). Re-pins the CI gate reusable workflow to 09878f2a2c0a8907cc69fe48973ea604753ecab1 (hyperpolymath/proven-cicd-and-workflows#144), which stops a false CI/gate = failure when a workflow name contains an emoji (GitHub rejects 4-byte UTF-8 in a status description; seen on hyperpolymath/resource-algebra#48).
Unlike the other consumers, this branch did not pin d2140a5. The two callers pinned d49708186e72... (an ancestor of 09878f2), while actions.lock and the test fixture still held 0862fe8b4001..., so scripts/check-lock-sync.sh already failed on the base (exit 1: tamper guard unlocked, ci-gate.yml ref missing, stale entry). Both callers use the same suite reusables, so all of it moves to 09878f2.
09878f2 is a commit on an UNMERGED suite branch, so a second re-pin follows #139's squash merge.
This PR touches gate files, so the tamper guard may fail guard / check until an admin applies the gate-change-approved label. Agents do not apply it.
Changes
ci-gate.yml (2 lines) and ci-gate-tamper-guard.yml (1 line): new SHA, # cicd-suite ... comments kept.
actions.lock: ci-gate.yml entry and dependency record moved to the new SHA (stale 0862fe8 dropped); new key for ci-gate-tamper-guard.yml, which was missing.
Proven 3-outcome test & bench suite, Proven suite verdict, Agda, Rocq and Lean in the pinned Guix, and therefore CI/gate, all fail at one step: registry-check (bun scripts/registry/claims-registry.mjs check) stops with "The ledger lost entries: main has 4, this tree has 3".
That compares this tree's proof ledger with main. This PR changes no ledger file; it touches only the gate callers, actions.lock, a test fixture and the CHANGELOG. The missing entry is one that landed on main after the base branch claude/ci-gate-pr-start (#112) was cut, so the base is behind main. Every stacked PR on #112 will fail this check until that branch catches up with main.
CI/gate is reporting those real failures correctly. It did produce a verdict, which is what this re-pin needs.
I'm not merging main into #112's branch from here, because it isn't this PR's branch. Once #112 is updated, merging its base into this PR will bring the ledger in.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Stacked on #112 (
claude/ci-gate-pr-start). Re-pins the CI gate reusable workflow to09878f2a2c0a8907cc69fe48973ea604753ecab1(hyperpolymath/proven-cicd-and-workflows#144), which stops a falseCI/gate = failurewhen a workflow name contains an emoji (GitHub rejects 4-byte UTF-8 in a status description; seen on hyperpolymath/resource-algebra#48).Unlike the other consumers, this branch did not pin
d2140a5. The two callers pinnedd49708186e72...(an ancestor of09878f2), whileactions.lockand the test fixture still held0862fe8b4001..., soscripts/check-lock-sync.shalready failed on the base (exit 1: tamper guard unlocked,ci-gate.ymlref missing, stale entry). Both callers use the same suite reusables, so all of it moves to09878f2.09878f2is a commit on an UNMERGED suite branch, so a second re-pin follows #139's squash merge.This PR touches gate files, so the tamper guard may fail
guard / checkuntil an admin applies thegate-change-approvedlabel. Agents do not apply it.Changes
ci-gate.yml(2 lines) andci-gate-tamper-guard.yml(1 line): new SHA,# cicd-suite ...comments kept.actions.lock:ci-gate.ymlentry and dependency record moved to the new SHA (stale0862fe8dropped); new key forci-gate-tamper-guard.yml, which was missing.tests/workflows/squabble_gate_test.sh:SUITE_PINfixture value.CHANGELOG.adoc: new entry.RSR Quality Checklist
Required
unsafe, no banned functions.envfiles includedAs Applicable
CHANGELOGor release notes updatedTesting
Run locally:
scripts/check-lock-sync.sh: exit 0 (exit 1 on the base branch).tests/workflows/squabble_gate_test.sh: 102 passed, 0 failed.tests/workflows/check_lock_sync_test.sh: 26 PASS lines, exit 0.tests/workflows/validate_workflows_test.sh: 83 PASS lines, exit 0.tests/workflows/archetype_lock_merge_test.sh: SKIPPED by the script itself (noarchetypes/in a minted repo).What is NOT proven
09878f2survives the squash merge of #139.actionlintwas not run.Screenshots
N/A
Generated by Claude Code