peaks-loop 4.1.1 → 4.1.2

package/CHANGELOG.md

@@ -1,5 +1,55 @@
 # Changelog
 
+## 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。
+
+### 1. 资产真源：升级不再静默冻结入口（4 feat + 1 refactor + 1 test）
+
+原先三个安装器（`installBundledSkills` / `installBundledAgents` / `installBundledOutputStyles`）把归属判断写成 `resolve(marker.sourcePath) === resolve(sourcePath)`，比对的原件是**装它的那个版本**的包路径。实测这条路径里带 node 版本号（`…\nvm\v24.21.0\node_modules\…`），于是这个判断本身就是一个"版本内有效"的事实：一次 node 升级之后的第一次 `npm i -g peaks-loop@latest`，此后每一次运行都会**跳过**该条目 —— 既不更新，也不报错。而唯一的修复路径 `reconcileJunctions` postinstall 从不传入，其余所有情况都落到一个**无声的** `skipped`：升级既不修旧链，也不说没修。本机实测：8 个 IDE 目录 × 44 个 `peaks-*` 条目，全部解析进同一个包路径。
+
+现在三族都走真源（skills 原本已走，agents / output-styles 在 `4e1bd85a` 补齐）：`~/.peaks/{skills,agents,output-styles}/<name>` 放真副本，IDE 侧入口指向它 —— 升级变成**重写一份副本，而不是重指 176 条链**。归属由 `.peaks-managed` 边车 + 两侧 `realpath` 决定，**绝不用字符串相等**（Windows junction 的 `readlinkSync` 拼写不保证，这正是旧安装器里那处脆弱点，新模块不许抄它）；旧的 JSON 边车按两条臂之一收养 —— 记录的包路径已不再解析（更早一次安装），或那个路径**就是**正在安装的这个包（原地升级）；记录的路径解析到**另一个活的包**则原样不动 —— 那是第二份安装，不是陈旧的。
+
+Windows 不给**文件**符号链接（没有开发者模式或管理员时），而 skills 用的 junction 从不需要这个权限。宿主拒绝时写实体副本（保留"每次运行都保持最新"的语义），并在返回值与 stderr 上说明这次拒绝 —— `copied` 与 `skipped` 现在各自说得出自己是哪一个；一次不带理由的降级与一次成功无法区分。
+
+`dbf91c25` 把真源根从 `~/.agents` 改成 `~/.peaks`（owner 在本次 job 内改的决定）：`~/.agents` 是**共享命名空间**（`npx skills`、agentrecall、agentlink 都往那里写），而 `~/.peaks` 是 peaks-loop 自己的家且**已在使用**（实测 `~/.peaks/agents/` 存在并持有 `ecc`）；共享约定唯一的好处（给原生读它的工具省一条软链）本次**没有任何测量**证明过。环境变量复用 `PEAKS_HOME`（`peaksHome()`，`src/services/sop/sop-paths.ts:29`）而非新造一个 —— 一个目录两个旋钮就是一对可以互相矛盾的值。
+
+`e08dc4af` 补上最后一块：安装器此前**只会加**。把某个 skill 从包里删掉，它的真源副本、各 IDE 目录里的链、`.peaks-managed` 边车会永远留在用户机器上 —— 这与"更新"的含义不符。新的 `canonical-store-prune.mjs` 删真源条目 / IDE 链 / 边车，凡是 `isManagedEntry` **证明不了**是自己的一律保留；顺带把 `ensureCanonicalCopy` 原先无条件的 `rmSync` 换成 `action: 'unmanaged'`（→ `skipped`）—— 那正是根目录搬迁时记下的隐患：`~/.peaks/agents/` 真的有一个 peaks-loop 自己建的 69 条目 `ecc/`，一个同名捆绑资产本会把它静默删掉。**负控是本片重点**：用户自建的真目录 `peaks-gamma`（无边车）同时放进真源与 IDE 目录，`pruned: []`，两者逐字节存活；把 `isManagedEntry` 强制成 `return true` 则三臂转红。端到端实测（一次性 HOME / USERPROFILE / PEAKS_HOME）：装 alpha 与 beta、从包里去掉 alpha、重跑 —— `pruned: ["skills/peaks-alpha", "…\.claude\skills/peaks-alpha"]`，四件产物全消失，beta 未动。
+
+**发布白名单是本版反复咬人的一处。** `package.json#files` 是 npm 发布白名单，而仓库里**没有任何东西读它** —— 一个不在里面的模块会让每一个已发布包的用户在 `ERR_MODULE_NOT_FOUND` 上崩掉，而整个测试套件保持全绿。本分支三次踩到（`canonical-store.mjs`、`canonical-store-prune.mjs`、`canonical-store-link.mjs`）：slice 1 加文件时无人导入，`npm pack --dry-run` 给出 `canonical-store shipped: false`，直到 slice 2 接上 import 才暴露。`87d2b86b` 把一条"枚举两个模块名"的守卫（第三个模块出现就会放行）换成 `install-skills-published-modules.test.ts` —— 从安装器自己的相对 import 里**读出规则**，没有表要维护；解析器先断言解析结果非空，再用同一份解析器跑 fixture 文本，于是"解析器退化成空转"会被它自己的读法抓住，而不是被它恰好指向的文件抓住。
+
+**本版未测（记录而非隐瞒）**：trae / codex / cursor 是否跟随文件符号链接（只探过 Claude Code 2.1.292）；以及一次自然发生的、无开发者模式下的 EPERM。**记录未修**：手工删掉一条链会让对应 IDE 边车变成孤儿，prune 不扫这种情况（有意的范围限制）；nvm 用户保留旧 node 版本时那条包路径仍可解析，条目会两条收养臂都不落，现在报在 stderr 上（此前无声）。
+
+### 2. codegraph 升到 1.6.2：包模型换了骨，配置轴反了向（2 feat + 1 fix）
+
+`0.7.10` → `1.6.2` 的升级**不是**表面工作。在 Node v24.21.0（ABI 137）上 `better-sqlite3@11.10.0` 没有预编译二进制，0.7.10 的原生后端在本机根本建不起来，`prebuild-install` 落到 `node-gyp`（需要 Visual Studio），于是退到 `node-sqlite3-wasm` —— 而它打不开 WAL 模式的数据库（带对照实测：DELETE 模式打开、WAL 模式报 `unable to open database file`）。也就是说 codegraph 在这台机器上**已经死了好几天**，每一次 RD 派发都在静默降级。1.6.2 是自包含的，直接用 Node 内建的 `node:sqlite`，完整 WAL。
+
+**包模型**：1.6.2 的主包 `dist/` 下**没有可执行 JavaScript**（只有 `.d.ts`）加两个 shim，代码在一个自带 `node.exe` 的平台子包里。于是 `dist/types.js`、`dist/extraction/grammars.js`、`dist/bin/codegraph.js` 全是 MODULE_NOT_FOUND —— 正是 peaks-loop 全部的 spawn 目标。新的 `codegraph-upstream-layout.ts` 是这四个触点的**唯一**定位器：先探 `<平台包>/lib/dist/bin/codegraph.js`（1.6.x），再退回 `<主包>/dist/...`（0.7.x）；必须经 `createRequire(<主包>/package.json)` 解析，因为平台包只链在主包自己的 `node_modules/` 里。
+
+**配置轴是一个陷阱**：1.6.2 不只是把配置文件从 `.codegraph/config.json` 搬到 `<root>/codegraph.json`，它把 `include` 的**语义反了**。0.7.x 里 `include` 是白名单；1.6.x 里它的意思是"即使被 .gitignore 丢掉也强行纳入索引"，准入模型是 `force-include`。只换路径的改法会把**每一个**受支持的 tracked 文件报成缺口 —— 一个看起来像绿的、方向相反的失败。新的 `codegraph-project-config.ts` 通过探测上游同时定出**源**与**模型**，两条臂都对着真实的 0.7.10 与 1.6.2 安装测过。
+
+两个 reconciler 的处置都写明而不是暗示：`codegraph-include-reconciler.ts` **删除** —— 它的前提是上游那份 32 条默认模板（1.6.2 已无），它的动作是往 `include` 追加 78 条 `**/*.ext`，在 1.6.x 下会把 gitignore 掉的源码**强行塞进**索引；只重定向读会留下这条写路径仍是活的，那是更坏的结果。`codegraph-exclude-reconciler.ts` **保留、但把范围收窄**到项目自撰的 `exclude`，读写两端都搬到真实源。**顺带修掉一条活的缺陷**：exclude reconciler 原先用 `include` 做预过滤，而 1.6.x 下 `include` 什么都不准入，于是这道闸**从来不会触发** —— 在那种组合存在多久，它就无声了多久。
+
+`e60948bf` 明确**推迟**验收判据 1（`peaks codegraph status` 在 1.6.2 下退出 76，因为完整性轴读 `.codegraph/config.json`，那是 1.6.2 从不写的文件；在**新初始化的真实 git 仓库**上复现：`init` 退出 0，`status` 退出 76 并报 `ENOENT`），`c61bf331` 把它关掉：现在退出 0，且该轴是**真的被求值**而不是被跳过 —— 一个全新的 1.6.2 git 仓库上 `--peaks-json` 给出 `indexIntegrityVerdict: "clean"`、`admissionModel: "force-include"`、`trackedSourceCount: 2`、`admittedTrackedCount: 2`、`indexedFileCount: 2`、`gap: false`、`includeGap: []`、`deadRows: []`，这些数字与那个仓库里的两个文件相符，是量出来的而不是默认值。
+
+**一条因为上游而非并发而闪的臂**：1.6.2 自己会在约 **1.3%** 的 `init` 调用上以 `0xC0000005` 中止进程，而且是**串行**的 —— 一个只做单次 spawn、不用 vitest 的最小工装实测 458 次里 6 次中止，stdout 每次都停在同一字节，那里 `extraction/index.js` 正在建一个 8 线程的 `ParseWorkerPool`；`status`（该臂真正的主语）从不中止（0/80）。上游的 `--liftoff-only` 启动器形态修不了它（1/318，Fisher p≈0.13），所以**不许**在生产调用里粉饰。修复只落在测试里：**只**重试 setup 那次 spawn、只认那一个退出码、上限三次、每次换新项目目录；`status` 永远只 spawn 一次；每条漂移断言逐字节未动；另有一条对照臂钉住"只有一个退出码可重试"。残余 ≈ 2.2e-6 每次运行。**仍然敞开并记录在案**：生产有同样的 ~1.3% `init` 暴露面（每一个消费者的 `peaks codegraph init` 都会以那个频率中止），真正的修复属于 `src/services/codegraph/`，本片被划在范围之外。
+
+**失败原因进入 dispatch（`33fdefdf`）**：RD 派发块读的是 `preflight.available ? preflight.block : null`，于是 codegraph 一旦失败，preflight 的 `note`（上游原因的唯一载体）就被丢掉，提示词退回一句常量"codegraph unavailable — proceeding on project-scan only"。失败分支因此渲染出一段**读起来与正常状态一模一样**的块，每个 dispatch 记录里，坏索引与健康索引无法区分 —— codegraph 在这台机器上坏了这么久没被注意到，就是这么来的：上游一直在说 `Failed to index: unable to open database file`，而派发路径上没有任何东西复述它。新的 `codegraph-unavailable-block.ts` 负责渲染原因，退回常量改成"没拿到原因"而不是暗示"没有原因"；手臂同时判别**有**与**无**（一条断言该块**不**包含裸露的上游行），所以"渲染了某个 note"不能满足它们。修复前把四个源文件回退到 HEAD、只留新模块，观察到的是一次断言失败而非加载错误：6 failed / 4 passed。
+
+### 3. 两次"新文件对门禁不可见"（2 fix）
+
+`.husky/` 的 census 腿走的是 `git ls-files`，所以新文件在未 track 时**门禁看不见** —— 本分支两次踩到（`f8073e1f` 对 slice 1 的四个新文件，`b88c4056` 对 tripwire 的三个）。两次都发生在 RD 报告与全量套件都跑了、都报绿的状态下；是 commit 让文件可见，下一次运行就有三个失败。第二次发生在这条教训**已经写进** `sediment-backlog.md` 一小时之后，所以它被记成"必须改的做法"而不是一条事实：一片的验收运行必须在文件已提交的状态下取，或者那次运行必须自己声明是未 track 时取的。`b88c4056` 用 `node .husky/peaks-gate-baseline.mjs` 重生成基线（该生成器只在有人要求抬高上限时拒绝）。
+
+`f8073e1f` 还含一行不显眼的配置：`config/eslint/tsconfig.lint.json` 加上 `../../scripts/canonical-store.mjs`。这不是装饰 —— `.mjs` 会被同名的 `.d.mts` 在 TypeScript 的扩展名优先级组 `[.mts, .d.mts, .mjs]` 里遮蔽，`include` glob 于是**静默丢掉**那个 `.mjs`；`.js` 被 `.d.ts` 遮蔽有豁免，`.mjs` 没有。
+
+### 4. 文档与记忆（3 docs）
+
+`2a70a651` 补上 `.peaks/docs/canonical-store.md`（真源模型、升级会发生什么、怎么验证与回退，含 4.1.1 升级 runbook）—— 一个跨四个 slice 落地的机制此前没有一页描述它，而它引入的两条行为是用户会**不被告知**就遇上的；README 加上短版与指针。`backlog.md` §2.56 记录缺陷：边车用字符串比较安装版本的包路径来判定归属，那是一条带 node 版本号的路径，所以这个判断是"版本内有效"的事实。页面里每一条行为断言都带代码引用，共 17 处，逐条对着它点名的行核过。`594be46f` 沉淀三条教训（后端被换掉之后要查能力而不是查标签；census 守卫看不见未 track 的文件，所以 pre-commit 绿不是绿；不带理由的降级与成功无法区分），索引到 448 files / 106 lessons。`17c7e2a8` 沉淀"守卫点了规则的名、却只查了名单"这一次：规则读取型守卫需要两条防御 —— 先断言解析非空（否则"什么都没找到"会以"对零个元素循环"的形式通过），以及把同一份解析器喂给 fixture 文本。
+
+### 5. 本版验证
+
+`tsc --noEmit -p tsconfig.json` 退出 0；`pnpm build` 退出 0；`pnpm test:unit` 退出 0 —— **406 files / 4238 passed / 3 skipped / 0 failed**（与改动前逐字相同）；版本 parity `shared-dist`（`OK (via import) CLI_VERSION=4.1.2`）与 `runtime-src`（`OK (via extract) RUNTIME_VERSION=4.1.2`）双双退出 0；`peaks changeset check --project . --json` 返回 `ok: true`（`state: staged-empty`），`.changeset/` 仍**只有** `config.json`；`peaks baseline diff --project . --json` 退出 0（15 行）；**`peaks baseline audit --project . --json` verdict 为 `consistent`**（15/15 journey，crossCheck `guardVsAudit: agree`，`findings: []`）。README 两版的**版本徽章行**更新到 `4.1.2(2026-10-08)` / `4.1.2 (2026-10-08)`，而 `README.md:107` 正文那句"从 4.1.1 升级时会发生什么"是**有意保留的历史陈述，未改动**。
+
 ## 4.1.1 — 2026-10-05 (一次"闸自己坏了整整一个版本"、注释债第一次进棘轮、以及五个从真实使用里捞出来的缺陷)
 
 **版本级别**: 未发布区间 `v4.1.0..HEAD` 共 **14 个 commit**（6 fix / 4 feat / 1 test / 1 refactor / 1 docs / 1 chore）。**取 patch，而不是按 4.1.0 自己写下的判据取 minor** —— 这条判据不是被推翻，而是被有意收窄：本版新增的两条命令（`peaks comments audit` / `peaks comments prune`）是**仓库自己的维护表面**，只读或只动本仓注释，不改变任何既有命令的输入输出，也不要求下游做任何事；对外承诺的内容全是修复（其中一条是门禁崩溃）。`^4.1.0` 的下游直接匹配本版。4 个 workspace 包各 +1 patch（internal-runtime 0.0.40→0.0.41、mut 0.1.54→0.1.55、shared 0.0.89→0.0.90、shared-channel 0.0.57→0.0.58），顺带把"本地 manifest 比 registry 新"（mut 的 0.1.54 从未发布）这个坑一次清掉：`scripts/release-pack.mjs` 按拓扑序把 5 个包在同一次 CI 运行里一起发出去，`pnpm pack` 把 `workspace:*` 重写成精确 pin，实测 tarball 内 `CLI_VERSION` 为 4.1.1。

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.1 (2026-10-05) |
+| **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) |
 | **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 |
@@ -292,10 +292,10 @@ It changes, but **the gates hold**. Audit fails = nothing ships. QA fails = noth
 
 If you maintain a project that depends on `peaks-loop` (or that runs `npm install peaks-loop` as part of CI / contributor onboarding), three behaviors are worth pinning in your head:
 
-- **`codegraph` is a transitive dependency.** `peaks-loop` pins `@colbymchenry/codegraph@0.7.10` in its `dependencies`, so `npm install` / `pnpm install` will pull it automatically. The CLI command group `peaks codegraph …` (status / init / index / query / files / context / affected) is shipped inside `dist/services/codegraph/`. No extra install step required.
+- **`codegraph` is a transitive dependency.** `peaks-loop` pins `@colbymchenry/codegraph@1.6.2` in its `dependencies`, so `npm install` / `pnpm install` will pull it automatically. The CLI command group `peaks codegraph …` (status / init / index / query / files / context / affected) is shipped inside `dist/services/codegraph/`. No extra install step required.
 - **`.codegraph/` directory ownership is shared.** Tools like aider, cody, and similar agents also create a top-level `.codegraph/`. `peaks codegraph init` will refuse to overwrite a foreign schema and exits with code 73 + a `CODEGRAPH_INIT_CONFLICT` envelope. If your project already has a `.codegraph/` from another tool, move / rename it (or remove it if you no longer need it) before running `peaks codegraph init`.
 - **Session binding lives under `.peaks/_runtime/<sessionId>/`.** Codegraph orchestration context (and other per-session evidence) is written there by RD / QA slices. Add `.peaks/_runtime/` to your project's `.gitignore` to avoid committing local session state. A missing / unbound session produces a graceful skip-with-warning, never a crash.
-- **Doctor fallback for yarn-pnp / pnpm-strict.** `peaks doctor` falls back to a filesystem walk when `require.resolve('@colbymchenry/codegraph/package.json')` throws, so downstream installs under strict resolution modes still get a green check (or a `severity: 'warning'` if the version drifted from the pinned `0.7.10`).
+- **Doctor fallback for yarn-pnp / pnpm-strict.** `peaks doctor` falls back to a filesystem walk when `require.resolve('@colbymchenry/codegraph/package.json')` throws, so downstream installs under strict resolution modes still get a green check (or a `severity: 'warning'` if the version drifted from the pinned `1.6.2`).
 - **Tarball size / verify.** Each release ships the codegraph service under `dist/services/codegraph/`. Per-release verification lives at `scripts/verify-codegraph-tarball.mjs` (run `node scripts/verify-codegraph-tarball.mjs` locally before tagging a release). Exit 0 means the whitelist is intact; exit 1 means the tarball is missing the codegraph service files.
 
 Install snippet (typical consumer):
@@ -315,7 +315,7 @@ npx peaks doctor --project .
 Three common pitfalls:
 
 1. **`peaks codegraph init` exits 73** — your project has a pre-existing `.codegraph/` from another tool. Move it out of the way (or remove it), then re-run.
-2. **`peaks doctor` warns about codegraph version drift** — your lockfile resolved a different `@colbymchenry/codegraph` version than the pinned `0.7.10`. Pin to `0.7.10` in your lockfile; the warning does not flip the doctor exit code.
+2. **`peaks doctor` warns about codegraph version drift** — your lockfile resolved a different `@colbymchenry/codegraph` version than the pinned `1.6.2`. Pin to `1.6.2` in your lockfile; the warning does not flip the doctor exit code.
 3. **Session-bound artifacts under `.peaks/_runtime/` are noisy in `git status`** — add the path to your project's `.gitignore`. The `peaks-loop` repo already does this; consumers should mirror the rule.
 
 ---

package/README.md

@@ -88,6 +88,27 @@ npm i -g peaks-loop
 
 ---
 
+## 装上以后，文件放在哪
+
+`npm i -g` 之后，三类资产（**skills / agents / output-styles**）的**实体只存一份**，放在你自己 home 下的
+`~/.peaks/{skills,agents,output-styles}`；每个 IDE 目录里（`~/.claude/…`、`~/.trae/…` 等）的条目都是**指向它的链接**
+（目录用 junction，单个 `.md` 文件用符号链接）。所以升级 `peaks-loop` 时链接目标不变、不需要重建，也不会因为
+包路径（里面嵌着 node 版本号）变化而静默断裂。
+
+两件会直接影响你的事：
+
+- **受管入口会在升级时被覆盖。** 由 peaks-loop 装进去的入口（比如 `~/.claude/agents/karpathy-reviewer.md`）旁边有一份
+  `.peaks-managed` 边车标记归属，升级时内容会被更新。**想换成你自己的版本，删掉那份额边车即可** —— 没有标记的入口
+  一律视为你自己建的，**永不被替换、也永不被删除**。
+- **有些 Windows 机器上会退化成实体副本。** 没有开发者模式、也不是管理员时，建不出**文件**符号链接（目录用的 junction
+  不受影响），安装器会写实体副本并在 stderr 明说 `installed as REAL COPIES because this host refused a symlink`。
+  内容照样跟着升级走，只是不再与真源共享同一份。
+
+真源根可用环境变量 `PEAKS_HOME` 重定向。完整的模型、从 4.1.1 升级时会发生什么、怎么验证与回退 →
+[`.peaks/docs/canonical-store.md`](./.peaks/docs/canonical-store.md)。
+
+---
+
 ## 它能为你做什么
 
 代码、内容、项目健康、issue 修复、自定义工作流 —— **4.x 已经覆盖五条域**,每条域都有专门编排器,按"门禁不通过就停"的纪律一条一条跑。
@@ -154,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.1(2026-10-05) |
+| **最新版本** | [![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) |
 | **覆盖域** | 代码(`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 |
@@ -292,10 +313,10 @@ winget install Python.Python.3.12
 
 如果你的项目依赖 `peaks-loop`(或者把 `npm install peaks-loop` 写进 CI / 协作者 onboarding),有三件事需要先记清:
 
-- **`codegraph` 是传递依赖。** `peaks-loop` 在 `dependencies` 里硬钉 `@colbymchenry/codegraph@0.7.10`,所以 `npm install` / `pnpm install` 会自动拉取。CLI 命令组 `peaks codegraph …`(status / init / index / query / files / context / affected)打包在 `dist/services/codegraph/`,无需额外安装步骤。
+- **`codegraph` 是传递依赖。** `peaks-loop` 在 `dependencies` 里硬钉 `@colbymchenry/codegraph@1.6.2`,所以 `npm install` / `pnpm install` 会自动拉取。CLI 命令组 `peaks codegraph …`(status / init / index / query / files / context / affected)打包在 `dist/services/codegraph/`,无需额外安装步骤。
 - **`.codegraph/` 目录归属是共享的。** aider / cody 等类似工具也会在项目根创建 `.codegraph/`。`peaks codegraph init` 拒绝覆盖外源 schema,以 exit code 73 + `CODEGRAPH_INIT_CONFLICT` 凭据退出。如果你的项目里已经有其他工具建的 `.codegraph/`,跑 `peaks codegraph init` 之前先移走 / 改名(或确认不再需要后删除)。
 - **session 绑定落在 `.peaks/_runtime/<sessionId>/`。** codegraph 编排上下文(以及其他 session 级证据)由 RD / QA 切片写入。把 `.peaks/_runtime/` 加进项目的 `.gitignore`,避免误提交本地 session 状态。session 缺失 / 未绑定时优雅降级为「跳过 + 警告」,绝不 crash。
-- **yarn-pnp / pnpm-strict 的 doctor 兜底。** `peaks doctor` 在 `require.resolve('@colbymchenry/codegraph/package.json')` 抛错时回退到文件系统遍历,因此严格解析模式下的下游安装也能拿到绿色 check(若版本偏离钉死的 `0.7.10` 则降级为 `severity: 'warning'`)。
+- **yarn-pnp / pnpm-strict 的 doctor 兜底。** `peaks doctor` 在 `require.resolve('@colbymchenry/codegraph/package.json')` 抛错时回退到文件系统遍历,因此严格解析模式下的下游安装也能拿到绿色 check(若版本偏离钉死的 `1.6.2` 则降级为 `severity: 'warning'`)。
 - **tarball 大小 / 自检。** 每次发布都把 codegraph service 打进 `dist/services/codegraph/`。逐版本自检脚本见 `scripts/verify-codegraph-tarball.mjs`(发布前本地跑 `node scripts/verify-codegraph-tarball.mjs`)。exit 0 表示 whitelist 完好,exit 1 表示 tarball 漏了 codegraph service 文件。
 
 典型下游安装片段:
@@ -314,7 +335,7 @@ npx peaks doctor --project .
 三个常见坑:
 
 1. **`peaks codegraph init` 退出码 73** —— 项目里已有外源 `.codegraph/`(aider / cody 等)。把它挪开(或删掉)再重跑。
-2. **`peaks doctor` 报 codegraph 版本漂移** —— 你的 lockfile 解到了一个跟钉死 `0.7.10` 不同的版本。在 lockfile 里钉到 `0.7.10`;这条 warning 不会让 doctor 退出码翻红。
+2. **`peaks doctor` 报 codegraph 版本漂移** —— 你的 lockfile 解到了一个跟钉死 `1.6.2` 不同的版本。在 lockfile 里钉到 `1.6.2`;这条 warning 不会让 doctor 退出码翻红。
 3. **`.peaks/_runtime/` 下的 session 产物在 `git status` 里嘈杂** —— 把这条路径加进项目的 `.gitignore`。`peaks-loop` 仓库已经这样做;下游消费者应当镜像这条规则。
 
 ---

package/bin/node-floor.mjs

@@ -0,0 +1,59 @@
+/**
+ * The Node version floor, checked by `bin/peaks.js` before it imports the app.
+ *
+ * WHY THIS FILE IS NEXT TO THE SHIM AND NOT IN `src/`. Every store now imports
+ * `node:sqlite`, so on a Node that predates that builtin the failure is raised while
+ * resolving the import graph — `ERR_UNKNOWN_BUILTIN_MODULE`, before one line of our code
+ * runs. A check inside the CLI would be compiled into the very graph that cannot load.
+ * `bin/peaks.js` is already the place that translates pre-app Node failures (a stale
+ * `dist/`) into sentences, so the floor lives with it.
+ *
+ * WHY 24. `node:sqlite` exists in 22.5+ but not as something this code can import
+ * unconditionally; 24 is the line measured on the developer host that started this change,
+ * where `import { DatabaseSync } from 'node:sqlite'` works with no flag and no warning.
+ * The number is asserted against `package.json#engines.node` by
+ * `tests/unit/cli/node-floor.test.ts`, because two spellings of one boundary is this
+ * repository's oldest defect class.
+ *
+ * WHAT IT REFUSES TO GUESS. An empty version string is not evidence of an old Node, so it
+ * does not block anyone; a NON-empty string that cannot be parsed fails loudly instead,
+ * because a wrong "you're fine" costs a crash two commands later and a wrong "too old"
+ * costs one confusing message.
+ */
+
+/** The major version at which `node:sqlite` is importable with no flag. */
+export const MIN_NODE_MAJOR = 24;
+
+/**
+ * A short reason string when `version` is below the floor, undefined when it is not.
+ *
+ * Returns the reason rather than printing it so the caller decides the stream and the exit
+ * code, and so the predicate is testable at every version without spawning a Node per case.
+ */
+export function nodeFloorProblem(version) {
+  if (typeof version !== 'string' || version.length === 0) return undefined;
+  const major = Number.parseInt(version.replace(/^v/, ''), 10);
+  if (!Number.isFinite(major)) {
+    return `the running Node version could not read as a version: "${version}"`;
+  }
+  if (major >= MIN_NODE_MAJOR) return undefined;
+  return `Node ${version} predates the builtin SQLite module`;
+}
+
+/** The full operator-facing message: what is wrong, and what to do about it. */
+export function nodeFloorSentence(version) {
+  return (
+    `peaks-loop requires Node >=${String(MIN_NODE_MAJOR)}.0.0 — found ${version || 'unknown'}.\n` +
+    '  why:    the stores read and write through `node:sqlite`, a Node builtin. It replaced\n' +
+    '          a native SQLite addon so that installing this CLI needs no C++ toolchain and\n' +
+    '          no prebuilt binary matching your Node ABI.\n' +
+    '  fix:    switch to Node ' +
+    String(MIN_NODE_MAJOR) +
+    '.x (nvm install ' +
+    String(MIN_NODE_MAJOR) +
+    ' && nvm use ' +
+    String(MIN_NODE_MAJOR) +
+    '),\n' +
+    '          then re-run the same command.\n'
+  );
+}

package/bin/peaks.js

@@ -20,6 +20,19 @@
  */
 import { fileURLToPath } from 'node:url';
 
+import { nodeFloorProblem, nodeFloorSentence } from './node-floor.mjs';
+
+/**
+ * Checked before the app is imported, because the thing it checks is an import: the stores
+ * load `node:sqlite` at module scope, so below the floor the process dies resolving the
+ * graph and never reaches a check written inside the CLI.
+ */
+const floorProblem = nodeFloorProblem(process.versions.node);
+if (floorProblem !== undefined) {
+  process.stderr.write(nodeFloorSentence(process.versions.node));
+  process.exit(1);
+}
+
 const PACKAGE_ROOT = fileURLToPath(new URL('..', import.meta.url));
 
 /** Workspace-internal packages whose absence always means "stale build". */

package/config/eslint/tsconfig.lint.json

@@ -33,7 +33,8 @@
     "../../scripts/dist-freshness.mjs",
     "../../scripts/install-skills.mjs",
     "../../scripts/packages-build-prerequisite.mjs",
-    "../../scripts/verify-version-parity.mjs"
+    "../../scripts/verify-version-parity.mjs",
+    "../../scripts/canonical-store.mjs"
   ],
   "include": [
     "../../src/**/*",

package/dist/cli/cli-helpers.d.ts

@@ -30,7 +30,6 @@ export interface CliEnvelope {
 }
 export declare function printCliEnvelope(io: ProgramIO, r: CliEnvelope): void;
 /**
- * Slice rid-001 (P0-1 envelope closure) — canonical envelope shim
  * for `src/cli/index.ts`'s 3 raw `console.error(JSON.stringify(...))`
  * sites, plus `src/cli/program.ts:162`'s default `ProgramIO.stderr`
  * fallback.

package/dist/cli/cli-helpers.js

@@ -58,7 +58,6 @@ export function printCliEnvelope(io, r) {
     process.exitCode = 1;
 }
 /**
- * Slice rid-001 (P0-1 envelope closure) — canonical envelope shim
  * for `src/cli/index.ts`'s 3 raw `console.error(JSON.stringify(...))`
  * sites, plus `src/cli/program.ts:162`'s default `ProgramIO.stderr`
  * fallback.

package/dist/cli/commands/_cli-error-envelope.js

@@ -1,4 +1,3 @@
-// Slice 015 — single source of truth for translating a thrown error from
 // the service layer (createRdSwarmPlan, createTechPlan, etc.) into a CLI
 // envelope code + user-facing nextActions.
 //
@@ -16,12 +15,10 @@
 // codes based on the runtime error class/message. The CLI catch sites
 // become data-only — they call the helper, then format the envelope.
 import { ProviderNotConfiguredError } from '../../services/config/model-routing.js';
-// Slice 015 risk A: goal-validation uses a substring match on the error
 // message thrown by `validatePlanningInput`. If validatePlanningInput's
 // message wording changes in a future slice, this branch silently
 // degrades into INTERNAL_ERROR. Mitigated by the helper's unit test
 // pinning the literal substring.
-// Slice 015 — match the goal-validation throw message. The current
 // `validatePlanningInput` literal is `"Goal must be non-empty"` (capital
 // G, "non-empty" with hyphen). The regex tolerates common wording
 // variations (`must be non-empty`, `must not be empty`, case-insensitive)

package/dist/cli/commands/adapter-commands-s2a.d.ts

@@ -1,7 +1,6 @@
 /**
  * `peaks adapter *` — vendor adapter registry CLI surface.
  *
- * Slice S2-a of RD-2 (2026-07-08 session). Two subcommands:
  *
  *   list     — list registered user adapters (persisted at
  *              `.peaks/runtime/adapters.json`).

package/dist/cli/commands/adapter-commands.d.ts

@@ -1,7 +1,6 @@
 /**
  * `peaks skill adapter <verb>` — adapter selection + detection CLI.
  *
- * Slice 2026-07-04-cli-15a (Task 15a of the 18-verb plan). Two verbs:
  *
  *   list        — return the known adapter id list
  *   set-active  — record which adapter is currently active

package/dist/cli/commands/api-diff-commands.d.ts

@@ -6,7 +6,6 @@
  * artifact — so `api-diff` is a sibling of an existing command with identical
  * semantics and an identical option shape. A new `peaks api` group would be a
  * brand-new verb family whose cost the design (docs/superpowers/specs/
- * 2026-09-12-frontend-acl-contract-design.md §3/§5) records as medium and
  * acknowledged; nothing about this slice needs it.
  *
  * The command is read-only: it creates no contract artifact and writes no file.

package/dist/cli/commands/api-diff-commands.js

@@ -6,7 +6,6 @@
  * artifact — so `api-diff` is a sibling of an existing command with identical
  * semantics and an identical option shape. A new `peaks api` group would be a
  * brand-new verb family whose cost the design (docs/superpowers/specs/
- * 2026-09-12-frontend-acl-contract-design.md §3/§5) records as medium and
  * acknowledged; nothing about this slice needs it.
  *
  * The command is read-only: it creates no contract artifact and writes no file.

package/dist/cli/commands/audit-commands.js

@@ -18,7 +18,8 @@ import { addJsonOption, getErrorMessage, printResult } from '../cli-helpers.js';
 import { fail, ok } from 'peaks-loop-shared/result';
 import { writeAuditDecision } from '../../services/audit/decision-writer.js';
 import { computeProseRatio } from '../../services/audit/prose-ratio-calculator.js';
-import { writeMachineOutput, writeNarrative, writePrompt } from '../../services/audit/artifact-writer.js';
+import { writeMachineOutput, writeNarrative, writePrompt, writeDecision } from '../../services/audit/artifact-writer.js';
+import { parseRedLineAuditInput, RedLineAuditInputError } from '../../services/audit/red-line-audit-input.js';
 const SUPPORTED_ARTIFACT_KINDS = [
     'decision',
     'prompt',
@@ -117,7 +118,6 @@ export function registerAuditCommands(program, io) {
     // and the dev-preference red line "Default-no on new CLI commands",
     // we extend the existing command rather than register a new subcommand.
     //
-    // 2026-09-09-ecc-dynamic-and-cleanup B3: the dead
     // `--enable-agent-shield` / `--disable-agent-shield` flags were removed.
     // `runStaticAudit`'s agentShield state is a frozen "always disabled" stub
     // (Slice 3 of 4.0.0-beta.11 removed the subprocess), so the flags had no
@@ -169,7 +169,6 @@ export function registerAuditCommands(program, io) {
                 ...(decision ? { decision } : {})
             };
             const nextActions = [];
-            // 2026-09-09-ecc-dynamic-and-cleanup B3: the ECC AgentShield opt-in
             // nextActions block was removed. `agentShield.installed` is a frozen
             // `false`, so the block printed on every run and pointed users at a
             // removed subprocess, removed flags, and a dead preference.
@@ -226,7 +225,6 @@ export function registerAuditCommands(program, io) {
             process.exitCode = 1;
         }
     });
-    // Slice 2026-09-12-llm-provider-binding — `peaks audit goal` now runs the
     // gate it advertises. `auditGoal()` was already correct (one `LlmRunner`
     // call, 6-dimension validation, `IncompleteAuditError` on a partial audit);
     // what was missing was a provider binding, so the command answered with a
@@ -297,7 +295,6 @@ export function registerAuditCommands(program, io) {
         }
     });
     // ---------------------------------------------------------------------------
-    // peaks audit artifact write — Slice 2026-06-26-audit-artifact-writer-generalization
     //
     // First-class CLI surface for the 4 audit artifact types. Replaces the
     // 2026-06-22 "hand `git add` into .peaks/memory/" anti-pattern that left
@@ -313,7 +310,7 @@ export function registerAuditCommands(program, io) {
         .description('Persist a single audit artifact to .peaks/memory/ via the artifact-writer (canonical frontmatter)')
         .requiredOption('--project <path>', 'target project root')
         .requiredOption('--kind <kind>', `artifact kind (${SUPPORTED_ARTIFACT_KINDS.join(' | ')})`)
-        .requiredOption('--input <path>', 'path to source file (markdown for prompt/narrative; JSON for machine-output)')
+        .requiredOption('--input <path>', 'path to source file (markdown for prompt/narrative; JSON for machine-output and decision)')
         .option('--name <name>', 'display name (H1 in body); defaults to file basename')
         .option('--description <text>', 'description field for frontmatter; defaults to a generic placeholder')
         .option('--rid <id>', 'optional request id to disambiguate multiple writes on the same day')
@@ -392,22 +389,16 @@ export function registerAuditCommands(program, io) {
                     break;
                 }
                 case 'decision': {
-                    // --kind decision requires JSON of `RedLineAudit` shape; for now
-                    // surface a clear error so callers don't silently write junk.
-                    printResult(io, fail('audit.artifact.write', 'KIND_DECISION_USE_STATIC_RECORD', `--kind decision should use 'peaks audit static --record' which writes a RedLineAudit snapshot. 'peaks audit artifact write --kind decision' is reserved for future direct-snapshot writes (not implemented yet).`, {
-                        kind: 'decision',
-                        slug: '',
-                        title: '',
-                        date: '',
-                        filePath: '',
-                        memoryDir: '',
-                        indexPath: '',
-                        indexSynced: false
-                    }, [
-                        "Re-run with 'peaks audit static --record --project <root>' for RedLineAudit snapshots."
-                    ]), options.json);
-                    process.exitCode = 1;
-                    return;
+                    // `--input` is a RedLineAudit JSON document — typically
+                    // an archived `peaks audit static` result — validated field by field
+                    // before it reaches the writer, because the writer renders whatever
+                    // it is given into a memory record with no further checks.
+                    // `--name` and `--description` do not apply: the decision slug and
+                    // title come from the scan date (and `--rid`), exactly as
+                    // `peaks audit static --record` derives them.
+                    const audit = parseRedLineAuditInput(readFileSync(inputAbs, 'utf8'));
+                    record = writeDecision(audit, writeOpts);
+                    break;
                 }
                 default: {
                     // Unreachable: isSupportedArtifactKind already filtered.
@@ -416,7 +407,9 @@ export function registerAuditCommands(program, io) {
             }
         }
         catch (err) {
-            printResult(io, fail('audit.artifact.write', 'WRITE_FAILED', getErrorMessage(err), {
+            // A malformed decision input is the caller's document, not a write
+            // failure: name it as input so the remedy reads as "fix the JSON field".
+            printResult(io, fail('audit.artifact.write', err instanceof RedLineAuditInputError ? 'AUDIT_ARTIFACT_INPUT_INVALID' : 'WRITE_FAILED', getErrorMessage(err), {
                 kind: options.kind,
                 slug: '',
                 title: '',
@@ -425,7 +418,11 @@ export function registerAuditCommands(program, io) {
                 memoryDir: '',
                 indexPath: '',
                 indexSynced: false
-            }, ['Inspect the error message; for --kind machine-output ensure --input is valid JSON']), options.json);
+            }, err instanceof RedLineAuditInputError
+                ? [
+                    'Inspect the named field; --kind decision takes the JSON shape `peaks audit static --json` prints.'
+                ]
+                : ['Inspect the error message; for --kind machine-output ensure --input is valid JSON']), options.json);
             process.exitCode = 1;
             return;
         }

package/dist/cli/commands/autonomous-swarm-commands.js

@@ -112,7 +112,6 @@ function addAutonomousPlanOptions(command) {
         .option('--no-dry-run', 'unsupported: do not execute autonomous planning from this CLI'));
 }
 export function registerAutonomousSwarmCommands(program, io) {
-    // Register the new rid-014 dry-run planner under
     // `peaks workflow autonomous-swarm` (the existing `peaks workflow
     // autonomous` registration owns the bare `autonomous` name and is
     // untouched). The legacy `registerSwarmCommands` and

package/dist/cli/commands/bee-commands.d.ts

@@ -1,5 +1,4 @@
 /**
- * peaks bee * CLI — M7 (spec §7A.2 / §10 RL-9 / AC-24 / AC-25 / AC-26).
  *
  * Adds:
  *   peaks bee export --bee <id> --out <path.tar.gz>
@@ -19,7 +18,6 @@
  * touched it.
  *
  * The `peaks skill sediment export / import` alias lives in
- * `src/cli/commands/skill-sediment.ts` for one release cycle.
  */
 import type { Command } from 'commander';
 import { type ProgramIO } from '../cli-helpers.js';

package/dist/cli/commands/bee-commands.js

@@ -1,5 +1,4 @@
 /**
- * peaks bee * CLI — M7 (spec §7A.2 / §10 RL-9 / AC-24 / AC-25 / AC-26).
  *
  * Adds:
  *   peaks bee export --bee <id> --out <path.tar.gz>
@@ -19,7 +18,6 @@
  * touched it.
  *
  * The `peaks skill sediment export / import` alias lives in
- * `src/cli/commands/skill-sediment.ts` for one release cycle.
  */
 import { existsSync, mkdirSync } from 'node:fs';
 import { join } from 'node:path';

package/dist/cli/commands/best-practice-scan-command.d.ts

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-08-12 best-practice-scan — CLI subcommand.
  *
  * `peaks best-practice-scan --intent <goal> --project <path> [--lang <lang>] [--commit]`
  *

package/dist/cli/commands/best-practice-scan-helpers.js

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-08-12 best-practice-scan — support constants + pure helpers
  * extracted from `best-practice-scan-command.ts` (file-size cap campaign).
  * Mechanical move only: help-text constants, the artifact directory path
  * helper, and the synthetic-lookup refusal renderer.

package/dist/cli/commands/changeset-commands.d.ts

@@ -1,11 +1,9 @@
 /**
- * rid-011 — peaks changeset check (Phase 4 slice 2).
  *
  *   - `peaks changeset check` — hard gate, exit non-zero if any staged
  *     .changeset/*.md exists. No warning mode, no --strict, no
  *     --skip-changeset-check.
  *
- * Wired into `_register.ts` via the rid-007 auto-registration barrel;
  * do NOT add a second registration call in `program.ts`.
  */
 import type { Command } from 'commander';

package/dist/cli/commands/changeset-commands.js

@@ -1,11 +1,9 @@
 /**
- * rid-011 — peaks changeset check (Phase 4 slice 2).
  *
  *   - `peaks changeset check` — hard gate, exit non-zero if any staged
  *     .changeset/*.md exists. No warning mode, no --strict, no
  *     --skip-changeset-check.
  *
- * Wired into `_register.ts` via the rid-007 auto-registration barrel;
  * do NOT add a second registration call in `program.ts`.
  */
 import { findProjectRoot } from '../../services/config/config-safety.js';

package/dist/cli/commands/code-commands.d.ts

@@ -15,7 +15,6 @@
  *   - `peaks code should-pause --step <step> --mode <mode>` (D5)
  *   - `peaks code post-compact-detect --project <path>` (D7)
  *
- * rid-024: 7 sub-commands extracted into 3 sibling files:
  *   - code-mode-gate-commands.ts (plan + should-pause)
  *   - code-job-shape-commands.ts (detect-job + read-job-shape)
  *   - code-runtime-commands.ts (post-compact-detect + auto-compact + context-now + gate-step-08 + emit-handoff)
@@ -84,7 +83,5 @@ export declare function runCodeFast(opts: {
  * CLI command is a thin surface that builds the plan and emits a JSON
  * envelope for downstream tooling.
  *
- * rid-024: this function is now a thin orchestrator that delegates to 3
- * sibling register functions + the rid-020b run register.
  */
 export declare function registerCodeCommands(program: Command, io: ProgramIO): void;

package/dist/cli/commands/code-commands.js

@@ -15,7 +15,6 @@
  *   - `peaks code should-pause --step <step> --mode <mode>` (D5)
  *   - `peaks code post-compact-detect --project <path>` (D7)
  *
- * rid-024: 7 sub-commands extracted into 3 sibling files:
  *   - code-mode-gate-commands.ts (plan + should-pause)
  *   - code-job-shape-commands.ts (detect-job + read-job-shape)
  *   - code-runtime-commands.ts (post-compact-detect + auto-compact + context-now + gate-step-08 + emit-handoff)
@@ -106,8 +105,6 @@ export async function runCodeFast(opts) {
  * CLI command is a thin surface that builds the plan and emits a JSON
  * envelope for downstream tooling.
  *
- * rid-024: this function is now a thin orchestrator that delegates to 3
- * sibling register functions + the rid-020b run register.
  */
 export function registerCodeCommands(program, io) {
     const code = program

package/dist/cli/commands/code-gate-command.d.ts

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-08-06-codegate-vendor-neutral — `peaks code-gate` CLI command.
  *
  * Vendor-neutral PreToolUse hook entry. Reads the standard hook JSON
  * payload from stdin (`{tool, input}` shape) and either exits 0

package/dist/cli/commands/code-gate-command.js

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-08-06-codegate-vendor-neutral — `peaks code-gate` CLI command.
  *
  * Vendor-neutral PreToolUse hook entry. Reads the standard hook JSON
  * payload from stdin (`{tool, input}` shape) and either exits 0

package/dist/cli/commands/code-job-shape-commands-read-job-shape.d.ts

@@ -1,5 +1,4 @@
 /**
- * Slice rid-024 — `peaks code read-job-shape`.
  *
  * Extracted from code-job-shape-commands.ts (C wave 4 near-cap split). Owns:
  * read-job-shape (read + print). Command name, options, emitted message text,

package/dist/cli/commands/code-job-shape-commands-read-job-shape.js

@@ -1,5 +1,4 @@
 /**
- * Slice rid-024 — `peaks code read-job-shape`.
  *
  * Extracted from code-job-shape-commands.ts (C wave 4 near-cap split). Owns:
  * read-job-shape (read + print). Command name, options, emitted message text,

package/dist/cli/commands/code-job-shape-commands.d.ts

@@ -1,7 +1,5 @@
 /**
- * Slice rid-024 — `peaks code detect-job` + `peaks code read-job-shape`.
  *
- * Extracted from code-commands.ts (rid-024 split).
  * Owns: detect-job (write JobShapeDecision), read-job-shape (read+print).
  */
 import type { Command } from 'commander';

package/dist/cli/commands/code-job-shape-commands.js

@@ -1,7 +1,5 @@
 /**
- * Slice rid-024 — `peaks code detect-job` + `peaks code read-job-shape`.
  *
- * Extracted from code-commands.ts (rid-024 split).
  * Owns: detect-job (write JobShapeDecision), read-job-shape (read+print).
  */
 import { existsSync, readFileSync } from 'node:fs';
@@ -131,7 +129,6 @@ export function registerCodeJobShapeCommands(code, io) {
     // `catch` is not duplicated into a second silent-swallow site.
     registerCodeJobShapeReadCommand(code, io, readActiveSidForJobShape);
 }
-// Local helper (was `readActiveSid` in code-commands.ts before rid-024 split).
 // Both detect-job and read-job-shape need to read the active sid from
 // presence. We re-import getSkillPresence here to avoid the cross-file
 // helper import.