@xulthekl/team-flow 0.67.0 → 0.68.0

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

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

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "team-flow",
-  "version": "0.67.0",
+  "version": "0.68.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) + jarvis (team-flow decision agent, opt-in). 28 skills + 17 agents, one install.",
   "source": "./",
   "author": {

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "team-flow",
-  "version": "0.67.0",
+  "version": "0.68.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.67.0"
+    "version": "0.68.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) + jarvis (team-flow decision agent, opt-in). 28 skills + 17 agents, one install.",
-  "version": "0.67.0",
+  "version": "0.68.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.67.0"
+    "version": "0.68.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.67.0",
+      "version": "0.68.0",
       "source": ".",
       "author": {
         "name": "LT",

package/CHANGELOG.md

@@ -4,6 +4,39 @@ All notable changes to `team-flow` will be documented in this file.
 
 The format loosely follows Keep a Changelog.
 
+## [0.68.0] - 2026-09-30
+
+### Added（security-baseline 企业安全基线集成：四层全量落地；设计 = 工作区 `docs/plan/security-baseline-integration-design.md` v1.3 + P3 修正，P1.5 完整档三轮闭合 0 Critical）
+
+**L1 基线双载体（单一真相源）**
+- 新增 `skills/ce-brainstorm/references/security-baseline.md`（44 项企业安全设计控制点人类可读权威 + verdict→门禁映射）+ `security-baseline.json`（机器可读，`baseline_version` + 逐项 trigger/locus/severity）——测试断言 md↔json 44 行逐项对齐。**企业 xlsx 原件不入本仓**（脱敏，来源指针留 workspace 设计文档）。
+
+**Scope Deriver（范围推导，唯一实现）**
+- 新增 `scripts/lib/security-scope.mjs`：gitChangedFiles（base_sha 锚定）+ 路径启发式 + spec/arch 关键词 → 10 类触发类别 + 适用项；**排除 change 目录自身**（realpath 归一防 macOS /var 符号链接）；推导结果落盘 `<change-dir>/.security-scope.json`（含 `scope_hash`，预像 = 规范化触发集+适用集）。
+- 新增 CLI `tf security scope <change-dir> [--json]` + `tf security baseline`（`scripts/lib/cmd-security.mjs`，COMMANDS + HELP 双注册）。LLM/人从不手写 scope JSON——对账是脚本 vs 脚本（设计 §二.6）。
+
+**L2 守卫双维度（guard 33→35 维）**
+- 新增 `scripts/guard/checks/security-baseline.mjs`（重档 full/hotfix/planned）+ `security-baseline-light.mjs`（轻档 quick/lightweight；tweak 豁免）。判定序：存量分档（无 `schema_version` → WARN 软着陆）→ 现场推导落盘 → 无触发静默 PASS（留痕）→ skip 短路（`security_scope_hash` 不匹配即失效）→ 档位分流（重档查 `.security-verification.json` 完备性：适用集 ⊆ items、缺席=uncovered、must uncovered=FAIL / should=WARN、not-applicable reason ≥10 字符或含序号）→ infra 项交接检查（`security/handoff.md` transition 前置）。
+- guard.mjs 四表分挂（基础 TRANSITION / WORKFLOW hotfix / QUICK ×2 / PLANNED）；state 三环三键（BUILTIN_DEFAULTS + writeState + SETTABLE_FIELDS：`security_baseline_skipped/_skip_reason/security_scope_hash`）。
+- 反向验证通过：临时移除维度 → 单测 14 红 / 恢复 → 19 绿。
+
+**L3/L4/L5 判据送达（三通道 + 时序前置）**
+- L3 code-reviewer 三处同步（agents Output Contract / SKILL Step 2.5 / prompt 模板内联 `[SECURITY_SCOPE_JSON]` 占位）；派发侧 workflow-start SKILL + routing-rules 加 `tf security scope` 前置与 dispatch 传参。
+- L4 spec-writer design.md「适用触发类别确认」小节 + planned 主代理分支指引（planned 无 spec-writer）；security-sentinel **双副本**（ce-plan + ce-compound）同步增引基线。
+- L5 release-archivist 三分支 handoff 时序前置（legacy ①b / planned ④b / direct ⓪，各在 transition 之前）+ 跨 change 台账 `.team-flow/security-todos.md`；**planned verification 生产者 = 最终审查（P3 修正，planned 不派 code-reviewer）**；hotfix 重档归属 + tweak L5 豁免注记。
+- `doc-consistency.test.mjs` 新增 19 条安全基线注入锚点 + 三分支时序断言（规则送到执行者/派发者，机械守护）。
+
+### Changed
+- 维度计数横展 33→35 共 12 处（guard-dimensions 头部映射 / 使用说明矩阵与出路表 / test-matrix / e2e skill 描述等）；`docs/team-flow 使用说明` 新增 security-baseline 维度行 + 门禁出路行。
+- `code-reviewer` "6-step" 计数宣称去数字化（实际已 9 步）；`report_path` 交叉核验措辞改「写入者自约束」（当前无机械对账，不虚称）。
+
+### Fixed
+- 非 git 目录跑 `tf security scope` 的 stderr `fatal:` 泄漏（stdio 收窄，只给结构化 `error=no-baseline` 提示）。
+
+### Testing
+- 新增 `tests/lib/guard-security-baseline.test.mjs` 19 例（存量软着陆正反例 / 推导留痕 / skip 三态 / verdict 映射 / 完备性对账 / infra 交接 / 三环写入 / 双载体一致性 / 四档分流）；doc-consistency +15；e2e P7 planned 夹具按新流程补 scope+verification。
+- `npm test` 1383→**1419** + `test:e2e` **103** 全绿；`check-versions` PASS；`lint:skills` 本迭代引入 error 清零（余 7 存量）；`tf doctor` All checks passed；P4 双门禁 plugin-validator **PASS** / skill-reviewer **PASS_WITH_WARNINGS**（Major/Minor 全修，遗留见 Roadmap P2-72/73）。
+
 ## [0.67.0] - 2026-09-25
 
 ### Added（agent-governance 治理演进全量：P0–P2 七批次；设计 = 工作区 `teamflow-agent-governance-design-memo.md` v0.5 + 实施计划 v1.2，P1.5 标准档两轮 + 收官验证 0 Critical）

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

package/README.md

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

package/agents/code-reviewer.md

@@ -12,7 +12,7 @@ skills:
 
 You are an independent Code Reviewer. You review code changes for quality, spec compliance, architecture soundness, and implementation completeness. You write the review report to disk and return a summary.
 
-**Your preloaded Skill contains the detailed methodology** (6-step review process, calibration rules, severity definitions, critical rules). Follow it for HOW. This prompt defines WHO you are and WHAT you must deliver.
+**Your preloaded Skill contains the detailed methodology** (step-by-step review process, calibration rules, severity definitions, critical rules). Follow it for HOW. This prompt defines WHO you are and WHAT you must deliver.
 
 ## Iron Law
 
@@ -37,8 +37,15 @@ Produce a structured review report with the following sections:
 2. **Verdict**: PASS / PASS_WITH_WARNINGS / FAIL
 3. **Findings table**: severity, category, file, line, description, suggestion
 4. **Spec compliance matrix**: spec requirement → implementation status
-5. **Summary**: key strengths, critical issues, recommendations
-6. **Report File**: path to the written report file + confirmation
+5. **Security Baseline 核验**（security-baseline-integration-design v1.3）: 逐条 verdict
+   - 适用子集 = 派发时 dispatch prompt 显式传入的 `.security-scope.json` **code-locus 适用项**（**不要自行推导**；缺传参时先跑 `tf security scope <change-dir>` 取）。
+   - 每项 verdict ∈ `satisfied | not-applicable | uncovered`；`not-applicable` 必须带 reason（≥10 字符或含控制点序号，否则视同 uncovered）；must 项 uncovered = Critical。
+   - 核验完成**必须写盘** `<change-dir>/.security-verification.json`：
+     `{"items":[{"id":<序号>,"verdict":"...","reason":"..."}], "report_path":"<本报告路径>", "round":<n>}`
+   - `report_path` **写为 receipt `--report` 同一路径**（写入者自约束——当前无机械对账，勿声称已核验）；guard 只读该 JSON，不解析本报告 markdown。
+   - 仅末 wave 产一份；**planned 档不派本 agent**（其 JSON 由 release-archivist 最终审查产，见其 SKILL ④）。
+6. **Summary**: key strengths, critical issues, recommendations
+7. **Report File**: path to the written report file + confirmation
 
 Your preloaded Skill provides the full report template and formatting guidelines. Write the report to disk, then return summary + file path.
 
@@ -54,7 +61,7 @@ Your preloaded Skill defines severity levels (Critical / Important / Minor) and
 ## Red Lines
 
 **DO:**
-- Follow the preloaded Skill's 6-step review methodology
+- Follow the preloaded Skill's review methodology
 - Read specs and design BEFORE reading implementation — establish requirements baseline
 - Cite specific file:line for every finding
 - Distinguish spec violations (Critical) from style issues (Minor)

package/docs/README_en.md

@@ -126,7 +126,7 @@ npm install -g team-flow
 
 ### Version
 
-- Current: `v0.67.0`
+- Current: `v0.68.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/team-flow /344/275/277/347/224/250/350/257/264/346/230/216/357/274/210/347/240/224/345/217/221/345/233/242/351/230/237/347/211/210/357/274/211.md"

@@ -1,6 +1,6 @@
 # team-flow 使用说明（研发团队版）
 
-> 版本锚点：v0.67.0（28 skills + 17 agents）· 更新日期：2026-09-21
+> 版本锚点：v0.68.0（28 skills + 17 agents）· 更新日期：2026-09-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)。
 
@@ -173,7 +173,7 @@ workflow-start 在初始化时自动推断（`tf runtime infer`），你也可
 | 模式 | 判据（自动推断） | 特点 | 门禁差异（对比 full） |
 |------|----------------|------|--------|
 | **full** | 默认（不满足下面两个） | 全流程：需求探索→架构门→四件套→契约→执行计划→TDD→逐 wave 审查→完整收尾 | 基准：`executing→closing` 挂 10 维 |
-| **hotfix** | ≤2 任务、≤2 文件，且不动 schema/API、不新增模块 | 跳过需求探索和规划制品，最小契约仍需 DP-3 批准 | 入口换一套更轻的维度：`contract-current`+`dp3-approved` 取代 full 的 artifacts-exist / schema-valid / contract-fresh / dp-gate-passed；不查 `test-matrix-ready`。出口 6 维——省 `test-matrix-complete`、`arch-snapshot`、`delegation-status`、`arch-merged`，**但执行计划与逐 wave 审查回执仍要** |
+| **hotfix** | ≤2 任务、≤2 文件，且不动 schema/API、不新增模块 | 跳过需求探索和规划制品，最小契约仍需 DP-3 批准 | 入口换一套更轻的维度：`contract-current`+`dp3-approved` 取代 full 的 artifacts-exist / schema-valid / contract-fresh / dp-gate-passed；不查 `test-matrix-ready`。出口 7 维——省 `test-matrix-complete`、`arch-snapshot`、`delegation-status`、`arch-merged`，**但执行计划、逐 wave 审查回执与 `security-baseline`（v1.3 重档）仍要** |
 | **tweak** | ≤4 任务，且文件全是配置/文档类（无代码文件）、不动 schema/API、不新增模块 | 直接进 approved-for-build，直接编辑 | 入口不查 `execution-plan-ready` / `test-matrix-ready`，但仍查 `artifacts-exist`+`contract-fresh`+`dp-gate-passed`。出口仅 3 维（`tasks-complete`、`tests-passing`、`specs-merged`），省掉其余 7 项 |
 
 **注意三件事**：
@@ -232,7 +232,7 @@ workflow-start 在初始化时自动推断（`tf runtime infer`），你也可
 tf runtime guard check <change-dir> <from-state> <to-state> [--workflow full|hotfix|tweak]
 ```
 
-**full 模式的完整转换矩阵**（**33 个维度** + 1 个 workflow 限制维度；v0.64.0 增 quick/lightweight/planned 轻路径 11 维；agent-governance P1-1 增 **prd-clarity / history-risk** 接活前双维度——**无记录/INDEX 空的冷启动场景**零行为变化；INDEX 积累丰富的项目 history-risk 命中即阻断，属该维 experimental 设计而非回归）：
+**full 模式的完整转换矩阵**（**35 个维度** + 1 个 workflow 限制维度；v0.64.0 增 quick/lightweight/planned 轻路径 11 维；agent-governance P1-1 增 **prd-clarity / history-risk** 接活前双维度——**无记录/INDEX 空的冷启动场景**零行为变化；INDEX 积累丰富的项目 history-risk 命中即阻断，属该维 experimental 设计而非回归）：
 
 | 转换 | 维度 |
 |------|------|
@@ -240,7 +240,7 @@ tf runtime guard check <change-dir> <from-state> <to-state> [--workflow full|hot
 | specifying→bridging | artifacts-exist、schema-valid |
 | bridging→approved-for-build | artifacts-exist、schema-valid、contract-fresh、dp-gate-passed、dp3-approved、**gates-probed**（v0.63.0）、**prd-clarity**、**history-risk**（P1-1） |
 | approved-for-build→executing | artifacts-exist、contract-fresh、dp-gate-passed、execution-plan-ready、test-matrix-ready、**prd-clarity**、**history-risk**（P1-1） |
-| **executing→closing** | **11 维**：**contract-fresh（v0.63.0）**、tasks-complete、tests-passing、specs-merged、execution-plan-ready、execution-reviews-passed、compound-captured、test-matrix-complete、arch-snapshot、delegation-status、arch-merged |
+| **executing→closing** | **12 维**：**contract-fresh（v0.63.0）**、tasks-complete、tests-passing、specs-merged、execution-plan-ready、execution-reviews-passed、compound-captured、test-matrix-complete、arch-snapshot、delegation-status、arch-merged、**security-baseline（v1.3）** |
 | executing↔debugging | debugging 入口无门禁；回 executing 挂 contract-fresh、execution-plan-ready |
 | exploring→bridging / exploring→approved-for-build | 0 维，但**一一对应**：`exploring→bridging` 仅 hotfix 可走、`exploring→approved-for-build` 仅 tweak 可走；full 走或其他组合都直接 FAIL |
 | 7 条回退 + 6 条放弃 | 0 维（回退是合法操作，不需要门禁放行） |
@@ -261,7 +261,9 @@ tf runtime guard check <change-dir> <from-state> <to-state> [--workflow full|hot
 | compound-captured | executing→closing | 缺 `learnings.md`（change 根目录，非空）→ 写它，或 `tf state set <dir> compound_skipped true` |
 | arch-snapshot | executing→closing | 产品级架构快照缺失 → 补快照或物化 SKIPPED 标记 |
 | arch-merged | executing→closing | 架构增量未回写全局台账 → **先跑 `tf arch-merge <change-dir>` 再转换**（v0.53.0 B' 时序）；确无增量可回写时 `tf state set <dir> arch_merge_skipped true` + `arch_merge_skip_reason` |
+| security-baseline（v1.3） | executing→closing | 缺 `.security-verification.json` → 派发 code-reviewer（末 wave / planned 最终审查）产核验 JSON（dispatch 传 `[SECURITY_SCOPE_JSON]`）；命中 infra 项缺 handoff → transition 前写 `security/handoff.md`；整体确不适用 → `tf state set <dir> security_baseline_skipped true` + `security_baseline_skip_reason` + `security_scope_hash`（取 `tf security scope` 输出） |
 | delegation-status | executing→closing | 非 glaf4-delegation 模式直接 PASS；该模式须 `delegation_status=success` |
+| security-baseline / security-baseline-light（v1.3） | executing→closing（重档 full/hotfix/planned；轻档 quick/lightweight；tweak 豁免） | 现场推导 `.security-scope.json`：无适用触发类别=静默 PASS（留痕）；重档须 `.security-verification.json` 逐条 verdict（must uncovered=FAIL、缺席=uncovered）；命中 infra 项须 transition 前写 `security/handoff.md`；skip 出路 `security_baseline_skipped`+`security_baseline_skip_reason`+`security_scope_hash`（三键，hash 变即失效）；存量（无 `schema_version`）WARN 软着陆 |
 | artifacts-exist / schema-valid | specifying→bridging 起 | 四件套缺失或 Validator 不通过（SHALL/MUST、Scenario、跨段冲突） |
 | prd-clarity | 接活前（bridging→approved / approved→executing，quick/lightweight/planned 前门） | 产品级 PRD 清晰度记录为 fail → 回 S2 重跑 `tf prd check-clarity` 修至 PASS 后重建 change；无记录 = 中性放行（存量/direct/hotfix） |
 | history-risk | 同上（experimental） | solutions INDEX 中**按 change 名词根匹配**的条目 N≥3 且最高 severity=critical → 阻断。**出路（改数据源头，无 state 确认通道）**：① 坑已根治 → 按 compound 退役/降档处理相关条目后重建 INDEX；② 误关联 → 调整 change 名避开词根。N<3 / INDEX 空 / 无匹配 = 中性 |
@@ -754,4 +756,4 @@ tf runtime guard check <change-dir> <from> <to> --json
 
 ---
 
-*本文档基于 v0.60.0 源码全量核对产出（2026-09-13 同步），v0.67.0 增量同步 agent-governance 改动（33 维矩阵 / prd-clarity·history-risk 出路 / 复利注入与见习门控，2026-09-25）。发现与实际行为不符，请 `/team-flow:workflow-feedback` 反馈——这正是本插件的演进方式。*
+*本文档基于 v0.60.0 源码全量核对产出（2026-09-13 同步），v0.67.0 增量同步 agent-governance 改动（35 维矩阵——v1.3 增 security-baseline 双维度，2026-09-30；prd-clarity·history-risk 出路 / 复利注入与见习门控，2026-09-25）。发现与实际行为不符，请 `/team-flow:workflow-feedback` 反馈——这正是本插件的演进方式。*

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) + jarvis (team-flow decision agent, opt-in). 28 skills, one install.",
-  "version": "0.67.0",
+  "version": "0.68.0",
   "contextFileName": "GEMINI.md"
 }

package/hooks/session-start

@@ -1,11 +1,11 @@
 #!/usr/bin/env bash
-# v0.67.0: auto-sync CLI version with plugin version
+# v0.68.0: auto-sync CLI version with plugin version
 set -e
 
 # ═══════════════════════════════════════════════════════════════
 # Plugin version (update this when releasing new versions)
 # ═══════════════════════════════════════════════════════════════
-PLUGIN_VERSION="0.67.0"
+PLUGIN_VERSION="0.68.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.67.0.
+Current version: v0.68.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.67.0",
+  "version": "0.68.0",
   "description": "Unified plugin (28 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.67.0",
+  "version": "0.68.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) + jarvis (team-flow decision agent, opt-in). 28 skills + 17 agents, one install.",
   "author": {
     "name": "LT"

package/scripts/guard/checks/security-baseline-light.mjs

@@ -0,0 +1,9 @@
+// scripts/guard/checks/security-baseline-light.mjs — 安全基线闸门（轻档：quick/lightweight）
+// 设计：docs/plan/security-baseline-integration-design.md v1.3 §L2
+// 与重档共享全部判定（存量分档 / 推导落盘 / skip 短路 / infra 交接），
+// **省略逐条 verdict 核验**（direct 档无审查 receipt，verification 无生产者——诚实降级 §八.5）。
+import { evaluateSecurityBaseline } from './security-baseline.mjs';
+
+export function checkSecurityBaselineLight(changeDir) {
+  return evaluateSecurityBaseline(changeDir, 'light');
+}

package/scripts/guard/checks/security-baseline.mjs

@@ -0,0 +1,141 @@
+// scripts/guard/checks/security-baseline.mjs — 安全基线闸门（重档：full/hotfix/planned）
+// 设计：docs/plan/security-baseline-integration-design.md v1.3 §L2
+// 输入只读结构化制品，不解析 markdown 审查报告：
+//   ① .security-scope.json（现场推导落盘，security-scope.mjs 唯一实现）
+//   ② .security-verification.json（L3 code-reviewer 产出）
+//   ③ state 键（security_baseline_skipped / _skip_reason / security_scope_hash + schema_version）
+// 判定序（v1.3 重排）：存量分档 → 现场推导 → 无类别 PASS → skip 短路 →
+// 重/轻档分流（完备性对账 + verdict 映射）→ infra 交接检查。
+import { existsSync, readFileSync } from 'node:fs';
+import { join } from 'node:path';
+import { readState } from '../../lib/state-loader.mjs';
+import { deriveSecurityScope, loadSecurityBaseline, readScopeFile } from '../../lib/security-scope.mjs';
+
+const VERIFICATION_FILE = '.security-verification.json';
+const HANDOFF_REL = join('security', 'handoff.md');
+
+function readVerification(changeDir) {
+  const p = join(changeDir, VERIFICATION_FILE);
+  if (!existsSync(p)) return null;
+  try { return JSON.parse(readFileSync(p, 'utf-8')); } catch { return 'malformed'; }
+}
+
+// verdict → 门禁映射（设计 §L3，写死）：
+//   must+satisfied / should+satisfied → PASS
+//   not-applicable → 须过 reason 判据（≥10 字符或含控制点序号），否则视同 uncovered
+//   uncovered / 缺席 → must=FAIL，should=WARN（不阻断）
+function evaluateVerdicts(baseline, scope, verification) {
+  const failures = [];
+  const warnings = [];
+  const byId = new Map((verification.items || []).map(i => [Number(i.id), i]));
+  const reasonOk = (v, id) => {
+    const r = (v.reason || '').trim();
+    return r.length >= 10 || r.includes(String(id));
+  };
+
+  for (const id of scope.code_item_ids) {
+    const item = baseline.items.find(b => b.id === id);
+    const v = byId.get(id);
+    const must = item?.severity === 'must';
+    if (!v) {
+      // 完备性对账：适用项缺席 = uncovered（防空/残缺 items 空过，设计 §L3）
+      (must ? failures : warnings).push(`#${id} ${item?.title ?? ''} 缺席于 verification（=uncovered）`);
+      continue;
+    }
+    if (v.verdict === 'satisfied') continue;
+    if (v.verdict === 'not-applicable') {
+      if (!reasonOk(v, id)) {
+        failures.push(`#${id} not-applicable 的 reason 不合格（需 ≥10 字符或含序号）`);
+      }
+      continue;
+    }
+    // uncovered 或未知 verdict（未知按 uncovered，fail-closed）
+    if (must) failures.push(`#${id} ${item?.title ?? ''} uncovered（must）`);
+    else warnings.push(`#${id} ${item?.title ?? ''} uncovered（should，WARN 不阻断）`);
+  }
+  return { failures, warnings };
+}
+
+/**
+ * 核心求值。mode = 'full'（查 verification）| 'light'（跳过逐条核验）
+ */
+export function evaluateSecurityBaseline(changeDir, mode) {
+  const state = readState(changeDir);
+
+  // 步 1：存量分档（单一判据 = 无 schema_version → WARN 软着陆，设计 §二.3）
+  if (state.schema_version == null) {
+    return { pass: true, failures: [], reason: 'legacy soft-land: no schema_version (存量 change，安全基线不阻断)' };
+  }
+
+  // 步 2：现场推导（写盘留痕；推导失败 fail-closed）
+  let scope;
+  try {
+    scope = deriveSecurityScope(changeDir, { source: 'guard' });
+  } catch (e) {
+    return { pass: false, failures: [`security scope derive crashed: ${e.message}`] };
+  }
+  if (scope.error) {
+    return {
+      pass: false,
+      failures: [`scope derive degraded (error=${scope.error}) — 无法推导适用范围，fail-closed；检查 git 基线（tf state init 打戳 base_sha）后重试 tf security scope`],
+    };
+  }
+
+  // 步 3：无适用触发类别 → PASS（已落盘留痕，可区分"无触发"与"门禁未生效"）
+  if (scope.triggered_categories.length === 0) {
+    return { pass: true, failures: [], reason: `no applicable trigger categories (${scope.files_scanned} surface files scanned); scope written for audit` };
+  }
+
+  // 步 4：skip 短路（最先于实质检查；hash 不匹配 = 范围已变 → skip 失效继续）
+  const skipped = state.security_baseline_skipped === true || state.security_baseline_skipped === 'true';
+  if (skipped) {
+    const reason = (state.security_baseline_skip_reason || '').trim();
+    if (!reason || reason === 'null') {
+      return { pass: false, failures: ['security_baseline_skipped=true but no skip reason — set security_baseline_skip_reason via tf state set'] };
+    }
+    if (state.security_scope_hash && state.security_scope_hash === scope.scope_hash) {
+      return { pass: true, failures: [], reason: `skipped: ${reason}` };
+    }
+    // hash 缺失/不匹配 → skip 失效（fail-closed 方向），继续实质检查
+  }
+
+  // 步 5：档位分流
+  if (mode === 'full') {
+    const ver = readVerification(changeDir);
+    if (!ver) {
+      return {
+        pass: false,
+        failures: [`.security-verification.json missing — 派发 code-reviewer（末 wave / planned 最终审查）产核验 JSON；无适用 code 项时亦须落盘（空 items + 全 N/A 说明）`],
+      };
+    }
+    if (ver === 'malformed') {
+      return { pass: false, failures: ['.security-verification.json malformed (JSON parse failed)'] };
+    }
+    const baseline = loadSecurityBaseline();
+    const { failures, warnings } = evaluateVerdicts(baseline, scope, ver);
+    if (failures.length) {
+      return { pass: false, failures, ...(warnings.length ? { warnings } : {}) };
+    }
+    if (warnings.length) {
+      return { pass: true, failures: [], reason: `pass with WARN: ${warnings.join('; ')}` };
+    }
+  }
+  // light 档（quick/lightweight）：不查 verification（direct 档无审查 receipt，设计 §八.5）
+
+  // 步 6：infra/config/process 交接检查（检查对象 = handoff.md，台账不进 guard）
+  if (scope.infra_item_ids.length > 0) {
+    const handoffPath = join(changeDir, HANDOFF_REL);
+    if (!existsSync(handoffPath) || !readFileSync(handoffPath, 'utf-8').trim()) {
+      return {
+        pass: false,
+        failures: [`infra-scope items ${scope.infra_item_ids.join('/')} apply but security/handoff.md missing or empty — write the handoff BEFORE tf state transition closing (设计 §L5 时序)`],
+      };
+    }
+  }
+
+  return { pass: true, failures: [] };
+}
+
+export function checkSecurityBaseline(changeDir) {
+  return evaluateSecurityBaseline(changeDir, 'full');
+}

package/scripts/guard/guard.mjs

@@ -36,6 +36,9 @@ import { checkCompoundWritebackLight } from './checks/compound-writeback-light.m
 import { checkTestMergedLight } from './checks/test-merged-light.mjs';
 import { checkCrossChangeConsistencyLight } from './checks/cross-change-consistency-light.mjs';
 import { checkExecutionReviewsPassedLight } from './checks/execution-reviews-passed-light.mjs';
+// security-baseline-integration-design v1.3：安全基线双维度（executing→closing）
+import { checkSecurityBaseline } from './checks/security-baseline.mjs';
+import { checkSecurityBaselineLight } from './checks/security-baseline-light.mjs';
 
 // Transition matrix: <from>:<to> → required check dimensions
 const TRANSITION_CHECKS = {
@@ -82,7 +85,12 @@ const TRANSITION_CHECKS = {
   // artifacts_hash）→ **伪绿静默通过**。本维度直接比对 state.artifacts_hash 与制品实算值，
   // refresh-hash 无法清屏（它只改 plan JSON，不碰 state）——故为 refresh-hash 之外的独立锚。
   // hotfix/tweak 不挂：二者跳过 spec-writer、无 planning 四件，冻结机制本身 N/A（设计 §3.9）。
-  'executing:closing':              ['contract-fresh', 'tasks-complete', 'tests-passing', 'specs-merged', 'execution-plan-ready', 'execution-reviews-passed', 'compound-captured', 'test-matrix-complete', 'arch-snapshot', 'delegation-status', 'arch-merged'],
+  // v1.3（security-baseline-integration-design）：security-baseline 新增——
+  // 44 项企业安全基线的机械闸门（现场推导 scope + verification 完备性 + infra 交接）。
+  // full（legacy variant）走本基表；hotfix 走 WORKFLOW 表、planned 走 PLANNED 表、
+  // quick/lightweight 走 QUICK 表挂 -light 变体、tweak 天然不挂（豁免）。
+  // 存量 change（无 schema_version）WARN 软着陆，冷启动零行为变化。
+  'executing:closing':              ['contract-fresh', 'tasks-complete', 'tests-passing', 'specs-merged', 'execution-plan-ready', 'execution-reviews-passed', 'compound-captured', 'test-matrix-complete', 'arch-snapshot', 'delegation-status', 'arch-merged', 'security-baseline'],
 
   // Debugging side-path
   'executing:debugging':            [],
@@ -116,7 +124,9 @@ const WORKFLOW_TRANSITION_CHECKS = {
     'bridging:approved-for-build': ['contract-current', 'dp3-approved'],
     'approved-for-build:executing': ['contract-current', 'dp3-approved', 'execution-plan-ready'],
     // hotfix exemption: no test-matrix-complete (v0.12 §45.3)
-    'executing:closing': ['tasks-complete', 'tests-passing', 'specs-merged', 'execution-plan-ready', 'execution-reviews-passed', 'compound-captured'],
+    // v1.3：security-baseline 重档——hotfix 走逐 wave 审查（execution-reviews-passed 已挂），
+    // code-reviewer 派发即 verification 生产者，重档不死锁（P1.5 R3-C1 裁定回滚）。
+    'executing:closing': ['tasks-complete', 'tests-passing', 'specs-merged', 'execution-plan-ready', 'execution-reviews-passed', 'compound-captured', 'security-baseline'],
   },
   tweak: {
     'exploring:approved-for-build': [],
@@ -141,14 +151,15 @@ const QUICK_TRANSITION_CHECKS = {
   quick: {
     'exploring:approved-for-build': ['direct-short-path', 'prd-clarity', 'history-risk'],
     'approved-for-build:executing': ['direct-short-path', 'test-matrix-ready', 'prd-clarity', 'history-risk'],
-    'executing:closing': ['direct-short-path', 'direct-test-result', 'test-matrix-complete'],
+    // v1.3：security-baseline-light——direct 档无审查 receipt，省逐条 verdict（设计 §八.5）
+    'executing:closing': ['direct-short-path', 'direct-test-result', 'test-matrix-complete', 'security-baseline-light'],
     'executing:debugging': [],
     'debugging:executing': ['direct-test-result'],
   },
   lightweight: {
     'exploring:approved-for-build': ['direct-short-path', 'prd-clarity', 'history-risk'],
     'approved-for-build:executing': ['direct-short-path', 'test-matrix-ready', 'prd-clarity', 'history-risk'],
-    'executing:closing': ['direct-short-path', 'direct-test-result', 'lightweight-completion-evidence', 'test-matrix-complete'],
+    'executing:closing': ['direct-short-path', 'direct-test-result', 'lightweight-completion-evidence', 'test-matrix-complete', 'security-baseline-light'],
     'executing:debugging': [],
     'debugging:executing': ['direct-test-result'],
   },
@@ -166,6 +177,8 @@ const PLANNED_TRANSITION_CHECKS = {
     'execution-plan-ready', 'execution-reviews-passed-light', 'test-matrix-complete',
     'tests-passing', 'arch-merged-light', 'compound-writeback-light', 'test-merged-light',
     'cross-change-consistency-light', 'delegation-status', 'specs-merged', 'tasks-complete',
+    // v1.3：security-baseline 重档（planned 有最终审查，verification 有生产者）
+    'security-baseline',
   ],
   'executing:debugging': [],
   'debugging:executing': ['execution-plan-ready', 'tests-passing'],
@@ -298,7 +311,7 @@ async function main() {
     'test-matrix-complete': (dir) => checkTestMatrixComplete(dir, CTX),
     'test-matrix-ready': (dir) => checkTestMatrixReady(dir, CTX),
     'gates-probed': (dir) => checkGatesProbed(dir),
-    // agent-governance P1-1（33 维）：接活前双维度。缺失态中性——冷启动零行为变化。
+    // agent-governance P1-1：接活前双维度。缺失态中性——冷启动零行为变化。
     'prd-clarity': (dir) => checkPrdClarityState(dir),
     'history-risk': (dir) => checkHistoryRisk(dir),
     'arch-readiness': (dir) => checkArchReadiness(dir),
@@ -317,6 +330,10 @@ async function main() {
     'test-merged-light': (dir) => checkTestMergedLight(dir),
     'cross-change-consistency-light': (dir) => checkCrossChangeConsistencyLight(dir),
     'execution-reviews-passed-light': (dir) => checkExecutionReviewsPassedLight(dir),
+    // security-baseline-integration-design v1.3（35 维）：安全基线双维度。
+    // 重档（full/hotfix/planned）查 verification 完备性；轻档（quick/lightweight）省逐条核验。
+    'security-baseline': (dir) => checkSecurityBaseline(dir),
+    'security-baseline-light': (dir) => checkSecurityBaselineLight(dir),
   };
 
   const checks = [];

package/scripts/lib/cmd-security.mjs

@@ -0,0 +1,61 @@
+// scripts/lib/cmd-security.mjs — tf security 子命令
+// v1.3（security-baseline-integration-design）：`tf security scope <change-dir> [--json]`
+// 运行共享推导模块（scripts/lib/security-scope.mjs 唯一实现），落盘 .security-scope.json
+// 并打印 scope_hash。调用点：① L3 派发前（主会话取适用子集随 dispatch prompt 传参）
+// ② 人工刷新（guard 对账 FAIL 后重跑）。LLM/人从不手写 scope JSON（设计 §二.6）。
+import { parseArgs } from 'node:util';
+import { deriveSecurityScope, loadSecurityBaseline, SCOPE_FILE } from './security-scope.mjs';
+
+export async function run(args) {
+  const { positionals, values } = parseArgs({
+    args,
+    options: { json: { type: 'boolean', default: false } },
+    allowPositionals: true,
+  });
+
+  const sub = positionals[0];
+
+  if (sub === 'baseline') {
+    // tf security baseline [--json] — 查看基线双载体（人类可读路径 + 版本锚）
+    const data = loadSecurityBaseline();
+    if (values.json) {
+      console.log(JSON.stringify({
+        baseline_version: data.baseline_version,
+        items: data.items.length,
+        path: new URL('../../skills/ce-brainstorm/references/security-baseline.json', import.meta.url).pathname,
+      }, null, 2));
+    } else {
+      console.log(`security-baseline ${data.baseline_version} — ${data.items.length} items (md+json 双载体，见 skills/ce-brainstorm/references/security-baseline.md)`);
+    }
+    return 0;
+  }
+
+  if (sub !== 'scope') {
+    console.error('Usage: tf security <scope|baseline> <args>\n' +
+      '  scope <change-dir> [--json]   推导适用触发类别并落盘 .security-scope.json\n' +
+      '  baseline [--json]             查看 44 项基线版本锚');
+    return 2;
+  }
+
+  const changeDir = positionals[1];
+  if (!changeDir) {
+    console.error('Usage: tf security scope <change-dir> [--json]');
+    return 2;
+  }
+
+  const result = deriveSecurityScope(changeDir, { source: 'cli' });
+
+  if (values.json) {
+    console.log(JSON.stringify(result, null, 2));
+  } else {
+    if (result.error) {
+      console.error(`scope derive degraded (error=${result.error}) — 基线/diff 不可用，gate 侧将 fail-closed`);
+    }
+    console.log(`Scope written: ${SCOPE_FILE}`);
+    console.log(`  triggered: ${result.triggered_categories.length ? result.triggered_categories.join(', ') : '(none — 静默 PASS 类别)'}`);
+    console.log(`  applicable items: ${result.applicable_items.length} (code: ${result.code_item_ids.length}, infra-only: ${result.infra_item_ids.length})`);
+    console.log(`  scope_hash: ${result.scope_hash}`);
+  }
+  // 推导失败（无基线/diff 失败）按 fail-closed 返回非零，供调用方判断
+  return result.error ? 1 : 0;
+}

package/scripts/lib/cmd-state.mjs

@@ -78,6 +78,11 @@ const SETTABLE_FIELDS = [
   'gates_probed_skipped', 'gates_probed_skip_reason', 'gates_probed_na',
   // v0.64.0（§4 arch-design-light）：轻架构说明显式跳过键（须附理由）
   'arch_design_light_skipped', 'arch_design_light_skip_reason',
+  // security-baseline-integration-design v1.3（§L2 三环第 3 环）：安全基线跳过三键。
+  // 三键必须与 state-loader BUILTIN_DEFAULTS + writeState 序列化分支同步注册，
+  // 缺任一环即「回显成功却零写入」。skip 写入规范：设置 skipped 必须同批带
+  // security_scope_hash（值取最近 tf security scope 输出），hash 缺失时 guard 判 skip 失效。
+  'security_baseline_skipped', 'security_baseline_skip_reason', 'security_scope_hash',
 ];
 
 export async function run(args) {