fix(roadmap): preserve authored progress when rendering local drafts

bun scripts/roadmap.ts --check renders local issue drafts, but the local renderer wrote whole files rather than replacing the generated section. A release-consumer verification removed five committed progress sections covering specialist routing, forester recovery, browser elimination and replay compatibility. Remote publishing already preserves content through bounded markers; local rendering did not use that contract.

The source fix uses the same bounded-section merger for local drafts and the index. Existing unbounded drafts are migrated only when their generated prefix exactly matches the current canonical catalog. Unknown edited legacy boundaries fail without changing the file. Authored progress is retained outside the closing marker. This preserves the command's documented validate-and-render behavior.

Retained filesystem regressions reproduce the actual overwrite and verify local updates, safe legacy migration, an unmarked index, refusal without modification, and idempotence. Nine roadmap tests pass (32 assertions); the actual CLI rerender preserves all108 files byte for byte, including recovered and newly authored notes. Lint and app/tools/STX types pass.

The fix is being committed with the current browser-first work and will be closed only after the owning main CI is qualified. Related: #4 and #191.

The fix is on main in 808e064, with the retained preservation receipt. All 107 drafts and the local index now use bounded generated sections. Five erased authored progress sections were recovered from their committed bytes. Unknown edited legacy boundaries fail without modification.

Nine filesystem/catalog tests pass with 32 assertions. The actual CLI and the complete installed-consumer verifier preserve all 108 files byte for byte, including authored progress. Full consumer types, lint and tests pass. Exact main CI40208919317 is running; leaving this open until that owning check completes.

Exact main CI 40208919317 succeeded on 85ac0f1, which remains origin/main. The original job log confirms 272 unit tests, zero failures, 22,758 assertions.

The original campaign-browser-check artifact 12604504234 is 19,659 bytes. Its SHA-256 481b25aad73ed1cad91acf0c5bb7e1137055e895aaedf5b9f6522c852275d3f4 matches GitHub's digest, every ZIP CRC passes, and every recorded assertion across 385 browser steps passes with zero console, network or collection errors. The complete normal seed-2 battle ran 610,472 ms, reached defeat, then acknowledged save and passed the seed/outcome assertions after a real reload. The archive contains diagnostics and media identities only, with no original raster upload.

This qualifies the specific source fixes and the published Stacks 0.75.310 adoption recorded in the source/publication and browser acceptance receipts. The broader roadmap remains open for human-victory coverage, all seeds, factions, religious AI, original Gold balance/timing, campaigns and complete native applications.