huangruiteng · Oct 14, 2026 · Oct 14, 2026
@@ -7,9 +7,12 @@ legacy-work-basis and reserved-value changes reached main. The production
 identical to that main; only its existing witnesses and records are added.
 The [staged scope revision](https://github.com/loopx-project/loopx/pull/4789)
 remains the acceptance boundary. **26 rows inventoried is not 26 formal producer
-proofs or tracker closure.** The source-inventory PR still needs integration
-and final owner closeout. The original three Host-ACK fixture failures have
-already been repaired on main through #6344; #6285 is not an additional merge
+proofs or tracker closure.** #6270 merged as
+`1c2542df730e51fd50c892a1236e1b7166768a7b` (2026-10-14); final owner closeout on
+one revision is still open, and the integrated readback at the end of this
+record is a candidate for it. The original three Host-ACK fixture failures were
+repaired on main through #6344; #6285 merged separately as
+`5ea7497b52f4b094ee2e4528f92bf69b934a25ee` (2026-10-13) and was never a merge
 prerequisite for those same cases.
 
 The registry still contains 26 entries, including `task_lease_lifecycle_operation`
@@ -157,13 +160,13 @@ The ordinary scenario still refuses the superseded Turn before acknowledging
 the current one. Original ACK, persisted scheduler state and byte-stable replay
 assertions pass without relaxing the Host-readback rule.
 
-[#6285](https://github.com/loopx-project/loopx/pull/6285) remains a separate open
-proposal at `f6c8aae7a7e8ba917861992a1ad21eb29477bf26`. Its current diff still adds
-shared fixture setup, extra ordinary-Turn absent/mismatched cases and explicit
-applied-RRULE readback; it is not byte-identical to main or reported as merged.
-Those remaining changes do not make the original three main failures recur.
-Do not duplicate its patch here or require another merge merely to count the
-same fixture repair twice.
+[#6285](https://github.com/loopx-project/loopx/pull/6285) merged as
+`5ea7497b52f4b094ee2e4528f92bf69b934a25ee` on 2026-10-13 after an exact-head
+approved review at `f6c8aae7a7e8ba917861992a1ad21eb29477bf26`. It adds shared
+fixture setup, extra ordinary-Turn absent/mismatched cases and explicit
+applied-RRULE readback to the same settlement CLI file. Those cases do not make
+the original three failures recur, and the same fixture repair is credited once,
+to #6344.
 
 Historical results remain tied to their original snapshots: main
 `509c38c502d3d0b4eafb01550efcdc4b5b5a1d17` had 206 passed / 3 failed in this group,
@@ -263,11 +266,26 @@ instruction” claim is obsolete. Advisory findings do not become blocking proof
 The current baseline includes #6251 typed-failure and #6268 canonical-selection
 repairs, #6260 shared consistency, #6290 legacy-work-basis repair and #6313 source
 disposition. These resolve named code/meaning gaps; they do not extend #4447's
-original closure scope. The original Host-ACK blocker is resolved in main;
-the additional source witnesses and inventory in #6270 are still proposed.
-Stage 3 and the issue remain open for that integration and final owner closeout
-on one revision with explicit passed/failed/untested evidence. A remaining
-#6285 enhancement is not a new closure condition for this tracker.
+original closure scope. The original Host-ACK blocker is resolved in main, and
+the #6270 source witnesses and inventory are integrated. Stage 3 and the issue
+remain open only for final owner closeout on one revision with explicit
+passed/failed/untested evidence; the merged #6285 cases are not a closure
+condition for this tracker.
 Installed frontend/Lark/live-model, general Goal/team qualification and blanket
 F6 proof are outside this tracker. No production provider, permission or
 persistence format changes here; raw logs and local Goal state stay private.
+
+## Integrated readback at `c185e3f0cf19419a1786c882b006eb4567ff449e` (2026-10-14)
+
+Candidate record for Stage 3, not owner acceptance. The exact selections above
+were re-run on canonical main after #6270 merged: 663 Python domain and
+monitor-recovery cases, 706 semantic/value-note cases, 448 native TypeScript
+cases and 211 critical settlement/scope/source cases passed with no skips.
+The drift smoke passes at 26 entries / 51 owner symbols with F1/F2 6/26, F3 0/26,
+F4 4/4, F5 1/1, F6 0/0 and 45 unresolved producer sites, 17 unable to provide
+evidence. Failed: the full Python suite is not green on this revision;
+`tests/control_plane/test_effect_interpreter_packet.py::test_real_executor_uses_verdict_and_replays_persisted_plan`
+fails in CI and locally with `LoopX Turn route is not host executable`, outside
+these evidence groups and outside this tracker's scope. Untested: installed
+frontend/Lark, live models and whole-tree F6. Counts are evidence boundaries,
+not a completion percentage.
@@ -4,9 +4,11 @@
 本次在结算失败、选择、旧工作基线及保留值处置合入后，更新既有 #6270 清单。
 候选的 `loopx/`、`apps/`、`packages/` 生产树与此 main 完全相同，只增加既有见证和记录。
 验收仍沿 [#4789 分阶段范围](https://github.com/loopx-project/loopx/pull/4789)。
-**26 行清单不是 26 项正式 producer 证明，也不是 tracker 关闭。** 来源清单 PR 仍需
-集成并由 owner 完成最终验收。原先三个 Host-ACK fixture 失败已由 #6344 在主干修复；
-不再把另合一次 #6285 当作这些场景通过的前提。
+**26 行清单不是 26 项正式 producer 证明，也不是 tracker 关闭。** #6270 已于
+2026-10-14 合入（`1c2542df730e51fd50c892a1236e1b7166768a7b`）；owner 对单一版本的
+最终验收仍开放，本记录末尾的集成读回是其候选。原先三个 Host-ACK fixture 失败已由
+#6344 在主干修复；#6285 于 2026-10-13 另行合入（`5ea7497b52f4b094ee2e4528f92bf69b934a25ee`），
+从来不是这些场景通过的前提。
 
 注册表仍为 26 项，已用实际 `task_lease_lifecycle_operation` 替换退休的 `lease_action`。
 F1/F2 仍是 **6/26**：五项 kernel 和 settlement-binding witness。其余二十项跨运行时
@@ -110,11 +112,11 @@ Todo-less 场景保留缺失/不匹配 manifest 的拒绝、无 scheduler 写入
 普通场景仍先拒绝过期 Turn，再确认当前 Turn。原 ACK、持久 scheduler 状态和字节
 稳定重放断言均通过，没有放宽宿主回读规则。
 
-[#6285](https://github.com/loopx-project/loopx/pull/6285) 仍是独立开放提案，当前 head 为
-`f6c8aae7a7e8ba917861992a1ad21eb29477bf26`。其剩余差异包括共享 fixture、普通 Turn
-额外缺失/不匹配反例和 applied-RRULE 显式回读；不能说它与 main 字节相同或已经合并。
-这些剩余增强不会使原三个主干失败重新成立，不在本 PR 复制其补丁，也不为了给同一
-fixture 修复重复记账而要求再合一次。
+[#6285](https://github.com/loopx-project/loopx/pull/6285) 已于 2026-10-13 在 exact-head
+`f6c8aae7a7e8ba917861992a1ad21eb29477bf26` 获批准评审后合入（`5ea7497b52f4b094ee2e4528f92bf69b934a25ee`）。
+它为同一个 settlement CLI 测试文件加入共享 fixture、普通 Turn 额外缺失/不匹配反例和
+applied-RRULE 显式回读。这些用例不会使原三个失败重新成立；同一 fixture 修复只记一次，
+归于 #6344。
 
 旧结果保留原截面：main `509c38c502d3d0b4eafb01550efcdc4b5b5a1d17` 的该组为
 206 passed / 3 failed；另一个加入当时 #6285 fixture 的隔离组合中，settlement CLI
@@ -207,8 +209,20 @@ uv run --extra test python -m pytest -q \
 
 当前基线已包含 #6251 typed-failure、#6268 canonical-selection、#6260 shared
 consistency、#6290 legacy-work-basis 及 #6313 含义处置。它们消除了具体代码/含义
-缺口，不扩大 #4447 原关闭范围。原 Host-ACK 阻塞已在主干解决；#6270 新来源见证与
-清单仍待集成。Stage 3 与 issue 为此集成及 owner 最终验收保持开放，验收须点名一个
-revision 及其 passed/failed/untested 边界；#6285 剩余增强不是本 tracker 的新关闭条件。安装前端/Lark、真实模型、完整
+缺口，不扩大 #4447 原关闭范围。原 Host-ACK 阻塞已在主干解决；#6270 来源见证与清单
+已集成。Stage 3 与 issue 仅为 owner 最终验收保持开放，验收须点名一个 revision 及其
+passed/failed/untested 边界；已合入的 #6285 用例不是本 tracker 的关闭条件。安装前端/Lark、真实模型、完整
 Goal/团队资格和通用 F6 不属本 tracker；本次不改生产 provider/权限/持久格式，日志及
 本地 Goal 状态保留在私有位置。
+
+## `c185e3f0cf19419a1786c882b006eb4567ff449e` 上的集成读回（2026-10-14）
+
+Stage 3 的候选记录，不是 owner 验收。#6270 合入后，在正式主干上按上文原选择重跑：
+领域+monitor 恢复 663 项、语义/value-note 706 项、原生 TypeScript 448 项、关键
+结算/scope/来源组 211 项全部通过，无跳过。drift smoke 通过：26 项 / 51 个 owner
+符号，F1/F2 6/26、F3 0/26、F4 4/4、F5 1/1、F6 0/0，45 个 producer 站点未解析，其中
+17 个不能提供证据。失败：同一版本的完整 Python 套件不绿，
+`tests/control_plane/test_effect_interpreter_packet.py::test_real_executor_uses_verdict_and_replays_persisted_plan`
+在 CI 与本地均以 `LoopX Turn route is not host executable` 失败，不在上述证据组内，
+也不属本 tracker 范围。未测：已安装前端/Lark、真实模型、全树 F6。计数只是证据边界，
+不是完成百分比。
@@ -1048,9 +1048,12 @@ development-time advisory; it does not close this tracker's source obligations.
 The [current registered-source inventory](ledger/semantic-vocabulary-convergence-v0/2026-10-12-registered-source-treatment.md)
 records all 26 entries, current-main evidence and compatibility boundaries.
 The owner merged both source-meaning dispositions in #6313. Main now includes
-the original Host-ACK fixture repair through #6344, verified on `60d833b13`.
-Source-inventory integration and final single-revision owner acceptance remain
-open; the remaining #6285 enhancements are separate. F1/F2 stays 6/26, with no source-domain inflation or F6-wide claim.
+the original Host-ACK fixture repair through #6344, verified on `60d833b13`,
+the #6285 settlement-chain readback cases (`5ea7497b5`, 2026-10-13) and the
+#6270 source inventory and witnesses (`1c2542df7`, 2026-10-14). Final
+single-revision owner acceptance remains open; the integrated readback at
+`c185e3f0c` in that ledger is a candidate record, not the acceptance. F1/F2
+stays 6/26, with no source-domain inflation or F6-wide claim.
 Milestone obligations and historical measurements retain their original scope/SHA.
 
 | Milestone | Shipped behavior | Entry gate | Exit evidence | Rollback |

@@ -841,9 +841,11 @@ controller 消费。Stage 1 的 composition/replay/selection/inbox 及交叠 #47
 
 [当前登记来源清单](ledger/semantic-vocabulary-convergence-v0/2026-10-12-registered-source-treatment.zh-CN.md)
 列出 26 项、当前主干上的执行证据及兼容边界。#6313 的两项含义处置已由 owner 合入；
-原 Host-ACK fixture 修复已由 #6344 进入主干，并在 `60d833b13` 重验通过；来源清单
-集成与最终单一版本 owner 验收仍开放，#6285 的剩余增强独立处理。F1/F2 保持 6/26，
-不抬高 producer 范围或声称通用 F6；历史测量保留原 SHA，下表验收义务不变。
+原 Host-ACK fixture 修复已由 #6344 进入主干，并在 `60d833b13` 重验通过；#6285 的
+结算链回读用例（`5ea7497b5`，2026-10-13）与 #6270 来源清单及见证（`1c2542df7`，
+2026-10-14）均已合入主干。最终单一版本 owner 验收仍开放；该账本中 `c185e3f0c` 的
+集成读回是候选记录，不是验收。F1/F2 保持 6/26，不抬高 producer 范围或声称通用 F6；
+历史测量保留原 SHA，下表验收义务不变。
 
 | 里程碑 | 交付行为 | 进入门 | 退出证据 | 回滚 |
 | --- | --- | --- | --- | --- |