Colby McHenry 22f92a828b docs(steps): the in-order reading, and what validating it found ...

Spec §3.13.1 describes the rail as built: what it is made of (records the same
pass makes as the links), what makes the fold possible (a guard naming the
decision it belongs to), the items, and the words. `CLAUDE.md` names
`api/program.ts` and what the guard reader now returns. `CHANGELOG.md` gets the
user-facing feature and the three fixes under it.

Both plans now say what happened: the 2026-08-29 plan carries a BUILT header
with where the build differs from it (a guard's `branch`, reading a function
once per rail, blocks as one kind carrying facts, loops needing a reading of
their own), the answers to its open questions, and a §8 recording the six
endpoints read against their source — plus the two gaps left open on purpose,
a mongoose `product.save()` the effects table does not know and the nested
`const handleX = async () => …` that is still not a node.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01REFyW9hmNrxhwN5wxRoAkC

2026-08-29 13:48:04 -05:00

..

2026-04-24-framework-resolver-extract.md

feat: wire up framework route extraction (#89)

2026-05-07 22:03:33 -05:00

2026-08-28-steps-and-screens-for-apis-and-web.md

docs(steps): the in-order reading, and what validating it found

2026-08-29 13:48:04 -05:00

2026-08-29-steps-in-code-order.md

docs(steps): the in-order reading, and what validating it found

2026-08-29 13:48:04 -05:00