ci: rosetta-audit -- pinned cross-language consistency gate on engine PRs (#2557) - #2617
Merged
Merged
Conversation
…engine PRs (#2557) The engine had no rosetta gate: a PR shifting corpus-observed counts merged green here and detonated keyword-rosetta later on an unrelated PR (the #2552 cobol drift surfaced days late that way). rosetta-audit.yml now checks out keyword-rosetta at the pinned KEYWORD_ROSETTA_REF Actions variable (set: 7686b0a) and runs all 46 verify gates + the corpus's baseline-gated n/a review audit against the PR's engine build -- path-filtered to engine code, ~6 min, workflow_dispatch for manual runs. BUMPING_THE_ROSETTA_PIN.md documents the re-baseline protocol (the crucible-pin twin): corpus re-baseline PR with ENGINE_REF=pull/<N>/head -> merge -> engine PR bumps the var. ecosystem.md's rosetta-sweep row updated to the new choreography (no more draft-PR limbo / rerun dance). Cross-repo: companion keyword-rosetta PRs #6 (n/a semantics) + #7 (ENGINE_REF + na_check); the n/a audit step self-activates when the pin advances past #7. Closes #2557 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PUfXMUECX4Vq1vqh9mMQqt
Contributor
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Engine half of #2557's Phase-5 integration; redesigns the clunky two-repo choreography surfaced by the jcl sweep (#2581).
The two defects this fixes
main, so corpus PRs needing unmerged engine rules sat draft+red, then needed manual reruns.What this adds
rosetta-audit.yml: checkout keyword-rosetta @vars.KEYWORD_ROSETTA_REF(set to7686b0a, current corpus main), run all 46 gates +na_check --ciagainst the PR's engine. Path-filtered togitgalaxy/**/pyproject.toml(~6 min),workflow_dispatchfor manual proving runs.docs/self_scan/BUMPING_THE_ROSETTA_PIN.md: the crucible-pin-twin protocol — intentional drift re-baselines in the corpus repo (its newENGINE_REF=pull/<N>/headescape hatch, from keyword-rosetta#7), then the engine PR bumps the var. Never a way to silence a red.Verification
Proving run via workflow_dispatch on this branch (link in comments once green): all 46 gates against the pinned corpus + this branch's engine. The n/a audit step self-activates once the pin advances past keyword-rosetta#7 (it prints an explicit notice until then).
Cross-repo: companions keyword-rosetta#6 (n/a semantics, approved+green) and #7 (ENGINE_REF + na_check, stacked on #6). Merge order: rosetta #6 → #7 → this PR → bump
KEYWORD_ROSETTA_REFto the new corpus SHA.Closes #2557
🤖 Generated with Claude Code
https://claude.ai/code/session_01PUfXMUECX4Vq1vqh9mMQqt