Development record
itd-183 review residue: a projected field takes site.Section.Body, which ends at the next heading of any level, so a ### under a projected ## is dropped silently while the redactor uses the level-aware rule; the intent projection names Scope Conditions and Mechanism, headings no shipped record carries, so the charter's five-fields claim is not what the run does (three fields travel today); the two artefact writes are sequential os.WriteFile calls, non-atomic and overwrite-in-place; git status collapses an untracked directory so admitted files inside it are not refused; a preamble before --- lets origin through on whole-file rows (record_schema refuses such records); storeNodeType carries adr/iss entries no row uses; the --dry-run help overclaims when --out is inside the repository.
itd-183 review residue: a projected field takes site.Section.Body, which ends at the next heading of any level, so a ### under a projected ## is dropped silently while the redactor uses the level-aware rule; the intent projection names Scope Conditions and Mechanism, headings no shipped record carries, so the charter's five-fields claim is not what the run does (three fields travel today); the two artefact writes are sequential os.WriteFile calls, non-atomic and overwrite-in-place; git status collapses an untracked directory so admitted files inside it are not refused; a preamble before --- lets origin through on whole-file rows (record_schema refuses such records); storeNodeType carries adr/iss entries no row uses; the --dry-run help overclaims when --out is inside the repository.
Frontmatter
| id | iss-2608300229100392 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2608300229100392-itd-183-review-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