peaks-loop 4.1.1 → 4.1.3

package/dist/services/ide/adapters/tongyi-lingma-adapter.js

@@ -1,5 +1,4 @@
 /**
- * Tongyi Lingma IDE adapter (slice 2026-07-25-tongyi-lingma-adapter-ship) —
  * peaks-loop 第九个内置 IDE 适配器(填表)。
  *
  * 不可消除的 per-IDE 字段(本 slice 填表;字段值暂为占位):
@@ -10,7 +9,6 @@
  *   - toolMatcher = 'Bash'                         (UNVERIFIED)
  *
  * 这些字段在真实 Tongyi Lingma 安装 dogfood 完成前不得标记 VERIFIED。
- * 见 [[2026-07-24-multi-ide-adapter-policy]] §3 step 5。
  */
 import { homedir } from 'node:os';
 import { join, resolve } from 'node:path';

package/dist/services/ide/adapters/trae-adapter.d.ts

@@ -4,10 +4,7 @@ import type { IdeAdapter } from '../ide-types.js';
  *
  * 不可消除的 per-IDE 字段(slice #1 锁定):
  *   - settings.dirName = '.trae'            : Trae 项目根下的配置目录
- *   - settings.settingsFileName = 'settings.json'  (VERIFIED against Trae 1.x fixture, slice 009-009-2026-06-07-trae-dogfood)
  *   - envVar = 'TRAE_PROJECT_DIR'    : Trae 注入的 env 变量(用于 ${...} 占位)
- *   - hookEvent = 'beforeToolCall'  (VERIFIED against Trae 1.x fixture, slice 009-009-2026-06-07-trae-dogfood)
- *   - toolMatcher = 'terminal'      (VERIFIED against Trae 1.x fixture, slice 009-009-2026-06-07-trae-dogfood)
  *
  * Slice #1 的 slim `IdeAdapter` shape 在 slice #1 RD 中被锁为"填表"模式。
  * 本文件是 slice #2 第一个真实客户,验证 slice #1 抽出的形状真的可以

package/dist/services/ide/adapters/trae-adapter.js

@@ -6,10 +6,7 @@ import { traeSubAgentDispatcher } from '../../dispatch/sub-agent-dispatcher.js';
  *
  * 不可消除的 per-IDE 字段(slice #1 锁定):
  *   - settings.dirName = '.trae'            : Trae 项目根下的配置目录
- *   - settings.settingsFileName = 'settings.json'  (VERIFIED against Trae 1.x fixture, slice 009-009-2026-06-07-trae-dogfood)
  *   - envVar = 'TRAE_PROJECT_DIR'    : Trae 注入的 env 变量(用于 ${...} 占位)
- *   - hookEvent = 'beforeToolCall'  (VERIFIED against Trae 1.x fixture, slice 009-009-2026-06-07-trae-dogfood)
- *   - toolMatcher = 'terminal'      (VERIFIED against Trae 1.x fixture, slice 009-009-2026-06-07-trae-dogfood)
  *
  * Slice #1 的 slim `IdeAdapter` shape 在 slice #1 RD 中被锁为"填表"模式。
  * 本文件是 slice #2 第一个真实客户,验证 slice #1 抽出的形状真的可以
@@ -46,15 +43,15 @@ export const TRAE_ADAPTER = {
     displayName: 'Trae',
     settings: {
         dirName: '.trae',
-        settingsFileName: 'settings.json', // VERIFIED against Trae 1.x fixture — slice 009-009-2026-06-07-trae-dogfood (2026-06-07)
+        settingsFileName: 'settings.json',
         resolveSettingsFile: (scope, projectRoot) => {
             const root = scope === 'global' ? homedir() : resolve(projectRoot ?? homedir());
             return join(root, '.trae', 'settings.json');
         }
     },
     envVar: 'TRAE_PROJECT_DIR',
-    hookEvent: 'beforeToolCall', // VERIFIED against Trae 1.x fixture — slice 009-009-2026-06-07-trae-dogfood (2026-06-07); fixture at tests/fixtures/trae/trae-1x-payload.json
-    toolMatcher: 'terminal', // VERIFIED against Trae 1.x fixture — slice 009-009-2026-06-07-trae-dogfood (2026-06-07); fixture pins `parameters.tool: 'terminal'`
+    hookEvent: 'beforeToolCall',
+    toolMatcher: 'terminal',
     // Slice #009: Trae's sub-agent dispatcher is UNVERIFIED — Trae sub-agent
     // tool name TBD on real dogfood; byte-level identical to claude-code by
     // design so the dispatcher shape is uniform across both adapters. Awaiting

package/dist/services/ide/adapters/zcode-adapter.js

@@ -1,5 +1,4 @@
 /**
- * z-code IDE adapter (slice 2026-07-09-add-zcode-adapter) — peaks-loop 的第九个
  * 内置 IDE 适配器。
  *
  * z-code 是一个 VS Code-style 的 Anthropic-compatible 桌面应用:
@@ -171,7 +170,6 @@ export const ZCODE_ADAPTER = {
     hookEvent: 'PreToolUse',
     // UNVERIFIED — 同上,占位用 `Bash` matcher。
     toolMatcher: 'Bash',
-    // Slice 2026-07-09: z-code 桌面应用没有公开 Task 工具 dispatch 协议,
     // 用 `nullSubAgentDispatcher` 占位 — peaks sub-agent dispatch CLI 在
     // z-code 上返回 SubAgentNotSupportedError,符合 slice #008 P-5 capability
     // 检查契约 (CLI 不崩溃)。

package/dist/services/ide/current-model-detector.js

@@ -1,5 +1,4 @@
 /**
- * Runtime current-model detector (Slice 2026-07-09 add-zcode-adapter, Slice C).
  *
  * Walks the registered IDE adapter chain and asks the IDE adapter
  * (when it opts in via `IdeAdapter.detectCurrentModel?`) to report the

package/dist/services/ide/hook-protocol.d.ts

@@ -11,13 +11,11 @@ export declare const CLAUDE_CODE_DENY_SHAPE: Record<string, unknown>;
 export declare const CLAUDE_CODE_DENY_TRANSPORT: PeaksDecisionTransport;
 /**
  * Compute the deny decision shape for Trae (Cursor-style sibling IDE).
- * VERIFIED against Trae 1.x fixture — slice 009-009-2026-06-07-trae-dogfood (2026-06-07).
  * Shape is the standard Cursor/Claude sibling envelope: `hookSpecificOutput`
  * with `hookEventName`, `permissionDecision`, `permissionDecisionReason`.
  * The hookEventName is `'beforeToolCall'` for Trae vs `'PreToolUse'` for
  * Claude Code — the only field that differs between the two siblings.
  * Fixture: tests/fixtures/trae/trae-1x-payload.json. Constant NAME preserved
- * (per slice 009 PRD R-3); only the shape was already correct from slice #3.
  */
 export declare const TRAE_DENY_SHAPE: Record<string, unknown>;
 export declare const TRAE_DENY_TRANSPORT: PeaksDecisionTransport;

package/dist/services/ide/hook-protocol.js

@@ -19,13 +19,11 @@ export const CLAUDE_CODE_DENY_TRANSPORT = {
 };
 /**
  * Compute the deny decision shape for Trae (Cursor-style sibling IDE).
- * VERIFIED against Trae 1.x fixture — slice 009-009-2026-06-07-trae-dogfood (2026-06-07).
  * Shape is the standard Cursor/Claude sibling envelope: `hookSpecificOutput`
  * with `hookEventName`, `permissionDecision`, `permissionDecisionReason`.
  * The hookEventName is `'beforeToolCall'` for Trae vs `'PreToolUse'` for
  * Claude Code — the only field that differs between the two siblings.
  * Fixture: tests/fixtures/trae/trae-1x-payload.json. Constant NAME preserved
- * (per slice 009 PRD R-3); only the shape was already correct from slice #3.
  */
 export const TRAE_DENY_SHAPE = {
     hookSpecificOutput: {

package/dist/services/ide/ide-compact-types.d.ts

@@ -21,7 +21,6 @@ export interface IdeCompactProfile {
      * spawns this via `child_process.spawn` (shell-exec pathway) or
      * writes it to an IDE hook file (ide-native pathway).
      *
-     * ZERO EXECUTOR as of slice 2026-09-13-auto-compact-trigger-ownership: every
      * `shell-exec` branch now only REPORTS that it will not spawn (see
      * `auto-compact-dispatcher.ts`), and the `ide-native` branch registers a
      * harness-side trigger instead. The field is retained because the sibling
@@ -50,7 +49,6 @@ export interface IdeCompactProfile {
      * declared, peaks-loop writes the window it computes its ratio against
      * into the adapter's machine-local settings `env` block, under this key,
      * so both sides reference one number instead of two independent
-     * resolutions (slice 2026-09-13-auto-compact-trigger-ownership).
      *
      * `undefined` = this IDE exposes no such knob. peaks-loop then cannot
      * close the drift; `peaks compact harness-window` reports that instead of
@@ -76,13 +74,11 @@ export interface IdeCompactProfile {
      * that do not opt in simply omit the field; new IDEs are addable
      * without touching the generic reader.
      *
-     * Added in slice 2026-09-02-vendor-neutral-context-probe.
      */
     readonly readContextPercentFallback?: (input: ContextPercentFallbackInput) => ContextPercentProbe | null;
     /**
      * Optional locator for the IDE's per-session transcript file (jsonl),
      * keyed by the OUTER (harness) session id. `peaks code context-audit`
-     * (slice 2026-09-10-context-audit-and-discipline, Slice A) uses it to
      * group the session's tool results by tool + short input key, so the
      * generic audit service never learns any vendor's on-disk layout.
      *
@@ -101,7 +97,6 @@ export interface IdeCompactProfile {
  * owns the vendor-specific fallback logic (statusline poll, transcript
  * lookup, etc.); the generic reader stays IDE-agnostic.
  *
- * Added in slice 2026-09-02-vendor-neutral-context-probe.
  */
 export interface ContextPercentFallbackInput {
     /** Project root (the probe's `--project` anchor). */
@@ -122,7 +117,6 @@ export interface ContextPercentFallbackInput {
      * of config-path knowledge. UNVALIDATED — the adapter validates it via
      * `parseContextWindowOverride` and warns on a bad value.
      *
-     * Slice 2026-09-09-context-window-override.
      */
     readonly configWindowTokens?: unknown;
     /**
@@ -131,7 +125,6 @@ export interface ContextPercentFallbackInput {
      * key name) — the window peaks-loop configured for the harness. Feeds the
      * `harness-env` layer of `resolveContextWindow`.
      *
-     * Slice 2026-09-13-auto-compact-trigger-ownership.
      */
     readonly harnessWindowTokens?: unknown;
     /**

package/dist/services/ide/ide-mcp-install-types.d.ts

@@ -0,0 +1,78 @@
+/**
+ * The REGISTRATION profile of one harness's MCP entry point (spec §8.3).
+ *
+ * WHY THIS IS NOT `IdeMcpProfile`. That profile (on `IdeAdapter.mcp`) answers
+ * "how does this harness SPELL a peaks tool name", which the pre-tool branch
+ * needs. This one answers "how does this harness register a server", which only
+ * the distribution path needs. One field would conflate two questions asked by
+ * two callers that never run together.
+ *
+ * WHY IT DECLARES ARGV AND NOT A COMMAND STRING. Registering is the HARNESS's
+ * own operation: `peaks mcp install` calls the harness's entry point rather than
+ * hand-editing the harness's config file, because that file is full of the
+ * user's state and hand-editing it is neither safe nor version-stable (§8.3).
+ * The entry is declared as an ARRAY with three placeholders, so the engine that
+ * consumes it substitutes values into an array and never builds a command line.
+ *
+ * WHY add AND remove ARE BOTH DECLARED. A harness's register verb is not
+ * idempotent — same name, same scope, and it fails, with no `--force` and no
+ * `update` — so the install is delete-then-add (§8.3). Both halves are therefore
+ * part of the contract, and `scopes` exists because the entry can already sit in
+ * more than one of them: the delete is a sweep, not a targeted call.
+ *
+ * WHAT IS DELIBERATELY ABSENT: any harness name, any platform name, and any
+ * branch on either. A vendor's own spellings belong in its adapter, which is the
+ * only module that fills this type in.
+ */
+/** Placeholder for the server key the harness files peaks under. */
+export declare const MCP_NAME_PLACEHOLDER = "<name>";
+/** Placeholder for one scope the entry can live in; substituted once per removal. */
+export declare const MCP_SCOPE_PLACEHOLDER = "<scope>";
+/** Placeholder for the launched server argv — the command and every token after it. */
+export declare const MCP_SERVER_ARGV_PLACEHOLDER = "<server-argv>";
+/** The placeholders an argv template may carry, and nothing else may look like one. */
+export declare const MCP_ARGV_PLACEHOLDERS: readonly ["<name>", "<scope>", "<server-argv>"];
+/**
+ * How one harness registers, and unregisters, a peaks MCP server.
+ *
+ * Optional on `IdeAdapter`, like `skillInstall?` / `standardsProfile?`: an
+ * adapter that omits it is declaring "this harness has no registration entry
+ * peaks may call", and every consumer reads that as "nothing to do" rather than
+ * as an error.
+ */
+export interface IdeMcpInstallProfile {
+    /** The server key this harness files peaks under. The install touches only this one. */
+    readonly serverName: string;
+    /**
+     * Every scope the entry can live in. The delete sweeps all of them, because a
+     * previous install may have written a different one and the harness's own
+     * removal fails on the scope that is empty.
+     */
+    readonly scopes: readonly string[];
+    /** The scope the entry is (re-)written to. Must be one of `scopes`. */
+    readonly targetScope: string;
+    /** argv template that registers the server. Carries `<name>` and `<server-argv>`. */
+    readonly addArgv: readonly string[];
+    /** argv template that unregisters it. Carries `<name>` and `<scope>`. */
+    readonly removeArgv: readonly string[];
+}
+/** The values an argv template is expanded with. */
+export interface McpArgvValues {
+    readonly serverName: string;
+    readonly scope: string;
+    readonly serverArgv: readonly string[];
+}
+/**
+ * A declaration that cannot drive an install is a defect in the adapter, and it
+ * is reported as one rather than silently producing an argv the harness will
+ * reject. That is the whole argument for throwing here: a profile missing its
+ * server-argv placeholder would install a registration that launches nothing,
+ * and nothing would say so.
+ */
+export declare function assertMcpInstallProfile(profile: IdeMcpInstallProfile): void;
+/**
+ * Expand one argv template. A placeholder that stands for SEVERAL tokens expands
+ * to all of them, which is why this returns an array and why the launched server
+ * argv is passed as one: the caller never joins and never splits.
+ */
+export declare function expandMcpArgv(argv: readonly string[], values: McpArgvValues): readonly string[];

package/dist/services/ide/ide-mcp-install-types.js

@@ -0,0 +1,104 @@
+/**
+ * The REGISTRATION profile of one harness's MCP entry point (spec §8.3).
+ *
+ * WHY THIS IS NOT `IdeMcpProfile`. That profile (on `IdeAdapter.mcp`) answers
+ * "how does this harness SPELL a peaks tool name", which the pre-tool branch
+ * needs. This one answers "how does this harness register a server", which only
+ * the distribution path needs. One field would conflate two questions asked by
+ * two callers that never run together.
+ *
+ * WHY IT DECLARES ARGV AND NOT A COMMAND STRING. Registering is the HARNESS's
+ * own operation: `peaks mcp install` calls the harness's entry point rather than
+ * hand-editing the harness's config file, because that file is full of the
+ * user's state and hand-editing it is neither safe nor version-stable (§8.3).
+ * The entry is declared as an ARRAY with three placeholders, so the engine that
+ * consumes it substitutes values into an array and never builds a command line.
+ *
+ * WHY add AND remove ARE BOTH DECLARED. A harness's register verb is not
+ * idempotent — same name, same scope, and it fails, with no `--force` and no
+ * `update` — so the install is delete-then-add (§8.3). Both halves are therefore
+ * part of the contract, and `scopes` exists because the entry can already sit in
+ * more than one of them: the delete is a sweep, not a targeted call.
+ *
+ * WHAT IS DELIBERATELY ABSENT: any harness name, any platform name, and any
+ * branch on either. A vendor's own spellings belong in its adapter, which is the
+ * only module that fills this type in.
+ */
+/** Placeholder for the server key the harness files peaks under. */
+export const MCP_NAME_PLACEHOLDER = '<name>';
+/** Placeholder for one scope the entry can live in; substituted once per removal. */
+export const MCP_SCOPE_PLACEHOLDER = '<scope>';
+/** Placeholder for the launched server argv — the command and every token after it. */
+export const MCP_SERVER_ARGV_PLACEHOLDER = '<server-argv>';
+/** The placeholders an argv template may carry, and nothing else may look like one. */
+export const MCP_ARGV_PLACEHOLDERS = [
+    MCP_NAME_PLACEHOLDER,
+    MCP_SCOPE_PLACEHOLDER,
+    MCP_SERVER_ARGV_PLACEHOLDER
+];
+/**
+ * One template's structural requirements: it must carry something, its
+ * bracket-shaped tokens must be ones the engine knows how to substitute, and the
+ * placeholders the caller needs in it must be there. An unknown placeholder is a
+ * refusal rather than a literal, because passing it through would hand the
+ * harness an argument that means nothing to it.
+ */
+function assertArgvTemplate(label, argv, required, refuse) {
+    if (argv.length === 0)
+        refuse(`${label} is empty`);
+    for (const token of argv) {
+        const bracketShaped = token.startsWith('<') && token.endsWith('>');
+        const known = MCP_ARGV_PLACEHOLDERS.includes(token);
+        if (bracketShaped && !known)
+            refuse(`${label} carries unknown placeholder '${token}'`);
+    }
+    for (const placeholder of required) {
+        if (!argv.includes(placeholder))
+            refuse(`${label} does not carry ${placeholder}`);
+    }
+}
+/**
+ * A declaration that cannot drive an install is a defect in the adapter, and it
+ * is reported as one rather than silently producing an argv the harness will
+ * reject. That is the whole argument for throwing here: a profile missing its
+ * server-argv placeholder would install a registration that launches nothing,
+ * and nothing would say so.
+ */
+export function assertMcpInstallProfile(profile) {
+    const refuse = (reason) => {
+        throw new Error(`IdeMcpInstallProfile is not installable: ${reason}`);
+    };
+    if (profile.serverName.length === 0)
+        refuse('serverName is empty');
+    if (profile.scopes.length === 0)
+        refuse('scopes is empty');
+    if (!profile.scopes.includes(profile.targetScope)) {
+        refuse(`targetScope '${profile.targetScope}' is not one of the declared scopes`);
+    }
+    assertArgvTemplate('addArgv', profile.addArgv, [MCP_NAME_PLACEHOLDER, MCP_SCOPE_PLACEHOLDER, MCP_SERVER_ARGV_PLACEHOLDER], refuse);
+    assertArgvTemplate('removeArgv', profile.removeArgv, [MCP_NAME_PLACEHOLDER, MCP_SCOPE_PLACEHOLDER], refuse);
+}
+/**
+ * Expand one argv template. A placeholder that stands for SEVERAL tokens expands
+ * to all of them, which is why this returns an array and why the launched server
+ * argv is passed as one: the caller never joins and never splits.
+ */
+export function expandMcpArgv(argv, values) {
+    const expanded = [];
+    for (const token of argv) {
+        if (token === MCP_NAME_PLACEHOLDER) {
+            expanded.push(values.serverName);
+            continue;
+        }
+        if (token === MCP_SCOPE_PLACEHOLDER) {
+            expanded.push(values.scope);
+            continue;
+        }
+        if (token === MCP_SERVER_ARGV_PLACEHOLDER) {
+            expanded.push(...values.serverArgv);
+            continue;
+        }
+        expanded.push(token);
+    }
+    return expanded;
+}

package/dist/services/ide/ide-types.d.ts

@@ -13,12 +13,13 @@
  */
 import type { SubAgentDispatcher } from '../dispatch/sub-agent-dispatcher.js';
 import type { ContextPercentFallbackInput, IdeCompactProfile } from './ide-compact-types.js';
+import type { IdeMcpInstallProfile } from './ide-mcp-install-types.js';
 /**
  * Re-exported so every importer of `./ide-types.js` keeps seeing the whole
  * adapter type surface from the original path (b1 file-size campaign: the two
  * declarations now live in `./ide-compact-types.js`).
  */
-export type { ContextPercentFallbackInput, IdeCompactProfile };
+export type { ContextPercentFallbackInput, IdeCompactProfile, IdeMcpInstallProfile };
 export type IdeId = 'claude-code' | 'trae' | 'codex' | 'cursor' | 'qoder' | 'tongyi-lingma' | 'hermes' | 'openclaw' | 'zcode';
 export interface IdeCapabilities {
     /** peaks gate enforce 是否适用该 IDE(必备) */
@@ -68,8 +69,6 @@ export interface IdeAdapter {
      * this field, calls `supportsRole` + `buildToolCall`, and returns the
      * resulting tool-call descriptor in the JSON envelope. Encapsulates the per-IDE sub-agent dispatch surface (slice #009). The dispatcher's `buildToolCall` returns the IDE-native tool-call descriptor at runtime.
      *
-     * Added in slice 2026-06-07-sub-agent-dispatch-decouple. See PRD #002
-     * G1 (AC-1, AC-2) + [[slim-ideadapter-shape-is-the-contract]].
      */
     readonly subAgentDispatcher: SubAgentDispatcher;
     /**
@@ -83,8 +82,6 @@ export interface IdeAdapter {
      * the threshold regardless of this field — `promptSizeAware` only
      * controls the hook layer (R-15: G9 hook is LLM-platform-specific).
      *
-     * Added in slice 2026-06-07-sub-agent-context-governance. See PRD
-     * #003 G9.2 + AC-56. Default `false` to preserve slice #009's
      * `peaks hooks install` output byte-stability.
      */
     readonly promptSizeAware: boolean;
@@ -100,7 +97,6 @@ export interface IdeAdapter {
      * value (Claude Code), are annotated UNVERIFIED for future slices
      * (Trae, slice #012+), or omit it entirely (not-yet-registered IDEs).
      *
-     * Added in slice 011-2026-06-07-ide-adapter-resource-profile.
      */
     readonly standardsProfile?: IdeStandardsProfile;
     /**
@@ -111,21 +107,17 @@ export interface IdeAdapter {
      * this; adapters that don't (Trae in slice 1.3.2) leave it undefined
      * and follow the legacy path with a warning.
      *
-     * Added in slice 011-2026-06-07-ide-adapter-resource-profile.
      */
     readonly skillInstall?: IdeSkillInstall;
     /**
-     * v2.13.0 auto-compact (AC-1 + AC-3): per-IDE compact-capability
      * descriptor. When `undefined`, peaks-loop falls back to the
      * `llm-self-compress` pathway (the LLM summarizes its own context).
      * Adapters that fill this expose a 4-stage protocol so peaks-loop
      * can drive compact autonomously:
      *
      *   1. `envVarForContextPercent` — env-var the IDE sets per turn
-     *      (e.g. `CLAUDE_CONTEXT_USAGE_PERCENT`). Read by AC-1.
      *   2. `compactCommand` — slash command or shell-call the IDE
      *      accepts to trigger compact (e.g. `/compact`). Dispatched
-     *      by AC-3.
      *   3. `compactPathway` — `'shell-exec' | 'ide-native' |
      *      'llm-self-compress' | 'noop'`. `shell-exec` means peaks-loop
      *      spawns `compactCommand` via `child_process.spawn` (zero IDE
@@ -140,7 +132,6 @@ export interface IdeAdapter {
      * `compactPathway: 'llm-self-compress'` until L2-dogfood verifies
      * each IDE's actual compact surface.
      *
-     * Added in slice 2026-06-27-auto-compact-protocol. See
      * `.peaks/memory/2026-06-27-auto-compact-design.md`.
      */
     readonly compact?: IdeCompactProfile;
@@ -162,7 +153,6 @@ export interface IdeAdapter {
      * locally and return `undefined`. The orchestration layer also
      * catches, but defense in depth.
      *
-     * Added in slice 2026-07-09 add-zcode-adapter (Slice C); only the
      * `zcode` adapter opts in this slice. Future slices can opt in
      * other IDEs without changing this signature (optional method).
      */
@@ -182,10 +172,52 @@ export interface IdeAdapter {
      * funnelling all vendor signal through this method.
      */
     readonly resolveCallerId: (env?: NodeJS.ProcessEnv) => string;
+    /**
+     * How this harness SPELLS the MCP tool names of a peaks server.
+     *
+     * Optional, like `skillInstall?` / `standardsProfile?` / `compact?`: an adapter
+     * that leaves it undefined declares "this harness has no MCP tool surface I can
+     * name", and every consumer treats that as "nothing to match" rather than as an
+     * error.
+     *
+     * It exists because one tool has SEVERAL spellings. A server registered
+     * directly and the same server arriving through a plugin produce different
+     * tool names, and an enforcement matcher written against one of them does not
+     * fire on the other — silently. Declaring them here is what lets the
+     * pre-tool branch and the installed hook entry agree on the full set.
+     *
+     * `resolveCallerId` above is the precedent for the placement rule: a vendor's
+     * naming convention is vendor signal, and vendor signal is funnelled through
+     * the adapter so no other module has to know it.
+     */
+    readonly mcp?: IdeMcpProfile;
+    /**
+     * How this harness REGISTERS an MCP server (spec §8.3), consumed by
+     * `peaks mcp install/uninstall`. Optional, like `mcp` above: leaving it
+     * undefined declares "no registration entry peaks may call", and the install
+     * reads that as "nothing to do". See `ide-mcp-install-types.ts`.
+     */
+    readonly mcpInstall?: IdeMcpInstallProfile;
+}
+/**
+ * The MCP naming profile of one harness.
+ *
+ * Deliberately ONE field. Templates both MATCH a concrete tool name and
+ * CONSTRUCT one, which is what lets a conformance test build a call for a
+ * channel it has never seen (spec §6.3) instead of restating the harness's
+ * naming in the test — a restatement that would go stale the moment a channel
+ * is added.
+ */
+export interface IdeMcpProfile {
+    /**
+     * Tool-name templates. `*` is replaced by the bare MCP tool id, so
+     * `mcp__peaks__*` describes every tool of a server registered under the name
+     * `peaks` on the direct channel.
+     */
+    readonly toolNameTemplates: readonly string[];
 }
 /**
  * Per-IDE standards-file location + format profile. Used by the
- * `peaks standards init` dispatch layer (slice 011) to write the
  * project-level standards files at the IDE-specific path, not the
  * Claude Code hardcoded one. Adapters that omit this field trigger
  * the legacy Claude Code path with a stderr warning.

package/dist/services/ide/mcp-tool-matcher.d.ts

@@ -0,0 +1,34 @@
+import type { IdeAdapter, IdeMcpProfile } from './ide-types.js';
+/** The placeholder an adapter's tool-name template uses for the bare tool id. */
+export declare const TOOL_ID_PLACEHOLDER = "*";
+/** A concrete tool name matched back to the adapter template that produced it. */
+export interface McpToolMatch {
+    /** The bare tool id — the part the template's placeholder stood for. */
+    readonly toolId: string;
+    /** The template that matched, so a caller can report which channel fired. */
+    readonly template: string;
+}
+/** The declared profile, or an empty one for an adapter that opts out. */
+export declare function mcpProfileOf(adapter: IdeAdapter): IdeMcpProfile | undefined;
+/** Every tool-name template the adapter declares, in declaration order. */
+export declare function mcpToolNameTemplates(adapter: IdeAdapter): readonly string[];
+/** The concrete harness tool name for a tool id under one template. */
+export declare function mcpToolName(template: string, toolId: string): string;
+/**
+ * The tool id a concrete name carries under one template, or `undefined`. The
+ * template is anchored: an unanchored match would let a longer name smuggle the
+ * id (and would make `matchMcpToolName` order-dependent).
+ */
+export declare function mcpToolIdFrom(template: string, toolName: string): string | undefined;
+/**
+ * Match a concrete harness tool name against every template the adapter
+ * declares, in declaration order. This is the ONE entry point the enforcement
+ * branch uses, so "which channels are covered" is answered by the adapter alone.
+ */
+export declare function matchMcpToolName(adapter: IdeAdapter, toolName: string): McpToolMatch | undefined;
+/**
+ * The PreToolUse `matcher` source covering every declared channel, ready to be
+ * joined into a hook entry's matcher field. `*` becomes `.*` and everything else
+ * is escaped, so the source matches exactly the names the templates describe.
+ */
+export declare function mcpHookMatcher(adapter: IdeAdapter): string | undefined;

package/dist/services/ide/mcp-tool-matcher.js

@@ -0,0 +1,84 @@
+// src/services/ide/mcp-tool-matcher.ts
+//
+// The vendor-translation layer for MCP tool NAMES (spec §6.3, §13).
+//
+// An MCP tool's name is harness-specific AND channel-specific: the very same
+// `peaks_status` tool is spelled one way when the server is registered directly
+// and another way when it arrives through a plugin. A matcher hard-coded against
+// one spelling keeps working on the channel it was written for and SILENTLY
+// stops firing on the other — the failure mode is an enforcement layer that
+// reports nothing because it never ran. So the spellings are declared by the
+// adapter (`IdeAdapter.mcp`) and this module is the only place that turns a
+// declaration into (a) a match against a concrete tool name and (b) the
+// PreToolUse matcher written into the harness's settings.
+//
+// Vendor names do not belong here: every string below is either generic syntax
+// or comes from the adapter. The isolation zone lives in `adapters/`.
+/** The placeholder an adapter's tool-name template uses for the bare tool id. */
+export const TOOL_ID_PLACEHOLDER = '*';
+/** The declared profile, or an empty one for an adapter that opts out. */
+export function mcpProfileOf(adapter) {
+    return adapter.mcp;
+}
+/** Every tool-name template the adapter declares, in declaration order. */
+export function mcpToolNameTemplates(adapter) {
+    return adapter.mcp?.toolNameTemplates ?? [];
+}
+/** Escape a literal segment so it cannot act as a pattern metacharacter. */
+function escapeLiteral(value) {
+    return value.replace(/[.*+?^${}()|[\]\\]/g, '\\$&');
+}
+/**
+ * Split a template on its placeholder. A template must carry EXACTLY one
+ * placeholder: zero would make the tool id unaddressable, and two would make the
+ * captured id ambiguous. Both are adapter bugs, so they throw with the template
+ * in the message rather than degrading to a matcher that matches nothing.
+ */
+function splitTemplate(template) {
+    const parts = template.split(TOOL_ID_PLACEHOLDER);
+    if (parts.length !== 2 || parts[0] === undefined || parts[1] === undefined) {
+        throw new Error(`MCP tool-name template '${template}' must contain exactly one '${TOOL_ID_PLACEHOLDER}' placeholder.`);
+    }
+    return [parts[0], parts[1]];
+}
+/** The concrete harness tool name for a tool id under one template. */
+export function mcpToolName(template, toolId) {
+    const [prefix, suffix] = splitTemplate(template);
+    return `${prefix}${toolId}${suffix}`;
+}
+/**
+ * The tool id a concrete name carries under one template, or `undefined`. The
+ * template is anchored: an unanchored match would let a longer name smuggle the
+ * id (and would make `matchMcpToolName` order-dependent).
+ */
+export function mcpToolIdFrom(template, toolName) {
+    const [prefix, suffix] = splitTemplate(template);
+    const pattern = new RegExp(`^${escapeLiteral(prefix)}(.*)${escapeLiteral(suffix)}$`);
+    const matched = pattern.exec(toolName);
+    return matched?.[1];
+}
+/**
+ * Match a concrete harness tool name against every template the adapter
+ * declares, in declaration order. This is the ONE entry point the enforcement
+ * branch uses, so "which channels are covered" is answered by the adapter alone.
+ */
+export function matchMcpToolName(adapter, toolName) {
+    for (const template of mcpToolNameTemplates(adapter)) {
+        const toolId = mcpToolIdFrom(template, toolName);
+        if (toolId !== undefined)
+            return { toolId, template };
+    }
+    return undefined;
+}
+/**
+ * The PreToolUse `matcher` source covering every declared channel, ready to be
+ * joined into a hook entry's matcher field. `*` becomes `.*` and everything else
+ * is escaped, so the source matches exactly the names the templates describe.
+ */
+export function mcpHookMatcher(adapter) {
+    const sources = mcpToolNameTemplates(adapter).map((template) => {
+        const [prefix, suffix] = splitTemplate(template);
+        return `${escapeLiteral(prefix)}.*${escapeLiteral(suffix)}`;
+    });
+    return sources.length === 0 ? undefined : sources.join('|');
+}

package/dist/services/ide/resource-profile.d.ts

@@ -1,7 +1,6 @@
 /**
  * Resource profile accessors for the per-IDE dispatch layer.
  *
- * Slice #011-2026-06-07-ide-adapter-resource-profile introduced two new
  * optional fields on the `IdeAdapter` interface:
  *
  *   - `standardsProfile` — where the IDE reads its project-level

package/dist/services/job/job-commit-verification.d.ts

@@ -1,10 +1,8 @@
 /**
- * D2 (rid 2026-10-03-job-ledger-truthfulness) — can this commit sha be proved to
  * exist in this repository?
  *
  * WHY THIS EXISTS. `peaks job checkpoint --state done --commit-sha <sha>` checked
  * only `sha.length >= 7` (`job-orchestrator.ts:55`), so a typo'd sha was accepted
- * and written into the ledger. Measured 2026-10-02 on `2026-10-02-c-wave9`, and
  * again for this slice against the committed build: a 12-hex string that
  * `git cat-file` calls `Not a valid object name` produced `ok: true` and a
  * `state.json` whose `commitSha` named it. A ledger that points at a commit which

package/dist/services/job/job-commit-verification.js

@@ -1,10 +1,8 @@
 /**
- * D2 (rid 2026-10-03-job-ledger-truthfulness) — can this commit sha be proved to
  * exist in this repository?
  *
  * WHY THIS EXISTS. `peaks job checkpoint --state done --commit-sha <sha>` checked
  * only `sha.length >= 7` (`job-orchestrator.ts:55`), so a typo'd sha was accepted
- * and written into the ledger. Measured 2026-10-02 on `2026-10-02-c-wave9`, and
  * again for this slice against the committed build: a 12-hex string that
  * `git cat-file` calls `Not a valid object name` produced `ok: true` and a
  * `state.json` whose `commitSha` named it. A ledger that points at a commit which

package/dist/services/job/job-orchestrator.d.ts

@@ -36,7 +36,6 @@ export declare class JobOrchestrator {
     constructor(store: JobStateStore);
     init(input: JobInitInput): JobState;
     /**
-     * D1 (rid 2026-10-03-job-ledger-truthfulness) — register one more slice on an
      * existing job.
      *
      * WHY THIS EXISTS. The slice list was decided once, at `peaks job init

package/dist/services/job/job-orchestrator.js

@@ -27,7 +27,6 @@ export class JobOrchestrator {
         return this.store.init(input);
     }
     /**
-     * D1 (rid 2026-10-03-job-ledger-truthfulness) — register one more slice on an
      * existing job.
      *
      * WHY THIS EXISTS. The slice list was decided once, at `peaks job init