docs: refresh weekly fork retirement evidence

[joeshull]

Downstream feature: true
Downstream rationale: keeps the fork retirement ledger auditable — refreshed baseline SHAs after the #119 sync, re-verified upstream evidence for all four waiting capabilities at code level, and recorded the sync's union resolution of the plugin markdown surface; the path is not on the governance allowlist.

Weekly maintenance of docs/fork-retirement.md. No capability status changed: all four remain waiting. Evidence refreshed against live upstream main at d1b705a0c and fork integration at f88e21fc3 (post-sync).

Changes:

• Active count unchanged (4 waiting; no upstream-candidate, no retired).
• Baseline: origin/internal/main at f88e21fc3 (the Downstream sync: merge live main into internal/main #119 sync merge), mirror/upstream at d1b705a0c; review-period merges docs: refresh weekly fork retirement evidence (2026-09-12) #118 (docs) and Downstream sync: merge live main into internal/main #119 (sync resolution) land no product capability.
• Recorded the mirror's 8-commit advance (f22a37e613 → d1b705a0c) and verified at code level that none of the upstream commits touch the four capabilities.
• Recorded how Downstream sync: merge live main into internal/main #119 resolved the Sync upstream main into internal/main #114 conflict: union of upstream fix(app): keep incomplete Markdown formatted while streaming getpaseo/paseo#4742's streaming parser with the fork's plugin extensions (streaming parser is extension-applied too), plus the @types/markdown-it ^10.0.3 → ^14.1.2 reconciliation, lockfile hoisting, and Nix-hash refresh. Capability 1 behavior unchanged.
• Capability 1: upstream candidates feat(app): provide SvgXml to plugins getpaseo/paseo#4749/feat(app): let plugins extend assistant markdown rendering getpaseo/paseo#4750/feat(app): provide MarkdownSource to plugins getpaseo/paseo#4752 still open with unchanged heads; added the precision that upstream's app-internal SvgXml imports (e.g. provider-icons.ts) are host-internal rendering, not the plugin surface; zero plugin-surface matches at d1b705a0c.
• Capability 2: added the precise upstream file path (providers/omp/agent.ts), the OmpProviderIdleScheduler detail (default 10 ms retry, no budget, no child awareness), and the re-verified interrupt path (interrupt() → terminalizeActiveWork() → subagentIndex.terminalizeRunning(...) still terminalizes running children).
• Capability 3: fix(omp): preserve described select options getpaseo/paseo#3628 head unchanged (f8e7b93da); zero optionDetails matches upstream.
• Capability 4: claude: spare background subagents from an interrupt, and let one be stopped getpaseo/paseo#4594 re-checked — server diff touches agent-manager/claude provider but agent-prompt.ts and agent-run-state.ts remain absent; fix(server): forward steerActiveTurn through wrapSessionProvider getpaseo/paseo#4633 head unchanged; upstream task_notification/admission behavior re-verified.

Verification: npm run format:check clean on the refreshed file; ledger claims re-derived from fetched refs and gh PR inspection this run (dates and heads quoted in the document). Docs-only change — no runtime behavior.

Weekly resolver report

• Active waiting capability count: 4 (plugin assistant-markdown surface; OMP task/subagent lifecycle; OMP Ask option descriptions; Claude background/autonomous subagent lifecycle).
• Status changes this run: none — all four re-verified waiting against upstream main at d1b705a0c (code-level checks, not PR titles alone); no new capability added; no capability promoted to upstream-candidate.
• Upstream replacements adopted: none — feat(app): provide SvgXml to plugins getpaseo/paseo#4749/feat(app): let plugins extend assistant markdown rendering getpaseo/paseo#4750/feat(app): provide MarkdownSource to plugins getpaseo/paseo#4752, fix(omp): preserve described select options getpaseo/paseo#3628, claude: spare background subagents from an interrupt, and let one be stopped getpaseo/paseo#4594/fix(server): forward steerActiveTurn through wrapSessionProvider getpaseo/paseo#4633 all still open with unchanged heads; fix(omp): keep parent non-idle while internal task subagents run getpaseo/paseo#3371 remains closed unmerged.
• Fork implementations removed: none.
• Sync PRs: Sync upstream main into internal/main #114 (head main → base internal/main) found CONFLICTING; no existing Downstream sync: true resolver, so Downstream sync: merge live main into internal/main #119 was created and merged (merge commit f88e21fc3, first parent from internal/main, second parent live main d1b705a0c); Sync upstream main into internal/main #114 merged automatically afterward. Conflict: packages/app/src/components/message.tsx (upstream fix(app): keep incomplete Markdown formatted while streaming getpaseo/paseo#4742 streaming parser vs fork plugin extensions) resolved as a union; semantically required @types/markdown-it/lockfile/Nix-hash reconciliation included; focused tests (127 app + 77 plugin), typecheck, lint, format green; one playwright flake (transport timeouts, two unrelated specs) passed on re-run.
• Ledger PR: this PR (Downstream feature: true); verification = format clean, evidence re-derived from fetched refs and live gh inspection.

[joeshull]

Focused governance review of 87f5f9ca7 (Downstream feature, docs-only).

Verdict: PASS. No high-risk findings. No advisory findings. Confidence 0.99.

• Diff limited to docs/fork-retirement.md; body has exactly one Downstream feature: true line, one non-empty Downstream rationale: line, no conflicting mode or upstream-provenance markers, and the ## Weekly resolver report as the final section.
• Evidence spot-checks against fetched refs: upstream d1b705a0c has zero optionDetails and zero plugin-surface SvgXml/addMarkdownExtension/MarkdownSource; upstream completeTurnAfterProviderIdle is the described state-only 10 ms loop in providers/omp/agent.ts; fork c9f842ff6/f88e21fc3 retains the optionDetails, acceptsPromptDuringAutonomousTurn, and bounded child-aware gate markers. Quoted SHAs (f88e21fc3, d1b705a0c, bbe56f99d) resolve as described.
• npm run format:check passes on the refreshed file.