fix(rendering): collapsed-running tail gate — first live soak catch#465
Merged
Juliusolsson05 merged 1 commit intoJul 7, 2026
Merged
Conversation
…bundle 5b19529f) "awaiting reads but not rendering read... they get sent but then they just go away": the v1 collapsed-running rule treated "no block result + no committed trace" as death, but during normal streaming the committed tail lags BEHIND recent history turns (19s in the soak bundle) - the exact "not caught up" state this pipeline's own law says must NEVER mean suppress. In-flight Read/Bash fan-outs vanished mid-run. The rule now requires POSITIVE death evidence: committed truth moved PAST the turn (tail > turn end) with no trace of the tool - same pure trick as ghost rule 4, no wall clock, identity cache stays sound. The true dangling case (1b2b5e96, tail 47s past the dead turn) still hides; verified against its fixture. Adapter also stamps lookups.toolCallsById status onto tool candidates - 'completed' is resolution evidence even when the result never paired into the block. Corpus accountability: the suite HAD caught this when the v1 rule shipped (3 fixtures flipped) and the bless argued 'modern legacy hides these too' from git history without executing it. Re-blessed with the corrected verdict and the lesson recorded in the whys: renderer- equivalence claims must be executed, not argued. 142 pipeline tests; both tsc gates clean in-worktree. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Juliusolsson05
added a commit
that referenced
this pull request
Jul 7, 2026
…type fix(rendering): add missing RuntimeSemanticTurn.lookups type field (unbreaks #465)
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.
First live-soak bug (bundle 5b19529f, 'reads get sent then just go away'): the v1 collapsed-running rule suppressed in-flight churn tools while the committed tail lagged — violating the pipeline's own 'not caught up ⇒ never suppress' law. Now requires committed truth to have moved past the turn (pure tail gate, ghost-rule-4 style); lookups
completedstatus counts as resolution evidence. True dangling case still hides (fixture-verified). Includes the corpus-accountability re-bless: the original 'modern legacy also hides these' verdict was argued, not executed — corrected, lesson recorded. 142 tests, gates clean.🤖 Generated with Claude Code