Repository navigation
docs/plans: ci-merge-freshness decision record (stale-green root of the 3× fleet-red) - #5474
Merged
Merged
Conversation
…he 3× fleet-red) Pins the 3× fleet-red to stale-green (PR validated against a pre-gate base, merged without re-validating current main) via the #5429 timeline receipts; ranks the merge-policy fixes (merge-queue >> require-up-to-date under the approval outage); scopes neat-ibex's reverse-staleness lens as complementary, not the 3×-red killer. Decision record for the operator's merge-policy call. Co-Authored-By: Claude Opus 4.8 <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.
Decision record for the merge-policy call surfaced by the 3× fleet-red root-cause. Docs-only.
The fleet-red that hit
mainthree times (#5445/#5453, #5429/#5465) is stale-green — a PR validated against a base that pre-dates a newly-landed gate, merged without re-validating against currentmain. Pinned with receipts (the #5429 timeline: CI green @06:11 → gate #5418 landed @06:33 → merged @15:04 on the same head, never re-run). The forward completeness gates already exist and work; the hole is freshness, which is a merge-policy fix, not a lens.The doc ranks the two by-construction options (merge-queue ≫ require-up-to-date under the current approval outage), flags the interaction with the
[TEMPORARY POLICY]manual-merge workflow, and scopes neat-ibex's reverse-staleness lens as complementary (it fixes #5466-mode stale entries, not the freshness gap).This is the artifact for the operator's merge-policy decision (merge-queue vs required-check). bright-stag is surfacing the same call in parallel.
🤖 Generated with Claude Code