peaks-cli 1.3.4 → 1.3.6

package/dist/src/cli/commands/hook-handle.d.ts

@@ -7,10 +7,10 @@ import { type ProgramIO } from '../cli-helpers.js';
  *   1. 读 stdin
  *   2. auto-detect 来源 IDE(env / stdin shape / cwd)
  *   3. 归一化到 peaks canonical schema
- *   4. dispatch 到内部 peaks 逻辑(目前:gate enforce 或 progress start)
+ *   4. dispatch 到内部 peaks 逻辑(目前:gate enforce)
  *   5. 用 IDE 期望的格式发回决策
  *
- * Slice #1 阶段:peaks hook handle 与 peaks gate enforce / peaks progress start
+ * Slice #1 阶段:peaks hook handle 与 peaks gate enforce
  * 并存(后者内部走 hook-translator)。Slice #2 把 IDE settings 改成调用
  * peaks hook handle 即可。Slice #3 删除旧命令。
  */

package/dist/src/cli/commands/hook-handle.js

@@ -30,18 +30,18 @@ async function readStdin() {
  *   1. 读 stdin
  *   2. auto-detect 来源 IDE(env / stdin shape / cwd)
  *   3. 归一化到 peaks canonical schema
- *   4. dispatch 到内部 peaks 逻辑(目前:gate enforce 或 progress start)
+ *   4. dispatch 到内部 peaks 逻辑(目前:gate enforce)
  *   5. 用 IDE 期望的格式发回决策
  *
- * Slice #1 阶段:peaks hook handle 与 peaks gate enforce / peaks progress start
+ * Slice #1 阶段:peaks hook handle 与 peaks gate enforce
  * 并存(后者内部走 hook-translator)。Slice #2 把 IDE settings 改成调用
  * peaks hook handle 即可。Slice #3 删除旧命令。
  */
 export function registerHookHandleCommand(program, io) {
-    const hook = program.command('hook').description('Peaks 自有 hook 协议单一入口（slice #1 新增；后续 slice 将逐步替代 gate enforce / progress start）');
+    const hook = program.command('hook').description('Peaks 自有 hook 协议单一入口（slice #1 新增；后续 slice 将逐步替代 gate enforce）');
     addJsonOption(hook
         .command('handle')
-        .description('Read stdin hook payload, auto-detect IDE, dispatch to peaks gate/progress logic, output IDE-formatted decision')
+        .description('Read stdin hook payload, auto-detect IDE, dispatch to peaks gate-enforce logic, output IDE-formatted decision')
         .option('--project <path>', 'project the gates evaluate against (default: current directory)', '.')).action(async (options) => {
         try {
             const raw = await readStdin();
@@ -74,7 +74,7 @@ export function registerHookHandleCommand(program, io) {
                 rawIdeFormat: ide,
                 rawPayload: parsed
             });
-            // Dispatch by toolName. For slice #1, we only handle Bash and Task.
+            // Dispatch by toolName. For slice #1+, we only handle Bash. Task tool sub-agent dispatch goes through `peaks sub-agent dispatch` (slice #009) and does not need a hook entry.
             // Other tools: allow (no-op; future events will be added here).
             if (hook.toolName === 'Bash' && typeof fallbackCommand === 'string' && fallbackCommand.trim().length > 0) {
                 // Lazy import to avoid circular: peaks gate enforce logic
@@ -89,11 +89,6 @@ export function registerHookHandleCommand(program, io) {
                     return;
                 }
             }
-            else if (hook.toolName === 'Task') {
-                // peaks progress start is a fire-and-forget; do not block hook.handle.
-                // Slice #1: simply acknowledge (no terminal spawn from hook handle itself;
-                // the legacy `peaks progress start` command still does that).
-            }
             const allow = formatDecisionResponse(ide, 'allow');
             io.stdout(allow.stdout);
             if (options.json === true) {

package/dist/src/cli/commands/hooks-commands.js

@@ -1,7 +1,9 @@
+import { existsSync } from 'node:fs';
 import { fail, ok } from '../../shared/result.js';
 import { addJsonOption, printResult, getErrorMessage } from '../cli-helpers.js';
 import { findProjectRoot } from '../../services/config/config-safety.js';
-import { applyHookInstall, planHookInstall, readHookStatus, removeHookInstall } from '../../services/skills/hooks-settings-service.js';
+import { applyHookInstall, planHookInstall, readHookStatus, readInstalledEntriesFromSettings, removeHookInstall } from '../../services/skills/hooks-settings-service.js';
+import { readJsonObjectFile } from '../../services/ide/shared/atomic-json.js';
 import { detectIdeFromContext } from '../../services/ide/hook-translator.js';
 import { getAdapter } from '../../services/ide/ide-registry.js';
 function resolveScope(options) {
@@ -23,60 +25,63 @@ function resolveIdeForCommand(options, projectRoot) {
     }
     return detectIdeFromContext({ env: process.env, cwd: projectRoot ?? process.cwd(), parsedStdin: null });
 }
-// Slice #3: compute the per-IDE peaks hook entries for the CLI response
-// summary. Replaces the slice #1 PEAKS_HOOK_ENTRIES constant which was
-// hardcoded to claude-code values. Slice 2026-06-06-sub-agent-spawn-bug-
-// and-decouple: the sub-agent progress matcher now reads from
-// `adapter.subAgentToolMatcher` instead of being hardcoded to 'Task', so
-// every IDE self-reports its sub-agent tool name (claude-code: 'Task',
-// future adapters: whatever the adapter declares).
-function listInstalledEntriesForIde(ide) {
+/**
+ * Slice #014: compute the per-IDE peaks hook entries for the install /
+ * dry-run RESPONSE SUMMARY. This is the *desired* shape (what the install
+ * WOULD write), not what is on disk. The status command uses a different
+ * helper (`readInstalledEntriesFromSettings`) that reads the actual
+ * settings.json.
+ *
+ * After slice #014 only the gate-enforce entry is ever installed
+ * (the legacy progress-start surface is gone). The summary mirrors
+ * the install shape so the JSON envelope doesn't claim a hook the
+ * service did not write.
+ */
+function listExpectedEntriesForIde(ide, _skipProgress = false) {
     const adapter = getAdapter(ide);
     if (ide === 'trae') {
-        return [
-            { matcher: adapter.toolMatcher, sentinel: 'peaks hook handle' },
-            { matcher: adapter.subAgentToolMatcher, sentinel: 'peaks progress start' }
-        ];
+        return [{ matcher: adapter.toolMatcher, sentinel: 'peaks hook handle' }];
     }
-    // Default (claude-code) and any future registered adapters.
-    return [
-        { matcher: adapter.toolMatcher, sentinel: 'peaks gate enforce' },
-        { matcher: adapter.subAgentToolMatcher, sentinel: 'peaks progress start' }
-    ];
+    return [{ matcher: adapter.toolMatcher, sentinel: 'peaks gate enforce' }];
 }
 export function registerHooksCommands(program, io) {
     const hooks = program
         .command('hooks')
-        .description("Manage the Peaks-managed hook entries in the adapter's settings.json (default: .claude/settings.json for Claude, .trae/settings.json for Trae): (1) gate-enforce hook (SOP gate), (2) progress-start hook (auto-spawn sub-agent progress terminal). Both are installed / removed together. The IDE is auto-detected from env / cwd; override with --ide <id>.");
+        .description("Manage the Peaks-managed hook entry in the adapter's settings.json (default: .claude/settings.json for Claude, .trae/settings.json for Trae). Slice #014: the only installed entry is the gate-enforce hook (SOP gate). The legacy progress-start hook (auto-spawn sub-agent progress terminal) is no longer installed — sub-agent progress is now surfaced via the dispatch + heartbeat flow (`peaks sub-agent dispatch` / `peaks sub-agent heartbeat`). The IDE is auto-detected from env / cwd; override with --ide <id>.");
     addJsonOption(hooks
         .command('install')
-        .description(`Install all peaks-managed hook entries into the adapter's settings.json. Idempotent: re-runs are no-ops. Project scope by default.`)
+        .description(`Install the peaks-managed gate-enforce hook entry into the adapter's settings.json. Slice #014: only the gate-enforce entry is installed; the legacy progress-start entry is no longer installed. Idempotent: re-runs are no-ops. Project scope by default.`)
         .option('--global', 'install into the user-level ~/.claude/settings.json instead of the project')
         .option('--project <path>', 'project root path (auto-detected from cwd when omitted)')
         .option('--ide <id>', "target adapter id (claude-code | trae); default: auto-detect from env/cwd")
-        .option('--dry-run', 'show what would change without writing')).action((options) => {
+        .option('--dry-run', 'show what would change without writing')
+        .option('--no-progress', 'skip the progress-start PreToolUse hook entry; install ONLY the gate-enforce entry')).action((options) => {
         const scope = resolveScope(options);
         const projectRoot = resolveProjectRoot(scope, options.project);
         const ide = resolveIdeForCommand(options, projectRoot);
+        const skipProgress = options.progress === false;
         try {
             if (options.dryRun === true) {
-                const plan = planHookInstall(scope, projectRoot, { ide });
-                const dryRunEntries = listInstalledEntriesForIde(ide);
+                const plan = planHookInstall(scope, projectRoot, { ide, skipProgress });
+                const dryRunEntries = listExpectedEntriesForIde(ide, skipProgress);
                 printResult(io, ok('hooks.install', {
                     ...plan,
                     ide,
                     applied: false,
                     dryRun: true,
+                    skipProgress,
                     entries: dryRunEntries
                 }, [], [`would install ${dryRunEntries.length} peaks-managed hook entries`]), options.json);
                 return;
             }
-            const result = applyHookInstall(scope, projectRoot, { ide });
+            const result = applyHookInstall(scope, projectRoot, { ide, skipProgress });
             // Slice #3: build the per-IDE entries summary from the actual installed
             // entries, not the slice #1 PEAKS_HOOK_ENTRIES constant (which is the
             // claude-code default). The user's JSON envelope must reflect the IDE
-            // they targeted.
-            const installedEntries = listInstalledEntriesForIde(ide);
+            // they targeted. Slice #014: the install only emits the gate-enforce
+            // entry; the summary mirrors the install shape, NOT a hardcoded
+            // expected list.
+            const installedEntries = listExpectedEntriesForIde(ide, skipProgress);
             const nextActions = result.applied
                 ? [
                     'Restart the IDE (or reload the workspace) so the hook entries take effect',
@@ -87,18 +92,19 @@ export function registerHooksCommands(program, io) {
                 ...result,
                 ide,
                 dryRun: false,
+                skipProgress,
                 entries: installedEntries.map((e) => ({ matcher: e.matcher, sentinel: e.sentinel }))
             }, [], nextActions), options.json);
         }
         catch (error) {
             const message = getErrorMessage(error);
-            printResult(io, fail('hooks.install', 'HOOKS_INSTALL_FAILED', message, { scope, ide, applied: false }, [message]), options.json);
+            printResult(io, fail('hooks.install', 'HOOKS_INSTALL_FAILED', message, { scope, ide, applied: false, skipProgress }, [message]), options.json);
             process.exitCode = 1;
         }
     });
     addJsonOption(hooks
         .command('uninstall')
-        .description("Remove all peaks-managed hook entries (gate-enforce + progress-start) from the target settings.json. Third-party hooks are preserved.")
+        .description("Remove the peaks-managed gate-enforce hook entry from the target settings.json. Any legacy progress-start entry that a pre-#014 install left behind is also removed (sentinel-based scan). Third-party hooks are preserved.")
         .option('--global', 'remove from the user-level ~/.claude/settings.json instead of the project')
         .option('--project <path>', 'project root path (auto-detected from cwd when omitted)')
         .option('--ide <id>', 'target adapter id (claude-code | trae); default: auto-detect from env/cwd')).action((options) => {
@@ -126,10 +132,19 @@ export function registerHooksCommands(program, io) {
         const ide = resolveIdeForCommand(options, projectRoot);
         try {
             const status = readHookStatus(scope, projectRoot, { ide });
+            // Slice #014: read the ACTUAL on-disk entries (post-install shape),
+            // not the IDE-EXPECTED list. Pre-#014 `listInstalledEntriesForIde`
+            // returned the expected list and reported `entries: [Bash, Task]`
+            // even when the file only had `Bash`. The new helper reads the
+            // file and reports whatever peaks-managed entries are present,
+            // including any legacy progress-start entry that a pre-#014
+            // install left behind.
+            const settingsPath = status.settingsPath;
+            const settings = existsSync(settingsPath) ? readJsonObjectFile(settingsPath) : {};
             printResult(io, ok('hooks.status', {
                 ...status,
                 ide,
-                entries: listInstalledEntriesForIde(ide)
+                entries: readInstalledEntriesFromSettings(settings, ide)
             }), options.json);
         }
         catch (error) {

package/dist/src/cli/commands/project-commands.js

@@ -78,7 +78,13 @@ export function registerProjectCommands(program, io) {
         .description('Scan a session artifact directory and extract <!-- peaks-memory:start --> blocks into .peaks/memory/')
         .requiredOption('--session-id <id>', 'session id (e.g. 2026-05-29-session-89ff35)')
         .requiredOption('--project <path>', 'target project root')
-        .option('--dry-run', 'preview writes without changing files', true)
+        // Slice #015: drop the `--dry-run true` default. With the default
+        // set to true, `options.dryRun === true && options.apply === true`
+        // fired on every `--apply` call (because dryRun was true by
+        // default), permanently breaking `--apply`. `--dry-run` is now
+        // opt-in; the mutual-exclusion check below is correct without a
+        // special-case.
+        .option('--dry-run', 'preview writes without changing files')
         .option('--apply', 'write extracted memories into .peaks/memory/')).action((options) => {
         if (options.dryRun === true && options.apply === true) {
             printResult(io, fail('project.memories:extract', 'INVALID_MEMORY_EXTRACT_FLAGS', 'Use either --dry-run or --apply, not both', { sessionId: options.sessionId, projectRoot: options.project }, ['Run without --apply to preview writes, or pass --apply to write memories']), options.json);

package/dist/src/cli/commands/workspace-commands.js

@@ -449,8 +449,7 @@ export async function resolveFirstTimeHooksInstall(options) {
     // effectiveMode === 'ask' AND TTY: prompt once.
     process.stderr.write('\nPeaks-Cli: install the PreToolUse hooks for this project now?\n' +
         '  → Bash matcher: `peaks gate enforce` (SOP gate enforcement)\n' +
-        '  → Task matcher: `peaks progress start` (auto-spawn sub-agent progress terminal)\n' +
-        'Both run on every Claude Code tool call without further prompting. The decision is sticky\n' +
+        'The gate-enforce hook runs on every Claude Code tool call without further prompting. The decision is sticky\n' +
         '(recorded in .peaks/.peaks-init-hooks-decision.json) and re-runs of `workspace init` will\n' +
         'honour it. Re-run with --install-hooks=skip or --install-hooks=auto to override.\n\n' +
         'Install now? [Y/n]: ');

package/dist/src/cli/program.js

@@ -7,10 +7,11 @@ import { registerCoreAndArtifactCommands } from './commands/core-artifact-comman
 import { registerWorkflowCommands } from './commands/workflow-commands.js';
 import { registerCapabilityWorkerConfigAndSCCommands } from './commands/capability-worker-config-sc-commands.js';
 import { registerCodegraphCommands } from './commands/codegraph-commands.js';
-import { registerMcpCommands } from './commands/mcp-commands.js';
 import { registerOpenSpecCommands } from './commands/openspec-commands.js';
 import { registerPerfCommands } from './commands/perf-commands.js';
-import { registerProgressCommands } from './commands/progress-commands.js';
+// Slice #014: peaks progress * CLI surface deleted (replaced by sub-agent
+// dispatch + heartbeat, slice #009 + #010). Sub-agent progress is
+// surfaced via `peaks sub-agent dispatch|heartbeat|share`.
 import { registerProjectCommands } from './commands/project-commands.js';
 import { registerRequestCommands } from './commands/request-commands.js';
 import { registerScanCommands } from './commands/scan-commands.js';
@@ -85,10 +86,8 @@ Run peaks (no arguments) for a quickstart. You likely want one of:
     registerWorkflowCommands(program, io);
     registerCapabilityWorkerConfigAndSCCommands(program, io);
     registerCodegraphCommands(program, io);
-    registerMcpCommands(program, io);
     registerOpenSpecCommands(program, io);
     registerPerfCommands(program, io);
-    registerProgressCommands(program, io);
     registerProjectCommands(program, io);
     registerRequestCommands(program, io);
     registerScanCommands(program, io);

package/dist/src/services/dashboard/project-dashboard-service.d.ts

@@ -1,6 +1,5 @@
 import { type RequestArtifactRole, type RequestArtifactSummary } from '../artifacts/request-artifact-service.js';
 import type { OpenSpecChangeSummary } from '../openspec/openspec-types.js';
-import type { McpScanReport } from '../mcp/mcp-types.js';
 import type { CapabilityItem } from '../recommendations/recommendation-types.js';
 import { type SkillPresence } from '../skills/skill-presence-service.js';
 export type ProjectDashboardRequests = {
@@ -19,10 +18,6 @@ export type ProjectDashboardUnderstand = {
     graphPath: string;
     parseError?: string;
 };
-export type ProjectDashboardMcp = {
-    servers: McpScanReport['servers'];
-    scopes: McpScanReport['scopes'];
-};
 export type ProjectDashboardDoctor = {
     ok: boolean;
     passed: number;
@@ -57,7 +52,6 @@ export type ProjectDashboardRunbookHealth = {
 };
 export type ProjectDashboardCapabilities = {
     count: number;
-    mcpCount: number;
     sample: Array<Pick<CapabilityItem, 'capabilityId' | 'name' | 'itemType' | 'category'>>;
 };
 export type ProjectDashboardSkillPresence = {
@@ -76,7 +70,6 @@ export type ProjectDashboard = {
     requests: ProjectDashboardRequests;
     openspec: ProjectDashboardOpenSpec;
     understand: ProjectDashboardUnderstand;
-    mcp: ProjectDashboardMcp;
     doctor: ProjectDashboardDoctor;
     runbookHealth: ProjectDashboardRunbookHealth;
     capabilities: ProjectDashboardCapabilities;

package/dist/src/services/dashboard/project-dashboard-service.js

@@ -1,6 +1,5 @@
 import { listRequestArtifacts } from '../artifacts/request-artifact-service.js';
 import { scanOpenSpec } from '../openspec/openspec-scan-service.js';
-import { scanMcpServers } from '../mcp/mcp-scan-service.js';
 import { scanUnderstandAnything } from '../understand/understand-scan-service.js';
 import { seedCapabilityItems } from '../recommendations/capability-seed-items.js';
 import { requiredSkillNames } from '../../shared/paths.js';
@@ -78,7 +77,6 @@ function buildCapabilitiesSummary(sampleSize) {
     const items = seedCapabilityItems;
     return {
         count: items.length,
-        mcpCount: items.filter((item) => item.itemType === 'mcp').length,
         sample: items.slice(0, sampleSize).map((item) => ({
             capabilityId: item.capabilityId,
             name: item.name,
@@ -109,10 +107,9 @@ export async function loadProjectDashboard(options) {
     const clock = options.clock ?? defaultClock;
     const sampleSize = options.sampleCapabilities ?? 8;
     const okPolicy = options.okPolicy ?? 'workspace-only';
-    const [items, openspecReport, mcpReport, understandReport, doctorAndRunbook] = await Promise.all([
+    const [items, openspecReport, understandReport, doctorAndRunbook] = await Promise.all([
         listRequestArtifacts({ projectRoot: options.projectRoot }),
         scanOpenSpec({ openspecRoot: `${options.projectRoot}/openspec` }),
-        scanMcpServers({ projectRoot: options.projectRoot }),
         scanUnderstandAnything({ projectRoot: options.projectRoot }),
         loadDoctorAndRunbookHealth(options.doctorReport, options.runbookHealth)
     ]);
@@ -142,10 +139,6 @@ export async function loadProjectDashboard(options) {
             graphPath: understandReport.graph.path,
             ...(understandReport.graph.parseError !== undefined ? { parseError: understandReport.graph.parseError } : {})
         },
-        mcp: {
-            servers: mcpReport.servers,
-            scopes: mcpReport.scopes
-        },
         doctor: doctorAndRunbook.doctor,
         runbookHealth: doctorAndRunbook.runbookHealth,
         capabilities: buildCapabilitiesSummary(sampleSize),

package/dist/src/services/dispatch/sub-agent-dispatcher.d.ts

@@ -8,29 +8,29 @@
  * here, never leaked to SKILL.md.
  *
  * Why this exists:
- *   - Prior SKILL.md hardcoded `Task(subagent_type="general-purpose", ...)`
- *     which made peaks-cli depend on Claude Code's specific sub-agent
- *     tool name. Adding a new IDE (Trae, future Cursor, etc.) required
- *     editing every SKILL.md that mentioned sub-agent dispatch.
- *   - This file (plus the per-IDE adapter wiring) collapses all
- *     per-IDE sub-agent specifics to a single `SubAgentDispatcher`
- *     instance per adapter. SKILL.md now only references
- *     `peaks sub-agent dispatch <role>`, and the IDE-private tool
- *     name flows through the returned `data.toolCall` at runtime.
+ * - Prior SKILL.md hardcoded `Task(subagent_type="general-purpose", ...)`
+ * which made peaks-cli depend on Claude Code's specific sub-agent
+ * tool name. Adding a new IDE (Trae, future Cursor, etc.) required
+ * editing every SKILL.md that mentioned sub-agent dispatch.
+ * - This file (plus the per-IDE adapter wiring) collapses all
+ * per-IDE sub-agent specifics to a single `SubAgentDispatcher`
+ * instance per adapter. SKILL.md now only references
+ * `peaks sub-agent dispatch <role>`, and the IDE-private tool
+ * name flows through the returned `data.toolCall` at runtime.
  *
  * Cross-reference: PRD #002 G1 (AC-1..AC-5); RD tech-doc-002 §2.
  */
 /**
  * Role string namespace. Soft whitelist — the CLI does NOT hard-validate
- * specific role names. Empirically observed (peaks-qa SKILL.md): 3 top
- * roles + 3 sub-roles + arbitrary business subdivisions:
+ * specific role names. Empirically observed (peaks-qa SKILL.md):3 top
+ * roles +3 sub-roles + arbitrary business subdivisions:
  *
- *   - top:           rd | qa | ui | txt | general-purpose
- *   - qa sub-roles:  qa-business | qa-perf | qa-security
- *   - business细分:  qa-business-regression | qa-business-api
- *                    | qa-business-frontend | ...
- *   - promotable:    prd-business | prd-technical | prd-ux |
- *                    ui-visual | ui-flow | ui-component | ...
+ * - top: rd | qa | ui | txt | general-purpose
+ * - qa sub-roles: qa-business | qa-perf | qa-security
+ * - business细分: qa-business-regression | qa-business-api
+ * | qa-business-frontend | ...
+ * - promotable: prd-business | prd-technical | prd-ux |
+ * ui-visual | ui-flow | ui-component | ...
  *
  * Any non-empty string is a valid role. CLI emits a "soft whitelist"
  * hint in --help but does not reject unknown values.
@@ -64,43 +64,48 @@ export interface SubAgentDispatchInput {
  */
 export interface SubAgentDispatcher {
     /**
-     * Short label used in envelope `ide` field and CLI help text.
-     * e.g. "claude-code" / "trae" / "null".
-     */
+    * Short label used in envelope `ide` field and CLI help text.
+    * e.g. "claude-code" / "trae" / "null".
+    */
     readonly label: string;
     /**
-     * Whether this dispatcher supports dispatching a given role.
-     * claude-code returns true for all non-empty strings; trae is
-     * byte-identical (UNVERIFIED pending real Trae dogfood);
-     * null-dispatcher always returns false.
-     */
+    * Whether this dispatcher supports dispatching a given role.
+    * claude-code returns true for all non-empty strings; trae is
+    * byte-identical (UNVERIFIED pending real Trae dogfood);
+    * null-dispatcher always returns false.
+    */
     supportsRole(role: SubAgentRole): boolean;
     /**
-     * Build the IDE-specific tool call descriptor for a dispatch.
-     * Must be pure: no I/O, no side effects. The CLI wraps the
-     * returned descriptor in its JSON envelope.
-     */
+    * Build the IDE-specific tool call descriptor for a dispatch.
+    * Must be pure: no I/O, no side effects. The CLI wraps the
+    * returned descriptor in its JSON envelope.
+    */
     buildToolCall(input: SubAgentDispatchInput): SubAgentToolCall;
 }
 /**
  * Claude Code dispatcher. Real, byte-level implementation.
  *
- *   - `supportsRole`: any non-empty string (Claude Code's
- *     `general-purpose` sub-agent accepts any prompt).
- *   - `buildToolCall`: returns `{name: 'Task', args: {subagent_type,
- *     description, prompt}}` — the exact shape the `Task` tool
- *     in Claude Code expects.
+ * - `supportsRole`: any non-empty string (Claude Code's
+ * `general-purpose` sub-agent accepts any prompt).
+ * - `buildToolCall`: returns `{name: 'Task', args: {subagent_type,
+ * description, prompt}}` — the exact shape the `Task` tool
+ * in Claude Code expects.
  */
 export declare const claudeCodeSubAgentDispatcher: SubAgentDispatcher;
 /**
  * Trae dispatcher. UNVERIFIED — Trae sub-agent tool name TBD on real
  * dogfood. Byte-level identical to claude-code by design so:
- *   1. The slice #008 `subAgentToolMatcher: 'Task'` install entry
- *      stays byte-stable (the generated `.trae/settings.json` does
- *      not change).
- *   2. The dispatcher's return shape is uniform across both
- *      adapters — a single byte-equality test can verify the
- *      placeholder contract.
+ * - The dispatcher's return shape is uniform across both adapters
+ * — a single byte-equality test can verify the placeholder
+ * contract.
+ * - Future real Trae dogfood can replace the body of
+ * `buildToolCall` without breaking the adapter contract.
+ *
+ * Slice #014: the legacy `subAgentToolMatcher: 'Task'` install entry
+ * is gone — the field is removed from `IdeAdapter`. Slice #009+
+ * dispatched sub-agents directly, not via a PreToolUse hook. The Trae
+ * dispatcher remains a placeholder so the dispatch surface is uniform
+ * across adapters.
  *
  * When real Trae dogfood lands, replace the body of `buildToolCall`
  * with Trae's actual sub-agent tool name + args shape. The interface

package/dist/src/services/dispatch/sub-agent-dispatcher.js

@@ -8,26 +8,26 @@
  * here, never leaked to SKILL.md.
  *
  * Why this exists:
- *   - Prior SKILL.md hardcoded `Task(subagent_type="general-purpose", ...)`
- *     which made peaks-cli depend on Claude Code's specific sub-agent
- *     tool name. Adding a new IDE (Trae, future Cursor, etc.) required
- *     editing every SKILL.md that mentioned sub-agent dispatch.
- *   - This file (plus the per-IDE adapter wiring) collapses all
- *     per-IDE sub-agent specifics to a single `SubAgentDispatcher`
- *     instance per adapter. SKILL.md now only references
- *     `peaks sub-agent dispatch <role>`, and the IDE-private tool
- *     name flows through the returned `data.toolCall` at runtime.
+ * - Prior SKILL.md hardcoded `Task(subagent_type="general-purpose", ...)`
+ * which made peaks-cli depend on Claude Code's specific sub-agent
+ * tool name. Adding a new IDE (Trae, future Cursor, etc.) required
+ * editing every SKILL.md that mentioned sub-agent dispatch.
+ * - This file (plus the per-IDE adapter wiring) collapses all
+ * per-IDE sub-agent specifics to a single `SubAgentDispatcher`
+ * instance per adapter. SKILL.md now only references
+ * `peaks sub-agent dispatch <role>`, and the IDE-private tool
+ * name flows through the returned `data.toolCall` at runtime.
  *
  * Cross-reference: PRD #002 G1 (AC-1..AC-5); RD tech-doc-002 §2.
  */
 /**
  * Claude Code dispatcher. Real, byte-level implementation.
  *
- *   - `supportsRole`: any non-empty string (Claude Code's
- *     `general-purpose` sub-agent accepts any prompt).
- *   - `buildToolCall`: returns `{name: 'Task', args: {subagent_type,
- *     description, prompt}}` — the exact shape the `Task` tool
- *     in Claude Code expects.
+ * - `supportsRole`: any non-empty string (Claude Code's
+ * `general-purpose` sub-agent accepts any prompt).
+ * - `buildToolCall`: returns `{name: 'Task', args: {subagent_type,
+ * description, prompt}}` — the exact shape the `Task` tool
+ * in Claude Code expects.
  */
 export const claudeCodeSubAgentDispatcher = {
     label: 'claude-code',
@@ -44,12 +44,17 @@ export const claudeCodeSubAgentDispatcher = {
 /**
  * Trae dispatcher. UNVERIFIED — Trae sub-agent tool name TBD on real
  * dogfood. Byte-level identical to claude-code by design so:
- *   1. The slice #008 `subAgentToolMatcher: 'Task'` install entry
- *      stays byte-stable (the generated `.trae/settings.json` does
- *      not change).
- *   2. The dispatcher's return shape is uniform across both
- *      adapters — a single byte-equality test can verify the
- *      placeholder contract.
+ * - The dispatcher's return shape is uniform across both adapters
+ * — a single byte-equality test can verify the placeholder
+ * contract.
+ * - Future real Trae dogfood can replace the body of
+ * `buildToolCall` without breaking the adapter contract.
+ *
+ * Slice #014: the legacy `subAgentToolMatcher: 'Task'` install entry
+ * is gone — the field is removed from `IdeAdapter`. Slice #009+
+ * dispatched sub-agents directly, not via a PreToolUse hook. The Trae
+ * dispatcher remains a placeholder so the dispatch surface is uniform
+ * across adapters.
  *
  * When real Trae dogfood lands, replace the body of `buildToolCall`
  * with Trae's actual sub-agent tool name + args shape. The interface

package/dist/src/services/ide/adapters/claude-code-adapter.js

@@ -32,7 +32,6 @@ export const CLAUDE_CODE_ADAPTER = {
     envVar: 'CLAUDE_PROJECT_DIR',
     hookEvent: 'PreToolUse',
     toolMatcher: 'Bash',
-    subAgentToolMatcher: 'Task',
     // Slice #009: Claude Code uses the `Task` tool for sub-agent dispatch.
     // The CLI calls `claudeCodeSubAgentDispatcher.buildToolCall` to construct
     // the exact args shape the `Task` tool expects.
@@ -46,9 +45,7 @@ export const CLAUDE_CODE_ADAPTER = {
     ],
     capabilities: {
         gateEnforce: true,
-        progressStart: true,
         statusline: true,
-        mcpInstall: true,
     },
     // Slice #011: standards profile. Claude Code reads its constitution at
     // CLAUDE.md + module-level rules under .claude/rules/**. The values mirror

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

@@ -56,11 +56,10 @@ export const TRAE_ADAPTER = {
     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'`
-    subAgentToolMatcher: 'Task', // UNVERIFIED — Trae's sub-agent tool name is unknown; matches the prior hardcoded 'Task' literal so byte-level install output is unchanged. Will be dogfooded when a real Trae 1.x install dispatches a sub-agent.
     // 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 slice #008 `subAgentToolMatcher: 'Task'` install entry
-    // stays byte-stable. Awaiting real Trae 1.x dogfood to confirm/replace.
+    // design so the dispatcher shape is uniform across both adapters. Awaiting
+    // real Trae 1.x dogfood to confirm/replace.
     subAgentDispatcher: traeSubAgentDispatcher,
     // Slice #010 G9: Trae supports `beforeToolCall` which can wrap
     // `peaks sub-agent-dispatch-guard`. Opt in (matches the byte-stable
@@ -71,21 +70,7 @@ export const TRAE_ADAPTER = {
     ],
     capabilities: {
         gateEnforce: true,
-        progressStart: true,
         statusline: true,
-        // Slice #007-007-2026-06-07-mcp-decouple: mcpInstall is LOAD-BEARING.
-        // The 4 MCP capabilities (playwright, chrome-devtools, figma, context7)
-        // are installed via `peaks mcp plan/apply` which writes to the global
-        // `~/.claude/settings.json` file. Trae 1.x's MCP integration is
-        // UNVERIFIED (the Trae fixture did not dogfood the MCP install path),
-        // so the 6 SKILL.md files must surface a Trae-specific path (manual
-        // install + manual tool invocation) rather than promising `peaks mcp
-        // apply` will work on Trae. Skill bodies consume this flag through
-        // the IDE adapter's `capabilities.mcpInstall`; setting it to true
-        // without a real Trae MCP install dogfood would be a regression.
-        // Cross-reference: .peaks/memory/trae-adapter-sets-mcpinstall-false-trae-mcp-integration-is-unverified.md
-        // and the 4 per-capability memos under .peaks/memory/mcp-decouple-*.md.
-        mcpInstall: false
     }
     // Standards: UNVERIFIED — see slice #012+ (Trae real-install dogfood for
     // the `standardsProfile` and `skillInstall` fields). The slice #011

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

@@ -16,12 +16,8 @@ export type IdeId = 'claude-code' | 'trae' | 'codex' | 'cursor' | 'qoder' | 'ton
 export interface IdeCapabilities {
     /** peaks gate enforce 是否适用该 IDE(必备) */
     readonly gateEnforce: true;
-    /** peaks progress start(sub-agent 派发)是否适用 */
-    readonly progressStart: boolean;
     /** peaks statusline 状态栏是否适用 */
     readonly statusline: boolean;
-    /** peaks mcp install 是否适用 */
-    readonly mcpInstall: boolean;
 }
 export interface IdeSettingsLocation {
     /** 项目根下的 settings 目录名,例如 '.claude' / '.trae' / '.cursor' */
@@ -48,23 +44,10 @@ export interface IdeAdapter {
     readonly hookEvent: string;
     /** hook 数组元素的 matcher 字段(工具名匹配),例如 'Bash' / 'Task' / 'terminal' */
     readonly toolMatcher: string;
-    /**
-     * The tool name used by this IDE to invoke a sub-agent (e.g. Claude Code
-     * uses 'Task' to dispatch a sub-agent, Trae may use a different name).
-     * Consumed by the `peaks progress start` hook entry so each IDE self-
-     * reports its sub-agent tool name. Additive on `toolMatcher`: the
-     * `toolMatcher` field still drives the gate-enforce hook entry, this
-     * one drives the sub-agent-progress hook entry.
-     *
-     * Added in slice 2026-06-06-sub-agent-spawn-bug-and-decouple.
-     */
-    readonly subAgentToolMatcher: string;
     /**
      * Per-IDE sub-agent dispatcher. The `peaks sub-agent dispatch` CLI reads
      * this field, calls `supportsRole` + `buildToolCall`, and returns the
-     * resulting tool-call descriptor in the JSON envelope. Additive on
-     * `subAgentToolMatcher`: the matcher still drives the gate-enforce hook
-     * entry; this field drives the runtime sub-agent dispatch surface.
+     * 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]].