peaks-loop 4.1.2 → 4.1.4

package/.claude-plugin/marketplace.json

@@ -1,106 +1,195 @@
 {
   "metadata": {
     "pluginRoot": ".",
-    "version": "2.0.3"
+    "version": "4.1.4"
   },
   "plugins": [
     {
       "name": "peaks-loop",
-      "description": "Cross-AI-IDE workflow-gating CLI + 11-skill family. Turns LLM improvisation into auditable engineering process. Skills cover PRD / R&D / UI / QA / change-control / context / SOP definition / orchestration. Soft-fail gates block irreversible actions mid-conversation (even under --dangerously-skip-permissions).",
-      "version": "2.0.3",
+      "description": "Loop Engineering CLI — workflow primitive / loop guards / evaluators / slice orchestration",
+      "version": "4.1.4",
       "author": {
         "name": "SquabbyZ"
       },
       "homepage": "https://github.com/SquabbyZ/peaks-loop",
       "repository": "https://github.com/SquabbyZ/peaks-loop",
       "license": "MIT",
-      "tags": [
-        "workflow",
-        "gating",
+      "keywords": [
+        "peaks-loop",
+        "loop-engineering",
+        "ai-orchestration",
+        "ai-coding-agent",
+        "ai-programmer",
+        "multi-agent",
+        "claude-code",
+        "codex",
+        "z-code",
+        "cursor",
+        "trae",
+        "tongyi-lingma",
+        "agent-harness",
+        "agentic-engineering",
+        "autonomous-workflow",
+        "workflow-orchestration",
+        "llm-workflow",
+        "long-running-task",
+        "sub-agent-dispatch",
+        "dag-orchestration",
+        "slice-decomposition",
         "sop",
+        "openspec",
+        "karpathy",
+        "darwin",
+        "anti-drift",
+        "evolution-evaluation",
+        "ci-cd",
+        "github-actions",
+        "trusted-publishing",
+        "oidc",
+        "monorepo",
+        "pnpm",
+        "vitest",
         "code-review",
-        "agent-team",
-        "cross-ide",
-        "claude-code",
-        "memory",
-        "second-opinion"
-      ],
-      "keywords": [
-        "AI IDE",
-        "agent guardrails",
-        "SOP engine",
-        "cross-IDE",
-        "developer workflow",
-        "irreversible-action gates"
+        "tdd",
+        "security-scan",
+        "lint",
+        "typecheck",
+        "devtool",
+        "cli",
+        "developer-tools"
       ],
+      "mcpServers": {
+        "peaks": {
+          "command": "peaks",
+          "args": [
+            "mcp",
+            "serve"
+          ]
+        }
+      },
       "skills": [
         {
-          "name": "peaks-solo",
-          "path": "./skills/peaks-solo",
-          "description": "Dispatcher (分诊员) — natural-language front door for the Peaks-Loop skill family. Use when the user describes a task in NL and does not know which peaks-* skill fits. NOT for code/content/doctor/issue-fix-orchestrator/SOP work (use the specific skill)."
+          "name": "peaks-audit",
+          "path": "./skills/peaks-audit",
+          "description": "Gate autonomous LLM work on a 6-dimension audit + user-accepted goal. Use IMMEDIATELY after a need is expressed, BEFORE any PRD/RD/QA work starts."
         },
         {
           "name": "peaks-code",
           "path": "./skills/peaks-code",
-          "description": "Full-auto orchestration facade for the Peaks-Loop skill family. Use when the user asks Peaks-Loop to handle a project workflow end-to-end."
+          "description": "Code-domain loop engineering orchestrator for the Peaks-Loop skill family. Use when the user asks Peaks-Loop to handle a code-repo workflow end-to-end (端到端/全流程/需求开发), especially from a product document (PRD/飞书文档/Feishu doc) through implementation and validation. Coordinates peaks-prd, peaks-rd, peaks-qa, peaks-ui, peaks-sc, and peaks-txt while preserving user confirmation gates. Triggers on `/peaks-code`, \"peaks code\", \"全流程开发\", \"端到端迭代\". General primitives (peaks-resume / peaks-status / peaks-test) are sibling skills, not children."
         },
         {
-          "name": "peaks-resume",
-          "path": "./skills/peaks-resume",
-          "description": "Resume an in-flight peaks-code slice in the current session."
+          "name": "peaks-content",
+          "path": "./skills/peaks-content",
+          "description": "Non-code orchestrator for content workflows (draft / edit / publish / archive). Use when a user wants to drive an end-to-end content-production loop (blog post, newsletter, marketing copy, social thread, doc page) where the LLM must coordinate draft / edit / tone / publish / archive stages with explicit gates between them, and where the user only wants to speak natural language and pick options. NOT for free-form chatting; NOT for code review. Reuses the peaks-loop Loop Engineering primitives (Loop Engineering Asset, Bee Asset, Workflow Trace, Evolution Evaluation) but does NOT import peaks-code internals. Triggers on `/peaks-content`, \"peaks content\", \"content workflow\", \"publish this to <channel>\", \"edit the draft\", \"archive the previous version\"."
         },
         {
-          "name": "peaks-status",
-          "path": "./skills/peaks-status",
-          "description": "Show the current state of the peaks-code orchestrator in a compact summary."
+          "name": "peaks-doctor",
+          "path": "./skills/peaks-doctor",
+          "description": "Orchestrate peaks-loop's L3 doctor (peaks audit + peaks doctor + peaks openspec from-doctor) for project health. Use when the user asks for a project health check, doctor report, audit, or wants to convert doctor findings into OpenSpec change records. Coordinates the L2 audit framework + the L3.2 doctor + the L3.3 from-doctor proposal generator. Triggers on `/peaks-doctor`, \"peaks doctor\", \"项目健康\", \"doctor report\", \"health check\", \"check the project\", \"audit my repo\".",
+          "userInvocable": false
         },
         {
-          "name": "peaks-test",
-          "path": "./skills/peaks-test",
-          "description": "Run the project's test suite on the current repo and report results."
+          "name": "peaks-final-review",
+          "path": "./skills/peaks-final-review",
+          "description": "Final-review skill for Peaks. Use when a workflow needs to assemble 4-dimension business-review evidence (functional-completeness, problem-resolution, no-new-bugs, existing-functionality-intact) for human acceptance at the end of an autonomous slice. Triggers on \"/peaks-final-review\", \"prepare final review\", \"4-dim review\", or peaks-code end-of-workflow handoff."
+        },
+        {
+          "name": "peaks-ide",
+          "path": "./skills/peaks-ide",
+          "description": "Orchestrate peaks-loop's IDE-aware behavior (hooks + statusline + handle) for a user's specific IDE. Detects the current state (which IDE the user is on, what peaks has already installed), plans the install / switch / status / uninstall actions, and invokes the existing peaks CLI primitives. Triggers on `/peaks-ide`, \"set up peaks for my IDE\", \"switch peaks to Trae\", \"what did peaks install\", \"uninstall peaks hooks\". Sits between the user and `peaks hooks install` / `peaks statusline install` / `peaks hook handle` — those are the CLI primitives; this skill is the user-facing surface.",
+          "userInvocable": false
+        },
+        {
+          "name": "peaks-issue-fix-orchestrator",
+          "path": "./skills/peaks-issue-fix-orchestrator",
+          "description": "End-to-end orchestrator that surveys open issues in a target repo, classifies them by difficulty, mines reference merged-PRs, fixes each issue with real commits (with Repository + AI-modified declaration), writes normalized PR description files, and emits a one-line submit script. Use when the user wants to drive a \"fix N open issues and prepare PRs\" run on an upstream repo (any language; primarily Python + TypeScript). Reuses Loop Engineering primitives: 4-layer asset model, Darwin ratchet, karpathy-engineered red lines, Human-NL-Choice-Only. Triggers on `/peaks-issue-fix-orchestrator`, \"fix 30 issues\", \"dogfood on <repo>\", \"open-issue sweep on <repo>\"."
+        },
+        {
+          "name": "peaks-perf-audit",
+          "path": "./skills/bee/peaks-perf-audit",
+          "description": "Independent performance audit skill. Reads the immutable peaks-prd handoff + the project-level perf-template.md, performs a 6-dimension perf audit, and writes a structured envelope to `.peaks/_runtime/<sessionId>/audit/perf-<rid>.md`. Decoupled from peaks-rd 5-way fan-out per slice v2.12.0 (Group A, Tier 3). Use when the slice introduces CPU-bound hot loops, I/O throughput changes, memory allocation patterns, concurrency model changes, bundle size deltas, or cold-start costs.",
+          "userInvocable": false
         },
         {
           "name": "peaks-prd",
           "path": "./skills/bee/peaks-prd",
-          "description": "Product and requirement skill for Peaks. Use when a workflow needs PRD, refactor goals, non-goals, behavior preservation, acceptance criteria, product change proposals, or user-confirmable product artifacts.",
+          "description": "Product and requirement role for Peaks-Loop (LLM-only internal role; not user-invocable.\nTriggered by peaks-code via `peaks sub-agent dispatch --role prd`.)\nUse when a workflow needs PRD, refactor goals, non-goals, behavior preservation,\nacceptance criteria, product change proposals, or user-confirmable product artifacts.",
+          "userInvocable": false
+        },
+        {
+          "name": "peaks-qa",
+          "path": "./skills/bee/peaks-qa",
+          "description": "QA and verification role for Peaks-Loop (LLM-only internal role; not user-invocable.\nTriggered by peaks-code via `peaks sub-agent dispatch --role qa`.)\nUse when a workflow needs unit-test coverage evidence, regression matrices,\nbaseline reports, validation reports, acceptance checks, or refactor verification gates.",
           "userInvocable": false
         },
         {
           "name": "peaks-rd",
           "path": "./skills/bee/peaks-rd",
-          "description": "Research and development skill for Peaks. Use for engineering analysis, refactor planning, project scanning, code standards, unit-test coverage gates, implementation contracts, task graphs, and RD handoffs. Always use this for Peaks-Loop refactor workflows.",
+          "description": "Research and development role for Peaks-Loop (LLM-only internal role; not user-invocable.\nTriggered by peaks-code via `peaks sub-agent dispatch --role rd`.)\nUse for engineering analysis, refactor planning, project scanning, code standards,\nunit-test coverage gates, implementation contracts, task graphs, and RD handoffs.\nAlways use this for Peaks-Loop refactor workflows.",
           "userInvocable": false
         },
         {
-          "name": "peaks-qa",
-          "path": "./skills/bee/peaks-qa",
-          "description": "QA and verification skill for Peaks. Use when a workflow needs unit-test coverage evidence, regression matrices, baseline reports, validation reports, acceptance checks, or refactor verification gates.",
-          "userInvocable": false
+          "name": "peaks-resume",
+          "path": "./skills/peaks-resume",
+          "description": "Universal resume primitive for any in-flight Peaks-Loop workflow (orchestrator-agnostic). Detects the current session's deepest completed gate and surfaces a resume option via AskUserQuestion. Use when ANY bee (peaks-code, future peaks-research, future peaks-content, …) needs to recover from /compact or session interruption. Triggers on \"/peaks-resume\", \"continue the unfinished work\", \"继续完成\", \"把刚才没做完的收尾\". (Replaces peaks-resume as a top-level primitive.)"
         },
         {
-          "name": "peaks-ui",
-          "path": "./skills/bee/peaks-ui",
-          "description": "UI and experience skill for Peaks. Use when a workflow touches UI/UX, interaction design, visual direction, design systems, frontend page behavior, high-fidelity HTML prototypes, or UI regression seeds.",
+          "name": "peaks-reviewer",
+          "path": "./skills/bee/peaks-reviewer",
+          "description": "Third-party independent code-review skill for Peaks. Use as a parallel reviewer to karpathy-reviewer when a workflow needs an out-of-band (non-RD-model) review pass to mitigate single-LLM self-dogfood blind spots. Emits a schema-validated ReviewerEnvelope (no free-form LLM JSON). v2.14.0 G4.",
           "userInvocable": false
         },
         {
           "name": "peaks-sc",
           "path": "./skills/bee/peaks-sc",
-          "description": "Source control, sync, and change-control skill for Peaks. Use when a workflow needs change impact, artifact retention, commit boundaries, GitHub artifact repository pointers, sync state, or rollback evidence.",
+          "description": "Source control, sync, and change-control role for Peaks-Loop (LLM-only internal role;\nnot user-invocable. Triggered by peaks-code via `peaks sub-agent dispatch --role sc`.)\nUse when a workflow needs change impact, artifact retention, commit boundaries,\nGitHub artifact repository pointers, sync state, or rollback evidence.",
           "userInvocable": false
         },
         {
-          "name": "peaks-txt",
-          "path": "./skills/bee/peaks-txt",
-          "description": "Context and knowledge skill for Peaks. Use when a workflow needs context capsules, role-specific context slices, decision records, assumptions, discarded options, staleness checks, lessons, or reusable project memory.",
+          "name": "peaks-security-audit",
+          "path": "./skills/bee/peaks-security-audit",
+          "description": "Independent security audit skill. Reads the immutable peaks-prd handoff + the project-level security-template.md, performs an OWASP Top-10 + 8-dimension threat model audit, and writes a structured envelope to `.peaks/_runtime/<sessionId>/audit/security-<rid>.md`. Decoupled from peaks-rd 5-way fan-out per slice v2.12.0 (Group A, Tier 2). Use when the slice introduces authn/authz, secrets, input validation, path/filesystem trust, SQL/NoSQL injection, XSS/content injection, dependency supply chain, or external API surface changes.",
           "userInvocable": false
         },
+        {
+          "name": "peaks-slice-decompose",
+          "path": "./skills/peaks-slice-decompose",
+          "description": "Run multi-pass slice decomposition on a PRD-ready request and emit a v2 envelope with passes, cross-pass edges, and an LLM-arbitration trace. Use when a PRD is ready and the caller needs service-level and/or file-level cuts in one artifact."
+        },
+        {
+          "name": "peaks-solo",
+          "path": "./skills/peaks-solo",
+          "description": "Dispatcher (分诊员) for the Peaks-Loop skill family. Use when the user describes a task in natural language and does NOT know which peaks-* skill fits. peaks-solo reads the live skill pool via `peaks skill search`, dispatches to a matching leaf (peaks-code / peaks-content / peaks-doctor / peaks-issue-fix-orchestrator / etc.) or falls back to self-planned execution (deep-search / WebSearch / Bash / Edit markdown) if no leaf matches, and then asks the user whether to sediment the result.\n\nTriggers: 自然语言描述诉求且无明确 peaks-* skill 选择 / \"帮我处理这个\" / \"我不知道该用哪个\" / \"随便都行\".\n\nNOT for: code-specific work (use /peaks-code) / content-specific work (use /peaks-content) / project health check (use /peaks-doctor) / issue sweep (use /peaks-issue-fix-orchestrator) / SOP authoring (use /peaks-sop)."
+        },
         {
           "name": "peaks-sop",
           "path": "./skills/peaks-sop",
-          "description": "Authoring skill for user-defined SOPs in Peaks. Use when a user wants to create, edit, debug, or register their own gated workflow."
+          "description": "Authoring skill for user-defined SOPs (standard operating procedures) in Peaks. Use when a user wants to create, edit, debug, or register their own gated workflow — ordered phases plus gates that block advancement until conditions are met — by describing it in natural language instead of hand-writing JSON or memorizing CLI commands. DOMAIN-AGNOSTIC: not just software/release flows — equally for content publishing, compliance and approval checklists, data pipelines, onboarding, ops runbooks, or any personal repeatable procedure, wherever \"don''t enter the next stage until X is true\" applies and X is checkable via a file, file content, or a command."
+        },
+        {
+          "name": "peaks-status",
+          "path": "./skills/peaks-status",
+          "description": "Universal status primitive for any in-flight Peaks-Loop workflow (orchestrator-agnostic). Reads the existing CLI primitives (peaks skill presence, peaks session list, peaks project dashboard, peaks request show) and renders a 1-screen status table. Use when the user asks \"where are we\", \"现在到哪了\", \"what's the current state\" for ANY bee (peaks-code, future peaks-research, …). Triggers on \"/peaks-status\", \"现在到哪了\", \"what is the current state\", \"show me the dashboard\". (Replaces peaks-status as a top-level primitive.)"
+        },
+        {
+          "name": "peaks-test",
+          "path": "./skills/peaks-test",
+          "description": "Universal test-runner primitive for any in-flight Peaks-Loop workflow (orchestrator-agnostic). Runs the project's test suite on the current repo and reports results. Use when the user asks \"run the tests\", \"跑一下 test\", \"跑测试\" for ANY bee (peaks-code, future peaks-research, …). Triggers on \"/peaks-test\", \"跑一下 test\", \"跑测试\", \"run the tests\", \"test now\". (Replaces peaks-test as a top-level primitive.)"
+        },
+        {
+          "name": "peaks-txt",
+          "path": "./skills/bee/peaks-txt",
+          "description": "Context and knowledge role for Peaks-Loop (LLM-only internal role; not user-invocable.\nTriggered by peaks-code via `peaks sub-agent dispatch --role txt`.)\nUse when a workflow needs context capsules, role-specific context slices, decision records,\nassumptions, discarded options, staleness checks, lessons, or reusable project memory.",
+          "userInvocable": false
+        },
+        {
+          "name": "peaks-ui",
+          "path": "./skills/bee/peaks-ui",
+          "description": "UI and experience role for Peaks-Loop (LLM-only internal role; not user-invocable.\nTriggered by peaks-code via `peaks sub-agent dispatch --role ui`.)\nUse when a workflow touches UI/UX, interaction design, visual direction, design systems,\nfrontend page behavior, high-fidelity HTML prototypes, or UI regression seeds.",
+          "userInvocable": false
         }
       ]
     }
   ]
-}
+}

package/CHANGELOG.md

@@ -1,5 +1,117 @@
 # Changelog
 
+## 4.1.4 — 2026-10-10 (修掉推送门上的一个假绿；`src/cli/commands` 清空超帽；两条"BLOCKING 却拦不住任何东西"的步骤；以及一项被推迟的边界)
+
+**版本级别**: 未发布区间 `v4.1.3..HEAD` 共 **17 个 commit**（1 feat / 5 fix / 6 refactor / 2 test / 其余 docs+memory）。取 **patch**，依维护者 2026-07-22 的常设规则"默认版本新增采用最小的版本位"。4 个 workspace 包各 +1 patch（internal-runtime 0.0.43→0.0.44、mut 0.1.57→0.1.58、shared 0.0.92→0.0.93、shared-channel 0.0.60→0.0.61），`CLI_VERSION` 与 `RUNTIME_VERSION` 由 `scripts/sync-version.mjs` 同步。**本版不新增命令族**，所以 4.1.3 那条"新增命令应取 minor"的注记不适用。
+
+### 1. 推送门上的一个假绿（1 fix，三轮交付）
+
+**leg 2 的分类器会把"新增了 gated 文件却忘了重生成基线"的改动放过去。** 实测 `6a1938a8` 那次推送：leg 2 跑了 601 个测试，**其中没有一条**是钉"每个 in-scope 文件都在 `gate-baseline.json` 里有 `files[]` 行"的那个守卫——它住在 `tests/unit/standards/`，而分类器只把 `src/<area>` 映射到 `tests/unit/<area>`，**没有任何一条路径通向那里**。守卫直到**下一次**推送（改了 `.husky/` 触发全量）才变红，`0c5fe123` 就是那两次提交需要付的修。
+
+分类器现在是一个**纯模块**（`scripts/test-changed-classify.mjs`），三条规则旧映射表达不了：
+
+- **R1** 基线**内容**动了 ⇒ 跑它的守卫套件（`tests/unit/standards/` + `tests/unit/lint/`），而不是 0 个测试
+- **R2** 任何 `A`/`D`/`R`/`C` ⇒ 跑人口守卫（按 git **status** 判定，不重述 census 的策略目录）
+- **R3** census 的**策略源文件**被改 ⇒ 同样跑（`M src/services/scan/file-size-policy.ts` 会让 44 个 `.md` 突然进 scope）
+
+**只有 `generatedAt` 动了的重生成仍然是惰性的（0 测试）——但现在是建立在一个真命题上。** 旧豁免写的理由是"没有测试读它"，那是**假的**：读者经由 `tests/unit/standards/_file-size-cap-scan.ts` 的 `BASELINE_PATH` 常量抵达它，而 2026-09-23 那次搜索找的是路径**字符串**，看不见常量间接引用。
+
+**第一版实现被 5 路评审否决，而这是本版最有价值的一段记录。** 它把守卫加进**选择集**，于是"没映射到测试 ⇒ 跑全量"那张网永不触发：**新增一个 CI workflow 会一个读 `.github/` 的测试都不跑**（实测有 5 个）。四个来源独立撞上同一缺陷，而 AC5 的验收臂看不见它——**因为那条臂用的正是唯一还能漏下去的形状**（`M README.md`）。修完的形状是：**守卫是映射的加法，不是全量网的替代品**，且那张复现表变成了一组臂。
+
+### 2. `src/cli/commands` 清空超帽（6 refactor）
+
+**30 个超帽文件 → 0**（目录从 300 走到 440 个跟踪文件）。配方是**拆分与压函数必须在同一次交付里完成**——只拆会把 `eslintFindings` 推高（本仓第一批就这样被拒过 +23/+19），一起做则下降。
+
+三个 `src/services` 顶层文件也一并处理（`hooks-settings-service` 1037→300、`auto-compact-orchestrator` 1030→285、`config-service` 1011→253）。
+
+**四个 ceiling 全程只降不升**：
+
+```
+fileSizeOverCap        112 -> 78
+fileSizeExcessLines  30352 -> 22502
+eslintFindings        1951 -> 1760
+eslintErrors           709 ->  590
+```
+
+### 3. 两条"BLOCKING 却拦不住任何东西"的步骤（1 fix）
+
+**由一次真实事故追出**：本会话的编排者跑完 4 个 slice、11 个提交，**从未执行 Step 11 的记忆沉淀**，而契约写着它 BLOCKING。追查后是两条可定位的缺陷：
+
+- **Step 11 没有任何可执行的拒绝点。** `verify-pipeline` 查 QA 与 Gate H；`emit-handoff` 查 **job 账本**；`gate-step-08` 查 job 叙述——**没有一个查 memory**。唯一"可执行的" Step 11 相关物，断言的是 SKILL.md 里那个**标题**存在。
+- **`gate-step-08` 在输入缺失时 fail-open**，并把"我没有能力判断"说成"我判断了，这不像 Job"。实测：整轮**一次 `Next: slice #N of M` 都没出现**。而这个真空本仓的 drift **D-003** 已记过（`JOB_SHAPE_NOT_DECIDED` 自 4.0.0-beta.6 起不再抛），它只是从另一个角度又咬了一次。
+
+修法：`emit-handoff` 增加 `block-no-sediment`（信号取自 `.peaks/memory/index.json`，**peaks 自己的状态，不是裸 mtime**；三值化且 **`unknown` 拒绝**）；`gate-step-08` 三态化，**无决定但有账本 ⇒ 拒绝**。**两半都端到端验过**：把 `job-shape.json` 移开 ⇒ exit 2；让 memory index 不可读 ⇒ exit 1。**这里的 fail-closed 语义是"别再声称一个你没做出的判断"，不是"拦下每一次 Bash 调用"**——该 hook 跑在每个会话的每次 Bash 上。
+
+同时把 5 条反馈记忆提升到强制层（3 条 Layer A 由 CLI 自行生成注册，2 条 Layer B 写成**真的** PreToolUse hook：一条拦会改全局状态的命令，一条拦"把测试运行器管进管道"——后者本会话被犯过两次）。**Layer B 的注册一度只存在于 gitignored 的生成文件里**，所以本版把两条条目加进生成器、**并把它从 475 行压到 299 行**（帽 300）以不抬 ceiling。**`shell` pin 是真正的坑**：照抄旁边那条的约定会让两个 hook 变成非阻断错误从而**静默放行**。
+
+### 4. 一项被推迟的边界（1 fix）
+
+slice 1 当初**刻意推迟**了 git C-quoting：含非 ASCII/控制字节的路径会被加引号，于是匹配不上任何锚定正则。推迟的理由是它先于本版存在、且当时 0 个受影响路径。本版用 `git diff --name-status -z`（NUL 分隔、不加引号不转义）关掉它，`parseNameStatus` 按 status 字母隐含的字段数消费记录。**对照是真的**：同一份 diff 去掉 `-z` 确实带引号，而 HEAD 的解析器逐字返回那个带引号路径。
+
+### 5. 边界取证（2 test）
+
+三项"机制存在但从未端到端跑过"的欠账：`format:check` 在 CI runner 上**确实评过**（不是被跳过）；PATH 上的 `peaks` 是**已安装构建**而非工作树，且**8 个未推送提交新增的 161 个 src 文件全部不在已安装 dist 里而两边都报 4.1.3**——本地 e2e 覆盖**看起来存在而实际为零**；棘轮唯一的联合判定例外 `COUPLED_SIZE_RISE`**确实能开，而且是有条件的**（双向实测）。
+
+审计另外补上了两处此前**没有任何东西能抓到**的行为（`docker rm --force` 的 argv、`docker run` 的 flags），方式是对未驱动路径做**注入式直接调用测试**——评审证明过：五个相同的注册表哈希是**一个维度重复五次**，而它**看不见函数体**。
+
+---
+
+## 4.1.3 — 2026-10-09 (只读 MCP 能力面首次发布：把"只读"做成可证伪的东西；两处"工具在说假话"的修复；三批尺寸债，以及门禁自己被加固)
+
+**版本级别**: 未发布区间 `v4.1.2..HEAD` 共 **20 个 commit**（2 feat / 3 fix / 4 refactor / 2 chore(gate) / 2 merge / 其余 docs+memory）。取 **patch**，依维护者 2026-07-22 的常设规则"默认版本新增采用最小的版本位"。
+
+**但此处必须如实记一笔**：本版**确实新增了命令族**（`peaks mcp serve|install|uninstall`）。4.1.2 那条写的是"取 patch：本版不新增命令"，本版**不适用那句**——取 patch 是常设规则的默认，不是"没有新增命令"。按严格语义化版本，新增用户可见命令应当取 minor。4 个 workspace 包各 +1 patch（shared 0.0.91→0.0.92、internal-runtime 0.0.42→0.0.43、mut 0.1.56→0.1.57、shared-channel 0.0.59→0.0.60），`CLI_VERSION` 与 `RUNTIME_VERSION` 由 `scripts/sync-version.mjs` 同步（`bump-version.mjs` 只管清单，两者都在 tag 之前，否则 publish.yml 的 `gate-cli-version` 会在 `npm publish` 前中止）。
+
+### 1. 只读 MCP 能力面（2 feat）——核心不是"能调用"，而是"只读这件事被证明过"
+
+`peaks mcp serve` 把既有的非 gate 能力以 MCP stdio 暴露给 AI Harness；`peaks mcp install|uninstall` 把它注册进 harness。**CLI 不删**，MCP 是并列的一条调用路径。
+
+**"只读"不是一句声明，是一条可证伪的断言。** 分类键是**完整 argv**（含 flag），不是命令名——13 个命令族全部读写成对存在，有些**默认就是写**，只看命令名会把写当成读。白名单是手写真源（`contracts/readonly-surface.json`）+ 生成物（`contracts/readonly-argv-whitelist.json`），生成物才是运行时读的那个。
+
+证明分三层：(A) 文件系统 + state-store 快照差分；(B) 进程内对 `child_process` / `fetch` / `http(s).request` 的测试替身拦截；(C) CI-only 的无网络只读挂载沙箱。执行面分 L1–L4 四层，其中 L3 是 PreToolUse matcher 覆盖，**MCP 分支 fail-closed**（与 Bash 分支的 fail-open 相反）——这条分支被刻意放在强制链最前面，因为 MCP 工具名既不匹配 Bash matcher 也不是 worktree 工具，放在后面会被直接放行。
+
+**客户端那一跳已实测**：真 Claude Code 2.1.295 上 `claude mcp add … peaks -- <node> <bin/peaks.js> mcp serve` 被原样接受，`claude mcp list` 报 `✔ Connected`，即 harness 真的 spawn 了 server 并完成握手。这是本能力**唯一无法在离线环境推断**的一步，也是这一版敢发出来的理由。
+
+**注意**：`peaks mcp install` 会**写用户的 `~/.claude.json`**（user scope），卸载会扫掉全部已声明 scope。这是本仓第一次发出去会改用户环境的命令。
+
+### 2. 两处"工具在说假话"（2 fix + 1 fix(baseline)）
+
+**`peaks mcp uninstall` 在删不掉时返回 `ok: true` 并断言"no registration was present"。** 实测：注册项仍在（`claude mcp get peaks` 仍 `✔ Connected`），harness 配置前后逐字节相同，而移除命令**超时被杀**。根因是 `runMcpUninstallPlan` 把**任何**失败的移除都归入 `absent`，然后无条件 `ok: true`。安装侧容忍失败的移除是对的（紧接着就要写，旧项在不在无关紧要），卸载侧不成立——移除**就是**那个操作。修法只划一条**不需要读 harness 输出**的界（读它的英文是 vendor-specific，本仓禁止）：`exit 0` → 已移除；`exit ≠ 0` → 它**表了态**（absent，不变）；**超时/未启动 → 它从未给出裁决**（`unknown`，`ok: false`）。`detail` 从此只在所有 scope 都表了态且都没找到时才说"没有注册项"。
+
+**同一分支还漏了信息**：失败信封的 `data` 只带 `{ ide }`，整份 report 被丢掉——而这条分支在本次改动之前**不可达**（卸载恒为 `ok:true`），所以这个信息丢失是本版引入并本版修掉的。R3 场景（一个 scope 移除成功、另一个从未答复）下，`--json` 的消费者现在看得见 `removed`。
+
+**`npx` / `npm` 解析器差一级目录。** `locateNpmCliScript` 在 win32 上从 `process.execPath` 往上找**两级**，而标准 Windows 布局（MSI、zip、nvm-for-windows）都是**一级**。在第 3 个硬编码候选（`C:/Program Files/nodejs`）也不存在的机器上，它找不到 `npm-cli.js` / `npx-cli.js`，**静默回退到裸名 `npx`/`npm`**——正是这个模块被写出来专门要绕开的那个 `.cmd` shim。长期不可见是因为那个硬编码候选恰好命中默认安装与 CI 的 `windows-latest`。
+
+### 3. 门禁自己被加固（2 chore(gate)）
+
+**两条不会失败的门被修成会失败。** `peaks-gate staged`（无参）曾打印 `EMPTY CHANGE SET — NOTHING WAS CHECKED` 却 **exit 0**；`format:check` 与 pre-commit 的范围本就不一致而 CI 根本没跑它。后者接进 CI 时被写成**集合包含**棘轮而非计数棘轮——一个计数看不见**替换**（删一个、加一个，计数不变）。
+
+**单调守卫的第一个、也是唯一一个例外**：`fileSizeOverCap`（文件数）与 `fileSizeExcessLines`（超出行数）各自独立棘轮，而规则是"任一 key 高于基线即拒"。于是把 1125 行拆成 2 份、每份仍 >300 时 `overCap 1→2` 被拒——一个**把超出行数降下来的改动**被挡住。新政策：`overCap` 允许上涨，**仅当**同一次变更中 `excess` 严格下降；双升则拒。
+
+**基线生成器在本版拒绝过两次，两次都是改源码而不是抬 ceiling**：一次 `commentNarrativeLines: 22 → 24`（新模块头注释写了切片名，而 `rid-id` 是 8 个 NARRATIVE_MARKER 之一），一次 `comment narrative: 63 > ceiling 22 (+41)`。这条拒绝路径在本版内**真的被执行过**，不是事后补的说辞。
+
+### 4. 三批尺寸债（4 refactor）——能降 ceiling 的只有 `src/`
+
+`src/cli/commands` 从 10 个最严重的文件拆成 110 个模块（三批），`scripts/` 4 个文件拆成 16 个模块。**四个 ceiling 全部下降，无一上升**：
+
+```
+eslintFindings     2055 -> 1951      fileSizeOverCap      122 -> 112
+eslintErrors        770 ->  709      fileSizeExcessLines 35536 -> 30352
+```
+
+**配方是"拆分与压函数必须在同一次交付里完成"**，这条是血换来的：第一批只拆，`eslintFindings`/`eslintErrors` 被**推高** +23/+19（把一个长函数切成 helper 之后，原函数在压缩前必然仍超 50 行），被拒后第二遍才把 51 个函数压到 0；第二、三批一次做完，分别 −61 和 −43。
+
+**`scripts/**` 与 `tests/**` 是 shadow 人口，不受任何 file-size ceiling 约束**（`gate/legs.mjs` 只 check `partition.gated`）。拆它们**不移动任何 ceiling**——实测前后均为 `117 / 32979`，移动的只有 census 与 shadow 块。它们是被 owner（2026-10-03）刻意排除在 ceiling 之外的，本版如实记录这一点，而不是把"拆了 4 个文件"说成还了 ceiling 的债。
+
+### 5. 未验证（记录而非隐瞒）
+
+- **C 层沙箱从未实跑**（CI-only，本仓无 runner）；`format:check` job 同样**从未在 runner 上跑过**。
+- **L3 端到端未验**：PATH 上的 `peaks` 是已安装构建而非工作树。
+- **S1 政策例外的端到端触发未验**：机制只在纯函数层被测，"允许涨" ≠ "已经涨过"。
+- **MCP 只读证明的白名单覆盖面**：分类键是完整 argv，但白名单是手写枚举；一条新命令若忘记分类会落到默认分支。`_no-mcp-source-import-scan` 守着"服务层不得 import MCP"这条不变量，但**不守**白名单本身的完备性。
+- **`scripts/**` 的债是自愿还的**，没有任何门会因为不还而变红（见 §4）。
+- **发布路径的一处结构性冲突（过程，非产品）**：`git push origin <tag>` 单独推送**永远过不了本仓 pre-push 门**——只推 tag 时 `origin/main...HEAD` 为空，而门在空变更集上按设计拒绝（"nothing to compare ≠ compared and clean"）。也就是说**每一次发布都必须靠一次 `--no-verify`**，恰是本仓钩子注释里警告过的形状。本版未修（属门机器，须单独立项）。
+
 ## 4.1.2 — 2026-10-08 (资产真源落地: 升级不再静默冻结入口; codegraph 换上 1.6.2 的包模型, 顺带照出一条从未响过的失败路径)
 
 **版本级别**: 未发布区间 `v4.1.1..HEAD` 共 **14 个 commit**（6 feat / 3 fix / 1 refactor / 1 test / 3 docs）。取 **patch**：本版不新增命令，不改变任何既有命令的输入输出形状 —— 两件主要工作都是"让已经承诺的行为真的发生"。4 个 workspace 包各 +1 patch（shared 0.0.90→0.0.91、internal-runtime 0.0.41→0.0.42、mut 0.1.55→0.1.56、shared-channel 0.0.58→0.0.59），与 `scripts/bump-version.mjs` 的 lockstep 规则（每个可发布包跟随根版本 +1 patch）一致；实测子包自身的 `version` 字段**不进** `pnpm-lock.yaml`（workspace 依赖在 lock 里是 `link:` 形态、importer 条目为 `packages/peaks-loop-shared: {}`，无版本行），故本版**不需要**改 lockfile。

package/README-en.md

@@ -155,7 +155,7 @@ Every lane opens with **one slash command**.
 
 | | |
 | --- | --- |
-| **Latest** | [![npm](https://img.shields.io/npm/v/peaks-loop?style=for-the-badge&logo=npm&logoColor=white&color=cb3837)](https://www.npmjs.com/package/peaks-loop) — 4.1.2 (2026-10-08) |
+| **Latest** | [![npm](https://img.shields.io/npm/v/peaks-loop?style=for-the-badge&logo=npm&logoColor=white&color=cb3837)](https://www.npmjs.com/package/peaks-loop) — 4.1.4 (2026-10-10) |
 | **Domains** | Code (`peaks-code`) · Content (`peaks-content`) · Project health (`peaks-doctor`) · Issue sweep (`peaks-issue-fix-orchestrator`) · Custom SOP (`peaks-sop`) · Cross-domain primitives (`peaks-solo` dispatcher · `peaks-resume` · `peaks-status` · `peaks-test` · `peaks-slice-decompose`) |
 | **Sediment pool** | `~/.peaks/` local pool · twice-clean runs auto-promote to a bee · broken runs come back for you to redefine · the bee grows with your taste |
 | **Test suite** | 285+ cases · 4 packages (peaks-loop / peaks-loop-mut / peaks-loop-shared-channel / peaks-loop-shared) · **0 timeouts** · 14 BDD caller-binding edge cases |

package/README.md

@@ -175,7 +175,7 @@ npm i -g peaks-loop
 
 | | |
 | --- | --- |
-| **最新版本** | [![npm](https://img.shields.io/npm/v/peaks-loop?style=for-the-badge&logo=npm&logoColor=white&color=cb3837)](https://www.npmjs.com/package/peaks-loop) — 4.1.2(2026-10-08) |
+| **最新版本** | [![npm](https://img.shields.io/npm/v/peaks-loop?style=for-the-badge&logo=npm&logoColor=white&color=cb3837)](https://www.npmjs.com/package/peaks-loop) — 4.1.4(2026-10-10) |
 | **覆盖域** | 代码(`peaks-code`) · 内容(`peaks-content`) · 项目健康(`peaks-doctor`) · 批量修 issue(`peaks-issue-fix-orchestrator`) · 自定义 SOP(`peaks-sop`) · 通用原语(`peaks-solo` 分诊 / `peaks-resume` 续 / `peaks-status` 看 / `peaks-test` 测 / `peaks-slice-decompose` 切片) |
 | **沉淀池** | `~/.peaks/` 本地池 · 跑两次自动晋升成 bee · 跑翻车让你重定义 · bee 跟着你的口味长 |
 | **测试套件** | 1096 cases · 4 packages (peaks-loop 1015 / runtime 39 / mut 22 / shared-channel 20) · **CI 首次全绿**(ubuntu + windows) · 14 BDD caller-binding coverage |

package/contracts/readonly-argv-whitelist.json

@@ -0,0 +1,211 @@
+{
+  "schemaVersion": 1,
+  "source": "contracts/readonly-surface.json",
+  "readOnlyDefinition": "readOnly = no persistent-state write AND no network AND no LLM billing AND no CLI->external process spawn (output constancy over time is deliberately NOT part of it)",
+  "entries": [
+    {
+      "id": "skill-presence",
+      "tool": "peaks_status",
+      "commandPath": [
+        "skill",
+        "presence"
+      ],
+      "argv": [
+        {
+          "kind": "literal",
+          "value": "skill"
+        },
+        {
+          "kind": "literal",
+          "value": "presence"
+        },
+        {
+          "kind": "literal",
+          "value": "--json"
+        }
+      ],
+      "params": {},
+      "introspection": {
+        "optionTokens": [
+          "--json"
+        ],
+        "positionalCount": 0
+      }
+    },
+    {
+      "id": "session-list",
+      "tool": "peaks_status",
+      "commandPath": [
+        "session",
+        "list"
+      ],
+      "argv": [
+        {
+          "kind": "literal",
+          "value": "session"
+        },
+        {
+          "kind": "literal",
+          "value": "list"
+        },
+        {
+          "kind": "literal",
+          "value": "--json"
+        }
+      ],
+      "params": {},
+      "introspection": {
+        "optionTokens": [
+          "--json"
+        ],
+        "positionalCount": 0
+      }
+    },
+    {
+      "id": "request-show",
+      "tool": "peaks_status",
+      "commandPath": [
+        "request",
+        "show"
+      ],
+      "argv": [
+        {
+          "kind": "literal",
+          "value": "request"
+        },
+        {
+          "kind": "literal",
+          "value": "show"
+        },
+        {
+          "kind": "param",
+          "name": "rid"
+        },
+        {
+          "kind": "literal",
+          "value": "--role"
+        },
+        {
+          "kind": "param",
+          "name": "role"
+        },
+        {
+          "kind": "literal",
+          "value": "--json"
+        },
+        {
+          "kind": "literal",
+          "value": "--project"
+        },
+        {
+          "kind": "param",
+          "name": "project"
+        }
+      ],
+      "params": {
+        "rid": {
+          "type": "slug",
+          "pattern": "^[a-z0-9][a-z0-9-]*$",
+          "binding": {
+            "kind": "positional",
+            "token": "request-id",
+            "required": true
+          },
+          "constraintSource": "handwritten"
+        },
+        "role": {
+          "type": "enum",
+          "values": [
+            "prd",
+            "ui",
+            "rd",
+            "qa",
+            "sc"
+          ],
+          "binding": {
+            "kind": "option",
+            "token": "--role",
+            "required": true
+          },
+          "constraintSource": "handwritten"
+        },
+        "project": {
+          "type": "path",
+          "binding": {
+            "kind": "option",
+            "token": "--project",
+            "required": true
+          },
+          "constraintSource": "handwritten"
+        }
+      },
+      "introspection": {
+        "optionTokens": [
+          "--role",
+          "--json",
+          "--project"
+        ],
+        "positionalCount": 1
+      }
+    },
+    {
+      "id": "memory-search",
+      "tool": "peaks_memory_search",
+      "commandPath": [
+        "memory",
+        "search"
+      ],
+      "argv": [
+        {
+          "kind": "literal",
+          "value": "memory"
+        },
+        {
+          "kind": "literal",
+          "value": "search"
+        },
+        {
+          "kind": "param",
+          "name": "query"
+        },
+        {
+          "kind": "literal",
+          "value": "--limit"
+        },
+        {
+          "kind": "param",
+          "name": "limit"
+        }
+      ],
+      "params": {
+        "query": {
+          "type": "token",
+          "binding": {
+            "kind": "positional",
+            "token": "query",
+            "required": true
+          },
+          "constraintSource": "handwritten"
+        },
+        "limit": {
+          "type": "integer",
+          "min": 1,
+          "max": 50,
+          "default": 6,
+          "binding": {
+            "kind": "option",
+            "token": "--limit",
+            "required": false
+          },
+          "constraintSource": "handwritten"
+        }
+      },
+      "introspection": {
+        "optionTokens": [
+          "--limit"
+        ],
+        "positionalCount": 1
+      }
+    }
+  ]
+}

package/dist/cli/commands/asset-command-shared.d.ts

@@ -0,0 +1,12 @@
+import { openStateDb } from '../../services/skillhub/sqlite-store.js';
+import { CrystallizationService, type CrystallizationTrigger } from '../../services/crystallization/index.js';
+export declare function collectRepeatable(value: string, previous: string[]): string[];
+export declare const DISPOSE_MODES: readonly ["trace_only", "retain", "destroy"];
+export type DisposeMode = (typeof DISPOSE_MODES)[number];
+export declare function parseTriggerFlag(raw: string): CrystallizationTrigger | null;
+/** `--project`, else the nearest project root above cwd, else cwd. */
+export declare function resolveAssetProjectRoot(project: string | undefined): string;
+/** Ensure `<projectRoot>/.peaks/` exists and open its `state.db`. */
+export declare function openAssetDb(projectRoot: string): ReturnType<typeof openStateDb>;
+/** The CrystallizationService wiring every asset verb repeats, built once. */
+export declare function createCrystallizationService(db: ReturnType<typeof openStateDb>): CrystallizationService;