Apply Roadmap Review

# Roadmap Review — Apply Accepted Refresh

You are Codex.

Goal:
Apply an accepted roadmap review packet to repository planning docs, then stop before any slice execution work starts.

## Preconditions
- Review packet exists at `changes/<yyyy-mm-dd>-roadmap-review-<slug>/`
- `ROADMAP_REVIEW.md` exists
- the human has accepted the review packet for application
- the verdict in `ROADMAP_REVIEW.md` is `REFRESH_NOW`
- `ROADMAP_PATCH.md` exists
- `DOC_IMPACT.md` exists

If any precondition fails, stop and report exactly what is missing.

## Read order
1) `ROADMAP.md`
2) `SPEC.md`
3) `ARCHITECTURE.md`
4) `README.md`
5) `docs/runbook.md`
6) `changes/<...>/ROADMAP_REVIEW.md`
7) `changes/<...>/ROADMAP_PATCH.md`
8) `changes/<...>/DOC_IMPACT.md`

## What to update

### A) ROADMAP is mandatory
Apply `ROADMAP_PATCH.md` into `ROADMAP.md`:
- preserve the roadmap format and style already used in the repo
- apply milestone, status, sequencing, and dependency changes exactly
- keep the roadmap milestone-level, not task-level
- do not create a new active slice pointer unless explicitly instructed

### B) Supporting docs are conditional but strict
Use `DOC_IMPACT.md`:
- if SPEC impact is `required`, update only the named sections in `SPEC.md`
- if ARCHITECTURE impact is `required`, update only the named sections in `ARCHITECTURE.md`
- if README/runbook impact is `required`, update only the named sections and keep changes factual
- if ADR impact is `required`, create `docs/adr/<yyyy-mm-dd>-<slug>.md` with:
  - Context
  - Decision
  - Alternatives
  - Consequences
- if any impact is `optional` or `none`, do not edit that document in this step

### C) No execution work in this step
Do not create or update:
- `changes/<slice>/PLAN.md`
- `changes/<slice>/TASK_QUEUE.md`
- `changes/<slice>/NOW.md`
- implementation code
- PR or release artifacts

This step is planning truth sync only.

## Validation checklist
- [ ] `ROADMAP.md` updated and internally consistent
- [ ] Supporting doc changes match `DOC_IMPACT.md`
- [ ] Required ADR created if flagged
- [ ] No implementation or slice execution files created

## Output (chat)
Return:
1) files changed
2) what changed in roadmap sequencing or status (short bullets)
3) whether SPEC / ARCHITECTURE / README / runbook / ADR changed (and why)
4) exact next prompt to run:
- usually `prompts/3-dev/00-driver-plan.md`
- if strategy questions remain unresolved, return to `prompts/7-roadmap-review/01-roadmap-review.md`