Development record
opensTag restates htmlTagRe's rule in hand-written code giving one file two definitions of what opens a tag
issueresolvednitpickiss-2608301251394412
opensTag restates htmlTagRe's rule in hand-written code giving one file two definitions of what opens a tag
Found by the round-9 adversarial RUTHLESS review of build/itd-183.
opensTag (project.go:670-679) restates htmlTagRe's rule in hand-written
code -- its own comment says "on htmlTagRe's own rule". That is two definitions
of "what opens a tag" in one file.
Repo law (one-canonical-primitive): flag for consolidation on the second copy, never let a third appear. Flagged here so the floor intent inherits it.
Grounds
- pursued: we expect the attribute walk to open exactly where htmlTagRe matches on any input the pattern reads to its closing bracket; an input where opensTag and htmlTagRe disagree would show it wrong
Frontmatter
| id | iss-2608301251394412 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | nitpick |
.abcd/work/issues/resolved/iss-2608301251394412-openstag-restates-htmltagre-s-rule-in.md
open on GitHub ↗ · commit history ↗
mentions3
- itd-183The cold reading sees exactly what the assembler passes — positive inclusion, field projection, and a per-run manifest
- itd-194The reading include table admits only what the exclusion floor can read
- spc-2609021003136831The include table declares what the floor parses, the floor refuses the markdown it cannot resolve, and the manifest marks every item it did not examine