docs(roadmap): #96 shipped — escape-mechanics ask delivered on tf PR 7

[dividedby]

What

Roadmap bookkeeping for #96 — the deliverable itself (the framed leaf ask) already shipped as a comment on skrabe/tweakcc-fixed PR 7: skrabe/tweakcc-fixed#7 (comment).

Closes #96.

The delivered ask (summary)

Single intent-ping comment (issues disabled on tf; doctrine: comment over draft PR for a pure ask), sequenced after #93's evidence comment on the same PR. Both options framed with honest costs, his pick, nothing implemented:

• (a) extractor emits a per-prompt delimiter field (backtick | quote) in the prompts JSON — data already read at apply time via content[matchIndex-1] in his systemPrompts.ts; cost = schema addition riding every future extraction.
• (b) an auditMisbinds-style escape audit flagging escaped placeholders under quote delimiters / unescaped literal ${...} under backtick; cost = zero until run, catches at audit time not authoring time.

Evidence re-verified before posting: cb08b73 revert rationale (quote-context corruption, the lcc PR 5 class); prompts-2.1.170.json has no delimiter context; the ${JSON.stringify(...)} literals behind #94's advisory orphan JSON confirmed in both fable-5 and opus-4-8 sets at lcc pr-6.

Roadmap change

• Leaf ask: make escape-or-not mechanical — per-prompt delimiter context in extraction output or an escape audit (draft + intent ping) #96 row → Done section with the delivery URL and both options recorded; wave line updated.
• A future implementation (if/when skrabe picks an option and passes it to us) is a new row, not a reopen.

🤖 Generated with Claude Code