cowork-flow 2.1.0 → 2.3.0

package/CHANGELOG.md

@@ -4,6 +4,27 @@
 
 ### Added
 
+## [2.3.0] - 2026-10-21
+
+### Added
+
+- **`cwf project init` 宿主自动判定与 `--host` 主旗标**：省略 `--host` 时先按项目已有的宿主标记（与 `project sync` 同一套探测）判定，交互终端再回退到选择器；`--host` 可重复/逗号分隔，`--platform`、`--platforms` 保留为兼容别名。非交互且探测为空时仍明确报 `Host selection required`，不静默猜宿主。
+
+### Changed
+
+- **`--developer` 省略时从 git 身份就近取值**：顺序为已有 `.developer` > 显式参数 > `git config user.name`（已有身份不被覆盖；初次运行会标注 `(from git user.name)`）；无 git 身份时交互终端提示、非交互仍报错，`--dry-run` 只报告 `would-skip` 不失败。`project init` / `project sync` 的输出行由 `Platforms:` 改为 `Hosts:`。
+
+### Fixed
+
+- **bootstrap 技能在非 TTY 下初始化失败**：六份共享的 `cowork-flow-bootstrap` 技能改为提示 agent 传入所在宿主（`npx cowork-flow project init --host <host>`），不再依赖交互选择器或位置参数 `.`，AI 宿主/CI 可直接完成初始化；六份载荷保持字节一致。
+
+## [2.2.0] - 2026-10-20
+
+### Changed
+
+- **计划与任务验证段纳入规范门禁检查**：`task-planning` 的计划 `Final Verification`、任务规则与 Self-Review 要求按 `dev_type` 逐条核对 `.cowork-flow/spec/<dev_type>/` 适用规范与项目门禁——改动被规范覆盖时，把决定命令或 `规范核对:` 行写进计划的 Final Verification 与任务简报的 Verification Command，标 `pass` / `not_applicable` 并写理由；`decision-anchor` 契约的 `## 验证命令` 同步要求该检查行，并明确为 review 强提醒而非 `spec-check` 硬门禁，120 字符/10 行限制不变。
+- **模板示例统一展示规范核对行**：`decision-anchor` Schema 的 `## 验证命令` 示例新增 `规范核对:` 行；`task-planning` 任务简报的 `Verification Command` 示例块后补充写法说明，避免新建计划/任务漏写规范检查项。
+
 ## [2.1.0] - 2026-10-19
 
 ### Added
@@ -386,7 +407,9 @@
 
 此版本未保留本地条目正文，详情见 [GitHub Release](https://github.com/fishlikewater/cowork-flow/releases/tag/v0.0.47)。
 
-[Unreleased]: https://github.com/fishlikewater/cowork-flow/compare/v2.1.0...HEAD
+[Unreleased]: https://github.com/fishlikewater/cowork-flow/compare/v2.3.0...HEAD
+[2.3.0]: https://github.com/fishlikewater/cowork-flow/compare/v2.2.0...v2.3.0
+[2.2.0]: https://github.com/fishlikewater/cowork-flow/compare/v2.1.0...v2.2.0
 [2.1.0]: https://github.com/fishlikewater/cowork-flow/compare/v2.0.0...v2.1.0
 [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

package/README.en.md

@@ -50,25 +50,33 @@ below with `npx cowork-flow` — except for `cwf self update`.
 Preview the files that will be written:
 
 ```bash
-cwf project init . --platform codex --developer alice --dry-run
+cwf project init --host codex --developer alice --dry-run
 ```
 
 Drop `--dry-run` once the list looks right:
 
 ```bash
-cwf project init . --platform codex --developer alice
+cwf project init --host codex --developer alice
 ```
 
 Replace `codex` with the host you use:
 
 `codex`, `claude-code`, `opencode`, `zcode`, `qoder`, `kimi-code`, `dsh`.
 
-For a new project, replace `.` with `./my-project` and enter that directory. Use
-`--platform all` only when the project really will be worked on from several hosts.
+The command initializes the current directory by default. For a new project, pass the
+target directory as a positional argument, for example
+`cwf project init ./my-project --host codex`, then enter that directory. When `--host`
+is omitted, init first looks for host markers already in the project (such as
+`.codex/` or `.claude/`); an interactive terminal offers a picker when none is found,
+and a non-interactive environment needs an explicit host. Use `--host all` only when
+the project really will be worked on from several hosts.
 
 Initialization adds `AGENTS.md`, `.cowork-flow/`, and the matching host files. It does
-not touch application code. `--developer` is optional; on an existing project, always
-run `--dry-run` first.
+not touch application code. An existing `.developer` is never overwritten; on first
+initialization an explicit `--developer` wins over `git config user.name`. With no git
+identity, an interactive terminal prompts and a non-interactive run fails (`--dry-run`
+only reports `would-skip`). `--platform` / `--platforms` remain accepted aliases of
+`--host`. On an existing project, always run `--dry-run` first.
 
 ### 3. Finish host setup
 
@@ -135,7 +143,7 @@ how the project is organized, see [architecture and extension](docs/architecture
 
 | Command | Purpose |
 |---|---|
-| `cwf project init [target] --platform <host> [--developer <name>] [--dry-run] [--force]` | Initialize a project |
+| `cwf project init [target] --host <host> [--developer <name>] [--dry-run] [--force]` | Initialize a project |
 | `cwf project sync [target] [--dry-run] [--force]` | Update the cowork-flow-managed files in a project |
 | `cwf host add <host> [--component <name>] [--dry-run] [--force] [--prune-old] [--uninstall]` | Install a machine-level host component |
 | `cwf host remove <host> [--component <name>] [--dry-run] [--force]` | Remove a machine-level host component |

package/README.md

@@ -44,22 +44,22 @@ cwf --version
 先预览将要写入的文件：
 
 ```bash
-cwf project init . --platform codex --developer alice --dry-run
+cwf project init --host codex --developer alice --dry-run
 ```
 
 确认无误后去掉 `--dry-run`：
 
 ```bash
-cwf project init . --platform codex --developer alice
+cwf project init --host codex --developer alice
 ```
 
 把 `codex` 换成你正在使用的宿主：
 
 `codex`、`claude-code`、`opencode`、`zcode`、`qoder`、`kimi-code`、`dsh`。
 
-新项目可以把 `.` 换成 `./my-project`，然后进入该目录。只有确实会在多个宿主中使用时，才需要 `--platform all`。
+命令默认在当前目录初始化；新项目把目标目录作为位置参数传入，例如 `cwf project init ./my-project --host codex`，再进入该目录。省略 `--host` 时，会先按项目里已有的宿主标记（如 `.codex/`、`.claude/`）自动判定；没有标记的交互终端会让你选择，非交互环境则需要显式传入。只有确实会在多个宿主中使用时，才用 `--host all`。
 
-初始化会加入 `AGENTS.md`、`.cowork-flow/` 和对应的宿主文件，不会修改业务代码。`--developer` 可以省略；已有项目建议始终先跑 `--dry-run`。
+初始化会加入 `AGENTS.md`、`.cowork-flow/` 和对应的宿主文件，不会修改业务代码。已有 `.developer` 不会被覆盖；首次初始化时显式 `--developer` 优先于 `git config user.name`。git 也没有身份时，交互终端会提示，非交互环境报错（`--dry-run` 只报告 `would-skip`，不失败）。`--platform` / `--platforms` 是 `--host` 的兼容别名。已有项目建议始终先跑 `--dry-run`。
 
 ### 3. 完成宿主设置
 
@@ -117,7 +117,7 @@ cwf project sync .
 
 | 命令 | 用途 |
 |---|---|
-| `cwf project init [target] --platform <host> [--developer <name>] [--dry-run] [--force]` | 初始化项目 |
+| `cwf project init [target] --host <host> [--developer <name>] [--dry-run] [--force]` | 初始化项目 |
 | `cwf project sync [target] [--dry-run] [--force]` | 更新项目内由 cowork-flow 管理的文件 |
 | `cwf host add <host> [--component <name>] [--dry-run] [--force] [--prune-old] [--uninstall]` | 安装机器级宿主组件 |
 | `cwf host remove <host> [--component <name>] [--dry-run] [--force]` | 卸载机器级宿主组件 |

package/docs/direction.md

@@ -52,7 +52,7 @@
 
 ## 6. 待决项与缓行
 
-- **待维护者拍板：中文面文档是否英文化 / 双语。** 英文社区是 spec-driven development 讨论的主场，与 `AGENTS.md` 的「文档语言：中文」约定冲突，需单独立项评估；契约与英文版 README 已先行英文化（`5f602c0`），待决收窄为 `docs/`、`template/AGENTS.md`、`CHANGELOG.md`。
+- **已拍板（2026-10-21）：详细文档维持中文，README 保持中英双语。** 英文社区是 spec-driven development 讨论的主场，但当前详细文档约 590 行、随 npm 以纯 Markdown 发布，全量双语会引入翻译漂移与文档框架成本。决定：`docs/`、`template/AGENTS.md`、`CHANGELOG.md` 维持中文；`README.md` / `README.en.md` 双语同步；不引入 VuePress/mkdocs 或目录式双语。未来若英文需求被证实，采用并列 `docs/*.en.md`，只覆盖安装面文档，并新增“英文文件与中文源文件标题集合一致”的漂移门禁后再落地。
   - 2026-10-13 澄清：「文档语言：中文」约束的是下游宿主工作时**产出文档**的语言，不要求把随包分发的产品载荷（`template/skills/`、`template/.cowork-flow/spec/contracts/`、`presets/`）翻译成中文。
 - **维持缓行**：MCP 写工具（须先重开 `fact-layer-access` 契约）、新宿主接入、自创跨 agent 协议。
 - **观察项（触发条件已到）**：机器可解析 AC 是与 Spec Kit / OpenSpec 互操作的第一块砖（spec 制品 ↔ decision-anchor 映射），符合「SDD 工具之下的状态层」定位。原定「待 agent-teams 排期落定后议」，而 1.9.0 多执行者协作主线已实现，可排入讨论。

package/docs/hosts.md

@@ -9,7 +9,9 @@
 | 项目级文件 | 当前项目的 `AGENTS.md`、`.cowork-flow/` 和宿主目录 | `cwf project init` / `cwf project sync` |
 | 机器级组件 | 宿主的用户配置目录，如插件、预设或 hook | `cwf host add` / `cwf host remove` |
 
-每个项目至少需要执行一次 `cwf project init`。是否需要 `cwf host add`，取决于宿主：
+每个项目至少需要执行一次 `cwf project init`。省略 `--host` 时，init 先按项目里已有的宿主标记（如 `.codex/`、`.claude/`）自动判定，与 `cwf project sync` 使用同一套探测；没有标记的交互终端会给出选择器，非交互环境则必须显式传 `--host`。`--platform` / `--platforms` 仍是兼容别名。
+
+是否需要 `cwf host add`，取决于宿主：
 
 | 宿主 | 初始化后是否需要机器级组件 | 建议命令 |
 |---|---|---|

package/package.json

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

package/presets/claude-code/skills/cowork-flow-bootstrap/SKILL.md

@@ -17,10 +17,12 @@ workflow entry `./.cowork-flow/run`).
 
 ## No runtime: offer the install
 
-Tell the user this repository has no cowork-flow runtime, then offer:
+Tell the user this repository has no cowork-flow runtime, then offer (replace
+`<host>` with the host you are running in: `codex`, `claude-code`, `opencode`,
+`zcode`, `qoder`, `kimi-code`, or `dsh`):
 
 ```bash
-npx cowork-flow project init .
+npx cowork-flow project init --host <host>
 ```
 
 After init the project carries its own Skills (`.agents/skills/`), the task

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

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

package/presets/codex/skills/cowork-flow-bootstrap/SKILL.md

@@ -17,10 +17,12 @@ workflow entry `./.cowork-flow/run`).
 
 ## No runtime: offer the install
 
-Tell the user this repository has no cowork-flow runtime, then offer:
+Tell the user this repository has no cowork-flow runtime, then offer (replace
+`<host>` with the host you are running in: `codex`, `claude-code`, `opencode`,
+`zcode`, `qoder`, `kimi-code`, or `dsh`):
 
 ```bash
-npx cowork-flow project init .
+npx cowork-flow project init --host <host>
 ```
 
 After init the project carries its own Skills (`.agents/skills/`), the task

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

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

package/presets/kimi-code/skills/cowork-flow-bootstrap/SKILL.md

@@ -17,10 +17,12 @@ workflow entry `./.cowork-flow/run`).
 
 ## No runtime: offer the install
 
-Tell the user this repository has no cowork-flow runtime, then offer:
+Tell the user this repository has no cowork-flow runtime, then offer (replace
+`<host>` with the host you are running in: `codex`, `claude-code`, `opencode`,
+`zcode`, `qoder`, `kimi-code`, or `dsh`):
 
 ```bash
-npx cowork-flow project init .
+npx cowork-flow project init --host <host>
 ```
 
 After init the project carries its own Skills (`.agents/skills/`), the task

package/presets/opencode/cowork-flow/skills/cowork-flow-bootstrap/SKILL.md

@@ -17,10 +17,12 @@ workflow entry `./.cowork-flow/run`).
 
 ## No runtime: offer the install
 
-Tell the user this repository has no cowork-flow runtime, then offer:
+Tell the user this repository has no cowork-flow runtime, then offer (replace
+`<host>` with the host you are running in: `codex`, `claude-code`, `opencode`,
+`zcode`, `qoder`, `kimi-code`, or `dsh`):
 
 ```bash
-npx cowork-flow project init .
+npx cowork-flow project init --host <host>
 ```
 
 After init the project carries its own Skills (`.agents/skills/`), the task

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

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

package/presets/qoder/skills/cowork-flow-bootstrap/SKILL.md

@@ -17,10 +17,12 @@ workflow entry `./.cowork-flow/run`).
 
 ## No runtime: offer the install
 
-Tell the user this repository has no cowork-flow runtime, then offer:
+Tell the user this repository has no cowork-flow runtime, then offer (replace
+`<host>` with the host you are running in: `codex`, `claude-code`, `opencode`,
+`zcode`, `qoder`, `kimi-code`, or `dsh`):
 
 ```bash
-npx cowork-flow project init .
+npx cowork-flow project init --host <host>
 ```
 
 After init the project carries its own Skills (`.agents/skills/`), the task

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

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

package/presets/zcode/skills/cowork-flow-bootstrap/SKILL.md

@@ -17,10 +17,12 @@ workflow entry `./.cowork-flow/run`).
 
 ## No runtime: offer the install
 
-Tell the user this repository has no cowork-flow runtime, then offer:
+Tell the user this repository has no cowork-flow runtime, then offer (replace
+`<host>` with the host you are running in: `codex`, `claude-code`, `opencode`,
+`zcode`, `qoder`, `kimi-code`, or `dsh`):
 
 ```bash
-npx cowork-flow project init .
+npx cowork-flow project init --host <host>
 ```
 
 After init the project carries its own Skills (`.agents/skills/`), the task

package/src/cli.js

@@ -149,7 +149,7 @@ async function defaultSelectPlatforms({ message, choices, defaultSelected = [] }
       const action = applyPickerKey(state, text, key, choices);
       if (action?.outcome === 'cancel') {
         cleanup();
-        reject(new Error('Platform selection cancelled'));
+        reject(new Error('Host selection cancelled'));
         return;
       }
       if (action?.outcome === 'confirm') {

package/src/commands/init.js

@@ -1,9 +1,12 @@
+import { execFile } from 'node:child_process';
 import { access, readFile } from 'node:fs/promises';
 import { join, resolve } from 'node:path';
+import { promisify } from 'node:util';
 
 import {
   applyPlan,
   buildInitPlan,
+  detectInstalledPlatforms,
   summarizePlan
 } from '../lib/copy-template.js';
 import { readPackageInfo } from '../lib/package-info.js';
@@ -15,6 +18,8 @@ import {
 } from '../lib/platforms.js';
 import { parseFlags, UsageError } from '../lib/cli-flags.js';
 
+const execFileAsync = promisify(execFile);
+
 // The manifest layer reports a plain Error; re-thrown as a
 // usage error so a bad host name exits with the
 // argv-mistake code.
@@ -29,15 +34,19 @@ function parsePlatformSelectionOrUsage(values) {
 function parseInitArgs(args) {
   const { flags, positionals } = parseFlags(args, {
     boolean: ['--dry-run', '--force'],
-    value: ['--platform', '--platforms', '--developer'],
-    repeatable: ['--platform', '--platforms'],
+    value: ['--host', '--platform', '--platforms', '--developer'],
+    repeatable: ['--host', '--platform', '--platforms'],
     positional: { min: 0, max: 1, name: '[target]' }
   });
   return {
     developer: flags['--developer'] ?? null,
     dryRun: Boolean(flags['--dry-run']),
     force: Boolean(flags['--force']),
-    platforms: [...(flags['--platform'] ?? []), ...(flags['--platforms'] ?? [])],
+    platforms: [
+      ...(flags['--host'] ?? []),
+      ...(flags['--platform'] ?? []),
+      ...(flags['--platforms'] ?? [])
+    ],
     target: positionals[0] === undefined ? process.cwd() : resolve(positionals[0])
   };
 }
@@ -57,7 +66,7 @@ async function pathExists(path) {
 function normalizeDeveloperName(value) {
   const name = String(value ?? '').trim();
   if (!name) {
-    throw new UsageError('Developer name required. Run: cwf project init <target> --developer <name>');
+    throw new UsageError('Developer name required. Run: cwf project init [target] --developer <name>');
   }
   if (/[\\/]/.test(name)) {
     throw new UsageError('Developer name must not contain path separators');
@@ -65,6 +74,32 @@ function normalizeDeveloperName(value) {
   return name;
 }
 
+function normalizeGitDeveloper(value) {
+  const name = String(value ?? '').trim();
+  if (!name || /[\\/]/.test(name) || (name.startsWith('<') && name.endsWith('>'))) {
+    return null;
+  }
+  return name;
+}
+
+// `git config user.name` reads the local repository first and falls back to the
+// global config, which is the "nearest identity" this command wants. A missing
+// binary, an unset value, or a directory that vanishes under us all mean "no
+// git identity", never a failed init.
+async function readGitDeveloper(target) {
+  const cwd = await pathExists(target) ? target : process.cwd();
+  try {
+    const { stdout } = await execFileAsync('git', ['config', 'user.name'], {
+      cwd,
+      timeout: 5000,
+      windowsHide: true
+    });
+    return normalizeGitDeveloper(stdout);
+  } catch {
+    return null;
+  }
+}
+
 async function readExistingDeveloper(target) {
   const developerFile = join(target, '.cowork-flow', '.developer');
   if (!await pathExists(developerFile)) {
@@ -78,19 +113,30 @@ async function readExistingDeveloper(target) {
 async function resolveDeveloperName(options, prompt) {
   const existing = await readExistingDeveloper(options.target);
   if (existing) {
-    return { existing: true, name: existing };
+    return { existing: true, name: existing, source: 'existing' };
   }
 
-  if (options.dryRun && !options.developer) {
-    return { existing: false, name: null };
+  if (options.developer) {
+    return { existing: false, name: normalizeDeveloperName(options.developer), source: 'flag' };
   }
 
-  let name = options.developer;
-  if (!name && typeof prompt === 'function') {
-    name = await prompt('Developer name: ');
+  const gitName = await readGitDeveloper(options.target);
+
+  if (options.dryRun) {
+    return { existing: false, name: gitName, source: gitName ? 'git' : null };
   }
 
-  return { existing: false, name: normalizeDeveloperName(name) };
+  if (typeof prompt === 'function') {
+    const answer = await prompt(`Developer name${gitName ? ` [${gitName}]` : ''}: `);
+    const typed = String(answer ?? '').trim();
+    return {
+      existing: false,
+      name: normalizeDeveloperName(typed || gitName),
+      source: typed ? 'prompt' : 'git'
+    };
+  }
+
+  return { existing: false, name: normalizeDeveloperName(gitName), source: 'git' };
 }
 
 async function resolvePlatforms(options, selectPlatforms) {
@@ -98,10 +144,17 @@ async function resolvePlatforms(options, selectPlatforms) {
     return parsePlatformSelectionOrUsage(options.platforms);
   }
 
+  // Reuse the same marker-based detection `project sync` uses, so init and sync
+  // agree on what "this project already uses" means.
+  const detected = await detectInstalledPlatforms(options.target);
+  if (detected.length > 0) {
+    return detected;
+  }
+
   let selected = null;
   if (typeof selectPlatforms === 'function') {
     selected = await selectPlatforms({
-      message: 'Select platforms to set up',
+      message: 'Select hosts to set up',
       choices: SUPPORTED_PLATFORMS.map((platform) => ({
         label: platformLabel(platform),
         value: platform
@@ -156,13 +209,16 @@ export async function runInitWithOptions(
 
   await applyPlan(plan, { dryRun: options.dryRun, fileSystem });
   io.writeOut(summarizePlan(plan, options.dryRun));
-  io.writeOut(`Platforms: ${formatPlatformList(platforms)}\n`);
+  io.writeOut(`Hosts: ${formatPlatformList(platforms)}\n`);
 
   if (options.dryRun) {
     if (developer.existing) {
       io.writeOut(`dry-run preserve-existing=.cowork-flow/.developer for developer ${developer.name}\n`);
     } else if (developer.name) {
-      io.writeOut(`dry-run would-create=.cowork-flow/.developer for developer ${developer.name}\n`);
+      const source = developer.source === 'git' ? ' (from git user.name)' : '';
+      io.writeOut(`dry-run would-create=.cowork-flow/.developer for developer ${developer.name}${source}\n`);
+    } else {
+      io.writeOut('dry-run would-skip=.cowork-flow/.developer (no developer identity; pass --developer)\n');
     }
     io.writeOut('Next: update AGENTS.md and .cowork-flow/config.yaml for this project.\n');
     return 0;
@@ -171,7 +227,8 @@ export async function runInitWithOptions(
   if (developer.existing) {
     io.writeOut(`Developer already initialized: ${developer.name}\n`);
   } else {
-    io.writeOut(`Developer initialized: ${developer.name}\n`);
+    const source = developer.source === 'git' ? ' (from git user.name)' : '';
+    io.writeOut(`Developer initialized: ${developer.name}${source}\n`);
   }
   io.writeOut('Next: update AGENTS.md and .cowork-flow/config.yaml for this project.\n');
   return 0;

package/src/commands/registry.js

@@ -35,7 +35,7 @@ const FLAG_HELP = {
 const flag = (name) => ({ name, kind: 'boolean', description: FLAG_HELP[name] });
 const valueFlag = (name, valueName) => ({ name, kind: 'value', valueName, description: FLAG_HELP[name] });
 
-const PLATFORM_TOKENS = `${hostRegistry.platformIds.join('|')}|all`;
+const HOST_TOKENS = `${hostRegistry.platformIds.join('|')}|all`;
 const HOST_NOTE = `Hosts: ${Object.entries(HOST_COMPONENTS)
   .map(([id, host]) => `${id} (${Object.keys(host.components).join(', ')})`)
   .join('; ')}.`;
@@ -51,18 +51,19 @@ export const COMMANDS = [
   {
     path: ['project', 'init'],
     summary: 'Copy the cowork-flow template into a project',
-    usage: `project init [target] --platform <${PLATFORM_TOKENS}> [--developer <name>] [--dry-run] [--force]`,
+    usage: `project init [target] --host <${HOST_TOKENS}> [--developer <name>] [--dry-run] [--force]`,
     flags: [
-      { name: '--platform', kind: 'value', valueName: 'host', repeatable: true, description: 'Host to set the project up for; repeatable and comma-separated' },
-      { name: '--platforms', kind: 'value', valueName: 'host', repeatable: true, description: 'Alias of --platform' },
-      { name: '--developer', kind: 'value', valueName: 'name', description: 'Developer name recorded in .cowork-flow/.developer' },
+      { name: '--host', kind: 'value', valueName: 'host', repeatable: true, description: 'Host to set the project up for; repeatable and comma-separated, auto-detected when omitted' },
+      { name: '--platform', kind: 'value', valueName: 'host', repeatable: true, description: 'Alias of --host' },
+      { name: '--platforms', kind: 'value', valueName: 'host', repeatable: true, description: 'Alias of --host' },
+      { name: '--developer', kind: 'value', valueName: 'name', description: 'Developer name recorded in .cowork-flow/.developer; falls back to git user.name' },
       flag('--dry-run'),
       flag('--force')
     ],
     positional: { min: 0, max: 1, name: '[target]' },
     examples: [
-      'cwf project init . --platform codex --developer alice',
-      'cwf project init ./my-project --platform all --dry-run'
+      'cwf project init --host codex --developer alice',
+      'cwf project init ./my-project --host all --dry-run'
     ],
     run: (args, context) => runInit(args, context)
   },

package/src/commands/sync.js

@@ -43,6 +43,6 @@ export async function runSync(args, { io, fileSystem }) {
     const readiness = await buildReadinessReport(plan, { fileSystem });
     io.writeOut(formatReadinessReport(readiness));
   }
-  io.writeOut(`Platforms: ${platforms.length > 0 ? formatPlatformList(platforms) : 'none'}\n`);
+  io.writeOut(`Hosts: ${platforms.length > 0 ? formatPlatformList(platforms) : 'none'}\n`);
   return 0;
 }

package/src/lib/host-assets.js

@@ -172,7 +172,7 @@ function selectionRules(index) {
         const platformId = aliases.get(token);
         if (!platformId) {
           throw new Error(
-            `Unsupported platform: ${token}. Supported platforms: ${platformIds.join(', ')}`
+            `Unsupported host: ${token}. Supported hosts: ${platformIds.join(', ')}`
           );
         }
         selected.add(platformId);
@@ -180,7 +180,7 @@ function selectionRules(index) {
     }
     if (selected.size === 0) {
       throw new Error(
-        `Platform selection required. Run: cwf project init <target> --platform ${platformIds.join('|')}`
+        `Host selection required. Run: cwf project init [target] --host ${platformIds.join('|')}`
       );
     }
     return platformIds.filter((platformId) => selected.has(platformId));

package/template/.cowork-flow/.version

@@ -1 +1 @@
-2.1.0
+2.3.0

package/template/.cowork-flow/spec/contracts/decision-anchor.md

@@ -33,6 +33,7 @@ translated heading would simply stop being read.
 
 ## 验证命令
 - `<command>` → <expected>
+- 规范核对：逐条核对 `.cowork-flow/spec/<dev_type>/` 适用规范 → pass / not_applicable（附理由）
 ```
 
 ## Section requirements
@@ -44,7 +45,7 @@ translated heading would simply stop being read.
 | `## 被拒方案` | optional | required for brainstorming tasks, so a rejected option is not reconsidered during execution |
 | `## 关键假设` | optional | filled in for complex tasks to surface implicit constraints; not read by the runtime parser |
 | `## 范围边界` | optional | prevents scope creep |
-| `## 验证命令` | optional | filled in for complex tasks, as the basis for automated verification |
+| `## 验证命令` | optional | filled in for complex tasks, as the basis for automated verification; when the changed files are covered by `.cowork-flow/spec/backend/` or `frontend/` rules, it must also carry the spec/gate check for the task's `dev_type` (deciding command, or clause-by-clause `pass` / `not_applicable` with reason) |
 
 ### Machine-readable line formats (for injection)
 
@@ -54,6 +55,11 @@ fact view (`services/fact_view.parse_decision_anchor`). Line-format conventions:
 - `## 验证命令`: one command per line (an optional `- ` prefix), truncated to 120
   characters, at most 10 lines; the implementing agent runs them itself
   (self-declared, self-checked) and the reviewer verifies the execution evidence.
+  When the changed files are covered by `.cowork-flow/spec/<dev_type>/` rules, the
+  section must also carry the spec/gate check for the task's `dev_type`: a deciding
+  command, or a `规范核对:` line reviewed clause by clause (`pass` /
+  `not_applicable` + reason). This is a strong review reminder, not a `spec-check`
+  hard gate.
 - `## 范围边界`: only the first non-empty line is taken, truncated to 160
   characters.
 

package/template/skills/task-planning/SKILL.md

@@ -45,7 +45,7 @@ Start with a concise brief:
 | **Task Type** | Tiny / Normal / High-risk: <reason> |
 | **Strategy** | Serial / Parallel: <why> |
 | **Success Criteria** | AC-001 / AC-002 / AC-003 |
-| **Final Verification** | `<command>` -> exit 0; `<command>` -> exit 0 |
+| **Final Verification** | `<command>` -> exit 0; clause-by-clause check against applicable `.cowork-flow/spec/<dev_type>/` rules and project gates -> `pass` / `not_applicable` per clause |
 | **Primary Risk** | Low / Medium / High: <one sentence> |
 
 ## Goal
@@ -116,6 +116,8 @@ Then list task briefs, followed by integrated verification and completion checks
   <command>
   ```
 
+  When changed files are covered by `.cowork-flow/spec/<dev_type>/` rules, add the deciding command or a spec/gate check line (`pass` / `not_applicable` with reason; format example in `decision-anchor.md`) here; it is a strong review reminder, not a hard gate.
+
   **Completion Conditions**
   - <2-4 checkable conditions>
 
@@ -128,7 +130,7 @@ Then list task briefs, followed by integrated verification and completion checks
 
 - For Tiny tasks, keep the brief short but still name exact file boundaries, completion conditions, and verification commands.
 - For behavior changes, include a failing test before implementation when behavior can be tested.
-- For implementation tasks whose changed files are covered by `.cowork-flow/spec/` requirements, name the covered spec files in the plan so review can check them clause by clause.
+- For implementation tasks whose changed files are covered by `.cowork-flow/spec/` requirements, name the covered spec files in the plan and add the clause check to the task's `Verification Command` and the plan's `Final Verification`: run the deciding command when one exists, otherwise check clause by clause and record `pass` / `not_applicable` with reason. This is a strong review reminder, not a separate hard gate.
 - Do not add shallow tests just to satisfy process. Avoid tests that only assert existence, mirror implementation details, count mock calls without behavior, or snapshot empty structure.
 - For complex problems, test depth first: business invariants, cross-layer contracts, state transitions, error boundaries, and real regression paths before narrow unit cases.
 - Map behavior-changing tests to stable `decision-anchor.md` acceptance IDs when useful; do not create `tdd.jsonl` or write TDD evidence records into `check.jsonl`.
@@ -190,3 +192,4 @@ Before handoff:
 3. Confirm every Normal or High-risk task has file boundaries, key symbols, implementation notes, test proof, completion conditions, and prohibited drift.
 4. Check names, paths, command syntax, and expected outputs.
 5. Confirm the plan says to stop and report back when code facts conflict with the plan, a plan-external file becomes necessary, or a test fails for an unplanned reason.
+6. Confirm Final Verification carries the applicable `.cowork-flow/spec/<dev_type>/` clause check, or states why no spec file applies.