@thincoder/core 0.10.13 → 0.11.1

package/CHANGELOG.md

@@ -3,6 +3,35 @@
 All notable changes to the core package are documented here.
 Format: Keep a Changelog · 中文 · 号在发布时定（CalVer——见 `docs/RELEASE.md` §4）。
 
+## [0.11.1] — 2026-11-04
+
+### Added
+
+- **`ssh` 文件传输**：工具新增 `put` / `get` 两动作（单文件、二进制安全）——执行体 = 系统 `scp`，缺省 `-O`（经典协议，网络设备普遍只实现这一支），`protocol:"sftp"` 可覆盖；硬超时杀树；`get` 半截档按「字节数或 mtime 变过」才删，未被动过的旧档不删。
+- **写门射程扩到十三把**：`ssh` 入入口集，但**只 `get` 要号**（`put` 写远端，本门不判）；`touchedPaths` 钩子回绝对形，`~` 落点不再被判成「项目内虚构路径」。
+- **项目标准档声明口 `docRoot.standards`**：评审的「方法论符合度」维度不再是空跑。
+- **`path-resolve.mjs`** ∥ **`tools/process-doc-mark.mjs`** ∥ **`persona-tester.md`**（tester 角色人格）。
+- **SSE 首 chunk 与流中途分窗**：长 prefill 不再被 120s 静默超时误杀。
+- **`x-opencode-session` 改为每会话一个**（值位模板 `${sessionId}`）。
+- **`ledger/count` 跨项目读面**：界改用调用方 `cwd`。
+
+### Changed
+
+- **派单动作表 = 四列**（动作 / 落点 / 期望 / **原因**）——原因格写依据（设计判据 / 实测 / 裁定），不是「不改会怎样」；写门教学块射程行同步补 `ssh` 并写明两半。
+- **台账契约五面收到同一句上**：回执分流 ∥ 待核销拒文 ∥ 逐边枚举 ∥ §5 门判据 ∥ 六态迁移表。
+- **一本批档一并发**；打回即重置 §3 状态行。
+- **提示词面**：单测档住哪 ∥ 先例必须在盘 ∥ 无一越档。
+
+### Fixed
+
+- **doc-check 围栏闭合判定加长度**：嵌套围栏不再把代码行并成段落落。
+- **`ssh` 有状态剥离 ＋ 帽窗**：保头保尾、中段可取回。
+- **`ledger` evidence 读数**从「尺寸超标」改成「太长、读不下去」。
+
+### Removed
+
+- **轻通道退役**：`agent/light-round.mjs` ∥ `agent/live-batch.mjs` ∥ `agent/unbooked-pen.mjs` ∥ `scripts/api-contract.mjs` 及其文档三档。
+
 ## [0.10.13] — 2026-10-26
 
 ### Added

package/advisor/messages.mjs

@@ -54,6 +54,7 @@ export function buildDesignApprovalBlock(designToken, designId) {
     "## Approval Signal",
     echo,
     "The verdict line is checked mechanically: without a `VERDICT: pass` line, or with a `VERDICT: changes-required` line, no token is issued even when the token is echoed.",
+    "Put that same verdict line on its own line inside the text you append to the batch record's §3 (`batch append`): the §3 write itself is checked the same way, and a §3 append that states no verdict — or states both — is refused before anything lands.",
     "🟡 (Advisory) and 🔵 (Note) findings do NOT block approval — list them if present, but still include the token. If any 🔴 (Critical) issue remains unresolved, do NOT include the token. A reasoned non-fix accepted by the reviewer does not block (🔴 only — 🟡/🔵 never block approval); anything else stays unresolved.",
   ].join("\n")
 }
@@ -155,8 +156,9 @@ function buildAdvisorUserMessageInner(agent, prior, reviewType, designToken = nu
       }
     }
 
-    // Engineering mode: the project standards section — the declaration face is gone with the
-    // manifest `advisor` key, so this is always an explicit degradation (PO-2).
+    // Engineering mode: the project standards section — read from the project's own
+    // declaration (`docRoot.standards`); three states, each machine-distinguishable:
+    // undeclared / declared-but-unreadable / injected. Never a probed convention name (PO-2).
     if (agent.config?.agent?.engineering) {
       injectProjectStandards(agent, parts, guideRoot)
     }

package/advisor/notice.mjs

@@ -78,7 +78,7 @@ export function buildTypeGateRefusal({ criterion, received = null, declared = nu
   }
   parts.push(
     '  • type="code"   — code review: reviews the code you changed; pass paths=[...] to scope files/directories (documents=[...] adds acceptance-criteria context).',
-    '  • type="design" — design review: reviews design / requirement documents; pass documents=[...] (the explicit list) — plus batchDoc when a batch record is in flight.',
+    '  • type="design" — design review: reviews design / requirement documents; pass documents=[...] (the explicit list) and batchDoc — required, the batch record this review belongs to.',
     "Nothing was sent: no review instance, no round consumed, no design token minted, no LLM call.",
   )
   return parts.join("\n")

package/advisor/project-context.mjs

@@ -13,13 +13,15 @@
  * dimension it could no longer check (silent failure, the worst class: invisible
  * and unfixable by the user). Missing pieces now say so, and the reviewer is told
  * to state the limitation in its findings. The document map is derived from the
- * manifest's `docRoot` (the one place that says where the docs live); the standards
- * face has no derivable convention name and is therefore an explicit degradation.
+ * manifest's `docRoot` (the one place that says where the docs live); the standards face
+ * is the project's OWN declaration too (`docRoot.standards`) — the probe was retired, the
+ * declaration replaced guessing — and it degrades in three machine-distinguishable states:
+ * undeclared (no path), declared but unreadable (the declared path is named), and injected.
  */
 import { readFileSync, existsSync } from "node:fs"
 import { resolve, join, relative, dirname, sep } from "node:path"
 import { providerSpec } from "../config.mjs"
-import { DEFAULT_MANIFEST, docRootPaths, readManifest } from "../manifest.mjs"
+import { DEFAULT_MANIFEST, docRootPaths, manifestFilePath, readManifest } from "../manifest.mjs"
 
 /** Project guide (AGENTS.md) injection budget — decision 2026-08-08:
  *  NO fixed truncation; long-context models (1M+) get up to 5% of their context
@@ -37,6 +39,29 @@ export const NO_DOC_MAP_NOTICE = "(No document map found — no README.md under
 export const NO_STANDARDS_NOTICE = "(No project standards document — nothing in the project declares one — judge methodology compliance from the Project Guide (when present) and the review criteria above; state the limitation in your findings.)"
 export const NO_GIT_NOTICE = "(No git repository detected — change-set context is unavailable; read the review-scope files directly.)"
 
+/**
+ * 态 2 —— 声明了标准档，但一份都读不到（文案单源 = `docs/core/design/MANIFEST.md` §2.12）。
+ * 与 `NO_STANDARDS_NOTICE` **不得同形**：那句说的是「没有任何东西声明」，而这里恰好是「声明了但
+ * 读不到」。同形会让作者以为自己没声明过，回头去补一个其实已经有的声明——所以本句必带声明路径；
+ * `reason` 两因分列（`no such file` 修路径 ∥ `read failed: <code>` 修权限）。
+ * @param {{path: string, reason: string}} p — 声明路径（绝对形）+ 读不到的原因
+ * @returns {string}
+ */
+export const STANDARDS_UNREADABLE_NOTICE = ({ path, reason }) =>
+  `(Project standards declared at ${path} in the manifest, but unreadable — ${reason};\n` +
+  "the methodology-compliance criterion is unchecked.\n" +
+  "Fix the path or the file — do NOT declare it again. State the limitation in your findings.)"
+
+/**
+ * 半读句 —— 多份声明里有几份读不到（态 3 的下半；KD-M1-61 拒掉「只注入首份」：其余既不注入也不报
+ * = 静默丢声明，与需求档 §5.1 验收 ③「任何一面都不得静默跳过」相抵）。
+ * @param {{unreadable: string[]}} p — 逐份 `"<路径>: <原因>"`（路径绝对形）
+ * @returns {string}
+ */
+export const STANDARDS_PARTIAL_NOTICE = ({ unreadable }) =>
+  `(Of the standards declared in the manifest, these could not be read — ${unreadable.join("; ")};\n` +
+  "the standard set above is INCOMPLETE. Fix them — do NOT declare them again. State the limitation in your findings.)"
+
 /**
  * Discover the project root for the review — user decision 2026-08-08:
  * the project root is a SUBDIRECTORY of the working directory, never an
@@ -207,16 +232,101 @@ export function injectDocumentMap(agent, parts, root) {
   return mapPath
 }
 
+/** 消息里的路径书写（\ → /）：与 `injectProjectGuide` 的根注记同款（`relative(...).split(sep).join("/")`），
+ *  且让「声明路径字面」在消息里可 grep（`docs/nope` 而非 `docs\nope`）。读盘仍用原样路径。 */
+const displayPath = (p) => String(p).replaceAll("\\", "/")
+
 /**
- * Inject the project standards section (PO-2). The declaration face is gone with the manifest
- * `advisor` key, and no standards file name is derivable from what the project does declare (the old
- * `METHODOLOGY.md` probe was deleted exactly because most projects have none). The section stays so the
- * reviewer is TOLD the dimension is unchecked — visible degradation, not a silent skip.
- * @returns {null} always degraded
+ * Inject the project standards section (PO-2 · 判据 ∥ 文案单源 = `docs/core/design/MANIFEST.md` §2.12).
+ *
+ * 三态（**可机判互异**，本面立身之本 = 用声明、不猜固定名）：
+ *   态 1 未声明 —— `docRoot.standards` 缺键 / `null` / 一个路径都没得来 ⇒ `NO_STANDARDS_NOTICE`
+ *        （零路径字面、零 `declared`）。
+ *   态 2 声明了但读不到 —— 声明了路径、逐份都不可读 ⇒ `STANDARDS_UNREADABLE_NOTICE`（点名**声明了
+ *        的绝对路径** + 原因）。绝不与态 1 同形。
+ *   态 3 读到 —— 正文注入（多份 = 按声明序拼接）；部分读不到时正文在前、半读句点名不可读的逐份。
+ *
+ * 取值源 = `read.ok && read.manifest ? read.manifest : DEFAULT_MANIFEST`（同 `declaredDocRoots` 先例，
+ * 不另立第二套判定）⇒ 整档缺失 / 非法一律 `std === null` ⇒ 态 1；`paths.length === 0 ⇒ 态 1` 是硬不
+ * 变量——态 2 句永不含 `undefined` 路径。数据档本身读抛（非 ENOENT）收为态 2 族，不中断消息组装。
+ *
+ * @param {Object} agent — the parent agent（`cwd` / provider 取上下文窗口）
+ * @param {string[]} parts — message parts (mutated)
+ * @param {string|null} [root] — project root from the guide walk（`null` ⇒ `agent.cwd`；与
+ *   `injectDocumentMap` 同一 base）
+ * @returns {string|string[]|null} 注入的标准档绝对路径（单份 = 串，多份 = 数组）；降级 ⇒ null
  */
-export function injectProjectStandards(_agent, parts, _root) {
+export function injectProjectStandards(agent, parts, root) {
   parts.push("## Project Standards")
-  parts.push(NO_STANDARDS_NOTICE) // degraded — visible by contract
+  const base = root ?? agent.cwd
+
+  // 数据档本身读抛（权限 / 目录等——`readManifest` fail-closed 上抛）：收为态 2 族，不冒 `undefined`。
+  let read
+  try {
+    read = readManifest(base)
+  } catch (e) {
+    parts.push(STANDARDS_UNREADABLE_NOTICE({ path: displayPath(manifestFilePath(base)), reason: `manifest read failed: ${e?.code ?? "unknown"}` }))
+    parts.push("")
+    return null
+  }
+
+  const std = (read.ok && read.manifest ? read.manifest : DEFAULT_MANIFEST).docRoot.standards
+  // 态 1（两入口）：未声明（缺键 / null / undefined）∥ 声明了但一个合法路径都没得来。
+  // 后者是硬不变量：宁可判「未声明」，也绝不发一句带 `undefined` 的「declared at …」。
+  const paths = std == null ? [] : docRootPaths(std, base)
+  if (paths.length === 0) {
+    parts.push(NO_STANDARDS_NOTICE) // degraded — visible by contract
+    parts.push("")
+    return null
+  }
+
+  const readable = []
+  const unreadable = []
+  for (const p of paths) {
+    if (!existsSync(p)) { unreadable.push({ path: p, reason: "no such file" }); continue }
+    try {
+      readable.push({ path: p, text: readFileSync(p, "utf8") })
+    } catch (e) {
+      unreadable.push({ path: p, reason: `read failed: ${e?.code ?? "unknown"}` })
+    }
+  }
+  // 态 2：声明了，一份都读不到。
+  if (readable.length === 0) {
+    parts.push(STANDARDS_UNREADABLE_NOTICE({ path: displayPath(unreadable[0].path), reason: unreadable[0].reason }))
+    parts.push("")
+    return null
+  }
+
+  // 态 3：正文（多份 = 按声明序拼接，共用一次注入的同一预算——一次评审注入就是一个预算单位）。
+  parts.push("The file below is the project's standards document. Judge methodology compliance against it.")
   parts.push("")
-  return null
+  const body = readable.map((r) => r.text).join("\n\n")
+  // 预算算式复用同两条常量、**逐注入独立计算**（不与指南共享池——两面语义不同，不该互相记账）。
+  // providerSpec 取值在 body 之外算：上下文规格查不到也不得伪装成「没有标准档」。
+  const resolvedProvider = agent.provider ?? agent._provider
+  const ctx = providerSpec(resolvedProvider).context
+  const cap = Math.max(PROJECT_GUIDE_MIN, Math.floor(ctx * PROJECT_GUIDE_FRACTION))
+  let shown = body
+  // 计量与切片**同一单位**（码点）：两条口径混用会让含星平面字符（emoji / 生僻字）的标准档在
+  // 「其实全给了」时也报 PARTIAL、并给出 truncated at N of M 的假读数（M 是 UTF-16 长度）。
+  const chars = [...body]
+  if (chars.length > cap) {
+    // 被截断的那一份（拼接期已有逐份偏移；偏移同以码点计）——恢复指针必须指向它，否则评审拿着残缺规矩判。
+    let offset = 0
+    let cut = readable[readable.length - 1].path
+    for (const r of readable) {
+      const len = [...r.text].length
+      if (cap < offset + len) { cut = r.path; break }
+      offset += len + 2 // +2 = 拼接分隔符 "\n\n"
+    }
+    // 截断的风险不在大小，在**静默**：指南截断丢的是指针，标准档截断丢的是判据本身。
+    shown = chars.slice(0, cap).join("") + `\n\n…(truncated at ${cap} of ${chars.length} chars — the standard set is PARTIAL;\nread the full file — ${displayPath(cut)} — for the rest)`
+  }
+  parts.push(shown)
+  // 半读句：正文在前，缺口逐份点名（零静默——KD-M1-61）。
+  if (unreadable.length > 0) {
+    parts.push(STANDARDS_PARTIAL_NOTICE({ unreadable: unreadable.map((u) => `${displayPath(u.path)}: ${u.reason}`) }))
+  }
+  parts.push("")
+  return readable.length === 1 ? readable[0].path : readable.map((r) => r.path)
 }

package/agent/completion.mjs

@@ -15,6 +15,18 @@ const MAX_VERIFY_RETRIES = 3
 const MAX_ADVISOR_PUSHBACKS = 3
 const MAX_EMPTY_RETRIES = 2
 
+/**
+ * 响应「有实质」判据（单源——判空面与清零面读同一份；AGENT-LOOP.md §6.5① · D-AL28）：有非空正文
+ * **或** 有工具调用 ⇒ 实质，两种形都证明「刚才那次空是瞬时的」。此处也是唯一判空式，不另写
+ * `.trim() === ""`——两份一漂，判空与清零就不再是同一件事（判空加宽、清零面漏跟）。
+ * 「或」不是「且」：带工具调用但正文为空（提供端常见形态）必须判为实质——写成「且」，工具轮就不清零，
+ * 空计数跨轮累计，「中间成功过却照样抛」原样留存。
+ * @param {object} response - chat response with .content, .toolCalls（同下方 handleCompletion 的既有契约）
+ */
+export function isSubstantiveResponse(response) {
+  return String(response.content ?? "").trim() !== "" || response.toolCalls.length > 0
+}
+
 /**
  * Handle a model turn with zero tool calls. May push back (verify/advisor/pending tasks)
  * or accept the completion.
@@ -29,7 +41,7 @@ const MAX_EMPTY_RETRIES = 2
  * @param {object} callbacks - { onTurnEnd, onSubTurnBreak }
  */
 export function handleCompletion(agent, response, depth, turn, guardPushbacks, honestReminderInjected, advisorPushbacks, callbacks) {
-  if (String(response.content ?? "").trim() === "") {
+  if (!isSubstantiveResponse(response)) {
     // Transient empty response (reasoning exhausted / output truncated): instead of
     // aborting the whole turn, inject a reminder and let the model respond again.
     // Bounded — after MAX_EMPTY_RETRIES consecutive empties, surface the original error.

package/agent/digest-account.mjs

@@ -1,49 +1,51 @@
 /**
  * agent/digest-account.mjs — 消化账务单件（AGENT-LOOP-ASYNC-POOL.md §6.31 · 批 digest-accounting ·
- * 台账 #930）：投递 ≠ 销账——报告不许无声消失。
+ * 台账 #930；批 digest-retry-amplify · 台账 #1850：投递恒一次）：投递 ≠ 销账——报告不许无声消失。
  *
- * 三角色（§6.31.2）：**投递**（注入但留容器）∥ **见账**（消化轮收尾逐条机检账目覆盖）∥
- * **销账**（覆盖才离容器 + 释放 report）。本档承载：常量（`DA_RETRY_LIMIT`）/ 回合分类
- * （`isDigestRound`）/ 投递门控（`shouldDeliverEntry`）/ 账目合同（`coversDigestId` 解析 ∥
- * `digestAccountRequirement` 要求行）/ 见账 pass（`accountDigestRound`——销账 ∥ 重投标记 ∥
- * 升级）/ 读面（`unsettledRows` · `unsettledRow` · `unsettledCount`）/ 落痕清位 ∕ 取件助手
- * （`armAccountRound` · `harvestAccountOutput`）。
+ * 三角色（§6.31.2）：**投递**（注入但留容器——每条恒一次）/ **见账**（消化轮收尾逐条机检账目覆盖）/
+ * **销账**（覆盖才离容器 + 释放 report；未覆盖计一个未签收轮，达 `DA_MISS_LIMIT` ⇒ 升级）。本档承载：
+ * 常量（`DA_MISS_LIMIT`）/ 回合分类（`isDigestRound`）/ 投递门控（`shouldDeliverEntry`）/ 账目合同
+ * （`coversDigestId` 解析 ∥ `digestAccountRequirement` 要求行）/ 见账 pass（`accountDigestRound`——
+ * 销账 ∥ 未签收轮 ∥ 升级四步含终局披露）/ 读面（`unsettledRows` · `unsettledRow` · `unsettledCount`）/
+ * 落痕清位 ∕ 取件助手（`armAccountRound` · `harvestAccountOutput`）。
  *
  * 载体（§6.31.2）：`_daSession`（会话标记——挂起会话置 / 复位，`agent/suspension.mjs`）与
  * `_unsettledDigests`（升级账本——经 `async-settle.mjs` 写助手）；账目态挂条目字段
- * （`_daDelivered` / `_daRetry` / `_daFailures`）。**fallback 面**（无 `_daSession`——headless /
- * 直连 `runAgent`）零账目动作（不销账 / 不重投 / 不升级）：缺省条逐字沿用取尽语义（先离容后注入）；
+ * （`_daDelivered` / `_daMissRounds`）。**fallback 面**（无 `_daSession`——headless /
+ * 直连 `runAgent`）零账目动作（不销账 / 不计未签收轮 / 不升级）：缺省条逐字沿用取尽语义（先离容后注入）；
  * 已投递未销账条同判据跳过且留容器（§6.31 出口缝② · 父侧裁定 2026-10-05）。
  *
  * 边界（§6.31.12）：不做处理质量机检（只保「不许无声」）；升级账本无 TTL（会话期面——
  * 中止清、idle 存续）。
  */
-import { logEvent } from "../log.mjs"
+import { logEvent, errText } from "../log.mjs"
 import { pushReal } from "../context.mjs"
 import { carrierField, releaseSettledEntry, appendUnsettledDigest } from "../agent-tools/async-settle.mjs"
 import { DIGEST_ACCOUNT_DOMAIN } from "./helpers.mjs"
 
-/** 同条重投上限（§6.31.5 KD-DA4）：重投 ≤ DA_RETRY_LIMIT ⇒ 总投递 ≤ 3 次；超限 ⇒ 升级。 */
-export const DA_RETRY_LIMIT = 2
+/** 同条未签收上限（§6.31.5 KD-DA11）：积满 DA_MISS_LIMIT 个未签收消化轮 ⇒ 升级（离容器 + 账本 + 提醒 + 终局披露一次）。
+ *  依据 = 「连空 3 轮仍须在容器、第 4 轮补签仍能销账」的**下界**（N = 4——无额外余量；可复算；不取观测值——
+ *  修前观测受「总投递 ≤3」删失）。 */
+export const DA_MISS_LIMIT = 4
 
 /**
  * 回合分类单点（§6.31.2）：账目只属**消化轮**（autoTurn ∧ 非上行唤醒轮 ∧ 非 timer 轮）——
- * timer / 上行轮投递不销账、不重投（其账目在后续消化轮）。
+ * timer / 上行轮投递不销账（其账目在后续消化轮）。
  */
 export function isDigestRound(opts) {
   return opts?.autoTurn === true && opts?.upstreamTurn !== true && opts?.timerTurn !== true
 }
 
 /**
- * 投递门控（§6.31.4 单点谓词；批 async-delivery-formalize 2026-10-12 · §6.34 收窄）：
- * - `!_daDelivered` ∧ 本回合 = 系统轮（`autoTurn`）⇒ 投（首次投递——**用户回合零投递**）；
- * - `_daRetry` ∧ 本回合 = 消化轮 ⇒ 投（重投经消化轮回路）；
- * - 其余 ⇒ 跳过（防重复注入）。
+ * 投递门控（§6.31.4 单点谓词 · 批 digest-retry-amplify 收为单门）：`!_daDelivered` ∧ 本回合 = 系统轮
+ * （`autoTurn`）⇒ 投（首次投递——**用户回合零投递**）；`_daDelivered` 已置 ⇒ 恒跳过（**每条只投一次**——
+ * 重投回路退场，§6.31.5 KD-DA4）。注入抛错 ⇒ `_daDelivered` 未置 ⇒ 下一系统轮重试注入
+ * （注入失败的再试，不属投递回路）。
  * 注：`autoTurn` 判据由调用方（`run-start.mjs` 会话态支）传入；回退面（非会话态支）不经本谓词。
  */
-export function shouldDeliverEntry(entry, digestRound, autoTurn) {
-  if (entry?._daDelivered !== true) return autoTurn === true
-  return entry._daRetry === true && digestRound === true
+export function shouldDeliverEntry(entry, autoTurn) {
+  if (entry?._daDelivered === true) return false
+  return autoTurn === true
 }
 
 /** 账目要求行（§6.31.3）：核常量（helpers.mjs）+ 未销账 id 清单动态拼（`<ids>` 占位替换）。 */
@@ -77,70 +79,94 @@ export function coversDigestId(output, id) {
  * 见账 pass（§6.31.5——消化轮收尾 `finalizeAgentTurn` 单点调用；调用方已判 `isDigestRound ∧
  * `_daSession` ∧ 非会话停止径）：
  * - 投递账 = pending ∩ `_daDelivered`；覆盖 ⇒ 离容器（splice）+ `releaseSettledEntry`（含 report 释放）；
- * - 未覆盖 ⇒ `_daFailures += 1`；≤ `DA_RETRY_LIMIT` ⇒ `_daRetry = true`（下轮重投）；超限 ⇒ **升级**
- *   （离容器 + 入 `_unsettledDigests` + 恰一条提醒（pushReal）+ 恰一条 `ev:unsettled`）。
- * 缺痕（output == null——抛错 / 撞帽 / 未收口）⇒ 全条未覆盖（安全方向——假阴可重投；假阳是事故本相）。
+ * - 未覆盖（空回合 ∥ 有输出未签收——同判同计）⇒ `_daMissRounds += 1`；< `DA_MISS_LIMIT` ⇒ 条留容器、
+ *   **零投递动作**；达上限 ⇒ **升级**（四步固定先后：账本 → 提醒 → 离容器 → 终局披露）。
+ * 缺痕（output == null——抛错 / 撞帽 / 未收口 / 整 run 零非空正文）⇒ 按未签收判（与「有输出未签收」同出口）。
+ *
+ * async（§6.31.5 升级支 ④）：披露复用首投注入器 ⇒ pass 变 async——唯一调用点 = `run-stages.mjs` 的
+ * finalize 单点（已 await）。披露逐条 try/catch：判据 = **披露失败不得使报告离开可见面**
+ * （账本 + 提醒 + status 面 `preview` 已在披露之前落定，失败降级可见性、留痕不静默）。
  */
-export function accountDigestRound(carrier) {
+export async function accountDigestRound(carrier) {
   const pending = carrierField(carrier, "_pendingAsyncResults")
-  if (!Array.isArray(pending)) return { covered: 0, retried: 0, unsettled: 0 }
+  if (!Array.isArray(pending)) return { covered: 0, unsettled: 0 }
   const output = harvestAccountOutput(carrier)
   const covered = []
-  const retried = []
   const upgraded = []
   for (const entry of [...pending]) {
     if (entry?._daDelivered !== true) continue
     if (output != null && coversDigestId(output, entry.id)) { covered.push(entry); continue }
-    entry._daFailures = (entry._daFailures ?? 0) + 1
-    if (entry._daFailures <= DA_RETRY_LIMIT) { entry._daRetry = true; retried.push(entry) }
-    else upgraded.push(entry)
+    entry._daMissRounds = (entry._daMissRounds ?? 0) + 1
+    if (entry._daMissRounds >= DA_MISS_LIMIT) upgraded.push(entry)
   }
   for (const entry of covered) {
     const i = pending.indexOf(entry)
     if (i >= 0) pending.splice(i, 1)
     releaseSettledEntry(entry)
   }
+  if (upgraded.length === 0) return { covered: covered.length, unsettled: 0 }
+  // 升级四步固定先后（§6.31.5——纯内存的两面先落、披露最后：披露是本 pass 唯一的 I/O，
+  // 抛错会中断余下条目判定并越过 `run-stages.mjs` 的 `_inAutoTurn = false` 与 guard 快照）。
+  // ① 入账本（纯内存）：账本记录 = **快照**，只喂 status 面与 `preview`——被注入的对象是原条目（见 ④）。
   for (const entry of upgraded) {
-    const i = pending.indexOf(entry)
-    if (i >= 0) pending.splice(i, 1)
     appendUnsettledDigest(carrier, {
       id: String(entry.id),
       role: entry.role ?? "subagent",
-      failures: entry._daFailures,
+      missRounds: entry._daMissRounds,
       report: entry.report ?? null,
       at: Date.now(),
     })
   }
-  // 升级：恰一条提醒（机器线 + 人读线——`pushReal`）+ 恰一条留痕（同点；字段单源 = LOGGING.md §6.2）。
+  // ② 提醒：恰一条（机器线 + 人读线——`pushReal`）+ 恰一条留痕（字段单源 = LOGGING.md §6.2）。
   // 注：`ids` 以 join 串落盘——`logEvent` 只收标量（数组字段会被静默丢弃——先例 `ev:discarded`）。
-  if (upgraded.length > 0) {
+  {
     const ids = upgraded.map((entry) => String(entry.id))
     pushReal(carrier, { role: "user", content: unsettledReminder(upgraded.length, ids) })
     logEvent("ev:unsettled", { n: upgraded.length, ids: ids.join(", ") })
   }
-  return { covered: covered.length, retried: retried.length, unsettled: upgraded.length }
+  // ③ 离容器（纯结构）：至此条目定态「已升级」，不再参与判定 ⇒ 披露结构上至多一次。
+  for (const entry of upgraded) {
+    const i = pending.indexOf(entry)
+    if (i >= 0) pending.splice(i, 1)
+  }
+  // ④ 终局披露：**按 role 与首投同分流**（consult → `injectConsultResult`；其余 → `injectAsyncResult`——
+  // 内部已分派 bg / browser）；不新造第二投递形。注入的对象 = **原条目**（墓碑值
+  // `error != null ? "failed" : "consumed"` 与评审族投递水印 `entry.run` 都按原条目字段才成立）。
+  const { injectAsyncResult } = await import("../agent-tools/subagent.mjs")
+  const { injectConsultResult } = await import("../agent-tools/consult.mjs")
+  for (const entry of upgraded) {
+    try {
+      if (entry.role === "consult") await injectConsultResult(carrier, entry)
+      else await injectAsyncResult(carrier, entry)
+    } catch (e) {
+      // 逐条 continue（形同 `suspension.mjs` 注入循环收口；差异 = 该处首错即 return）——
+      // 账本 + 提醒已在 ① ② 落地，单条披露失败不得拦住余下条目，也不得拦住 finalize 的收尾两步。
+      logEvent("ev:unsettled-disclose-failed", { id: String(entry.id), err: errText(e, 200) })
+    }
+  }
+  return { covered: covered.length, unsettled: upgraded.length }
 }
 
-/** 升级提醒行（§6.31.5——逐字 = 父侧定稿：含 n / 轮数（= 重投上限 + 1）/ id 清单与接手指引）。 */
+/** 升级提醒行（§6.31.5——含 n / 轮数（恒 = `DA_MISS_LIMIT`，升级只在第 N 个未签收轮发生）/ id 清单与接手指引）。 */
 export function unsettledReminder(n, ids) {
-  return `[System reminder: ${n} background report(s) were delivered but never accounted after ${DA_RETRY_LIMIT + 1} digest rounds — automatic re-delivery has stopped and they are marked UNSETTLED: ${ids.map((id) => `#${id}`).join(", ")}. Their content was delivered in this conversation; process them there or re-spawn the work. Readable via subagent action:'status'.]`
+  return `[System reminder: ${n} background report(s) were delivered but never accounted after ${DA_MISS_LIMIT} digest rounds — they are marked UNSETTLED: ${ids.map((id) => `#${id}`).join(", ")}. Their content was delivered once in this conversation and is re-delivered once right below as the final delivery — if that copy is missing, the delivery failed and the full text stays readable via subagent action:'status'. Process it there or re-spawn the work.]`
 }
 
 /**
  * 读面（§6.31.6——status 段 ∥ 端面残余行共用单点）：行 = `{ id, role, state, attempts }`；
- * state ∈ `awaiting-digest`（在途未投递 ∥ 已投递未判）/ `retrying`（判过未覆盖）/
- * `unsettled`（已升级——随携 `preview` ≤400 字符）。
+ * state ∈ `awaiting-digest`（在途未投递 ∥ 已投递未判 = `attempts == 0`）/ `unaccounted`（判过未签收 =
+ * `attempts > 0`）/ `unsettled`（已升级——随携 `preview` ≤400 字符）；`attempts` = 未签收轮数 `_daMissRounds`。
  */
 export function unsettledRows(carrier) {
   const rows = []
   const pending = carrierField(carrier, "_pendingAsyncResults")
   for (const entry of Array.isArray(pending) ? pending : []) {
-    const failures = entry?._daFailures ?? 0
+    const missRounds = entry?._daMissRounds ?? 0
     rows.push({
       id: String(entry.id),
       role: entry.role ?? "subagent",
-      state: failures > 0 ? "retrying" : "awaiting-digest",
-      attempts: failures,
+      state: missRounds > 0 ? "unaccounted" : "awaiting-digest",
+      attempts: missRounds,
     })
   }
   const ledger = carrierField(carrier, "_unsettledDigests")
@@ -149,7 +175,7 @@ export function unsettledRows(carrier) {
       id: String(u.id),
       role: u.role ?? "subagent",
       state: "unsettled",
-      attempts: u.failures ?? 0,
+      attempts: u.missRounds ?? 0,
       preview: String(u.report ?? "").slice(0, 400),
     })
   }
@@ -162,11 +188,12 @@ export function unsettledRow(carrier, id) {
   return unsettledRows(carrier).find((row) => row.id === key) ?? null
 }
 
-/** 端面残余行判据（§6.31.6）：pending 中 `_daFailures > 0` 条数（升级条已离容器——由升级提醒承载）。 */
+/** 端面残余行判据（§6.31.6）：pending 中 `_daMissRounds > 0` 条数（与状态面 `unaccounted` 同判据；
+ *  升级条已离容器——由升级提醒承载）。 */
 export function unsettledCount(carrier) {
   const pending = carrierField(carrier, "_pendingAsyncResults")
   let n = 0
-  for (const entry of Array.isArray(pending) ? pending : []) if ((entry?._daFailures ?? 0) > 0) n += 1
+  for (const entry of Array.isArray(pending) ? pending : []) if ((entry?._daMissRounds ?? 0) > 0) n += 1
   return n
 }
 
@@ -181,7 +208,7 @@ export function armAccountRound(carrier) {
 }
 
 /** 落痕取件（§6.31.5——载体吸收读：父字段优先 / 回退 `history`）；读值 = 本 run 多轮累积文本（#939）；
- *  缺痕（本 run 零输出落痕——零模型轮 / 起跑即断）⇒ null。 */
+ *  缺痕（本 run 零输出落痕——零模型轮 / 起跑即断 / 每轮正文皆空）⇒ null。 */
 export function harvestAccountOutput(carrier) {
   const own = carrier?._lastRunOutput
   if (own !== undefined && own !== null) return own

package/agent/dispatch-run.mjs

@@ -28,7 +28,7 @@ export async function runPreparedItem(item, agent, depth, signal, callbacks) {
       ? "Error: plan mode is active — only read-only tools are allowed. Exit plan mode first."
       : item.reason === "engineering design gate"
         ? `Error: design review required before any file modification. ${item.hint}`
-        : item.reason === "d5 freeze window" || item.reason === "cross-batch record write"
+        : item.reason === "d5 freeze window" || item.reason === "cross-batch record write" || item.reason === "ledger binding"
         ? `Error: ${item.hint}`
         : item.reason === "denied by user"
         ? "Error: permission denied by user"

package/agent/dispatch.mjs

@@ -7,15 +7,17 @@
  */
 import { FILE_MUTATORS, toolTouchPaths } from "./helpers.mjs"
 import { runHooks } from "../hooks.mjs"
-import { isCodePath, declarationForTarget } from "../conventions.mjs"
+// 面判定单源（2026-10-27 三链统一批 · 设计档 §2.1）：设计门的面判据由 `isCodePath` 换成 `faceOf`——
+// 与写锁共用同一份判据（两道门各用一套必然漂移：设计门放的、写锁拦的各说各话）。`isCodePath` / `classifyPath`
+// 本体零改（其余六个消费面语义不变）；`declarationForTarget` 仍用来取出辖判定与提示指针。
+import { declarationForTarget } from "../conventions.mjs"
 import { manifestFilePath } from "../manifest.mjs"
+import { faceOf } from "./write-face.mjs"
 import { resolve, relative } from "node:path"
 import { anyLiveDesignSlot } from "../token-ttl.mjs"
-// F-LC5（LIGHT-CHANNEL §2.8 · 2026-10-09）：轻通道轮在盘谓词（代码笔通路——两件双在盘 ⇒ 父侧代码笔放行）。
-import { lightRoundOpen } from "./light-round.mjs"
 // M4 写权门禁（模块设计 §2.1#2）：冻结窗口判据组装（被审文件集 = 声明文档集 + 批次档
 // 的合流点）落 write-gate.mjs 单一权威源——本档只 import 消费（KD-M4-4 拆分点）。
-import { freezeWindowConflict, batchRecordWriteConflict } from "./write-gate.mjs"
+import { freezeWindowConflict, batchRecordWriteConflict, ledgerBindWriteConflict } from "./write-gate.mjs"
 // 门面谓词 ∕ 记账（2026-09-28 拆分外提——见头注）：动作级四谓词 + logToolError 住 ./dispatch-gates.mjs。
 import {
   logToolError, isSubagentConsumeDesignAction, isSubagentEscalateAction,
@@ -76,30 +78,23 @@ export async function executeToolCalls(agent, toolByName, toolCalls, callbacks,
       continue
     }
 
-    // Engineering mode PARENT gate: the parent agent must not touch code files
+    // Engineering mode PARENT gate: the parent agent must not touch the product face
     // before the design review passed. Signaled by a live design slot (design-review
     // approval — persists in the session slot, survives across turns; _engDesignReviewed
-    // is eng-coder-only and reset per run). Exemptions = the non-code classes of
-    // thincoder-core/conventions.mjs (documentation and temp scratch files) — writing a design
-    // document IS the design step. Anything inside a declared code segment (default:
-    // src — incl. src/prompts/*.md) is product code, not documentation, and needs a
-    // design token. The project can declare its own code paths (the manifest's
-    // `codePaths`) so a non-src layout is not silently exempted. Mechanically
-    // blocks "talk then code".
-    // F-LC5（LIGHT-CHANNEL §2.8 · 2026-10-09）：轻通道轮在盘 = 机械开路——轮次台账行（在途 · title 携「收尾链
-    // 待跑」· 携指针）与所指轮档（§1 状态行「进行中」）双在盘期间父侧代码笔放行（谓词 fail-closed）。
-    // 查找面 = 会话锚 + 其直接子目录一层（纯向下——工作区锚会话同判）。
+    // is eng-coder-only and reset per run). Exemption = the doc face only (manifest
+    // `docRoot` paths + the project manifest itself); every other path is the product
+    // face and needs a design token — writing a design document IS the design step.
+    // Mechanically blocks "talk then code".
     // F11（#1104 · PORTABILITY §3.9 / D20）：辖域 = 目标所属项目——逐目标沿祖先链取最近带档
     // 目录（`declarationForTarget`——nearest wins ∥ 纯向上 ∥ 发现梯不参与）；出辖（祖先链无档）
     // ⇒ 放行（门只管 manifest 树以内的内容）。相对形先按会话 cwd 解析（cwd 只是相对基，非声明源）；
-    // 在辖目标按所属项目装载声明，项目内判定（code 段 ∥ 兜底 fail-closed ∥ doc·temp·aux·state 豁免）零改。
+    // 在辖目标按两值面判（`write-face.mjs`）——文档面放行 ∥ 其余一切产品面（fail-closed）。
     // DESIGN-TOKEN-SETTLEMENT D3（2026-09-08）：资格判据 = 权威槽"任一活槽存在"
     // （anyLiveDesignSlot——查内存 Map，miss 回读槽文件——单值镜像 `_engDesignToken`
     // 已退役，门禁不再读镜像——AC4）。
     if (agent.config?.agent?.engineering && depth === 0
         && !anyLiveDesignSlot(agent)
-        && FILE_MUTATORS.has(toolCall.name)
-        && !(await lightRoundOpen(agent))) {
+        && FILE_MUTATORS.has(toolCall.name)) {
       const paths = toolTouchPaths(tool, args)
       // Unknown/missing paths (non-string / empty — nothing to judge) block conservatively.
       // Known paths are judged per target: resolve against the session cwd first, then
@@ -112,7 +107,8 @@ export async function executeToolCalls(agent, toolByName, toolCalls, callbacks,
         if (typeof p !== "string" || p.trim() === "") { blocked = true; continue }
         const abs = resolve(agent.cwd, p)
         const conv = declarationForTarget(abs)
-        if (!conv || !isCodePath(abs, conv)) continue
+        if (!conv) continue // 出辖（祖先链无档）⇒ 放行（零改）
+        if (faceOf(abs) !== "product") continue // 面判单源（`write-face.mjs`）——文档面 / 出辖放行
         blocked = true
         if (!noteConv && !conv.declared) noteConv = conv
       }
@@ -124,8 +120,7 @@ export async function executeToolCalls(agent, toolByName, toolCalls, callbacks,
         prepared.push({
           toolCall, tool, denied: true,
           reason: "engineering design gate",
-          hint: `Engineering mode: write the design document first（location per your project's document conventions）, then call advisor with type='design' to review it, and wait for user approval. Implementation is done by eng-coder subagents.${convNote} ` +
-            `If this is a light-channel code pen: the gate looks for the round from the session anchor and its direct subdirectories — book the round first (an in-flight batch record plus a 在途 ledger row carrying 「收尾链待跑」 pointing at the record); code pens pass once that is on disk.`,
+          hint: `Engineering mode: write the design document first（location per your project's document conventions）, then call advisor with type='design' to review it, and wait for user approval. Implementation is done by eng-coder subagents.${convNote}`,
         })
         continue
       }
@@ -164,6 +159,19 @@ export async function executeToolCalls(agent, toolByName, toolCalls, callbacks,
       }
     }
 
+    // 写锁（第三道 · 2026-11-03 笔-账绑定批 · 设计档 §2.3）：本笔报的 `ledger:"#N"` 必须是**目标所属项目**
+    // 台账里一条 `status = 在途` 的行。位次 = 既有两道之后（既有拒因先报）；判序 = 先判目标所属项目
+    // （出辖 ⇒ 门不管），再按号查该根台账；台账读不到 ⇒ 拒（业务门）。
+    // 入口集 = 十三把（写盘七件 + `bash` ∥ `execute` + `git` + `manifest` ∥ `memory` + `ssh`）——`bash` ∥ `execute`
+    // 与写盘工具同一判据、不按命令内容分类（决策 36）；`git` 只对写型 action 要号（决策 37）；`ssh` 只对 `get` 要号。
+    // 只在工程模式生效（`agent.config.agent.engineering`）∥ 只在 depth 0（子代理走既有 token 门）。
+    // 路径集与 `args.ledger` 由判据函数自己取（调形只传 tool + toolName + args）。
+    const ledgerConflict = await ledgerBindWriteConflict(agent, depth, tool, toolCall.name, args)
+    if (ledgerConflict) {
+      prepared.push({ toolCall, tool, denied: true, reason: "ledger binding", hint: ledgerConflict.message })
+      continue
+    }
+
     // Readonly tools (and autoApprove — the short-circuit, unchanged for the
     // whole batch too) skip the permission stage entirely.
     // AGENT-LOOP-SUBAGENT.md §6.7.6 D-E3 task-domain authorization (spawn-time): an eng-coder child's

package/agent/family-tools.mjs

@@ -45,17 +45,21 @@ export async function assembleFamilyTools({
     return { ...tool, description: tool.description + `\nCurrently configured consultants (this tool's pool): ${list}` }
   }
 
-  // Role enum is mutually exclusive: normal mode has "coder", engineering mode has "eng-coder"/"eng-designer"
+  // Role enum is mutually exclusive: normal mode has "coder", engineering mode has "eng-coder"/"eng-designer";
+  // "tester" (AGENT-LOOP-SUBAGENT.md §6.59) is dispatchable in both modes — it runs verification and returns
+  // readings; its tool table (read-only set ∪ execute/bash − {verify, advisor}) holds no write tool. Run-only is the
+  // role contract, not a sandbox (§6.59.7 边界 1 — `bash` can still write, and that is by design).
+  const testerSuffix = " role='tester' runs verification and reports the readings back — it never edits code or documents."
   const subagentRoles = (depth === 0 && engineering)
     ? {
-        enum: ["explore", "eng-designer", "eng-coder"],
+        enum: ["explore", "eng-designer", "eng-coder", "tester"],
         description: "The sub-agent role — see the tool description for the role capability matrix. Exact spelling required.",
-        suffix: " In engineering mode, use role='eng-coder' for implementation (coder is disabled) and role='eng-designer' for writing the requirements/design documents.",
+        suffix: " In engineering mode, use role='eng-coder' for implementation (coder is disabled) and role='eng-designer' for writing the requirements/design documents." + testerSuffix,
       }
     : {
-        enum: ["explore", "plan", "coder"],
+        enum: ["explore", "plan", "coder", "tester"],
         description: "The sub-agent role — see the tool description for the role capability matrix. Exact spelling required.",
-        suffix: "",
+        suffix: testerSuffix,
       }
 
   const filteredSubagent = depth === 0 ? {