Development record
The claim parser and stamper are blind to a multi-line HTML comment, so a commented-out bullet under Scope Conditions is counted as a live condition, the stamp writes a marker inside the comment, the marker's closing sequence terminates the outer comment early, a stray closing sequence renders as prose, the parked condition carries a live identity, and ready reports READY — a rewrite that corrupts rendered content. The resolution of iss-2608300235388164 does not cover the comment clause its body names. Extend the mask to a comment span (an unclosed opener masks until the line carrying the closer), let the gate name it and the stamp refuse it exactly as for a fence.
The claim parser and stamper are blind to a multi-line HTML comment, so a commented-out bullet under Scope Conditions is counted as a live condition, the stamp writes a marker inside the comment, the marker's closing sequence terminates the outer comment early, a stray closing sequence renders as prose, the parked condition carries a live identity, and ready reports READY — a rewrite that corrupts rendered content. The resolution of iss-2608300235388164 does not cover the comment clause its body names. Extend the mask to a comment span (an unclosed opener masks until the line carrying the closer), let the gate name it and the stamp refuse it exactly as for a fence.
Frontmatter
| id | iss-2608300259316871 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | major |
.abcd/work/issues/resolved/iss-2608300259316871-stamp-writes-into-a-commented-out-bullet.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2608300235388164The claim parser and stamper are fence-blind and comment-blind: a Scope Conditions heading inside a fenced code block shadows the real section (first match wins) so intent plan writes a marker into the fence and intent ready reports READY on the example while the real conditions go unchecked; a fenced example bullet under the real heading is stamped and counted; a commented-out block is read as live and the stamp's closing sequence ends the outer comment early; a hand-typed marker of the wrong shape is silent prose, gets a real marker glued beside it, and the bogus comment leaks into the JSON text; a second Scope Conditions heading is ignored without report; stampPlanned is a read-modify-write with no lock. Track fence state in sectionLineRange, refuse to stamp a section containing a fence or a duplicate heading, fault a malformed marker by name with a delete-it remedy.