Trim ROADMAP.md to next-release-only (relocate history → release notes, vision → VISION.md)

Context

@tobiu flagged (2026-06-16) that ROADMAP.md carries a lot of historical + vision artifacts. The principle: the roadmap holds only the coming-next item (short-term). The vision lives in .github/VISION.md; shipped history lives in resources/content/release-notes/. Diagnosis this session (V-B-A'd against origin/dev:ROADMAP.md): 5 of 8 sections are vision-or-history.

The Problem

ROADMAP.md headers today: ## Vision · ## Shipped: v13 · ## Current Focus: Agent Harness · ## Agent OS Foundation (+ ### v12.1 Baseline + ### Shipped since v12.1 — 332 tickets) · ## Longer Horizon. Only Current Focus is genuinely next/short-term. The rest is vision-restatement + shipped-history that already has homes elsewhere — so the roadmap reads as an archive, burying the one thing a reader needs (what's next).

The Architectural Reality

Relocation homes exist (the trim moves, it does not delete): .github/VISION.md (the institution vision); the chunked release notes at resources/content/release-notes/ (the shipped-v13 detail lives at the _index.json-mapped chunk-2/v13.0.0.md). Steward of the ROADMAP slice per the update-roadmap skill (#13380) model: @neo-opus-vega.

The Fix

Reshape ROADMAP.md to next-only:

• KEEP: ## Current Focus (the live next-release thesis + cornerstones + deferred set + stewards) + the pending ## Next: v13.1 section (#13391).
• REPLACE with 1-line pointers: ## Vision → .github/VISION.md; ## Shipped: v13 + ## Agent OS Foundation + ### v12.1 Baseline + ### Shipped since v12.1 + ## Longer Horizon → resources/content/release-notes/ (the detail already lives in the release notes; relocate any unique foundation/vision prose to VISION.md before deleting inline — lose nothing).

Decision Record impact

aligned-with the roadmap = cornerstones-not-archive model (the update-roadmap skill #13380). No ADR.

Acceptance Criteria

• ROADMAP.md = the next-release scope only (Current Focus / next milestone) + a 1-line .github/VISION.md pointer + a 1-line resources/content/release-notes/ pointer.
• No shipped-history detail or vision-restatement remains inline — and a pre-delete check confirms each relocated block already exists in VISION.md / the release notes (nothing lost).
• Cross-family review + @neo-opus-vega (ROADMAP steward) sign-off.

Out of Scope

• The durable skill rule that PREVENTS re-accumulation — that's the sibling ticket (update-roadmap skill fix).
• #13391's v13.1-section add — this trims around it; sequence after #13391 merges, or rebase to include it so the v13.1 section is preserved.

Related

Steward: @neo-opus-vega (ROADMAP slice). Sibling: the update-roadmap skill-fix ticket (filed alongside this). Complements #13391 (v13.1 section add). Skill: #13380.

Release classification: substrate/docs (NOT v13-release-blocking) → boardless.

Contract Ledger

(Backfilled 2026-06-17 per @neo-gpt's intake-gate — the public ROADMAP.md surface needs its authority-keying explicit before the implementing PR #13447 closes this ticket.)

Evolution

• 2026-06-17 (scope): beyond the original trim, this ticket now also reframes the next-release section to the v13.1 cockpit end-goal per @tobiu's directive ("the v13.1 end goal + scope into the roadmap"). Grounded in ADR 0020 + the #13436 cockpit UX/IA convergence + the keeper/proof correction. Delivered in PR #13447.
• 2026-06-17 (intake): Contract Ledger backfilled (above) per @neo-gpt's needs-contract-alignment halt; the v13.0.0 release-note link corrected to the chunk-2/ path (the flat path the prior ROADMAP carried does not exist).

Origin Session ID: c5cc7e13-6f5d-4090-908c-c8dfa496163a