Development record
graveyard evidence is terminal-safe but not markdown-safe and untyped: termsafe.Sanitize leaves CommonMark and raw-HTML openers for the layer-3 interpreter to read, and cap or shadow notices share the plain evidence string array with record-influenced text, so a crafted path can forge an omission notice — a typed field or CleanProse pass closes the channel
issueresolvedminoriss-2608270926037088
graveyard evidence is terminal-safe but not markdown-safe and untyped: termsafe.Sanitize leaves CommonMark and raw-HTML openers for the layer-3 interpreter to read, and cap or shadow notices share the plain evidence string array with record-influenced text, so a crafted path can forge an omission notice — a typed field or CleanProse pass closes the channel
Grounds
- pursued: a crafted path or bullet can no longer pass for an omission notice or carry live markup to the layer-3 interpreter; shown wrong if any graveyard builder writes record text into notices or bypasses gvText, which TestGraveyardRecordTextIsMarkdownSafe and TestGraveyardCraftedRecordTextStaysEvidence would catch
Frontmatter
| id | iss-2608270926037088 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2608270926037088-graveyard-evidence-is-terminal-safe-but.md
open on GitHub ↗ · commit history ↗