Development record
itd-177 second-round residue: the structural faults (duplicated heading, fenced section) are checked only after the claim-state switch, so a nullity or empty first section hides a second Scope Conditions heading carrying real bullets and the gate passes while the stamp refuses; the malformed-marker guard is case-sensitive so a capitalised near-miss gets a real marker glued beside it; no size check after stamping, so a record near the read cap can be written larger than its own reader accepts and the next Load refuses the whole corpus; a marker inside an inline code span is accepted and excised; the plugin page says every fault is refused by the stamp where two-marker and duplicated-id bullets are skipped rather than refused.
itd-177 second-round residue: the structural faults (duplicated heading, fenced section) are checked only after the claim-state switch, so a nullity or empty first section hides a second Scope Conditions heading carrying real bullets and the gate passes while the stamp refuses; the malformed-marker guard is case-sensitive so a capitalised near-miss gets a real marker glued beside it; no size check after stamping, so a record near the read cap can be written larger than its own reader accepts and the next Load refuses the whole corpus; a marker inside an inline code span is accepted and excised; the plugin page says every fault is refused by the stamp where two-marker and duplicated-id bullets are skipped rather than refused.
Frontmatter
| id | iss-2608300259321329 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2608300259321329-itd-177-second-round-residue.md
open on GitHub ↗ · commit history ↗
mentions1
- itd-177An intent's claims are typed and its scope conditions keep their identity across edits — the readiness gate refuses an intent that leaves a context claim unrecorded