The markup-shape refusal reads the whole document instead of the unfenced body, so a fenced HTML example refuses every assembly. verifyRedaction in internal/core/reading/project.go calls markupShapeOf over strings.Join(lines) and ignores the fence mask it already computed, unlike rawHTMLHeading and the indented-ATX and excluded-key scans beside it, which all take the mask. A code block showing an HTML attribute whose value opens on the line after its equals sign is an EXAMPLE, not markup the bundle carries; any admitted markdown document holding one refuses the run at every position. Expected: the shape scan reads the unfenced body, with fenced lines blanked rather than dropped so a line number still names the document's own line, and the same shape outside a fence still refuses.

The markup-shape refusal reads the whole document instead of the unfenced body, so a fenced HTML example refuses every assembly. verifyRedaction in internal/core/reading/project.go calls markupShapeOf over strings.Join(lines) and ignores the fence mask it already computed, unlike rawHTMLHeading and the indented-ATX and excluded-key scans beside it, which all take the mask. A code block showing an HTML attribute whose value opens on the line after its equals sign is an EXAMPLE, not markup the bundle carries; any admitted markdown document holding one refuses the run at every position. Expected: the shape scan reads the unfenced body, with fenced lines blanked rather than dropped so a line number still names the document's own line, and the same shape outside a fence still refuses.

Grounds

• pursued: a fenced code block showing markup is an example and never material the mask must bound, so an admitted markdown document holding one assembles at every position while unfenced markup of the same shape still refuses. What would show it wrong: an assembly refused over a document whose only occurrence of the shape is inside a fence, or an unfenced occurrence admitted.