The Shipped heading is still located fence-blind #183

New issue

Closed

opened 2026-08-16 01:18:56 +00:00 by john · 1 comment

john commented

2026-08-16 01:18:56 +00:00

Owner

From the phase 2 risk_surface review (medium, adjudicated survivor).

Phase 2 made the ## Active bound fence-aware by taking both ends from sectionSpan, on the stated reason that a start found fence-blind cannot be repaired by a fence-aware end. The ## Shipped heading two steps later is still a bare findIndex over a ^## Shipped$ regex, so a requirements file carrying a fenced template example with ## Shipped in it appends the archived rows inside the code fence instead of to the real section.

The shipped templates/REQUIREMENTS.md is exactly the shape that made the Active reader wrong, so the same file shape reaches this one.

Found in: cadence-core/bin/lib/milestone-prune.mjs (the Shipped landing step)

From the phase 2 risk_surface review (medium, adjudicated survivor). Phase 2 made the `## Active` bound fence-aware by taking both ends from `sectionSpan`, on the stated reason that a start found fence-blind cannot be repaired by a fence-aware end. The `## Shipped` heading two steps later is still a bare findIndex over a `^## Shipped$` regex, so a requirements file carrying a fenced template example with `## Shipped` in it appends the archived rows inside the code fence instead of to the real section. The shipped templates/REQUIREMENTS.md is exactly the shape that made the Active reader wrong, so the same file shape reaches this one. Found in: cadence-core/bin/lib/milestone-prune.mjs (the Shipped landing step)