Repository navigation
Record #10933 x #10934 as the next stale-green instance in gunbc.plans.ci_merge_freshness - #10984
Merged
Merged
Conversation
…s.ci_merge_freshness A deletion (#10934) crossed a new consumer (#10933) in never-jointly-validated PRs: #10934's green run started before #10933 merged and #10934 merged on that head without re-running. main went red with 2 IMPORT-MEMBER-ABSENT findings from this pair until #10977. Records the timeline, the independently established ReadbackConfirmed construction the run never reached, and the contributing factor (one manager held both lanes and never compiled the merged pair). No new mechanism: the instance sits under the record's existing retirement condition. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01S44GATAuUiFerAsjYZFmaa
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01S44GATAuUiFerAsjYZFmaa
…d what landed inside it Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01S44GATAuUiFerAsjYZFmaa
added 2 commits
September 11, 2026 02:10
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.
This PR records the #10933 × #10934 incident as the next instance in the existing stale-green authority,
gunbc.plans.ci_merge_freshness, as §7. It adds no new failure-mode row and no mechanism, and it is separate from #10978.Same class as §1 (#5429). #10934's green witnesses run 34520652774 started at 19:28:58Z against a base without #10933. #10933 merged at 20:07:51Z while that run was in flight. #10934 then merged at 21:23:51Z on the same head, never re-run. The one difference from §1 is what crossed: there a gate crossed a module, here a new consumer crossed a deletion. §2's "overlapping, never-jointly-validated PRs" covers both.
Facts are kept at their grain:
mainata4b21cb8e47(run 34531957010, declarations phase): exactly 2 IMPORT-MEMBER-ABSENT findings from this pair. The same run carries a third, from an unrelated crossing (grain_admits_single_cabinet, repaired by Follow the rename #10865 made: grain_admits_single_cabinet is now grain_offers_single_cabinet #10968). §7 names it and excludes it from the count.ReadbackConfirmedwithobserved_digest, so restoring the imports alone would not have repaired the tree.The instance sits under the record's existing retirement condition, the §3 merge-time freshness requirement.
Verification: this is a prose-only edit to an existing
PlanIsAuthorityOnlycarrier, with no committed projection. I did not compile it locally, so CI is the compile check. I checked every timestamp, SHA and finding againstghand the run log.🤖 Generated with Claude Code
https://claude.ai/code/session_01S44GATAuUiFerAsjYZFmaa