plastic-roadmap

# Roadmap A roadmap is a named, ordered, delivery-side collection of intents: the delivery-side counterpart to a release (completion-side, `CHANGELOG.md`). It lives at `roadmaps/{slug}.md`, a sibling of `INDEX.md` wherever `INDEX.md` lives: the global tier's `~/.plastic/roadmaps/` (beside `~/.plastic/INDEX.md`), or a project's root, `~/.plastic/projects/{slug}/roadmaps/` (beside that project's `INDEX.md` and `project.yml`). It never sits inside `store/`, which holds intent directories, not project artifacts. A roadmap file has four parts: a title/meta header, `## Goal` (prose), `## Batches` (ordered; entries inside a batch are parallel-safe, batches run sequentially), and an append-only dated `## Log`. A roadmap written before owner ruling 145 may instead use the legacy `## Waves` heading; reading accepts both, but every new roadmap is scaffolded with `## Batches`, and an existing roadmap file's heading is never renamed to migrate it. Each batch entry mirrors that intent's status in `INDEX.md` (`queued`/`delivering`/`delivered`/`abandoned`/`blocked`). **`INDEX.md` is the single writer of intent status; on any conflict INDEX wins and the roadmap entry is corrected to match.** The skill operates on the roadmap file directly via Read/Edit. The one deterministic helper it uses is the savepoint ledger writer (`scripts/roadmap-savepoint`, `append`/`rebuild`); every verb's closing step calls `append` after its Read/Edit, and the roadmap `.md` file itself stays Read/Edit-only. #...