fix(prose-tests): each prescribed command runs as written - #582
Merged
Conversation
This was referenced Jul 27, 2026
Merged
leeovery
force-pushed
the
fix/prose-walker-run-as-written
branch
from
July 27, 2026 15:57
4420d72 to
9725f1e
Compare
leeovery
force-pushed
the
fix/prose-orchestrator-per-run-checks
branch
from
July 27, 2026 15:58
15c7654 to
cdb4039
Compare
leeovery
force-pushed
the
fix/prose-walker-run-as-written
branch
from
July 27, 2026 15:58
9725f1e to
b41c414
Compare
leeovery
force-pushed
the
fix/prose-orchestrator-per-run-checks
branch
from
July 27, 2026 15:59
cdb4039 to
788b27a
Compare
leeovery
force-pushed
the
fix/prose-walker-run-as-written
branch
from
July 27, 2026 15:59
b41c414 to
40009f9
Compare
leeovery
force-pushed
the
fix/prose-orchestrator-per-run-checks
branch
from
July 27, 2026 16:00
788b27a to
220247c
Compare
leeovery
force-pushed
the
fix/prose-walker-run-as-written
branch
from
July 27, 2026 16:00
40009f9 to
964711d
Compare
leeovery
force-pushed
the
fix/prose-orchestrator-per-run-checks
branch
from
July 27, 2026 16:01
220247c to
b36e00f
Compare
leeovery
force-pushed
the
fix/prose-walker-run-as-written
branch
from
July 27, 2026 16:01
964711d to
d431692
Compare
leeovery
force-pushed
the
fix/prose-orchestrator-per-run-checks
branch
from
July 27, 2026 16:02
b36e00f to
36a43a5
Compare
leeovery
force-pushed
the
fix/prose-walker-run-as-written
branch
from
July 27, 2026 16:02
d431692 to
a77e9ff
Compare
leeovery
force-pushed
the
fix/prose-orchestrator-per-run-checks
branch
from
July 27, 2026 17:05
36a43a5 to
0c91077
Compare
leeovery
force-pushed
the
fix/prose-walker-run-as-written
branch
from
July 27, 2026 17:05
a77e9ff to
fb6b748
Compare
leeovery
force-pushed
the
fix/prose-orchestrator-per-run-checks
branch
from
July 27, 2026 17:06
0c91077 to
ef246f0
Compare
leeovery
force-pushed
the
fix/prose-walker-run-as-written
branch
from
July 27, 2026 17:06
fb6b748 to
a8f2f19
Compare
leeovery
force-pushed
the
fix/prose-orchestrator-per-run-checks
branch
from
July 27, 2026 17:06
ef246f0 to
f3f73ca
Compare
leeovery
force-pushed
the
fix/prose-walker-run-as-written
branch
from
July 27, 2026 17:06
a8f2f19 to
b684124
Compare
leeovery
force-pushed
the
fix/prose-orchestrator-per-run-checks
branch
from
July 27, 2026 17:07
f3f73ca to
5ed559d
Compare
leeovery
force-pushed
the
fix/prose-walker-run-as-written
branch
from
July 27, 2026 17:07
b684124 to
967b9ee
Compare
leeovery
force-pushed
the
fix/prose-orchestrator-per-run-checks
branch
from
July 27, 2026 17:08
5ed559d to
1a12bc8
Compare
leeovery
force-pushed
the
fix/prose-walker-run-as-written
branch
from
July 27, 2026 17:08
967b9ee to
34347e9
Compare
leeovery
force-pushed
the
fix/prose-orchestrator-per-run-checks
branch
from
July 27, 2026 17:08
1a12bc8 to
3224e10
Compare
leeovery
force-pushed
the
fix/prose-walker-run-as-written
branch
from
July 27, 2026 17:08
34347e9 to
cf257dd
Compare
leeovery
force-pushed
the
fix/prose-orchestrator-per-run-checks
branch
from
July 27, 2026 17:09
3224e10 to
bbe8844
Compare
leeovery
force-pushed
the
fix/prose-walker-run-as-written
branch
from
July 27, 2026 17:09
cf257dd to
2898cfe
Compare
leeovery
force-pushed
the
fix/prose-orchestrator-per-run-checks
branch
from
July 27, 2026 17:09
bbe8844 to
b8a86ad
Compare
leeovery
force-pushed
the
fix/prose-walker-run-as-written
branch
from
July 27, 2026 17:09
2898cfe to
85fec01
Compare
leeovery
force-pushed
the
fix/prose-orchestrator-per-run-checks
branch
from
July 27, 2026 17:09
b8a86ad to
29ce889
Compare
leeovery
force-pushed
the
fix/prose-walker-run-as-written
branch
from
July 27, 2026 17:09
85fec01 to
4045d5c
Compare
The quick-fix confirmation walk skipped two commands the prose prescribes unconditionally — the project-default format set and the scoping start/complete pair — and still landed a world the asserter passed, having converged on the same state by other means. The deterministic checks caught it, which is what they are for; but the walker rule it slipped through was real. "Follow the prose literally" never said what literal means for a fenced command. Now it does: one call per fence, never batched, merged, reordered, or replaced by an equivalent that lands the same state. A walk that reaches the right end by different calls has not tested the calls the prose prescribes, and its record claims the prose does something it does not. Co-Authored-By: Claude Opus 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
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
The quick-fix confirmation walk skipped two commands the prose prescribes unconditionally — the project-default format set and the scoping start/complete pair — and still landed a world the asserter passed, having converged on the same state by other means.
calls_includecaught it, which is what it's for; but the walker rule it slipped through was real: "follow the prose literally" never said what literal means for a fenced command.Now it does — one rule added:
Test plan
🤖 Generated with Claude Code
Stack