Apply Initiative Roadmap Patch

# Off-Roadmap Initiative — Apply Accepted Roadmap Patch

You are Codex.

Goal:
Apply an accepted large-scope intake packet to repository source-of-truth docs, then stop before execution.
This step converts strategy intake into committed planning truth.

## Preconditions
- Intake packet exists at `changes/<yyyy-mm-dd>-intake-<initiative-slug>/`
- `INITIATIVE_INTAKE.md` exists
- Recommendation is `ACCEPT_NOW` or `SPLIT_AND_STAGE`
- `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) `changes/<...>/INITIATIVE_INTAKE.md`
5) `changes/<...>/ROADMAP_PATCH.md`
6) `changes/<...>/DOC_IMPACT.md`

## What to update

### A) ROADMAP is mandatory
Apply `ROADMAP_PATCH.md` into `ROADMAP.md`:
- add/modify initiative milestones exactly
- preserve roadmap format/style already used in repo
- set statuses as proposed (`[NEXT]`, `[PARKED]`, etc.)
- update sequencing/dependency notes
- do not create a new active slice pointer unless explicitly instructed

### B) SPEC / ARCHITECTURE are conditional but strict
Use `DOC_IMPACT.md`:
- if SPEC impact is marked required, update only affected sections in `SPEC.md`
- if ARCHITECTURE impact is marked required, update only affected sections in `ARCHITECTURE.md`
- if ADR is required, create `docs/adr/<yyyy-mm-dd>-<slug>.md` with:
  - context
  - decision
  - consequences
  - alternatives considered
  Keep it concise and decision-focused.

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

This step is planning truth sync only.

## Validation checklist
- [ ] `ROADMAP.md` updated and consistent
- [ ] Required `SPEC.md` updates applied (if flagged)
- [ ] Required `ARCHITECTURE.md` updates applied (if flagged)
- [ ] Required ADR created (if flagged)
- [ ] No implementation or slice execution files created

## Output (chat)
Return:
1) Files changed
2) What changed in roadmap sequencing (short bullets)
3) Whether SPEC / ARCH / ADR changed (and why)
4) Exact next prompt to run:
- usually `prompts/3-dev/00-driver-plan.md`
- if unresolved strategy blockers remain, return to `prompts/5-off-roadmap/02-large-initiative-intake.md`