Development record
itd-183 fourth-round residue, all Low: sameRendering models only emphasis and code marks, so a heading carrying an HTML comment or tag, an entity, a link wrapper, a homoglyph, or nested in a blockquote or list item renders as the excluded title but slugs differently (strip tags and comments, decode common entities, unwrap links before slugging, or refuse on a slug substring match and correct the comment); top-level YAML spellings of an excluded key that the line pattern misses travel (explicit key, top-level or nested flow mapping, a double-quoted key with an escape); the two --out refusals interpolate the resolved absolute directory built from the operator's relative string, which scrubPaths cannot redact when cwd is not a prefix; status.go reads run-directory names under the assembler's own scratch, worth a charter sentence so it is not mistaken for an invariant-14 breach.
itd-183 fourth-round residue, all Low: sameRendering models only emphasis and code marks, so a heading carrying an HTML comment or tag, an entity, a link wrapper, a homoglyph, or nested in a blockquote or list item renders as the excluded title but slugs differently (strip tags and comments, decode common entities, unwrap links before slugging, or refuse on a slug substring match and correct the comment); top-level YAML spellings of an excluded key that the line pattern misses travel (explicit key, top-level or nested flow mapping, a double-quoted key with an escape); the two --out refusals interpolate the resolved absolute directory built from the operator's relative string, which scrubPaths cannot redact when cwd is not a prefix; status.go reads run-directory names under the assembler's own scratch, worth a charter sentence so it is not mistaken for an invariant-14 breach.
Frontmatter
| id | iss-2608300349309723 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2608300349309723-itd-183-fourth-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