harnessed 4.8.0 → 4.9.1

package/dist/index.mjs

@@ -1,6 +1,6 @@
 // package.json
 var package_default = {
-  version: "4.8.0"};
+  version: "4.9.1"};
 
 // src/index.ts
 var VERSION = package_default.version;

package/dist/index.mjs.map

@@ -1 +1 @@
-{"version":3,"sources":["../package.json","../src/index.ts"],"names":[],"mappings":";AAAA,IAAA,eAAA,GAAA;AAAA,EAEE,OAAA,EAAW,OAkGb,CAAA;;;AC/FO,IAAM,UAAU,eAAA,CAAI","file":"index.mjs","sourcesContent":["{\n  \"name\": \"harnessed\",\n  \"version\": \"4.8.0\",\n  \"description\": \"AI coding harness package manager + composition orchestrator\",\n  \"type\": \"module\",\n  \"license\": \"Apache-2.0\",\n  \"author\": \"easyinplay\",\n  \"repository\": {\n    \"type\": \"git\",\n    \"url\": \"https://github.com/easyinplay/harnessed.git\"\n  },\n  \"homepage\": \"https://github.com/easyinplay/harnessed#readme\",\n  \"bugs\": \"https://github.com/easyinplay/harnessed/issues\",\n  \"keywords\": [\n    \"claude-code\",\n    \"ai-harness\",\n    \"package-manager\",\n    \"composition\",\n    \"skill-pack\",\n    \"mcp\",\n    \"orchestrator\"\n  ],\n  \"engines\": {\n    \"node\": \">=22.0.0\"\n  },\n  \"packageManager\": \"pnpm@10.12.0\",\n  \"bin\": {\n    \"harnessed\": \"./dist/cli.mjs\",\n    \"harnessed-inject-state\": \"./bin/harnessed-inject-state.mjs\"\n  },\n  \"main\": \"./dist/index.mjs\",\n  \"types\": \"./dist/index.d.ts\",\n  \"exports\": {\n    \".\": {\n      \"types\": \"./dist/index.d.ts\",\n      \"import\": \"./dist/index.mjs\",\n      \"default\": \"./dist/index.mjs\"\n    },\n    \"./schemas\": {\n      \"types\": \"./dist/schemas/index.d.ts\",\n      \"import\": \"./dist/schemas/index.mjs\"\n    },\n    \"./package.json\": \"./package.json\"\n  },\n  \"files\": [\n    \"dist\",\n    \"bin\",\n    \"manifests\",\n    \"messages\",\n    \"workflows\",\n    \"routing\",\n    \"config-templates\",\n    \"schemas\",\n    \"README.md\",\n    \"LICENSE\",\n    \"NOTICE\",\n    \"THIRD-PARTY-NOTICES.md\"\n  ],\n  \"scripts\": {\n    \"dev\": \"tsup --watch\",\n    \"build\": \"tsc --noEmit && tsup\",\n    \"build:schema\": \"node ./scripts/build-schema.mjs\",\n    \"validate:schema\": \"node ./scripts/validate-schema.mjs\",\n    \"typecheck\": \"tsc --noEmit\",\n    \"test\": \"vitest run --passWithNoTests\",\n    \"test:watch\": \"vitest\",\n    \"test:coverage\": \"vitest run --coverage --passWithNoTests\",\n    \"bench\": \"vitest bench --run\",\n    \"lint\": \"biome check .\",\n    \"lint:fix\": \"biome check --write .\",\n    \"format\": \"biome format --write .\"\n  },\n  \"dependencies\": {\n    \"@anthropic-ai/claude-agent-sdk\": \"0.3.142\",\n    \"@clack/prompts\": \"^0.10.1\",\n    \"@sinclair/typebox\": \"^0.34.49\",\n    \"ajv\": \"^8.20.0\",\n    \"ajv-errors\": \"^3.0.0\",\n    \"ajv-formats\": \"^3.0.1\",\n    \"commander\": \"^13.0.0\",\n    \"diff\": \"^9.0.0\",\n    \"expr-eval\": \"^2.0.2\",\n    \"picocolors\": \"^1.1.1\",\n    \"proper-lockfile\": \"^4.1.2\",\n    \"yaml\": \"^2.9.0\"\n  },\n  \"devDependencies\": {\n    \"@biomejs/biome\": \"^2.0.0\",\n    \"@types/node\": \"^22.10.0\",\n    \"@types/proper-lockfile\": \"^4.1.4\",\n    \"@vitest/coverage-v8\": \"^4.0.0\",\n    \"tsup\": \"^8.3.0\",\n    \"typescript\": \"^5.6.0\",\n    \"vitest\": \"^4.0.0\"\n  },\n  \"pnpm\": {\n    \"onlyBuiltDependencies\": [\n      \"esbuild\"\n    ]\n  }\n}\n","// Main library entry — re-exports public APIs.\n// phase 1.1 batch 1: skeleton only; schema validator wired in batch 2 (T3+).\n\nimport pkg from '../package.json' with { type: 'json' }\n\nexport const VERSION = pkg.version\n"]}
+{"version":3,"sources":["../package.json","../src/index.ts"],"names":[],"mappings":";AAAA,IAAA,eAAA,GAAA;AAAA,EAEE,OAAA,EAAW,OAkGb,CAAA;;;AC/FO,IAAM,UAAU,eAAA,CAAI","file":"index.mjs","sourcesContent":["{\n  \"name\": \"harnessed\",\n  \"version\": \"4.9.1\",\n  \"description\": \"AI coding harness package manager + composition orchestrator\",\n  \"type\": \"module\",\n  \"license\": \"Apache-2.0\",\n  \"author\": \"easyinplay\",\n  \"repository\": {\n    \"type\": \"git\",\n    \"url\": \"https://github.com/easyinplay/harnessed.git\"\n  },\n  \"homepage\": \"https://github.com/easyinplay/harnessed#readme\",\n  \"bugs\": \"https://github.com/easyinplay/harnessed/issues\",\n  \"keywords\": [\n    \"claude-code\",\n    \"ai-harness\",\n    \"package-manager\",\n    \"composition\",\n    \"skill-pack\",\n    \"mcp\",\n    \"orchestrator\"\n  ],\n  \"engines\": {\n    \"node\": \">=22.0.0\"\n  },\n  \"packageManager\": \"pnpm@10.12.0\",\n  \"bin\": {\n    \"harnessed\": \"./dist/cli.mjs\",\n    \"harnessed-inject-state\": \"./bin/harnessed-inject-state.mjs\"\n  },\n  \"main\": \"./dist/index.mjs\",\n  \"types\": \"./dist/index.d.ts\",\n  \"exports\": {\n    \".\": {\n      \"types\": \"./dist/index.d.ts\",\n      \"import\": \"./dist/index.mjs\",\n      \"default\": \"./dist/index.mjs\"\n    },\n    \"./schemas\": {\n      \"types\": \"./dist/schemas/index.d.ts\",\n      \"import\": \"./dist/schemas/index.mjs\"\n    },\n    \"./package.json\": \"./package.json\"\n  },\n  \"files\": [\n    \"dist\",\n    \"bin\",\n    \"manifests\",\n    \"messages\",\n    \"workflows\",\n    \"routing\",\n    \"config-templates\",\n    \"schemas\",\n    \"README.md\",\n    \"LICENSE\",\n    \"NOTICE\",\n    \"THIRD-PARTY-NOTICES.md\"\n  ],\n  \"scripts\": {\n    \"dev\": \"tsup --watch\",\n    \"build\": \"tsc --noEmit && tsup\",\n    \"build:schema\": \"node ./scripts/build-schema.mjs\",\n    \"validate:schema\": \"node ./scripts/validate-schema.mjs\",\n    \"typecheck\": \"tsc --noEmit\",\n    \"test\": \"vitest run --passWithNoTests\",\n    \"test:watch\": \"vitest\",\n    \"test:coverage\": \"vitest run --coverage --passWithNoTests\",\n    \"bench\": \"vitest bench --run\",\n    \"lint\": \"biome check .\",\n    \"lint:fix\": \"biome check --write .\",\n    \"format\": \"biome format --write .\"\n  },\n  \"dependencies\": {\n    \"@anthropic-ai/claude-agent-sdk\": \"0.3.142\",\n    \"@clack/prompts\": \"^0.10.1\",\n    \"@sinclair/typebox\": \"^0.34.49\",\n    \"ajv\": \"^8.20.0\",\n    \"ajv-errors\": \"^3.0.0\",\n    \"ajv-formats\": \"^3.0.1\",\n    \"commander\": \"^13.0.0\",\n    \"diff\": \"^9.0.0\",\n    \"expr-eval\": \"^2.0.2\",\n    \"picocolors\": \"^1.1.1\",\n    \"proper-lockfile\": \"^4.1.2\",\n    \"yaml\": \"^2.9.0\"\n  },\n  \"devDependencies\": {\n    \"@biomejs/biome\": \"^2.0.0\",\n    \"@types/node\": \"^22.10.0\",\n    \"@types/proper-lockfile\": \"^4.1.4\",\n    \"@vitest/coverage-v8\": \"^4.0.0\",\n    \"tsup\": \"^8.3.0\",\n    \"typescript\": \"^5.6.0\",\n    \"vitest\": \"^4.0.0\"\n  },\n  \"pnpm\": {\n    \"onlyBuiltDependencies\": [\n      \"esbuild\"\n    ]\n  }\n}\n","// Main library entry — re-exports public APIs.\n// phase 1.1 batch 1: skeleton only; schema validator wired in batch 2 (T3+).\n\nimport pkg from '../package.json' with { type: 'json' }\n\nexport const VERSION = pkg.version\n"]}

package/manifests/optional/perturn-inject.yaml

@@ -0,0 +1,49 @@
+# yaml-language-server: $schema=../../schemas/manifest.v1.schema.json
+# Phase 35 (v5.0 Spec 3/G) — opt-in per-turn injection hook.
+# Registers a UserPromptSubmit hook that runs bin/harnessed-inject-state.mjs each
+# turn: the bin prints a <workflow-state> breadcrumb (you-are-here / next sub) +
+# a relevance-filtered <project-context> block for the ACTIVE session's workflow
+# (session-scoped via the composite ledger key — Phase 34/35). The bin exits 0
+# silently when there is no active workflow, so an enabled hook in a non-workflow
+# repo is a cheap no-op. Opt-in (manifests/optional/) because per-turn injection
+# has a token cost (~1500 budget) and only matters in a harnessed-workflow repo.
+# Idempotent — re-install on an existing matching entry → skip.
+apiVersion: harnessed/v1
+kind: Manifest
+metadata:
+  name: perturn-inject
+  display_name: Per-Turn State Injection (UserPromptSubmit)
+  description: Opt-in UserPromptSubmit hook injecting the active session's workflow-state + project-context each turn (Spec 3/G).
+  upstream:
+    source: perturn-inject
+    homepage: https://github.com/easyinplay/harnessed
+    repository: https://github.com/easyinplay/harnessed.git
+    license: MIT
+    notice: First-party harnessed hook (Phase 35, v5.0 Spec 3/G).
+spec:
+  type: cc-hook
+  component_type: command
+  category: meta
+  install_type: hook
+  install:
+    method: cc-hook-add
+    cmd: "node bin/harnessed-inject-state.mjs"
+    hook_event: UserPromptSubmit
+    hook_command: "node bin/harnessed-inject-state.mjs"
+    idempotent_check: "grep -q harnessed-inject-state ~/.claude/settings.json"
+  verify:
+    cmd: "grep -q harnessed-inject-state ~/.claude/settings.json"
+    timeout_ms: 5000
+    expected_exit_code: 0
+  uninstall:
+    cmd: "true"
+  upstream_health:
+    stability: beta
+    last_check: "2026-06-25"
+    last_known_good_version: "0.1.0"
+    fallback_action: warn
+  signed_by: easyinplay
+  platforms:
+    - linux
+    - darwin
+    - win32

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "harnessed",
-  "version": "4.8.0",
+  "version": "4.9.1",
   "description": "AI coding harness package manager + composition orchestrator",
   "type": "module",
   "license": "Apache-2.0",

package/workflows/auto/SKILL.md

@@ -105,18 +105,18 @@ Sister `workflows/capabilities.yaml`:
 
 ## How to invoke
 
-Use the Bash tool to run:
-
-```bash
-echo "$ARGUMENTS" | harnessed run auto --task-stdin
-```
-
-If `$ARGUMENTS` is empty, run `harnessed run auto` (no stdin pipe).
-
-After completion, the Bash output prints a `Next:` hint on stderr suggesting the next stage. Decide whether to invoke based on conversation context — the hint is informational, not prescriptive.
-- For stage-by-stage review, append `--staged` (pauses between stages for user review).
-
-<!-- harnessed-generated:v3.4.4 -->
+Orchestrated CC-natively. Do NOT pipe to `harnessed run auto` — that is the CI/headless
+path (an in-process SDK spawn that blocks the session, bypasses Agent Teams, and hangs when
+invoked from inside a Claude Code session).
+
+Run the `/auto` slash command instead (generated by `harnessed setup` at
+`~/.claude/commands/auto.md`). It drives the stage natively: `harnessed gates` → which
+subs fire, `harnessed prompt <sub>` → each spawn-ready prompt, then a CC-native subagent
+(Task / Agent tool) per fired sub, recording each outcome with `harnessed checkpoint`. The
+full state-machine steps live in `~/.claude/commands/auto.md`; if that file is absent,
+follow that same gates → prompt → spawn → checkpoint sequence yourself.
+
+<!-- harnessed-generated:v4.9.1 -->
 
 ## References
 

package/workflows/auto/SKILL.zh-Hans.md

@@ -104,18 +104,16 @@ Sister `workflows/capabilities.yaml`:
 
 ## 如何调用
 
-使用 Bash 工具运行：
+CC-native 编排。**不要** pipe 到 `harnessed run auto` —— 那是 CI/headless 路径(in-process
+SDK spawn,会阻塞 session、绕过 Agent Teams,在 Claude Code 内部调用时还会挂死)。
 
-```bash
-echo "$ARGUMENTS" | harnessed run auto --task-stdin
-```
+改用 `/auto` slash command(由 `harnessed setup` 生成于 `~/.claude/commands/auto.md`)。
+它以 CC-native 方式驱动:`harnessed gates` 决定哪些 sub fire,`harnessed prompt <sub>` 给出每个
+spawn-ready prompt,然后用 CC-native subagent(Task / Agent 工具)逐个 spawn 已 fire 的 sub,
+每个结果用 `harnessed checkpoint` 记录。完整 state-machine 步骤见 `~/.claude/commands/auto.md`;
+若该文件不存在,自行按 gates → prompt → spawn → checkpoint 同序执行。
 
-如果 `$ARGUMENTS` 为空，运行 `harnessed run auto`（不带 stdin pipe）。
-
-完成后，Bash 输出会在 stderr 打印 `Next:` 提示，建议下一个阶段。根据对话上下文决定是否调用 — 该提示仅供参考，不作强制指引。
-- 如需逐 stage 审查，追加 `--staged`（每个 stage 完成后暂停，等待用户 review）。
-
-<!-- harnessed-generated:v3.4.4 -->
+<!-- harnessed-generated:v4.9.1 -->
 
 ## 参考文档
 

package/workflows/discuss/auto/SKILL.md

@@ -53,17 +53,18 @@ Sister `workflows/capabilities.yaml`:
 
 ## How to invoke
 
-Use the Bash tool to run:
-
-```bash
-echo "$ARGUMENTS" | harnessed run discuss --task-stdin
-```
-
-If `$ARGUMENTS` is empty, run `harnessed run discuss` (no stdin pipe).
-
-After completion, the Bash output prints a `Next:` hint on stderr suggesting the next stage. Decide whether to invoke based on conversation context — the hint is informational, not prescriptive.
-
-<!-- harnessed-generated:v3.4.4 -->
+Orchestrated CC-natively. Do NOT pipe to `harnessed run discuss` — that is the CI/headless
+path (an in-process SDK spawn that blocks the session, bypasses Agent Teams, and hangs when
+invoked from inside a Claude Code session).
+
+Run the `/discuss` slash command instead (generated by `harnessed setup` at
+`~/.claude/commands/discuss.md`). It drives the stage natively: `harnessed gates` → which
+subs fire, `harnessed prompt <sub>` → each spawn-ready prompt, then a CC-native subagent
+(Task / Agent tool) per fired sub, recording each outcome with `harnessed checkpoint`. The
+full state-machine steps live in `~/.claude/commands/discuss.md`; if that file is absent,
+follow that same gates → prompt → spawn → checkpoint sequence yourself.
+
+<!-- harnessed-generated:v4.9.1 -->
 
 ## References
 

package/workflows/discuss/auto/SKILL.zh-Hans.md

@@ -53,17 +53,16 @@ Sister `workflows/capabilities.yaml`:
 
 ## 如何调用
 
-使用 Bash 工具运行：
+CC-native 编排。**不要** pipe 到 `harnessed run discuss` —— 那是 CI/headless 路径(in-process
+SDK spawn,会阻塞 session、绕过 Agent Teams,在 Claude Code 内部调用时还会挂死)。
 
-```bash
-echo "$ARGUMENTS" | harnessed run discuss --task-stdin
-```
+改用 `/discuss` slash command(由 `harnessed setup` 生成于 `~/.claude/commands/discuss.md`)。
+它以 CC-native 方式驱动:`harnessed gates` 决定哪些 sub fire,`harnessed prompt <sub>` 给出每个
+spawn-ready prompt,然后用 CC-native subagent(Task / Agent 工具)逐个 spawn 已 fire 的 sub,
+每个结果用 `harnessed checkpoint` 记录。完整 state-machine 步骤见 `~/.claude/commands/discuss.md`;
+若该文件不存在,自行按 gates → prompt → spawn → checkpoint 同序执行。
 
-若 `$ARGUMENTS` 为空，运行 `harnessed run discuss`（不带 stdin pipe）。
-
-执行完成后，Bash 输出会在 stderr 打印 `Next:` 提示，建议下一个阶段。请根据对话上下文决定是否调用——该提示仅供参考，非强制指令。
-
-<!-- harnessed-generated:v3.4.4 -->
+<!-- harnessed-generated:v4.9.1 -->
 
 ## 参考资料
 

package/workflows/discuss/phase/SKILL.md

@@ -53,17 +53,18 @@ Sister `workflows/judgments/phase-gate.yaml`:
 
 ## How to invoke
 
-Use the Bash tool to run:
-
-```bash
-echo "$ARGUMENTS" | harnessed run discuss-phase --task-stdin
-```
-
-If `$ARGUMENTS` is empty, run `harnessed run discuss-phase` (no stdin pipe).
-
-After completion, the Bash output prints a `Next:` hint on stderr suggesting the next stage. Decide whether to invoke based on conversation context — the hint is informational, not prescriptive.
-
-<!-- harnessed-generated:v3.4.4 -->
+Orchestrated CC-natively. Do NOT pipe to `harnessed run discuss-phase` — that is the CI/headless
+path (an in-process SDK spawn that blocks the session, bypasses Agent Teams, and hangs when
+invoked from inside a Claude Code session).
+
+Run the `/discuss-phase` slash command instead (generated by `harnessed setup` at
+`~/.claude/commands/discuss-phase.md`). It drives the stage natively: `harnessed gates` → which
+subs fire, `harnessed prompt <sub>` → each spawn-ready prompt, then a CC-native subagent
+(Task / Agent tool) per fired sub, recording each outcome with `harnessed checkpoint`. The
+full state-machine steps live in `~/.claude/commands/discuss-phase.md`; if that file is absent,
+follow that same gates → prompt → spawn → checkpoint sequence yourself.
+
+<!-- harnessed-generated:v4.9.1 -->
 
 ## References
 

package/workflows/discuss/phase/SKILL.zh-Hans.md

@@ -53,17 +53,16 @@ Sister `workflows/judgments/phase-gate.yaml`:
 
 ## 如何调用
 
-使用 Bash 工具运行：
+CC-native 编排。**不要** pipe 到 `harnessed run discuss-phase` —— 那是 CI/headless 路径(in-process
+SDK spawn,会阻塞 session、绕过 Agent Teams,在 Claude Code 内部调用时还会挂死)。
 
-```bash
-echo "$ARGUMENTS" | harnessed run discuss-phase --task-stdin
-```
+改用 `/discuss-phase` slash command(由 `harnessed setup` 生成于 `~/.claude/commands/discuss-phase.md`)。
+它以 CC-native 方式驱动:`harnessed gates` 决定哪些 sub fire,`harnessed prompt <sub>` 给出每个
+spawn-ready prompt,然后用 CC-native subagent(Task / Agent 工具)逐个 spawn 已 fire 的 sub,
+每个结果用 `harnessed checkpoint` 记录。完整 state-machine 步骤见 `~/.claude/commands/discuss-phase.md`;
+若该文件不存在,自行按 gates → prompt → spawn → checkpoint 同序执行。
 
-若 `$ARGUMENTS` 为空，运行 `harnessed run discuss-phase`（不带 stdin pipe）。
-
-执行完成后，Bash 输出会在 stderr 打印 `Next:` 提示，建议下一个阶段。请根据对话上下文决定是否调用——该提示仅供参考，非强制指令。
-
-<!-- harnessed-generated:v3.4.4 -->
+<!-- harnessed-generated:v4.9.1 -->
 
 ## 参考资料
 

package/workflows/discuss/strategic/SKILL.md

@@ -57,17 +57,18 @@ Sister `workflows/judgments/strategic-gate.yaml`:
 
 ## How to invoke
 
-Use the Bash tool to run:
-
-```bash
-echo "$ARGUMENTS" | harnessed run discuss-strategic --task-stdin
-```
-
-If `$ARGUMENTS` is empty, run `harnessed run discuss-strategic` (no stdin pipe).
-
-After completion, the Bash output prints a `Next:` hint on stderr suggesting the next stage. Decide whether to invoke based on conversation context — the hint is informational, not prescriptive.
-
-<!-- harnessed-generated:v3.4.4 -->
+Orchestrated CC-natively. Do NOT pipe to `harnessed run discuss-strategic` — that is the CI/headless
+path (an in-process SDK spawn that blocks the session, bypasses Agent Teams, and hangs when
+invoked from inside a Claude Code session).
+
+Run the `/discuss-strategic` slash command instead (generated by `harnessed setup` at
+`~/.claude/commands/discuss-strategic.md`). It drives the stage natively: `harnessed gates` → which
+subs fire, `harnessed prompt <sub>` → each spawn-ready prompt, then a CC-native subagent
+(Task / Agent tool) per fired sub, recording each outcome with `harnessed checkpoint`. The
+full state-machine steps live in `~/.claude/commands/discuss-strategic.md`; if that file is absent,
+follow that same gates → prompt → spawn → checkpoint sequence yourself.
+
+<!-- harnessed-generated:v4.9.1 -->
 
 ## References
 

package/workflows/discuss/strategic/SKILL.zh-Hans.md

@@ -57,17 +57,16 @@ Sister `workflows/judgments/strategic-gate.yaml`:
 
 ## 如何调用
 
-使用 Bash 工具运行：
+CC-native 编排。**不要** pipe 到 `harnessed run discuss-strategic` —— 那是 CI/headless 路径(in-process
+SDK spawn,会阻塞 session、绕过 Agent Teams,在 Claude Code 内部调用时还会挂死)。
 
-```bash
-echo "$ARGUMENTS" | harnessed run discuss-strategic --task-stdin
-```
+改用 `/discuss-strategic` slash command(由 `harnessed setup` 生成于 `~/.claude/commands/discuss-strategic.md`)。
+它以 CC-native 方式驱动:`harnessed gates` 决定哪些 sub fire,`harnessed prompt <sub>` 给出每个
+spawn-ready prompt,然后用 CC-native subagent(Task / Agent 工具)逐个 spawn 已 fire 的 sub,
+每个结果用 `harnessed checkpoint` 记录。完整 state-machine 步骤见 `~/.claude/commands/discuss-strategic.md`;
+若该文件不存在,自行按 gates → prompt → spawn → checkpoint 同序执行。
 
-若 `$ARGUMENTS` 为空，运行 `harnessed run discuss-strategic`（不带 stdin pipe）。
-
-执行完成后，Bash 输出会在 stderr 打印 `Next:` 提示，建议下一个阶段。请根据对话上下文决定是否调用——该提示仅供参考，非强制指令。
-
-<!-- harnessed-generated:v3.4.4 -->
+<!-- harnessed-generated:v4.9.1 -->
 
 ## 参考资料
 

package/workflows/discuss/subtask/SKILL.md

@@ -58,17 +58,18 @@ Sister `workflows/judgments/subtask-gate.yaml`:
 
 ## How to invoke
 
-Use the Bash tool to run:
-
-```bash
-echo "$ARGUMENTS" | harnessed run discuss-subtask --task-stdin
-```
-
-If `$ARGUMENTS` is empty, run `harnessed run discuss-subtask` (no stdin pipe).
-
-After completion, the Bash output prints a `Next:` hint on stderr suggesting the next stage. Decide whether to invoke based on conversation context — the hint is informational, not prescriptive.
-
-<!-- harnessed-generated:v3.4.4 -->
+Orchestrated CC-natively. Do NOT pipe to `harnessed run discuss-subtask` — that is the CI/headless
+path (an in-process SDK spawn that blocks the session, bypasses Agent Teams, and hangs when
+invoked from inside a Claude Code session).
+
+Run the `/discuss-subtask` slash command instead (generated by `harnessed setup` at
+`~/.claude/commands/discuss-subtask.md`). It drives the stage natively: `harnessed gates` → which
+subs fire, `harnessed prompt <sub>` → each spawn-ready prompt, then a CC-native subagent
+(Task / Agent tool) per fired sub, recording each outcome with `harnessed checkpoint`. The
+full state-machine steps live in `~/.claude/commands/discuss-subtask.md`; if that file is absent,
+follow that same gates → prompt → spawn → checkpoint sequence yourself.
+
+<!-- harnessed-generated:v4.9.1 -->
 
 ## References
 

package/workflows/discuss/subtask/SKILL.zh-Hans.md

@@ -58,17 +58,16 @@ Sister `workflows/judgments/subtask-gate.yaml`:
 
 ## 如何调用
 
-使用 Bash 工具运行：
+CC-native 编排。**不要** pipe 到 `harnessed run discuss-subtask` —— 那是 CI/headless 路径(in-process
+SDK spawn,会阻塞 session、绕过 Agent Teams,在 Claude Code 内部调用时还会挂死)。
 
-```bash
-echo "$ARGUMENTS" | harnessed run discuss-subtask --task-stdin
-```
+改用 `/discuss-subtask` slash command(由 `harnessed setup` 生成于 `~/.claude/commands/discuss-subtask.md`)。
+它以 CC-native 方式驱动:`harnessed gates` 决定哪些 sub fire,`harnessed prompt <sub>` 给出每个
+spawn-ready prompt,然后用 CC-native subagent(Task / Agent 工具)逐个 spawn 已 fire 的 sub,
+每个结果用 `harnessed checkpoint` 记录。完整 state-machine 步骤见 `~/.claude/commands/discuss-subtask.md`;
+若该文件不存在,自行按 gates → prompt → spawn → checkpoint 同序执行。
 
-若 `$ARGUMENTS` 为空，运行 `harnessed run discuss-subtask`（不带 stdin pipe）。
-
-执行完成后，Bash 输出会在 stderr 打印 `Next:` 提示，建议下一个阶段。请根据对话上下文决定是否调用——该提示仅供参考，非强制指令。
-
-<!-- harnessed-generated:v3.4.4 -->
+<!-- harnessed-generated:v4.9.1 -->
 
 ## 参考资料
 

package/workflows/plan/architecture/SKILL.md

@@ -54,17 +54,18 @@ trigger `is-complex-architecture` 重构 ref。
 
 ## How to invoke
 
-Use the Bash tool to run:
-
-```bash
-echo "$ARGUMENTS" | harnessed run plan-architecture --task-stdin
-```
-
-If `$ARGUMENTS` is empty, run `harnessed run plan-architecture` (no stdin pipe).
-
-After completion, the Bash output prints a `Next:` hint on stderr suggesting the next stage. Decide whether to invoke based on conversation context — the hint is informational, not prescriptive.
-
-<!-- harnessed-generated:v3.4.4 -->
+Orchestrated CC-natively. Do NOT pipe to `harnessed run plan-architecture` — that is the CI/headless
+path (an in-process SDK spawn that blocks the session, bypasses Agent Teams, and hangs when
+invoked from inside a Claude Code session).
+
+Run the `/plan-architecture` slash command instead (generated by `harnessed setup` at
+`~/.claude/commands/plan-architecture.md`). It drives the stage natively: `harnessed gates` → which
+subs fire, `harnessed prompt <sub>` → each spawn-ready prompt, then a CC-native subagent
+(Task / Agent tool) per fired sub, recording each outcome with `harnessed checkpoint`. The
+full state-machine steps live in `~/.claude/commands/plan-architecture.md`; if that file is absent,
+follow that same gates → prompt → spawn → checkpoint sequence yourself.
+
+<!-- harnessed-generated:v4.9.1 -->
 
 ## References
 

package/workflows/plan/architecture/SKILL.zh-Hans.md

@@ -54,17 +54,16 @@ trigger `is-complex-architecture` 重构 ref。
 
 ## 如何调用
 
-使用 Bash 工具运行：
+CC-native 编排。**不要** pipe 到 `harnessed run plan-architecture` —— 那是 CI/headless 路径(in-process
+SDK spawn,会阻塞 session、绕过 Agent Teams,在 Claude Code 内部调用时还会挂死)。
 
-```bash
-echo "$ARGUMENTS" | harnessed run plan-architecture --task-stdin
-```
+改用 `/plan-architecture` slash command(由 `harnessed setup` 生成于 `~/.claude/commands/plan-architecture.md`)。
+它以 CC-native 方式驱动:`harnessed gates` 决定哪些 sub fire,`harnessed prompt <sub>` 给出每个
+spawn-ready prompt,然后用 CC-native subagent(Task / Agent 工具)逐个 spawn 已 fire 的 sub,
+每个结果用 `harnessed checkpoint` 记录。完整 state-machine 步骤见 `~/.claude/commands/plan-architecture.md`;
+若该文件不存在,自行按 gates → prompt → spawn → checkpoint 同序执行。
 
-若 `$ARGUMENTS` 为空，运行 `harnessed run plan-architecture`（不带 stdin pipe）。
-
-完成后，Bash 输出会在 stderr 打印 `Next:` 提示，建议下一阶段。是否调用由对话上下文决定——该提示仅供参考，非强制指令。
-
-<!-- harnessed-generated:v3.4.4 -->
+<!-- harnessed-generated:v4.9.1 -->
 
 ## 参考文档
 

package/workflows/plan/auto/SKILL.md

@@ -54,17 +54,18 @@ Sister `workflows/capabilities.yaml`:
 
 ## How to invoke
 
-Use the Bash tool to run:
-
-```bash
-echo "$ARGUMENTS" | harnessed run plan --task-stdin
-```
-
-If `$ARGUMENTS` is empty, run `harnessed run plan` (no stdin pipe).
-
-After completion, the Bash output prints a `Next:` hint on stderr suggesting the next stage. Decide whether to invoke based on conversation context — the hint is informational, not prescriptive.
-
-<!-- harnessed-generated:v3.4.4 -->
+Orchestrated CC-natively. Do NOT pipe to `harnessed run plan` — that is the CI/headless
+path (an in-process SDK spawn that blocks the session, bypasses Agent Teams, and hangs when
+invoked from inside a Claude Code session).
+
+Run the `/plan` slash command instead (generated by `harnessed setup` at
+`~/.claude/commands/plan.md`). It drives the stage natively: `harnessed gates` → which
+subs fire, `harnessed prompt <sub>` → each spawn-ready prompt, then a CC-native subagent
+(Task / Agent tool) per fired sub, recording each outcome with `harnessed checkpoint`. The
+full state-machine steps live in `~/.claude/commands/plan.md`; if that file is absent,
+follow that same gates → prompt → spawn → checkpoint sequence yourself.
+
+<!-- harnessed-generated:v4.9.1 -->
 
 ## References
 

package/workflows/plan/auto/SKILL.zh-Hans.md

@@ -54,17 +54,16 @@ Sister `workflows/capabilities.yaml`：
 
 ## 如何调用
 
-使用 Bash 工具运行：
+CC-native 编排。**不要** pipe 到 `harnessed run plan` —— 那是 CI/headless 路径(in-process
+SDK spawn,会阻塞 session、绕过 Agent Teams,在 Claude Code 内部调用时还会挂死)。
 
-```bash
-echo "$ARGUMENTS" | harnessed run plan --task-stdin
-```
+改用 `/plan` slash command(由 `harnessed setup` 生成于 `~/.claude/commands/plan.md`)。
+它以 CC-native 方式驱动:`harnessed gates` 决定哪些 sub fire,`harnessed prompt <sub>` 给出每个
+spawn-ready prompt,然后用 CC-native subagent(Task / Agent 工具)逐个 spawn 已 fire 的 sub,
+每个结果用 `harnessed checkpoint` 记录。完整 state-machine 步骤见 `~/.claude/commands/plan.md`;
+若该文件不存在,自行按 gates → prompt → spawn → checkpoint 同序执行。
 
-若 `$ARGUMENTS` 为空，运行 `harnessed run plan`（不带 stdin pipe）。
-
-完成后，Bash 输出会在 stderr 打印 `Next:` 提示，建议下一阶段。是否调用由对话上下文决定——该提示仅供参考，非强制指令。
-
-<!-- harnessed-generated:v3.4.4 -->
+<!-- harnessed-generated:v4.9.1 -->
 
 ## 参考文档
 

package/workflows/plan/phase/SKILL.md

@@ -56,17 +56,18 @@ reframe)。
 
 ## How to invoke
 
-Use the Bash tool to run:
-
-```bash
-echo "$ARGUMENTS" | harnessed run plan-phase --task-stdin
-```
-
-If `$ARGUMENTS` is empty, run `harnessed run plan-phase` (no stdin pipe).
-
-After completion, the Bash output prints a `Next:` hint on stderr suggesting the next stage. Decide whether to invoke based on conversation context — the hint is informational, not prescriptive.
-
-<!-- harnessed-generated:v3.4.4 -->
+Orchestrated CC-natively. Do NOT pipe to `harnessed run plan-phase` — that is the CI/headless
+path (an in-process SDK spawn that blocks the session, bypasses Agent Teams, and hangs when
+invoked from inside a Claude Code session).
+
+Run the `/plan-phase` slash command instead (generated by `harnessed setup` at
+`~/.claude/commands/plan-phase.md`). It drives the stage natively: `harnessed gates` → which
+subs fire, `harnessed prompt <sub>` → each spawn-ready prompt, then a CC-native subagent
+(Task / Agent tool) per fired sub, recording each outcome with `harnessed checkpoint`. The
+full state-machine steps live in `~/.claude/commands/plan-phase.md`; if that file is absent,
+follow that same gates → prompt → spawn → checkpoint sequence yourself.
+
+<!-- harnessed-generated:v4.9.1 -->
 
 ## References
 

package/workflows/plan/phase/SKILL.zh-Hans.md

@@ -56,17 +56,16 @@ reframe）。
 
 ## 如何调用
 
-使用 Bash 工具运行：
+CC-native 编排。**不要** pipe 到 `harnessed run plan-phase` —— 那是 CI/headless 路径(in-process
+SDK spawn,会阻塞 session、绕过 Agent Teams,在 Claude Code 内部调用时还会挂死)。
 
-```bash
-echo "$ARGUMENTS" | harnessed run plan-phase --task-stdin
-```
+改用 `/plan-phase` slash command(由 `harnessed setup` 生成于 `~/.claude/commands/plan-phase.md`)。
+它以 CC-native 方式驱动:`harnessed gates` 决定哪些 sub fire,`harnessed prompt <sub>` 给出每个
+spawn-ready prompt,然后用 CC-native subagent(Task / Agent 工具)逐个 spawn 已 fire 的 sub,
+每个结果用 `harnessed checkpoint` 记录。完整 state-machine 步骤见 `~/.claude/commands/plan-phase.md`;
+若该文件不存在,自行按 gates → prompt → spawn → checkpoint 同序执行。
 
-若 `$ARGUMENTS` 为空，运行 `harnessed run plan-phase`（不带 stdin pipe）。
-
-完成后，Bash 输出会在 stderr 打印 `Next:` 提示，建议下一阶段。是否调用由对话上下文决定——该提示仅供参考，非强制指令。
-
-<!-- harnessed-generated:v3.4.4 -->
+<!-- harnessed-generated:v4.9.1 -->
 
 ## 参考文档
 

package/workflows/research/SKILL.md

@@ -39,43 +39,15 @@ Sister `workflows/capabilities.yaml` entries:
 
 ## How to invoke
 
-**Preferred path** (master orchestrator): dispatch to the per-sub-workflow slash commands in the order this stage prescribes. Each sub command lives at `<claude-home>/commands/<sub-name>.md` (installed by `harnessed setup`) with its own dual-path fallback.
-
-**Fallback path** (when the upstream isn't installed or returns no result): use the Task tool to spawn a general-purpose subagent with this prompt:
-
-> You are a **Research analyst**.
->
-> **Mission**: Multi-source investigation (docs / web search / codebase grep / library probe) producing a `findings.md` with citations, NOT speculation. Use `ctx7` for library docs, `tavily-mcp` / `exa-mcp` for web, `gh` CLI for GitHub artifacts, and codebase `Grep` for internal references.
->
-> **Default-suspect mode**: assume the change is broken / risky / incomplete until proven otherwise. Cite `file:line` for every finding; do not generalize.
->
-> **Review checklist**:
-> 1. Resolve each unknown claim to a citable source (URL, file:line, or `ctx7` doc id)
->
-> 2. Cite version explicitly when discussing library / framework APIs (training cutoff may be stale)
->
-> 3. Capture conflicting sources side-by-side; do not silently pick one
->
-> 4. Flag `OPEN: <question>` for items the user must decide; never paper over
->
-> 5. Persist results to `.planning/<phase>/findings.md` for cross-session handoff
->
-> **Output format**: structured report with severity-classified findings (verified / unverified / conflicting / open). One finding per line: `[severity] file:line — problem (one sentence); fix: suggested change`. If no findings, say so explicitly. No preamble, no end-of-report summary.
-
-(Role prompt is self-contained — works even when the upstream `specialist` user-skill / plugin isn't installed.)
-
-(`harnessed setup` also installs a `research` Claude Code slash command at `<claude-home>/commands/research.md` so `/research` is a real platform slash command — both files carry the same dual-path instruction. Previous v3.4.x `harnessed research --apply` CLI claims are removed; that subcommand was never implemented.)
-
-## How to invoke
-
-Use the Bash tool to run:
-
-```bash
-echo "$ARGUMENTS" | harnessed run research --task-stdin
-```
-
-If `$ARGUMENTS` is empty, run `harnessed run research` (no stdin pipe).
-
-After completion, the Bash output prints a `Next:` hint on stderr suggesting the next stage. Decide whether to invoke based on conversation context — the hint is informational, not prescriptive.
-
-<!-- harnessed-generated:v3.4.4 -->
+Orchestrated CC-natively. Do NOT pipe to `harnessed run research` — that is the CI/headless
+path (an in-process SDK spawn that blocks the session, bypasses Agent Teams, and hangs when
+invoked from inside a Claude Code session).
+
+Run the `/research` slash command instead (generated by `harnessed setup` at
+`~/.claude/commands/research.md`). It drives the stage natively: `harnessed gates` → which
+subs fire, `harnessed prompt <sub>` → each spawn-ready prompt, then a CC-native subagent
+(Task / Agent tool) per fired sub, recording each outcome with `harnessed checkpoint`. The
+full state-machine steps live in `~/.claude/commands/research.md`; if that file is absent,
+follow that same gates → prompt → spawn → checkpoint sequence yourself.
+
+<!-- harnessed-generated:v4.9.1 -->