@xulthekl/team-flow 0.45.0 → 0.47.0

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

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

package/.claude-plugin/marketplace.json

@@ -1,6 +1,6 @@
 {
   "name": "team-flow",
-  "description": "Unified workflow plugin: team-flow + compound-engineering core subset + architecture-design + prototype + workflow-orchestrator + workflow-bootstrap + e2e + session-handoff + workflow-feedback + business-analysis. 25 skills + 16 agents, one install.",
+  "description": "Unified workflow plugin: team-flow + compound-engineering core subset + architecture-design + prototype + workflow-orchestrator + workflow-bootstrap + e2e + session-handoff + workflow-feedback + business-analysis. 26 skills + 17 agents, one install.",
   "owner": {
     "name": "LT",
     "url": "https://github.com/LT"
@@ -8,8 +8,8 @@
   "plugins": [
     {
       "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. 25 skills + 16 agents with embedded TDD, SDD, code review, debugging, delta spec sync, and design-system-driven prototyping.",
-      "version": "0.45.0",
+      "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.47.0",
       "source": "./",
       "author": {
         "name": "LT",

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "team-flow",
-  "version": "0.45.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). 25 skills + 16 agents, one install.",
+  "version": "0.47.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). 26 skills + 17 agents, one install.",
   "source": "./",
   "author": {
     "name": "LT",

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "team-flow",
-  "version": "0.45.0",
+  "version": "0.47.0",
   "description": "Spec-first workflow that bridges OpenSpec-style planning and Superpowers-style execution discipline.",
   "author": {
     "name": "MageByte",
@@ -26,7 +26,7 @@
   "interface": {
     "displayName": "team-flow",
     "shortDescription": "Spec-first workflow with guarded execution.",
-    "longDescription": "A self-contained Codex workflow plugin with 25 skills for intent exploration, planning artifacts, execution contracts, TDD execution, review gates, systematic debugging, closure, delta spec sync, and independent business analysis.",
+    "longDescription": "A self-contained Codex workflow plugin with 26 skills for intent exploration, planning artifacts, execution contracts, TDD execution, review gates, systematic debugging, closure, delta spec sync, and independent business analysis.",
     "developerName": "MageByte",
     "category": "Developer Tools",
     "composerIcon": "./assets/icon.svg",

package/.cursor-plugin/marketplace.json

@@ -5,13 +5,13 @@
   },
   "metadata": {
     "description": "Unified workflow plugin marketplace for Cursor (team-flow: team-flow + compound + architecture-design + prototype).",
-    "version": "0.45.0"
+    "version": "0.47.0"
   },
   "plugins": [
     {
       "name": "team-flow",
       "source": ".",
-      "description": "Unified workflow plugin: team-flow + compound-engineering core subset + architecture-design + prototype + business-analysis. 25 skills + 16 agents."
+      "description": "Unified workflow plugin: team-flow + compound-engineering core subset + architecture-design + prototype + business-analysis. 26 skills + 17 agents."
     }
   ]
 }

package/.cursor-plugin/plugin.json

@@ -1,8 +1,8 @@
 {
   "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). 25 skills + 16 agents, one install.",
-  "version": "0.45.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). 26 skills + 17 agents, one install.",
+  "version": "0.47.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.45.0"
+    "version": "0.47.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.45.0",
+      "version": "0.47.0",
       "source": ".",
       "author": {
         "name": "LT",

package/AGENTS.md

@@ -1,6 +1,6 @@
 # AGENTS.md · team-flow
 
-> team-flow 统一插件 = **team-flow**（spec 驱动开发）+ **compound-engineering 核心子集**（全局复利）+ **architecture-design**（4A+DDD 增量设计）+ **prototype**（本地 HTML 原型）+ **e2e**（AC 驱动 Playwright E2E）+ **workflow-orchestrator**（产品级编排）+ **workflow-bootstrap**（既有项目接入）。一次安装，七套能力协同（25 skills + 16 agents），支持 9 安装面（Claude Code, Cursor, OpenAI Codex CLI/App, GitHub Copilot CLI, Gemini CLI, OpenCode, WorkBuddy, Trae, ima-copilot）。
+> team-flow 统一插件 = **team-flow**（spec 驱动开发）+ **compound-engineering 核心子集**（全局复利）+ **architecture-design**（4A+DDD 增量设计）+ **prototype**（本地 HTML 原型）+ **e2e**（AC 驱动 Playwright E2E）+ **workflow-orchestrator**（产品级编排）+ **workflow-bootstrap**（既有项目接入）。一次安装，七套能力协同（26 skills + 17 agents），支持 9 安装面（Claude Code, Cursor, OpenAI Codex CLI/App, GitHub Copilot CLI, Gemini CLI, OpenCode, WorkBuddy, Trae, ima-copilot）。
 
 ## What This Is
 
@@ -12,7 +12,7 @@
 
 ### 身份与依赖关系
 
-- **team-flow**（本插件）：Claude Code / Cursor 等宿主的插件实体（`plugin.json` name = `team-flow`），包含 25 个 skills + 16 个 agents + hooks + templates
+- **team-flow**（本插件）：Claude Code / Cursor 等宿主的插件实体（`plugin.json` name = `team-flow`），包含 26 个 skills + 17 个 agents + hooks + templates
 - **@xulthekl/team-flow**（npm 底座包）：team-flow 的 CLI 工具层（`package.json` name = `@xulthekl/team-flow`，bin = `tf` / `team-flow`），提供状态机、校验、复利 CLI 等运行时能力
 - 关系：team-flow 插件 **包含** @xulthekl/team-flow npm 包作为底座（同一仓库、同一版本）。skills 中的 `tf ...` 调用的是已全局安装的 @xulthekl/team-flow CLI，版本由 session-start hook 自动同步
 - 历史身份（已废弃）：`spec-superflow`（npm 包名，0.11.0 后停止发布）/ `ssf`（CLI 前缀）/ `.spec-superflow.yaml`（状态文件）—— 详见设计增强方案 v0.9 §27
@@ -33,7 +33,7 @@ node --test tests/e2e.test.mjs --test-name-pattern="parseDeltaSpec"
 npm run validate
 ```
 
-## 能力概览（十套合一，25 skills）
+## 能力概览（十套合一，26 skills）
 
 ### 1. team-flow（底座，9 skills）
 spec 驱动开发过程。8 态变更机：`exploring → specifying → bridging → approved-for-build → executing → closing`（另有 `debugging` 侧路径 + `abandoned` 终态）。
@@ -61,7 +61,7 @@ spec 驱动开发过程。8 态变更机：`exploring → specifying → bridgin
 - 用法：`/e2e [原型|集成|验收] [spec路径]`
 
 ### 6. workflow-orchestrator（1 skill，产品级编排，v0.7 重设计 + v0.15.0 多需求）
-- 编排产品级工作流：S1 路径路由（含需求选择）→ S2 PRD+原型（循环上提，orchestrator 直接编排，**冻结前 PRD 完整性评审**）→ S3 ce-plan（pipeline 快速路径，**入口问定 plan_mode**）→ **ARCH 产品级架构设计（v0.36.0：architecture-design product 模式 8 步 → iterations/vN/architecture.md 快照 → 评审门 PASS 才进 S4）** → S4 拆分验证+分发 → S5 全局监控
+- 编排产品级工作流：S1 路径路由（含需求选择）→ S2 PRD+原型（循环上提，orchestrator 直接编排，**冻结前 PRD 完整性评审**）→ **ARCH 产品级架构设计（v0.36.0：architecture-design product 模式 8 步 → iterations/vN/architecture.md 快照 → 评审门 PASS 才进 S3；2026-08-19 上移 S3 前，S3 计划/S4 拆分是最终任务拆分须基于架构）** → S3 ce-plan（pipeline 快速路径，**入口问定 plan_mode**，基于 ARCH 架构定稿）→ S4 拆分验证+分发 → S5 全局监控
 - v0.7 关键变更：原型循环从 ce-brainstorm 内部上提到 orchestrator 层直接编排；新增反馈环路（vN 内修订+变更履历，非升版）；新增增量入口（S1 路径路由器，**7 种入口路径**，v0.20.0 增「原型补跑/重跑」）；S5 多 change 并行时必选
 - **v0.20.0**：S1 路由新增第 7 种入口「原型补跑/重跑」（PRD 冻结 ∧ prototype 缺失/需重做 → 部分重入 S2 原型循环，PRD 不动、保留有效 S3/S4）；后台子代理等待范式（依赖完成通知，禁 TaskOutput 轮询）（设计 §22）
 - **v0.15.0 多需求并行**：`.team-flow/registry.yaml` 注册表 + 每需求一份 `.team-flow/requirements/<req-id>/orchestrator.yaml`，状态天然隔离
@@ -143,8 +143,8 @@ STRATEGY.md CONCEPTS.md 产品策略(BA) / 领域词汇
   S3 计划阶段 → ce-plan（pipeline 快速路径，入口问定 plan_mode）
      plan.md：change 拆分 + 依赖 DAG + 高阶技术方向（不含接口清单）
      反馈环路：plan 暴露 PRD 问题可回退 S2
-  [ARCH 产品级架构设计（v0.36.0）] → architecture-design product 模式 8 步设计
-     → docs/architecture/iterations/vN/architecture.md（6 产物快照，预测态不写全局）→ 评审门 PASS 才进 S4
+  [ARCH 产品级架构设计（v0.36.0；2026-08-19 上移 S3 前）] → architecture-design product 模式 8 步设计
+     → docs/architecture/iterations/vN/architecture.md（6 产物快照，预测态不写全局）→ 评审门 PASS 才进 S3
      skip 须物化（iterations/vN/SKIPPED）；旧项目首轮 arch_baseline 缺失 → 逆向重建
   S4 拆分验证与分发 → arch-readiness 门（快照覆盖 change 触及 BC）→ change-split-auditor 审计（必选门禁）→ 创建 change → 进入 team-flow
      并行策略建议 + 验收标准预分配；反馈环路：依赖图不可执行可回退 S3
@@ -174,7 +174,7 @@ STRATEGY.md CONCEPTS.md 产品策略(BA) / 领域词汇
   全局作为下一 change / 下一 PRD 版本的 grounding → 闭环
 ```
 
-## Skills 索引（25 个）
+## Skills 索引（26 个）
 
 | Skill | 归属 | 用途 |
 |---|---|---|
@@ -203,6 +203,7 @@ STRATEGY.md CONCEPTS.md 产品策略(BA) / 领域词汇
 | session-handoff | 会话交接 | 上下文腐化时压缩会话为交接文档（v0.16.0） |
 | workflow-feedback | 工作流反馈 | 工作流问题结构化记录（v0.16.0） |
 | business-analysis | 独立业务分析 | 将任意输入整理为 requirement/vN/business-analysis.md（独立外挂，v0.44.0） |
+| project-initialize | 项目初始化引导 | 工作空间代码服务为空时：架构选择（glaf4/前端分离/单体微服务/拆分）→ 服务命名确认 → 创建服务子目录 → 委托初始化（glaf4 走 glaf4-dev，非 glaf4 走内置引导）（v0.45.0） |
 
 ### 触发域分层（v0.12.0 新增）
 
@@ -219,7 +220,7 @@ STRATEGY.md CONCEPTS.md 产品策略(BA) / 领域词汇
 
 > **规则**：新增 skill 时必须在此表登记所属层级。产品级新需求触发词归 workflow-orchestrator 独占。
 
-### Agents 索引（v0.7 新增，v0.30.0 增至 16 个）
+### Agents 索引（v0.7 新增，v0.47.0 增至 17 个）
 
 > **agent 文件设计规范见 CONTRIBUTING.md §6 + `templates/agent-template.md`**（v0.33.0）：frontmatter 必须合法 YAML（非法时 Claude Code 静默降级，skills: 预加载与 tools: 限制全部失效）；description 单句、禁 `<example>` 块；新增/修改 agent 必过 frontmatter-lint + 实证探针。
 
@@ -231,7 +232,8 @@ STRATEGY.md CONCEPTS.md 产品策略(BA) / 领域词汇
 | change-split-auditor | plan.md 拆分质量审计 | Read/Bash/Grep/Glob | orchestrator S4 脚手架前（必选门禁，PASS 方可继续） |
 | code-reviewer | spec 合规审查（批次完成/合并门禁） | Read/Bash/Grep/Glob | build-executor 批次完成、release-archivist 合并前 |
 | cross-change-consistency-checker | 跨 change 冲突检测 | Read/Bash/Grep/Glob | orchestrator S5 多 change 并行/closing 时 |
-| prd-completeness-reviewer | PRD 完整性评审（能否支撑 plan/spec，5 维度） | Read/Bash/Grep/Glob | orchestrator S2 / ce-brainstorm 冻结前门禁（v0.15.0） |
+| prd-completeness-reviewer | PRD 完整性评审（能否支撑 plan/spec，6 维度含 §8.4 契约级细节 D6） | Read/Bash/Grep/Glob | orchestrator S2 / ce-brainstorm 冻结前门禁（v0.15.0，v0.47.0 并入 D6） |
+| prd-writer | PRD 撰写 agent——契约级 §8.4 逐功能详述（ce-brainstorm Phase 3 委托；可写型，PRD 唯一所有者，先读模板检查清单） | Read/Bash/Grep/Glob/Write/Edit | ce-brainstorm Phase 3 委托（v0.47.0） |
 | prototype-builder | 原型绘制执行者（种子优先：template.html+layouts.md 组合；**v0.20.0 产物落盘硬闸门**：index.html 未落盘非空禁返 done + 大产出分片；**v0.21.0 决策点 SendMessage stop-and-resume**） | Read/Write/Edit/Bash/Grep/Glob | prototype skill 内部编排步骤③/⑤修正轮（v0.15.0，v0.18.0 种子优先） |
 | prototype-env-scout | 原型环境探查 + 2-3 差异化方向（direction-picker；**v0.20.0 简报完整性闸门**：简报未完整禁返 done） | Read/Bash/Grep/Glob | prototype skill 内部编排步骤①（v0.15.0，v0.18.0 direction-picker） |
 | prototype-reviewer | PRD 6 维度 + P0 grep + craft 4 席 rubric 评审 | Read/Bash/Grep/Glob | orchestrator S2 原型循环每轮产出后 |

package/CHANGELOG.md

@@ -4,6 +4,37 @@ All notable changes to `team-flow` will be documented in this file.
 
 The format loosely follows Keep a Changelog.
 
+## [0.47.0] - 2026-08-21
+
+### Added（PRD §8.4 契约级详述规范，v0.47.0）
+
+设计来源：`docs/architecture-api-db-design-enhancement-v0.20.md` §81（2026-08-21，来源 workflow-feedback 20260821-131256 P1 artifact-quality）
+
+- **重构 `templates/prd.md` §8.4 契约级检查清单**：UI 功能 11 维（页面布局/权限规则/区块说明/搜索模块/表格列定义/交互规则/弹层结构/动态字段/导入导出规则/状态操作差异/异常边界）+ 非 UI 功能 7 维（触发条件/输入输出/处理步骤/异常处理/权限角色/幂等并发/性能约束）双形态；NA 机制（不适用须标注 NA+理由，未标注且未覆盖=缺失）；模板为单一权威
+- **`prd-brainstorm-profile.md` 新增「功能细节（契约级）」核心维度**（替代按需扩展）：Standard/Deep 强制契约级澄清，产出 detail_ledger（`requirement/vN/detail-ledger.md`）
+- **新增 `prd-writer` agent**：ce-brainstorm Phase 3 委托撰写（写法 2 预加载 ce-brainstorm，Iron Law=先读模板 §8.4 检查清单，不提问、不虚构、missing_info 回传，PRD 唯一所有者）
+- **`prd-completeness-reviewer` 并入 D6 维度**（5 维→6 维）：§8.4 契约级细节——核心维度缺失/悬空功能=Critical，辅助维度缺失=Important；detail_ledger 交叉核对（澄清已确认但 PRD 缺失/标 NA=Critical）；`template_path` 入参（自定义模板支持）
+- **ce-brainstorm 流程更新**：Phase 1.3b 功能细节澄清 + Phase 3 委托 prd-writer + QA-4 派发归并（standalone→Phase 3.5 §3.5.5、orchestrated→orchestrator S2 step 3.5，QA-4 不重复派发）+ 完整性评审全路径门禁（有原型/非 UI/跳过原型三路径均强制派发）
+- **orchestrated 路径补齐**：s2-prd-prototype-loop.md step 3.5（冻结前完整性评审门禁，补此前纯后端/跳过原型路径静默漏评审缺口）
+- agent 计数 16→17 全平台同步（plugin.json / .claude-plugin / .cursor-plugin / package.json / AGENTS.md / README / usage-guide）
+- 710/710 测试通过
+
+## [0.46.0] - 2026-08-19
+
+### Added（PROJECT_INITIALIZE 场景 + project-initialize skill + ARCH 上移，v0.46.0）
+
+设计来源：`docs/plan/glaf4-dev-integration-design.md` v2.1 §6.5（2026-08-19 LT 定案）
+
+- **新增 `project-initialize` skill**：产品级初始化引导流程——识别需初始化 → 引导新会话 → 架构选择（glaf4 体系/前端分离/单体微服务/拆分）→ 服务命名确认 → team-flow 创建空服务子目录（git init + .gitignore）→ 委托初始化（glaf4 走 glaf4-dev PROJECT_INITIALIZE，非 glaf4 走 workflow-bootstrap B1.5）；3 references（architecture-choice / service-layout / glaf4-initialize-delegation）
+- **触发接入**（编排层 Pre-check 检测驱动，不靠用户显式触发）：
+  - orchestrator ARCH 评审 PASS 后、S3 前：Pre-check 1 服务初始化检测（场景①）
+  - workflow-start Route to build-executor 前：Pre-check 2 服务缺漏检测（场景②，AskUserQuestion 区分"未拉取 git pull"vs"需要初始化"）
+- **ARCH 上移 S3 前**（LT 决策）：S3 计划/S4 拆分是最终任务拆分须基于架构——orchestrator / CLAUDE.md SOP / architecture-design / state-model / s3-plan-pipeline 统一"PASS 才进 S3"
+- **实证闭合**：gen-service 空目录冲突（run 树 .glaf4-dev 存在 → `out dir not empty` BLOCKED）+ 环境就绪（JDK8 + 本地 gtmc-glaf4-starter-parent + 空目录生成 92 文件）
+- **双评审修复**：skill-reviewer（B1 gen-service 缓解补 .git/.gitignore 白名单化 + M1 bootstrap 契约 + M2 触发场景）+ code-reviewer（F1-F3 ARCH 残留/计数同步）
+- skill 计数 25→26 全平台同步（plugin.json / .claude-plugin / .cursor-plugin / .codex-plugin / gemini-extension / README / AGENTS）
+- 708/708 测试通过
+
 ## [0.45.0] - 2026-08-18
 
 ### Added（glaf4-dev 集成增强，v0.45.0）

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

package/README.md

@@ -1,6 +1,6 @@
 # team-flow
 
-> 当前版本：`v0.45.0`
+> 当前版本：`v0.47.0`
 
 > 统一插件：**team-flow**（spec 驱动开发）+ **compound-engineering 核心子集**（全局复利）+ **architecture-design**（4A+DDD 增量设计）+ **prototype**（本地 HTML 原型）+ **e2e**（AC 驱动 E2E）+ **workflow-orchestrator**（产品级编排）+ **workflow-bootstrap**（既有项目接入）。一次安装，七套能力协同。
 
@@ -34,7 +34,7 @@
 git clone <your-repo> && <cli> plugin install ./team-flow
 ```
 
-> 不同宿主 CLI 的安装子命令略有差异（如 Claude Code 为 `/plugin add`，Cursor 为 `plugin install`）。以宿主文档为准；本插件提供单一 `plugin.json`，一次安装即加载全部 25 个 skills。
+> 不同宿主 CLI 的安装子命令略有差异（如 Claude Code 为 `/plugin add`，Cursor 为 `plugin install`）。以宿主文档为准；本插件提供单一 `plugin.json`，一次安装即加载全部 26 个 skills。
 
 ## 配置（插件层扩展字段）
 
@@ -70,7 +70,7 @@ specs/<cap>/        每变更设计/任务/契约 + learnings.md
 STRATEGY.md CONCEPTS.md 策略 / 领域词汇
 ```
 
-## 十套能力（25 skills）
+## 十套能力（26 skills）
 
 - **team-flow**（9）：workflow-start / need-explorer / spec-writer / contract-builder / build-executor / code-reviewer / spec-merger / release-archivist / bug-investigator
 - **compound 核心子集**（6）：ce-brainstorm / ce-plan / ce-compound / ce-strategy / ce-ideate / ce-proof
@@ -84,9 +84,9 @@ STRATEGY.md CONCEPTS.md 策略 / 领域词汇
 - **设计系统**（1）：design-system（独立创建/迭代项目级设计系统，用户主导交互，v0.19.0）
 - **业务分析**（1）：business-analysis（将任意输入整理为 requirement/vN/business-analysis.md，多轮单问澄清，独立外挂，v0.44.0）
 
-### 配套 agents（16 个，v0.30.0 增至 16）
+### 配套 agents（17 个，v0.47.0 增至 17）
 
-全部由编排层 dispatch（主代理只编排，need-explorer 为主进程交互式澄清）：architecture-design（架构设计门控）/ architecture-reviewer（架构自动审查）/ bug-investigator（bug 根因调查）/ change-split-auditor（拆分质量审计）/ code-reviewer（代码审查）/ cross-change-consistency-checker（跨 change 一致性）/ prd-completeness-reviewer（PRD 完整性评审）/ prototype-builder（原型绘制）/ prototype-env-scout（原型环境探查）/ prototype-reviewer（原型评审）/ need-explorer（需求探索）/ spec-writer（规格编写）/ contract-builder（执行契约构建）/ build-executor（TDD 构建执行）/ release-archivist（发布归档）/ business-analysis（独立业务分析）。
+全部由编排层 dispatch（主代理只编排，need-explorer 为主进程交互式澄清）：architecture-design（架构设计门控）/ architecture-reviewer（架构自动审查）/ bug-investigator（bug 根因调查）/ change-split-auditor（拆分质量审计）/ code-reviewer（代码审查）/ cross-change-consistency-checker（跨 change 一致性）/ prd-completeness-reviewer（PRD 完整性评审，含 §8.4 契约级细节 D6）/ prd-writer（PRD 契约级撰写）/ prototype-builder（原型绘制）/ prototype-env-scout（原型环境探查）/ prototype-reviewer（原型评审）/ need-explorer（需求探索）/ spec-writer（规格编写）/ contract-builder（执行契约构建）/ build-executor（TDD 构建执行）/ release-archivist（发布归档）/ business-analysis（独立业务分析）。
 
 ### 命名约定
 

package/agents/architecture-design.md

@@ -28,7 +28,7 @@ You are an independent architecture designer. You read the change brief, plan, e
 | 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：只写快照不写全局。
+**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 才进 S3（2026-08-19：ARCH 上移 S3 前，原"进 S4"）；时序 P1：只写快照不写全局。
 
 ## Inputs
 

package/agents/prd-completeness-reviewer.md

@@ -1,13 +1,13 @@
 ---
 name: prd-completeness-reviewer
-description: PRD 完整性自动评审。在 PRD 写入后、冻结前，独立检查"需求描述是否完整到能支撑后续 plan/spec 实施"（5 维度），输出分级完整性报告。直接写审查报告文件，返回摘要 + 文件路径。与 claim verifier 分工——claim verifier 管"说得对不对"（核查事实声明），本 agent 管"说得全不全、能否落地"。
+description: PRD 完整性自动评审。在 PRD 写入后、冻结前，独立检查"需求描述是否完整到能支撑后续 plan/spec 实施"（6 维度，含 §8.4 契约级细节 D6），输出分级完整性报告。直接写审查报告文件，返回摘要 + 文件路径。与 claim verifier 分工——claim verifier 管"说得对不对"（核查事实声明），本 agent 管"说得全不全、能否落地"。由编排层在 PRD 冻结前显式派发（workflow-orchestrator S2 / ce-brainstorm Phase 3.6 前）。
 
 model: inherit
 color: yellow
 tools: ["Read", "Bash", "Grep", "Glob", "Write"]
 ---
 
-You are an independent PRD Completeness Reviewer. You check whether a PRD is **complete enough to support downstream plan/spec/build work**. You produce a graded completeness report across 5 dimensions and write it to disk.
+You are an independent PRD Completeness Reviewer. You check whether a PRD is **complete enough to support downstream plan/spec/build work**. You produce a graded completeness report across 6 dimensions and write it to disk.
 
 ## The Iron Law
 
@@ -26,10 +26,12 @@ Do NOT duplicate claim verification. A statement can be factually correct yet st
 |-----------|-------------|
 | `prd_path` | PRD 文件路径（e.g., `requirement/v1/prd.md`） |
 | `concepts_path` | （可选）CONCEPTS.md 路径，用于术语一致性比对 |
+| `template_path` | PRD 模板路径（可选，默认 `templates/prd.md`；§8.4 检查清单单一权威，以解析后的模板为基准） |
+| `detail_ledger_path` | （可选）detail_ledger 路径（功能细节澄清产出；存在时用于 D6 交叉核对 NA 标注一致性） |
 
 If `prd_path` is missing or unreadable, report `FAIL` with reason `INPUT_ERROR`.
 
-## 5-Dimension Checklist
+## 6-Dimension Checklist
 
 | Dim | Name | Check Content | Severity |
 |-----|------|---------------|----------|
@@ -38,6 +40,7 @@ If `prd_path` is missing or unreadable, report `FAIL` with reason `INPUT_ERROR`.
 | D3 | 边界与非功能 | 空/错/异常状态、性能/兼容约束 | Important |
 | D4 | 术语一致性 | 与 CONCEPTS.md / §6 业务术语一致 | Minor |
 | D5 | 范围闭环 | in/out scope 明确，无悬空功能 | Important |
+| D6 | §8.4 契约级细节 | 逐功能模块按模板检查清单覆盖适用维度（UI 11 维/非 UI 7 维）；§7↔§8.4 交叉核对无悬空功能。**基准 = 模板 §8.4 检查清单（单一权威）** | Critical（核心维度缺失/悬空）/ Important（辅助维度缺失） |
 
 ## Review Process
 
@@ -71,6 +74,14 @@ If `prd_path` is missing or unreadable, report `FAIL` with reason `INPUT_ERROR`.
    - Any out-of-scope item that other requirements implicitly depend on?
    Missing scope declaration or dangling feature = Important.
 
+8. **D6 §8.4 契约级细节完整度**：Read the template §8.4 checklist FIRST — `template_path`（默认 `templates/prd.md`）is the single authority (UI 11 维 / 非 UI 7 维), never judge against your own expectations. Then for each function module in the PRD §8.4:
+   - 判定功能形态（UI/非 UI），按对应维度清单核对覆盖度；**未标注 NA 且未覆盖的适用维度 = 缺失**
+   - **核心维度缺失 = Critical**：功能概述缺失；UI 页面布局/表格列定义缺失；非 UI 输入输出/处理步骤/异常处理缺失
+   - **辅助维度缺失 = Important**：UI 权限规则/搜索模块/弹层结构/动态字段/导入导出/状态操作差异/异常边界；非 UI 触发条件/权限角色/幂等并发/性能约束
+   - **§7 系统功能清单 ↔ §8.4 详述块交叉核对**：§7 列出但 §8.4 无详述 = **悬空功能 = Critical**
+   - 维度不适用但已显式标注 `NA + 理由` 的模块 = 不视为缺失（但需抽查 NA 理由合理性）
+   - **detail_ledger 交叉核对（可选）**：若 `detail_ledger_path` 提供，对比澄清期确认的维度状态与 PRD §8.4 覆盖/NA 标注——澄清已确认内容但 PRD 缺失或标 NA = Critical；澄清标 NA 但 PRD 有详述 = 记录不阻断
+
 ### Phase 3: 汇总判定
 
 Aggregate findings → final verdict per the Judgment Criteria.
@@ -81,9 +92,9 @@ Aggregate findings → final verdict per the Judgment Criteria.
 |---------|-----------|--------|
 | **PASS** | Critical=0 且 Important=0 | 可进入冻结 / 下游 plan |
 | **PASS_WITH_WARNINGS** | Critical=0 且 Important>0 | 警告项交人工裁定，不阻断 |
-| **FAIL** | Critical>0 | 必须回 Phase 1.3 补充后重新评审 |
+| **FAIL** | Critical>0 | 必须回 Phase 1.3/Phase 3 补充后重新评审 |
 
-**FAIL 仅由 Critical 触发**（D1/D2 缺失）。Important（D3/D5）误报不触发 FAIL。Minor（D4）仅记录。
+**FAIL 仅由 Critical 触发**（D1/D2 缺失；D6 核心维度缺失、D6 悬空功能）。Important（D3/D5/D6 辅助维度）误报不触发 FAIL。Minor（D4/D6 可读性）仅记录。
 
 ## Output Format
 
@@ -122,6 +133,9 @@ Aggregate findings → final verdict per the Judgment Criteria.
 ### D5 范围闭环 — {PASS/WARN}
 [in/out scope 声明状态 + 悬空功能列表]
 
+### D6 §8.4 契约级细节 — {PASS/FAIL} ({m}/{n} modules contract-grade)
+[逐功能模块检查：功能形态 | 适用维度覆盖 | NA 标注 | 悬空功能 | 状态]
+
 ## Findings
 | # | Dim | Severity | PRD Source | Requirement | Description | Suggestion |
 |---|-----|----------|-----------|-------------|-------------|------------|
@@ -146,6 +160,8 @@ Aggregate findings → final verdict per the Judgment Criteria.
 - Distinguish "missing" from "present-but-unverifiable" (both Critical for D2, but different fixes)
 - Give a clear, unambiguous verdict
 - Treat vague AC ("表现良好"/"快速响应" without threshold) as a D2 Critical
+- Read the template §8.4 checklist BEFORE assessing D6 — the template is the single authority, not your expectations
+- Distinguish "维度不适用（已标注 NA）" from "维度缺失（未标注 NA 且未覆盖）" in D6
 
 **DON'T:**
 - Modify the PRD or any other artifact — only write the review report
@@ -154,3 +170,4 @@ Aggregate findings → final verdict per the Judgment Criteria.
 - Trigger FAIL on Important or Minor findings — FAIL is Critical-only
 - Mark stylistic/wording polish as findings — completeness, not prose quality
 - Omit the PRD source reference for any finding
+- Judge D6 against your own detail expectations — cite the template checklist dimension name for every D6 finding

package/agents/prd-writer.md

@@ -0,0 +1,68 @@
+---
+name: prd-writer
+description: PRD 撰写 agent——在 ce-brainstorm 主会话完成交互澄清（Phase 0-2.6 + 功能细节澄清）之后、QA-4 审查之前，按 PRD 模板 §8.4 契约级检查清单将已确认产出整理为契约级 PRD 草稿（requirement/vN/prd.md）。可写型，负责 PRD 文档。
+
+model: inherit
+color: green
+tools: ["Read", "Bash", "Grep", "Glob", "Write", "Edit"]
+skills:
+  - ce-brainstorm
+---
+
+You are an independent PRD Writer. You turn the confirmed brainstorm outputs (business-analysis.md, dialogue-log.md, detail_ledger, synthesis summary) into a contract-grade PRD document at `requirement/vN/prd.md`. You execute ONLY the PRD writing phase — interactive clarification (Phase 0-2.6) is ALREADY DONE by the main conversation.
+
+## Scope Boundary
+
+You write PRD documents only. You do NOT run interactive phases, do NOT ask the user questions, do NOT modify business-analysis.md / dialogue-log.md / detail_ledger. Any information gap is reported as `missing_info` in your output contract — never invented.
+
+## Artifact Ownership
+
+**You are the sole owner of `requirement/vN/prd.md`.** No other agent or the orchestration layer may directly edit it. Modification requests (review feedback) MUST be routed through you via `SendMessage` resume.
+
+**Your preloaded Skill (ce-brainstorm) contains the detailed methodology** — PRD template resolution, `references/brainstorm-sections.md` chapter mapping (incl. §8.4 功能模块提取规则), `references/prd-mapping.md` version format. Follow it for HOW. This prompt defines WHO you are and WHAT you must deliver.
+
+## Iron Law
+
+1. **先读模板 §8.4 检查清单再撰写**：定位 `template_path`（默认 `templates/prd.md`）§8.4（UI 11 维 / 非 UI 7 维），以解析后的模板为逐功能详述的强制基准，不在他处猜测规范。
+2. **逐功能模块契约级详述**：每个功能按「功能形态」（UI/非 UI）覆盖对应必含维度；维度不适用时标注 `NA + 一句理由`；**未标注 NA 且未覆盖 = PRD 不完整**。
+3. **无信息章节保留模板占位，不虚构**：data source 未覆盖的内容保留 `{占位}`，并列入 `missing_info`。
+4. **不写实现契约**：接口路径/表字段/类结构/算法实现属 change 级 spec/design，PRD 只写产品行为与规则。
+
+## Inputs
+
+| Parameter | Description |
+|-----------|-------------|
+| `prd_path` | 目标 PRD 路径（e.g., `requirement/v1/prd.md`） |
+| `template_path` | PRD 模板路径（默认 `templates/prd.md`） |
+| `business_analysis_path` | business-analysis.md 路径（§2/§3/§7/§8 数据源） |
+| `dialogue_log_path` | dialogue-log.md 路径（§1.2 修订记录引用） |
+| `detail_ledger_path` | detail_ledger 路径（功能细节澄清产出，§8.4 数据源） |
+| `synthesis_summary` | 综合确认产出（scope 判定与核心决策） |
+
+If `template_path` is missing or unreadable, report `FAIL` with reason `INPUT_ERROR`.
+
+## Structured Output Contract
+
+Return the following YAML to the orchestration layer:
+
+```yaml
+status: done | blocked              # done: PRD 草稿已写入并通过自检
+artifact_path: requirement/vN/prd.md
+missing_info: [...]                 # 保留占位的未澄清信息清单（供 QA-4 / D6 定位）
+summary: "..."                      # 2-3 sentence overview + 待主会话确认点
+```
+
+## Red Lines
+
+**DO:**
+- 先读模板 §8.4 检查清单，再逐功能模块按维度详述
+- 从 detail_ledger / business-analysis.md 提取已确认信息，保持信息完整（页面布局/搜索字段/表格列/交互规则/级联逻辑等关键细节不得丢失或过度概括）
+- 功能描述含糊到"一句话说不清"时，先拆分功能再详述
+- 结束回复用显式终止标记：`FINAL VERDICT: <DONE | BLOCKED | FAIL>`
+
+**DON'T:**
+- 不执行交互阶段，不向用户提问（澄清已由主会话完成）
+- 不虚构未确认信息——data source 缺失就保留占位 + 列入 missing_info
+- 不写接口/表/类/算法等实现契约（属 change 级 spec/design）
+- 不修改 business-analysis.md / dialogue-log.md / detail_ledger / ledger.md
+- 不删除模板占位——无信息章节保留 `{占位}`

package/docs/README_en.md

@@ -126,7 +126,7 @@ npm install -g team-flow
 
 ### Version
 
-- Current: `v0.45.0`
+- Current: `v0.47.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

@@ -2,6 +2,8 @@
 <!-- 每条一行，按 severity 降序，≤150 行硬上限 -->
 | date | phase | domain | type | severity | summary | file |
 |------|-------|--------|------|----------|---------|------|
+| 2026-08-21 | cross-phase | general | insight | medium | (no summary) | cross-phase/2026-08-21-no-summary.md |
+| 2026-08-19 | cross-phase | general | insight | medium | (no summary) | cross-phase/2026-08-19-no-summary.md |
 | 2026-08-18 | cross-phase | general | insight | medium | (no summary) | cross-phase/2026-08-18-no-summary.md |
 | 2026-08-17 | cross-phase | general | insight | medium | (no summary) | cross-phase/2026-08-17-no-summary.md |
 | 2026-08-07 | cross-phase | general | insight | medium | (no summary) | cross-phase/2026-08-07-no-summary.md |

package/docs/solutions/cross-phase/2026-08-19-no-summary.md

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

package/docs/solutions/cross-phase/2026-08-21-no-summary.md

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

package/docs/usage-guide.md

@@ -1,6 +1,6 @@
 # team-flow 使用说明（研发团队版）
 
-> 版本锚点：v0.44.0（25 skills + 16 agents）· 更新日期：2026-08-17
+> 版本锚点：v0.47.0（26 skills + 17 agents）· 更新日期：2026-08-21
 > 读者：使用 team-flow 做日常研发的工程师。不需要你懂插件内部实现，只需要照着路径走。
 > 配套文档：安装细节见 [INSTALL.md](../INSTALL.md)；状态机细节见 [state-machine.md](state-machine.md)；决策点细节见 [decision-points.md](decision-points.md)；平台差异见 [platform-matrix.md](platform-matrix.md)。
 

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). 25 skills, one install.",
-  "version": "0.45.0",
+  "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.47.0",
   "contextFileName": "GEMINI.md"
 }

package/hooks/session-start

@@ -1,11 +1,11 @@
 #!/usr/bin/env bash
-# v0.45.0: auto-sync CLI version with plugin version
+# v0.47.0: auto-sync CLI version with plugin version
 set -e
 
 # ═══════════════════════════════════════════════════════════════
 # Plugin version (update this when releasing new versions)
 # ═══════════════════════════════════════════════════════════════
-PLUGIN_VERSION="0.45.0"
+PLUGIN_VERSION="0.47.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.45.0.
+Current version: v0.47.0.
 
 ## Key Documents
 - README.md: Chinese homepage with full usage guide and FAQ

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@xulthekl/team-flow",
-  "version": "0.45.0",
-  "description": "Unified plugin (25 skills + 16 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.",
+  "version": "0.47.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",
   "bin": {

package/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "team-flow",
-  "version": "0.45.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). 25 skills + 16 agents, one install.",
+  "version": "0.47.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). 26 skills + 17 agents, one install.",
   "author": {
     "name": "LT"
   },

package/skills/architecture-design/SKILL.md

@@ -176,7 +176,7 @@ change 进入 closing 阶段时，由 release-archivist 调用 `tf arch-merge` C
 | 变更级（默认） | workflow-start（exploring→specifying） | 五项检查 | `changes/<name>/architecture/` 三件套 + sql/ | architecture-design 子代理 |
 | 产品级（product 模式） | workflow-orchestrator S3.5（architecture 阶段） | 8 步全系统结构级设计（无五项检查） | `docs/architecture/iterations/vN/architecture.md`（6 产物快照） | architecture-design product 模式子代理（唯一 owner） |
 
-**产品级模式执行**：按 `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：只写快照不写全局。
+**产品级模式执行**：按 `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 才进 S3（2026-08-19：ARCH 上移 S3 前，原"进 S4"）。时序遵守 P1：只写快照不写全局。
 
 ### 独立调用
 

package/skills/architecture-design/references/s3.5-architecture-template.md

@@ -2,7 +2,7 @@
 
 > 产品级架构设计（architecture 阶段）产出的权威文档模板。基于 4A + DDD 方法论，覆盖 6 类产物。
 > 位置：`docs/architecture/iterations/vN/architecture.md`（预测态快照，P1：不写全局当前态）。
-> 产出后须经产品级评审门（architecture-reviewer product 视角）PASS 才进 S4。
+> 产出后须经产品级评审门（architecture-reviewer product 视角）PASS 才进 S3（2026-08-19：ARCH 上移 S3 前，原"进 S4"）。
 
 ## 文档骨架