test(conventions): templated-fence ratchet — check 13 lands D4 (7c)

[leeovery]

Stage 7c — the closing PR of the render-surfaces stack (design log: #489; base: #500). D3 and D4 decided and landed.

D4 — the ratchet lint (check 13)

"A templated menu/display fence in prose is a violation" — now mechanical. The census scanner (rendering-instruction line → following fence; markers/signposts excluded as chrome; templated = placeholder syntax or @if/@foreach) counts per file and compares against RATCHET_PINS, the 174 remaining sites across 81 files. Drift fails both ways:

• count above pin → "render new output from the engine — a genuinely judgment-only site is pinned deliberately, with the PR saying why"
• count below pin → "a site was converted; shrink its pin (the ratchet only tightens)"
• pin for a deleted file → prune

So no new templated fence can land silently, every conversion shows up as a shrinking diff, and the pin map always mirrors reality. Zero-false-positive doctrine holds: counts, not line numbers, so unrelated edits never trip it.

D3 — static menus stay prose

Decided (a): the 83 static menus (conclude gates, y/n confirms, mode choices) have none of the failure class the programme kills — no placeholder to misfill, no state to drift from — and their grammar is already under checks 3–5. Converting them would be ~30 catalogue entries of fixed text: surfaces earned by nothing.

Test plan

• Corpus clean at the 174-site pin map (i.e., the lint passes on the stack as it stands).
• Negative fixtures: unpinned templated menu caught; pinned site sanctioned; stale over-pin caught with the shrink message; deleted-file pin caught; static menu, templated marker, and templated signpost all correctly out of scope.
• npm test — 1528/1528 (lint suite 27/27). Typecheck clean.

🤖 Generated with Claude Code

Stack

1. feat(engine): render surface catalogue — resume-gate and task-list pilots #490
2. feat(engine): finding + findings-summary surfaces — review-findings loop unified #491
3. feat(engine): task-gate surfaces — proposed-task, tasks-overview, author-task-gate, phase-tree #492
4. feat(engine): selection projection + bridge continuation surfaces #493
5. feat(engine): transaction confirmation sections — lifecycle verbs carry their own chrome #496
6. feat(engine): entry-gate + phase-note — entry validation derives engine-side #497
7. feat(engine): the fence is the frame — boxedFrame retired (D8) #498
8. feat(engine): topic complete + discovery-session close fold their kb warnings (7a) #499
9. feat(engine): resume-gate variants + entry-gate --own + phase-completed --paths (7b) #500
10. test(conventions): templated-fence ratchet — check 13 lands D4 (7c) #501 👈 current