add-coder 0.2.0 → 0.2.2

package/README.en.md

@@ -1,6 +1,6 @@
 # add-coder
 
-> 🌐 [🀄中文](./README.md) | English
+> 🌐 [🀄中文](https://github.com/xiaomingming92/add-coder/blob/main/README.md) | 🔤[English] — ⚠️ This file is temporarily unmaintained. The English translation is now embedded in README.md (scroll to ## 🔤 English README). Will resume standalone maintenance when the community grows.
 
 **AI Governance, Implemented** — The complete scaffolding from [codein2027](https://github.com/xiaomingming92/codein2027) for rapidly building the ADD programming paradigm. Built on the core principle of **Audit as Infrastructure**, it shatters the black-box programming process and cross-session amnesia, evolving the programming paradigm into an auditable, traceable, and convergent new era. [NPM](https://www.npmjs.com/package/add-coder) · [GitHub](https://github.com/xiaomingming92/add-coder)
 
@@ -181,12 +181,13 @@ npx add-coder init
        │  Handoff / DevLog Timeline Docs      │
        └─────────────────────────────────────┘
                            │
-              ┌────────────┼────────────┐
-              ▼            ▼            ▼
-       ┌──────────┐ ┌──────────┐ ┌──────────┐
-       │ Claude   │ │  Qoder   │ │  VS Code │
-       │ Hooks    │ │  Hooks   │ │  Config  │
-       └──────────┘ └──────────┘ └──────────┘
+    ┌──────────┬───────────┼───────────┬──────────┐
+    ▼          ▼           ▼           ▼          ▼
+┌──────┐ ┌──────┐ ┌──────────┐ ┌──────┐ ┌──────┐
+│Claude│ │Qoder │ │ VS Code  │ │ Trae │ │Codex │
+│Hooks │ │Hooks │ │  Config  │ │Hooks │ │Hooks │
+│14/17 │ │10/17 │ │  10/17   │ │ 6/17 │ │ 6/17 │
+└──────┘ └──────┘ └──────────┘ └──────┘ └──────┘
                            │
               ┌────────────┘
               ▼
@@ -226,3 +227,90 @@ npx add-coder init
 |------|-------------|
 | Demo Repo | A full example repository showcasing end-to-end closed-loop practice of Policy-Update-Loop and the Report system |
 | MCP Restructure | MCP toolchain architecture upgrade, improving audit and gateway tool extensibility and standalone deployment capability |
+| Memory Enhancement | Long-term project knowledge memory and plan-level sparse memory |
+
+---
+<details id="chinese-readme">
+<summary>🀄 中文 README</summary>
+
+**AI 代码治理的落地方案** — [codein2027](https://github.com/xiaomingming92/codein2027) 快速构建 ADD 编程范式的完整脚手架。以「审计即基础设施」为核心，彻底打破编程过程黑盒与跨轮失忆，让编程范式进化为可审计、可追溯、可收敛的新时代。 [NPM](https://www.npmjs.com/package/add-coder) · [GitHub](https://github.com/xiaomingming92/add-coder)
+
+> 🧭 **从零上手实操？** 请参见 [GUIDE.md](https://github.com/xiaomingming92/add-coder/blob/main/GUIDE.md)
+
+```bash
+npx add-coder init
+```
+
+## 这不是模板工具，这是架构差异
+
+### ① 审计是基础设施，而非事后日志
+| 传统模式 | add-coder |
+|---|---|
+| 日志是 append-only 文本文件 | 审计是 **结构化数据表**（DevOperation + AuditLog），支持按 plan/step/agent/tool 多维查询 |
+| 审计靠开发者自觉记录 | **MCP 审计工具链** 自动记录每次操作 |
+| 无关联性 | Plan → Spec → Task → Step → Tool Call，形成完整证据链 |
+
+### ② 门禁驱动，而非自由对话
+```
+DPS (Design-Process Symmetry)  — 设计/实现/文档/审计 四维各 25%，< 85% BLOCKED
+RAHS (Runtime Architecture Health Score) — 运行时架构健康度，< 90% BLOCKED
+```
+这不是「建议」，是**架构阻断** — 不通过闸门的 Step 无法推进到下一步。
+
+### ③ 跨轮记忆，而非每轮失忆
+- **Handoff 文档** — 每轮 Session 结束时自动生成结构化交接文档
+- **Plan 索引** — 所有 Plan 通过 `index.md` 集中索引
+- **DevLog 时序记录** — 每一步操作写入 `{YYYY-MM}/{DD}/` 时间轴
+
+### ④ Policy-Update-Loop：治理自我进化
+```
+执行 → 审计 → 边界报告 → 规则调整 → 下一轮执行
+```
+运行时产生的 Report 会反过来更新 governance rules。
+
+### ⑤ 多 IDE 的 Hook 即治理层
+| IDE | 治理文档 | 覆盖事件 | Hook 配置 |
+|---|---|---|---|
+| Claude Code | [ADD-governance-claude-code.md](./ADD-governance-claude-code.md) | 14/17 | `.claude/hooks/*.sh` |
+| Qoder CN | [ADD-governance-qoder-cn.md](./ADD-governance-qoder-cn.md) | 10/17 | `.qoder/hooks/*.sh` |
+| VS Code Copilot | [ADD-governance-vscode-copilot.md](./ADD-governance-vscode-copilot.md) | 10/17 | `.github/hooks/*.json` → `.vscode/hooks/*.sh` |
+| Trae | [ADD-governance-trae.md](./ADD-governance-trae.md) | 6/17 | `hooks.json` → `.trae/hooks/*.sh` |
+| Codex | [ADD-governance-codex.md](./ADD-governance-codex.md) | 0 (原生) / 14 (导入 Claude) | `.codex/hooks.json` |
+
+## 快速开始
+```bash
+npx add-coder init
+```
+
+| 命令 | 说明 |
+|---|---|
+| `init` | 初始化 ADD 模板，支持 `--adapter claude\|qoder\|vscode\|trae\|codex\|auto` |
+| `sync` | 增量同步缺失文件 |
+| `status` | 检查模板完整性 |
+
+| 选项 | 说明 |
+|---|---|
+| `--adapter <type>` | 目标 IDE：claude / qoder / vscode / trae / codex / auto |
+| `--force` | 覆盖已有文件 |
+| `--dry-run` | 预览模式，不写入 |
+
+## MCP 审计工具链
+| 工具 | 用途 |
+|---|---|
+| `record_dev_operation` | 记录开发操作审计 |
+| `query_audit_logs` | 按 planKeyword / targetId 查询审计记录 |
+| `check_dps` | DPS 闸门（< 85% BLOCKED） |
+| `check_rahs` | RAHS 闸门（< 90% BLOCKED） |
+
+## 前置条件
+- Node.js >= 20 · Prisma ^7.0 · PostgreSQL / SQLite
+
+## 🎬 预告
+| 计划 | 说明 |
+|---|---|
+| Demo 仓库演示 | Policy-Update-Loop 与 Report 体系端到端闭环实践 |
+| MCP 能力重构 | MCP 工具链架构升级 |
+| 对话记忆增强 | 长期项目知识记忆和 plan 级别的稀疏记忆 |
+
+> 📦 [更新日志](./CHANGELOG.md)
+</details>

package/README.md

@@ -1,6 +1,6 @@
 # add-coder
 
-> 🌐 🀄中文 | [English](./README.en.md)
+> 🀄中文 | 🔤[English](#-english-readme)
 
 **AI 代码治理的落地方案** — [codein2027](https://github.com/xiaomingming92/codein2027) 快速构建 ADD 编程范式的完整脚手架。以「审计即基础设施」为核心，彻底打破编程过程黑盒与跨轮失忆，让编程范式进化为可审计、可追溯、可收敛的新时代。 [NPM](https://www.npmjs.com/package/add-coder) · [GitHub](https://github.com/xiaomingming92/add-coder)
 
@@ -172,15 +172,16 @@ npx add-coder init
        │  Handoff / DevLog 时序文档            │
        └─────────────────────────────────────┘
                            │
-              ┌────────────┼────────────┐
-              ▼            ▼            ▼
-       ┌──────────┐ ┌──────────┐ ┌──────────┐
-       │ Claude   │ │  Qoder   │ │  VS Code │
-       │ Hooks    │ │  Hooks   │ │  Config  │
-       └──────────┘ └──────────┘ └──────────┘
+    ┌──────────┬───────────┼────────┬─────┐
+    ▼          ▼           ▼        ▼     ▼
+┌──────┐ ┌──────┐ ┌──────────┐ ┌──────┐ ┌──────┐
+│Claude│ │Qoder │ │ VS Code  │ │ Trae │ │Codex │
+│Hooks │ │Hooks │ │  Config  │ │Hooks │ │Hooks │
+│14/17 │ │10/17 │ │  10/17   │ │ 6/17 │ │ 6/17 │
+└──────┘ └──────┘ └──────────┘ └──────┘ └──────┘
                            │
-              ┌────────────┘
-              ▼
+                           |
+                           ▼
        ┌─────────────────────────────────────┐
        │     Caijuehub 规则引擎               │
        │  TOML 驱动的策略体系                 │
@@ -216,3 +217,238 @@ npx add-coder init
 |------|------|
 | Demo 仓库演示 | 提供完整示例仓库，展示 Policy-Update-Loop 与 Report 体系的端到端闭环实践 |
 | MCP 能力重构 | MCP 工具链架构升级，提升审计与门禁工具的可扩展性和独立部署能力 |
+| 对话记忆增强 | 长期项目知识记忆和plan级别的稀疏记忆 |
+
+
+
+---
+## 🔤 English README
+
+**AI Governance, Implemented** — The complete scaffolding from [codein2027](https://github.com/xiaomingming92/codein2027) for rapidly building the ADD programming paradigm. Built on the core principle of **Audit as Infrastructure**, it shatters the black-box programming process and cross-session amnesia, evolving the programming paradigm into an auditable, traceable, and convergent new era. [NPM](https://www.npmjs.com/package/add-coder) · [GitHub](https://github.com/xiaomingming92/add-coder)
+
+
+> 🧭 **Getting hands-on?** See [GUIDE.md](https://github.com/xiaomingming92/add-coder/blob/main/GUIDE.md) — trigger word quick reference, requirements-to-Plan, and full workflow walkthrough.
+
+```bash
+npx add-coder init
+```
+
+---
+
+## Not a Template Tool — An Architectural Difference
+
+There are already plenty of AI coding templates, hook adapters, and MCP scaffolds. What fundamentally sets add-coder apart is not "what files it generates," but a **paradigm shift at the architectural level**:
+
+### ① Audit Is Infrastructure, Not After-the-Fact Logging
+
+Traditional AI development: Chat → Generate code → Dig through chat history afterward to find "who changed what"
+
+| Traditional Model | add-coder |
+|-------------------|-----------|
+| Logs are append-only text files | Audit is a **structured data table** (DevOperation + AuditLog), supporting multi-dimensional queries by plan/step/agent/tool |
+| Auditing relies on developer discipline | The **MCP audit toolchain** automatically records every operation; system gateways enforce checks |
+| No traceability | Audit events are naturally linked: Plan → Spec → Task → Step → Tool Call, forming a complete evidence chain |
+
+### ② Gateway-Driven, Not Free-Form Conversation
+
+Traditional AI coding is "you say, I do" — quality depends entirely on the LLM's state that day. add-coder embeds **dual quality gateways** into the architecture:
+
+```
+DPS (Design-Process Symmetry)  — Design / Implementation / Docs / Audit, each weighted 25%, < 85% BLOCKED
+RAHS (Runtime Architecture Health Score) — Runtime architecture health, < 90% BLOCKED
+```
+
+These are not "suggestions" — they are **architectural blocks**. A Step cannot advance without passing its gateway.
+
+### ③ Cross-Session Memory, Not Per-Session Amnesia
+
+The fatal flaw of AI conversations: architectural decisions from last session, bugs fixed, agreements reached — all forgotten in the next conversation. add-coder solves this at the architecture level:
+
+- **Handoff Documents** — Automatically generated structured handoff at the end of each session, auto-loaded by the next session
+- **Plan Index** — All Plans are centrally indexed via `index.md`, supporting fuzzy-match quick lookup
+- **DevLog Timeline** — Every operation is written to the `{YYYY-MM}/{DD}/` timeline, enabling full historical state traceability
+
+### ④ Policy-Update-Loop: Self-Evolving Governance (the scaffold itself does not include this architectural capability; a DEMO repo will be provided next to better illustrate the Policy-Update-Loop and Report system)
+
+Not a static template, but a **closed-loop adaptive system**:
+
+```
+Execute → Audit → Boundary Report → Rule Adjustment → Next Execution
+```
+
+Runtime-generated Reports feed back into governance rules, enabling continuous evolution of governance strategies.
+
+### ⑤ Multi-IDE Hooks as the Governance Layer
+
+Hooks are not "notification push" — they are the **IDE runtime interception layer**:
+
+| Hook Type | Function |
+|-----------|----------|
+| PreToolUse | Validates whitelist before tool invocation, injects context, DPS condition checks |
+| PostToolUse | Automatic audit logging, Plan sync detection, format guarding |
+| PreCompact | Forces retention of critical document paths during cross-session context compression |
+| PromptSubmit | Injects ADD vocabulary triggers, ensuring zero-latency LLM response to commands like "acceptance" and "gateway" |
+
+Each IDE（Claude Code / Qoder CN / VS Code Copilot / Trae / Codex）has its own hook implementation, but the **governance logic is unified** — the architecture is consistent, only the adapter layer differs.
+
+| IDE | Governance Doc | Events Covered | Hook Config |
+|---|---|---|---|
+| Claude Code | [ADD-governance-claude-code.md](./ADD-governance-claude-code.md) | 14/17 | `.claude/hooks/*.sh` |
+| Qoder CN | [ADD-governance-qoder-cn.md](./ADD-governance-qoder-cn.md) | 10/17 | `.qoder/hooks/*.sh` |
+| VS Code Copilot | [ADD-governance-vscode-copilot.md](./ADD-governance-vscode-copilot.md) | 10/17 | `.github/hooks/*.json` → `.vscode/hooks/*.sh` |
+| Trae | [ADD-governance-trae.md](./ADD-governance-trae.md) | 6/17 | `hooks.json` → `.trae/hooks/*.sh` |
+| Codex | [ADD-governance-codex.md](./ADD-governance-codex.md) | 0 native / 14 (via Claude import) | `.codex/hooks.json` |
+
+---
+
+## Quick Start
+
+```bash
+npx add-coder init
+```
+
+The first `init` auto-detects your IDE and interactively guides you through database selection (PostgreSQL / SQLite / self-managed), container runtime (podman / docker / self-managed), Prisma initialization, and ADD template deployment.
+
+```bash
+npx add-coder init
+# → Choose IDE (Qoder / Claude / VS Code)
+# → Choose database (PostgreSQL / SQLite / self-managed)
+# → Choose container (podman / docker / self-managed)
+# → prisma init + add.prisma copied
+# → prisma db push (adds new tables only, no data deletion)
+# → prisma generate
+# → ADD governance model ready ✓
+```
+
+> **Env file priority**: `.env.development.local` > `.env.development` > `.env.local` > `.env`
+
+## Commands
+
+| Command | Description |
+|---------|-------------|
+| `init` | Initialize ADD templates, supports `--adapter claude\|qoder\|vscode\|auto` |
+| `sync` | Incrementally sync missing files |
+| `status` | Check template integrity |
+
+### init Internal Flow
+
+| Step | Action | Description |
+|------|--------|-------------|
+| ① | Detect IDE | Scan for `.qoder/` `.claude/` `.vscode/` existence, or specify via `--adapter` |
+| ② | Load config | Interactive Q&A > `add-coder.config.ts` > auto-detect > defaults |
+| ③ | DB deployment | `db-ensure.sh` starts container/PG connection + `injectPrisma()` Caijue layer (Prisma init → AddUser model copy → db push → generate) |
+| ④ | Render templates | 55 core template files (skills/agents/templates/plans/specs/scripts…) |
+| ⑤ | Deploy adapters | Copy core content to `.add/` `.qoder/` `.claude/` directories, supplement IDE-specific hooks/mcp |
+| ⑥ | Write files | Four modes: interactive / yes / force / dry-run; `.sh` scripts auto `chmod` |
+| ⑦ | Output summary | Created / skipped / overwritten stats + next-step hints |
+
+### init Options
+
+| Option | Description |
+|--------|-------------|
+| `--adapter <type>` | Target IDE: claude / qoder / vscode / trae / codex / auto (default) |
+| `--config <path>` | Specify config file |
+| `--yes` | Skip interactions, create new files only |
+| `--force` | Overwrite existing files |
+| `--dry-run` | Preview mode, no writes |
+
+## Generated Content
+
+| Directory | Content |
+|-----------|---------|
+| `.add/` | ADD shared core (skills, agents, docs, scripts, rules, etc.) |
+| `.claude/` | Claude Code adapter (hooks, settings.json, mcp.json) |
+| `.qoder/` | Qoder adapter (hooks, settings.json, mcp.json) |
+| `.vscode/` | VS Code adapter (settings.json, tasks.json) |
+| `.trae/` | Trae adapter (hooks.json, settings.json) |
+| `.codex/` | Codex adapter (hooks.json, settings.json) |
+
+## MCP Audit Toolchain
+
+`init` automatically deploys the MCP server (`mcp-server.ts`) into the project, loaded by the IDE via `mcp.json`. The following audit and governance tools are provided:
+
+| Tool | Purpose | Trigger Scenario |
+|------|---------|-----------------|
+| `record_dev_operation` | Record development operation audits (before/after/reason) | Every file change, config modification |
+| `query_audit_logs` | Query audit records by planKeyword / targetId | Cross-session context recovery, iteration evidence verification |
+| `get_project_context` | Get ADD workflow status snapshot | Fresh conversation start |
+| `get_db_schema` | Get Prisma schema info | Database-related operations |
+| `check_dps` | DPS gateway (Design/Implementation/Docs/Audit, each 25%) | End of Step 0 |
+| `check_rahs` | RAHS gateway (runtime architecture health) | Step 4/8 |
+| `check_add_route_status` | add-route file existence check | Before Step 3 |
+| `check_spec_sync` | Spec doc checkbox status vs. code consistency | After Spec execution |
+| `find_related_docs` | Search related architecture/spec documents | Context understanding |
+
+> Full tool list: [MCP Toolchain Specification](https://github.com/xiaomingming92/codein2027/blob/main/docs/大田精准耕播智能决策系统/knowledge/02-规范/%E3%80%8A%E5%BC%80%E5%8F%91%E6%93%8D%E4%BD%9C%E5%AE%A1%E8%AE%A1%E5%AD%98%E6%A1%A3%E8%A7%84%E8%8C%83%E3%80%8B.md).
+
+## Architecture Overview
+
+```
+                    ┌─────────────┐
+                    │  ADD Paradigm│
+                    │  Step 0-9    │
+                    └──────┬──────┘
+                           │ Gateway-driven
+              ┌────────────┼────────────┐
+              ▼            ▼            ▼
+       ┌──────────┐ ┌──────────┐ ┌──────────┐
+       │DPS Gateway│ │RAHS Gate │ │Compliance│
+       └────┬─────┘ └────┬─────┘ └────┬─────┘
+            │            │            │
+              ▼            ▼            ▼
+       ┌─────────────────────────────────────┐
+       │        Audit Infrastructure Layer    │
+       │  DevOperation / AuditLog Tables      │
+       │  MCP Audit Toolchain                 │
+       │  Handoff / DevLog Timeline Docs      │
+       └─────────────────────────────────────┘
+                           │
+    ┌──────────┬───────────┼───────────┬──────────┐
+    ▼          ▼           ▼           ▼          ▼
+┌──────┐ ┌──────┐ ┌──────────┐ ┌──────┐ ┌──────┐
+│Claude│ │Qoder │ │ VS Code  │ │ Trae │ │Codex │
+│Hooks │ │Hooks │ │  Config  │ │Hooks │ │Hooks │
+│14/17 │ │10/17 │ │  10/17   │ │ 6/17 │ │ 6/17 │
+└──────┘ └──────┘ └──────────┘ └──────┘ └──────┘
+                           │
+              ┌────────────┘
+              ▼
+       ┌─────────────────────────────────────┐
+       │       Caijuehub Rule Engine          │
+       │  TOML-Driven Policy System           │
+       │  Detect / Adapt / Prisma / Write —   │
+       │  Fully Configurable                  │
+       └─────────────────────────────────────┘
+```
+
+## Prerequisites
+
+- Node.js >= 20
+- Prisma ^7.0 (auto-detected during `init`, guided installation if missing)
+- PostgreSQL / SQLite (MCP toolchain depends on DevOperation + AuditLog tables)
+
+> **Recommended**: Run PostgreSQL via Podman/Docker, reference config:
+> ```yaml
+> postgres:
+>   image: docker.io/postgres:16-alpine
+>   ports: ["127.0.0.1:5433:5432"]
+>   environment:
+>     POSTGRES_DB: mydb
+>     POSTGRES_USER: admin
+>     POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
+> ```
+> Mount data volume to `~/data/your_project/postgres/` to avoid data loss on container removal.
+
+> 📦 [Changelog](./CHANGELOG.md)
+
+---
+
+## 🎬 Coming Soon
+
+| Plan | Description |
+|------|-------------|
+| Demo Repo | A full example repository showcasing end-to-end closed-loop practice of Policy-Update-Loop and the Report system |
+| MCP Restructure | MCP toolchain architecture upgrade, improving audit and gateway tool extensibility and standalone deployment capability |
+| Memory Enhancement | Long-term project knowledge memory and plan-level sparse memory |
+
+---

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "add-coder",
-  "version": "0.2.0",
+  "version": "0.2.2",
   "private": false,
-  "description": "[codein2027](https://github.com/xiaomingming92/codein2027) 快速构建 ADD 编程范式的完整脚手架——AI 代码治理的落地方案。以「审计即基础设施」为核心，彻底打破编程过程黑盒与跨轮失忆，让编程范式进化为可审计、可追溯、可收敛的新时代。npx 即用，人人可体验。",
+  "description": "[codein2027](https://github.com/xiaomingming92/codein2027) - A complete scaffolding for building the ADD programming paradigm, the implementation layer for AI code governance. Core principle: Audit as Infrastructure. Breaks the black-box programming process and cross-session amnesia, evolving programming paradigms into an auditable, traceable, and convergent new era. npx-ready.\n\n[codein2027](https://github.com/xiaomingming92/codein2027) 快速构建 ADD 编程范式的完整脚手架——AI 代码治理的落地方案。以「审计即基础设施」为核心，彻底打破编程过程黑盒与跨轮失忆，让编程范式进化为可审计、可追溯、可收敛的新时代。npx 即用，人人可体验。",
   "repository": {
     "type": "git",
     "url": "https://github.com/xiaomingming92/add-coder.git"

package/templates/adapters/claude/hooks/doc-format-guard.sh

@@ -104,7 +104,7 @@ if [ -z "$TEMPLATE_NAME" ]; then
   fi
 fi
 
-SCHEMA_FILE="$TEMPLATES_DIR/$(echo "${TEMPLATE_NAME%.md}" | sed 's/-template$//').schema.json"
+SCHEMA_FILE="$TEMPLATES_DIR/${TEMPLATE_NAME%.md}.schema.json"
 # L84: schema 文件不存在 → 无校验规则，阻断（不允许无规则放行）
 if [ ! -f "$SCHEMA_FILE" ]; then
   echo "⛔ 阻断：模板 ${TEMPLATE_NAME} 缺少对应的 .schema.json 校验规则" >&2

package/templates/adapters/qoder/hooks/doc-format-guard.sh

@@ -104,7 +104,7 @@ if [ -z "$TEMPLATE_NAME" ]; then
   fi
 fi
 
-SCHEMA_FILE="$TEMPLATES_DIR/$(echo "${TEMPLATE_NAME%.md}" | sed 's/-template$//').schema.json"
+SCHEMA_FILE="$TEMPLATES_DIR/${TEMPLATE_NAME%.md}.schema.json"
 # L84: schema 文件不存在 → 无校验规则，阻断（不允许无规则放行）
 if [ ! -f "$SCHEMA_FILE" ]; then
   echo "⛔ 阻断：模板 ${TEMPLATE_NAME} 缺少对应的 .schema.json 校验规则" >&2

package/templates/core/hooks/doc-format-guard.sh

@@ -104,7 +104,7 @@ if [ -z "$TEMPLATE_NAME" ]; then
   fi
 fi
 
-SCHEMA_FILE="$TEMPLATES_DIR/$(echo "${TEMPLATE_NAME%.md}" | sed 's/-template$//').schema.json"
+SCHEMA_FILE="$TEMPLATES_DIR/${TEMPLATE_NAME%.md}.schema.json"
 # L84: schema 文件不存在 → 无校验规则，阻断（不允许无规则放行）
 if [ ! -f "$SCHEMA_FILE" ]; then
   echo "⛔ 阻断：模板 ${TEMPLATE_NAME} 缺少对应的 .schema.json 校验规则" >&2

package/templates/core/hooks/lib/context-inject.sh

@@ -0,0 +1,96 @@
+#!/bin/bash
+# context-inject.sh — 上下文注入模板
+# 共享库
+
+# 结构化 SessionStart JSON 注入
+build_session_start_json() {
+  local plan="$1" step="$2" round="$3" handoff="$4"
+  cat <<EOF
+{
+  "continue": true,
+  "hookSpecificOutput": {
+    "hookEventName": "SessionStart",
+    "additionalContext": "上次 ADD 流程未完成:\n  Plan: ${plan}\n  轮次: ${round}\n  当前 Step: ${step} (add-route)\n  恢复命令: query_audit_logs({ planKeyword: '${plan}' })\n  handoff: ${handoff}"
+  }
+}
+EOF
+}
+
+# Stop 四象限分流 few-shot 上下文
+build_stop_context() {
+  local quadrant="$1" info="$2"
+  case "$quadrant" in
+    "no_add_no_dev")
+      echo "[ADD Stop] 无活跃 Plan，无代码改动。正常结束。"
+      ;;
+    "no_add_has_dev")
+      cat <<'EOF'
+[ADD Stop] ⚠️ 检测到代码修改但无活跃 ADD Plan。
+
+Plan 不是"文档开销"——它是代码治理的基础设斻。跳过 Plan 的后果:
+  · 没有 add-route → 每次改动无法追溯到具体 Task
+  · 没有 tasks.md → 后续 AI Session 不知道改了哪些文件
+  · 没有 handoff → 交接时上下文全丢，只能靠 git log 猜
+
+你必须立即补救，二选一:
+
+方案 A — 补 ADD 流程（招安）:
+  Step 0: 读 .qoder/templates/plan-template.md → 生成 Plan → .qoder/plans/{today}/{keyword}-plan-v1.md
+          生成 add-route → check_dps ≥ 85
+  Step 1: 扩展 AgentAuditPhase（如需要）
+  Step 2: 确认 agentAudit() 通道
+  Step 3: 将已写代码关联到 tasks.md
+  完成后可正常停止。
+
+方案 B — 补不上则回滚:
+  如果改动太复杂无法追溯生成 Plan，则:
+  ① git diff 确认改动范围
+  ② git checkout -- <改动的文件> 撤回
+  ③ 告知用户 "以下改动已回滚，请先走 ADD 流程再重新实施: <文件列表>"
+
+无论选 A 还是 B，完成后告诉用户下次执行 session-init 恢复上下文。
+EOF
+      ;;
+    "has_add_no_dev")
+      echo "[ADD Stop] ADD 流程进行中 (${info})，本次无代码改动。下次继续时执行 session-init 恢复上下文。"
+      ;;
+    "has_add_dev_step02")
+      echo "[ADD Stop] ADD Step 0-2: 文档先行/审计准备阶段。无需验收闭环。下一步: 进入 Step 3 代码实现。"
+      ;;
+    "has_add_dev_step3")
+      echo "[ADD Stop] ADD Step 3: 代码实现进行中 (${info})。完成后进入 Step 3.5 实现审查。"
+      ;;
+    "has_add_dev_unclosed")
+      cat <<'EOF'
+[ADD Stop] ⚠️ 代码已完成但验收未闭环:
+${info}
+
+请依次执行（不要等下次会话）:
+  ① Write devlog → handoff 同目录 devlog-{plan}-v{n}.md
+     格式: # Devlog: {plan}\n 日期 / Plan / 轮次 / 本轮改了什么 / 验收结果 / 遗留项 / 架构回看
+  ② Edit handoff → 更新 §验证标准 全部 [x] + 补充审计 ID
+     ★ 同步: checklist 有新 cuid → handoff ADD-7 表必须对应新增行
+     ★ Step 0 准入: handoff + add-route + Specs 三元组缺一不可，缺则回退 Step 0.5
+  ③ Read docs/ → 回看架构文档确认一致性
+  ④ Edit add-route → 勾选对应 Step [x]
+
+以上全部完成后 Agent 才能停止。
+
+下次恢复: 读 handoff → 查同目录 devlog-*.md → query_audit_logs
+EOF
+      ;;
+        "has_add_dev_closed")
+      echo "[ADD Stop] ✅ 验收闭环: add-route全部[x], devlog已记录, handoff已更新。验收幂等——重复触发不覆盖已有结论。"
+      ;;
+  esac
+}
+
+# 写操作前置守卫上下文
+build_pretool_context() {
+  local plan="$1" round="$2"
+  cat <<EOF
+[ADD PreToolUse] 当前 Plan: ${plan}，轮次: ${round}。
+本次写入应属于 ADD Step 3 代码实现阶段。
+完成后执行 record_dev_operation 记录审计。
+EOF
+}

package/templates/core/hooks/lib/state-detect.sh

@@ -0,0 +1,104 @@
+#!/bin/bash
+# state-detect.sh — ADD 活跃流程检测 + dev action 追踪
+# 共享库
+
+PROJECT_DIR="${QODER_PROJECT_DIR:-${QODERCN_PROJECT_DIR:-$PWD}}"
+QODER_DIR="$PROJECT_DIR/.qoder"
+PLANS_DIR="$QODER_DIR/plans"
+
+# dev action 标记文件（项目级，PreToolUse 写入，Stop 读取）
+DEV_FLAG="/tmp/qoder_dev_$(echo "$PROJECT_DIR" | md5sum 2>/dev/null | cut -c1-8 || echo "default")"
+
+# 检测活跃 ADD 流程
+# 返回: "plan_keyword::step_x/total::round_n/total_r::handoff_path::add_route_path" 或 ""
+detect_active_add() {
+  local handoff=""
+  local today_dir="$PLANS_DIR/$(date +%Y-%m)"
+  [ -d "$today_dir" ] && handoff=$(find "$today_dir" -name "*handoff*.md" -mtime -7 -type f 2>/dev/null | head -1)
+  [ -z "$handoff" ] && handoff=$(find "$PLANS_DIR" -name "*handoff*.md" -mtime -7 -type f 2>/dev/null | head -1)
+  [ -z "$handoff" ] && return 1
+
+  local plan_kw=$(basename "$handoff" | sed 's/-handoff.*//')
+
+  # add-route
+  local add_route=$(find "$PLANS_DIR" -name "*add-route*.md" -type f 2>/dev/null | head -1)
+
+  # Step 统计（从 add-route）
+  local step_info="?"
+  if [ -f "$add_route" ]; then
+    local ck=$(grep -c '\[x\]' "$add_route" 2>/dev/null || true)
+    local uc=$(grep -c '\[ \]' "$add_route" 2>/dev/null || true)
+    ck=${ck:-0}; uc=${uc:-0}
+    local total=$((ck + uc))
+    [ "$total" -gt 0 ] && step_info="${ck}/${total}"
+  fi
+
+  # 轮次统计（从 handoff）
+  local round_info="?"
+  if grep -q '<第[0-9]轮>' "$handoff" 2>/dev/null; then
+    local ck=$(grep -c '\[x\]' "$handoff" 2>/dev/null || true); ck=${ck:-0}
+    local total=$(grep -c '<第[0-9]轮>' "$handoff" 2>/dev/null || true); total=${total:-0}
+    [ "$total" -gt 0 ] && round_info="${ck}/${total}"
+  else
+    round_info="1/1"
+  fi
+
+  echo "${plan_kw}::${step_info}::${round_info}::${handoff}::${add_route:-none}"
+}
+
+# 标记 dev action
+mark_dev_action() {
+  touch "$DEV_FLAG" 2>/dev/null || true
+}
+
+# 检测 dev action
+has_dev_action() {
+  [ -f "$DEV_FLAG" ]
+}
+
+# 清理 dev action 标记（验收闭环后调用）
+clear_dev_action() {
+  rm -f "$DEV_FLAG" 2>/dev/null || true
+}
+
+# 检查验收完整度，返回 issues 文本
+check_add_completeness() {
+  local handoff="$1" add_route="$2"
+  local issues=""
+
+  # devlog（内容已回流至 handoff，检查 handoff 是否含验收结果）
+  if [ -f "$handoff" ] && ! grep -qE '验收|收敛|闭环|本轮改了什么|devlog' "$handoff" 2>/dev/null; then
+    issues="${issues}  [ ] devlog 缺失（handoff 无验收记录）\n"
+  fi
+
+  # handoff 验证标准
+  if [ -f "$handoff" ]; then
+    local uc=$(grep -c '\[ \]' "$handoff" 2>/dev/null || echo "0")
+    [ "$uc" -gt 0 ] && issues="${issues}  [ ] handoff ${uc} 项未勾选\n"
+  fi
+
+  # add-route Step
+  if [ -f "$add_route" ]; then
+    local uc=$(grep -c '\[ \]' "$add_route" 2>/dev/null || echo "0")
+    [ "$uc" -gt 0 ] && issues="${issues}  [ ] add-route ${uc} Step 未闭环\n"
+  fi
+
+  echo -e "$issues"
+}
+
+# 检查是否已验收（幂等保护）
+# 返回 0 = 未验收，1 = 已验收
+is_already_accepted() {
+  local add_route="$1" handoff="$2"
+  # add-route Step 8 是否已 [x]
+  if [ -f "$add_route" ]; then
+    # 检查 Step 8 产出项是否勾选
+    if grep -A 10 'Step 8' "$add_route" 2>/dev/null | grep -q '\[x\].*验证并更新项目状态'; then
+      # handoff 是否有验收记录
+      if [ -f "$handoff" ] && grep -qE '✅.*验收|收敛|全部闭环|全部.*完成' "$handoff" 2>/dev/null; then
+        return 0
+      fi
+    fi
+  fi
+  return 1
+}

package/templates/core/hooks/lib/vocabulary.sh

@@ -0,0 +1,49 @@
+#!/bin/bash
+# vocabulary.sh — 从 vocabulary markdown 表格加载触发词
+# 单一数据源: .qoder/vocabulary/add-governance-vocabulary.md §类别 A-F 表格
+
+VOCABULARY_FILE="$PWD/.qoder/vocabulary/add-governance-vocabulary.md"
+
+# 输出格式: 优先级::触发词正则::响应文本（:: 避免与触发词内的 | 冲突）
+load_triggers() {
+  [ ! -f "$VOCABULARY_FILE" ] && return 1
+  sed -n '/^## 类别 A: 文档类型/,/^## 类别 [G-Z]/p' "$VOCABULARY_FILE" \
+    | grep -E '^\| (P0|P1|P2) ' \
+    | while IFS='|' read -r _ prio raw_trigger action; do
+        prio=$(echo "$prio" | xargs)
+        trigger=$(echo "$raw_trigger" | sed 's/`//g;s/ *\/ */|/g;s/^ *//;s/ *$//')
+        action=$(echo "$action" | xargs)
+        [ -z "$trigger" ] && continue
+        echo "${prio}::${trigger}::${action}"
+      done || true
+}
+
+match_trigger() {
+  local prompt="$1"
+  while IFS= read -r line; do
+    [ -z "$line" ] && continue
+    local prio="${line%%::*}"
+    local rest="${line#*::}"
+    local regex="${rest%%::*}"
+    local action="${rest#*::}"
+    # 跳过开发关键词检测行（由 Layer 2/3 分流处理，特征：超长regex含"修bug"）
+    if echo "$regex" | grep -qE '修\.\?bug|fix\.\?bug' 2>/dev/null; then
+      continue
+    fi
+    if echo "$prompt" | grep -qiE "$regex" 2>/dev/null; then
+      echo "[ADD 触发] ${regex} → ${action}"
+    fi
+  done < <(load_triggers 2>/dev/null)
+}
+
+load_dev_keywords() {
+  load_triggers 2>/dev/null | while IFS= read -r line; do
+    [ -z "$line" ] && continue
+    # 只取包含"开发|改功能"的开发关键词检测行
+    if echo "$line" | grep -q '开发|改功能' 2>/dev/null; then
+      local rest="${line#*::}"
+      local regex="${rest%%::*}"
+      echo "$regex"
+    fi
+  done || true
+}

package/templates/core/hooks/pre-tool-use.sh

@@ -1,78 +1,131 @@
 #!/bin/bash
-# pre-tool-use.sh — Claude Code PreToolUse：四路守卫
+# pre-tool-use.sh — PreToolUse §A§B（阻断模式，通用适配版）
+# §A: Bash 裸写保护 — 拦截所有绕过 IDE 追踪的文件写操作
+# §B: 源码 Plan 关联检查 — 无 Plan 的 src/**/*.ts 编辑阻断
 # 治理卡位 #4: 危险命令拦截 / 模板路径兜底 / 写入前置守卫 / 敏感文件保护
 set -euo pipefail
 
+input=$(cat)
+
+# 探测 MAGIC_DIR 和 PROJECT_DIR（兼容多种 adapter）
 HOOK_DIR="$(cd "$(dirname "$0")" && pwd)"
-export CURRENT_MAGIC=$(basename "$(dirname "$HOOK_DIR")")
-COMMON_LIB="$HOOK_DIR/lib/common.sh"
-[ -f "$COMMON_LIB" ] && source "$COMMON_LIB"
-
-input=$(parse_input)
-tool_name=$(json_get "$input" "tool_name")
-[ -z "$tool_name" ] && tool_name=$(echo "$input" | grep -o '"tool_name"[[:space:]]*:[[:space:]]*"[^"]*"' 2>/dev/null | sed 's/.*: *"\([^"]*\)".*/\1/' || echo "")
-
-export PROJECT_DIR="${CLAUDE_PROJECT_DIR:-$PWD}"
-
-# ── ① Bash matcher: 危险命令拦截 + 终端写文件拦截 ──
-if [ "$tool_name" = "Bash" ]; then
-  cmd=$(echo "$input" | grep -o '"command"[[:space:]]*:[[:space:]]*"[^"]*"' 2>/dev/null | sed 's/.*: *"\([^"]*\)".*/\1/' || echo "")
-  # 危险命令
-  if echo "$cmd" | grep -qiE 'rm[[:space:]]+-rf[[:space:]]+/|DROP[[:space:]]+TABLE|git[[:space:]]+push[[:space:]]+--force|mkfs\.|dd[[:space:]]+if='; then
-    echo "⛔ 危险命令已被阻止: $cmd" >&2
-    exit $EXIT_BLOCK
-  fi
-  # 终端写文件拦截（含 > / >> / << heredoc / mv / touch / python -c > file）
-  if echo "$cmd" | grep -qE '(cat|echo|tee|sed[[:space:]]+-i|awk|printf|cp|mv|dd|touch)[[:space:]]*.*([>]{1,2}|[|][[:space:]]*tee|<<)'; then
-    echo "⛔ 禁止通过终端命令直接写文件: $cmd。请使用 Write/Edit/SearchReplace 工具。" >&2
-    exit $EXIT_BLOCK
+PARENT="$(dirname "$HOOK_DIR")"
+MAGIC_DIR="$(basename "$PARENT")"
+PROJECT_DIR="${CLAUDE_PROJECT_DIR:-${QODER_PROJECT_DIR:-${QODERCN_PROJECT_DIR:-$(dirname "$PARENT")}}}"
+
+# ── §A 辅助函数: 阻断日志 ──
+_log_block() {
+  local rule="$1" cmd="$2"
+  mkdir -p "$PROJECT_DIR/$MAGIC_DIR/debug-dump"
+  cat >> "$PROJECT_DIR/$MAGIC_DIR/debug-dump/stdin.log" <<BLOCKLOG
+=== $(date) [BLOCKED by §A: ${rule}] ===
+command: ${cmd:0:300}
+=== DONE ===
+BLOCKLOG
+}
+
+# ═══════════════ §A: Bash 工具写入保护 ═══════════════
+# 任何通过 Bash 修改文件内容的操作都会绕过 IDE 工具层（Write/SearchReplace），
+# 导致 Plan 关联检查、doc-format-guard、审计追踪全部失效。
+# 因此全局阻断所有可写文件的 Bash 命令，强制走 IDE 工具通道。
+command=$(echo "$input" | jq -r '.tool_input.command // empty')
+if [ -n "$command" ]; then
+
+  # 检测 1: 脚本解释器 — 可写任意文件，无法解析脚本内容做细粒度拦截
+  if echo "$command" | grep -qE '^\s*(python3?|node|ruby|perl|php)(\s|$)'; then
+    _reason="禁止通过脚本解释器直接修改文件。请使用 Write 或 SearchReplace 工具操作文件。"
+    cat >&2 <<'EOF'
+⛔ [ADD PreToolUse §A] 阻断: 禁止通过脚本解释器直接修改文件。
+
+  python/node/ruby/perl/php 可在脚本中写入任意文件，绕过:
+    · Plan 关联检查（哪个文件属于哪个 ADD Plan？）
+    · doc-format-guard（章节/占位符/禁止词校验）
+    · 审计追踪（agentAudit 无法感知 Bash 内部的文件变更）
+
+  → 请改用 Write 或 SearchReplace 工具操作文件。
+  → 如需运行构建/测试脚本，使用 npx/pnpm/npm 命令。
+EOF
+    echo "{\"hookSpecificOutput\":{\"hookEventName\":\"PreToolUse\",\"permissionDecision\":\"ask\",\"permissionDecisionReason\":\"${_reason}\"}}"
+    _log_block "脚本解释器" "$command"
+    exit 2
   fi
-  # mv 无重定向但仍操作文件
-  if echo "$cmd" | grep -qE '^[[:space:]]*mv[[:space:]]+/tmp/'; then
-    echo "⛔ 禁止通过 mv /tmp/ 绕过 IDE 工具: $cmd" >&2
-    exit $EXIT_BLOCK
+
+  # 检测 2: sed -i 原地编辑
+  if echo "$command" | grep -qE '\bsed\b.*-i'; then
+    _reason="禁止通过 sed -i 直接编辑文件。请使用 SearchReplace 工具。"
+    cat >&2 <<'EOF'
+⛔ [ADD PreToolUse §A] 阻断: 禁止通过 sed -i 原地编辑文件。
+
+  sed -i 直接写入文件，绕过 IDE 工具层的所有校验。
+  → 请改用 SearchReplace 工具。
+EOF
+    echo "{\"hookSpecificOutput\":{\"hookEventName\":\"PreToolUse\",\"permissionDecision\":\"ask\",\"permissionDecisionReason\":\"${_reason}\"}}"
+    _log_block "sed -i" "$command"
+    exit 2
   fi
-  # python/node 脚本写文件
-  if echo "$cmd" | grep -qE '(python3|python|node)[[:space:]].*[>]{1,2}'; then
-    echo "⛔ 禁止通过脚本语言直接写文件: $cmd。请使用 Write/Edit/SearchReplace 工具。" >&2
-    exit $EXIT_BLOCK
+
+  # 检测 3: 输出重定向 (>/>>) 写入文件
+  if echo "$command" | grep -qE '[>]{1,2}\s+\S'; then
+    _reason="禁止通过重定向写入文件。请使用 Write 工具。"
+    cat >&2 <<'EOF'
+⛔ [ADD PreToolUse §A] 阻断: 禁止通过重定向(>/>>)写入文件。
+
+  重定向写入绕过 IDE 工具层，变更无法追踪。
+  → 请改用 Write 工具。
+EOF
+    echo "{\"hookSpecificOutput\":{\"hookEventName\":\"PreToolUse\",\"permissionDecision\":\"ask\",\"permissionDecisionReason\":\"${_reason}\"}}"
+    _log_block "重定向" "$command"
+    exit 2
   fi
-  mark_dev_action
-  exit 0
-fi
 
-# ── ② Write/Edit matcher: 文件写入前置守卫 ──
-if [ "$tool_name" = "Write" ] || [ "$tool_name" = "Edit" ]; then
-  file_path=$(echo "$input" | grep -o '"file_path"[[:space:]]*:[[:space:]]*"[^"]*"' 2>/dev/null | sed 's/.*: *"\([^"]*\)".*/\1/' || echo "")
-  [ -z "$file_path" ] && exit 0
-
-  # 检查是否写入 plans/specs/reviews 目录但无活跃 ADD Plan
-  if echo "$file_path" | grep -qE '\.(qoder|claude|add)/plans/|\.(qoder|claude|add)/specs/|\.(qoder|claude|add)/reviews/'; then
-    if type detect_active_add >/dev/null 2>&1; then
-      state=$(detect_active_add 2>/dev/null || true)
-      if [ -z "$state" ]; then
-        echo "[ADD PreToolUse] ⚠️ 正在写入 Plan/Spec/Review 文档但无活跃 ADD Plan——请先执行 add-paradigm" >&2
-      fi
-    fi
+  # 检测 4: tee / dd 写入
+  if echo "$command" | grep -qE '\btee\b|\bdd\b.*of='; then
+    _reason="禁止通过 tee/dd 写入文件。请使用 Write 或 SearchReplace 工具。"
+    cat >&2 <<'EOF'
+⛔ [ADD PreToolUse §A] 阻断: 禁止通过 tee/dd 写入文件。
+
+  → 请改用 Write 或 SearchReplace 工具。
+EOF
+    echo "{\"hookSpecificOutput\":{\"hookEventName\":\"PreToolUse\",\"permissionDecision\":\"ask\",\"permissionDecisionReason\":\"${_reason}\"}}"
+    _log_block "tee/dd" "$command"
+    exit 2
   fi
 
-  # 敏感文件保护
-  if echo "$file_path" | grep -qE '\.env$|\.env\.production$|\.env\.local$|credentials|secrets'; then
-    echo "⛔ 敏感文件受保护，禁止写入: $file_path" >&2
-    exit $EXIT_BLOCK
+  # 检测 5: cp / mv / touch — 可创建或覆盖文件
+  if echo "$command" | grep -qE '^\s*(cp|mv|touch)\b'; then
+    _reason="禁止通过 cp/mv/touch 操作文件。请使用 Write 或 SearchReplace 工具。"
+    cat >&2 <<'EOF'
+⛔ [ADD PreToolUse §A] 阻断: 禁止通过 cp/mv/touch 操作文件。
+
+  → 请改用 Write 或 SearchReplace 工具。
+EOF
+    echo "{\"hookSpecificOutput\":{\"hookEventName\":\"PreToolUse\",\"permissionDecision\":\"ask\",\"permissionDecisionReason\":\"${_reason}\"}}"
+    _log_block "cp/mv/touch" "$command"
+    exit 2
   fi
 
-  mark_dev_action
+  # 放行: 构建工具(npx/pnpm/npm/yarn)、版本控制(git)、
+  #        只读操作(ls/cat/grep/find/head/tail/wc)、目录操作(mkdir/rmdir) 等
   exit 0
 fi
 
-# ── ③ Read matcher: 模板路径兜底 ──
-if [ "$tool_name" = "Read" ]; then
-  file_path=$(echo "$input" | grep -o '"file_path"[[:space:]]*:[[:space:]]*"[^"]*"' 2>/dev/null | sed 's/.*: *"\([^"]*\)".*/\1/' || echo "")
-  if echo "$file_path" | grep -q 'templates/'; then
-    echo "[ADD PreToolUse] 提示: 模板文件已通过 hook 预读到上下文，可跳过重复读取" >&2
-  fi
+# ═══════════════ §B: 源码 Plan 关联检查 ═══════════════
+file_path=$(echo "$input" | jq -r '.tool_input.file_path // empty')
+[ -z "$file_path" ] && exit 0
+
+if ! echo "$file_path" | grep -qE '(src/|/src/).*\.(ts|tsx)$'; then
+  exit 0
+fi
+
+MOD=$(basename "$file_path" | sed 's/\.[jt]sx\?$//')
+
+MATCHES=$(grep -rl "$MOD" "$PROJECT_DIR/$MAGIC_DIR/plans" "$PROJECT_DIR/$MAGIC_DIR/specs" "$PROJECT_DIR/$MAGIC_DIR/reports" 2>/dev/null | wc -l)
+
+if [ "$MATCHES" -gt 0 ]; then
+  echo "{\"hookSpecificOutput\":{\"hookEventName\":\"PreToolUse\",\"permissionDecision\":\"allow\",\"permissionDecisionReason\":\"相关 ADD Plan 已存在\"}}"
   exit 0
 fi
 
-exit 0
+echo "⛔ 阻断: ${file_path} 无相关 ADD Plan。请先创建 Plan（plan-template / simple-plan-template）。" >&2
+echo "{\"hookSpecificOutput\":{\"hookEventName\":\"PreToolUse\",\"permissionDecision\":\"ask\",\"permissionDecisionReason\":\"无相关 ADD Plan。请用 AskUserQuestion 询问用户选择 plan-template 或 simple-plan-template 创建 Plan。\"}}"
+exit 2

package/templates/core/hooks/prompt-submit.sh

@@ -1,23 +1,20 @@
 #!/bin/bash
-# UserPromptSubmit — 触发词路由 + 模板全文注入（Claude Code 适配）
+# prompt-submit.sh — UserPromptSubmit 触发词智能路由（通用适配版）
 # 治理卡位 #3: Layer 1 精准触发 → Layer 2 阻断 → Layer 3 状态注入
 set -euo pipefail
 
-HOOK_DIR="$(cd "$(dirname "$0")" && pwd)"
-export CURRENT_MAGIC=$(basename "$(dirname "$HOOK_DIR")")
-
-COMMON_LIB="$HOOK_DIR/lib/common.sh"
-[ -f "$COMMON_LIB" ] && source "$COMMON_LIB"
-
-export PROJECT_DIR="${CLAUDE_PROJECT_DIR:-$PWD}"
-
-input=$(parse_input)
-prompt=$(echo "$input" | grep -o '"prompt"[[:space:]]*:[[:space:]]*"[^"]*"' 2>/dev/null | sed 's/.*: *"\([^"]*\)".*/\1/' || echo "")
+input=$(cat)
+prompt=$(echo "$input" | jq -r '.prompt // empty')
 [ -z "$prompt" ] && exit 0
 
-# ─── Layer 1: 精准触发词路由 + 验收幂等保护 ───
-matched=$(match_trigger "$prompt")
+HOOK_DIR="$(cd "$(dirname "$0")" && pwd)"
+source "$HOOK_DIR/lib/vocabulary.sh" 2>/dev/null || true
+source "$HOOK_DIR/lib/state-detect.sh" 2>/dev/null || true
+
+# ─── Layer 1: 精准 P0 触发词 ───
+matched=$(match_trigger "$prompt" 2>/dev/null || true)
 if [ -n "$matched" ]; then
+  # 验收幂等保护: 如果已验收，提示不重复
   if echo "$prompt" | grep -qiE '验收|收敛' 2>/dev/null; then
     add_state=$(detect_active_add 2>/dev/null || true)
     if [ -n "$add_state" ]; then
@@ -28,9 +25,12 @@ if [ -n "$matched" ]; then
 [ADD 验收] ⚠️ 已验收。进入 Review 模式:
   ① 重新检查 checklist [T]/[R] 项
   ② 审查 audit 记录完整性
-  ③ 如有差异 → Review 回流至 handoff（增量更新）
+  ③ 如有差异 → Review 回流至 handoff（增量更新，不覆盖已有结论）
   ④ 无差异 → 记录 'Review 已确认，无新发现'
+  ★ 同步检查: 如 checklist 有新 cuid 但 handoff 审计表缺失 → 更新 handoff ADD-7 表 + query_audit_logs 命令
 EOF
+        HOOK_DIR="$(cd "$(dirname "$0")" && pwd)"
+        "$HOOK_DIR/review-checklist.sh" "$_handoff" "$_add_route" 2>/dev/null || true
         exit 0
       fi
     fi
@@ -39,40 +39,37 @@ EOF
   exit 0
 fi
 
-# ─── 开发关键词检测 ───
-if ! echo "$prompt" | grep -qiE '开发|改功能|修.?bug|加需求|新增|重构|实施|验收|继续|生成plan|生成计划'; then
+# ─── 开发关键词检测（动态加载） ───
+dev_kw=$(load_dev_keywords 2>/dev/null || true)
+if [ -z "$dev_kw" ]; then
   exit 0
 fi
 
-echo "[ADD PromptSubmit] 检测到开发关键词" >&2
+if ! echo "$prompt" | grep -qiE "$dev_kw"; then
+  exit 0
+fi
 
-# ─── Layer 2: 无活跃 ADD → 阻断 ───
+# ─── Layer 2/3: 按活跃 ADD 分流 ───
 state=$(detect_active_add 2>/dev/null || true)
 if [ -z "$state" ]; then
-  cat <<'EOF'
+  # Layer 2: 无活跃 ADD → 强制启动
+  cat >&2 <<'EOF'
 [ADD 强制规则] 检测到开发任务。你必须先执行 add-paradigm SKILL 完成 ADD 工作流:
   Step 0: 文档先行 (Plan → Review → Specs)
+  Step 1: 扩展 AgentAuditPhase
+  Step 2: 确认 agentAudit() 通道
   Step 3: 代码实现 + 审计植入
+  ...
   Step 8: 收敛判断
 如果 add-paradigm SKILL 尚未激活，请先调用它。
 EOF
   exit 2
 fi
 
-# ─── Layer 3: 有活跃 ADD → 注入状态 + 模板全文 ───
-IFS='::' read -r plan step rounds handoff add_route <<< "$state"
-cat <<EOF
-[ADD 当前状态]
-  Plan: ${plan}
-  轮次: ${rounds}
-  当前 Step: ${step}
-  handoff: ${handoff}
-EOF
-
-# 模板全文注入（tpl-injected 去重）
-TPL_SCRIPT="$HOOK_DIR/lib/preload-templates.sh"
-if [ -f "$TPL_SCRIPT" ]; then
-  bash "$TPL_SCRIPT" --full --top 5
-fi
-
+# Layer 3: 有活跃 ADD → 注入状态
+plan=$(echo "$state" | awk -F'::' '{print $1}')
+step=$(echo "$state" | awk -F'::' '{print $2}')
+rounds=$(echo "$state" | awk -F'::' '{print $3}')
+handoff=$(echo "$state" | awk -F'::' '{print $4}')
+echo "[ADD 状态] Plan: ${plan}, 轮次: ${rounds}, Step: ${step}, handoff: ${handoff}"
 exit 0

package/templates/core/scripts/gen-plan-index.sh

@@ -0,0 +1,84 @@
+#!/bin/bash
+# 生成 {MAGIC_DIR}/plans/index.md 总览清单 — 按日期分层，每日自动更新
+# 自动探测 MAGIC_DIR（.qoder / .claude / .vscode / .trae / .codex / .add）
+set -e
+
+# 探测 MAGIC_DIR：在当前目录向上查找包含 plans/ 的隐藏目录
+SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
+CURRENT="$SCRIPT_DIR"
+MAGIC_DIR=""
+while [ "$CURRENT" != "/" ]; do
+  for d in "$CURRENT"/.qoder "$CURRENT"/.claude "$CURRENT"/.vscode "$CURRENT"/.trae "$CURRENT"/.codex "$CURRENT"/.add; do
+    if [ -d "$d/plans" ]; then
+      MAGIC_DIR="$d"
+      break 2
+    fi
+  done
+  CURRENT="$(dirname "$CURRENT")"
+done
+
+if [ -z "$MAGIC_DIR" ]; then
+  echo "❌ 未找到 MAGIC_DIR（.qoder / .claude / .vscode / .trae / .codex / .add 均无 plans/ 子目录）" >&2
+  exit 1
+fi
+
+PLANS_DIR="$MAGIC_DIR/plans"
+INDEX="$PLANS_DIR/index.md"
+NOW=$(date '+%Y-%m-%d %H:%M:%S')
+TOTAL=$(find "$PLANS_DIR" -mindepth 2 -type f -name '*.md' ! -name 'index.md' | wc -l)
+
+# 阶段1：收集数据到临时文件
+TMP=$(mktemp)
+find "$PLANS_DIR" -mindepth 2 -type f -name '*.md' ! -name 'index.md' | sort | while IFS= read -r f; do
+  rel="${f#$PLANS_DIR/}"
+  month="${rel%%/*}"
+  rest="${rel#*/}"
+  day="${rest%%/*}"
+  fn=$(basename "$rel")
+
+  case "$fn" in
+    *add-route*) tag="add-route" ;;
+    *handoff*)   tag="handoff" ;;
+    *execution*) tag="execution" ;;
+    *)           tag="plan" ;;
+  esac
+
+  topic=$(head -1 "$f" 2>/dev/null | sed 's/^#\+\s*//' | sed 's/ - .*//' | sed 's/  .*//')
+  if [ -z "$topic" ] || [ "${#topic}" -le 3 ]; then
+    topic=$(echo "$fn" | sed 's/\.md$//;s/-v[0-9]*$//;s/-plan$//;s/-handoff$//;s/-add-route$//;s/-execution$//;s/^farm-agent-//;s/^team-coordinator-//;s/^co-agent-//;s/^agent-//' | tr '-' ' ')
+  fi
+
+  echo "${month}|${day}|${tag}|${fn}|${topic}" >> "$TMP"
+done
+
+# 阶段2：写入 index.md
+cat > "$INDEX" << EOF
+# Plans 总览
+
+> 自动生成: $NOW | 文档总数: $TOTAL | 下次更新: 每天 2:00 AM
+
+EOF
+
+prev_month=""
+first=true
+while IFS='|' read -r month day tag fn topic; do
+  if [ "$month" != "$prev_month" ]; then
+    prev_month="$month"
+    first=true
+  fi
+
+  if $first; then
+    { echo ""; echo "## $month"; echo ""; echo "| 日 | 类型 | 文档 | 主题 |"; echo "|---|------|------|------|"; } >> "$INDEX"
+    first=false
+  fi
+
+  echo "| $day | $tag | [$fn]($month/$day/$fn) | $topic |" >> "$INDEX"
+done < <(sort -t'|' -k1,1r -k2,2n "$TMP")
+
+rm -f "$TMP"
+
+echo "" >> "$INDEX"
+echo "---" >> "$INDEX"
+echo "*索引由 \`$(basename "$MAGIC_DIR")/scripts/gen-plan-index.sh\` 自动生成，勿手动编辑*" >> "$INDEX"
+
+echo "✅ index.md 已更新 ($TOTAL 文档)"

package/templates/core/templates/simple-plan-template.schema.json

@@ -100,10 +100,10 @@
         "{ACTION_2}",
         "{ACTION_3}"
     ],
-    "forbidden_terms": [ "Phase", 
+    "forbidden_terms": [
+        "Phase", 
         "Round",
-        "轮次",
-        "阶段",
-        "步骤"
-    ]
+        "阶段"
+    ],
+    "forbidden_terms_note": "禁止使用 Phase/Round/阶段 作为 Task 分组词，必须使用模板规定的「轮次」。'步骤'和'轮次'不禁——它们是模板自身的结构关键词。"
 }

package/templates/core/templates/spec-template.schema.json

@@ -34,7 +34,6 @@
     "forbidden_terms": [
         "Phase",
         "Step",
-        "Task",
         "阶段",
         "步骤"
     ]

package/templates/core/templates/standard-plan-template.schema.json

@@ -66,8 +66,7 @@
     "forbidden_terms": [
         "Phase",
         "Round",
-        "轮次",
-        "阶段",
-        "步骤"
-    ]
+        "阶段"
+    ],
+    "forbidden_terms_note": "禁止使用 Phase/Round/阶段 作为 Task 分组词，必须使用模板规定的「轮次」。'步骤'和'轮次'不禁——它们是模板自身的结构关键词。"
 }