chore: remove phase proofs and workflow policy checker#14
Merged
Conversation
The phase 1/2/4 fixture proofs, the rebuild validation workflow, and the string-matching workflow policy checker were delivery-phase scaffolding. The real publish path (validate -> staging -> production) supersedes them, and the policy checker's exact-fragment assertions broke on every legitimate workflow edit. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Jul 23, 2026
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.
Summary
First of two cleanup PRs stripping delivery-phase scaffolding so the repo does one thing: publish deb/rpm packages to R2.
check_workflow_policy.py+ test: it asserted exact string fragments (with exact occurrence counts) ofpublish.ymlandphase5-publish.sh, so every legitimate workflow edit broke it. It cannot protect anything a reviewer doesn't — anyone able to edit the workflow can edit the checker in the same PR.phase1-local.sh,phase2-local.sh,testdata/, moon tasks): these ran docker fixture builds, throwaway GPG keygen, and container installs of a fake package on every CI run (~30s+ each, confirmed in run 29972545107) while proving nothing the Go unit tests and the real publish flow don't.phase4-staging.sh+ moon task: staging rehearsal pinned to a fixture project, superseded by the staging job inpublish.yml.rebuild.yml: manual workflow whose only job was re-running the phase 2 fixture proof.spikes/phase0artifacts (run.sh,fault-injection.sh,EVIDENCE.md,README.md).Dockerfile.toolsandbuild-repository.shstay for now because the live publish scripts reference them; they move/shrink in the follow-up PR.phase3-ci.sh→lint-workflows.sh: keeps pinned actionlint + ShellCheck (cheap, real), drops the policy checker.No behavior change to the publish path —
publish.ymland the phase 5 scripts are untouched here. A follow-up PR simplifies those.Testing
scripts/lint-workflows.sh(actionlint + shellcheck + dispatch-payload test) passes locally.go build ./...andgo test ./...pass locally.🤖 Generated with Claude Code