Repository navigation
Conversation
…pture Two turns racing turn completion could both compute max(count)+1 and share a checkpointTurnCount, colliding on the deterministic git ref. The decider now rejects thread.turn.diff.complete when another turn already owns the submitted count, and the reactor re-reads checkpoint context after the slow git capture, re-capturing at a fresh count when a concurrent turn claimed it first. Tests: decider.turnDiffComplete 5/5 green (red-on-base: 1 failed, 4 passed); CheckpointReactor 46/46 green including a new race test that fails on base (turn-1 lands at count 1, colliding). Authored with AI assistance (Muse, Meta's Muse Spark) under the contributor's direction.
github-actions
Bot
added
vouch:trusted
This was referenced Oct 16, 2026
This branch has not been deployed
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
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.
What Changed
The decider now rejects
thread.turn.diff.completewhen another turn already owns the submitted checkpoint turn count, and the CheckpointReactor re-reads checkpoint context after the slow git capture, re-capturing at a fresh count when a concurrent turn claimed it first.Why
Two turns racing turn completion could both compute max(count)+1 and share a checkpointTurnCount, colliding on the deterministic git ref.
Validation
decider.turnDiffComplete5/5 green (red-on-base: 1 failed, 4 passed).CheckpointReactor46/46 green including a new race test that fails on base (turn-1 lands at count 1, colliding with turn-2's placeholder).Checklist
Authored with AI assistance (Muse, Meta's Muse Spark) under the contributor's direction.