feat(plugin): campaign invariants — verify the machinery, not only artifacts#83
Merged
Merged
Conversation
…tifacts
Closes the gap a real v1.35->v1.55 relay field report identified in 0.6.0: the
self-verify interval was the right shape but artifact-scoped — it re-checked the
work, never the release machinery. All three machinery failures shipped a whole
bad round and none was named:
1. required_status_checks.contexts was [] — every --auto merge landed without
CI ("PRs merge in seconds").
2. merged != released — ten "LANDED" reports with no tag pushed.
3. cancel-in-progress merge trains left the tagged commit's CI cancelled, so a
"verified" release sat on an unverified commit.
Adds a "Verify the machinery, not only the artifacts (campaign invariants)" block
to the operating contract (single source): assert the gate is non-empty before a
round; merged != released (tag + success run, not cancelled/queued); only a green
HEAD before the tag makes the round's evidence whole. Broadens the self-verify
clauses (operating contract + feature-loop) to check machinery AND artifacts with
fresh-context subagents. release-execution step 5 now asserts these before tagging
(reference, not restatement). Bump to 0.8.0.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Closes the gap a real v1.35→v1.55 relay field report found in 0.6.0: the self-verify interval was the right shape but artifact-scoped — it re-checked the work, never the release machinery. Three machinery failures shipped a whole bad round and none was named:
required_status_checks.contexts: []→ every--automerge landed without CI.cancel-in-progressmerge trains left the tagged commit's CIcancelled.Adds a "Verify the machinery (campaign invariants)" block to the operating contract (single source): assert the required-checks gate is non-empty before a round; merged ≠ released (tag +
successrun); only a green HEAD before the tag makes the round whole. Broadens the self-verify clauses (contract + feature-loop) to check machinery and artifacts with fresh-context subagents, andrelease-executionstep 5 asserts these before tagging (a reference, not a restatement). → 0.8.0.🤖 Generated with Claude Code