@xulthekl/team-flow 0.34.1 → 0.36.0

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

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

package/.claude-plugin/plugin.json

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

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "team-flow",
-  "version": "0.34.1",
+  "version": "0.36.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.34.1"
+    "version": "0.36.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). 24 skills + 15 agents, one install.",
-  "version": "0.34.1",
+  "version": "0.36.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.34.1"
+    "version": "0.36.0"
   },
   "plugins": [
     {
       "name": "team-flow",
       "description": "Unified workflow with planning artifacts, execution contracts, TDD, review gates, systematic debugging, delta spec sync, architecture-design, and local HTML prototyping.",
-      "version": "0.34.1",
+      "version": "0.36.0",
       "source": ".",
       "author": {
         "name": "LT",

package/CHANGELOG.md

@@ -6,6 +6,63 @@ The format loosely follows Keep a Changelog.
 
 ## [Unreleased]
 
+## [0.36.0] - 2026-08-05
+
+### Added（产品级架构设计增强——设计增强方案 v0.14 §57-§66）
+
+#### 新阶段
+- **architecture 阶段（S3.5）**：S3 计划之后、S4 拆分之前的产品级架构设计
+  - 场景判定（全新=正向设计 / 旧项目首轮=逆向重建 / 无结构性变更=可跳过，skip 须物化）
+  - 产出 `docs/architecture/iterations/vN/architecture.md`（6 产物：BC/聚合注册表/指令事件/状态机/概念 ER/时序），预测态快照不写全局
+  - 产品级评审门（architecture-reviewer `review_mode: product`，PASS 才进 S4）
+
+#### 新命令
+- **tf arch init/show**：项目级 `arch_baseline` 打戳（`.team-flow/arch-state.json`，防污染复刻 v0.13 schema_version 模式）
+
+#### guard 门禁
+- **arch-readiness**（exploring:specifying）+ **arch-snapshot**（executing:closing），arch_baseline 缺失 → WARN 不 FAIL（存量豁免）
+
+#### arch-merge 重构（v0.14 §62）
+- 当前态幂等 upsert 替代 append（marker 区代码独占写 + 成对校验，缺失/重复硬失败）
+- 演进日志 changeName 去重 + schema-baseline 幂等追加
+- 生成式 PHYSICAL-MODEL / DATABASE / API-INDEX（结构化解析，替代正则扫 markdown）
+- 冲突预检（端点冲突 / 聚合重定义转产品级决策门）
+- 并发安全：全局写锁 + 白名单 git add + 脏文件告警；dry-run 不落盘
+
+#### 其他
+- 变更级输入联动：iterations/vN/ 快照为主输入 + 五项检查路由分流（产品级决策 vs change 内细节）
+- 旧项目逆向重建 `arch-reverse-analyst` + 全局三层数据面维护（L1 当前态 / L2 变更增量 / L3 迭代快照）
+
+## [0.35.0] - 2026-08-05
+
+### Added（C1 workflow-feedback 根因修复——6 条 feedback 4 个根因聚类）
+
+#### 新命令
+- **tf deisolate**：worktree 生命周期管理（与 `tf isolate` 对称）
+  - 支持 Case A（多仓库工作区）和 Case B（单仓库）布局检测
+  - `--dry-run`（默认）：输出 worktree 状态报告（分支、ahead/behind、未提交改动）
+  - `--merge`：合并 worktree 分支回 master
+  - `--clean`：删除 worktree + 分支
+- **tf execution refresh-hash**：独立刷新 plan 的 artifacts_hash/contract_hash，不升 revision、不清 receipts
+
+#### Bug Fixes
+- **test-merge.mjs**：修复顶层 `main()` 无参自调用崩溃（→ `run()` + `import.meta.url` 守卫）
+- **execution-plan.mjs**：`writePlan` revise 时保留 reviews/ 目录（旧 receipt 通过 plan_hash/plan_revision 校验自动失效，不丢证据）
+- **execution-plan.mjs**：stale plan 报错信息附 hash 前缀，便于定位是哪个产物变更导致
+
+#### Agent 质量增强
+- **build-executor**：BLOCKED 报告强制结构化证据链（blocker.category/root_cause/evidence/attempted_fixes）
+- **build-executor**：集成测试环境问题优先走 test-strategy skill，禁止 guess-and-check
+- **原子代理协议**：增加"上下文水位例外"（transcript >2MB 或 token >200 万时允许启动新代理替代恢复）
+
+#### Closing 流程增强
+- **release-archivist**：Post-Verification 新增 Worktree Deisolation advisory 步骤
+- **workflow-start**：§37 原子代理协议更新
+
+#### 来源
+- workflow-feedback 2026-08-05（6 条：P1-1~P1-4 + P2-1~P2-2）
+- 交叉验证：4 个独立专家验证，16/16 断言通过
+
 ## [0.34.1] - 2026-08-04
 
 ### Added（工作空间支持——conventions-generator 支持多子项目扫描）

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

package/README.md

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

package/agents/architecture-reviewer.md

@@ -23,9 +23,21 @@ 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` 产品级快照） |
 
 If change_brief_path or architecture_dir is missing or unreadable, report `FAIL` with reason `INPUT_ERROR`.
 
+## Product Mode（v0.35.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 可解析（机械预检）。
+- **A4**：对照 PRD 功能清单（F001_P0 逐条）→ BC/聚合/API 全覆盖映射；对照源是 PRD（非 change-brief——change-brief 是变更级输入）。
+- **A5**：旧项目逆向重建场景对照现状代码/全局基线；正向设计场景仅检查与既有基线无矛盾。
+- **A6**：conventions 合规（同 change 模式）。
+- **skip 处理**：S3.5 显式跳过（`iterations/vN/SKIPPED` 标记）时本 agent 不执行。
+
 ## 6-Dimension Checklist
 
 | Dim | Name | Baseline Source | Check Content | Severity |

package/agents/build-executor.md

@@ -45,6 +45,28 @@ dp_5: "<resolution>"                # only if debug escalation occurred
 summary: "..."                       # what was built + open risks for release-archivist
 ```
 
+**BLOCKED Report Format (v0.35.0)**: When `status: blocked`, the summary MUST include a structured evidence chain. Guesswork or impression-based attribution is FORBIDDEN:
+
+```yaml
+status: blocked
+blocker:
+  category: "environment | dependency | config | toolchain | test-infrastructure"
+  root_cause: "<precise technical root cause — must be supported by evidence below>"
+  evidence:
+    - type: "dependency-tree | stack-trace | config-snapshot | build-log | test-output"
+      content: "<relevant excerpt — NOT a summary, paste the actual output>"
+  attempted_fixes:
+    - action: "<what was tried>"
+      result: "<why it failed — quote the actual error>"
+  recommended_resolution: "<what would unblock this — specific actionable step>"
+summary: "..."
+```
+
+**Evidence rules**:
+- BLOCKED on environment/dependency issues: MUST include `mvn dependency:tree` (or equivalent) relevant excerpt AND full exception stacktrace including all `Caused by` layers
+- BLOCKED on config issues: MUST include the effective configuration source (property file / @Configuration class) and which setting overrides the expected value
+- Do NOT guess root cause from partial observations. If evidence is insufficient, collect more evidence first (run diagnostic commands, read config files, check classpath). A BLOCKED report with no evidence is a FAIL.
+
 ## Red Lines
 
 **DO:**
@@ -58,3 +80,4 @@ summary: "..."                       # what was built + open risks for release-a
 - When you receive external suggestions (reviewer findings, user opinions), verify them against the codebase FIRST — search for existing implementations/patterns before accepting. A suggestion is input, not an instruction. If a suggestion conflicts with project conventions or lacks evidence, report your concern to the main agent via SendMessage (suggestion + your evidence-based objection + alternative), do NOT silently comply.
 - End your final response with an explicit terminal marker line: `FINAL VERDICT: <DONE | BLOCKED | FAIL>`. Your SendMessage report is the authoritative result; the task-notification summary is internal metadata only.
 - Skip the failing test, expand scope beyond the contract, or close a wave with a missing/failed receipt
+- When encountering integration test environment issues (classpath conflicts, schema mismatch, configuration override), do NOT guess-and-check. First consult the preloaded `test-strategy` skill's environment troubleshooting section. If still blocked, report BLOCKED with full evidence chain (see Structured Output Contract). Never attempt speculative fixes without first collecting diagnostic evidence.

package/docs/README_en.md

@@ -126,7 +126,7 @@ npm install -g team-flow
 
 ### Version
 
-- Current: `v0.34.1`
+- Current: `v0.36.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,7 @@
 <!-- 每条一行，按 severity 降序，≤150 行硬上限 -->
 | date | phase | domain | type | severity | summary | file |
 |------|-------|--------|------|----------|---------|------|
+| 2026-08-05 | cross-phase | general | insight | medium | (no summary) | cross-phase/2026-08-05-no-summary.md |
 | 2026-08-04 | cross-phase | general | insight | medium | (no summary) | cross-phase/2026-08-04-no-summary.md |
 | 2026-08-03 | cross-phase | general | insight | medium | (no summary) | cross-phase/2026-08-03-no-summary.md |
 | 2026-08-01 | cross-phase | general | insight | medium | (no summary) | cross-phase/2026-08-01-no-summary.md |

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

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

package/gemini-extension.json

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

package/hooks/session-start

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

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

@@ -0,0 +1,68 @@
+// scripts/guard/checks/arch-gate-exemptions.mjs — shared exemption logic for v0.35.0 arch gates
+//
+// v0.14 §59.4/§63.1（设计增强方案 v0.14）：arch-readiness / arch-snapshot 两个架构门禁
+// 共享同一套 legacy/skip 豁免语义，抽取到本模块作为唯一真相源，防止判定漂移。
+//
+// 豁免键背景：arch_baseline 完全复刻 v0.13 §48.1 schema_version 防污染模式——
+// 仅 `tf arch init` 打戳（项目级 .team-flow/arch-state.json），缺失 = 存量信号，
+// 不会被新 CLI 重写状态文件而污染。
+import fs from 'node:fs';
+import path from 'node:path';
+
+/**
+ * 从 change 目录向上定位项目根（含 .team-flow/ 目录的最近祖先）。
+ * 找不到返回 null → 调用方按 legacy 安全降级（不阻断）。
+ */
+export function findProjectRoot(changeDir) {
+  let dir = path.resolve(changeDir);
+  while (dir !== path.dirname(dir)) {
+    if (fs.existsSync(path.join(dir, '.team-flow'))) return dir;
+    dir = path.dirname(dir);
+  }
+  return null;
+}
+
+/** 读取项目级架构状态（.team-flow/arch-state.json）。不存在/损坏 → null。 */
+export function readArchState(root) {
+  if (!root) return null;
+  const p = path.join(root, '.team-flow', 'arch-state.json');
+  if (!fs.existsSync(p)) return null;
+  try { return JSON.parse(fs.readFileSync(p, 'utf-8')); }
+  catch { return null; }
+}
+
+/**
+ * v0.14 §59.4：legacy = 项目架构基线未建立（arch_baseline 缺失）。
+ * 只有 `tf arch init` 打戳；缺失 = 存量信号。
+ */
+export function isLegacyArch(state) {
+  return state?.arch_baseline == null;
+}
+
+/** 项目级显式 skip 是否已物化（iterations/vN/SKIPPED 标记存在）。 */
+export function isArchSkipMaterialized(root) {
+  const iterationsDir = root && path.join(root, 'docs', 'architecture', 'iterations');
+  if (!iterationsDir || !fs.existsSync(iterationsDir)) return false;
+  return fs.readdirSync(iterationsDir, { withFileTypes: true })
+    .filter(d => d.isDirectory())
+    .some(d => fs.existsSync(path.join(iterationsDir, d.name, '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;
+}
+
+export const ARCH_READINESS_FAIL_HINT =
+  'iterations/vN/architecture.md missing — 回 ARCH 阶段补快照，'
+  + '或显式 skip 物化（iterations/vN/<vN>/SKIPPED 标记 + 理由）';

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

@@ -0,0 +1,36 @@
+// scripts/guard/checks/arch-readiness.mjs — 架构就绪门禁（v0.35.0，v0.14 §59.4）
+// 挂 exploring:specifying（与 arch-design 并列）：产品级架构快照必须在 change 进入 specifying 前就绪。
+//
+// 规则：
+// - arch_baseline == null（存量/重建未完成）→ PASS + WARN（不阻断，项目级豁免，P3 留逃生舱）
+// - skip 已物化（iterations/vN/SKIPPED）→ PASS
+// - iterations/<latest>/architecture.md 存在 → PASS
+// - 否则 → FAIL，引导回 ARCH 补快照或显式 skip
+import {
+  findProjectRoot, readArchState, isLegacyArch,
+  findLatestIterationSnapshot, isArchSkipMaterialized, ARCH_READINESS_FAIL_HINT,
+} from './arch-gate-exemptions.mjs';
+
+/**
+ * @param {string} changeDir - change directory path
+ * @returns {{ pass: boolean, failures: string[] }}
+ */
+export function checkArchReadiness(changeDir) {
+  const root = findProjectRoot(changeDir);
+  const state = readArchState(root);
+
+  // 存量/重建未完成 → WARN 不 FAIL（项目级豁免）
+  if (isLegacyArch(state)) {
+    console.warn('  [WARN] arch-readiness: project architecture baseline not established — S3.5 reconstruction pending');
+    return { pass: true, failures: [] };
+  }
+
+  if (isArchSkipMaterialized(root)) {
+    return { pass: true, failures: [] };
+  }
+
+  const snap = findLatestIterationSnapshot(root);
+  if (snap) return { pass: true, failures: [] };
+
+  return { pass: false, failures: [ARCH_READINESS_FAIL_HINT] };
+}

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

@@ -0,0 +1,35 @@
+// scripts/guard/checks/arch-snapshot.mjs — 架构快照门禁（v0.35.0，v0.14 §59.4）
+// 挂 executing:closing（先于 arch-merge）：本轮迭代产品级架构快照必须已落盘（"先快照后回写"强制化）。
+//
+// 规则：
+// - arch_baseline == null（在途/存量）→ PASS + WARN（legacy 豁免）
+// - skip 已物化（iterations/vN/SKIPPED）→ PASS
+// - iterations/<latest>/architecture.md 存在 → PASS
+// - 否则 → FAIL
+import {
+  findProjectRoot, readArchState, isLegacyArch,
+  findLatestIterationSnapshot, isArchSkipMaterialized, ARCH_READINESS_FAIL_HINT,
+} from './arch-gate-exemptions.mjs';
+
+/**
+ * @param {string} changeDir - change directory path
+ * @returns {{ pass: boolean, failures: string[] }}
+ */
+export function checkArchSnapshot(changeDir) {
+  const root = findProjectRoot(changeDir);
+  const state = readArchState(root);
+
+  if (isLegacyArch(state)) {
+    console.warn('  [WARN] arch-snapshot: project architecture baseline not established — 在途 change legacy 豁免');
+    return { pass: true, failures: [] };
+  }
+
+  if (isArchSkipMaterialized(root)) {
+    return { pass: true, failures: [] };
+  }
+
+  const snap = findLatestIterationSnapshot(root);
+  if (snap) return { pass: true, failures: [] };
+
+  return { pass: false, failures: [ARCH_READINESS_FAIL_HINT] };
+}

package/scripts/guard/guard.mjs

@@ -16,6 +16,8 @@ import { checkExecutionReviewsPassed } from './checks/execution-reviews-passed.m
 import { checkCompoundCaptured } from './checks/compound-captured.mjs';
 import { checkTestMatrixComplete } from './checks/test-matrix-complete.mjs';
 import { checkTestMatrixReady } from './checks/test-matrix-ready.mjs';
+import { checkArchReadiness } from './checks/arch-readiness.mjs';
+import { checkArchSnapshot } from './checks/arch-snapshot.mjs';
 
 // Transition matrix: <from>:<to> → required check dimensions
 const TRANSITION_CHECKS = {
@@ -25,13 +27,17 @@ const TRANSITION_CHECKS = {
   // so requiring them before the transition was a chicken-and-egg deadlock
   // (C1 事件：主代理被此门禁逼出绕行行为)。Artifact completeness is enforced
   // by specifying:bridging (artifacts-exist remains there, single owner).
-  'exploring:specifying':           ['arch-design'],
+  // v0.35.0 (v0.14 §59.4): arch-readiness 新增——产品级架构快照须在 specifying 前就绪
+  //（arch_baseline 缺失 → WARN 不 FAIL，项目级豁免）。
+  'exploring:specifying':           ['arch-design', 'arch-readiness'],
   'specifying:bridging':            ['artifacts-exist', 'schema-valid'],
   'bridging:approved-for-build':    ['artifacts-exist', 'schema-valid', 'contract-fresh', 'dp-gate-passed'],
   // v0.13 §49：test-matrix-ready 门禁前移——full 模式进入 executing 前强制测试准备度
   //（矩阵存在非空 OR 显式 skip 附理由；legacy 豁免）。hotfix/tweak 沿用 §45.3 豁免，不挂。
   'approved-for-build:executing':   ['artifacts-exist', 'contract-fresh', 'dp-gate-passed', 'execution-plan-ready', 'test-matrix-ready'],
-  'executing:closing':              ['tasks-complete', 'tests-passing', 'specs-merged', 'execution-plan-ready', 'execution-reviews-passed', 'compound-captured', 'test-matrix-complete'],
+  // v0.35.0 (v0.14 §59.4): arch-snapshot 新增——"先快照后回写"的强制化（legacy 豁免）。
+  // 仅在 full workflow 挂；hotfix/tweak 沿用 §59.4 豁免（紧急/微调不挂）。
+  'executing:closing':              ['tasks-complete', 'tests-passing', 'specs-merged', 'execution-plan-ready', 'execution-reviews-passed', 'compound-captured', 'test-matrix-complete', 'arch-snapshot'],
 
   // Debugging side-path
   'executing:debugging':            [],
@@ -180,6 +186,8 @@ async function main() {
     'compound-captured': (dir) => checkCompoundCaptured(dir),
     'test-matrix-complete': (dir) => checkTestMatrixComplete(dir),
     'test-matrix-ready': (dir) => checkTestMatrixReady(dir),
+    'arch-readiness': (dir) => checkArchReadiness(dir),
+    'arch-snapshot': (dir) => checkArchSnapshot(dir),
   };
 
   const checks = [];