fix(sim): implementation arcs take the prose's call order — task init creates#547
Open
leeovery wants to merge 1 commit into
Open
fix(sim): implementation arcs take the prose's call order — task init creates#547leeovery wants to merge 1 commit into
leeovery wants to merge 1 commit into
Conversation
… creates Found while authoring prose-test cases: no prose site ever issues `topic start` for implementation — task init owns creation (implementation-process Step 0). The sim's four implementation arcs ran topic start first, so the created arm (the real fresh path) was never exercised and the audited item shape was missing the four fields only that arm writes (analysis_cycle_total, current_phase, linters, project_skills). The arcs now call task init directly, pinned with mode=created; the implementation-loop scenario's second init is pinned mode=resumed. Co-Authored-By: Claude Fable 5 <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.
Summary
topic startbeforetask init, a call order no prose ever issues — implementation is the one phase wheretask initowns creation (implementation-process Step 0's created arm).analysis_cycle_total,current_phase,linters, andproject_skillsunwritten.task initdirectly, withmode=createdpinned at each fresh init andmode=resumedpinned on the implementation-loop scenario's genuine resume.Sibling change already in the prose-tests stack (#546): the
feature-implementedfixture had copied the sim's order and is fixed the same way — its snapshot diff shows the four recovered fields.Test plan
npm testgreen: 1678 tests, 0 fail (sim suite 14/14, ~125s).🤖 Generated with Claude Code