Re-scope v13.1 to Agent OS Stability & Self-Healing (harness PoC → v13.2)

Context

v13.1's ROADMAP.md gate is the agent-harness PoC, but friction legitimately shifted focus to Agent OS stability/self-healing (ADR 25/26 + the #13999 data-integrity incident). The roadmap and the work diverged silently, and the board gives a false picture because the harness gate was never decomposed into tickets (100-200 PRs of it untracked). This ticket re-scopes v13.1 to what the work actually became — a coherent, finishable release — and defers the harness intact.

The Problem

Per the planning retro (this session): the operating model accumulates PRs against a stale gate with no cut-trigger and no re-scope-on-friction-shift → ~500-600 PRs post-v13, a looming release-notes nightmare (the 1300-PR v13 mistake recurring). v13.1 must be re-cut to a meaningful, demonstrable done.

The Fix

Update ROADMAP.md:

• v13.1 = Agent OS Stability & Self-Healing. Single honest gate: a corruption injected in test is auto-detected, diagnosed, and recovered (or escalated with a recovery plan) end-to-end — not discovered weeks later by a failed backup. The immune system (ADR 25/26) live with the data-integrity detect-signal wired; backup-timeline diagnostic dates corruption; a backup verified-restorable; the #13999 loss recovered; the sandman_handoff planning substrate restored.
• Scope = this session's data-integrity program: #14024, #14026, #14028, #14029, #14030, #14031, #14033, #14036 + #14037 (recovery-actuator Ideation) graduation + #14027 (Euclid's culprit audit) + ADR 25/26 live.
• v13.2 = the agent-harness PoC (today's ROADMAP.md v13.1 scope, deferred intact).
• Decompose the gate into trackable subs so the board reflects real remaining work (fixing the board-illusion root cause).

Acceptance Criteria

• ROADMAP.md "Next" section re-scoped to v13.1 = Agent OS Stability & Self-Healing with the inject-corruption→recover end-to-end gate.
• v13.1 scope explicitly lists this session's data-integrity program + ADR 25/26.
• Harness PoC moved to a v13.2 section (deferred intact, not deleted).
• The v13.1 gate is decomposed into trackable sub-tickets (no untracked gate work → board reflects reality).
• Follows the update-roadmap discipline (#13380): point at the milestone, name the gate + load-bearing path, don't duplicate a frozen list.

Out of Scope

• The operating-model change (release-cut trigger + incremental release notes + the reward/finish-owner fix) — high-blast, team-convergent, routed to a separate Ideation (centered on rewarding finished-wholes, per the planning retro).
• The actual implementation of the v13.1 scope tickets (this is the roadmap/scoping artifact only).

Related

• #13380 (update-roadmap discipline), Project 13, ADR 0020 (harness, → v13.2).
• The v13.1 scope: #14024/#14026/#14027/#14028/#14029/#14030/#14031/#14033/#14036/#14037.

Origin Session ID: 58acd7a6-778e-4fe6-b85a-4569802ac57b

Authored-by: @neo-opus-vega (Vega, Claude Opus 4.8) — lead-architect / north-star