test(prose): a case starts where a session starts#563
Open
leeovery wants to merge 1 commit into
Open
Conversation
No session ever begins at a navigation skill, a processing skill, or a reference. `workflow-start` is the user's way in; after a context clear the bridge's plan file invokes a `workflow-*-entry` skill, or `workflow-discovery` for an epic continuation. That is the whole list. Four cases ignored it — two opened at `workflow-continue-*`, one at `workflow-discussion-process`, one inside `root-cause-validation.md`. A walk carries only the context it accumulates, so starting one in the middle leaves the world right and the reading that got there missing. The prose is then judged under conditions it was never written for, and the verdict is worthless whichever way it lands. continue-feature had the flaw written into its own expected path: "initialisation is casing only — no boot and no migrations, which the entry skill has already guaranteed". A case documenting the context it does not have. It is also the case that consumed a day of investigation producing findings that dissolved on inspection. The four are retired rather than repaired. Their stubs stay — stubs are a reusable library, not case-scenery. `entry` is now required and validated, so this cannot drift back in by authoring discipline alone. The same reasoning governs the far end of a walk, recorded as P9: stop at a gate and the delta is empty, the claims decay into descriptions of a display, and the asserter is left comparing the walker's account of what it showed against the case's account of what it should have shown — with no independent ground truth anywhere. Coverage of continue-* routing goes with them, and is not replaced here: it belongs in a case that starts at workflow-start and walks through selection until the route lands real state. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
leeovery
force-pushed
the
test/prose-cases-start-where-sessions-start
branch
from
July 26, 2026 18:52
52d39d6 to
5e3be38
Compare
This was referenced Jul 26, 2026
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
workflow-startis the user's way in; after a context clear the bridge's plan file invokes aworkflow-*-entryskill, orworkflow-discoveryfor an epic continuation. Verified against all six bridge continuation references.continue-feature-routes-to-discussion,continue-bugfix-routes-to-investigation(navigation skills),discussion-session-substituted(processing skill),root-cause-validation-clean-verdict(a reference). A walk carries only the context it accumulates, so a mid-session start leaves the world right and the reading that got there missing. The prose is judged under conditions it was never written for, and the verdict is worthless either way.continue-featurehad the flaw written into its own expected path: "initialisation is casing only — no boot and no migrations, which the entry skill has already guaranteed." A case documenting the context it doesn't have. It's also the case that consumed a day producing findings that dissolved on inspection.entryis now required and validated inlib/cases.cjs, so it can't drift back in on authoring discipline.design/prose-tests.md, with the same reasoning applied to where a walk ends: stop at a gate and the delta is empty, claims decay into descriptions of a display, and the asserter compares the walker's account of what it showed against the case's account of what it should have shown — no independent ground truth anywhere.Coverage note
Coverage of
continue-*routing goes with these cases and is not replaced here. It belongs in a case that starts atworkflow-startand walks through selection until the route lands real state — the "walk further" shape. Flagging rather than silently dropping.Test plan
node --testprose suites — 64/64, including 9 new tests covering each accepted and rejected entry class, a plausible-but-absent skill, and the live corpusCLAUDE.mdanddesign/prose-tests.mdupdated🤖 Generated with Claude Code
Stack