harnessed 3.4.3 → 3.5.0

package/dist/index.mjs

@@ -1,6 +1,6 @@
 // package.json
 var package_default = {
-  version: "3.4.3"};
+  version: "3.5.0"};
 
 // 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,OA8Fb,CAAA;;;AC3FO,IAAM,UAAU,eAAA,CAAI","file":"index.mjs","sourcesContent":["{\n  \"name\": \"harnessed\",\n  \"version\": \"3.4.3\",\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  },\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    \"manifests\",\n    \"workflows\",\n    \"routing\",\n    \"config-templates\",\n    \"schemas\",\n    \"README.md\",\n    \"LICENSE\",\n    \"NOTICE\"\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,OA8Fb,CAAA;;;AC3FO,IAAM,UAAU,eAAA,CAAI","file":"index.mjs","sourcesContent":["{\n  \"name\": \"harnessed\",\n  \"version\": \"3.5.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  },\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    \"manifests\",\n    \"workflows\",\n    \"routing\",\n    \"config-templates\",\n    \"schemas\",\n    \"README.md\",\n    \"LICENSE\",\n    \"NOTICE\"\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/package.json

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

package/workflows/auto/SKILL.md

@@ -103,14 +103,20 @@ Sister `workflows/capabilities.yaml`:
 - 4 stage-master `/discuss /plan /task /verify` 仍可独立 invoke — `/auto` 是 opt-in NEW workflow
 - `--staged` opt-in for stage gate UX (每 stage 完停 user review)
 
-<!-- v3.4.3-dual-path-invocation -->
 ## 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/commands/<sub-name>.md` with its own dual-path fallback.
+Use the Bash tool to run:
 
-**Fallback path** (when no slash command from the sub-list resolves): run each missing sub-workflow inline using its own role prompt from `~/.claude/skills/<sub-name>/SKILL.md`. Do NOT skip stages silently — each sub either runs or is logged as "skipped: <reason>".
+```bash
+echo "$ARGUMENTS" | harnessed run auto --task-stdin
+```
 
-(Sister `~/.claude/commands/auto.md` is also generated by `harnessed setup` so `/auto` is a real platform slash command — both files carry the same dual-path instruction. Previous v3.4.x `harnessed auto --apply` CLI claims are removed; that subcommand was never implemented.)
+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 -->
 
 ## References
 

package/workflows/capabilities.yaml

@@ -70,9 +70,9 @@ capabilities:
 
   caveman:
     # v3.4.2: dual-install ("互为补充") — caveman ships BOTH as user-skill
-    # (git clone caveman repo into ~/.claude/skills/caveman/) AND as Claude Code
-    # plugin (`caveman@caveman` in installed_plugins.json). Resolver detects
-    # either; emits combined warning only if BOTH are missing.
+    # (git clone caveman repo into <claude-home>/skills/caveman/) AND as Claude
+    # Code plugin (`caveman@caveman` in installed_plugins.json). Resolver
+    # detects either; emits combined warning only if BOTH are missing.
     impl: caveman
     install_type: [user-skill, plugin]
     skill_dir: caveman
@@ -179,7 +179,7 @@ capabilities:
     cmd: /ui-ux-pro-max
     since: v2.0
     category: tool-slash-cmd
-    description: UI/UX 默认主方案 数据驱动 (per ~/.claude/rules/web-design.md L5)
+    description: UI/UX 默认主方案 数据驱动
     fires_when:
       - phase.has_ui_changes == true
       - subtask.type == 'ui_polish'
@@ -192,7 +192,7 @@ capabilities:
     cmd: /frontend-design
     since: v2.0
     category: tool-slash-cmd
-    description: UI 创意/装饰补充 (per ~/.claude/rules/web-design.md L11)
+    description: UI 创意/装饰补充
     fires_when:
       - phase.has_ui_changes == true AND phase.requires_creative_polish == true
 
@@ -201,7 +201,7 @@ capabilities:
     cmd: playwright
     since: v2.0
     category: tool-bundled-skill
-    description: AI 实时操作浏览器 一行 Bash (per ~/.claude/rules/web-testing.md L8 手)
+    description: "AI 实时操作浏览器 一行 Bash (手层 — 探查 / 调试 / 一次性交互)"
     fires_when:
       - subtask.type == 'browser_probe'
 
@@ -210,7 +210,7 @@ capabilities:
     cmd: "@playwright/test"
     since: v2.0
     category: tool-plugin
-    description: E2E test framework TypeScript (per ~/.claude/rules/web-testing.md L8 脑)
+    description: "E2E test framework TypeScript (脑层 — 写测试 / 跑 CI / 断言 / fixtures / reporter)"
     fires_when:
       - subtask.type == 'e2e_test' AND subtask.language == 'typescript'
 
@@ -221,7 +221,7 @@ capabilities:
     cmd: /webapp-testing
     since: v2.0
     category: tool-bundled-skill
-    description: Python 后端联动 E2E (per ~/.claude/rules/web-testing.md L11 筋骨)
+    description: "Python 后端联动 E2E (筋骨层 — Python Playwright + with_server.py)"
     fires_when:
       - subtask.type == 'e2e_test' AND subtask.language == 'python'
 
@@ -230,7 +230,7 @@ capabilities:
     cmd: chrome-devtools
     since: v2.0
     category: tool-mcp
-    description: 性能/a11y/内存泄漏诊断 (per ~/.claude/rules/web-testing.md L45 非功能性)
+    description: 性能/a11y/内存泄漏诊断 (非功能性 only; NOT for E2E test)
     fires_when:
       - subtask.type in ['perf_diagnose', 'a11y_audit', 'memory_leak']
 
@@ -239,7 +239,7 @@ capabilities:
     cmd: ctx7
     since: v2.0
     category: tool-cli
-    description: 库 API/框架/SDK 文档抓取 (per ~/.claude/rules/context7.md)
+    description: 库 API/框架/SDK 文档抓取
     fires_when:
       - subtask.needs_library_docs == true
 
@@ -248,7 +248,7 @@ capabilities:
     cmd: tavily_search
     since: v2.0
     category: tool-mcp
-    description: Web 搜索默认 (关键词/库 API/时效) per ~/.claude/rules/web-search.md L17
+    description: Web 搜索默认 (关键词/库 API/时效)
     fires_when:
       - subtask.needs_web_search == true
 
@@ -257,7 +257,7 @@ capabilities:
     cmd: web_fetch_exa
     since: v2.0
     category: tool-mcp
-    description: 描述式/学术 Web 搜索 per ~/.claude/rules/web-search.md L24
+    description: "描述式/学术 Web 搜索 (覆盖默认 Tavily 的场景 — 描述式查询 / 学术 / 批量抓多 URL)"
     fires_when:
       - subtask.needs_web_search == true AND subtask.search_type in ['descriptive', 'academic']
 
@@ -432,7 +432,6 @@ capabilities:
     description: Manus-style persistent markdown planning (Claude Code plugin slash cmd)
     requires:
       plugin: planning-with-files >=2.2.0
-    plugin_path: ~/.claude/plugins/cache/planning-with-files/planning-with-files/2.34.0
     outputs:
       - task_plan.md
       - progress.md
@@ -451,7 +450,7 @@ capabilities:
     since: v2.0
     category: tool-bundled-skill
     description: Sub-task completion gate (verbatim COMPLETE; max-iterations fallback)
-    sdk_ref: src/routing/lib/ralphLoop.ts
+    sdk_ref: src/workflow/lib/ralphLoop.ts
     fires_when:
       - subtask.completion_required == true
 
@@ -469,14 +468,14 @@ capabilities:
 
   # ============================================================================
   # Bucket 5 — Agent Teams 3 升级触发 (per D-11 + Q-AUDIT-5b schema fix +
-  #            ~/.claude/rules/agent-teams.md L7 prereq)
+  #            bundled Agent Teams prerequisite: CC 2.1.133+ + env var)
   # ============================================================================
   #
   # Q-AUDIT-5b 2026-05-20 fix: settings_env_var root-level `env.CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS`
   # (NOT nested experimental.* — Wave A 本地 settings.json 实证修正 prior schema 错误)。
   # Per Q-AUDIT-2 D-11: harnessed doctor + setup 检查 env var present + cc_version ≥2.1.133。
   #
-  # 5 fires_when OR-chain (multi-select per ~/.claude/rules/agent-teams.md 升级触发):
+  # 5 fires_when OR-chain (multi-select; Agent Teams upgrade triggers):
   #   1. teammate_send_message_needed — teammate 间需 SendMessage 互通 (NOT fire-and-forget)
   #   2. subagent_context_overflow    — 某 subagent 撞 context 上限需分担
   #   3. shared_task_list             — 多 teammate 共享 task list 自协调
@@ -487,7 +486,7 @@ capabilities:
     cmd: TeamCreate
     since: v2.0
     category: agent-platform
-    description: Agent Teams team 创建 (CC 2.1.133+ experimental; per agent-teams.md L7)
+    description: Agent Teams team 创建 (CC 2.1.133+ experimental)
     requires:
       settings_env_var: env.CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS == "1"
       cc_version: ">=2.1.133"
@@ -513,7 +512,7 @@ capabilities:
     cmd: TeamDelete
     since: v2.0
     category: agent-platform
-    description: Agent Teams cleanup (shutdown_request 之后 TeamDelete; sister agent-teams.md 防呆清单)
+    description: Agent Teams cleanup (shutdown_request 之后 TeamDelete; mandatory cleanup discipline)
     requires:
       settings_env_var: env.CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS == "1"
       cc_version: ">=2.1.133"
@@ -993,7 +992,7 @@ capabilities:
       - subtask.parallel_count <= 3
       - subtask.communication_needed == false
 
-  # D-11 NEW google-workspace.yaml (gws CLI per ~/.claude/rules/google-workspace.md)
+  # D-11 NEW google-workspace.yaml (gws CLI — Google Workspace OAuth2 keyring auth)
   gws:
     impl: cli
     cmd: gws

package/workflows/disciplines/karpathy.yaml

@@ -1,5 +1,5 @@
 # workflows/disciplines/karpathy.yaml
-# karpathy 心法 + 编码硬限 — 机器化 ~/.claude/CLAUDE.md 「andrej-karpathy-skills」 节
+# karpathy 心法 + 编码硬限 — bundled discipline (think-before-coding / simplicity-first / surgical-changes / goal-driven)
 # Phase v3.0-3.3 W0.4 ship per D-09 (L0 Discipline Substrate)
 # Snapshot of CLAUDE.md as of v3.0 ship date (K7 mitigation, verbatim)
 

package/workflows/disciplines/language.yaml

@@ -20,7 +20,7 @@ rules:
       stay consistent with CLI tone.
     enforcement: info
     trigger: every Claude response
-    check_method: read ~/.claude/settings.json env.HARNESSED_USER_LANG, validate output lang matches
+    check_method: read env.HARNESSED_USER_LANG, validate output lang matches
 
   - id: preserve-english-categories
     description: 8 类强制保留英文原文,不翻译不音译 (语言无关 — 任何 user_lang 都适用)

package/workflows/disciplines/operational.yaml

@@ -1,6 +1,6 @@
 # workflows/disciplines/operational.yaml
-# 操作纪律 — 机器化 project CLAUDE.md (biome preempt + commit safety) +
-# ~/.claude/CLAUDE.md (A7 ADR / no-skip-hooks / authorization-not-transitive)
+# 操作纪律 — bundled discipline (biome preempt + commit safety +
+# A7 ADR + no-skip-hooks + authorization-not-transitive + destructive-ops-explicit)
 # Phase v3.0-3.3 W0.4 ship per D-09
 # Snapshot of CLAUDE.md as of v3.0 ship date (K7 mitigation, verbatim)
 

package/workflows/disciplines/output-style.yaml

@@ -1,5 +1,5 @@
 # workflows/disciplines/output-style.yaml
-# 对话回答风格 — 机器化 ~/.claude/CLAUDE.md 「对话回答风格」 节
+# 对话回答风格 — bundled discipline (BLUF + no-sycophantic + no-emoji + no-em-dash + 量词精确 + no-end-recap + no-empty-continuation-question)
 # Phase v3.0-3.3 W0.4 ship per D-09
 # Snapshot of CLAUDE.md as of v3.0 ship date (K7 mitigation, verbatim)
 

package/workflows/disciplines/priority.yaml

@@ -1,5 +1,5 @@
 # workflows/disciplines/priority.yaml
-# 优先级仲裁 — 机器化 ~/.claude/CLAUDE.md 「响应规范与优先级」 节
+# 优先级仲裁 — bundled discipline (7-tier hierarchy: gstack > gsd > superpowers > planning-with-files > karpathy > mattpocock > parallel)
 # Phase v3.0-3.3 W0.4 ship per D-09
 # Snapshot of CLAUDE.md as of v3.0 ship date (K7 mitigation, verbatim)
 

package/workflows/disciplines/protocols.yaml

@@ -1,5 +1,5 @@
 # workflows/disciplines/protocols.yaml
-# 跨 CC instance 协议 — 机器化 ~/.claude/rules/cc-handoff.md (Ideation→Onboarding +
+# 跨 CC instance 协议 — bundled cc-handoff protocols (Ideation→Onboarding +
 # Plan→Execute) + 写入边界表
 # Phase v3.0-3.3 W0.4 ship per D-09
 # Snapshot of CLAUDE.md as of v3.0 ship date (K7 mitigation, verbatim)

package/workflows/discuss/auto/SKILL.md

@@ -20,7 +20,7 @@ trigger_phrases:
 ## Overview
 
 4-stage cadence Stage ① master orchestrator delegating to 3 independent sub-workflows
-(per ~/.claude/CLAUDE.md "澄清/审查触发判据" 节 三层独立判断):
+(bundled 3-tier independent clarification: strategic / phase / subtask):
 
 | sub | gate ref | mode | when fires |
 | --- | -------- | ---- | ---------- |
@@ -51,21 +51,25 @@ Sister `workflows/capabilities.yaml`:
 
 - Slash command: `/discuss <text>` (bare per ADR 0030 namespace policy D-02 LOCK after `harnessed setup`)
 
-<!-- v3.4.3-dual-path-invocation -->
 ## 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/commands/<sub-name>.md` with its own dual-path fallback.
+Use the Bash tool to run:
 
-**Fallback path** (when no slash command from the sub-list resolves): run each missing sub-workflow inline using its own role prompt from `~/.claude/skills/<sub-name>/SKILL.md`. Do NOT skip stages silently — each sub either runs or is logged as "skipped: <reason>".
+```bash
+echo "$ARGUMENTS" | harnessed run discuss --task-stdin
+```
 
-(Sister `~/.claude/commands/discuss.md` is also generated by `harnessed setup` so `/discuss` is a real platform slash command — both files carry the same dual-path instruction. Previous v3.4.x `harnessed discuss --apply` CLI claims are removed; that subcommand was never implemented.)
+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 -->
 
 ## References
 
 - D-01 master orchestrator delegation pattern
 - D-02 bare slash cmd convention (ADR 0030 namespace policy LOCK)
 - D-04 Stage ① Discuss 三层独立判
-- ~/.claude/CLAUDE.md "澄清/审查触发判据" 节 verbatim
 - workflows/judgments/stage-routing.yaml — discuss-{strategic,phase,subtask}-delegate triggers
 - workflows/discuss/{strategic,phase,subtask}/workflow.yaml — 3 sub-workflow Phase 3.4 SHIPPED
 - workflows/judgments/fallback.yaml — 链式互不前置 chain-isolation 铁律

package/workflows/discuss/auto/workflow.yaml

@@ -1,11 +1,10 @@
 # workflows/discuss/auto/workflow.yaml — Phase v3.0-3.5 W1 T3.5.W1.1
 #
 # Stage ① Discuss master orchestrator — 3 sub-workflow parallel gate-eval (chain-isolation 铁律
-# per ~/.claude/CLAUDE.md "澄清/审查触发判据" 节 + fallback.yaml "链式互不前置")。
+# per bundled 3-tier clarification gate + fallback.yaml "链式互不前置")。
 # 3 sub 独立判 gate, 可能全跑 / 1-2 个 / 全跳 + 透明声明。
 #
 # Sister refs:
-#   - ~/.claude/CLAUDE.md "澄清/审查触发判据" 节 (战略 / Phase / 子任务三层独立判)
 #   - workflows/judgments/stage-routing.yaml — discuss-{strategic,phase,subtask}-delegate triggers
 #   - workflows/discuss/{strategic,phase,subtask}/workflow.yaml — 3 sub-workflow Phase 3.4 SHIPPED
 #   - workflows/capabilities.yaml — planning-with-files (discuss sink findings.md)

package/workflows/discuss/phase/SKILL.md

@@ -51,42 +51,23 @@ Sister `workflows/judgments/phase-gate.yaml`:
 - < 1 天工作量
 - bug 修复且已有最小复现
 
-<!-- v3.4.3-dual-path-invocation -->
 ## How to invoke
 
-**Preferred path** (when the upstream specialist is installed): use the SlashCommand tool to run `{{ capabilities.gsd-discuss-phase.cmd }}` — the upstream specialist takes over.
-
-**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 **Phase clarification analyst**.
->
-> **Mission**: Surface and resolve gray-area implementation decisions BEFORE a phase enters planning. Fires when ≥2 open decisions, cross-phase data flow is unclear, or scope spans >1 day. Adapted from GSD `/gsd-discuss-phase`.
->
-> **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. List every open decision as a single question (1 line each)
->
-> 2. For each, list 2-4 candidate answers with one-line tradeoffs
->
-> 3. Identify cross-phase contracts (data flow / API shape / migration order)
->
-> 4. Flag decisions blocking start (must answer before plan) vs. deferrable
->
-> 5. Persist to `.planning/<phase>/findings.md` + `knowledge.md` for hand-off
->
-> 6. If the layer is genuinely clear, say 'no clarification needed' and exit
->
-> **Output format**: structured report with severity-classified findings (blocking / deferrable / resolved). 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 `gsd-discuss-phase` user-skill / plugin isn't installed.)
-
-(Sister `~/.claude/commands/discuss-phase.md` is also generated by `harnessed setup` so `/discuss-phase` is a real platform slash command — both files carry the same dual-path instruction. Previous v3.4.x `harnessed discuss-phase --apply` CLI claims are removed; that subcommand was never implemented.)
+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 -->
 
 ## References
 
 - D-04 Stage ① Discuss 三层 (战略 / phase / 子任务)
-- ~/.claude/CLAUDE.md "Phase 层: GSD /gsd-discuss-phase"
 - workflows/capabilities.yaml — gsd-discuss-phase / planning-with-files
 - workflows/judgments/phase-gate.yaml — gsd-discuss-phase trigger
 - workflows/defaults.yaml — ralph_max_iterations.discuss-phase.* values (W2.2 backfill)

package/workflows/discuss/phase/workflow.yaml

@@ -1,7 +1,7 @@
 # workflows/discuss/phase/workflow.yaml — Phase v3.0-3.4 W0 T3.4.W0.2
 #
 # Stage ①.b Phase 层 sub-workflow — GSD /gsd-discuss-phase 灰色澄清
-# (sister ~/.claude/CLAUDE.md "澄清/审查触发判据 — Phase 层")。
+# (bundled 3-tier clarification — phase layer).
 #
 # Sister refs:
 #   - workflows/judgments/phase-gate.yaml — gsd-discuss-phase trigger

package/workflows/discuss/strategic/SKILL.md

@@ -2,7 +2,7 @@
 name: discuss-strategic
 description: |
   Stage ①.a 战略层 discuss sub-workflow — gstack /office-hours + /plan-ceo-review 新功能 / 新
-  milestone / 新产品方向启动前强制治理关卡 (sister ~/.claude/CLAUDE.md "🔒 新功能启动前强制")。
+  milestone / 新产品方向启动前强制治理关卡 (bundled gstack governance gate, mandatory before new-feature)。
   schema_version: harnessed.workflow.v3 with disciplines_applied (6 default) + tools_available
   (gstack-office-hours + gstack-plan-ceo-review + planning-with-files) + 3 phases (gate
   judgments.strategic-gate.* fires + planning-with-files /plan findings.md 持久化)。
@@ -55,45 +55,24 @@ Sister `workflows/judgments/strategic-gate.yaml`:
 - continuing 已有 phase 的执行
 - 用户已给明确 ticket / spec
 
-<!-- v3.4.3-dual-path-invocation -->
 ## How to invoke
 
-**Preferred path** (when the upstream specialist is installed): use the SlashCommand tool to run `{{ capabilities.gstack-office-hours.cmd }}` — the upstream specialist takes over.
-
-**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 **Strategic Office-Hours advisor (CEO + Product lens)**.
->
-> **Mission**: Stress-test the product / scope / business value of a new feature, milestone, or project BEFORE engineering investment. Adapted from gstack `/office-hours` + `/plan-ceo-review`.
->
-> **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. What user problem does this solve? Who specifically experiences it today?
->
-> 2. Why this, why now? (alternative cost of working on something else)
->
-> 3. What does success look like — measurable, not vibes (1 metric, not 5)?
->
-> 4. Is the scope MVP-able? What's the smallest cut that still proves the bet?
->
-> 5. What assumptions are load-bearing? Which would kill the feature if wrong?
->
-> 6. Who pays the maintenance cost after ship — same team, or a hand-off?
->
-> 7. Decision: ship / iterate / kill / table — with one-line reason
->
-> **Output format**: structured report with severity-classified findings (ship / iterate / kill / table (each with reason)). 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 `gstack-office-hours` user-skill / plugin isn't installed.)
-
-(Sister `~/.claude/commands/discuss-strategic.md` is also generated by `harnessed setup` so `/discuss-strategic` is a real platform slash command — both files carry the same dual-path instruction. Previous v3.4.x `harnessed discuss-strategic --apply` CLI claims are removed; that subcommand was never implemented.)
+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 -->
 
 ## References
 
 - D-04 Stage ① Discuss 三层 (战略 / phase / 子任务)
 - D-12 gstack 治理关卡强制
-- ~/.claude/CLAUDE.md "gstack 治理关卡 🔒 新功能启动前强制"
 - workflows/capabilities.yaml — gstack-office-hours / gstack-plan-ceo-review / planning-with-files
 - workflows/judgments/strategic-gate.yaml — office-hours / plan-ceo-review triggers
 - workflows/defaults.yaml — ralph_max_iterations.discuss-strategic.* values (W2.2 backfill)

package/workflows/discuss/strategic/workflow.yaml

@@ -1,11 +1,10 @@
 # workflows/discuss/strategic/workflow.yaml — Phase v3.0-3.4 W0 T3.4.W0.1
 #
 # Stage ①.a 战略层 sub-workflow — gstack 治理关卡 /office-hours + /plan-ceo-review
-# 新功能 / 新 milestone / 新产品方向启动前强制 (sister ~/.claude/CLAUDE.md
-# "gstack 治理关卡 🔒 新功能启动前强制" verbatim)。
+# 新功能 / 新 milestone / 新产品方向启动前强制 (bundled gstack governance gate —
+# mandatory before new-project / new-milestone / new-feature phases).
 #
 # Sister refs:
-#   - ~/.claude/CLAUDE.md "澄清/审查触发判据 — 战略层" 章节
 #   - workflows/judgments/strategic-gate.yaml — office-hours / plan-ceo-review triggers
 #   - workflows/capabilities.yaml — gstack-office-hours / gstack-plan-ceo-review / planning-with-files
 #   - src/workflow/schema/workflow.ts WorkflowSchemaV3 (Phase 3.3 W0.5 SHIPPED)

package/workflows/discuss/subtask/SKILL.md

@@ -56,43 +56,24 @@ Sister `workflows/judgments/subtask-gate.yaml`:
 - 标准库直接调用
 - bug 修复且已知根因
 
-<!-- v3.4.3-dual-path-invocation -->
 ## How to invoke
 
-**Preferred path** (when the upstream specialist is installed): use the SlashCommand tool to run `{{ capabilities.superpowers-brainstorming.cmd }}` — the upstream specialist takes over.
-
-**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 **Subtask brainstormer**.
->
-> **Mission**: Generate ≥2 implementation approaches for a single subtask and compare tradeoffs. Fires when core algorithm / data structure / API contract / high error-cost. Skip pure CRUD or single-obvious-path tasks.
->
-> **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. State the subtask in one sentence; confirm scope with user if ambiguous
->
-> 2. Produce 2-4 distinct approaches (not just '2 flavors of the same idea')
->
-> 3. For each: complexity, perf, failure modes, test surface, future change cost
->
-> 4. Recommend one with 1-2 line reason; flag risks of the chosen path
->
-> 5. Output a `findings.md` block the implementer can paste into the task
->
-> 6. If options collapse to one (others clearly bad), say so and exit fast
->
-> **Output format**: structured report with severity-classified findings (recommended / acceptable / rejected). 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 `superpowers-brainstorming` user-skill / plugin isn't installed.)
-
-(Sister `~/.claude/commands/discuss-subtask.md` is also generated by `harnessed setup` so `/discuss-subtask` is a real platform slash command — both files carry the same dual-path instruction. Previous v3.4.x `harnessed discuss-subtask --apply` CLI claims are removed; that subcommand was never implemented.)
+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 -->
 
 ## References
 
 - D-04 Stage ① Discuss 三层 (战略 / phase / 子任务)
 - D-05 phase.invokes_tools conditional fire (NEW v3)
-- ~/.claude/CLAUDE.md "子任务层: superpowers:brainstorming"
 - workflows/capabilities.yaml — superpowers-brainstorming / grill-with-docs / grill-me
 - workflows/judgments/subtask-gate.yaml — brainstorming trigger
 - workflows/defaults.yaml — ralph_max_iterations.discuss-subtask.* values (W2.2 backfill)

package/workflows/discuss/subtask/workflow.yaml

@@ -1,7 +1,7 @@
 # workflows/discuss/subtask/workflow.yaml — Phase v3.0-3.4 W0 T3.4.W0.3
 #
 # Stage ①.c 子任务层 sub-workflow — superpowers brainstorming (≥2 approach / 核心算法 /
-# API contract / 错误成本高)。Sister ~/.claude/CLAUDE.md "澄清/审查触发判据 — 子任务层"。
+# API contract / 错误成本高). Bundled 3-tier clarification — subtask layer.
 #
 # Sister refs:
 #   - workflows/judgments/subtask-gate.yaml — brainstorming trigger

package/workflows/execute-task/SKILL.md

@@ -38,10 +38,11 @@ v2 schema fields per `src/workflow/schema/workflow.ts` (T2.4.W0.1 16th surface
 - `parallelism: judgments.parallelism-gate.<route>.fires` (D-11 subagent / Agent Teams / main session route)
 - `fallback.max_iterations_exceeded: {action, message, exit_code}` (R20.10 acceptance c "explicit NOT silent")
 
-Per-phase models load from `workflows/execute-task/phases.yaml`; engine.runRouting
-spawns each phase as a sub-agent via `@anthropic-ai/claude-agent-sdk` 0.3.142+
+Per-phase models load from `workflows/execute-task/workflow.yaml` (v3 SoT post
+v3.4.4 Phase 6 — v2 phases.yaml deleted); runWorkflow spawns each phase as a
+sub-agent via `@anthropic-ai/claude-agent-sdk` 0.3.142+
 (`AgentDefinition` 5-字段 unpack — ADR 0011 § 4). ralph-loop SDK wrapper at 04-deliver
-reuses sister Phase 2.2 v0.2.0 ship: `src/routing/lib/ralphLoop.ts` (54L) + `sdkSpawn.ts` (91L)
+reuses sister Phase 2.2 v0.2.0 ship: `src/workflow/lib/ralphLoop.ts` (54L) + `sdkSpawn.ts` (91L)
 + 4-layer dual-signal `isComplete` (NOT 重写 — per RESEARCH § 3.1).
 
 ## CLI invocation (the only enforced entry — B-28)
@@ -78,6 +79,6 @@ the CLI subcommand above (B-28 single-entry contract).
 - ADR 0011 — execute-task SDK + ralph-loop integration (phase 2.2 W6 — finalize)
 - `.planning/intel/omc-comparison.md` § CD-2 — per-phase model tier defaults
 - `src/cli/execute-task.ts` — CLI implementation (T5.1)
-- `workflows/execute-task/phases.yaml` — 4-phase config (T3.3)
-- `src/routing/lib/sdkSpawn.ts` — SDK query() consumer (T4.1)
-- `src/routing/lib/ralphLoop.ts` — verbatim COMPLETE round-trip
+- `workflows/execute-task/workflow.yaml` — 4-phase config (v3 SoT; v3.4.4 Phase 6 ship — v2 phases.yaml deleted)
+- `src/workflow/lib/sdkSpawn.ts` — SDK query() consumer (T4.1)
+- `src/workflow/lib/ralphLoop.ts` — verbatim COMPLETE round-trip