test(prose): feature happy-path corpus — five worlds, seven cases#546
Open
leeovery wants to merge 2 commits into
Open
test(prose): feature happy-path corpus — five worlds, seven cases#546leeovery wants to merge 2 commits into
leeovery wants to merge 2 commits into
Conversation
Stage 3a of design/prose-tests.md. The canonical feature `pay` at five stop points (created/discussed/specified/planned/implemented), built by staged recipes mirroring the sim's pinned call sequences with the artifacts the prose actually reads — template-shaped session log, real local-markdown task files. Seven cases cover start surfacing, continue-feature selection and routing, every phase entry's validation-and-handoff, and the implementation pickup to first task start. Claims verified against the prose at authoring time; entry walks pin mutation-freedom (manifest-absent assertions) and the pickup pins the engine state contract (status + current_task). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…h — task init creates Authoring the corpus surfaced it: no prose site anywhere issues `topic start` for implementation — `task init` owns creation (process Step 0's created arm), and only that arm writes analysis_cycle_total, linters, project_skills, and current_phase. The fixture had copied the sim's off-prose order (topic start first), leaving a world shape no real run produces; the snapshot diff shows the four recovered fields. The implementation case now pins mode=created on the fresh path. The sim carries the same off-prose order — proposed separately. 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
payfrozen at each phase boundary (feature-created→feature-implemented), composed from staged builders infixtures/_shared/feature-mainline.cjs. Engine calls mirror the pipeline simulation's pinned sequences; content files are what the prose actually reads: a template-shaped discovery session log (Exploration backfilled, per confirm-trigger), a discussion with decisions, a spec, and real local-markdown task files per the format's authoring contract. All byte-deterministic (verified twice).tests/prose/feature/cases.md): workflow-start surfaces the fresh feature; continue-feature selection (no auto-select even with one item) and forward routing to discussion; discussion/specification/planning/review entry validation-and-handoff walks; and the implementation pickup through entry → task loop →pay-1-1started. Entry cases carry "restraint" assertions (manifest absent …— entries must not mutate before the process skill), the pickup pinsstatus=in-progress+current_task=pay-1-1.Test plan
npm testgreen: 1688 tests, 0 fail — corpus validation + all six fixtures rebuild byte-identical (~16s).feature-plannedworld, ran the prescribedtopic start/task init/task startcalls, confirmedcurrent_tasklands on the implementation item./prose-test --allafter merge — the corpus's maiden run doubles as the framework's first real proving.🤖 Generated with Claude Code