fix(prose-tests): a confirmed failure reports both runs' checks - #581
Merged
Conversation
This was referenced Jul 27, 2026
Merged
leeovery
force-pushed
the
fix/prose-orchestrator-per-run-checks
branch
from
July 27, 2026 15:57
f99fd81 to
15c7654
Compare
leeovery
force-pushed
the
fix/prose-world-log-is-the-walkers
branch
from
July 27, 2026 15:58
9412e52 to
10e4b3f
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-world-log-is-the-walkers
branch
from
July 27, 2026 15:59
10e4b3f to
2b28fbf
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-world-log-is-the-walkers
branch
from
July 27, 2026 16:00
2b28fbf to
d4cb1fa
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-world-log-is-the-walkers
branch
from
July 27, 2026 16:01
d4cb1fa to
d922066
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-world-log-is-the-walkers
branch
from
July 27, 2026 16:02
d922066 to
63505b3
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-world-log-is-the-walkers
branch
from
July 27, 2026 17:05
63505b3 to
d369706
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-world-log-is-the-walkers
branch
from
July 27, 2026 17:06
d369706 to
f6d5a76
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-world-log-is-the-walkers
branch
from
July 27, 2026 17:06
f6d5a76 to
8395c31
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-world-log-is-the-walkers
branch
from
July 27, 2026 17:07
8395c31 to
eeac038
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-world-log-is-the-walkers
branch
from
July 27, 2026 17:08
eeac038 to
b10ee75
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-world-log-is-the-walkers
branch
from
July 27, 2026 17:08
b10ee75 to
57763a4
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-world-log-is-the-walkers
branch
from
July 27, 2026 17:09
57763a4 to
650158a
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-world-log-is-the-walkers
branch
from
July 27, 2026 17:09
650158a to
12159bd
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-world-log-is-the-walkers
branch
from
July 27, 2026 17:09
12159bd to
5864743
Compare
leeovery
force-pushed
the
fix/prose-orchestrator-per-run-checks
branch
from
July 27, 2026 17:09
b8a86ad to
29ce889
Compare
The quick-fix verdict showed one CHECKS block with two FAILs in it. What actually happened: the first walk's checks all passed and it failed only on a path step; the confirmation walk then skipped two prescribed calls and its checks caught that. The verdict's single block was the second run's, standing silently for both — reading as though the case's checks failed, when the check failures were one walk's behaviour. The orchestrator was following its own instruction: report the evidence from the second run. That instruction is right for the path evidence and wrong for the checks, because checks that pass on one walk and fail on the other are not a property of the prose at all. They are the two walks behaving differently — and that variance is itself a finding, the exact signal that separates a defect from an unreliable walk. A confirmed or flaky verdict now carries both runs' check blocks, labelled per run, with any divergence between them named as walk variance. Untangling this from the verdict took transcript archaeology that the report should have made unnecessary. 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 verdict showed one CHECKS block with two FAILs. What actually happened: the first walk's checks all passed and it failed only on a path step; the confirmation walk then skipped two prescribed calls and its checks caught that. The single block was the second run's, standing silently for both — reading as though the case's checks failed, when the failures were one walk's behaviour.
The orchestrator was obeying its own instruction — report the evidence from the second run — which is right for path evidence and wrong for checks: checks that pass on one walk and fail on the other are not a property of the prose. They're the two walks behaving differently, and that variance is itself a finding — the exact signal separating a defect from an unreliable walk.
A confirmed or flaky verdict now carries both runs' check blocks, labelled (
first walk:/confirmation:), with any divergence named as walk variance. Untangling this took transcript archaeology the report should have made unnecessary.Test plan
🤖 Generated with Claude Code
Stack