decisions: record the retried date's promotion chain, window retry, reference exception and checks - #82
Merged
Conversation
…eference exception and checks Four lines under "Carried from the build, pending team review", from the live proof of 2026-09-28: a --retry-failed run promotes only after its reference and seed runs; the scheduled window cannot retry a failed date; an imported reference needs --allow-unreleased; neither the loop nor the retry path records check results. Co-Authored-By: Claude Fable 5.1 <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.
Four dated lines under "Carried from the build, pending team review" (Claude for Ben, 2026-09-28), from the live proof of processing date 2027-12-03 on rapid_rebuild:
--retry-failedrun cannot be promoted alone; a person promotes the reference run, the seed run and the retry run in that order. Team question: shouldrun promote-planof a seeded run include its seed chain's candidates.--allow-unreleased. Team question: import through a released image?check runfirst. Team question: should the loop and the retry path run the policy's checks?op-processing-date-loop.shpasses no--retry-failed.Proof: three promotions (reference with
--allow-unreleased, seed, retry) succeeded and were rolled back in reverse; the selection after rollback equals the before probe.Local build as CI: check-public-safety OK,
sphinx-build -Wrc=0, acceptance.sh all PASS.🤖 Generated with Claude Code