[cocolord]

Optional Turn writeback and declaration decoding pulled report construction, feedback adapters and full lease admission into paths that did not consume them. This proposal composes the existing loading repairs over target main fe36f31fd, retaining subscription validation, canonical scope spellings, digest ownership, refusal and replay behavior. It also adopts the synthetic Host UTF-8 fixture repair so the original task validator remains reachable on locale-default pipes.

中文：本次组合已有的报告构造、feedback 与声明 codec 按需加载修复，并采用合成 Host 的 UTF-8 fixture 修正。关闭态仍执行原配置校验，启用态保留 digest、来源、intent 与 replay；scope 和任务失败分类沿用原 owner。

The final diff adopts #8346 and #8365 into this existing PR. write_scope_codec.ts already isolates lexical declaration decoding from full lease admission; no additional interaction decoder is needed. The original PR ancestry is preserved. The paired RFC checkpoint retains the complete minimal-kernel acceptance gaps.

Validation at d643f2a2577f91d554540faeaa79f593230d464b	Result and boundary
Loading/digest, work requirements, lease and effect-program checks	60 passed on Node 22.22.3; selected-owner load failure rejects without fallback
Control-plane typecheck	Passed
Original complete CLI lifecycle	Four source/wheel × File/SQLite 101-Todo correctness episodes preserve the immutable fixture/artifact, scopes, original completion time, four receipts, one debit, refusal/restart/replay and two owned native exits each
Wheel ownership and resource bytes	Installed package ownership checked first; all 1,921 present tracked entries match source; seventeen source-only/doc/media omissions are unchanged
CPython 3.11 source and isolated wheel	Fourteen revalidation/UTF-8 cases passed in each distribution; original turn identity and one Host invocation retained
Real PostgreSQL 16.15	Store 391 and service 11 passed, zero skips, on disposable isolated databases; owned server stopped
Bilingual staged/head checks and public boundary	Passed; generated bundles, private state and local validation artifacts excluded
Extended affected Python suite	Running; final result will be read back before qualification
Standard exact-head premerge	Running; the maintainability ratchet currently reports a failure whose severity and scope remain to assess
New exact-head CI and review	Pending; prior component approvals do not approve this combined head

Runtime code was tested at 251d7eaeff4581d3436340f68c5b6cd8c8ebf1ad and is byte-identical at the final head; the final commit adds paired RFC evidence. All validation inputs are synthetic. Preparation failures remain recorded separately: missing generated Chat bundle, removed temporary Node path, missing isolated fixture dependency, and a PostgreSQL service run that skipped one case before its dedicated environment declaration was supplied.

Historical failures are retained: the earlier 532ecfd CI reported Frontstage HTTP 504, six Windows recovery failures and TypeScript digest/loading failures. Local composition/revalidation results do not establish that the new CI or the platform timeout is repaired. Frozen cost, attribution and bytecode campaigns were not repeated or relabeled.

This is an internal loading/refinement slice; existing report configuration journeys remain the caller surface. Future-facing refactoring applies the existing lazy compatibility pattern and lexical scope owner, with no new provider, configuration or policy owner. Full provider-first transaction, PostgreSQL host/wheel, whole-path/full marginal-cost/adoption, I3 for at least one minor release, M1/#8011, full R0/V10/R1, D2/D5/D6/D3 and context/model/split-install acceptance remain open. Exact-head review, required validation/readiness and explicit maintainer merge authorization remain required.

[loopx-agent]

Reviewer: model_agent | gpt-6.1-sol | OpenAI | runtime_reported | reasoning_effort=max

未发现阻断性问题。下列结论只资格关闭态构造隔离，不把作者的性能、wheel 或 PostgreSQL 计数作为本轮独立验证。

动机 / Motivation

运行 Turn 的用户即使关闭自动报告，旧的可选写回装配也会导入报告来源、预设和阶段构造代码。 旧路径在进入关闭态判断前加载报告构造依赖；本次将加载移到实际调用点，保持原有订阅校验、启用态结果和写回恢复。 独立冷进程探针在基线因导入报告源失败，在候选关闭态通过；14 组完整配置、hook 和警告对照一致。 范围是可选报告的构造加载隔离，不更换订阅、调度、存储或授权 owner。 完整 R0/V10/R1、安装组合、PostgreSQL host/wheel、模型采用和完整成本收益仍未验收。

改动思路 / Approach

继续让 canonical resolver 决定有效订阅，先解析 Goal override 或读取 live machine default，再判断 enabled。只有实际需要构造报告时才解析原 provider 导出。Core 的 durable writeback、原 Turn 身份与精确来源读回仍在前，可选 observer 的异常不能重做主写回或扣费。

两处 _LAZY_EXPORTS 只保留原模块别名及 patch 点；__getattr__ 缓存原 owner 对象，内部经模块属性读取，因此 patch 原公开别名仍生效。直接在函数里重导入会绕过这些已存在的调用方；移动整套报告 owner 则扩大本次边界。保留 canonical schedule 校验，避免为减少导入而跳过非法关闭配置。当前 PR 边界是两个实际装配调用方的构造隔离和兼容性，不是新的最小内核、报告配置或执行策略。

具体改动 / Changes

准确 head 532ecfd91a499bfd5d18421c1472e1a7f85bc78d，完整 PR 相对 merge base c263f7c78353fcaa914f23475d4d99d07eab7c01 为 5 文件 +323/-43：两处生产 Python +94/-43，新测试 +143，双语非规范检查点 +86。检查点没有修改原规范或历史失败，也没有降低任何阈值。

关键代码讲解

1. loopx/capabilities/periodic_report/post_writeback_hook.py:45 的 __getattr__ 延迟解析并保留原对象身份；_report_export 经模块取属性，兼容已有 monkeypatch。订阅 resolver 与 machine store 保留在实际装配路径。
2. 同文件 periodic_report_post_writeback_hooks_for_goal:96 在 enabled is True 后才取得 preset builder。14 组独立对照覆盖缺省、关闭、启用、override、非法 enabled/timezone/schedule/字段及 live default 翻转，hook、完整 warning/error 和无写入结果一致。
3. loopx/cli_commands/turn_post_writeback.py:46 的 drain_committed_turn_post_writeback_hooks 先取有效 hooks；关闭时在读取 settlement/source 前返回。启用后仍读取原 Turn 的 committed source，再交给原 dispatch owner，source/refusal/retry 保留 primary settlement。

规范依据：docs/architecture/rfcs/monorepo-distribution-split-v0.md，不可变版本 c263f7c78353fcaa914f23475d4d99d07eab7c01，并核对既有 docs/reference/protocols/periodic-report-v0.md 的 Post-writeback hook boundary。R0 — implemented 为有界装配 seam，完整计量仍 deferred；V1 — implemented 本 seam 的冷进程构造拒绝与关闭态无效果，整个 minimal/standard 闭包 deferred；V3 — implemented 本调用方的配置、启用输出及公开 CLI 恢复对照，完整命令 corpus deferred；I3 — implemented，原导出对象、wildcard 和 patch 点保持；R1 与完整 V10 — deferred，原有 owner 继续，不能由模块数量或小样本时延代替验收。

对主干的风险 / Risks

PASS：162 项相关测试，包括新增冷进程/导出测试，以及真实 File、默认 SQLite 的启用/关闭、原来源拒绝、后续状态变化和精确重放。独立同一公共 CLI harness 在 base/head 各跑 4 个开关×后端场景通过；冷 import-refusal oracle 在 base 因 todo_source 导入失败，在 head 通过并确认没有额外文件。14 组配置对照保留完整警告文本和同进程默认变更，未做语义归一化。另以同一生产装配入口验证已覆盖 Goal、同容器其他 Goal、新建 Goal、标题/顺序变化和非法配置修复；base/head 的 hook 数及完整 warning 一致。

标准 premerge 为 6 个直接检查及 14 个选择检查，无 blocking failure；双语、source 及公共边界检查通过。继承的 maintainability advisory 仍为 FAIL：当前 base/head 独立运行的完整 450 字节失败输出相同，指向未改动的 Lark 模块 metric debt；配置、oracle 与环境匹配，阈值保持。

语义与 CI 对齐

复用既有报告、订阅、source 和 dispatch 契约；导出表是局部兼容映射，不创造新的控制面词汇或授权。订阅仍按每次真实配置读取，缓存的是函数对象。已检查现有 machine/Goal 配置编辑器及 Lark request 路径，本内部加载改动没有新增前端操作。默认关闭时不增加指导、schema、必填字段、报告 sidecar、排程或外部效果；启用仍只产生未授权 generation/delivery 的原 intent。未查询或等待 CI；作者提供的历史 CI/性能观察没有升级为本轮证据。

我的整体评价 / Verdict

原 resolver、source 和 dispatcher 已拥有校验及效果；局部 lazy aliases 保留现有 patch 边界，没有新增决策 owner。 当前 PR 边界：两个实际装配调用方的构造隔离和兼容性，不是新的最小内核、报告配置或执行策略。

判断为 justified_increment。long_horizon preserved：File/SQLite 原 Turn 重放保持主写回和原来源，不因可选构造失败重复执行。user_experience preserved：既有配置编辑器和错误修复语义不变，没有增加人工准备或确认步骤。视觉检查为 not_applicable：两处 Python 装配与 RFC 记录不修改渲染呈现，已检查原有配置入口。

兼容别名服务于真实公开导入和 patch 调用方，当前直接复用既有 lazy 模式即可，无需建立新 loader 框架。失效导入、错误 warning 和默认继承均有负例。作者的完整 wheel/101-Todo/391+11 PostgreSQL 与性能实验没有在本轮重跑；没有据此声称安装采用、完整成本改善或父级验收通过。保留原后继工作和合并授权门。

English verdict: APPROVE: off-state construction isolation preserves enabled reporting and settlement semantics.