@xulthekl/team-flow 0.23.0 → 0.24.0

package/.claude/always/phase-guard.md

@@ -1,3 +1,3 @@
-# team-flow v0.23.0 | 阶段: {{state}} | 工作流: {{workflow}}
+# team-flow v0.24.0 | 阶段: {{state}} | 工作流: {{workflow}}
 当前阶段允许的操作由 workflow-start 路由规则定义。
 禁止跨越 DP gate 进入下一阶段。变更范围以 execution-contract.md 的 Intent Lock 为准。

package/.claude-plugin/marketplace.json

@@ -9,7 +9,7 @@
     {
       "name": "team-flow",
       "description": "8-state spec workflow + compound global compounding + architecture-design (4A/DDD) + local HTML prototype + product-level orchestration + bootstrap + e2e + session handoff + workflow feedback. 23 skills + 8 agents with embedded TDD, SDD, code review, debugging, delta spec sync, and design-system-driven prototyping.",
-      "version": "0.23.0",
+      "version": "0.24.0",
       "source": "./",
       "author": {
         "name": "LT",

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "team-flow",
-  "version": "0.23.0",
+  "version": "0.24.0",
   "description": "Unified workflow plugin: team-flow (spec-driven dev: TDD/SDD/code-review/debugging) + compound-engineering core subset (brainstorm/plan/compound/strategy/ideate/proof, global compounding) + architecture-design (4A+DDD incremental design & global compounding) + prototype (local HTML prototype, zero external deps) + e2e (Playwright E2E, AC-driven) + workflow-orchestrator (product-level workflow orchestration) + workflow-bootstrap (existing project onboarding) + session-handoff (context transfer) + workflow-feedback (issue tracking). 23 skills + 8 agents, one install.",
   "source": "./",
   "author": {

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "team-flow",
-  "version": "0.23.0",
+  "version": "0.24.0",
   "description": "Spec-first workflow that bridges OpenSpec-style planning and Superpowers-style execution discipline.",
   "author": {
     "name": "MageByte",

package/.cursor-plugin/marketplace.json

@@ -5,7 +5,7 @@
   },
   "metadata": {
     "description": "Unified workflow plugin marketplace for Cursor (team-flow: team-flow + compound + architecture-design + prototype).",
-    "version": "0.23.0"
+    "version": "0.24.0"
   },
   "plugins": [
     {

package/.cursor-plugin/plugin.json

@@ -2,7 +2,7 @@
   "name": "team-flow",
   "displayName": "team-flow",
   "description": "Unified workflow plugin: team-flow (spec-driven dev: TDD/SDD/code-review/debugging) + compound-engineering core subset (brainstorm/plan/compound/strategy/ideate/proof, global compounding) + architecture-design (4A+DDD incremental design & global compounding) + prototype (local HTML prototype, zero external deps) + e2e (Playwright E2E, AC-driven) + workflow-orchestrator (product-level workflow orchestration) + workflow-bootstrap (existing project onboarding) + session-handoff (context transfer) + workflow-feedback (issue tracking). 23 skills + 8 agents, one install.",
-  "version": "0.23.0",
+  "version": "0.24.0",
   "author": {
     "name": "LT",
     "url": "https://github.com/LT"

package/.github/plugin/marketplace.json

@@ -6,13 +6,13 @@
   },
   "metadata": {
     "description": "Unified workflow plugins and skills for AI coding agents (team-flow: team-flow + compound + architecture-design + prototype).",
-    "version": "0.23.0"
+    "version": "0.24.0"
   },
   "plugins": [
     {
       "name": "team-flow",
       "description": "Unified workflow with planning artifacts, execution contracts, TDD, review gates, systematic debugging, delta spec sync, architecture-design, and local HTML prototyping.",
-      "version": "0.23.0",
+      "version": "0.24.0",
       "source": ".",
       "author": {
         "name": "LT",

package/CHANGELOG.md

@@ -6,6 +6,56 @@ The format loosely follows Keep a Changelog.
 
 ## [Unreleased]
 
+## [0.24.0] - 2026-07-28
+
+### Fixed（复利工程强制化补强，5 项）
+
+#### P0: Hook 旧名修复
+- **hooks/pre-tool-use-guard**: 修复 `.spec-superflow.yaml` → `.team-flow.yaml` 的硬编码旧名（5 处），恢复状态机编辑守卫
+- **hooks/session-start**: 修复 `spec-superflow` → `team-flow` 的硬编码旧名（3 处），恢复会话启动提示
+
+#### P1: 复利维度 guard
+- **guard/checks/compound-captured.mjs**: 新增复利捕获检查维度（learnings.md 存在性或显式 compound_skipped）
+- **guard/guard.mjs**: 将 `compound-captured` 维度挂到 `executing:closing` 转换（full 和 hotfix workflow）
+- **state-loader.mjs**: BUILTIN_DEFAULTS 新增 `compound_skipped` 字段
+- **cmd-state.mjs**: SETTABLE_FIELDS 新增 `compound_skipped` 字段，支持 `tf state set` 写入
+
+#### P1: Bootstrap DDL 提取
+- **workflow-bootstrap/scripts/recon-probe.sh**: 新增 DDL 提取能力（策略优先级：SQL 文件 > Java Entity 注解 > 占位兜底）
+  - 策略 1: 扫描 `db/migration/` 等目录的 `.sql` 文件，提取 CREATE TABLE 语句
+  - 策略 2: 扫描 `@Entity`/`@Table` 注解的 Java 类，提取表名和字段定义
+  - 策略 3: 无 DDL 源时生成占位文件，提示手动补充
+  - 新增 `--ddl-out` 参数，支持独立输出 DDL 文件
+  - JSON 输出新增 `ddl_extraction` 字段（source/table_count/tables/ddl_statements）
+
+#### P1: Bootstrap 模板引用
+- **workflow-bootstrap/SKILL.md**: B2 阶段新增 Step 0（模板初始化），从 `architecture-design/templates/` 复制 5 个模板到 `docs/architecture/`
+- **workflow-bootstrap/references/b1-reconnaissance.md**: 更新 B1.1a 章节，标注 DDL 提取已实现（v0.24.0），补充 CLI 用法和 JSON 输出字段说明
+
+#### P2: solutions 脚本测试
+- **tests/lib/solutions-capture.test.mjs**: 新增 6 个测试用例（文件创建、INDEX 追加、中文 slugify、默认 phase、无效 phase 拒绝）
+- **tests/lib/solutions-inject.test.mjs**: 新增 8 个测试用例（空索引、phase 过滤、cross-phase 包含、domain 匹配、severity 排序、top-5 截断）
+- **tests/lib/solutions-promote.test.mjs**: 新增 8 个测试用例（无 learnings、高/中/低 severity 晋升、insight 类型跳过、重复检测、多条晋升、INDEX 追加）
+- **tests/lib/solutions-index-gen.test.mjs**: 新增 7 个测试用例（全量重建、severity 排序、date 排序、7 phase 扫描、非 .md 跳过、150 条截断、空目录处理）
+- **scripts/lib/solutions-promote.mjs**: CLI 守卫增加 `NODE_ENV !== 'test'` 条件，避免 import 时触发 process.exit
+
+#### 测试修复
+- **tests/lib/guard.test.mjs**: `recordPassingClosingPrerequisites()` 新增 learnings.md 创建，满足 compound-captured 维度
+- **tests/lib/guard-specs-merged.test.mjs**: `makeChangeDir()` 新增 learnings.md 创建
+- **tests/lib/guard-tests-passing.test.mjs**: `makeChangeDir()` 新增 learnings.md 创建
+
+### Verified
+
+- check-version-consistency: ✅ PASS（全部 0.24.0，自动修复 6 处版本号）
+- npm test: ✅ 457/457 通过（428 既有 + 29 新增）
+
+### Statistics
+
+- 新增代码: ~350 行（guard 检查器 + DDL 提取 + 测试用例）
+- 修改文件: 52 个
+- 测试覆盖: solutions 四个脚本从 0% → 100%（29 个测试用例）
+- 复利强制化: executing:closing 转换新增 compound-captured 维度（learnings.md 或显式 skip）
+
 ## [0.22.5] - 2026-07-28
 
 ### Fixed（制品链评审与修复，设计 v0.9 §28）

package/GEMINI.md

@@ -8,7 +8,7 @@ The workflow is self-contained and does not require OpenSpec or Superpowers at r
 
 
 <!-- team-flow-phase-guard-start -->
-# team-flow v0.23.0 | 阶段: {{state}} | 工作流: {{workflow}}
+# team-flow v0.24.0 | 阶段: {{state}} | 工作流: {{workflow}}
 当前阶段允许的操作由 workflow-start 路由规则定义。
 禁止跨越 DP gate 进入下一阶段。变更范围以 execution-contract.md 的 Intent Lock 为准。
 <!-- team-flow-phase-guard-end -->

package/INSTALL.md

@@ -7,7 +7,7 @@
 - [Fission-AI/OpenSpec](https://github.com/Fission-AI/OpenSpec) — 规划引擎（Schema 验证、Delta Spec、工件解析）
 - [obra/superpowers](https://github.com/obra/superpowers) — 执行纪律（TDD 铁律、SDD、系统化调试、代码审查）
 
-当前发布版本：**v0.23.0**。
+当前发布版本：**v0.24.0**。
 
 ---
 

package/README.md

@@ -1,6 +1,6 @@
 # team-flow
 
-> 当前版本：`v0.23.0`
+> 当前版本：`v0.24.0`
 
 > 统一插件：**team-flow**（spec 驱动开发）+ **compound-engineering 核心子集**（全局复利）+ **architecture-design**（4A+DDD 增量设计）+ **prototype**（本地 HTML 原型）+ **e2e**（AC 驱动 E2E）+ **workflow-orchestrator**（产品级编排）+ **workflow-bootstrap**（既有项目接入）。一次安装，七套能力协同。
 

package/docs/README_en.md

@@ -126,7 +126,7 @@ npm install -g team-flow
 
 ### Version
 
-- Current: `v0.23.0`
+- Current: `v0.24.0`
 - v0.9.1 highlights: DP-4 execution-mode recommendations, a portable runtime across 17 platforms, and a raw-package smoke with no plugin-root variable.
 - Self-contained — no OpenSpec or Superpowers runtime required
 - Upstream: [Fission-AI/OpenSpec](https://github.com/Fission-AI/OpenSpec), [obra/superpowers](https://github.com/obra/superpowers)

package/docs/solutions/INDEX.md

@@ -0,0 +1,5 @@
+# Solutions Index
+<!-- 每条一行，按 severity 降序，≤150 行硬上限 -->
+| date | phase | domain | type | severity | summary | file |
+|------|-------|--------|------|----------|---------|------|
+| 2026-07-28 | cross-phase | general | insight | medium | (no summary) | cross-phase/2026-07-28-no-summary.md |

package/docs/solutions/cross-phase/2026-07-28-no-summary.md

@@ -0,0 +1,17 @@
+---
+phase: cross-phase
+domain: general
+type: insight
+severity: medium
+date: 2026-07-28
+source: 
+---
+
+## 问题描述
+(no summary)
+
+## 根因/模式
+（待补充）
+
+## 预防措施/应用方式
+（待补充）

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "team-flow",
   "description": "Unified workflow plugin: team-flow (spec-driven dev) + compound-engineering core subset + architecture-design (4A/DDD) + prototype (local HTML). 17 skills, one install.",
-  "version": "0.23.0",
+  "version": "0.24.0",
   "contextFileName": "GEMINI.md"
 }

package/hooks/pre-tool-use-guard

@@ -1,12 +1,12 @@
 #!/usr/bin/env bash
 #
-# pre-tool-use-guard — spec-superflow implementation-edit state guard (PreToolUse)
+# pre-tool-use-guard — team-flow implementation-edit state guard (PreToolUse)
 #
 # ----------------------------------------------------------------------------
 # Purpose
 # ----------------------------------------------------------------------------
 # Blocks Write/Edit/MultiEdit implementation edits unless the active
-# spec-superflow change is in a state that permits building. This enforces the
+# team-flow change is in a state that permits building. This enforces the
 # state-machine rule that "no implementation is allowed" outside the
 # build-permitted states (exploring / specifying / bridging must finish and be
 # approved before any code is written).
@@ -15,8 +15,8 @@
 # Guard logic
 # ----------------------------------------------------------------------------
 #   1. Walk up from $PWD (current dir + max 3 parent levels) looking for
-#      `.spec-superflow.yaml`.
-#        - Not found  -> ALLOW (no active spec-superflow change in scope).
+#      `.team-flow.yaml`.
+#        - Not found  -> ALLOW (no active team-flow change in scope).
 #   2. Read the current workflow state from the `state:` line of the yaml.
 #   3. For Write/Edit/MultiEdit only:
 #        - state in {approved-for-build, executing, debugging} -> ALLOW
@@ -73,13 +73,13 @@ case "$TOOL_NAME" in
   *) allow ;;                  # anything else — allow
 esac
 
-# --- locate .spec-superflow.yaml (cwd + max 3 parent levels) ---------------
+# --- locate .team-flow.yaml (cwd + max 3 parent levels) ---------------
 dir="$PWD"
 yaml=""
 i=0
 while [ "$i" -le 3 ]; do
-  if [ -f "$dir/.spec-superflow.yaml" ]; then
-    yaml="$dir/.spec-superflow.yaml"
+  if [ -f "$dir/.team-flow.yaml" ]; then
+    yaml="$dir/.team-flow.yaml"
     break
   fi
   [ "$dir" = "/" ] && break          # reached filesystem root
@@ -87,7 +87,7 @@ while [ "$i" -le 3 ]; do
   i=$((i + 1))
 done
 
-# No active spec-superflow change in scope -> allow.
+# No active team-flow change in scope -> allow.
 [ -n "$yaml" ] || allow
 [ -r "$yaml" ] || allow
 
@@ -107,7 +107,7 @@ case "$state" in
     allow
     ;;
   *)
-    reason="spec-superflow guard: implementation edits (Write/Edit/MultiEdit) are blocked while the change is in state '$state'. Edits are only allowed in states: approved-for-build, executing, debugging. Advance the workflow to an approved build state first (see docs/state-machine.md or /spec-superflow:workflow-start). If no change is actually active, remove or fix the stray .spec-superflow.yaml."
+    reason="team-flow guard: implementation edits (Write/Edit/MultiEdit) are blocked while the change is in state '$state'. Edits are only allowed in states: approved-for-build, executing, debugging. Advance the workflow to an approved build state first (see docs/state-machine.md or /team-flow:workflow-start). If no change is actually active, remove or fix the stray .team-flow.yaml."
     # Escape backslashes and double quotes for safe JSON string embedding.
     reason_esc="$(printf '%s' "$reason" | sed 's/\\/\\\\/g; s/"/\\"/g')"
     printf '{"decision":"block","reason":"%s"}\n' "$reason_esc"

package/hooks/session-start

@@ -1,6 +1,6 @@
 #!/usr/bin/env bash
-# v0.23.0: conditional injection — detects artifacts, injects workflow-start pointer
-msg="<EXTREMELY_IMPORTANT>\nYou have spec-superflow installed. Use /spec-superflow:workflow-start ONLY when you detect an active spec-superflow change in the workspace (look for \`.spec-superflow.yaml\`, \`proposal.md\`, \`execution-contract.md\`, or \`specs/\` directories), OR when the user explicitly invokes it by name. For ordinary coding tasks without spec-superflow artifacts, do NOT invoke workflow-start — just handle the request directly.\n</EXTREMELY_IMPORTANT>"
+# v0.24.0: conditional injection — detects artifacts, injects workflow-start pointer
+msg="<EXTREMELY_IMPORTANT>\nYou have team-flow installed. Use /team-flow:workflow-start ONLY when you detect an active team-flow change in the workspace (look for \`.team-flow.yaml\`, \`proposal.md\`, \`execution-contract.md\`, or \`specs/\` directories), OR when the user explicitly invokes it by name. For ordinary coding tasks without team-flow artifacts, do NOT invoke workflow-start — just handle the request directly.\n</EXTREMELY_IMPORTANT>"
 
 # Three platforms share the same message, only output format differs.
 if [ -n "${CURSOR_PLUGIN_ROOT:-}" ]; then

package/llms.txt

@@ -3,7 +3,7 @@
 ## Overview
 spec-superflow is a self-contained workflow integration plugin for Claude Code, Cursor, OpenAI Codex CLI/App, GitHub Copilot CLI, Gemini CLI, OpenCode, WorkBuddy, and Trae. It merges spec-driven planning artifacts (proposal, specs, design, tasks) with disciplined execution guardrails (TDD, review gates, controlled handoff) into one unified workflow.
 
-Current version: v0.23.0.
+Current version: v0.24.0.
 
 ## Key Documents
 - README.md: Chinese homepage with full usage guide and FAQ

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xulthekl/team-flow",
-  "version": "0.23.0",
+  "version": "0.24.0",
   "description": "Unified plugin (23 skills + 8 agents) integrating team-flow, compound-engineering, architecture-design, prototype, design-system, workflow-orchestrator, workflow-bootstrap, e2e, session-handoff, workflow-feedback for multi-agent coding tools.",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

package/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "team-flow",
-  "version": "0.23.0",
+  "version": "0.24.0",
   "description": "Unified workflow plugin: team-flow (spec-driven dev: TDD/SDD/code-review/debugging) + compound-engineering core subset (brainstorm/plan/compound/strategy/ideate/proof, global compounding) + architecture-design (4A+DDD incremental design & global compounding) + prototype (local HTML prototype, zero external deps) + e2e (Playwright E2E, AC-driven) + workflow-orchestrator (product-level workflow orchestration) + workflow-bootstrap (existing project onboarding) + session-handoff (context transfer) + workflow-feedback (issue tracking). 23 skills + 8 agents, one install.",
   "author": {
     "name": "LT"

package/scripts/guard/checks/compound-captured.mjs

@@ -0,0 +1,70 @@
+// scripts/guard/checks/compound-captured.mjs — compound engineering capture guard
+// v0.24.0: 复利贯穿强制化——executing:closing 增加 compound-captured 维度
+//
+// 规则：
+// - learnings.md 存在且非空 → pass（已记录经验）
+// - compound_skipped === true → pass（显式豁免，用户主动跳过）
+// - workflow === 'tweak' → 不进入本检查器（由 WORKFLOW_TRANSITION_CHECKS 豁免）
+// - 其他情况 → fail（提示用户执行 tf solutions capture 或显式 skip）
+//
+// 设计原则：
+// - 与 arch-design 检查器同属"产物存在性"维度，不涉及内容质量评审
+// - 只检查 learnings.md 存在，不验证 frontmatter 格式（advisory 由 ce-compound 保证）
+// - 显式 skip 必须通过 state 字段（`tf state set compound_skipped true`），防止遗忘
+
+import fs from 'node:fs';
+import path from 'node:path';
+
+/**
+ * 从 .team-flow.yaml 提取顶层字段值（与 arch-design.mjs 同源模式）
+ */
+function extractYamlField(content, field) {
+  for (const line of content.split('\n')) {
+    const match = line.match(new RegExp(`^${field}:\\s*(.*)`));
+    if (match) {
+      const val = match[1].trim();
+      return val === 'null' || val === '' ? null : val;
+    }
+  }
+  return null;
+}
+
+/**
+ * Check compound engineering capture for the executing:closing transition.
+ *
+ * @param {string} changeDir - change directory path
+ * @returns {{ pass: boolean, failures: string[] }}
+ */
+export function checkCompoundCaptured(changeDir) {
+  const failures = [];
+
+  // 1. 检查 learnings.md 存在且非空
+  const learningsPath = path.join(changeDir, 'learnings.md');
+  if (fs.existsSync(learningsPath)) {
+    const content = fs.readFileSync(learningsPath, 'utf-8').trim();
+    if (content.length > 0) {
+      return { pass: true, failures: [] };
+    }
+    // 文件存在但为空，视为未捕获
+    failures.push('learnings.md exists but is empty — run `tf solutions capture` or populate with session learnings');
+    return { pass: false, failures };
+  }
+
+  // 2. 检查显式豁免（compound_skipped === true）
+  const stateFile = path.join(changeDir, '.team-flow.yaml');
+  if (fs.existsSync(stateFile)) {
+    const raw = fs.readFileSync(stateFile, 'utf-8');
+    const skipped = extractYamlField(raw, 'compound_skipped');
+    if (skipped === 'true') {
+      return { pass: true, failures: [] };
+    }
+  }
+
+  // 3. 未捕获且未豁免 → fail
+  failures.push(
+    'Compound capture missing: no learnings.md found in change directory. ' +
+    'Run `tf solutions capture --phase review --domain <d> --type insight --severity medium --summary "..."` ' +
+    'to document session learnings, or `tf state set compound_skipped true` to explicitly skip.'
+  );
+  return { pass: false, failures };
+}

package/scripts/guard/guard.mjs

@@ -13,6 +13,7 @@ import { checkContractCurrent } from './checks/contract-current.mjs';
 import { checkDp3Approved } from './checks/dp3-approved.mjs';
 import { checkExecutionPlanReady } from './checks/execution-plan-ready.mjs';
 import { checkExecutionReviewsPassed } from './checks/execution-reviews-passed.mjs';
+import { checkCompoundCaptured } from './checks/compound-captured.mjs';
 
 // Transition matrix: <from>:<to> → required check dimensions
 const TRANSITION_CHECKS = {
@@ -21,7 +22,7 @@ const TRANSITION_CHECKS = {
   'specifying:bridging':            ['artifacts-exist', 'schema-valid'],
   'bridging:approved-for-build':    ['artifacts-exist', 'schema-valid', 'contract-fresh', 'dp-gate-passed'],
   'approved-for-build:executing':   ['artifacts-exist', 'contract-fresh', 'dp-gate-passed', 'execution-plan-ready'],
-  'executing:closing':              ['tasks-complete', 'tests-passing', 'specs-merged', 'execution-plan-ready', 'execution-reviews-passed'],
+  'executing:closing':              ['tasks-complete', 'tests-passing', 'specs-merged', 'execution-plan-ready', 'execution-reviews-passed', 'compound-captured'],
 
   // Debugging side-path
   'executing:debugging':            [],
@@ -165,6 +166,7 @@ async function main() {
     'execution-plan-ready': (dir) => checkExecutionPlanReady(dir),
     'execution-reviews-passed': (dir) => checkExecutionReviewsPassed(dir),
     'arch-design': (dir) => checkArchDesign(dir),
+    'compound-captured': (dir) => checkCompoundCaptured(dir),
   };
 
   const checks = [];

package/scripts/lib/cmd-state.mjs

@@ -26,6 +26,8 @@ const SETTABLE_FIELDS = [
   // Architecture design gate (v0.9 §26, v0.22.5 评审修复 F02)
   'arch_design_decision', 'arch_design_reason',
   'arch_design_timestamp', 'arch_design_artifacts',
+  // Compound engineering capture gate (v0.24.0 复利贯穿强制化)
+  'compound_skipped',
 ];
 
 export async function run(args) {

package/scripts/lib/solutions-promote.mjs

@@ -130,7 +130,7 @@ ${learning.body}
   return { promoted, updated };
 }
 
-if (process.argv[1]?.includes('solutions-promote')) {
+if (process.env.NODE_ENV !== 'test' && process.argv[1]?.includes('solutions-promote')) {
   const args = { _: [] };
   for (let i = 2; i < process.argv.length; i++) {
     if (process.argv[i].startsWith('--')) {

package/scripts/lib/state-loader.mjs

@@ -43,6 +43,8 @@ const BUILTIN_DEFAULTS = {
   arch_design_reason: null,
   arch_design_timestamp: null,
   arch_design_artifacts: null,
+  // Compound engineering capture gate (v0.24.0 复利贯穿强制化)
+  compound_skipped: null,
 };
 
 /**
@@ -117,6 +119,9 @@ export function writeState(changeDir, state) {
   lines.push(`arch_design_reason: ${state.arch_design_reason ?? 'null'}`);
   lines.push(`arch_design_timestamp: ${state.arch_design_timestamp ?? 'null'}`);
   lines.push(`arch_design_artifacts: ${state.arch_design_artifacts ?? 'null'}`);
+  lines.push('');
+  lines.push('# === Compound engineering capture gate (v0.24.0) ===');
+  lines.push(`compound_skipped: ${state.compound_skipped ?? 'null'}`);
 
   fs.writeFileSync(filePath, lines.join('\n') + '\n', 'utf-8');
 }

package/skills/bug-investigator/SKILL.md

@@ -49,7 +49,7 @@ Scientific method: form a single hypothesis ("I think X is the root cause becaus
 
 ### DP-5: Debug Escalation (3+ Failures)
 
-3+ failed fixes = architectural problem. Each fix revealing new problems elsewhere = wrong architecture. Record: `npx --yes --package @xulthekl/team-flow@0.23.0 tf state set <change-dir> dp_5_result <decision>`. Discuss with user before attempting more fixes.
+3+ failed fixes = architectural problem. Each fix revealing new problems elsewhere = wrong architecture. Record: `npx --yes --package @xulthekl/team-flow@0.24.0 tf state set <change-dir> dp_5_result <decision>`. Discuss with user before attempting more fixes.
 
 ## Red Flags — Return to Phase 1
 

package/skills/build-executor/SKILL.md

@@ -15,18 +15,18 @@ When `architecture/sql/` exists, also read:
 - `architecture/sql/ddl/*.sql` — executable DDL scripts; reference directly for DB schema change tasks instead of hand-writing DDL
 - `architecture/sql/migration/*.sql` — data migration scripts; execute as-is for data transformation tasks
 
-Check workflow mode first: `npx --yes --package @xulthekl/team-flow@0.23.0 tf state get <change-dir> workflow`. If `tweak` → direct edit mode. If `hotfix` or `full` → standard contract-first discipline.
+Check workflow mode first: `npx --yes --package @xulthekl/team-flow@0.24.0 tf state get <change-dir> workflow`. If `tweak` → direct edit mode. If `hotfix` or `full` → standard contract-first discipline.
 
 Branch/worktree preflight before ANY implementation edit (mandatory — do not skip):
 1. Run the isolation check:
    ```bash
-   npx --yes --package @xulthekl/team-flow@0.23.0 tf isolate <change-dir>
+   npx --yes --package @xulthekl/team-flow@0.24.0 tf isolate <change-dir>
    ```
    This script enforces git isolation: if you are on `main`/`master` it creates a
    git worktree (preferred) or a new branch, and exits non-zero if it cannot and you
    have not approved `--force`.
-2. If `npx --yes --package @xulthekl/team-flow@0.23.0 tf isolate` exits non-zero: STOP. Do not edit `main`/`master` in place.
-   Ask the user for explicit approval (and re-run with `npx --yes --package @xulthekl/team-flow@0.23.0 tf isolate <change-dir> --force`
+2. If `npx --yes --package @xulthekl/team-flow@0.24.0 tf isolate` exits non-zero: STOP. Do not edit `main`/`master` in place.
+   Ask the user for explicit approval (and re-run with `npx --yes --package @xulthekl/team-flow@0.24.0 tf isolate <change-dir> --force`
    only after they approve).
 3. If it succeeds, report the chosen branch/worktree and make all implementation
    edits there.
@@ -52,15 +52,15 @@ Return to `specifying` or `bridging` if: new behavior appears, interfaces change
 For `full`/`hotfix`, generate proposed waves from the approved contract, then use the recommendation as a decision aid rather than silently defaulting a mode:
 
 ```bash
-npx --yes --package @xulthekl/team-flow@0.23.0 tf execution recommend <change-dir> \
+npx --yes --package @xulthekl/team-flow@0.24.0 tf execution recommend <change-dir> \
   --wave <wave-id>:<parallel|serial>:<task,...>[:<depends-on,...>] --json
 # Show every available mode, the observed facts, and the recommendation to the user.
 # The command writes a receipt tied to the artifacts, contract, and waves. After the user chooses, record that explicit confirmation:
-npx --yes --package @xulthekl/team-flow@0.23.0 tf execution plan <change-dir> \
+npx --yes --package @xulthekl/team-flow@0.24.0 tf execution plan <change-dir> \
   --mode <selected-mode> --confirm --reason "user-selected execution mode" \
   --wave <wave-id>:<parallel|serial>:<task,...>[:<depends-on,...>]
 # Add --acknowledge-recommendation when the selection differs from the recommendation.
-npx --yes --package @xulthekl/team-flow@0.23.0 tf execution show <change-dir> --json
+npx --yes --package @xulthekl/team-flow@0.24.0 tf execution show <change-dir> --json
 ```
 
 The optional fourth `--wave` segment names prerequisite wave IDs. `execution show --json` reports `current`, plus each wave's `depends_on`, `receipt`, `blockers`, `retryable`, and `eligible` status. A wave with `retryable: true` has a current `fail` receipt and is eligible only for its focused repair and re-review; its dependents remain blocked until its replacement `pass` receipt. Report the saved plan revision, selected mode, ordered waves, dependencies, and whether every `parallel` wave can actually be dispatched concurrently on the current platform. If concurrency is unavailable, state the capability and reason plainly; retain the planned `parallel` strategy and do not silently execute it as a serial or Batch Inline plan.
@@ -73,7 +73,7 @@ The recommendation uses task count, configured `execution.inlineThreshold`, and
 | **Inline** | Recommended for a single sequential task; always available for a user-confirmed choice |
 | **Batch Inline** | Recommended for a bounded sequential batch; it remains serial and is never presented as parallel |
 
-Do not transition to `executing` until `execution show` reports `current: true` and the phase guard passes. A revised plan must repeat `npx --yes --package @xulthekl/team-flow@0.23.0 tf execution recommend` and use `npx --yes --package @xulthekl/team-flow@0.23.0 tf execution revise --confirm`; it creates a new revision and invalidates receipts from the prior revision.
+Do not transition to `executing` until `execution show` reports `current: true` and the phase guard passes. A revised plan must repeat `npx --yes --package @xulthekl/team-flow@0.24.0 tf execution recommend` and use `npx --yes --package @xulthekl/team-flow@0.24.0 tf execution revise --confirm`; it creates a new revision and invalidates receipts from the prior revision.
 
 ## Batch Inline Execution
 
@@ -88,21 +88,21 @@ Boundaries: if any task touches >1 module, involves schema/API/config changes, o
 For full/hotfix by default. Dispatch according to the persisted plan, review each planned wave, and run a final broad review after all waves.
 
 ### Planned-Wave Loop
-1. Read the current plan with `npx --yes --package @xulthekl/team-flow@0.23.0 tf execution show <change-dir> --json`; only waves shown with `current: true` and `eligible: true` may start. A `retryable: true` wave may only be repaired and re-reviewed; do not dispatch its dependents until its replacement receipt is `pass`. The CLI encodes dependencies in `--wave <id>:<strategy>:<tasks>[:<depends-on,...>]` and rejects a review receipt for a wave whose prerequisites lack current `pass` receipts.
+1. Read the current plan with `npx --yes --package @xulthekl/team-flow@0.24.0 tf execution show <change-dir> --json`; only waves shown with `current: true` and `eligible: true` may start. A `retryable: true` wave may only be repaired and re-reviewed; do not dispatch its dependents until its replacement receipt is `pass`. The CLI encodes dependencies in `--wave <id>:<strategy>:<tasks>[:<depends-on,...>]` and rejects a review receipt for a wave whose prerequisites lack current `pass` receipts.
 2. A `parallel` wave may dispatch independent tasks simultaneously only when the platform supports concurrent dispatch. If it does not, disclose the unavailable capability and execute the same wave one task at a time without changing its stored strategy.
 3. A `serial` wave dispatches one task at a time in listed order.
 4. After every wave, write a non-empty persisted regular-file review report (separate from the implementer's report), then record exactly one receipt that names that review report:
    ```bash
-   npx --yes --package @xulthekl/team-flow@0.23.0 tf execution review <change-dir> \
+   npx --yes --package @xulthekl/team-flow@0.24.0 tf execution review <change-dir> \
      --wave <wave-id> --base <sha> --head <sha> --report <review-report-path> --verdict <pass|fail>
    ```
    Do not begin a dependent wave until its predecessor receipt is `pass`.
 5. Critical/Important findings require a `fail` receipt, a focused repair, re-review, then a replacement `pass` receipt. Never advance or close with a missing or failed receipt.
 
 ### Per-Task Loop
-1. **Dispatch implementer**: Load the template with `npx --yes --package @xulthekl/team-flow@0.23.0 tf runtime asset read skills/build-executor/implementer-prompt.md`. Extract task brief with `scripts/task-brief PLAN_FILE N`. Include: where task fits, brief path, interfaces from prior tasks, report file path.
+1. **Dispatch implementer**: Load the template with `npx --yes --package @xulthekl/team-flow@0.24.0 tf runtime asset read skills/build-executor/implementer-prompt.md`. Extract task brief with `scripts/task-brief PLAN_FILE N`. Include: where task fits, brief path, interfaces from prior tasks, report file path.
 2. **Handle response**: DONE → generate review package + dispatch reviewer. DONE_WITH_CONCERNS → assess. NEEDS_CONTEXT → provide context. BLOCKED → re-dispatch with better model or escalate.
-3. **Review**: Load `npx --yes --package @xulthekl/team-flow@0.23.0 tf runtime asset read skills/build-executor/task-reviewer-prompt.md`. Reviewer returns spec compliance + code quality verdicts with the wave ID, git range, report path, and `pass`/`fail` receipt command.
+3. **Review**: Load `npx --yes --package @xulthekl/team-flow@0.24.0 tf runtime asset read skills/build-executor/task-reviewer-prompt.md`. Reviewer returns spec compliance + code quality verdicts with the wave ID, git range, report path, and `pass`/`fail` receipt command.
 4. **Fix**: If Critical or Important issues, write the `fail` receipt, dispatch fix subagent, re-review, and write the replacement `pass` receipt.
 5. **Mark complete**: Append to `.superpowers/sdd/progress.md`: `Task N: complete (commits <base7>..<head7>, review clean)`
 
@@ -110,7 +110,7 @@ For full/hotfix by default. Dispatch according to the persisted plan, review eac
 Use the configured profile that matches the task role. Resolve it before dispatch:
 
 ```bash
-npx --yes --package @xulthekl/team-flow@0.23.0 tf runtime config --resolve-model <profile>
+npx --yes --package @xulthekl/team-flow@0.24.0 tf runtime config --resolve-model <profile>
 ```
 
 | Profile | Role |
@@ -123,11 +123,11 @@ npx --yes --package @xulthekl/team-flow@0.23.0 tf runtime config --resolve-model
 For platforms whose dispatch supports a `model` field, explicitly pass the resolved `model` value. If the result is `configured: false`, automatic selection is unavailable: do not invent a provider model and do not bypass the existing requirement to specify `model` explicitly. Resolution only reads configuration; it does not switch models.
 
 ### Progress Ledger
-Track in `.superpowers/sdd/progress.md`. Check for existing ledger — completed tasks are done. After each batch: `npx --yes --package @xulthekl/team-flow@0.23.0 tf state set <change-dir> batches_completed <N>`.
+Track in `.superpowers/sdd/progress.md`. Check for existing ledger — completed tasks are done. After each batch: `npx --yes --package @xulthekl/team-flow@0.24.0 tf state set <change-dir> batches_completed <N>`.
 
 ## Inline Execution Mode
 
-Only after a user-confirmed `inline` selection is recorded by `npx --yes --package @xulthekl/team-flow@0.23.0 tf execution plan --confirm`; a non-recommended selection also records `--acknowledge-recommendation`. Executes in the current session and still writes one review receipt per planned wave.
+Only after a user-confirmed `inline` selection is recorded by `npx --yes --package @xulthekl/team-flow@0.24.0 tf execution plan --confirm`; a non-recommended selection also records `--acknowledge-recommendation`. Executes in the current session and still writes one review receipt per planned wave.
 
 Per-task: extract brief → write failing test → confirm failure → implement → confirm green → checkpoint review (done-when criteria, SHALL/MUST verification) → commit → save a task-level recovery checkpoint when another task remains → append to progress ledger.
 
@@ -135,7 +135,7 @@ After a task is committed and reviewed, when another task remains, save the
 recovery context with real evidence:
 
 ```bash
-npx --yes --package @xulthekl/team-flow@0.23.0 tf checkpoint save <change-dir> \
+npx --yes --package @xulthekl/team-flow@0.24.0 tf checkpoint save <change-dir> \
   --task <completed-task-id> --next "<next task>" --completed "<completed work>" \
   --verification "<verification report path>" --review "<review report path>" \
   --risk "<open risk or None>" --commit-start <base-sha> --commit-end <head-sha>
@@ -143,7 +143,7 @@ npx --yes --package @xulthekl/team-flow@0.23.0 tf checkpoint save <change-dir> \
 
 This augments `.superpowers/sdd/progress.md`; it does not replace the progress
 ledger or add a new core workflow state. Do not claim a checkpoint is current
-when `npx --yes --package @xulthekl/team-flow@0.23.0 tf checkpoint list` reports it as stale.
+when `npx --yes --package @xulthekl/team-flow@0.24.0 tf checkpoint list` reports it as stale.
 
 If task hits BLOCKED (3+ fix failures or changes outside declared scope), escalate to SDD.
 
@@ -153,8 +153,8 @@ Skip TDD. Apply changes directly. Verify file integrity (exists, non-empty, vali
 
 ## DP Records
 
-DP-4 is written by `npx --yes --package @xulthekl/team-flow@0.23.0 tf execution plan`; do not write it with raw `state set`.
-DP-5 (debug escalation): `npx --yes --package @xulthekl/team-flow@0.23.0 tf state set <change-dir> dp_5_result "<resolution>"` + timestamp.
+DP-4 is written by `npx --yes --package @xulthekl/team-flow@0.24.0 tf execution plan`; do not write it with raw `state set`.
+DP-5 (debug escalation): `npx --yes --package @xulthekl/team-flow@0.24.0 tf state set <change-dir> dp_5_result "<resolution>"` + timestamp.
 
 ## Completion Standard
 

package/skills/build-executor/implementer-prompt.md

@@ -22,7 +22,7 @@ Subagent (general-purpose):
     ## Planned Wave
 
     You are assigned to planned wave [WAVE_ID] with strategy [WAVE_STRATEGY].
-    Read `npx --yes --package @xulthekl/team-flow@0.23.0 tf execution show <change-dir> --json` before editing. Do not start
+    Read `npx --yes --package @xulthekl/team-flow@0.24.0 tf execution show <change-dir> --json` before editing. Do not start
     unless all declared dependencies have `pass` review receipts. A `parallel`
     label permits concurrent dispatch only when the controller confirms the
     platform supports it; never change the saved wave strategy yourself.