Development record
itd-183 third-round residue: headings that render identically to an excluded title but differ in bytes (bold, code span, an NBSP inside) travel — compare slugs in the verifier and refuse; a relative --out the operator typed is absolutised against the working directory and echoed unscrubbed on the success surface and in --json out_dir, which the plugin page tells the host to report — echo the operator's string or route through the root redaction; a frontmatter block whose keys are all indented one space is valid YAML that both the field reader and the excluded-key pattern miss so origin travels — refuse; the parse fallback comment overclaims (an escaped tag in a yaml or toml file or a JSON array is admitted; hand-rewritten, so ruling 18 holds).
itd-183 third-round residue: headings that render identically to an excluded title but differ in bytes (bold, code span, an NBSP inside) travel — compare slugs in the verifier and refuse; a relative --out the operator typed is absolutised against the working directory and echoed unscrubbed on the success surface and in --json out_dir, which the plugin page tells the host to report — echo the operator's string or route through the root redaction; a frontmatter block whose keys are all indented one space is valid YAML that both the field reader and the excluded-key pattern miss so origin travels — refuse; the parse fallback comment overclaims (an escaped tag in a yaml or toml file or a JSON array is admitted; hand-rewritten, so ruling 18 holds).
Frontmatter
| id | iss-2608300320167335 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2608300320167335-itd-183-third-round-residue.md
open on GitHub ↗ · commit history ↗
mentions1
- itd-183The cold reading sees exactly what the assembler passes — positive inclusion, field projection, and a per-run manifest