@xulthekl/team-flow 0.56.0 → 0.56.1

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

@@ -1,3 +1,3 @@
-# team-flow v0.56.0 | 阶段: {{state}} | 工作流: {{workflow}}
+# team-flow v0.56.1 | 阶段: {{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 + independent business analysis. 26 skills + 17 agents with embedded TDD, SDD, code review, debugging, delta spec sync, and design-system-driven prototyping.",
-      "version": "0.56.0",
+      "version": "0.56.1",
       "source": "./",
       "author": {
         "name": "LT",

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "team-flow",
-  "version": "0.56.0",
+  "version": "0.56.1",
   "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) + business-analysis (independent requirement/scenario artifact) + design-system (design tokens + component contract + AI primer + showcase) + test-strategy (test strategy design) + project-initialize (new service onboarding). 26 skills + 17 agents, one install.",
   "source": "./",
   "author": {

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "team-flow",
-  "version": "0.56.0",
+  "version": "0.56.1",
   "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.56.0"
+    "version": "0.56.1"
   },
   "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) + business-analysis (independent requirement/scenario artifact). 26 skills + 17 agents, one install.",
-  "version": "0.56.0",
+  "version": "0.56.1",
   "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.56.0"
+    "version": "0.56.1"
   },
   "plugins": [
     {
       "name": "team-flow",
       "description": "Unified workflow with planning artifacts, execution contracts, TDD, review gates, systematic debugging, delta spec sync, architecture-design, independent business analysis, and local HTML prototyping.",
-      "version": "0.56.0",
+      "version": "0.56.1",
       "source": ".",
       "author": {
         "name": "LT",

package/CHANGELOG.md

@@ -4,6 +4,25 @@ All notable changes to `team-flow` will be documented in this file.
 
 The format loosely follows Keep a Changelog.
 
+## [0.56.1] - 2026-09-12
+
+### Fixed（v0.56.0 自身引入的回归 + P1.5 第一轮暴露的遗漏；**升级优先于 0.56.0**）
+
+来源：v0.56.0 的 P1.5 **完整档 3 轮**对抗验证第一轮（事实核查 / 反方辩护 / 场景遍历三路独立代理）。三路共暴露 51 条断言级核查 + 8 类场景缺口 + 5 项设计缺陷，本版仅处置其中**确定性的代码缺陷**；设计缺陷需修订 `docs/plan/compound-lifecycle-governance-design.md`（**v1.0 → v2.0 修订进行中，尚未落档**），不属本版范围。
+
+- **`tf test-merge` baselines 命名失配（v0.56.0 引入，危害高于其修复的原缺陷）**：v0.56.0 把 slug 规则从 `[^a-z0-9-]`（逐字符替换、不去首尾）换成 `slugify()`（保留 CJK、折叠连续、**去首尾分隔符**）。而 baselines 的 `moduleName` 形如 `DemoHome（demo-ui，medium）`，**恒以全角 `）` 结尾** ⇒ 旧规则产出的文件名恒以 `-` 结尾（`demohome-demo-ui-medium-.md`），新规则会去掉尾 `-` ⇒ **既有文件全部失配**（emp-auth 实测 **67/67**）⇒ 每个模块新建一份、目录翻倍。修法：新增 `resolveBaselinePath()` **双查找**——新 slug 优先 → 旧 slug 回退 → 都不存在才按新规则新建；命中旧命名文件**原地更新**（不强制改名，批量改名属 P1 的稳定 `module_id` + `--rekey` 范畴）。
+- **PHASES 单一真相源未做全（v0.56.0 遗留）**：`tests/lib/solutions-index-gen.test.mjs` 仍内联 7 项枚举（`'prd','plan','prototype','spec','build','review','cross-phase'`，缺 `architecture`）并把缺陷**固化为期望行为**（用例名 `scans all 7 phase directories`）。此为 PHASES 的第 3 份副本——v0.56.0 只收敛了 2 个生产消费点，测试侧漏改。修法：改为从 `solutions-phases.mjs` 导入。
+
+### Added
+
+- **枚举副本防漂移机械预防**（`tests/lib/solutions-phases.test.mjs`）：断言模板与文档中仍需列出的 phase 副本（`templates/learnings.md` 注释、`AGENTS.md` 目录树、`three-tier-index.md` 目录树）均覆盖 `SOLUTION_PHASES` 全部取值。背景：PHASES 历史上存在 **4 处**定义且相互矛盾，代码侧已收敛，文档侧用本组用例守护同步（支持"每 phase 一行"与"单行列全"两种排版）。
+- `test-merge.test.mjs` 新增「兼容旧 slug 命名」用例；`solutions-phases.test.mjs` 新增 3 条防漂移用例。
+
+### 验证
+
+- 全量测试 **1112/1112 通过**（基线 1108，+4）
+- **变异验证**（本轮已按事实核查建议留痕于设计文档附录 A.2）：去掉 `resolveBaselinePath` 的 legacy 回退 → 中文命名回归用例失败；从模板删 `architecture` → 防漂移用例失败并精确报出缺失项
+
 ## [0.56.0] - 2026-09-12
 
 ### Fixed（复利产物文件名退化 + 索引丢条目；来源：emp-auth 复利膨胀调查）

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.56.0 | 阶段: {{state}} | 工作流: {{workflow}}
+# team-flow v0.56.1 | 阶段: {{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.56.0**。
+当前发布版本：**v0.56.1**。
 
 ---
 

package/README.md

@@ -1,6 +1,6 @@
 # team-flow
 
-> 当前版本：`v0.56.0`
+> 当前版本：`v0.56.1`
 
 > 统一插件：**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.56.0`
+- Current: `v0.56.1`
 - 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/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) + business-analysis (independent requirement/scenario artifact). 26 skills, one install.",
-  "version": "0.56.0",
+  "version": "0.56.1",
   "contextFileName": "GEMINI.md"
 }

package/hooks/session-start

@@ -1,11 +1,11 @@
 #!/usr/bin/env bash
-# v0.56.0: auto-sync CLI version with plugin version
+# v0.56.1: auto-sync CLI version with plugin version
 set -e
 
 # ═══════════════════════════════════════════════════════════════
 # Plugin version (update this when releasing new versions)
 # ═══════════════════════════════════════════════════════════════
-PLUGIN_VERSION="0.56.0"
+PLUGIN_VERSION="0.56.1"
 
 # ═══════════════════════════════════════════════════════════════
 # Step 1: Auto-sync CLI version with plugin version

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.56.0.
+Current version: v0.56.1.
 
 ## 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.56.0",
+  "version": "0.56.1",
   "description": "Unified plugin (26 skills + 17 agents) integrating team-flow, compound-engineering, architecture-design, prototype, design-system, workflow-orchestrator, workflow-bootstrap, e2e, session-handoff, workflow-feedback, business-analysis 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.56.0",
+  "version": "0.56.1",
   "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) + business-analysis (independent requirement/scenario artifact) + design-system (design tokens + component contract + AI primer + showcase) + test-strategy (test strategy design) + project-initialize (new service onboarding). 26 skills + 17 agents, one install.",
   "author": {
     "name": "LT"

package/scripts/lib/test-merge.mjs

@@ -184,6 +184,32 @@ function extractDeferredItems(content) {
   return items;
 }
 
+/** v0.56.0 之前的 slug 规则（仅供**读取既有文件**时回退匹配；新写入一律走 `slugify`） */
+function legacySlug(moduleName) {
+  return String(moduleName ?? '').toLowerCase().replace(/[^a-z0-9-]/g, '-');
+}
+
+/**
+ * 解析既有 baseline 路径——兼容 v0.56.0 之前的命名规则。
+ *
+ * 背景（2026-09-12，v0.56.0 回归修复）：v0.56.0 把 slug 规则从 `legacySlug`
+ * （逐字符替换、不去首尾）换成 `slugify`（保留 CJK、折叠连续、去首尾分隔符）。
+ * 而 baselines 的 moduleName 形如 `DemoHome（demo-ui，medium）`，**恒以全角 `）` 结尾**
+ * ⇒ 旧规则产出的文件名恒以 `-` 结尾（`demohome-demo-ui-medium-.md`），新规则会去掉尾 `-`
+ * ⇒ 既有文件**全部失配**（emp-auth 实测 67/67）⇒ 每个模块新建一份、目录翻倍。
+ *
+ * 故读取时双查找：新 slug 优先 → 旧 slug 回退 → 都不存在才按新规则新建。
+ * 命中旧命名文件后**原地更新**（保持旧名，不强制改名）——批量改名属 P1 的
+ * 稳定 `module_id` + `--rekey` 迁移范畴（见 `docs/plan/compound-lifecycle-governance-design.md` §4.3）。
+ */
+function resolveBaselinePath(baselinesDir, moduleName) {
+  const next = join(baselinesDir, `${slugify(moduleName)}.md`);
+  if (existsSync(next)) return next;
+  const legacy = join(baselinesDir, `${legacySlug(moduleName)}.md`);
+  if (existsSync(legacy)) return legacy;
+  return next;
+}
+
 /**
  * Step 2: mergeBaselines — 增量合并到 baselines/{module}.md
  * dryRun（feedback 2026-08-05）：仅计算不写盘，返回 would-create/would-update 预览
@@ -199,9 +225,9 @@ export function mergeBaselines(ledgerDir, changeName, moduleSections, candidateL
 
   for (const [moduleName, sectionContent] of Object.entries(moduleSections)) {
     // 统一走 slug.mjs（保留 CJK）——原 `[^a-z0-9-]` 逐字符替换会把中文标题退化成纯短横线，
-    // 实证 emp-auth `baselines/--------------------.md`（2026-09-12）
-    const safeName = slugify(moduleName);
-    const baselinePath = join(baselinesDir, `${safeName}.md`);
+    // 实证 emp-auth `baselines/--------------------.md`（2026-09-12）；
+    // 路径解析经 resolveBaselinePath 双查找，兼容 v0.56.0 之前的旧命名存量
+    const baselinePath = resolveBaselinePath(baselinesDir, moduleName);
     const moduleCandidates = candidateLedger.filter(c =>
       c.candidate.toLowerCase().includes(moduleName.toLowerCase())
     );