@thincoder/core 0.9.1 → 0.9.3

package/CHANGELOG.md

@@ -0,0 +1,63 @@
+# Changelog（@thincoder/core）
+
+All notable changes to the core package are documented here.
+Format: Keep a Changelog · 中文 · 号在发布时定（CalVer——见 `docs/RELEASE.md` §4）。
+
+## [0.9.3] — 2026-09-22
+
+> 0.9.2 → 0.9.3（月内序号——发布时定号）
+
+### Added
+
+- **派生会话索引库**（`node:sqlite` · 零新依赖）：`read_history` 超大会话不再整档拒（>50k 消息经索引可查）+ `path:"all"` 跨会话检索（行携 `session.file` 回查锚）+ `tool_calls` 携参数；索引从记录段增量建 · 可重建（丢/坏自愈）· 主存（会话文件）零改。
+- **子代理「系统固块」**：机制性指令（审计五锚 + 批档行）改由 spawn 单点写入并拼进 system 面（前缀缓存契约——同 child 连跑 `systemPrompt` 逐字节相等）。
+- **进程族单源**：`killProcessTree` 收口为 `tools/process-tree.mjs`（核 / VSC 本地副本全消除）。
+- **退出即释放会话认领**：正常退出释放本进程认领（端标记保留作路标）——重启恢复不再依赖进程探测兜底。
+- **认领释放扩面**：ACP `session/close` · 跨 cwd 释放 · 被占槽返回可区分信号（零写）。
+
+### Changed
+
+- **批档工具词面协议结构化**：`batch status` enum 化（散文走 `note`）+ `create` 补 `source` / `prev` 前缀归一 / 占位自动；append/status 占位残留机检（fail-closed）。
+- **工程模式 `task` 工具机械停用**（追踪面 = 批档 + 台账；普通模式零改）。
+- **设置面**：敏感键谓词导出 + 非敏感父对象 JSON 化渲染（`[object Object]` 瑕疙消除）。
+- FTS 语言面外提 `fts-text.mjs`（`segmentCJK` / `buildFtsQuery` 单源 + re-export 面）。
+
+### Fixed
+
+- 会话索引自愈链（坏库 / 删库现场保留 + 重建）· 段轮转与等长改写的水位判别 · 源消失级联清行。
+
+## [0.9.2] — 2026-09-21
+
+> 0.9.1 → 0.9.2（月内序号——发布时定号）
+
+### Added
+
+- **PROJECT-MANIFEST 模型（按用点解析）**：项目发现五级梯（会话锚 → 带档祖先 → 一层子档 → 工作区……）+ owning-ancestor 归属 + 建档流；整档缺失不再静默（启动降级 + 明示提示）。
+- **批档生命周期工具** `batch`（create / append / status / close——原 `batch_segment` 更名，别名保留）。
+- **台账执行人列**（F-LX1）：executor 归属 + 判存活显示。
+- **信号行两档标签**（digest / ask）+ ask 参数 + 起始行（F-UC8）。
+- **会话认领释放**（F-CR1/CR2）：释放 + 拒绝零写入。
+
+### Changed
+
+- **非阻塞启动**：异步会话 GC · 陈旧清扫 · traces 清理（启动不再被大扫除卡住）。
+- **工程模式排除 `plan` 角色**（FR31——装配 / 命令 / 残留三面一致）。
+- **包面**：README 补建（static 工具口径收正）+ LICENSE + npm 元数据；`files` 白名单不变。
+
+### Fixed
+
+- 批别名残留（测试断言 / 提示词文档引用 / 错误串）· VSC 子代理块标题行与 CLI 对齐（标题段补全）。
+
+## [0.9.1] — 2026-09-21
+
+> 核首发（2026-09 当月推导——registry 无号 ⇒ `0.<当月>.1`；首发即本段 ✗ 无更早历史——核内容此前散在两产品仓 ✗ 无独立版本号可考 ✗）。
+
+### Added
+
+- **核包首发 `@thincoder/core@0.9.1`**：两产品共享机制收敛后的单一权威源——agent 执行环 / 子代理调度（spawn-gate · async 池 · notify_parent）· advisor 评审 · provider 层（SSE 流式 · thinking 映射 · 重试）· 记忆三层 · 工具系统 · 会话存储 · MCP 客户端 · git 集成 · 台账。
+- **提示词与工具文档随包分发**：`prompts/` 15 档 + `tool-docs/` 24 档（一致性断言 D 对象——与 CLI 装机目录 / vsix 三处逐字相等）。
+- **发布门禁**：`prepublishOnly` = `npm test`（与 CLI/VSC 门禁对称——2026-09-21 首发 补上）。
+
+### Changed
+
+- 两产品 `dependencies` 同步收正 `^0.1.0 → ^0.9.1`（声明面与 registry 实发对齐——断言 A）。

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 ThinCoder contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,90 @@
+# @thincoder/core
+
+**The shared core of the ThinCoder products — the mechanisms and the prompt content behind the ThinCoder CLI and the ThinCoder VS Code extension.**
+
+Both products are thin shells: this package owns everything they have in common — the agent loop and subagent
+scheduling, the advisor review system, the provider layer (SSE streaming, thinking-mode mapping, retries, rate
+gating), the three-layer memory with its code and document indexes, the built-in tool system, session storage,
+the MCP client, git and checkpoint integration, the ledger — plus the prompt texts and tool descriptions the
+two products assemble their model context from.
+
+The core has **zero third-party dependencies**: Node.js standard library only, pure ESM (`.mjs`), no build step.
+
+## Requirements
+
+- **Node.js >= 22.13.0** — the floor comes from the built-in `node:sqlite` module (usable without a flag since 22.13.0), which the memory and ledger modules use.
+
+## Install
+
+```bash
+npm install @thincoder/core
+```
+
+The package is a library — it ships no CLI of its own. Most users never install it directly: the two products
+declare it as a dependency (`thincoder`, the CLI, and `thincoder-vscode`, the VS Code extension). Install it
+directly when you build your own tooling on the shared core.
+
+## Importing
+
+There is no bare-root entry point — `import "@thincoder/core"` does not resolve (`ERR_PACKAGE_PATH_NOT_EXPORTED`).
+Every import is a subpath, and subpaths map 1:1 onto files in the package (`exports` is `{ "./*": "./*" }`), so
+include the `.mjs` extension:
+
+```js
+import { loadConfig } from "@thincoder/core/config.mjs"
+import { createAgent } from "@thincoder/core/agent.mjs"
+import { chat } from "@thincoder/core/provider/index.mjs"
+import { put, putMarkdown } from "@thincoder/core/memory.mjs"
+import { runAdvisorReview } from "@thincoder/core/advisor/run.mjs"
+```
+
+Nested paths work the same way (`@thincoder/core/git/checkpoint.mjs`, `@thincoder/core/mcp/transport-stdio.mjs`).
+
+## What's inside
+
+| Area | Modules |
+|---|---|
+| Agent loop, subagents | `agent.mjs` · `agent/` · `agent-tools/` |
+| Advisor review, consultation, escalate | `advisor/` · `agent-tools/consult.mjs` · `agent-tools/escalate-async.mjs` |
+| Provider layer (streaming, thinking mapping, retries, rate gate) | `provider/` |
+| Memory, embedding, code/doc indexes | `memory.mjs` · `memory/` · `embedding.mjs` |
+| Built-in tools | `tools/` |
+| Sessions | `session.mjs` · `session-*.mjs` |
+| MCP client | `mcp.mjs` · `mcp/` |
+| Git, checkpoints, team-memory sync | `git/` |
+| Ledger, traces | `ledger.mjs` · `traces/` |
+
+## Shared prompt content
+
+The two products author no slot prompts or tool-description bodies of their own: both assemble their model
+context from the texts in this package. `prompt-files.mjs` resolves them relative to the package itself, so the
+same files are loaded in every delivery state (local link, npm install, packaged extension).
+
+- `prompts/` — the slot-based prompt texts: personas, the common layer, the discipline layers, and the advisor
+  and consultation modules.
+- `tool-docs/` — one file per static built-in tool; these texts are what the model reads as tool descriptions.
+
+A prompt rule or a tool-description body is edited in exactly one place, and both products pick it up with the
+next release. The exception is two tool-face anchors — the bash terminal face in `tool-docs/bash.md` and the
+question-panel availability line in `tool-docs/question.md`: each product supplies those two values from its own
+`src/prompt-injections.mjs`, because they describe behavior that differs between the CLI and the extension.
+
+## Versioning
+
+Version numbers are calendar-based (CalVer): `year.month.monthly-count`, where the year segment counts from
+2026 (`0` = 2026). `0.9.1` is therefore the first core release of September 2026.
+
+The number marks release time, not API compatibility — read `CHANGELOG.md` for what changed.
+Per-release notes and artifacts: `CHANGELOG.md` in this package and the [GitHub Releases](https://github.com/xinbo-tech/thincoder/releases) page.
+
+## Contributing
+
+The core lives in `thincoder-core/` of the ThinCoder repository; bug reports and questions go to the
+repository issue tracker. Two conventions shape every change: pure ESM `.mjs` with no build step, and
+zero third-party dependencies — if the Node.js standard library can do it, no third-party package is
+allowed. `npm test` runs the offline unit suite; it runs again on release through `prepublishOnly`.
+Mechanism design documents live in the repository under `docs/core/design/`.
+
+## License
+
+MIT — see `LICENSE`.

package/advisor/loop.mjs

@@ -11,7 +11,7 @@ import { chat } from "../provider/core.mjs"
 import { providerSpec, assistantToolCallMessage } from "../config.mjs"
 import { toOpenAISchema } from "../tools/index.mjs"
 import { truncateAdvisorResult } from "./truncate.mjs"
-import { batchSegmentTool } from "../agent-tools/batch-segment.mjs"
+import { batchTool } from "../agent-tools/batch.mjs"
 import {
   estimateTokens, compactMessages, shouldBudgetNudge, budgetNudgeText, timeoutTail, renderTimeline,
   MAX_ADVISOR_TURNS, advisorContextBudget, TOOL_TIMEOUT_MS, REVIEW_TIMEOUT_MS, MAX_RESULT_CHARS,
@@ -42,7 +42,7 @@ function advisorToolsFor(agent, reviewType = "code", batchDoc = null) {
   const tools = [readTool, globTool, grepTool, lsTool, lspTool, advisorCodeSearchTool(agent)]
   // §2.20.3（第 4 批）：**只有绑定了批次档的设计评审**额外拿到写通道——代码评审工具集
   // 逐字节不变（零 git + 只读不变量，§2.20.8 #1）；未绑定 → 不挂载（fail-closed）。
-  if (reviewType === "design" && batchDoc) tools.push(batchSegmentTool(batchDoc, { review: true }))
+  if (reviewType === "design" && batchDoc) tools.push(batchTool(batchDoc, { review: true }))
   return { schemas: tools.map(toOpenAISchema), byName: new Map(tools.map((t) => [t.name, t])) }
 }
 // Test seam: the tool set is pure（恒在六工具 + 批次档绑定條件）。

package/advisor/run.mjs

@@ -10,7 +10,7 @@ import { buildObjectDeclarationBlock, buildDesignApprovalBlock } from "./message
 import { appendCitationReport } from "./citations.mjs"
 import { runAdvisorToolLoop } from "./loop.mjs"
 import { advisorIncompleteMarker, estimateTokens } from "./compaction.mjs"
-import { batchDocForReview } from "../agent-tools/batch-segment.mjs"
+import { batchDocForReview } from "../agent-tools/batch.mjs"
 
 // 拆分后 import 面（既有导出名逐一保面——re-export；谓词为本批新增）。
 export { ADVISOR_THINKING_PLACEHOLDER, MAX_RESULT_CHARS, renderTimeline as _renderTimeline } from "./compaction.mjs"

package/agent/completion.mjs

@@ -53,7 +53,9 @@ export function handleCompletion(agent, response, depth, turn, guardPushbacks, h
   // pending item can't be resolved). After the single reminder the model is free
   // to finish — updating the task list (task tool) resets the budget, so a fresh
   // list state earns one fresh reminder.
-  if (depth === 0 && agent.tasks.some((t) => t.status === "pending") && (agent._taskPushbacks ?? 0) < 1) {
+  // F10（催更门连带）：工程模式下 task 工具机械停用（装配摘除 + execute 拒）⇒ 不再发指向被拒
+  // 工具的提醒（死胡同提醒防线）；列表本体与 `_taskPushbacks` 预算语义零改。
+  if (depth === 0 && !agent.config?.agent?.engineering && agent.tasks.some((t) => t.status === "pending") && (agent._taskPushbacks ?? 0) < 1) {
     agent._taskPushbacks = (agent._taskPushbacks ?? 0) + 1
     const pending = agent.tasks.filter((t) => t.status === "pending").map((t) => t.title).join(", ")
     pushReal(agent, { role: "assistant", content: response.content })

package/agent/family-tools.mjs

@@ -6,7 +6,9 @@
  * （消灭「同一角色矩阵两份实现」= 本批缺陷的类根因）；端差（VSC 装饰链 / settings 追加 /
  * consult 池来源）经 `decorate` 注入——**不传 = 核默认形态**（CLI = 迁出前逐字）。
  *
- * 返回 = 家族段数组（`[task, plan, timer, ...depth 家族 / 角色段]`）——**不含** `agent.tools`
+ * 返回 = 家族段数组（**非**工程模式：`[task, plan, timer, ...depth 家族 / 角色段]`；工程模式：
+ * 固定段 = `[timer]`——plan 不入表（FR31 ① / KD8）· task 不入表（F10——工程模式机械停用，
+ * 同 KD8 卸载处置））——**不含** `agent.tools`
  * 展开与 `extraTools`（调用点各自展开：核 `agent/setup.mjs` 两段式）。
  *
  * 登记册**动态**载入：`agent-tools.mjs` 静态图经 consult/subagent 族可达核 agent 栈
@@ -20,11 +22,11 @@ export async function assembleFamilyTools({
   role = null,           // string   子代理角色（eng-coder / eng-designer / coder / consult / explore / …）
   engineering = false,   // boolean  depth-0 role enum 注入用（工程模式）
   consultModels = [],    // array    consult 池（[] ⇒ consult 工具不注册）
-  batchDoc = null,       // string   batchSegment 绑定路径（eng 角色）
+  batchDoc = null,       // string   批次档绑定路径（eng 角色 → batchTool 绑定）
   decorate = null,       // object   端差面：{ subagent?, consultStart?, consultStop?, settings? }
 } = {}) {
   // CORE-UNIFICATION TOOLS #83：consult 家族随统一登记册自 `../agent-tools.mjs` 取用（单一来源）
-  const { planTool, subagentTool, taskTool, skillTool, goalTool, verifyTool, recentChangesTool, timerTool, advisorTool, engTool, readHistoryTool, batchSegmentTool, consultStartTool, consultStopTool, parentChannelTool } = await import("../agent-tools.mjs")
+  const { planTool, subagentTool, taskTool, skillTool, goalTool, verifyTool, recentChangesTool, timerTool, advisorTool, engTool, readHistoryTool, contextTool, batchTool, consultStartTool, consultStopTool, parentChannelTool } = await import("../agent-tools.mjs")
   // 写命令（主 agent 专用）——动态 import 且**仅 depth===0 载入**（ledger 链静态达 node:sqlite——
   // W8 契约②；子代理路径不注册 = 零载入——depth>0 解构得空、不引用即无副作用）
   const { ledgerAddTool, ledgerUpdateTool, ledgerCloseTool } = depth === 0 ? await import("../ledger.mjs") : {}
@@ -137,7 +139,7 @@ export async function assembleFamilyTools({
     : []
 
   const depthOnly = depth === 0
-    ? [decorate?.subagent ?? filteredSubagent, skillTool, goalTool, engTool, verifyTool, recentChangesTool, readHistoryTool, advisorTool,
+    ? [decorate?.subagent ?? filteredSubagent, skillTool, goalTool, engTool, verifyTool, recentChangesTool, readHistoryTool, contextTool, advisorTool, batchTool(null),
       ...consultTools,
       // 台账写命令（M2——仅主 agent；查询面 ledger_count 住基础集 tools/index.mjs）。
       // fail-closed：子代理不挂载 = 写面机械不可达。
@@ -156,19 +158,30 @@ export async function assembleFamilyTools({
     // eng-coder: advisor + verify + the §18 audit-only subagent channel (D-E3).
     // eng-designer (§2.15 D): the survey-only subagent channel alone — no advisor
     // (it does not fire reviews) and no verify (its deliverable is documents, not code).
-    // §2.20.3（第 4 批）：两分支各追加 batch_segment——目标档 = spawn 时绑定的
-    // `batchDoc`（§2.20.2）；主 agent 不挂载（§1/§4/§6 走普通文档写）。
-    // SUBAGENT-UPSTREAM-CHANNEL（AGENT-LOOP-SUBAGENT.md §6.27.4 装配接线）：子代理上行通道
+    // BATCH-RECORD §4.3 挂载表（批次档生命周期工具化批）：eng 两分支各挂主名 `batch`
+    // （绑定段 append/status；目标 = spawn 绑定 `child._batchDoc`）——§2.20.3 的 batch_segment
+    // 挂载形态已随单名化收口退役（过渡别名 §4.14 不入生产挂载面）；depth-0 主 agent 同表挂载
+    // `batch`（D-BR18 扩权——create/close + append §1/§4/§6 + status §1（轮 2 裁定②：§4/§6
+    // 状态面走普通文档写），目标走可选 path / 在飞扫描）。
+    // SUBAGENT-UPSTREAM-CHANNEL（AGENT-LOOP-UPSTREAM.md §6.27.4 装配接线）：子代理上行通道
     // （`notify_parent`）随 depth>0 段**前置**——4 处携带 = eng-coder / eng-designer / coder / 兜底段
     // （未列名 depth>0 role 落同一兜底段 ⇒ 亦装配；语义 =「depth>0 且非 consult 皆装配」）；
     // 计数口径：`consult` 分支不入 ⇒ 「5 个插入点」读法已作废（实读 `thincoder-core/agent/family-tools.mjs:165-169`）。
     // consult 段不入（其角色语义 = 父发起的一次性会诊，父在其 settle 前不期望中途对话）。
-    : engChildRole === "eng-coder" ? [parentChannelTool, advisorTool, verifyTool, batchSegmentTool(batchDoc), ...(engChildSubagent ? [engChildSubagent] : [])]
-    : engChildRole === "eng-designer" ? [parentChannelTool, batchSegmentTool(batchDoc), ...(engChildSubagent ? [engChildSubagent] : [])]
+    : engChildRole === "eng-coder" ? [parentChannelTool, advisorTool, verifyTool, batchTool(batchDoc), ...(engChildSubagent ? [engChildSubagent] : [])]
+    : engChildRole === "eng-designer" ? [parentChannelTool, batchTool(batchDoc), ...(engChildSubagent ? [engChildSubagent] : [])]
     : role === "coder" ? [parentChannelTool, verifyTool, advisorTool]
     : role === "consult" ? [recentChangesTool]
     : [parentChannelTool]
 
-  // task/plan/timer 固定段（所有面都有）：装配序 = agent.tools → 固定段 → 家族段 → extraTools
-  return [taskTool, planTool, timerTool, ...depthOnly]
+  // 固定段（装配序 = agent.tools → 固定段 → 家族段 → extraTools）：timer 全模式全深度；
+  // plan 随模式位——ENG-PLAN-EXCLUSION（FR31 ① · KD8 卸载而非「注册 + 报错」· KD11 全深度两端）；
+  // task 随模式位——F10（task 工程模式机械停用；同 KD8 处置：**不入表**——模型不可见、零 token 税；
+  // execute 层另有机械拒兜底，见 `agent-tools/task.mjs`）。
+  // 工程模式固定段 = plan / task 皆**不入表**；普通模式固定段逐字不变（FR31 边界 / F10 边界）。
+  // 判据 = 单一模式位 `engineering`（不带深度分支——子代理面随同排除，role enum
+  // `:44-49` + spawn 门 / task execute 门已同向）。
+  return engineering
+    ? [timerTool, ...depthOnly]
+    : [taskTool, planTool, timerTool, ...depthOnly]
 }

package/agent/helpers.mjs

@@ -386,13 +386,22 @@ export const ENG_OFF_REMINDER =
   "Changes go through the normal workflow: you may edit files directly, advisor/verify " +
   "guards apply per config.]"
 
-/** Manual-tier auto-turn digest domain (AGENT-LOOP.md §17 D-S6): organize-only.
+/** Manual-tier auto-turn digest domain (normal-mode base — engineering variant =
+ *  AUTO_TURN_DIGEST_DOMAIN_ENG below): organize-only. Mechanism = AGENT-LOOP-ASYNC-POOL.md §6.8;
+ *  mode variant text = TOOLS.md §6.15.3.
  *  Injected per manual auto-turn run — writes/execute/spawns/questions are also
  *  mechanically denied (no permission handler + spawn gate); this steers first. */
 export const AUTO_TURN_DIGEST_DOMAIN =
   "[System reminder: auto-turn — background async subagents finished while there was no user message, and this turn runs automatically to digest their reports (the finished-report reminders above). No one is waiting for this reply, so organize only: 1) summarize each finished report's key points into this conversation for the user to read later; 2) update the task list with the task tool (allowed) to mark finished work done; 3) write decision points with a suggested next step as text — do not execute it. FORBIDDEN this turn (mechanically enforced): modifying files, bash/execute/verify, spawning subagents, asking questions — those need a real user message. End the turn once the summaries are written.]"
 
-/** Up-stream wake-turn domain (AGENT-LOOP-SUBAGENT.md §6.27.12.8): a running subagent sent
+/** Engineering-mode auto-turn digest domain variant (mode = `agent.config.agent.engineering`;
+ *  clause 2 drops the task-tool pointer — F10: the task tool is disabled in engineering mode,
+ *  the batch record + ledger are the tracking authority). Single line, verbatim from the
+ *  design doc (TOOLS.md §6.15.3); mechanism = AGENT-LOOP-ASYNC-POOL.md §6.8. Content authority = parent side. */
+export const AUTO_TURN_DIGEST_DOMAIN_ENG =
+  "[System reminder: auto-turn — background async subagents finished while there was no user message, and this turn runs automatically to digest their reports (the finished-report reminders above). No one is waiting for this reply, so organize only: 1) summarize each finished report's key points into this conversation for the user to read later; 2) (engineering mode: the task tool is disabled — no task-list update is expected this turn; the batch record + ledger are the tracking authority and are updated in real user turns); 3) write decision points with a suggested next step as text — do not execute it. FORBIDDEN this turn (mechanically enforced): modifying files, bash/execute/verify, spawning subagents, asking questions — those need a real user message. End the turn once the summaries are written.]"
+
+/** Up-stream wake-turn domain (AGENT-LOOP-UPSTREAM.md §6.27.12.8): a running subagent sent
  *  an in-flight message and is waiting for the reply — the digest domain's "No one is waiting
  *  for this reply" is the opposite of the truth, so the wake turn gets its own text.
  *  Verbatim from the design doc (single line — no newlines). Content authority = parent side. */

package/agent/run-stages.mjs

@@ -11,10 +11,10 @@ import { compressIfNeeded, compressFallback, COMPRESS_FAILURE_LIMIT } from "../c
 import { ensureAutoReminder, injectEngineeringReminder, ContinueError, snapshotGuard } from "./helpers.mjs"
 import { pushManifestStateReminder } from "./setup-reminders.mjs"
 import { cleanupConsultSessions } from "../agent-tools/consult.mjs"
-import { logEvent } from "../log.mjs"
+import { logEvent, errText } from "../log.mjs"
 // ASYNC-RESULT-CONTAINER.md D1：池 accessor（absorb 双池——advisor 独立池无队列）
 import { getAsyncPool, releaseSettledEntry } from "../agent-tools/async-settle.mjs"
-// 批 4 CLI-ASYNC-DISCARD（AGENT-LOOP-SUBAGENT.md §6.20）：中止分支「只清已死」收尾单点
+// 批 4 CLI-ASYNC-DISCARD（AGENT-LOOP-ASYNC-POOL.md §6.20）：中止分支「只清已死」收尾单点
 import { discardAbortedPool, discardAbortedAdvisors } from "../agent-tools/async-discard.mjs"
 // R10 L3 (MULTI-INSTANCE-COLLAB §2a.5 D-L3a)：回合末域登记 flush（写工具钩子累积 →
 // 整写一次本实例 peers 文件——无写入跳过；失败容忍不抛）
@@ -59,11 +59,28 @@ export function injectResponseReminders(agent, response) {
  * 计数复位（recentCallSigs——runAgent 回合级局部——经 ctx 传对象引用）/压缩完成事件
  * /AUTO 提醒重注入。失败：AbortError 透传；计数 + Q3 onCompressFail；
  * COMPRESS_FAILURE_LIMIT 连续失败降级 compressFallback（确定性截断——不发 LLM）。
+ * 模型主动压缩（`context` 工具）由本点消费（§6.16.2——取用即清槽；no-op 与失败各落一行注记）。
  */
 export async function runCompactionCheck(agent, ctx) {
   const { threshold, callbacks, compactionOverhead, signal, recentCallSigs } = ctx
+  // F-CC2（CONTEXT-COMPACTION.md §6.16.2）：模型主动压缩（`context` 工具）在**本安全点**消费——
+  // 取用即清槽（失败不重放；重发由模型再调）；`force` 只跳过阈值早退（模型判定优先于阈值），
+  // 其余全同（同 splitHistory / 同尾部预算 / 同摘要链 / 同回注 / 同基线失效）。
+  const pending = agent._pendingCompact
+  agent._pendingCompact = null
   try {
-    if (await compressIfNeeded(agent, threshold, callbacks, compactionOverhead, signal)) {
+    let compacted = await compressIfNeeded(
+      agent, threshold, callbacks,
+      pending ? { ...compactionOverhead, force: true, focus: pending.focus } : compactionOverhead,
+      signal,
+    )
+    if (!compacted && pending) {
+      // 强制面无可压（短历史无中段）⇒ 记 no-op 注记后**照常**跑阈值面（阈值面不因模型请求让位）
+      const { compactNoopNote } = await import("../agent-tools/context.mjs")
+      agent.history.push({ role: "user", content: compactNoopNote(), transient: true })
+      compacted = await compressIfNeeded(agent, threshold, callbacks, compactionOverhead, signal)
+    }
+    if (compacted) {
       agent._compressFailures = 0
       agent._planReminderAtLen = 0 // After compression history shrinks, reset cadence so reminders resume
       recentCallSigs.length = 0 // After compression history is rebuilt, reset stall detection counter
@@ -79,6 +96,11 @@ export async function runCompactionCheck(agent, ctx) {
     // Q3 (CONTEXT-COMPACTION §7 D-C1): a failed compression is surfaced to the panel;
     // COMPRESS_FAILURE_LIMIT consecutive failures still degrade to compressFallback.
     callbacks?.onCompressFail?.(compressError)
+    if (pending) {
+      // 失败注记（§6.16.2 回执面②）：模型面告知缺口——既有失败链 / 面板面零改，仅补一行机器注记
+      const { compactFailureNote } = await import("../agent-tools/context.mjs")
+      agent.history.push({ role: "user", content: compactFailureNote(errText(compressError), agent._compressFailures), transient: true })
+    }
     if (agent._compressFailures >= COMPRESS_FAILURE_LIMIT) {
       agent._compressFailures = 0
       if (compressFallback(agent)) callbacks.onCompress?.(agent._lastCompressInfo ?? {})
@@ -151,7 +173,7 @@ export async function finalizeAgentTurn(agent, ctx) {
   // driver aborts them on its own abort unwind.
   // Async subagent turn-end handling (AGENT-LOOP.md §15 D-A3 + §17 D-S1). Lifecycle:
   // - Ctrl+C (plain abort): children were aborted with the parent signal — discard dead
-  //   entries (tombstone/out-of-pool/notice — AGENT-LOOP-SUBAGENT.md §6.20; no stale
+  //   entries (tombstone/out-of-pool/notice — AGENT-LOOP-ASYNC-POOL.md §6.20; no stale
   //   errors injected — user explicitly stopped); consultation sessions are cross-turn
   //   background work since R17 — the abort branch is the ONLY normal-path place that
   //   aborts them (cleanupConsultSessions marks stopped → they never reach the digest).
@@ -205,7 +227,7 @@ export async function finalizeAgentTurn(agent, ctx) {
 }
 
 /**
- * Turn-end async subagent collection (AGENT-LOOP.md §17 D-S1 + §17.5 supersede):
+ * Turn-end async subagent collection (AGENT-LOOP-ASYNC-POOL.md §6.8 — D-S1 + suspension supersede):
  * two modes, selected by the caller's driver context (17.5.2/17.5.4 #2):
  * - suspDriven=false (fallback — headless/direct runAgent callers without a
  *   suspension driver): inject every entry that SETTLED during this run

package/agent/setup-reminders.mjs

@@ -19,16 +19,20 @@
  * pushManifestStateReminder carries the project phase as a self-healing single live line.
  * #34 adds the per-turn value refresh (mtime-gated re-read — §2.6 ③b / KD-M1-17..M1-19):
  * the line always carries the CURRENT on-disk phase, not the assembly-time snapshot.
+ * 2026-09-21（#188）：**状态选行**（③' `projectView(agent.cwd)` —— KD-M1-26）——`ok` ⇒ 相位行
+ * （逐字零改）；`no-project` / `ambiguous` ⇒ 报明行；`missing` / `invalid` ⇒ 有既往好值保守沿用、
+ * 无 ⇒ 报明行；无锚 ⇒ **零 I/O / 零报明**（KD-M1-27）。报明行构造 = `manifestReportLine` 四态。
  *
  * #113（S1 续轮第二批——VSC 侧并入 ④ 段）：`pushInjections`（机器行专用注入——编辑器上下文
  * 等端侧采集内容；同文去重）与 `appendImagePointer`（粘贴图指引——非多模态模型可见报错）
  * 两档并入——内容由端采集 / 传入（核内零端名），核供注入纪律单点。
  */
 import { statSync } from "node:fs"
+import { resolve } from "node:path"
 import { END } from "../session-slots.mjs"
 import { peerInstances } from "../peer-instances.mjs"
 import { specForModel } from "../config.mjs"
-import { manifestFilePath, readManifest } from "../manifest.mjs"
+import { manifestFilePath, readManifest, projectView } from "../manifest.mjs"
 
 /** env-state line builder — pure, unit-testable.
  *  §6.11（F1）：slot 字段入行——位置在 model 后 resumed 前（N3：无绑定 → 显式 null——
@@ -71,6 +75,39 @@ export function manifestStateLine({ phase }) {
   return `${MANIFEST_LINE_PREFIX}phase: ${phase}${discipline ? ` (discipline: ${discipline})` : ""}.]`
 }
 
+/**
+ * 报明行构造 — pure, unit-testable（**本批新增**——`docs/core/design/MANIFEST.md` §2.6 条 1b /
+ * KD-M1-26）：`projectView` 四非 ok 态各自的行文，**逐字**（同族前缀 `MANIFEST_LINE_PREFIX`——
+ * 报明行与相位行共用单活体机制）。歧义行按 `matched` **两变体**（`manifest` = 带档级「marker
+ * directories」/ `git` = 裸仓档「repositories … (none carries …)」——同口径 = `TOOLS.md` §6.13 A22）；
+ * `candidates` 按名排序（判据同 `discoverProjects`）、`<abs…>` 以「、」连接；`errors` 逐条以「；」连接。
+ * `ok` / 未知态 ⇒ `null`（无报明行——相位行归 `manifestStateLine`）。
+ * @param {{state?:string, cwd?:string, root?:string|null, path?:string|null, candidates?:string[], errors?:string[], matched?:string|null}} p 行素材（= `projectView` 返回面 + 锚）
+ * @returns {string|null} 行文 / null（非报明态）
+ */
+export function manifestReportLine({ state, cwd, root, path, candidates, errors, matched } = {}) {
+  if (state === "no-project") {
+    return `${MANIFEST_LINE_PREFIX}none — no project at ${cwd} (no manifest on the ancestor chain, none below). ` +
+      `Parameters fall back to defaults. Create PROJECT-MANIFEST.json here to land a project (git optional).]`
+  }
+  if (state === "ambiguous") {
+    const list = candidates ?? []
+    const head = matched === "git"
+      ? `ambiguous — ${list.length} candidate repositories under ${cwd} (none carries PROJECT-MANIFEST.json):`
+      : `ambiguous — ${list.length} candidate marker directories under ${cwd}:`
+    return `${MANIFEST_LINE_PREFIX}${head} ${list.join("、")} — target the intended one explicitly (the mechanism never picks).]`
+  }
+  if (state === "missing") {
+    return `${MANIFEST_LINE_PREFIX}missing — the resolved project root ${root} has no PROJECT-MANIFEST.json; ` +
+      `project parameters fall back to defaults until the file is generated.]`
+  }
+  if (state === "invalid") {
+    return `${MANIFEST_LINE_PREFIX}invalid — ${path} is not a usable declaration: ${(errors ?? []).join("；")}; ` +
+      `project parameters fall back to defaults until fixed.]`
+  }
+  return null // ok / 未知态——无报明行（相位行归 manifestStateLine）
+}
+
 /**
  * ③b 取值前置步（#34——`docs/core/design/MANIFEST.md` §2.6 条 3 · KD-M1-17–M1-19）：数据档
  * mtime 门控重读——盘上 mtime ≠ `agent._manifestMtime`（含缓存未设 = 首次观测）⇒ `readManifest`
@@ -79,7 +116,7 @@ export function manifestStateLine({ phase }) {
  * 沿用上次已知好值，缓存不推进（⇒ 下回合重试，自愈）。路径 = `manifestFilePath(agent.cwd)`
  * （项目根解析与读点同源——KD-M1-18，非「锚目录 + 档名」）；缓存载体 = `agent._manifestMtime`
  * （per-agent——KD-M1-19，同族先例 `agent._slotMtime`）。本步失败只降级注入面（运行期），
- * 与 E2 启动门槛（会话起点）两分——见 §2.5「运行期失败退化 vs 启动门槛」。
+ * 与**会话起点动作**两分——见 §2.5「运行期失败退化 vs 会话起点动作」（本批收正条名）。
  * @param {object} agent 主 agent（`agent.cwd` / `agent.manifest`）
  */
 function refreshManifest(agent) {
@@ -104,26 +141,45 @@ function refreshManifest(agent) {
 
 /**
  * 情境行注入（#28——`docs/core/design/MANIFEST.md` §2.6 模块契约）：manifest 的
- * `phase` 逐回合进模型上下文（判据序 ①–⑥ + 取值前置步 ③b = §2.6 表；#34 起值变由盘面驱动）。**自愈单活体**——
- * 同文活体在 → 幂等（零历史变更）；值变 → 就地摘旧行 + 落新行（保 `history` 数组引用）；
- * 压缩 / 会话重建吞行 → 下一回合重推（不落 system 槽——架构 E5.1 #5，`context.mjs`
- * 压缩面零触碰）。`transient:true` ⇒ 不进人读线（`_fullHistory`）。
- * @param {object} agent 主 agent（`agent.manifest` / `agent.history` / `agent.cwd`——③b 取值）
+ * `phase` 逐回合进模型上下文（判据序 ①–⑥ + 取值前置步 ③b = §2.6 表；#34 起值变由盘面驱动；
+ * 本批 + ③' 状态选行 / 报明行入口）。**自愈单活体**——同文活体在 → 幂等（零历史变更）；值变 →
+ * 就地摘旧行 + 落新行（保 `history` 数组引用）；压缩 / 会话重建吞行 → 下一回合重推（不落 system
+ * 槽——架构 E5.1 #5，`context.mjs` 压缩面零触碰）。`transient:true` ⇒ 不进人读线（`_fullHistory`）。
+ * @param {object} agent 主 agent（`agent.manifest` / `agent.history` / `agent.cwd`——③'/③b）
  * @param {{depth?: number}} [opts] 注入深度（仅 depth-0）
  * @returns {boolean} 是否落新行（测试断言用）
  */
 export function pushManifestStateReminder(agent, { depth = 0 } = {}) {
   if (depth !== 0) return false // ① 仅 depth-0（子代理读任务书——架构 §2.4 M5 零 manifest 读面）
   if (agent.config?.agent?.engineering !== true) return false // ② 模式门：仅工程模式
-  if (!agent.manifest) return false // ③ 无 manifest（normal 路径 / 装配缺失）→ 零注入
-  refreshManifest(agent) // ③b 取值前置步（#34）：mtime 门控重读——行构造须取刷新后的值
+  let line
+  if (!agent.cwd) {
+    // ③ 无锚门（KD-M1-27——**零 I/O / 零报明**）：状态无从解析 ⇒ 沿用内存值（有 ⇒ 相位行；
+    // 无既往好值 ⇒ 零注入）。既有无 cwd 夹具用例零改（§2.6 条 3 边界同源）。
+    if (!agent.manifest) return false
+    line = manifestStateLine({ phase: agent.manifest.phase })
+  } else {
+    // ③' 状态选行（KD-M1-26——**每回合实读**，成本两轴见 §2.6 条 3）：projectView 五态 ⇒ 选行。
+    const view = projectView(agent.cwd)
+    refreshManifest(agent) // ③b 取值前置步（#34）：mtime 门控重读——相位行须取刷新后的值
+    if (view.state === "ok") {
+      const phase = (agent.manifest ?? view.manifest)?.phase
+      line = phase === undefined ? null : manifestStateLine({ phase })
+    } else if (view.state === "no-project" || view.state === "ambiguous") {
+      line = manifestReportLine({ ...view, cwd: resolve(agent.cwd) }) // 本批新报明格（无项目 / 歧义）
+    } else if (agent.manifest) {
+      line = manifestStateLine({ phase: agent.manifest.phase }) // missing / invalid：有既往好值 ⇒ 保守沿用
+    } else {
+      line = manifestReportLine({ ...view, cwd: resolve(agent.cwd) }) // 首观即失败 ⇒ 至少可见一次（KD-M1-26）
+    }
+  }
+  if (!line) return false
   const history = agent.history
-  const line = manifestStateLine({ phase: agent.manifest.phase })
   // ④ 同文 user 行已在（活体）→ 幂等——零历史变更（同文口径 = pushInjections 的 history.some）
   if (history.some((m) => m.content === line)) return false
   // ⑤ 值已变 → 就地 splice 摘旧行（`role === "user"` 全匹配），保 history 数组引用。会话重建后
   //    `_manifestLine` 不随历史回来 → 先按行族前缀从 history 认领现存活体（否则旧行残留 +
-  //    新行入列 = 双活体，违 §2.6 定案「单活体」）。
+  //    新行入列 = 双活体，违 §2.6 定案「单活体」）。相位行 ↔ 报明行**同族前缀**⇒ 互相换位同机制。
   let old = agent._manifestLine
   if (!old) {
     for (const m of history) {

package/agent/setup.mjs

@@ -212,6 +212,12 @@ export async function prepareRun(agent, input, callbacks, {
   // let——下方按 projectRules / skills listing 尾部追加（L326/L331 +=）再赋值；
   // const 声明会 TypeError: Assignment to constant variable（每次 run 必炸）。
   let systemPrompt = base
+  // 派单固块（台账 #23 · AGENT-LOOP-SUBAGENT.md §6.26）：spawn 级固定的机制性指令（批次档路径行 /
+  // 审计模板）随 system 面下发——固块值在 child 生命周期内恒定 ⇒ run 内前缀逐字节稳定（前缀缓存
+  // 不破），且不在 `agent.history` 内 ⇒ 压缩只重建 history（吞不掉）。拼接位 = 槽位装配之后、
+  // 项目指令之前；`_spawnSystemBlock` 为 null/undefined ⇒ 分支不进（depth-0 / explore / plan /
+  // consult 的 system 逐字节同改前）。
+  if (agent._spawnSystemBlock) systemPrompt += `\n\n${agent._spawnSystemBlock}`
 
   // Time injection deliberately does NOT live here: system prompts must be byte-identical
   // across runs (provider prefix caches). The time rides a transient user reminder per turn

package/agent/write-gate.mjs

@@ -10,9 +10,9 @@
  *    展开走 `docRootPaths`）。缺 `docRoot` 键 → `readManifest`
  *    的 fillDefaults 已补默认（架构 §2.3 E2 便利 fallback 落点）；整档缺失 / 非法 JSON →
  *    `{ok:false}` → 回退 DEFAULT_MANIFEST.docRoot（本函数是壳门之下的便利层——E2 的
- *    「整档缺失 → 拒进正常循环」由壳面 requireManifest 在启动期拦（**工程模式会话**口径——
- *    普通会话装配钩子零 manifest I/O，KD-M1-12）：CLI make-agent.mjs / VSC
- *    setup.mjs 均 fail-closed）；读错（权限等）→ 上抛不伪装成缺失（manifest.mjs 契约）。
+ *    「整档缺失」由壳面 requireManifest 按用点处置（判 + 报明 / 建档，**不抛**——
+ *    启动侧恒不拒，KD-M1-25；**工程模式会话**口径——普通会话装配钩子零 manifest I/O，
+ *    KD-M1-12）：CLI make-agent.mjs / VSC setup.mjs 同判）；读错（权限等）→ 上抛不伪装成缺失（manifest.mjs 契约）。
  *    M6 的 `advisor.mjs` design-review 分类分支消费本导出
  *    （KD-M6-1——同源不重复实现；落 dispatch.mjs 会让 advisor 反向 import 门禁簇成环）。
  * 2. `freezeWindowConflict(agent, absPaths)` —— D5 冻结窗口判据组装：被审文件集 =
@@ -37,8 +37,8 @@ const REVIEW_ROOT_KEYS = ["requirements", "specs", "design", "modules", "batches
  * 评审目标解析单点（M4 §2.1#1）：读 manifest `docRoot` → 评审对象 / 被审文件的绝对路径
  * 集合（目录级，反斜杠归一；子键值形态 = 串 | 多根数组，逐键经 `docRootPaths` 展开）。
  * 缺 `docRoot` 键 → readManifest 已补默认；整档缺失 / 非法 →
- * `{ok:false}` → 回退 DEFAULT_MANIFEST.docRoot（便利层——E2 的「拒进正常循环」由壳面
- * requireManifest 在启动期拦（**工程模式会话**口径——KD-M1-12），本函数不重复拦）；
+ * `{ok:false}` → 回退 DEFAULT_MANIFEST.docRoot（便利层——E2 的「整档缺失」由壳面
+ * requireManifest 按用点处置（判 + 报明 / 建档，**不抛**——启动侧恒不拒，KD-M1-25；**工程模式会话**口径——KD-M1-12），本函数不重复拦）；
  * 读错（权限等）→ 上抛 fail-closed。
  * @param {Object} agent
  * @returns {string[]} 评审目标目录的绝对路径（去重）

package/agent-tools/advisor-async.mjs

@@ -1,5 +1,5 @@
 /**
- * advisor-async.mjs — async advisor reviews (AGENT-LOOP-SUBAGENT.md §6.10 — R13, 2026-09-06).
+ * advisor-async.mjs — async advisor reviews (AGENT-LOOP-ASYNC-POOL.md §6.10 — R13, 2026-09-06).
  *
  * The advisor tool runs reviews in a background pool at depth 0 (default async —
  * ruling ②-3 A): the launch returns an ack, the turn ends naturally, the session
@@ -20,7 +20,7 @@
  *  3. the async pool (agent._asyncAdvisors — ADVISOR_POOL_LIMIT = 4 default,
  *     agent.poolLimits.advisor configurable — POOL-CONFIG-UNIFIED; same-scope
  *     running launches are refused at once — never queued (F-5); over-limit +
- *     DIFFERENT scope launches QUEUE (ED-4 2026-09-16 — AGENT-LOOP-SUBAGENT.md §6.10:
+ *     DIFFERENT scope launches QUEUE (ED-4 2026-09-16 — AGENT-LOOP-ASYNC-POOL.md §6.10:
  *     agent._asyncAdvisorQueue, ack {queued, position}, slot release auto-start,
  *     queued cancel dequeue+renumber — the former over-limit refusal ②-6a is
  *     retired); cancel (ruling ②-6b — directed abort → cancelled settle: no
@@ -280,7 +280,7 @@ function relayAdvisorOutput(callbacks, prefix, chunk) {
   }
 }
 
-// ─── ED-4（2026-09-16 · AGENT-LOOP-SUBAGENT.md §6.10）：评审池排队（槽释放自动起跑）────────
+// ─── ED-4（2026-09-16 · AGENT-LOOP-ASYNC-POOL.md §6.10）：评审池排队（槽释放自动起跑）────────
 
 /** 排队出队单点（ED-4）：`_asyncAdvisorQueue` 剔除目标条目 + 余项 position 按 `1..n`
  *  重编号；读面经**载体吸收**（`carrierField`——#21⑤b）：部分 parent（只携池 + `history`）
@@ -368,7 +368,7 @@ export function launchAsyncAdvisor(parent, ctx, launch) {
     const idFields = { type: reviewType, scope: scopeSummary(documents?.length ? documents : paths), round: `${(run?.round ?? 0) + 1}/uncapped`, criterion: "scope-in-flight" }
     return { error: withIdentityLine(`Advisor: 此 scope 已有评审在跑——settle 后逐个发起 — ${scopeNote}; round/prior continuation would be ambiguous while it is in flight — wait for it to settle, then launch the next review.`, idFields) }
   }
-  // ED-4（AGENT-LOOP-SUBAGENT.md §6.10）：池满 + 异 scope ⇒ 排队（非拒）——ack 含 queued +
+  // ED-4（AGENT-LOOP-ASYNC-POOL.md §6.10）：池满 + 异 scope ⇒ 排队（非拒）——ack 含 queued +
   // position；running 计数只算 running 条目（排队不占槽）。原 ②-6a 拒发退役。
   const queued = runningAdvisorCount(parent) >= limit
   parent._asyncAdvisors ??= new Map()