docs(repo): 2.4 launches with the wave, only its wiring waits - #8
Merged
jundymek merged 1 commit intoAug 11, 2026
Merged
Conversation
Fourth codex finding on the closure commits, and the previous fix overshot: 2.4 does not have to wait for the scanner merge to start. Its spec directs the agent to build the config resolver and progress plumbing while waiting, and to integrate against contract types with inert stubs until each analyzer lands. Readiness now separates launching the story from wiring the scanner-dependent pipeline, and says why Epic 2's chain is not serial the way Epic 1's was. Refs: epic-1-contract-foundations Agent: superman (terminal-agents, claude-opus-5)
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.
My previous fix overshot, and the review caught that too
#7 corrected "2.4 can launch immediately" to "2.4 waits for 2.1". That was too strong. The 2.4 spec says the agent should start with the wave and only defer the parts that need a merged analyzer:
So launching the story and wiring the scanner-dependent pipeline are two different moments, and only the second waits. Describing 2.4 as blocked would idle an agent for the length of story 2.1 for no reason — the opposite failure to the one #7 fixed, and the more expensive one in a parallel harness.
What it changes
One paragraph in the retrospective's Next-epic readiness. It now separates launching from wiring, and says why Epic 2's chain is not serial the way Epic 1's was: here each story needed the previous one's code to exist at all, which is not true of 2.4 against 2.1.
The full codex record on the supervisor's own commits
Four findings, all real, all fixed, none dismissed:
1.4-perf-spikeflipped todonewhile its owner gate was openreview, on your call (#5)Worth stating plainly rather than burying: four rounds on a document that is one page of prose, all in the same corner of it — the sentence that tells the next launcher what to start. That sentence is the retrospective's only operational output, and a supervisor's own bookkeeping is the one artefact nobody else reviews.
The review pass on this head closes clean: "accurately reflects the declared Epic 2 dependencies and the explicit instructions allowing story 2.4 preparatory work while waiting for scanner integration".
Verification
docs/only. The epic head verified at closure (41fb746):pnpm lintclean,pnpm typecheckclean across six packages,pnpm test— 161 tests, 0 failures —pnpm buildclean. Nothing here touches it.Next
Once this merges I open the epic → master integration PR, carrying the closure review's pending-owner list: your merge click, acceptance of the 1.4 verdict, the six unticked steps in
1.4-perf-spike/MANUAL_TESTING.md, and the M1 milestone wording that still says "CI green".Refs: epic-1-contract-foundations
Agent: superman (terminal-agents, claude-opus-5)