@xulthekl/team-flow 0.36.2 → 0.36.4

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

@@ -1,3 +1,3 @@
-# team-flow v0.36.2 | 阶段: {{state}} | 工作流: {{workflow}}
+# team-flow v0.36.4 | 阶段: {{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. 24 skills + 15 agents with embedded TDD, SDD, code review, debugging, delta spec sync, and design-system-driven prototyping.",
-      "version": "0.36.2",
+      "version": "0.36.4",
       "source": "./",
       "author": {
         "name": "LT",

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "team-flow",
-  "version": "0.36.2",
+  "version": "0.36.4",
   "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). 24 skills + 15 agents, one install.",
   "source": "./",
   "author": {

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "team-flow",
-  "version": "0.36.2",
+  "version": "0.36.4",
   "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.36.2"
+    "version": "0.36.4"
   },
   "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). 24 skills + 15 agents, one install.",
-  "version": "0.36.2",
+  "version": "0.36.4",
   "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.36.2"
+    "version": "0.36.4"
   },
   "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.36.2",
+      "version": "0.36.4",
       "source": ".",
       "author": {
         "name": "LT",

package/AGENTS.md

@@ -100,13 +100,13 @@ prd/                    PRD（有版本 v1→v2→v3，git 分支隔离）
       ├── prd-completeness-review.md # PRD 完整性评审报告（prd-completeness-reviewer 产出，v0.15.0 新增）
 prototype/             全局原型系统（UI 契约真相源）：index.html / pages / components / assets / design-system.md / flow.md
 docs/
-  ├── architecture/    全局架构锚点：ARCHITECTURE.md / DATABASE.md / <bc>/（限界上下文目录）/ baseline.md（v0.6 新增）
+  ├── 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行，每条一行摘要+标签）
-      ├── prd/ plan/ prototype/ spec/ build/ review/ cross-phase/  # L2 分阶段目录
+      ├── prd/ plan/ architecture/ prototype/ spec/ build/ review/ cross-phase/  # L2 分阶段目录（v0.36.0 加 architecture）
       └── <file>.md    # L3 经验文件（YAML frontmatter: phase/domain/type/severity）
-changes/<name>/        变更脚手架（S4 创建）：.team-flow.yaml（变更级状态文件，P1-6 第二阶段改名 .team-flow.yaml）
-specs/<cap>/            每变更设计/任务/契约：spec.md / design.md / tasks.md / execution-contract.md / architecture.md / database.md / api.md / learnings.md
+changes/<name>/        变更脚手架（S4 创建）：.team-flow.yaml（变更级状态文件）/ change-brief.md（产品级交接物，含 upstream_arch_ref）/ architecture/（变更级三件套 + sql/）
+specs/<cap>/            每变更设计/任务/契约：spec.md / design.md / tasks.md / execution-contract.md / learnings.md（v0.9 起 architecture/ 三件套已迁至 changes/<name>/architecture/）
 STRATEGY.md CONCEPTS.md 产品策略(BA) / 领域词汇
 ```
 

package/CHANGELOG.md

@@ -6,6 +6,29 @@ The format loosely follows Keep a Changelog.
 
 ## [Unreleased]
 
+## [0.36.4] - 2026-08-05
+
+### Added（Wave 审查纪律 + 上下文轮转）
+
+- **workflow-start SKILL.md**：Route to code-reviewer 增加逐 wave 审查纪律——每次 code-reviewer dispatch 只审查一个 wave，禁止合并多 wave 审查（vrm4teamflow C1 事件修复）
+- **workflow-start SKILL.md**：Sub-agent Dispatch Protocol 增加 build-executor 交互轮次轮转——累计 ≥6 轮 SendMessage 交互时启动新 build-executor 子代理（交接文档必须含已完成 waves + 累积决策 + worktree SHA）
+
+## [0.36.3] - 2026-08-05
+
+### Fixed（v0.14 全链路缺口修复——27 项，复利链路 + agent 契约 + 门禁时序 + 交接/决策门 + guard hook + 快照生命周期 + 旧项目 + 文档同步 + 横展）
+
+- **复利链路（严重 #4）**：solutions PHASES 加 architecture；architecture-design 加载协议加复利注入（`tf solutions inject --phase architecture`）；S3.5 SOP 加复利捕获（Step 9）；ce-compound 补架构自动捕获场景
+- **agent 契约（严重 #1 #2）**：architecture-design / architecture-reviewer agent 加 product 模式（mode 参数/快照输入/INPUT_ERROR 分 mode/Phase1-A3 分叉/报告落盘 iterations/vN/auto-review.md）
+- **门禁触发点（严重 #3）**：`tf arch init` 打戳加 SOP 触发点（S3.5 完成条件 + orchestrator ARCH 节）——arch_baseline 从此可建立，arch 门禁不再永久空转
+- **门禁时序（重要 #5 + 一般 #16 #21）**：skip 物化限定最新迭代（防旧 SKIPPED 错误豁免）；iterations 数字排序（v10+）；FAIL 提示文案修正
+- **arch 门禁测试（重要 #10）**：新增 tests/lib/guard-arch-gates.test.mjs（7 例）；guard-dimensions 更新 16 维度 + arch-readiness 断言
+- **交接/决策门（重要 #12 #7 #6）**：change-brief 加 upstream_arch_ref；架构修订决策门 SOP 定义（deviation 登记）；API-INDEX 只扫已关闭 change；首轮特例状态标注；arch-snapshot 在途兜底
+- **guard hook + 门禁说明（重要 #9 #11）**：pre-tool-use-guard 豁免 docs/architecture/iterations/ + .team-flow/；workflow-start/release-archivist 补 arch 门禁说明 + FAIL 升级路径
+- **快照生命周期（重要 #8 + 一般 #17）**：s5-monitoring 迭代收尾标 archived；S3.5 补 domains/ + diagrams/ 产出 SOP
+- **旧项目链路（重要 #14 + 一般 #22）**：workflow-bootstrap 感知 arch-reverse-analyst/逆向重建（B5 + 修正陈旧指引）；recon-probe.sh 路径修正
+- **文档同步（一般 #15 #19 #20）**：AGENTS.md/README 目录树三层化；ch06/state-model/loading-protocol/模板 marker 陈旧修正；workspace 登记（design-doc-system/roadmap）
+- **横展（一般 #13 + 建议 #24 #25）**：arch-merge 白名单补 changelog/；doctor 加 arch-state 体检；cross-change 对照产品级注册表
+
 ## [0.36.2] - 2026-08-05
 
 ### Fixed

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

package/README.md

@@ -1,6 +1,6 @@
 # team-flow
 
-> 当前版本：`v0.36.2`
+> 当前版本：`v0.36.4`
 
 > 统一插件：**team-flow**（spec 驱动开发）+ **compound-engineering 核心子集**（全局复利）+ **architecture-design**（4A+DDD 增量设计）+ **prototype**（本地 HTML 原型）+ **e2e**（AC 驱动 E2E）+ **workflow-orchestrator**（产品级编排）+ **workflow-bootstrap**（既有项目接入）。一次安装，七套能力协同。
 
@@ -64,7 +64,7 @@ cp -r <plugin>/skills/prototype/references/prototype-scaffold/ <project>/prototy
 prd/               PRD + 实施方案 + 原型审查记录（v1→v2，分支隔离）
 prototype/         全局原型（UI 契约真相源）
 docs/
-  ├── architecture/  全局架构锚点（ARCHITECTURE.md / DATABASE.md / <bc>/ / baseline.md）
+  ├── architecture/  全局架构三层（v0.36.0）：ARCHITECTURE.md / PHYSICAL-MODEL.md / DATABASE.md / API-INDEX.md / INDEX.md / domains/<bc>.md / iterations/vN/（产品级快照）/ baseline.md
   └── solutions/     复利经验库（三层索引：INDEX.md → 分阶段目录 → 经验文件）
 specs/<cap>/        每变更设计/任务/契约 + learnings.md
 STRATEGY.md CONCEPTS.md 策略 / 领域词汇

package/agents/architecture-design.md

@@ -21,16 +21,27 @@ You are an independent architecture designer. You read the change brief, plan, e
 
 **Your preloaded Skill contains the detailed methodology** (F1-F8 frameworks, chapter knowledge, templates, conventions protocol, context loading protocol). Follow it for HOW. This prompt defines WHO you are and WHAT you must deliver.
 
+## Call Mode（v0.36.0：变更级 / 产品级）
+
+| 模式 | 编排入口 | 判定 | 产出 | 唯一事实源 |
+|------|---------|------|------|-----------|
+| change（默认） | workflow-start（exploring→specifying） | 五项检查 | `changes/<name>/architecture/` 三件套 + sql/ | 产品级快照（BC 边界/聚合注册表），只引用不重定义 |
+| product | workflow-orchestrator S3.5（ARCH 阶段） | 8 步全系统结构级设计（无五项检查） | `docs/architecture/iterations/vN/architecture.md`（6 产物） | 本快照是产品级唯一事实源 |
+
+**product 模式**：按 `references/s3.5-product-architecture.md` SOP（8 步）+ `references/s3.5-architecture-template.md` 模板 + `references/s3.5-loading-protocol.md` 加载协议；产出经 architecture-reviewer product 视角评审（`review_mode: product`）PASS 才进 S4；时序 P1：只写快照不写全局。
+
 ## Inputs
 
 | Parameter | Description |
 |-----------|-------------|
-| `change_brief_path` | change-brief.md 路径（scope / AC / 技术方向） |
+| `mode` | `change`（默认，workflow-start 五项检查）\| `product`（v0.36.0，S3.5 产品级架构设计） |
+| `change_brief_path` | change-brief.md 路径（scope / AC / 技术方向；change 模式必填） |
 | `plan_path` | prd/vN/plan.md 路径（高阶技术设计段） |
+| `snapshot_path` | docs/architecture/iterations/vN/architecture.md（产品级快照；change 模式主输入，product 模式产出目标） |
 | `specs_dir` | changes/<name>/specs/ 路径（现有规格，如有） |
 | `global_arch_dir` | docs/architecture/ 路径（As-Is 基线） |
 
-If change_brief_path is missing or unreadable, report `decision: skipped` with reason `INPUT_ERROR: change-brief missing`.
+If change_brief_path is missing or unreadable **in change mode**, report `decision: skipped` with reason `INPUT_ERROR: change-brief missing`. In product mode change_brief_path is optional（产品级设计发生在 change 存在之前）; 缺少时正常执行 8 步设计。
 
 ## Five-Check Gate (Architecture Change Determination)
 
@@ -44,7 +55,7 @@ Check the following five items in order. **All negative** → `decision: skipped
 
 ## Output Directory
 
-Architecture deliverables go in the change directory's `architecture/` subdirectory:
+**change 模式**（默认）：架构产出在 change 目录的 `architecture/` 子目录：
 
 ```
 changes/<name>/
@@ -57,11 +68,14 @@ changes/<name>/
         └── migration/           # Incremental migration scripts
 ```
 
+**product 模式**（v0.36.0）：产出在 `docs/architecture/iterations/vN/architecture.md`（6 产物：Context Map / 聚合注册表 / 指令事件 / 状态机 / 概念 ER / 时序），`snapshot_status: in-flight`，provenance 标注。**不写全局**（P1：预测态不进实际态）。
+
 ## Structured Output Contract
 
 Return the following YAML to the orchestration layer:
 
 ```yaml
+# change 模式
 decision: required | skipped
 reason: "..."                    # skipped: why no architecture changes
                                  # required: summary of architecture changes
@@ -71,6 +85,12 @@ artifacts:                       # required: list of produced files, skipped: em
   - architecture/api.md
   - architecture/sql/ddl/...
   - architecture/sql/migration/...
+
+# product 模式（v0.36.0）
+decision: completed | skipped    # completed: 8 步设计完成；skipped: 迭代无结构性变更（须物化 SKIPPED 标记）
+reason: "..."
+snapshot_path: docs/architecture/iterations/vN/architecture.md
+verdict: pending_review          # 评审门（architecture-reviewer product 视角）在产出后进行
 ```
 
 ## api.md Positioning — Architecture Routing Table
@@ -92,7 +112,7 @@ artifacts:                       # required: list of produced files, skipped: em
 
 **DON'T:**
 - Skip the five-check gate and jump to design
-- Load `baseline.md` or uninvolved domain sections (Skill defines what to load)
+- Load `baseline.md`（change 模式遵循 Skill 加载协议；**product 模式**须读 baseline.md + CONCEPTS.md 作输入，见 s3.5-product-architecture.md）
 - Embed SQL in markdown code blocks (use sql/ directory)
 - Produce api.md with Swagger-level detail (that's Swagger's job)
 - Produce artifacts when decision is `skipped`

package/agents/architecture-reviewer.md

@@ -11,7 +11,7 @@ You are an independent Architecture Consistency Reviewer. You check whether arch
 
 ## The Iron Law
 
-You are an independent reviewer. You did NOT participate in producing the architecture design. You read the deliverables fresh, compare them against the baseline and requirements, and report findings. You must NEVER write, edit, create, or delete any file. Your report is delivered in your response — the orchestration layer persists it to `changes/<name>/architecture/auto-review.md`.
+You are an independent reviewer. You did NOT participate in producing the architecture design. You read the deliverables fresh, compare them against the baseline and requirements, and report findings. You must NEVER write, edit, create, or delete any file. Your report is delivered in your response — the orchestration layer persists it to `changes/<name>/architecture/auto-review.md`（change 模式）或 `docs/architecture/iterations/vN/auto-review.md`（product 模式，v0.36.0）.
 
 ## Inputs
 
@@ -23,20 +23,24 @@ You are an independent reviewer. You did NOT participate in producing the archit
 | `architecture_dir` | 架构产出目录（e.g., `changes/<name>/architecture/`） |
 | `global_arch_dir` | 全局架构目录（e.g., `docs/architecture/`） |
 | `conventions_config` | conventions 配置（从 team-flow.config.json 读取的路径映射） |
-| `review_mode` | `change`（默认，审查 `changes/<name>/architecture/` 三件套）\| `product`（v0.35.0，审查 `docs/architecture/iterations/vN/architecture.md` 产品级快照） |
+| `review_mode` | `change`（默认，审查 `changes/<name>/architecture/` 三件套）\| `product`（v0.36.0，审查 `docs/architecture/iterations/vN/architecture.md` 产品级快照） |
+| `product_snapshot_path` | docs/architecture/iterations/vN/architecture.md（product 模式审查对象；v0.36.2 起 dispatch 传入） |
 
-If change_brief_path or architecture_dir is missing or unreadable, report `FAIL` with reason `INPUT_ERROR`.
+If change_brief_path or architecture_dir is missing or unreadable **in change mode**, report `FAIL` with reason `INPUT_ERROR`. In product mode，`change_brief_path` 可选（A4 对照源是 PRD 非 change-brief），审查对象是 `product_snapshot_path`；`product_snapshot_path` 缺失 → FAIL `INPUT_ERROR`。
 
-## Product Mode（v0.35.0，v0.14 §60.5）
+## Product Mode（v0.36.0，v0.14 §60.5）
 
 `review_mode: product` 时（S3.5 产品级评审门），审查对象与维度适配变化：
 
-- **审查对象**：`docs/architecture/iterations/vN/architecture.md`（6 产物：Context Map / 聚合注册表 / 指令事件 / 状态机 / 概念 ER / 时序）+ `domains/` 按域详细页；**不审查** change 内三件套。
-- **A1**：6 产物章节存在 + marker 成对 + anchor id 可解析（机械预检）。
+- **审查对象**：`product_snapshot_path`（`docs/architecture/iterations/vN/architecture.md`，6 产物：Context Map / 聚合注册表 / 指令事件 / 状态机 / 概念 ER / 时序）+ `domains/` 按域详细页；**不审查** change 内三件套。
+- **A1**：6 产物章节存在 + marker 成对 + anchor id 可解析（机械预检）；**不执行** change 模式的 `test -f architecture/{architecture,database,api}.md`。
+- **A2**：SQL/结构有效（若快照含 sql/ 引用；机械 grep）。
+- **A3**：对照 `references/s3.5-architecture-template.md`（产品级模板），非 `templates/architecture.md`（变更级模板）。
 - **A4**：对照 PRD 功能清单（F001_P0 逐条）→ BC/聚合/API 全覆盖映射；对照源是 PRD（非 change-brief——change-brief 是变更级输入）。
 - **A5**：旧项目逆向重建场景对照现状代码/全局基线；正向设计场景仅检查与既有基线无矛盾。
 - **A6**：conventions 合规（同 change 模式）。
 - **skip 处理**：S3.5 显式跳过（`iterations/vN/SKIPPED` 标记）时本 agent 不执行。
+- **报告落盘**：product 模式评审报告落盘 `docs/architecture/iterations/vN/auto-review.md`（非 `changes/<name>/architecture/auto-review.md`——product 模式无 change 目录）。
 
 ## 6-Dimension Checklist
 

package/agents/cross-change-consistency-checker.md

@@ -20,6 +20,7 @@ You are a read-only checker. You did NOT implement any change. You read all chan
 |-----------|-------------|
 | `change_dirs[]` | 多个 change 目录路径（e.g., `changes/change-1/`, `changes/change-2/`） |
 | `arch_path` | 全局架构目录（e.g., `docs/architecture/`，含 ARCHITECTURE.md / DATABASE.md） |
+| `product_snapshot_path` | 产品级架构快照 `docs/architecture/iterations/vN/architecture.md`（v0.36.3；聚合注册表唯一事实源，若存在） |
 | `prototype_path` | 全局原型目录（e.g., `prototype/`） |
 
 If `change_dirs` has fewer than 2 entries, Dim 1/2 are skipped (single change has no cross-change conflict). If `arch_path` or `prototype_path` is missing, the corresponding dimension is skipped with a note.
@@ -81,7 +82,7 @@ Use `grep` to search for API references across change specs and design docs.
 1. **Enumerate changes**: read each change directory's spec/design/tasks files
 2. **Dim 1**: Extract modified domain files per change, build mutation map, identify overlaps
 3. **Dim 2**: Extract API surface changes per change, cross-reference dependencies
-4. **Dim 3**: Read architecture anchors, compare each change against them
+4. **Dim 3**: Read architecture anchors **+ 产品级快照聚合注册表**（`product_snapshot_path`，v0.36.3——聚合注册表是唯一事实源，跨 change 冲突检测以它为准），compare each change against them
 5. **Dim 4**: Scan prototype testids, compare against change implementations
 6. **Aggregate**: collect all findings, grade by severity, produce report
 

package/docs/README_en.md

@@ -126,7 +126,7 @@ npm install -g team-flow
 
 ### Version
 
-- Current: `v0.36.2`
+- Current: `v0.36.4`
 - 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). 24 skills, one install.",
-  "version": "0.36.2",
+  "version": "0.36.4",
   "contextFileName": "GEMINI.md"
 }

package/hooks/pre-tool-use-guard

@@ -142,6 +142,21 @@ if [ -n "$file_path" ] && [ "${file_path##*/}" != ".team-flow.yaml" ]; then
   esac
 fi
 
+# --- v0.36.3 (§7.3): product-level architecture dir exemption ---------------
+# ARCH 阶段（S3.5）写 docs/architecture/iterations/ 快照、SKIPPED 标记、
+# .team-flow/ 产品级状态（orchestrator.yaml）是合法非 build 态写入。
+# .team-flow.yaml（change 状态）不在豁免内（state 禁写红线保留）。
+if [ -n "$file_path" ]; then
+  case "$file_path" in
+    */docs/architecture/iterations/*) allow ;;
+    */.team-flow/*) allow ;;
+  esac
+  case "${file_path#/private}" in
+    */docs/architecture/iterations/*) allow ;;
+    */.team-flow/*) allow ;;
+  esac
+fi
+
 # --- decision --------------------------------------------------------------
 case "$state" in
   approved-for-build|executing|debugging)

package/hooks/session-start

@@ -1,11 +1,11 @@
 #!/usr/bin/env bash
-# v0.36.2: auto-sync CLI version with plugin version
+# v0.36.4: auto-sync CLI version with plugin version
 set -e
 
 # ═══════════════════════════════════════════════════════════════
 # Plugin version (update this when releasing new versions)
 # ═══════════════════════════════════════════════════════════════
-PLUGIN_VERSION="0.36.2"
+PLUGIN_VERSION="0.36.4"
 
 # ═══════════════════════════════════════════════════════════════
 # 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.36.2.
+Current version: v0.36.4.
 
 ## 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.36.2",
+  "version": "0.36.4",
   "description": "Unified plugin (24 skills + 15 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.36.2",
+  "version": "0.36.4",
   "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). 24 skills + 15 agents, one install.",
   "author": {
     "name": "LT"

package/scripts/guard/checks/arch-gate-exemptions.mjs

@@ -39,30 +39,45 @@ export function isLegacyArch(state) {
   return state?.arch_baseline == null;
 }
 
-/** 项目级显式 skip 是否已物化（iterations/vN/SKIPPED 标记存在）。 */
-export function isArchSkipMaterialized(root) {
+/** 列出所有迭代目录（数字排序，v10 正确处理——字典序 v10 < v2 会取错最新）。 */
+export function listIterationDirs(root) {
   const iterationsDir = root && path.join(root, 'docs', 'architecture', 'iterations');
-  if (!iterationsDir || !fs.existsSync(iterationsDir)) return false;
+  if (!iterationsDir || !fs.existsSync(iterationsDir)) return [];
   return fs.readdirSync(iterationsDir, { withFileTypes: true })
     .filter(d => d.isDirectory())
-    .some(d => fs.existsSync(path.join(iterationsDir, d.name, 'SKIPPED')));
+    .map(d => d.name)
+    .sort((a, b) => {
+      const na = parseInt(a.replace(/\D/g, ''), 10) || 0;
+      const nb = parseInt(b.replace(/\D/g, ''), 10) || 0;
+      return na - nb;
+    });
+}
+
+/** 最新迭代目录路径（数字排序后最后）。无迭代 → null。 */
+export function findLatestIterationDir(root) {
+  const dirs = listIterationDirs(root);
+  if (dirs.length === 0) return null;
+  return path.join(root, 'docs', 'architecture', 'iterations', dirs[dirs.length - 1]);
+}
+
+/**
+ * skip 物化检查：只认最新迭代目录的 SKIPPED（v0.36.3 修复——防旧迭代陈旧标记
+ * 错误豁免新迭代的结构性变更，P3 原则要防的失效模式）。
+ */
+export function isArchSkipMaterialized(root) {
+  const latest = findLatestIterationDir(root);
+  if (!latest) return false;
+  return fs.existsSync(path.join(latest, 'SKIPPED'));
 }
 
 /** 最近一个迭代的产品级架构快照路径（iterations/<latest>/architecture.md）。不存在 → null。 */
 export function findLatestIterationSnapshot(root) {
-  const iterationsDir = root && path.join(root, 'docs', 'architecture', 'iterations');
-  if (!iterationsDir || !fs.existsSync(iterationsDir)) return null;
-  const dirs = fs.readdirSync(iterationsDir, { withFileTypes: true })
-    .filter(d => d.isDirectory())
-    .map(d => d.name)
-    .sort();
-  for (let i = dirs.length - 1; i >= 0; i--) {
-    const snap = path.join(iterationsDir, dirs[i], 'architecture.md');
-    if (fs.existsSync(snap)) return snap;
-  }
-  return null;
+  const latest = findLatestIterationDir(root);
+  if (!latest) return null;
+  const snap = path.join(latest, 'architecture.md');
+  return fs.existsSync(snap) ? snap : null;
 }
 
 export const ARCH_READINESS_FAIL_HINT =
-  'iterations/vN/architecture.md missing — 回 ARCH 阶段补快照，'
-  + '或显式 skip 物化（iterations/vN/<vN>/SKIPPED 标记 + 理由）';
+  'iterations/<vN>/architecture.md missing — 回 ARCH 阶段补快照，'
+  + '或显式 skip 物化（iterations/<vN>/SKIPPED 标记 + 理由）';

package/scripts/guard/checks/arch-snapshot.mjs

@@ -31,5 +31,12 @@ export function checkArchSnapshot(changeDir) {
   const snap = findLatestIterationSnapshot(root);
   if (snap) return { pass: true, failures: [] };
 
+  // v0.36.3 §63.4 在途 change 兜底：快照缺失但 change 已有增量产物 → 以 change 产物为实际态（存量升级场景）
+  const archDir = join(changeDir, 'architecture');
+  if (existsSync(archDir) && existsSync(join(archDir, 'architecture.md'))) {
+    console.warn('  [WARN] arch-snapshot: 产品级快照缺失，以 change 增量产物兜底（存量升级在途 change，快照后补为 v0）');
+    return { pass: true, failures: [] };
+  }
+
   return { pass: false, failures: [ARCH_READINESS_FAIL_HINT] };
 }

package/scripts/lib/arch-merge.mjs

@@ -120,9 +120,10 @@ function buildCurrentStateSection(aggregates, changeName) {
     lines.push(`| ${bc} | ${aggs.length} |`);
   }
   lines.push('', '### 聚合注册表');
-  lines.push('| 聚合ID | 上下文 | 根实体 | 来源 | 关键不变量 |', '|--------|--------|--------|------|-----------|');
+  // v0.36.3 §62.1 首轮特例：全局聚合全部来自已合并 change（=已落地态）；状态列标注
+  lines.push('| 聚合ID | 上下文 | 根实体 | 来源 | 状态 | 关键不变量 |', '|--------|--------|--------|------|------|-----------|');
   for (const a of aggregates) {
-    lines.push(`| ${a.id} | ${a.context} | ${a.root} | change:${changeName} | ${a.invariants || '—'} |`);
+    lines.push(`| ${a.id} | ${a.context} | ${a.root} | change:${changeName} | 已落地 | ${a.invariants || '—'} |`);
   }
   return lines.join('\n');
 }
@@ -224,10 +225,19 @@ function generateDatabase(globalArchDir, schemaPath) {
   return { generated: true, file: 'DATABASE.md', tables: tables.length };
 }
 
+/** v0.36.3 §62.4：判断 change 是否已关闭（读 .team-flow.yaml state）。 */
+function isChangeClosed(changeRoot) {
+  const stateFile = join(changeRoot, '.team-flow.yaml');
+  if (!existsSync(stateFile)) return false;
+  const m = readFileSync(stateFile, 'utf-8').match(/^state:\s*(.*)$/m);
+  const state = m ? m[1].trim() : '';
+  return state === 'closed' || state === 'closing';
+}
+
 /**
  * Step 6: API-INDEX.md 生成式（api-scan 核心）。
  * 扫描项目根下所有已关闭 change 的 architecture/api.md + domains/，归一化端点重建。
- * 保护：重建结果为空 → 拒绝覆盖（防历史手工端点被抹）。
+ * 保护：①重建结果为空 → 拒绝覆盖（防历史手工端点被抹）；②只扫已关闭 change（v0.36.3，在途半成品端点不得入全局）。
  */
 function generateApiIndex(projectRoot, globalArchDir, changeName) {
   const changesDir = join(projectRoot, 'changes');
@@ -237,7 +247,9 @@ function generateApiIndex(projectRoot, globalArchDir, changeName) {
   const endpoints = [];
   if (existsSync(changesDir)) {
     for (const changeDirName of readdirSync(changesDir)) {
-      const apiPath = join(changesDir, changeDirName, 'architecture', 'api.md');
+      const changeRoot = join(changesDir, changeDirName);
+      if (!isChangeClosed(changeRoot)) continue; // v0.36.3：只扫已关闭 change
+      const apiPath = join(changeRoot, 'architecture', 'api.md');
       if (!existsSync(apiPath)) continue;
       const ep = extractEndpoints(readFileSync(apiPath, 'utf-8'));
       for (const e of ep) endpoints.push({ ...e, source: changeDirName });
@@ -378,14 +390,17 @@ function preCheck(changeDir, archDir, projectRoot) {
 /* ============ Step 5: 变更脚本归档（保留） ============ */
 
 function archiveChangeScripts(changeDir, archDir, globalArchDir, changeName) {
-  const report = { ddl: 0, migration: 0 };
+  const report = { ddl: 0, migration: 0, files: [] };
   for (const subDir of ['ddl', 'migration']) {
     const srcDir = join(archDir, 'sql', subDir);
     const dstDir = join(globalArchDir, 'changelog', subDir);
     if (!existsSync(srcDir)) continue;
     if (!existsSync(dstDir)) makeDir(dstDir);
     const files = readdirSync(srcDir).filter(f => f.endsWith('.sql'));
-    for (const f of files) copyFile(join(srcDir, f), join(dstDir, f));
+    for (const f of files) {
+      copyFile(join(srcDir, f), join(dstDir, f));
+      report.files.push(join(dstDir, f)); // v0.36.3：changelog 文件入白名单（防自我制造脏文件告警）
+    }
     report[subDir] += files.length;
   }
   return report;
@@ -513,6 +528,7 @@ export function run(args = {}) {
       join(globalArchDir, 'schema-baseline.sql'),
       join(globalArchDir, 'API-INDEX.md'),
       join(globalArchDir, 'INDEX.md'),
+      ...(archiveResult.files || []),  // v0.36.3：changelog/ 复制文件入白名单
     ].filter(p => existsSync(p));
     const dirty = detectUntouchedDirtyFiles(globalArchDir, touchedFiles);
     if (dirty.length > 0) {

package/scripts/lib/cmd-doctor.mjs

@@ -299,6 +299,32 @@ function checkChangeTestGates(root) {
   return { pass: true, message: `${checked} change(s) pass test-gate hygiene (skip reasons + artifact references)` };
 }
 
+// v0.36.3 建议项：arch-state / iterations 一致性体检
+// 1. arch_baseline 已打戳但 iterations/ 无任何产品级快照 → arch 门禁将 FAIL（需回 ARCH 补快照）
+// 2. SKIPPED 与快照并存 → 语义矛盾
+function checkArchState(root) {
+  const warnings = [];
+  const archStatePath = join(root, '.team-flow', 'arch-state.json');
+  const iterationsDir = join(root, 'docs', 'architecture', 'iterations');
+  if (existsSync(archStatePath)) {
+    const hasSnapshot = existsSync(iterationsDir)
+      && readdirSync(iterationsDir, { withFileTypes: true })
+        .filter(d => d.isDirectory())
+        .some(d => existsSync(join(iterationsDir, d.name, 'architecture.md')));
+    if (!hasSnapshot) {
+      warnings.push('arch_baseline 已打戳但 iterations/ 无产品级快照——arch-readiness/arch-snapshot 门禁将 FAIL，需回 ARCH 阶段补快照');
+    }
+  }
+  if (existsSync(iterationsDir)) {
+    for (const d of readdirSync(iterationsDir, { withFileTypes: true }).filter(x => x.isDirectory())) {
+      const hasSkip = existsSync(join(iterationsDir, d.name, 'SKIPPED'));
+      const hasSnap = existsSync(join(iterationsDir, d.name, 'architecture.md'));
+      if (hasSkip && hasSnap) warnings.push(`${d}: SKIPPED 与快照并存，语义矛盾`);
+    }
+  }
+  return { pass: warnings.length === 0, message: warnings.length ? warnings.join('; ') : 'arch-state/iterations 一致' };
+}
+
 export async function run(args) {
   const root = process.cwd();
   const config = loadConfig(root);
@@ -317,6 +343,7 @@ export async function run(args) {
     ['Docs', checkDocs(root)],
     ['Change states', checkChangeStates(root)],
     ['Change test gates', checkChangeTestGates(root)],
+  ['Arch state', checkArchState(root)],
   ];
 
   // Config check

package/scripts/lib/solutions-capture.mjs

@@ -14,7 +14,7 @@
 import { readFileSync, writeFileSync, existsSync, mkdirSync, appendFileSync } from 'node:fs';
 import { join } from 'node:path';
 
-const PHASES = ['prd', 'plan', 'prototype', 'spec', 'build', 'review', 'cross-phase'];
+const PHASES = ['prd', 'plan', 'architecture', 'prototype', 'spec', 'build', 'review', 'cross-phase'];
 const MAX_INDEX_LINES = 150;
 
 function slugify(text) {

package/skills/architecture-design/SKILL.md

@@ -90,6 +90,16 @@ description: 基于 4A 企业架构 + DDD 领域驱动设计的架构/API/DB 设
 
 变更级聚合动作限三类：`extend`（既有聚合加字段/指令/事件/状态）、`new`（新增聚合，flag 登记待产品级晋升）、`refactor`（需决策门）。聚合 id 一律引用产品级注册表，不重定义（防重发明，v0.14 §61.3）。
 
+### 架构修订决策门（v0.36.3 定义，v0.14 §61.3/§61.4）
+
+**触发**：change 级设计触及产品级决策（BC 边界变更 / 聚合所有权变更 / 全局契约变更），或 arch-merge 冲突预检阻断聚合重定义。
+
+**流程**（不硬阻断，显式确认 + 登记 deviation）：
+1. **呈现变更摘要**：涉及的产品级决策 + 影响范围（引用快照章节）
+2. **用户确认**（阻塞问题工具）：接受 → 执行变更；拒绝 → 保持产品级定义，change 内走增量
+3. **登记 deviation**：确认后写入 `orchestrator.yaml` 的 `replan_log`（`seq/trigger: arch-deviation/before/after/approved_by`）+ 在 `iterations/vN/architecture.md` 演进日志追加修订记录（迭代收尾 S3.5 确认晋升）
+4. **`new` 聚合 flag**：在 `iterations/vN/architecture.md` 聚合注册表标注 `[pending-promotion]`，待下一迭代产品级晋升
+
 ### 执行流程
 
 ```
@@ -182,6 +192,10 @@ architecture-design 执行时的上下文组装：
 3. 读取匹配的 `.team-flow/conventions/*.md` 文件
 4. 注入为架构决策约束（advisory 级）
 
+**架构复利注入（v0.36.3，复利链路修复）**：
+1. 执行 `tf solutions inject --phase architecture`（失败静默）——注入 `docs/solutions/` 中 phase=architecture 的历史架构决策经验（BC 边界取舍/聚合划分理由/事件投影设计踩坑）
+2. 读取失败 / 无条目 → 静默跳过，不阻断（advisory 级，与 S1 复利注入同语义）
+
 **始终加载**：
 1. `Read docs/architecture/INDEX.md`（~50行摘要）
 2. `Read changes/<name>/change-brief.md`（如有）