feat(engine): entry-gate + phase-note — entry validation derives engine-side#497
Merged
Conversation
This was referenced Jul 22, 2026
Merged
Merged
leeovery
force-pushed
the
feat/render-transaction-folds
branch
from
July 22, 2026 14:24
7278f98 to
b37c869
Compare
leeovery
force-pushed
the
feat/render-entry-validation
branch
from
July 22, 2026 14:24
d375ed8 to
c2fe68a
Compare
leeovery
force-pushed
the
feat/render-transaction-folds
branch
from
July 22, 2026 14:25
b37c869 to
b3991a4
Compare
leeovery
force-pushed
the
feat/render-entry-validation
branch
from
July 22, 2026 14:25
c2fe68a to
776855e
Compare
leeovery
force-pushed
the
feat/render-transaction-folds
branch
from
July 22, 2026 14:25
b3991a4 to
e8afd7d
Compare
leeovery
force-pushed
the
feat/render-entry-validation
branch
from
July 22, 2026 14:26
776855e to
8df11bf
Compare
leeovery
force-pushed
the
feat/render-transaction-folds
branch
from
July 22, 2026 14:26
e8afd7d to
d269db1
Compare
leeovery
force-pushed
the
feat/render-entry-validation
branch
from
July 22, 2026 14:26
8df11bf to
1c86946
Compare
…erives engine-side The last surface family: entry prerequisite checks leave the prose. - entry-gate <wu>.<phase>.<topic> — the engine derives the verdict from manifest state and returns either nothing (clear — proceed) or the terminal blocker display: planning maps every specification status (missing / in-progress / proposed / superseded with its successor / promoted with its target); implementation and review check their plan/implementation prerequisites; specification is work-type-aware (feature and cross-cutting: the topic discussion; bugfix: the investigation; epic: at least one completed discussion). validate-spec and validate-source collapse onto one call each; implementation and review validate-phase drop their read-and-branch sections. - phase-note — the entry one-liners (Resuming/Reopening/Starting X) render from the address with an optional noun override (planning says "plan"); ten prose templates swapped. - selection not-found — the continue-* view snapshot for an unknown name now carries the terminal display; the five validate-selection references emit the section instead of authoring the block. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
leeovery
force-pushed
the
feat/render-entry-validation
branch
from
July 22, 2026 14:26
1c86946 to
3bc63d7
Compare
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.
Stage 6b of the render-surfaces programme (design log: #489; base: #496). The last surface family: entry prerequisite validation moves from prose read-and-branch to engine derivation.
Surfaces
render entry-gate <wu>.<phase>.<topic>— full absorption: the engine reads the manifest and returns either an empty response (clear — the flow proceeds) or the terminalDISPLAY: entry blocker. State machines per target phase:validate-spec.md(6 conditional blocks + a manifest read) andvalidate-source.md(4 work-type branches × 2-3 blocks + reads) each collapse to one call and two branches; implementation/reviewvalidate-phasedrop their read-and-branch prerequisite sections. Every blocker text byte-matches the old prose.render phase-note <wu>.<phase>.<topic> --verb <Word> [--noun <word>]— the entry one-liners (Resuming/Reopening/Starting …), ten templates swapped across seven entries (planning keeps its "Reopening plan" wording via--noun).Selection not-found — the continue-*
viewsnapshot for an unknown name now appends the per-type terminal display; fivevalidate-selectionreferences emit the section instead of authoring it.Test plan
npm test— 1518/1518. Typecheck + conventions lint clean.🤖 Generated with Claude Code
Stack