Development record
itd-188 fourth-round residue: spc-66's Tests section still says the guard folds every separator spelling to a slash, while the guard now folds only the ASCII reverse solidus and spaced separators and refuses every other non-ASCII spelling — a maintainer trusting the spec could allow a lookalike in prose believing it still folds; the definition's untrusted-input banner says an embedded instruction is a thing a fidelity flag reports while the flag section requires two disagreeing pieces of material, and the canary's behaviour text names a different candidate flag than its exemplar emits; the residual-entity regex refuses any ampersand followed by a letter (Q&A) without the comment saying so; the bypass table asserts only that some finding exists, so the Cf branch's message is pinned by one case.
itd-188 fourth-round residue: spc-66's Tests section still says the guard folds every separator spelling to a slash, while the guard now folds only the ASCII reverse solidus and spaced separators and refuses every other non-ASCII spelling — a maintainer trusting the spec could allow a lookalike in prose believing it still folds; the definition's untrusted-input banner says an embedded instruction is a thing a fidelity flag reports while the flag section requires two disagreeing pieces of material, and the canary's behaviour text names a different candidate flag than its exemplar emits; the residual-entity regex refuses any ampersand followed by a letter (Q&A) without the comment saying so; the bypass table asserts only that some finding exists, so the Cf branch's message is pinned by one case.
Frontmatter
| id | iss-2608300232312077 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2608300232312077-itd-188-fourth-round-residue.md
open on GitHub ↗ · commit history ↗