docs: reconcile authority retirement and qualification cadence

[huangruiteng]

Goal And Delivered Outcome

The current shared-authority and TypeScript RFC frontiers still counted already-merged delivery as pending work. Reconcile them against ce3862e33, live caller inspection and existing canonical tasks, and define when each remaining writer, capture hook and Python facade can actually be removed.

• Related to [Roadmap]: LoopX overall delivery program / LoopX 整体路线与交付总跟踪 #4574; base: main.
• Update the bilingual overall roadmap, shared-authority RFC and TS migration RFC through one detailed bilingual retirement ledger.
• Separate whole-Goal execution/consumer closure, matched File/SQLite qualification, default/upgrade entrypoints and last-caller deletion. Historical PR-count forecasts are no longer current estimates.
• Keep PostgreSQL service qualification and deferred Goal continuity work under their existing owners. Neither blocks unrelated local retirement.

Scope And Continuation

Complete within the requested planning scope. This PR changes documentation only; it does not delete runtime code, select a release default, migrate an active Goal or claim a completed soak. No additional dead module is certified by this audit.

The ledger gives proposed engineering windows, exact deletion conditions, fault/recovery checks and stop conditions. Existing promotion/profile/projection tasks and #4931/#5106/#5130/#5139/#4915 own relevant follow-through; no duplicate implementation program is created. Preserve migration and original-receipt readers separately from obsolete normal writers.

Validation

• Tested runtime revision: ce3862e33; documentation head: 76381668e189ed070d7fb412fe2f831cadb75fca (no runtime delta).
• Run state: finished.
• Input classes: synthetic, public_fixture, authorized_private_read_only.

Check kind	Result	Public-safe evidence / limitation
static	passed	Risk-selected premerge gate passed; 19 selected checks, with the inherited advisory failure below. Eight risk-profile smokes and public-boundary check passed.
static	failed	control-plane-maintainability-ratchet-smoke.py: unchanged loopx.status reexports 119 exceed 117. Independently reproduced in a pristine worktree at ce3862e33; native premerge classifies this as advisory_inherited_failure. No threshold raised.
static	passed	Eight changed Markdown files: local links, bilingual semantic readback and git diff --check; public-boundary scan clean. Two unrelated existing registry projection warnings remain.
real_entrypoint	passed	tests/control_plane/test_authority_archive.py and test_runtime_shadow_bounded_e2e.py: 19 tests, covering CLI archive/upgrade/cutover and bounded source capture.
real_backend	passed	tests/control_plane_ts/local_authority_migration.test.ts and authority_archive_crash.test.ts: 15 tests; isolated File/SQLite, interruption and recovery. Node 22.22.3 / SQLite 3.51.3.
real_backend	passed	Detached real-source data: full JSON parity for 1,101 Todos after three synthetic source transactions were drained by the production CLI. Four resulting transactions restored/audited into SQLite; a fifth new acknowledged write survived export/restore/audit into File. Private raw evidence is not published; this is not full replay of the original history, fresh production capture or live selector cutover.
real_backend	passed	Existing SQLite rehearsal: 100/1,000 commits, cold CLI sampling and cleanup. Formal D2 report remains incomplete; this is not default qualification.
real_backend	not_run	Formal capacity/platform/ten-day soak and installed UI/Host journey qualification: named follow-through, not claims made by this docs-only PR. No soak started.

Public fixtures reproduce the suite checks; the private snapshot adds bounded evidence only and is not a public reproducer. Runtime semantics and frontend behavior are unchanged.

Frontend / Visual Evidence

UI impact: none. No documentation chrome, public first-screen or frontend source changes.

Type of Change

• Documentation update

LoopX Area

• Public docs or presentation surface (README, protocols, dashboard)

Technical Direction

Overall R3/R4/R5/R6; shared authority D1-D3; TypeScript migration T0-T4. Future-facing simplification: retire the replaced implementation with its last caller; retain explicit migration obligations instead of another compatibility writer.

Shared-authority RFC fixture impact

No fixture schema or runtime contract change. Existing File/SQLite and legacy-source suites plus a detached authorized snapshot were used to check the plan's evidence boundary. PostgreSQL three-arm routing qualification is not applicable to this documentation-only diff and is not claimed.

Boundary Checklist

• No private state, credentials, raw logs, internal links or local paths in the diff or PR.
• No duplicated benchmark work.
• Scoped to the requested RFC cadence and deletion plan.
• UI impact is none.
• Commit carries DCO sign-off.

Exact-scope quality receipt: cqr_099b46f5c9cf85cc7910, fingerprint 099b46f5c9cf85cc7910024c1dc3668a13dba302b9e39621edfa5ad54b701e49, verified valid for all eight files. Safe-fix allowed, none applied; zero blockers/warnings and one inherited-test advisory; no safe-fix pass applied. Native premerge passed, no manual holds. This does not grant merge authority.