docs(authority): reconcile live writer cutoff and core trial sequence

[loopx-agent]

The retirement plan still named the former Todo re-export as the mutation owner and described the implemented cold-source importer as missing. That can send follow-up work back to completed prerequisites.

Reconcile the existing RFC and provider reference against the current source. Name six live caller families and their retained recovery obligations; keep one cohesive 2.0 normal-writer cutoff followed by producer cleanup. Insert the requested reversible core-developer SQLite trial between import qualification and the breaking cutoff. Compatible 1.x import/deprecation, existing canonical File selection, original receipts, complete backup qualification and frozen D2 evidence remain distinct.

Documentation only: no runtime default, authority gate, active Goal conversion or release activation changes. Validation covers the live source inventory (five mutation dispatches), 80 local links/anchors, semantic advisory/full-tree smoke, public-boundary scan and exact-scope change-quality qualification. Native premerge results and exact-head review follow below. An initial link-check harness rejected an existing directory target; the corrected check preserves all fragment checks. Initial quality recording rejected out-of-scope evidence references; corrected references bind the exact two-document diff. No code or qualification threshold changed to resolve those validation errors.

[loopx-agent]

Reviewer: model_agent; model=gpt-6.1-sol; provider=OpenAI; runtime_reported; reasoning_effort=xhigh
Approval conclusion (author-owned PR; GitHub blocks formal self-approval)
Exact head: c5164043aa06ef1e520547801baaaaa24a07b63d

动机

维护迁移与退役计划的开发者会遇到这个问题。按旧说明推进时，已实现的旧源导入仍被称为缺少实现，已退出的 Todo 转发层仍被列为写入 owner；这会把下一批工作导回完成的前置步骤。新说明按当前源码列出真正仍在写旧源的六类入口，并把核心开发者的可逆 SQLite 试用放在导入验收与不兼容删除之间。本批只更新已有文档，不改变当前默认、执行准入、旧 Goal、数据库或发布状态。实际安装采用、完整 Goal 备份、自然试用、旧 writer 删除及正式 D2/发布资格仍分别开放。

改动思路

复用现有迁移 RFC、provider reference 和可逆试用操作说明。先读不可变基线，再按真实 source caller 核实归属；没有增加另一份路线图、迁移器或 runtime gate。最强反对理由是现有文档已有大部分顺序，再追加计划可能只增加维护负担。本次替换了“导入未实现”和旧 façade 归属，把容易漏掉的 batch/Monitor/ownership/capture 合到同一个删除包，而非为五个 fallback 各提一项工作；核心试用直接链接已有操作说明。

相关 future-facing pass 是明确同族一次截止与之后的 producer cleanup。较大的 runtime 删除留在原实现阶段，当前不从静态引用或测试成功推导安全删除。

具体改动

关键内容讲解

• docs/reference/local-authority-provider-selection.md：两行旧归属更新到实际 mutation、batch、Monitor 及 retained capture/history/readback owner；英文和中文都纠正导入“缺实现”的描述，保留安装、完整备份与历史源支持的证据缺口。六族表逐项保留 validators、原回执、current-head rollback、未释放 lease 与 active binding/outbox 义务。交付顺序从三包改为四阶段，插入已有的小范围试用，保持兼容 1.x 与 2.0 cutoff 提案的界限。
• docs/architecture/rfcs/typescript-control-plane-migration-v0.md：将 current frontier 固定在 38cb407edc39752d3ad6b4d414ca5c5255aba177，并把同一入口清单、试用、完整 writer 截止和后续 producer 退役沉淀到原 T4 checkpoint。

独立评审依据为 docs/reference/local-authority-provider-selection.md @ 38cb407edc39752d3ad6b4d414ca5c5255aba177，判断的是修改前已接受的边界，而非用新文字自证：

• Retirement boundaries before changing the release default：implemented，本批准确归属现有调用族并保留历史恢复；真正删除 deferred 到同一 T4 实现包。
• Proposed compatibility cutoff and release sequence：implemented，保留 1.x additive import、2.0 不兼容提案、正常 mutation 前 canonical、既有 File provider、原操作恢复和当前 head 回退；没有宣布这些尚未执行的阶段已通过。
• Reversible developer trial / 可逆开发者试用：引用已有 docs/reference/sqlite-authority-store.md 同基线的试用 owner。implemented 是插入顺序与复用操作说明；真实自然 cohort 观察仍 deferred，未邀请开发者或改动 live Goal。

对主干的风险

无阻塞 finding。主要风险是把“准备退役”读成“已删除”或把协调源备份证据读成完整 Goal 备份。本次表格明确仍有真实调用，阶段仍是提案，并保留 cold import/原 receipt/active binding/过期未释放 lease 的各自恢复义务。六族源码直接核对包含五处 legacy mutation dispatch，claim 走 update；没有仅依据旧文档或库文件存在下结论。

验证：80 个本地链接/anchor、全树 semantic smoke、advisory、公开边界与 diff 检查通过；最终原生 premerge 为 3 direct + 9 catalog + 8 risk + 1 boundary，全部通过，CQR cqr_bc84f751ad38992a7410。初始链接探针错误拒绝既有目录链接；纠正检查器后保留 fragment 校验。初始 CQR 引用未改变源码路径而被拒；改为精确两文件证据引用。初次 premerge 的 strict receipt stale 保留，最终 committed diff 重新资格化并执行完整 gate 后通过，未豁免检查。CI 按 policy 未读取。

这不是新 runtime/打包使用资格，未重跑数据库或 natural soak；没有 UI 首屏变化。当前环境实际安装来源与整个历史支持矩阵仍是后续验收，正式 D2 原失败/缺失没有重分类。

我的整体评价

这是可独立审查、可直接回退的文档校准增量。long_horizon 和 user_experience 在当前运行时保持：没有增加正常操作步骤或人工许可；后续工作不再依据“导入代码缺失”空等，并复用已存在的试用操作路径。只改两个现有文档，75 增/14 删；runtime、协议、配置和语义 vocabulary 均未变。批准这个精确 head 的文档提案，不宣称全 T4、删除实现或发布完成，也不授予 merge/迁移/消息发送权限。

English verdict: APPROVE - c5164043aa06ef1e520547801baaaaa24a07b63d. Reconciles live writer ownership and the existing import/trial/major-cutoff sequence without changing runtime defaults or declaring qualification; source inventory, 80 local links, semantic checks and exact-scope native premerge passed.