FIX STEPS, asserted on `task.steps` rather than on a spy. A failing FINAL verification
and a Code Review REVISE each append pending named steps carrying their gate provenance,
and the card is re-dispatched to run them; completed implementation steps stay done,
because remediation appends and never reopens. A review failure with NO REVISE verdict
appends nothing — a transport error must not manufacture work. And no node id other than
those two gates can reach the appender, which is what keeps a red test INSIDE a step the
step's own problem: the executor fixes it there instead of littering the checklist.
The new tests drive the real routing seam and the real appender against the real built-in
registry — an injected IR is resolved away by workflow id and would have proved nothing.
CATALOG. `builtin-workflows-lifecycle.test.ts` never received an EXPECTATIONS entry when
V2 was registered, so its catalog-coverage assertion has been red on main since. The merge
gate does not run that file, which is why it survived. Its trail is identical to
builtin:coding-ideas by design: a read-only review lane changes what happens inside the
working columns, not where the card goes.
REGISTRY. The description still advertised "verify … summarize", steps that no longer
exist, and the layout still positioned four deleted nodes plus drew Documentation to the
LEFT of Code Review — so the editor rendered the review lane backwards against its own
edges. Both now match the graph.
AUDIT. `implementation-only-leakage` no longer flags `testing|verification`. That regex
belonged to the revision where a review gate ran the tests; testing came back to the
executor, so the planner emits that step on purpose and every V2 card was reporting
leakage against its own intended plan. Documentation and delivery are still flagged.
pnpm lint 0 errors, test:gate green, core + engine typecheck clean, 227 tests across the
touched files.
8328b458b0