@xulthekl/team-flow 0.55.0 → 0.56.0

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

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

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "team-flow",
-  "version": "0.55.0",
+  "version": "0.56.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) + 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.55.0",
+  "version": "0.56.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.55.0"
+    "version": "0.56.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) + business-analysis (independent requirement/scenario artifact). 26 skills + 17 agents, one install.",
-  "version": "0.55.0",
+  "version": "0.56.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.55.0"
+    "version": "0.56.0"
   },
   "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.55.0",
+      "version": "0.56.0",
       "source": ".",
       "author": {
         "name": "LT",

package/AGENTS.md

@@ -110,7 +110,7 @@ docs/
   ├── architecture/    全局架构三层（v0.36.0）：L1 当前态（ARCHITECTURE.md marker 区 / PHYSICAL-MODEL.md / DATABASE.md / API-INDEX.md / INDEX.md / domains/<bc>.md / diagrams/ / schema-baseline.sql / baseline.md）+ L2 changelog/ + L3 iterations/vN/architecture.md（产品级快照，archived 退役）
   └── solutions/       复利经验库（v0.5 新增，三层索引）
       ├── INDEX.md     # L1 轻量索引（≤150行，每条一行摘要+标签）
-      ├── requirement/ plan/ architecture/ prototype/ spec/ build/ review/ cross-phase/  # L2 分阶段目录（v0.36.0 加 architecture）
+      ├── prd/ plan/ architecture/ prototype/ spec/ build/ review/ cross-phase/  # L2 分阶段目录（枚举权威：scripts/lib/solutions-phases.mjs）
       └── <file>.md    # L3 经验文件（YAML frontmatter: phase/domain/type/severity）
 changes/<name>/        变更脚手架（S4 创建）：.team-flow.yaml（变更级状态文件）/ change-brief.md（产品级交接物，含 upstream_arch_ref）/ proposal.md / design.md / tasks.md / execution-contract.md / learnings.md（变更级经验台账）/ architecture/（变更级三件套 + sql/）
 specs/<cap>/            每变更规格：spec.md（v0.49.0 §83.3.5：learnings.md 归 change 根，不在此目录）
@@ -253,7 +253,7 @@ STRATEGY.md CONCEPTS.md 产品策略(BA) / 领域词汇
 ```
 docs/solutions/
 ├── INDEX.md                  # L1：轻量索引（≤150行，每条一行摘要+标签，按 severity 降序）
-├── requirement/ plan/ prototype/ spec/ build/ review/ cross-phase/  # L2：分阶段目录
+├── prd/ plan/ architecture/ prototype/ spec/ build/ review/ cross-phase/  # L2：分阶段目录（枚举权威：scripts/lib/solutions-phases.mjs）
 └── <date>-<summary>.md      # L3：经验文件（YAML frontmatter: phase/domain/type/severity/date/source）
 ```
 

package/CHANGELOG.md

@@ -4,6 +4,35 @@ All notable changes to `team-flow` will be documented in this file.
 
 The format loosely follows Keep a Changelog.
 
+## [0.56.0] - 2026-09-12
+
+### Fixed（复利产物文件名退化 + 索引丢条目；来源：emp-auth 复利膨胀调查）
+
+设计来源：`docs/plan/compound-lifecycle-governance-design.md` v1.0。输入 = **emp-auth v1 迭代（5 change）的复利产物实测**——发现"复利条目随迭代膨胀/重复"的表象下，实为**存储层无上限 + 身份层去重键选错 + 索引层无门禁**三层缺口（完整证据链见该方案附录 A；P1/P2 待实施）。
+
+本版处置其中两个**确定性缺陷**（P0）：
+
+- **PHASES 枚举三处定义互相矛盾**（`solutions-capture` 8 项含 `architecture` / `solutions-index-gen` 7 项缺 / 文档树写 `requirement`）：`tf solutions capture --phase architecture` 写入的条目在 `tf solutions index-gen` 重建后**从 INDEX.md 消失**——文件仍在磁盘，但对所有注入与检索通道不可见。新增 `scripts/lib/solutions-phases.mjs` 作唯一真相源，两处消费点收敛。
+- **slug 规则三套并存，两处不保留 CJK 且逐字符替换**：`test-merge.mjs` 的 `replace(/[^a-z0-9-]/g,'-')` 与 `sdd-overlay.mjs` 的 `replace(/[^A-Za-z0-9._-]/g,'_')` 把中文标题**逐字符**替换为分隔符，产生 `--------------------.md`（原名「执行结果（三仓实测，命令 + 实际输出）」）这类无信息量文件名（emp-auth 实测 17 个文件受影响）；叠加 baselines 的 `moduleName` 取自 test-matrix 三级标题原文（每轮自由命名）⇒ 文件名不稳定 ⇒ `existsSync` 不命中 ⇒ **新建而非增量合并**（`demohome` 三次 merge 全为 `A(Added)`，攒出 3 个文件）。新增 `scripts/lib/slug.mjs` 作唯一真相源（`slugify` / `safeName` / `CJK_CLASS`），4 处消费点收敛。
+
+**关键陷阱（已写入模块注释守护）**：字面「一-鿿」拼进字符类时，**前一个字符若为 `-` 会构成范围**——`[^..._-一-鿿]` 里的 `_-一` 是 U+005F–U+4E00 范围，U+4E00 以上的汉字（如「任务」U+4EFB）仍被替换。故 `CJK_CLASS` 以转义写法导出，`safeName` 的 `-` 置于字符类末尾。
+
+### Added
+
+- `scripts/lib/slug.mjs`（文件名/路径段安全化唯一真相源）、`scripts/lib/solutions-phases.mjs`（复利 phase 枚举唯一真相源）
+- `tests/lib/slug.test.mjs`（13 用例，含 U+4E00 以上汉字的范围陷阱守护）、`tests/lib/solutions-phases.test.mjs`（6 用例，含"capture 能写但 index-gen 扫不到"的行为级守护）、`tests/lib/test-merge.test.mjs` +1 用例（中文模块名不退化为短横线）
+
+### Changed
+
+- `AGENTS.md` ×2、`skills/ce-compound/references/three-tier-index.md` ×2：phase 目录列表同口径同步，顺带修正 `requirement/` → `prd/`（与脚本实际写入目录对齐），并补注"CLI 通道 phase 目录"与"ce-compound category 目录"两套词表互不兼容
+
+### 验证
+
+- 全量测试 **1108/1108 通过**
+- **4 项变异验证**确认新增测试具备判别力（去掉 `architecture` / index-gen 写死列表 / `safeName` 的 `-` 置中 / test-merge 还原旧正则——每项均使对应测试失败并报出原缺陷形态）
+- **行为等价实证**：以 emp-auth 真实 learnings 标题跑新 `slugify`，与既有条目文件名 **4/4 一致**（无回归）
+- 提交可见性：4 个新增文件未被 `.gitignore` 吞掉，2 个脚本进入 `npm pack` 白名单
+
 ## [0.55.0] - 2026-09-11
 
 ### Added（首次真实使用反馈处置：棕地机制 + 解析层加固）

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

package/README.md

@@ -1,6 +1,6 @@
 # team-flow
 
-> 当前版本：`v0.55.0`
+> 当前版本：`v0.56.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.55.0`
+- Current: `v0.56.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/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.55.0",
+  "version": "0.56.0",
   "contextFileName": "GEMINI.md"
 }

package/hooks/session-start

@@ -1,11 +1,11 @@
 #!/usr/bin/env bash
-# v0.55.0: auto-sync CLI version with plugin version
+# v0.56.0: auto-sync CLI version with plugin version
 set -e
 
 # ═══════════════════════════════════════════════════════════════
 # Plugin version (update this when releasing new versions)
 # ═══════════════════════════════════════════════════════════════
-PLUGIN_VERSION="0.55.0"
+PLUGIN_VERSION="0.56.0"
 
 # ═══════════════════════════════════════════════════════════════
 # 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.55.0.
+Current version: v0.56.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.55.0",
+  "version": "0.56.0",
   "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.55.0",
+  "version": "0.56.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) + 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/sdd-overlay.mjs

@@ -6,6 +6,7 @@ import { dirname, join } from 'node:path';
 import { computeArtifactsHash, normalizeCheckboxes } from './hash.mjs';
 import { parseTaskLine } from './md-normalize.mjs';
 import { readState } from './state-loader.mjs';
+import { safeName } from './slug.mjs';
 
 export const HANDOFF_TYPES = new Set(['prototype', 'research', 'experiment']);
 export const HANDOFF_DECISIONS = new Set(['accept', 'reject', 'defer']);
@@ -270,6 +271,4 @@ function requireText(value, field) {
   if (typeof value !== 'string' || !value.trim()) throw new Error(`${field} is required`);
 }
 
-function safeName(value) {
-  return String(value).replace(/[^A-Za-z0-9._-]/g, '_');
-}
+// safeName 已收敛到 slug.mjs（保留 CJK；`. _ -` 语义不变，如 taskId `1.1` 原样保留）

package/scripts/lib/slug.mjs

@@ -0,0 +1,68 @@
+/**
+ * slug — 文件名 / 路径段安全化的唯一真相源（2026-09-12，emp-auth 复利膨胀调查）
+ *
+ * 背景：同一插件内曾存在 3 套文件名安全化规则，其中两套**未保留 CJK 且逐字符替换**，
+ * 导致中文标题退化为纯短横线序列。实证（emp-auth v1 迭代）：
+ *   - `docs/test-ledger/baselines/--------------------.md`（原名「执行结果（三仓实测，命令 + 实际输出）」）
+ *   - 同目录 17 个文件名受影响，其中多份已无法从文件名辨识内容
+ *   - 叠加第二个因素：baselines 的 moduleName 取自 test-matrix 三级标题原文（每轮由 LLM
+ *     自由命名，如 `DemoHome 当前应用（demo-ui，medium）` vs `DemoHome（demo-ui，medium，revision 3）`）
+ *     ⇒ 文件名每轮变化 ⇒ `existsSync` 不命中 ⇒ **新建而非增量合并**（demohome 三次 merge
+ *     产出 3 个文件，git 记录全为 A）
+ *
+ * 约定：
+ * - 字符集统一为 **ASCII 字母数字 + CJK 统一表意文字（U+4E00–U+9FFF）**；其余字符折叠为分隔符
+ * - 一律使用 `+` 量词折叠连续非法字符——**禁止逐字符替换**（一个中文 = 一个分隔符是退化根因）
+ * - 两类用途语义不同，**不要互串**：
+ *   · slugify()  标题 → 文件名（小写、`.`/`_`/`-` 均折叠为分隔符、可截断）
+ *   · safeName() ID → 路径段（保留大小写与 `.` `_` `-`，不截断）——ID 自身以这些字符作分隔，
+ *     例如 taskId `1.1` MUST 保持为 `1.1`（折叠成 `1_1` 会失配既有 checkpoint 文件）
+ *
+ * @module slug
+ */
+
+/**
+ * CJK 统一表意文字区间字符类（U+4E00–U+9FFF）。
+ *
+ * 用 `\u` 转义写法而非字面「一-鿿」：字面写法拼进字符类时，**前一个字符若为 `-`
+ * 会被解析成范围**——`[^..._-一-鿿]` 里的 `_-一` 是 U+005F–U+4E00 范围，
+ * 结果 U+4E00 以上的汉字（如「任务」U+4EFB）仍被替换。转义写法无此风险。
+ */
+export const CJK_CLASS = '\\u4e00-\\u9fff';
+
+/** 转义正则元字符（separator 由调用方传入，可能是 `-` / `_` 等） */
+function escapeRe(s) {
+  return s.replace(/[.*+?^${}()|[\]\\]/g, '\\$&');
+}
+
+/**
+ * 标题 → 文件名 slug。
+ *
+ * 保留 ASCII 小写字母数字与 CJK；其余连续字符折叠为一个 separator；去掉首尾 separator。
+ *
+ * @param {string} value 原始文本（通常是条目标题 / 模块名）
+ * @param {{separator?: string, maxLength?: number}} [options]
+ *   separator 默认 `-`；maxLength > 0 时才截断（默认不截断，由调用方按场景显式传入）
+ * @returns {string}
+ */
+export function slugify(value, { separator = '-', maxLength = 0 } = {}) {
+  const esc = escapeRe(separator);
+  let s = String(value ?? '').toLowerCase();
+  s = s.replace(new RegExp(`[^a-z0-9${CJK_CLASS}]+`, 'g'), separator);
+  s = s.replace(new RegExp(`^(?:${esc})+|(?:${esc})+$`, 'g'), '');
+  return maxLength > 0 ? s.slice(0, maxLength) : s;
+}
+
+/**
+ * ID → 路径段安全名。
+ *
+ * 保留 ASCII 字母数字（含大小写）与 `.` `_` `-`，以及 CJK；其余连续字符折叠为一个 `_`。
+ * 不截断、不改大小写——ID 的既有语义（如 `1.1`、`W4-1`）MUST 原样保留。
+ *
+ * @param {string} value
+ * @returns {string}
+ */
+export function safeName(value) {
+  // `-` MUST 置于字符类末尾（否则与相邻字符构成范围）
+  return String(value ?? '').replace(new RegExp(`[^A-Za-z0-9._${CJK_CLASS}-]+`, 'g'), '_');
+}

package/scripts/lib/solutions-capture.mjs

@@ -16,17 +16,11 @@ import { readFileSync, writeFileSync, existsSync, mkdirSync, appendFileSync } fr
 import { join } from 'node:path';
 import { pathToFileURL } from 'node:url';
 import { SEVERITY_VALUES, isSeverity } from './severity.mjs';
+import { SOLUTION_PHASES } from './solutions-phases.mjs';
+import { slugify } from './slug.mjs';
 
-const PHASES = ['prd', 'plan', 'architecture', 'prototype', 'spec', 'build', 'review', 'cross-phase'];
 const MAX_INDEX_LINES = 150;
-
-function slugify(text) {
-  return text
-    .toLowerCase()
-    .replace(/[^a-z0-9一-鿿]+/g, '-')
-    .replace(/^-|-$/g, '')
-    .slice(0, 40);
-}
+const SLUG_MAX_LENGTH = 40;
 
 export function run(args = {}) {
   const phase = args.phase || 'cross-phase';
@@ -42,8 +36,8 @@ export function run(args = {}) {
 
   // 注：process.exit 后补 return——真实 CLI 下 exit 即终止；测试环境 mock exit 时
   // 不得继续执行（否则校验失败仍会写入文件，v0.23 §91.3.4 横展）。
-  if (!PHASES.includes(phase)) {
-    console.error(`Invalid phase: ${phase}. Valid: ${PHASES.join(', ')}`);
+  if (!SOLUTION_PHASES.includes(phase)) {
+    console.error(`Invalid phase: ${phase}. Valid: ${SOLUTION_PHASES.join(', ')}`);
     process.exit(1);
     return;
   }
@@ -61,7 +55,7 @@ export function run(args = {}) {
 
   // 生成文件名
   const date = new Date().toISOString().slice(0, 10);
-  const slug = slugify(summary);
+  const slug = slugify(summary, { maxLength: SLUG_MAX_LENGTH });
   const fileName = `${date}-${slug}.md`;
   const filePath = join(phaseDir, fileName);
 

package/scripts/lib/solutions-index-gen.mjs

@@ -17,8 +17,8 @@ import { readFileSync, writeFileSync, readdirSync, statSync, existsSync } from '
 import { join } from 'node:path';
 import { pathToFileURL } from 'node:url';
 import { severityRank } from './severity.mjs';
+import { SOLUTION_PHASES } from './solutions-phases.mjs';
 
-const PHASES = ['prd', 'plan', 'prototype', 'spec', 'build', 'review', 'cross-phase'];
 const MAX_INDEX_LINES = 150;
 
 function parseFrontmatter(content) {
@@ -54,7 +54,7 @@ export function run(args = {}) {
 
   const entries = [];
 
-  for (const phase of PHASES) {
+  for (const phase of SOLUTION_PHASES) {
     const phaseDir = join(dir, phase);
     if (!existsSync(phaseDir) || !statSync(phaseDir).isDirectory()) continue;
 

package/scripts/lib/solutions-phases.mjs

@@ -0,0 +1,32 @@
+/**
+ * solutions-phases — 复利条目 phase 目录的唯一真相源（2026-09-12）
+ *
+ * 背景：PHASES 枚举曾在 3 处各自定义且互相矛盾——
+ *   - `solutions-capture.mjs`   8 项（含 `architecture`，v0.36.3 加入）
+ *   - `solutions-index-gen.mjs` 7 项（**缺 `architecture`**）
+ *   - 文档树（three-tier-index.md / AGENTS.md）写 `requirement`，而 frontmatter 示例写 `prd`
+ *
+ * 后果（实证，emp-auth）：`tf solutions capture --phase architecture` 写入的条目在
+ * `tf solutions index-gen` 重建后会**从 INDEX.md 消失**——文件仍在磁盘，但对所有
+ * 注入 / 检索通道不可见。任何新增 phase 只改本文件。
+ *
+ * 注意：`docs/solutions/` 下另有 ce-compound 通道写入的 **category 目录**
+ * （`workflow-issues/` 等，见 skills/ce-compound/references/yaml-schema.md），
+ * 那套词表与本 phase 词表**互不兼容**，本模块不覆盖。
+ *
+ * @module solutions-phases
+ */
+
+/** 合法 phase 取值（同时是 docs/solutions/ 下的子目录名） */
+export const SOLUTION_PHASES = Object.freeze([
+  'prd', 'plan', 'architecture', 'prototype', 'spec', 'build', 'review', 'cross-phase',
+]);
+
+/**
+ * 是否为合法 phase 取值。
+ * @param {string} phase
+ * @returns {boolean}
+ */
+export function isSolutionPhase(phase) {
+  return SOLUTION_PHASES.includes(phase);
+}

package/scripts/lib/solutions-promote.mjs

@@ -23,6 +23,10 @@ import { join, basename } from 'node:path';
 import { pathToFileURL } from 'node:url';
 import { meetsMinSeverity, nextSeverity } from './severity.mjs';
 import { normalizeInline } from './md-normalize.mjs';
+import { slugify } from './slug.mjs';
+
+/** 文件名 slug 截断长度（与 solutions-capture 一致） */
+const SLUG_MAX_LENGTH = 40;
 
 /**
  * 剥离 YAML 行尾注释（空格 + `#` 起始）——v0.23 §91 硬化：
@@ -188,7 +192,7 @@ export function run(args = {}) {
       mkdirSync(phaseDir, { recursive: true });
     }
 
-    const slug = learning.title.toLowerCase().replace(/[^a-z0-9一-鿿]+/g, '-').slice(0, 40);
+    const slug = slugify(learning.title, { maxLength: SLUG_MAX_LENGTH });
     const fileName = `${date}-${slug}.md`;
     const filePath = join(phaseDir, fileName);
 

package/scripts/lib/test-merge.mjs

@@ -27,6 +27,7 @@
 import { readFileSync, writeFileSync, existsSync, cpSync, mkdirSync, readdirSync } from 'node:fs';
 import { join, basename, relative, resolve } from 'node:path';
 import { execSync } from 'node:child_process';
+import { slugify } from './slug.mjs';
 
 /**
  * 解析 CLI 参数数组为结构化对象
@@ -197,7 +198,9 @@ export function mergeBaselines(ledgerDir, changeName, moduleSections, candidateL
   const today = new Date().toISOString().slice(0, 10);
 
   for (const [moduleName, sectionContent] of Object.entries(moduleSections)) {
-    const safeName = moduleName.toLowerCase().replace(/[^a-z0-9-]/g, '-');
+    // 统一走 slug.mjs（保留 CJK）——原 `[^a-z0-9-]` 逐字符替换会把中文标题退化成纯短横线，
+    // 实证 emp-auth `baselines/--------------------.md`（2026-09-12）
+    const safeName = slugify(moduleName);
     const baselinePath = join(baselinesDir, `${safeName}.md`);
     const moduleCandidates = candidateLedger.filter(c =>
       c.candidate.toLowerCase().includes(moduleName.toLowerCase())

package/skills/ce-compound/references/three-tier-index.md

@@ -5,8 +5,9 @@
 ```
 docs/solutions/
 ├── INDEX.md                  # L1：轻量索引（≤150行，每条一行摘要+标签）
-├── requirement/              # 按阶段分目录
+├── prd/                      # 按阶段分目录（枚举权威：scripts/lib/solutions-phases.mjs）
 ├── plan/
+├── architecture/
 ├── prototype/
 ├── spec/
 ├── build/
@@ -14,6 +15,9 @@ docs/solutions/
 └── cross-phase/              # 跨阶段通用经验
 ```
 
+> 注意：目录树中**只有上述 phase 目录**由 `tf solutions` CLI 通道维护；`workflow-issues/`、
+> `build-errors/` 等 category 目录由 `/ce-compound` 通道写入，两套词表互不兼容。
+
 ## INDEX.md 格式
 
 ```markdown
@@ -29,7 +33,7 @@ docs/solutions/
 
 ```yaml
 ---
-phase: prd          # 阶段标签：prd | plan | prototype | spec | build | review | cross-phase
+phase: prd          # 阶段标签：prd | plan | architecture | prototype | spec | build | review | cross-phase
 domain: auth        # 领域标签（与 PRD/change 的领域对应）
 type: pitfall       # pitfall | pattern | decision | insight
 severity: high      # critical | high | medium | low（序定义于 scripts/lib/severity.mjs）