Skip to content

ci(ci-gate): re-pin the cicd-suite gate to 09878f2 (emoji-safe status descriptions) - #116

Open
hyperpolymath wants to merge 1 commit into
claude/ci-gate-pr-startfrom
claude/intelligent-johnson-i64bfk
Open

hyperpolymath wants to merge 1 commit into
claude/ci-gate-pr-startfrom
claude/intelligent-johnson-i64bfk

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Summary

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.
  • tests/workflows/squabble_gate_test.sh: SUITE_PIN fixture value.
  • CHANGELOG.adoc: new entry.

RSR Quality Checklist

Required

  • Tests pass (the workflow tests listed below)
  • Code is formatted / linter: not run, no source changed
  • No banned language patterns, no unsafe, no banned functions
  • SPDX license headers untouched
  • No secrets, credentials, or .env files included

As Applicable

  • CHANGELOG or release notes updated

Testing

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 (no archetypes/ in a minted repo).

What is NOT proven

  • The emoji fix in a live run.
  • That 09878f2 survives the squash merge of #139.
  • That the hand-added lock key for the tamper guard matches what GitHub resolves at startup; only the local sync checker was run.
  • actionlint was not run.

Screenshots

N/A


Generated by Claude Code

… descriptions)

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J4QvDiRggj6apeRQKPpAVR
@sonarqubecloud

Copy link
Copy Markdown

@hyperpolymath
hyperpolymath marked this pull request as ready for review November 18, 2026 01:43

Copy link
Copy Markdown
Owner Author

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.


Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants