cowork-flow 1.9.2 → 2.0.0

package/CHANGELOG.md

@@ -4,6 +4,27 @@
 
 ### Added
 
+## [2.0.0] - 2026-10-16
+
+### Added
+
+- **编辑期越界警告覆盖 6 宿主（抽共享模块）**：`spec-check` 删除后编辑期只剩 zcode 的 scope 越界提示（其余宿主 `unsupported`），现在把同一语义接到 claude-code / codex / qoder / opencode / dsh——编辑工具落盘后，若活动任务为 `in_progress`/`review` 且被改文件不在其 `implement.jsonl` 白名单内，回**一行** `⚠️ <rel> is outside the task's declared scope. If intended, declare it in the task's `implement.jsonl` (agent-mutable) or revert the edit.`；在范围、无任务、planning/completed、子代理会话、任何异常或超时一律静默——非阻塞、fail-open、全宿主 exit 0。判定逻辑从 `zcode_policy.py` 抽到共享模块 `adapters/host/edit_scope.py`（新增 `extract_edited_paths`：`file_path`/`filePath`/`path` 加 codex `apply_patch` 的 `*** Update File:` 文本，去重保序），zcode 改为引用后对 zcode 实际载荷输出逐字节相同（共享模块语义上是超集：额外识别 `path` 键与 apply_patch 文本路径，zcode 载荷不触发；其既有测试零改动全绿）。**通道**：claude-code / codex / qoder / opencode 走 `inject.py` 的 policy `post_tool_use` 槽（前三个回 `hookSpecificOutput.additionalContext` 信封，opencode 因 `emit_text` 得裸文本并追加到 `tool.execute.after` 的工具输出），dsh 在其 preset 插件的 `tools/post-execute` 里经 Python heredoc 直调共享模块，以 plugin notice 并入 `additionalContexts`。能力声明：`host-assets.json` 六个宿主 `editScopeWarning: plugin`，kimi-code 保持 `unsupported`（宿主丢弃 PostToolUse stdout）；`context-injection.md` 的 Per-edit warning 段同步改写。**迁移**：宿主侧载荷需 `cwf host add <host> --force` 重装（claude-code 的 `.claude/settings.json`、codex 的 `.codex/hooks.json`、qoder 的机器级插件 hooks.json、opencode 与 dsh 的插件文件都在载荷内）。Bash 重定向/tee 写文件仍不在覆盖范围（既有残余缺口）。
+
+### Changed
+
+- **末段裁剪抽成 `_cut_scope_rows`，体积按 Scope 行条数分摊，弱断言用例补强**：`_fit_stage_contract` 回到软预算以内（63 → 45 行），末段裁剪有了独立函数名与边界说明；`room` 由 `budget - len(fixed) - 1` 改为 `(budget - len(fixed) - scope_count) // scope_count`，多条 `Scope:` 前缀行不再"同时被截断又超预算"（单条时与旧式逐字节等价：2050 次逐预算渲染对照、其中 668 次走到末段裁剪，零差异）。复核曾判 `room < len("Scope: ") + 1` 下限与标签守卫行为重叠、可删——实测该结论只对 `0 ≤ room < 8` 成立：`room < 0` 时切片是 `line[:-k]`，从尾部切、前端保留，长条目的标签存活会让守卫放行一个被腰斩且仍超预算的块，下限是唯一拦截者，故保留并补了只能由它单独拦住的红证用例。契约与 docstring 的阈值措辞精确到 `len(fixed) + 9`。测试面：新增多条 Scope 行体积不变量用例，并把 6 条 `shallow_assertion_signal` 软提示一并处置（新用例补 `assertRegex` 钉消费者契约、`SpecEntriesForTaskDevTypeTest` 补 `assertEqual(resolved, …)` 与按 dev-type 所有权过滤后的精确列表），补强后 `review-check` 在该文件零告警。
+- **stage-contract 末段裁剪修复：任务身份与编辑策略优先于预算**：预算极小时末段裁剪原先对整块正文做码点截断，会把开标签一起截掉（实测产出 `<` 或 `<stage-contract task="` 这类半截标签，消费者正则匹配不到，块等于消失），或把 `Gates:` 编辑策略行切成半句（预算 400 实测只剩 `Gates: edit`）。现在末段裁剪只缩短 Scope 行：开标签、闭合标签与 Gates 行在任何预算下完整存活，超长部分由 Scope 行承担；截断若会把 Scope 行的 `Scope: ` 标签本身磨掉（切点落在条目首部空白处），则改回返回整块——宁可超预算，也不产出消费者正则匹配不到的 Scope 行。预算小到连这些固定行都装不下时同样返回整块、允许超过预算（保护行与可解析性优先于预算）。出厂 `budget = 3400` 下该末段不可达，对下游零可见变化——字节对比确认现有全部夹具在该预算下逐字节相同；`context-injection.md` 的 Budget 段与 `_fit_stage_contract` docstring 已写明三条不变量与下限，并新增扫预算可解析性用例与下限用例（各带红证）。
+- **stage-contract 注入容量放宽（Verify 行 10 条 / 块预算 3400 字）**：`Verify:` 行从"渲染 3 条 / 解析 5 条 / 全块 1200 字"放宽到"渲染 10 条 / 解析 10 条 / 全块 3400 字"，让 `decision-anchor.md` 的 `## 验证命令` 段放得下"先读规范再逐条核对改动"的强提醒加真实校验命令，不再静默丢弃第 4 条之后的命令（单条仍截断在 120 字）。三处预算来源同改并互锁：模板 `spec/runtime/scope-rules.json`、`context_paths.DEFAULT_SCOPE_RULES`、`fact_view.STAGE_CONTRACT_VERIFY_LIMIT`/`STAGE_CONTRACT_BUDGET`，新增"默认值↔常量"一致性测试补上第三条断链。`scope-rules.json` 进 `syncPolicy.safeFiles`，已有项目一次普通 `cwf project sync` 即拿到新默认值；代价是该文件的本地调优会在下次 sync 被覆盖（`context-injection.md` 与 `spec-checks.md` 已写明）。降级测试改为钉住自选预算并额外断言输入确实超预算，不再随生产常量漂移（原先升预算会让它们静默恒真）。
+- **kimi-code 裸命令一次装齐（组合组件）**：`kimi-code` 新增组合组件 `all` 并把 default 从 `plugin` 改指它——`cwf host add kimi-code` 一条命令先装上下文注入 hook（config.toml 托管块 + shim + marker），再装插件（sources/managed 两份载荷 + 宿主注册表记录），`cwf host remove kimi-code` 一次卸两者。组合器只做定向旗标剥除：`--force` 自动只达插件段（hook 无该旗标），未知旗标仍原样透传给 installer 报错；显式 `--component plugin` / `--component hook` 的单装语义不变（plugin 单装不写 config.toml）。`host list` 的组件列因此显示 `plugin, hook, all`。`docs/hosts.md` 的宿主表与 Kimi 段改为裸命令主推，升级路径写明 `cwf host add kimi-code --force`。
+
+### Removed
+
+- **spec-check 机制整体删除（破坏性）**：下游正式项目不会手写 `checks:` 声明，规范声明命令 / 编辑期提示 / 收口硬门禁 / doctor 体检被判定为冗余设计，整条链删除。**删除面**：`run spec-check` 命令与两个实现文件（573+178 行）、lifecycle 的 `SPEC-CHECK-PARSE-ERROR` / `SPEC-CHECK-EXECUTOR-ERROR` / `SPEC-CHECK-VIOLATION` / `SPEC-CHECK-UNCHECKED` 四个错误码与豁免构造（`meta.specCheckExempt` / `meta.specCheckSummary` 遥测随之消失）、`--allow-unchecked` 与 `allow_unchecked_specs`、全部宿主的编辑期 spec 提示（zcode 合并提示、claude-code / codex / qoder 的 `PostToolUse` 槽与 hooks.json 声明、opencode `tool.execute.after`、dsh `tools/post-execute`）、doctor 的 `specChecks` 体检、契约 `spec/contracts/spec-checks.md` 与 `SPEC_CHECKS_V1` 契约登记。**保留不动**：zcode 编辑期 scope 越界警告（`edit_scope_warning` 原样，PostToolUse 现在只回这条）、stage-contract 的 Specs 行与 h2 digest 注入、`--allow-missing-evidence` 的 AC 证据豁免链（含 `meta.evidenceExempt` 与打印/归档展示）、`allow_spec_file_modifications`，以及 review 结论的 `clause → command → negativeProof` triple（只删依赖 `checks:` 的措辞）。**契约搬迁**：`spec-checks.md` 的 digest 注入附录并入 `context-injection.md` 的 Specs 段，`spec/` 同步保护前缀与 `safeFiles` 具名例外说明并入 `docs/architecture.md`。**迁移**：`.cowork-flow/scripts/services/spec_check.py` 与 `.cowork-flow/scripts/adapters/cli/spec_check.py` 已登记 `obsoleteFiles`，一次普通 `cwf project sync` 即删除；已装项目里的 `spec/contracts/spec-checks.md` 受 `spec/` 保护前缀保护，sync 会明确报告 `Kept … (protected-path); delete manually if unwanted`，需手动清理；宿主侧载荷需 `cwf host add <host> --force` 重装。已声明 `checks:` 的项目从此失去该门禁——替代信号是 review 阶段既有的"逐条核对用户规范"清单项与 stage-contract 的 Specs 行。
+
+### Fixed
+
+- **注入文本与策略提示指向不存在的命令**：`<stage-contract>` 的 Gates 行尾句写 `self-declared via task context add`、zcode 越界编辑提示写 "add it with `task context add`"，但 CLI 只有 `{next, scope, specs}`（实测 `invalid choice: 'context'`）；`plan-binding.md` 与 `task-adopt.md` 同样引用 `task create` / `task create --from-plan`。这些内部适配器是有意不公开的（`test_context_commands_are_not_public_parser_commands` 锁定，`task_context_commands.py` 写明 public workflow 走 `task next` + 直编 JSONL），所以改文字到真实机制而非接线：Gates 尾句改为 `scope is agent-mutable (declare more in implement.jsonl)`，zcode 提示改为 "declare it in the task's `implement.jsonl`"，契约正文改为 `task next --title … --slug …` 与 `task next --from-plan <path>`。`.cowork-flow/scripts/**` 在 `syncPolicy.safePrefixes` 内，下游一次普通 `cwf project sync` 即生效；受 `spec/` 前缀保护的契约正文仍只对新装项目生效（既有取舍）。
+
 ## [1.9.2] - 2026-10-14
 
 ### Added
@@ -344,7 +365,8 @@
 
 此版本未保留本地条目正文，详情见 [GitHub Release](https://github.com/fishlikewater/cowork-flow/releases/tag/v0.0.47)。
 
-[Unreleased]: https://github.com/fishlikewater/cowork-flow/compare/v1.9.1...HEAD
+[Unreleased]: https://github.com/fishlikewater/cowork-flow/compare/v2.0.0...HEAD
+[2.0.0]: https://github.com/fishlikewater/cowork-flow/compare/v1.9.2...v2.0.0
 [1.9.2]: https://github.com/fishlikewater/cowork-flow/compare/v1.9.1...v1.9.2
 [1.9.1]: https://github.com/fishlikewater/cowork-flow/compare/v1.9.0...v1.9.1
 [1.9.0]: https://github.com/fishlikewater/cowork-flow/compare/v1.8.1...v1.9.0

package/docs/architecture.md

@@ -71,40 +71,7 @@
 
 `config.yaml`、`.developer`、规范、任务和计划按同步策略保护。`--force` 会扩大覆盖范围，因此已有项目应先用 `--dry-run` 查看变更。
 
-## 规范挂命令
-
-项目可以在 `.cowork-flow/spec/` 下的规范文件中声明检查命令。执行器只读取声明，不解析规范正文。
-
-```markdown
----
-checks:
-  - cmd: npm run lint --silent
-    files: "src/"
-    timeout: 60
-    when: both
----
-```
-
-可用字段：
-
-| 字段 | 含义 |
-|---|---|
-| `cmd` | 要执行的命令 |
-| `files` | 目录前缀或扩展名，如 `src/`、`*.ts`；多个值用逗号分隔 |
-| `timeout` | 秒数，默认 30，最长 120 |
-| `when` | `edit`、`lifecycle` 或 `both`，默认 `both` |
-
-唯一执行入口是 `./.cowork-flow/run spec-check`：
-
-| 结果 | 含义 | 是否阻断完成 |
-|---|---|---|
-| `pass` | 命令执行成功 | 否 |
-| `violation` | 命令执行失败且有违规 | 是 |
-| `unchecked` | 命令缺失、解释器缺失或超时 | 是，需显式放行 |
-
-`when: edit` 是编辑期提示，超时上限为 2.5 秒，不代替收口检查。收口阶段会执行全部声明，并把结果写入任务记录。
-
-模板不预置生效的项目检查命令，因为模板无法知道目标项目使用什么工具。需要检查时，在项目自己的 `spec/` 文件中声明。完整契约见 `.cowork-flow/spec/contracts/spec-checks.md`。
+`.cowork-flow/spec/` 前缀整体受同步保护：既有项目里的规范文件不会被 `sync` 覆盖，模板侧的规范更新只对全新 `init` 生效。具名例外是 `spec/runtime/host-assets.json` 中 `syncPolicy.safeFiles` 列出的文件——`spec/contracts/workflow-state-templates.md` 与 `spec/runtime/scope-rules.json`——它们随 `sync` 更新，使契约勘误与预算默认值能到达已装项目；代价是本地调过 `scope-rules.json` 的项目会在下一次 `sync` 丢掉这些改动。
 
 ## 扩展规则
 

package/docs/direction.md

@@ -45,7 +45,7 @@
 
 ## 5. 版本线
 
-- **1.8.x 已发布**：证据化完成（AC 事实化、`evidence.jsonl`、完成门禁）与 spec-check 采纳闭环。
+- **1.8.x 已发布**：证据化完成（AC 事实化、`evidence.jsonl`、完成门禁）。
 - **1.9.0 主线已实现，待发布**：多执行者协作事实——看板归属可见、依赖边、交接凭证。详见 [CHANGELOG](../CHANGELOG.md) 的 `[Unreleased]` 段。
 - 各版本的交付明细一律以 CHANGELOG 为准，本文不重复。
 

package/docs/hosts.md

@@ -19,7 +19,7 @@
 | ZCode | 需要 | `cwf host add zcode` |
 | Qoder | 需要 | `cwf host add qoder` |
 | DeepSeek Harness | 需要 | `cwf host add dsh` |
-| Kimi Code | 工作流注入需要 hook；全局插件可选 | `cwf host add kimi-code --component hook` |
+| Kimi Code | 需要 | `cwf host add kimi-code`（一条命令装齐 hook 与插件） |
 
 ## 通用命令
 
@@ -159,23 +159,27 @@ hook 行是否进入 agent 提示按版本分线：实测 DSH 0.1.1-rc.1 不收
 
 ## Kimi Code
 
-工作流状态注入使用 hook 组件：
+裸命令一次装齐两部分：先装上下文注入 hook（必需），再装插件：
 
 ```bash
-cwf host add kimi-code --component hook
-cwf host remove kimi-code --component hook
+cwf host add kimi-code
+cwf host remove kimi-code
 ```
 
-安装或更新后重载配置或新开会话。该组件总是重写自己的 hook 区块，不接受 `--force`。
+安装或更新后重载配置或新开会话。hook 组件总是重写自己的 hook 区块，不写插件；插件组件在未初始化项目中提供全局引导技能。单独安装某一半时用 `--component`：
 
-如果还需要在未初始化项目中提供全局引导技能，可以另外安装插件：
+```bash
+cwf host add kimi-code --component plugin
+cwf host add kimi-code --component hook
+```
+
+hook 组件不接受 `--force`（它总是接管重写自己的区块）；裸命令里的 `--force` 只作用于插件段：
 
 ```bash
-cwf host add kimi-code
-cwf host remove kimi-code
+cwf host add kimi-code --force
 ```
 
-命令会物化到 `$KIMI_CODE_HOME/plugins/sources/cowork-flow/`（稳定重装源）与 `$KIMI_CODE_HOME/plugins/managed/cowork-flow/`（宿主加载的副本），并直接写入宿主的插件注册表 `$KIMI_CODE_HOME/plugins/installed.json`，与 Kimi Code 自身的安装落盘格式一致。重启 Kimi Code 即生效，无需在 TUI 中手工安装。卸载会反向清理两份目录与注册记录。
+插件会物化到 `$KIMI_CODE_HOME/plugins/sources/cowork-flow/`（稳定重装源）与 `$KIMI_CODE_HOME/plugins/managed/cowork-flow/`（宿主加载的副本），并直接写入宿主的插件注册表 `$KIMI_CODE_HOME/plugins/installed.json`，与 Kimi Code 自身的安装落盘格式一致。重启 Kimi Code 即生效，无需在 TUI 中手工安装。卸载会反向清理两份目录与注册记录。
 
 ## MCP 客户端接入
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cowork-flow",
-  "version": "1.9.2",
+  "version": "2.0.0",
   "description": "CLI for installing and maintaining cowork-flow collaboration templates.",
   "keywords": [
     "ai-agent",

package/presets/claude-code/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "cowork-flow",
-  "version": "1.9.2",
+  "version": "2.0.0",
   "description": "AI 协作工作流引擎：任务生命周期、子代理调度、门禁与状态注入。将 cowork-flow 的完整工作流带入 Claude Code。",
   "displayName": "Cowork Flow",
   "author": {

package/presets/codex/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "cowork-flow",
-  "version": "1.9.2",
+  "version": "2.0.0",
   "description": "AI 协作工作流引擎：任务生命周期、子代理调度、门禁与状态注入。将 cowork-flow 的完整工作流带入 Codex。",
   "author": {
     "name": "fishlikewater",

package/presets/dsh/plugins/workflow-state.js

@@ -17,6 +17,11 @@
 // the text is byte-stable, so the static prompt prefix
 // stays cacheable.
 //
+// It also carries the editor-phase scope advisory on the finished tool
+// result (`tools/post-execute`): one line when an edited file is outside
+// the active task's declared scope, silent otherwise. The tool already
+// ran, so the notice only decorates the next request and never blocks.
+//
 // Degradation is silent: no `.cowork-flow` root, a missing
 // Python, a broken runtime, or the `COWORK_FLOW_HOOKS=0` /
 // `COWORK_FLOW_DISABLE_HOOKS=1` switches all yield an
@@ -97,14 +102,19 @@ const EDIT_EXEC_OPTIONS = {
   maxBuffer: 1024 * 1024,
 };
 
-// Editor-phase spec-check protocol: same root discovery,
-// then the shared edit-check entry so DSH sessions receive
-// the single-line violation hint the other hosts get from
-// their PostToolUse hook. Always exits 0.
-const PYTHON_EDIT_PROTOCOL = `\
+// Editor-phase scope protocol: same root discovery, then the shared
+// edit-scope entry the other hosts reach through their PostToolUse
+// hook, so DSH sessions get the identical single-line advisory. Prints
+// at most one line; exits 0 either way.
+const PYTHON_EDIT_SCOPE_PROTOCOL = `\
 import sys
 from pathlib import Path
 
+# The advisory line starts with a character outside the Windows ANSI
+# codepage (the warning sign), so stdout must be UTF-8 regardless of the
+# console: otherwise the print raises and the warning is swallowed.
+sys.stdout.reconfigure(encoding="utf-8", errors="replace", newline="")
+
 cwd = sys.argv[1]
 file_path = sys.argv[2]
 current = Path(cwd).resolve()
@@ -120,8 +130,13 @@ if root is None:
     raise SystemExit(0)
 sys.path.insert(0, str(root / ".cowork-flow" / "scripts"))
 try:
-    from services.spec_check import run_edit_checks
-    print(run_edit_checks(root, file_path))
+    from adapters.host.edit_scope import edit_scope_warning
+    print(edit_scope_warning(root, {
+        "cwd": cwd,
+        "hook_event_name": "PostToolUse",
+        "tool_name": "Write",
+        "tool_input": {"file_path": file_path},
+    }))
 except Exception:
     pass
 `;
@@ -305,12 +320,12 @@ export function editedFilePath(exec) {
 
 
 /**
- * Editor-phase spec check for one edited file. Returns the
+ * Editor-phase scope check for one edited file. Returns the
  * single-line warning, or '' when there is nothing to say:
- * no root, no interpreter, no declaration, a clean run, or
+ * no root, no interpreter, no active task, a clean run, or
  * a timeout. Never throws.
  */
-export async function runEditSpecCheck(cwd, filePath) {
+export async function runEditScopeCheck(cwd, filePath) {
   if (hooksDisabled() || !cwd || !filePath) {
     return '';
   }
@@ -321,7 +336,7 @@ export async function runEditSpecCheck(cwd, filePath) {
   const attempt = (candidate) => new Promise((resolvePromise) => {
     execFile(
       candidate.command,
-      [...candidate.args, '-c', PYTHON_EDIT_PROTOCOL, cwd, filePath],
+      [...candidate.args, '-c', PYTHON_EDIT_SCOPE_PROTOCOL, cwd, filePath],
       EDIT_EXEC_OPTIONS,
       (error, stdout) => {
         if (error) {
@@ -357,7 +372,7 @@ export async function runEditSpecCheck(cwd, filePath) {
  * preset deliberately does not import, so the shape is
  * built here with node's uuid.
  */
-function specNoticeMessage(text) {
+function noticeMessage(text) {
   return {
     id: randomUUID(),
     role: 'user',
@@ -366,7 +381,7 @@ function specNoticeMessage(text) {
       kind: 'plugin',
       plugin: 'cowork-flow',
       form: 'notice',
-      summary: 'spec-check',
+      summary: 'edit-scope',
     },
   };
 }
@@ -430,7 +445,7 @@ export function apply(ctx) {
     refresh(agent, false);
   });
 
-  // Editor-phase spec-check: the tool already ran, so this
+  // Editor-phase scope check: the tool already ran, so this
   // only adds context for the next request and never blocks
   // the call. The waterfall awaits next() first.
   ctx.on('tools/post-execute', async (exec, _result, next) => {
@@ -442,7 +457,7 @@ export function apply(ctx) {
     }
     let warning = '';
     try {
-      warning = await runEditSpecCheck(agent.cwd, filePath);
+      warning = await runEditScopeCheck(agent.cwd, filePath);
     } catch {
       warning = '';
     }
@@ -450,7 +465,7 @@ export function apply(ctx) {
       return downstream;
     }
     const contexts = [
-      specNoticeMessage(warning),
+      noticeMessage(warning),
       ...((downstream && downstream.additionalContexts) || []),
     ];
     if (downstream && downstream.kind === 'block') {

package/presets/kimi-code/.kimi-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "cowork-flow",
-  "version": "1.9.2",
+  "version": "2.0.0",
   "description": "AI 协作工作流引擎：任务生命周期、子代理调度、门禁与状态注入。将 cowork-flow 的完整工作流带入 Kimi Code。",
   "author": {
     "name": "fishlikewater",

package/presets/opencode/cowork-flow/plugin-core.js

@@ -1,11 +1,11 @@
 // Transport shim behind the opencode plugin. Every workflow fact
 // (contract digest, workflow-state, decision anchor, stage contract,
-// runtime-context bind) is rendered by the Python source
-// <scripts>/adapters/host/inject.py --host opencode; this module moves
-// bytes only. What stays here is what the Python side cannot reach:
-// the config-hook skills registration, the shell.env context-key
-// export, and the edit-phase spec-check the tool.execute.after hook
-// delegates to the project runtime.
+// runtime-context bind, edit-scope warning) is rendered by the Python
+// source <scripts>/adapters/host/inject.py --host opencode; this module
+// moves bytes only. What stays here is what the Python side cannot
+// reach: the config-hook skills registration, the shell.env context-key
+// export, and the tool-shape translation for the tool.execute.after
+// edit-scope delegation.
 //
 // This module must NOT live under plugins/: opencode
 // treats every file directly inside plugins/ as a plugin
@@ -175,8 +175,9 @@ function runInject(candidate, script, payload) {
 // inject.py and hand back whatever it printed. The payload spreads the
 // host input so every session/runtime-context key the Python identity
 // table knows arrives unchanged; hook_event_name and cwd are the two
-// fields the hook contract requires.
-async function renderViaInject(input) {
+// fields the hook contract requires. `overrides` swaps the event name
+// and adds the tool fields the PostToolUse contract needs.
+async function renderViaInject(input, overrides = null) {
   if (
     process.env.COWORK_FLOW_HOOKS === "0" ||
     process.env.COWORK_FLOW_DISABLE_HOOKS === "1"
@@ -188,9 +189,11 @@ async function renderViaInject(input) {
   if (!script) {
     return ""
   }
+  const extra = overrides && typeof overrides === "object" ? overrides : {}
   const payload = {
     ...(input && typeof input === "object" ? input : {}),
-    hook_event_name: "UserPromptSubmit",
+    ...extra,
+    hook_event_name: extra.hook_event_name || "UserPromptSubmit",
     cwd: inputCwd(input) || (root === pluginRoot ? null : root) || process.cwd(),
   }
   for (const candidate of pythonCandidates()) {
@@ -203,6 +206,34 @@ async function renderViaInject(input) {
   return ""
 }
 
+// Editor-phase scope warning: opencode sessions get the same
+// single-line out-of-scope advisory the other hosts receive on
+// PostToolUse. Best-effort — a missing runtime, a timeout, or any
+// error stays silent and never blocks the edit that already happened.
+const EDIT_TOOL_NAMES = new Set(["edit", "write"])
+
+function editedFilePath(input) {
+  const tool = typeof input?.tool === "string" ? input.tool : ""
+  if (!EDIT_TOOL_NAMES.has(tool)) {
+    return ""
+  }
+  const args = input?.args
+  const candidate = args && typeof args === "object" ? args.filePath : null
+  return typeof candidate === "string" && candidate.trim() ? candidate.trim() : ""
+}
+
+async function renderEditScopeWarning(input) {
+  const filePath = editedFilePath(input)
+  if (!filePath) {
+    return ""
+  }
+  return renderViaInject(input, {
+    hook_event_name: "PostToolUse",
+    tool_name: typeof input?.tool === "string" ? input.tool : "edit",
+    tool_input: { file_path: filePath },
+  })
+}
+
 function sanitize(value) {
   return String(value ?? "")
     .trim()
@@ -262,82 +293,6 @@ function injectShellEnv(input, output) {
   }
 }
 
-// Editor-phase spec-check: opencode sessions get the same
-// single-line violation hint zcode and claude-code
-// receive. Best-effort — a missing runtime, a timeout, or
-// any error stays silent and never blocks the edit that
-// already happened.
-const EDIT_TOOL_NAMES = new Set(["edit", "write"])
-const EDIT_CHECK_TIMEOUT_MS = 2500
-
-function editedFilePath(input) {
-  const tool = typeof input?.tool === "string" ? input.tool : ""
-  if (!EDIT_TOOL_NAMES.has(tool)) {
-    return ""
-  }
-  const args = input?.args
-  const candidate = args && typeof args === "object" ? args.filePath : null
-  return typeof candidate === "string" && candidate.trim() ? candidate.trim() : ""
-}
-
-function runEditSpecCheck(root, filePath) {
-  return new Promise((resolvePromise) => {
-    let settled = false
-    const finish = (value) => {
-      if (!settled) {
-        settled = true
-        resolvePromise(value)
-      }
-    }
-    const entry = resolve(
-      root,
-      DIR_WORKFLOW,
-      process.platform === "win32" ? "run.cmd" : "run"
-    )
-    if (!existsSync(entry)) {
-      finish("")
-      return
-    }
-    let child
-    try {
-      child = spawn(
-        entry,
-        ["spec-check", "--phase", "edit", "--file", filePath, "--throttled"],
-        {
-          cwd: root,
-          stdio: ["ignore", "pipe", "ignore"],
-          shell: process.platform === "win32",
-        }
-      )
-    } catch {
-      finish("")
-      return
-    }
-    const timer = setTimeout(() => {
-      try {
-        child.kill()
-      } catch {
-        // the edit must not be held up by a stuck checker
-      }
-      finish("")
-    }, EDIT_CHECK_TIMEOUT_MS)
-    let stdout = ""
-    if (child.stdout) {
-      child.stdout.on("data", (chunk) => {
-        stdout += String(chunk)
-      })
-    }
-    child.on("error", () => {
-      clearTimeout(timer)
-      finish("")
-    })
-    child.on("close", () => {
-      clearTimeout(timer)
-      finish(stdout.trim())
-    })
-  })
-}
-
 // The payload's own skills directory, located from this
 // module's file path and not from the repository root: the
 // machine install puts this file in
@@ -382,11 +337,11 @@ export function registerPayloadSkills(config) {
 
 // The plugin adapter imports the hook helpers; these are
 // the unit-test surface (transport, fail-open, shell env,
-// edit-phase delegation). opencode never reads this module.
+// edit-scope delegation). opencode never reads this module.
 export {
   renderViaInject,
   editedFilePath,
+  renderEditScopeWarning,
   findRepoRoot,
   injectShellEnv,
-  runEditSpecCheck,
 }

package/presets/opencode/plugins/cowork-flow.js

@@ -7,12 +7,10 @@
 // re-exported helper would be called as a plugin and break
 // host bootstrap.
 import {
-  editedFilePath,
-  findRepoRoot,
   injectShellEnv,
   registerPayloadSkills,
-  renderViaInject,
-  runEditSpecCheck
+  renderEditScopeWarning,
+  renderViaInject
 } from "../cowork-flow/plugin-core.js"
 
 export const CoworkFlowPlugin = async () => {
@@ -37,12 +35,12 @@ export const CoworkFlowPlugin = async () => {
         output.system.push(text)
       }
     },
+    // Editor-phase scope advisory: the tool already ran, so
+    // the single out-of-scope line is appended to its output
+    // and the call is never blocked. Non-edit tools and a
+    // missing/failing runtime stay silent.
     "tool.execute.after": async (input, output) => {
-      const filePath = editedFilePath(input)
-      if (!filePath) {
-        return
-      }
-      const warning = await runEditSpecCheck(findRepoRoot(input), filePath)
+      const warning = await renderEditScopeWarning(input)
       if (warning) {
         output.output = [output.output, warning].filter(Boolean).join("\n")
       }

package/presets/qoder/.qoder-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "cowork-flow",
-  "version": "1.9.2",
+  "version": "2.0.0",
   "description": "AI 协作工作流引擎：任务生命周期、子代理调度、门禁与状态注入。将 cowork-flow 的完整工作流带入 Qoder。",
   "displayName": "Cowork Flow",
   "author": {

package/presets/qoder/hooks/hooks.json

@@ -41,7 +41,7 @@
               "${QODER_PLUGIN_ROOT}/hooks/inject-context.mjs"
             ],
             "timeout": 30,
-            "statusMessage": "cowork-flow: 规范自查"
+            "statusMessage": "cowork-flow: 编辑越界自查"
           }
         ]
       }

package/presets/zcode/.zcode-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "cowork-flow",
-  "version": "1.9.2",
+  "version": "2.0.0",
   "description": "AI 协作工作流引擎：任务生命周期、子代理调度、门禁与状态注入。将 cowork-flow 的完整工作流带入 ZCode。",
   "author": {
     "name": "fishlikewater",

package/src/commands/host.js

@@ -13,6 +13,8 @@ import { runInstallOpenCodePlugin, FLAGS as OPENCODE_PLUGIN_FLAGS } from './inst
 import { runInstallQoderPlugin, FLAGS as QODER_PLUGIN_FLAGS } from './install-qoder-plugin.js';
 import { runInstallZCodePlugin, FLAGS as ZCODE_PLUGIN_FLAGS } from './install-zcode-plugin.js';
 
+const KIMI_ALL_FLAGS = [...new Set([...KIMI_HOOK_FLAGS, ...KIMI_PLUGIN_FLAGS])].sort();
+
 
 // Which machine-level integrations a host has.
 // Deliberately not part of host-assets.json: that manifest
@@ -58,10 +60,11 @@ export const HOST_COMPONENTS = {
     }
   },
   'kimi-code': {
-    default: 'plugin',
+    default: 'all',
     components: {
       plugin: { summary: 'Kimi Code plugin: the bootstrap Skill it loads at session start', flags: KIMI_PLUGIN_FLAGS, run: runInstallKimiPlugin },
-      hook: { summary: 'Kimi Code context-injection hook as a user-level config.toml [[hooks]] row', flags: KIMI_HOOK_FLAGS, run: runInstallKimiHook }
+      hook: { summary: 'Kimi Code context-injection hook as a user-level config.toml [[hooks]] row', flags: KIMI_HOOK_FLAGS, run: runInstallKimiHook },
+      all: { summary: 'Kimi Code hook plus plugin, installed in one command (the default)', flags: KIMI_ALL_FLAGS, run: runInstallKimiAll }
     }
   }
 };
@@ -78,6 +81,24 @@ export const HOST_FLAGS = [...new Set(
 )].sort();
 
 
+function withoutForceFlag(args) {
+  return args.filter((arg) => arg !== '--force' && !arg.startsWith('--force='));
+}
+
+
+// kimi-code's default component: the hook (injection, the
+// required half) first, then the plugin, in one command.
+// Both installers stay the only validators — unknown flags
+// pass through untouched and are rejected by whichever
+// installer reaches them — but `--force` cannot: the hook
+// has no such flag, so the combined path strips it for the
+// hook segment only, and the plugin still receives it.
+async function runInstallKimiAll(args) {
+  await runInstallKimiHook(withoutForceFlag(args));
+  await runInstallKimiPlugin(args);
+}
+
+
 function resolveHost(token) {
   const id = hostRegistry.platformIdFor(token);
   if (id === null) {

package/src/commands/registry.js

@@ -41,9 +41,11 @@ const HOST_NOTE = `Hosts: ${Object.entries(HOST_COMPONENTS)
   .join('; ')}.`;
 // The union across hosts contains one gap: kimi-code's
 // hook has no --force, so the help names it instead of
-// letting the user hit a usage error.
+// letting the user hit a usage error. kimi-code's default
+// component routes --force to the plugin segment only.
 const HOST_FORCE_NOTE = '`--force` applies to every component except kimi-code\'s hook, '
-  + 'which overwrites unconditionally and therefore does not accept the flag.';
+  + 'which overwrites unconditionally and therefore does not accept the flag; '
+  + 'kimi-code\'s default component consumes it for the plugin only.';
 
 export const COMMANDS = [
   {

package/template/.cowork-flow/.version

@@ -1 +1 @@
-1.9.2
+2.0.0

package/template/.cowork-flow/adapters/claude-code/adapter.yaml

@@ -13,7 +13,7 @@ capabilities:
   runtimeContextDispatch: native
   runtimeContextBinding: shim
   runtimeContextCleanup: native
-  editScopeWarning: unsupported
+  editScopeWarning: plugin
 dispatch:
   primitive: subagent
   agentsPath: .claude/agents

package/template/.cowork-flow/adapters/codex/adapter.yaml

@@ -13,7 +13,7 @@ capabilities:
   runtimeContextDispatch: native
   runtimeContextBinding: shim
   runtimeContextCleanup: native
-  editScopeWarning: unsupported
+  editScopeWarning: plugin
 dispatch:
   primitive: spawn_agent
   forkTurns: none

package/template/.cowork-flow/adapters/dsh/adapter.yaml

@@ -13,7 +13,7 @@ capabilities:
   runtimeContextDispatch: native
   runtimeContextBinding: shim
   runtimeContextCleanup: shim
-  editScopeWarning: unsupported
+  editScopeWarning: plugin
 dispatch:
   primitive: subagent
   memoryPath: AGENTS.md

package/template/.cowork-flow/adapters/opencode/adapter.yaml

@@ -13,7 +13,7 @@ capabilities:
   runtimeContextDispatch: native
   runtimeContextBinding: shim
   runtimeContextCleanup: native
-  editScopeWarning: unsupported
+  editScopeWarning: plugin
 dispatch:
   primitive: task
   agentsPath: .opencode/agents