peaks-loop 4.0.0-beta.6 → 4.0.0-beta.8

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

@@ -1,84 +0,0 @@
-import { homedir } from 'node:os';
-import { join, resolve } from 'node:path';
-import { cursorSubAgentDispatcher } from '../../dispatch/sub-agent-dispatcher.js';
-/**
- * Cursor IDE adapter —— peaks-loop 的第三个内置 IDE 适配器(slice #12, 2.4.0)。
- *
- * 不可消除的 per-IDE 字段(slice #1 锁定,same shape as trae-adapter.ts):
- *   - settings.dirName = '.cursor'            : Cursor 项目根下的配置目录
- *   - settings.settingsFileName = 'settings.json'
- *   - envVar = 'CURSOR_PROJECT_DIR'     : Cursor 注入的项目根 env 变量(用于 ${...} 占位)
- *   - hookEvent = 'beforeShellExecution': Cursor 的 shell hook event key(UNVERIFIED — see R-1)
- *   - toolMatcher = 'Bash'              : Cursor 的 shell execution tool matcher
- *
- * Slice #12 status (2026-06-17, 2.4.0):
- *   - Adapter is the third built-in IDE in peaks-loop after Claude Code (#1) and Trae (#2).
- *   - Confirms the slice #1 + slice #2 architecture scales linearly: registering
- *     a new IDE is genuinely a one-entry fill of the slim `IdeAdapter` shape.
- *   - 2 UNVERIFIED fields: `envVar` (Cursor's `CURSOR_PROJECT_DIR` is the
- *     most likely candidate but not confirmed against a live Cursor install;
- *     see PRD R-2) and `hookEvent` (Cursor docs may use a different event
- *     name; see PRD R-1). Both are annotated; the framework's fallback path
- *     (legacy Claude Code install + stderr warning) handles UNVERIFIED
- *     adapters without codepath changes.
- *   - Sub-agent dispatcher reuses `claudeCodeSubAgentDispatcher` by design
- *     (slice #009 rationale — byte-level identical across adapters; per-IDE
- *     divergence can be filled in a follow-up slice if Cursor's sub-agent
- *     shape is confirmed to differ).
- *   - `standardsProfile` and `skillInstall` are intentionally UNVERIFIED —
- *     real Cursor install dogfood required. Until then, the bundled-skills
- *     postinstall writes to `~/.claude/skills/` (legacy Claude Code fallback
- *     per slice #011 framework), with a stderr warning. Users on Cursor who
- *     want skills visible to Cursor's auto-loader must move the symlinks
- *     to `~/.cursor/skills/` manually (the warning text says so).
- *   - L1 install scope default = `project` (writes to `<projectRoot>/.cursor/settings.json`).
- *     `--scope global` is the explicit global path; the L1 default is the
- *     safer opt-in per slice #012 PRD scope clarification.
- */
-export const CURSOR_ADAPTER = {
-    id: 'cursor',
-    displayName: 'Cursor',
-    settings: {
-        dirName: '.cursor',
-        settingsFileName: 'settings.json',
-        resolveSettingsFile: (scope, projectRoot) => {
-            const root = scope === 'global' ? homedir() : resolve(projectRoot ?? homedir());
-            return join(root, '.cursor', 'settings.json');
-        },
-        supportsScope: (scope) => scope === 'project' || scope === 'global'
-    },
-    envVar: 'CURSOR_PROJECT_DIR', // UNVERIFIED — see slice #12 PRD R-2; fallback path still works
-    hookEvent: 'beforeShellExecution', // UNVERIFIED — see slice #12 PRD R-1; re-verify against Cursor's published hook schema
-    toolMatcher: 'Bash',
-    // Slice #12: Cursor sub-agent tool name TBD on real dogfood. Reusing the
-    // Claude Code dispatcher as a uniform placeholder (byte-level identical by
-    // design so the dispatcher's return shape is uniform across adapters —
-    // see slice #009 rationale). When real Cursor dogfood lands, replace the
-    // body of `claudeCodeSubAgentDispatcher.buildToolCall` (or add a
-    // `cursorSubAgentDispatcher`) without changing the adapter contract.
-    // Slice 1.3: promoted from `claudeCodeSubAgentDispatcher` placeholder
-    // to `cursorSubAgentDispatcher` (real file-polling awaitBatch, 30s
-    // default). The `buildToolCall` shape is still byte-identical to
-    // claude-code; only the awaitBatch wiring diverges.
-    subAgentDispatcher: cursorSubAgentDispatcher,
-    // Slice #12: Cursor supports `beforeShellExecution` which can wrap
-    // `peaks sub-agent-dispatch-guard`. Opt in (matches the byte-stable
-    // slice #008 install entry shape — same pattern as Trae adapter).
-    promptSizeAware: true,
-    installHints: [
-        'Restart Cursor so the beforeShellExecution hooks take effect.'
-    ],
-    capabilities: {
-        gateEnforce: true,
-        // Cursor has a statusline UI (Cmd+Shift+P → "Cursor: Open Status Bar")
-        // that can host peaks statusline output, so opt in to the capability.
-        statusline: true,
-    }
-    // Standards: UNVERIFIED — see slice #012+ (Cursor real-install dogfood for
-    // the `standardsProfile` and `skillInstall` fields). Until then, `peaks
-    // standards init` on a Cursor-detected project falls back to the Claude
-    // Code path (CLAUDE.md + .claude/rules/**) with a stderr warning, and the
-    // postinstall script writes skills + output-styles to the legacy
-    // `~/.claude/{skills,output-styles}` paths with a stderr warning. Users
-    // who want Cursor-specific paths must move the files manually.
-};

package/dist/src/services/ide/adapters/hermes-adapter.d.ts

@@ -1,21 +0,0 @@
-/**
- * Hermes IDE adapter (Slice #0.7) — peaks-loop 的第七个内置 IDE 适配器。
- *
- * 不可消除的 per-IDE 字段(slice #0.7 填表):
- *   - settings.dirName = '.hermes'          : Hermes 项目根下的配置目录
- *   - settings.settingsFileName = 'settings.json'
- *   - envVar = 'HERMES_PROJECT_DIR'   : Hermes 注入的 env 变量(用于 ${...} 占位)
- *   - hookEvent = 'PreToolUse'        : 现代 IDE 通用约定(UNVERIFIED — 待真实 Hermes 安装验证)
- *   - toolMatcher = 'Bash'            : 同上(UNVERIFIED)
- *
- * Slice #0.7 状态:
- *   - Slim adapter shape 跟 trae-adapter.ts / claude-code-adapter.ts 同型,
- *     验证 slice #1 抽出的形状在第 7 个 IDE 上仍然可以"填表"接入。
- *   - 4 UNVERIFIED fields (hookEvent, toolMatcher, envVar, dirName) 在
- *     Hermes 真实安装可用前均为占位值;待真实 Hermes fixture 验证后
- *     跟 trae-adapter 一样会被 VERIFIED 标记。
- *   - 见 PRD §0.7 + memory trae-adapter-values-verified-against-1x.md
- *     了解 UNVERIFIED → VERIFIED 的迁移路径。
- */
-import type { IdeAdapter } from '../ide-types.js';
-export declare const HERMES_ADAPTER: IdeAdapter;

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

@@ -1,51 +0,0 @@
-/**
- * Hermes IDE adapter (Slice #0.7) — peaks-loop 的第七个内置 IDE 适配器。
- *
- * 不可消除的 per-IDE 字段(slice #0.7 填表):
- *   - settings.dirName = '.hermes'          : Hermes 项目根下的配置目录
- *   - settings.settingsFileName = 'settings.json'
- *   - envVar = 'HERMES_PROJECT_DIR'   : Hermes 注入的 env 变量(用于 ${...} 占位)
- *   - hookEvent = 'PreToolUse'        : 现代 IDE 通用约定(UNVERIFIED — 待真实 Hermes 安装验证)
- *   - toolMatcher = 'Bash'            : 同上(UNVERIFIED)
- *
- * Slice #0.7 状态:
- *   - Slim adapter shape 跟 trae-adapter.ts / claude-code-adapter.ts 同型,
- *     验证 slice #1 抽出的形状在第 7 个 IDE 上仍然可以"填表"接入。
- *   - 4 UNVERIFIED fields (hookEvent, toolMatcher, envVar, dirName) 在
- *     Hermes 真实安装可用前均为占位值;待真实 Hermes fixture 验证后
- *     跟 trae-adapter 一样会被 VERIFIED 标记。
- *   - 见 PRD §0.7 + memory trae-adapter-values-verified-against-1x.md
- *     了解 UNVERIFIED → VERIFIED 的迁移路径。
- */
-import { homedir } from 'node:os';
-import { join, resolve } from 'node:path';
-import { traeSubAgentDispatcher } from '../../dispatch/sub-agent-dispatcher.js';
-export const HERMES_ADAPTER = {
-    id: 'hermes',
-    displayName: 'Hermes',
-    settings: {
-        dirName: '.hermes', // UNVERIFIED — placeholder; pending real Hermes 1.x fixture
-        settingsFileName: 'settings.json',
-        resolveSettingsFile: (scope, projectRoot) => {
-            const root = scope === 'global' ? homedir() : resolve(projectRoot ?? homedir());
-            return join(root, '.hermes', 'settings.json');
-        },
-        supportsScope: (scope) => scope === 'project' || scope === 'global'
-    },
-    envVar: 'HERMES_PROJECT_DIR', // UNVERIFIED
-    hookEvent: 'PreToolUse', // UNVERIFIED
-    toolMatcher: 'Bash', // UNVERIFIED
-    // Slice #0.7: Hermes sub-agent dispatcher UNVERIFIED — pending real Hermes
-    // dogfood. Reusing the Trae dispatcher as a uniform placeholder (byte-stable
-    // shape per slice #008; same rationale as Trae adapter).
-    subAgentDispatcher: traeSubAgentDispatcher,
-    // Slice #010 G9: Hermes PreToolUse is the assumed hook path. UNVERIFIED.
-    promptSizeAware: true,
-    installHints: [
-        'Restart Hermes (or reload the workspace) so the PreToolUse hooks take effect.'
-    ],
-    capabilities: {
-        gateEnforce: true,
-        statusline: true
-    }
-};

package/dist/src/services/ide/adapters/openclaw-adapter.d.ts

@@ -1,14 +0,0 @@
-/**
- * OpenClaw IDE adapter (Slice #0.7) — peaks-loop 的第八个内置 IDE 适配器。
- *
- * 不可消除的 per-IDE 字段(slice #0.7 填表):
- *   - settings.dirName = '.openclaw'        : OpenClaw 项目根下的配置目录
- *   - settings.settingsFileName = 'settings.json'
- *   - envVar = 'OPENCLAW_PROJECT_DIR' : OpenClaw 注入的 env 变量
- *   - hookEvent = 'PreToolUse'        : 现代 IDE 通用约定(UNVERIFIED)
- *   - toolMatcher = 'Bash'            : 同上(UNVERIFIED)
- *
- * Slice #0.7 状态: 同 hermes-adapter.ts 的 UNVERIFIED 占位说明。
- */
-import type { IdeAdapter } from '../ide-types.js';
-export declare const OPENCLAW_ADAPTER: IdeAdapter;

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

@@ -1,42 +0,0 @@
-/**
- * OpenClaw IDE adapter (Slice #0.7) — peaks-loop 的第八个内置 IDE 适配器。
- *
- * 不可消除的 per-IDE 字段(slice #0.7 填表):
- *   - settings.dirName = '.openclaw'        : OpenClaw 项目根下的配置目录
- *   - settings.settingsFileName = 'settings.json'
- *   - envVar = 'OPENCLAW_PROJECT_DIR' : OpenClaw 注入的 env 变量
- *   - hookEvent = 'PreToolUse'        : 现代 IDE 通用约定(UNVERIFIED)
- *   - toolMatcher = 'Bash'            : 同上(UNVERIFIED)
- *
- * Slice #0.7 状态: 同 hermes-adapter.ts 的 UNVERIFIED 占位说明。
- */
-import { homedir } from 'node:os';
-import { join, resolve } from 'node:path';
-import { traeSubAgentDispatcher } from '../../dispatch/sub-agent-dispatcher.js';
-export const OPENCLAW_ADAPTER = {
-    id: 'openclaw',
-    displayName: 'OpenClaw',
-    settings: {
-        dirName: '.openclaw', // UNVERIFIED
-        settingsFileName: 'settings.json',
-        resolveSettingsFile: (scope, projectRoot) => {
-            const root = scope === 'global' ? homedir() : resolve(projectRoot ?? homedir());
-            return join(root, '.openclaw', 'settings.json');
-        },
-        supportsScope: (scope) => scope === 'project' || scope === 'global'
-    },
-    envVar: 'OPENCLAW_PROJECT_DIR', // UNVERIFIED
-    hookEvent: 'PreToolUse', // UNVERIFIED
-    toolMatcher: 'Bash', // UNVERIFIED
-    // Slice #0.7: OpenClaw sub-agent dispatcher UNVERIFIED. Reusing Trae
-    // dispatcher as uniform placeholder.
-    subAgentDispatcher: traeSubAgentDispatcher,
-    promptSizeAware: true,
-    installHints: [
-        'Restart OpenClaw (or reload the workspace) so the PreToolUse hooks take effect.'
-    ],
-    capabilities: {
-        gateEnforce: true,
-        statusline: true
-    }
-};

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

@@ -1,42 +0,0 @@
-import type { IdeAdapter } from '../ide-types.js';
-/**
- * Trae IDE adapter —— peaks-loop 的第二个内置 IDE 适配器。
- *
- * 不可消除的 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 抽出的形状真的可以
- * 简单复制粘贴就接入新 IDE。
- *
- * 与 slice #1 claude-code-adapter.ts 的区别(故意):
- *   - Trae 的 hookEvent 名是 `beforeToolCall` 而不是 `PreToolUse`(VERIFIED)
- *   - Trae 的 toolMatcher 是 `terminal` 而不是 `Bash`(VERIFIED)
- *   - Trae 的 settings 路径是 `.trae/settings.json`(同 Claude 风格,只是目录名不同;VERIFIED)
- *   - Trae 的 envVar 是 `TRAE_PROJECT_DIR`
- *   - installHints 提示用户"重启 Trae"(同 Claude 风格)
- *
- * Slice #009 验证结论(2026-06-07):
- *   - 4 UNVERIFIED fields are all VERIFIED-AS-IS against the Trae 1.x fixture
- *     (tests/fixtures/trae/trae-1x-payload.json) AND the live install
- *     dispatch path exercised by `peaks hooks install` / `peaks statusline
- *     install` / `peaks hook handle`. The fixture mimics a real Trae 1.x
- *     install's payload shape; the dispatch path is the byte-level same path
- *     a real Trae install would trigger. Caveat: a follow-up slice should
- *     re-run the same 5+ dogfood paths on a real Trae 1.x install once one
- *     is available, to confirm the 1.x assumption is correct (see PRD R-1
- *     + the new memory at
- *     .peaks/memory/trae-adapter-values-verified-against-1x.md).
- *   - See .peaks/_runtime/2026-06-06-session-5b1095/qa/dogfood-trae-1x-2026-06-07.md
- *     for the full resolution table.
- *
- * Slice #3 refactor: the `peaks hooks install` command now dispatches on the
- * IDE adapter (auto-detect from env / cwd, override with `--ide trae`). When
- * a Trae install is run, the resulting `<root>/.trae/settings.json` will use
- * the `beforeToolCall` event key and the `terminal` matcher from this adapter.
- */
-export declare const TRAE_ADAPTER: IdeAdapter;

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

@@ -1,83 +0,0 @@
-import { homedir } from 'node:os';
-import { join, resolve } from 'node:path';
-import { traeSubAgentDispatcher } from '../../dispatch/sub-agent-dispatcher.js';
-/**
- * Trae IDE adapter —— peaks-loop 的第二个内置 IDE 适配器。
- *
- * 不可消除的 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 抽出的形状真的可以
- * 简单复制粘贴就接入新 IDE。
- *
- * 与 slice #1 claude-code-adapter.ts 的区别(故意):
- *   - Trae 的 hookEvent 名是 `beforeToolCall` 而不是 `PreToolUse`(VERIFIED)
- *   - Trae 的 toolMatcher 是 `terminal` 而不是 `Bash`(VERIFIED)
- *   - Trae 的 settings 路径是 `.trae/settings.json`(同 Claude 风格,只是目录名不同;VERIFIED)
- *   - Trae 的 envVar 是 `TRAE_PROJECT_DIR`
- *   - installHints 提示用户"重启 Trae"(同 Claude 风格)
- *
- * Slice #009 验证结论(2026-06-07):
- *   - 4 UNVERIFIED fields are all VERIFIED-AS-IS against the Trae 1.x fixture
- *     (tests/fixtures/trae/trae-1x-payload.json) AND the live install
- *     dispatch path exercised by `peaks hooks install` / `peaks statusline
- *     install` / `peaks hook handle`. The fixture mimics a real Trae 1.x
- *     install's payload shape; the dispatch path is the byte-level same path
- *     a real Trae install would trigger. Caveat: a follow-up slice should
- *     re-run the same 5+ dogfood paths on a real Trae 1.x install once one
- *     is available, to confirm the 1.x assumption is correct (see PRD R-1
- *     + the new memory at
- *     .peaks/memory/trae-adapter-values-verified-against-1x.md).
- *   - See .peaks/_runtime/2026-06-06-session-5b1095/qa/dogfood-trae-1x-2026-06-07.md
- *     for the full resolution table.
- *
- * Slice #3 refactor: the `peaks hooks install` command now dispatches on the
- * IDE adapter (auto-detect from env / cwd, override with `--ide trae`). When
- * a Trae install is run, the resulting `<root>/.trae/settings.json` will use
- * the `beforeToolCall` event key and the `terminal` matcher from this adapter.
- */
-export const TRAE_ADAPTER = {
-    id: 'trae',
-    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)
-        resolveSettingsFile: (scope, projectRoot) => {
-            const root = scope === 'global' ? homedir() : resolve(projectRoot ?? homedir());
-            return join(root, '.trae', 'settings.json');
-        },
-        supportsScope: (scope) => scope === 'project' || scope === 'global'
-    },
-    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'`
-    // 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
-    // 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
-    // slice #008 install entry shape).
-    promptSizeAware: true,
-    installHints: [
-        'Restart Trae (or reload the workspace) so the beforeToolCall hooks take effect.'
-    ],
-    capabilities: {
-        gateEnforce: true,
-        statusline: true,
-    }
-    // Standards: UNVERIFIED — see slice #012+ (Trae real-install dogfood for
-    // the `standardsProfile` and `skillInstall` fields). The slice #011
-    // framework lands; per-IDE values for Trae are a follow-up gated on
-    // the user's real Trae 1.x install. Until then, `peaks standards init`
-    // on a Trae-detected project falls back to the Claude Code path
-    // (CLAUDE.md + .claude/rules/**) with a stderr warning, and the
-    // postinstall script writes skills + output-styles to the legacy
-    // `~/.claude/{skills,output-styles}` paths with a stderr warning.
-};

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

@@ -1,47 +0,0 @@
-import { PEAKS_HOOK_SCHEMA, type IdeId, type PeaksCanonicalHook, type PeaksDecisionTransport } from './ide-types.js';
-export { PEAKS_HOOK_SCHEMA };
-export type { PeaksCanonicalHook, PeaksDecisionTransport };
-/**
- * Compute the deny decision shape for Claude Code (the only adapter registered
- * in slice #1). The output is a JSON object that, when written to stdout, makes
- * the Claude Code permission system block the tool call BEFORE the user's
- * permission prompt — un-bypassable, even under --dangerously-skip-permissions.
- */
-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;
-/**
- * Format a decision response for a given IDE. Slice #1 handles Claude Code;
- * slice #3 added Trae (1.x-assumption shape — see TRAE_DENY_SHAPE doc).
- * Future slices will add exit-code / both variants for IDEs that don't read
- * stdout.
- */
-export declare function formatDecisionResponse(ide: IdeId, decision: 'allow' | 'deny', reason?: string): {
-    stdout: string;
-    exitCode: number;
-};
-/**
- * Build a peaks canonical hook from a parsed stdin payload. Caller has already
- * done stdin parsing + IDE auto-detection; this function normalizes to the
- * canonical schema.
- */
-export interface BuildCanonicalHookInput {
-    readonly toolName: string;
-    readonly toolInput: Record<string, unknown>;
-    readonly projectRoot: string;
-    readonly rawIdeFormat: IdeId;
-    readonly rawPayload: unknown;
-    readonly event?: PeaksCanonicalHook['event'];
-}
-export declare function buildCanonicalHook(input: BuildCanonicalHookInput): PeaksCanonicalHook;

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

@@ -1,74 +0,0 @@
-import { PEAKS_HOOK_SCHEMA } from './ide-types.js';
-export { PEAKS_HOOK_SCHEMA };
-/**
- * Compute the deny decision shape for Claude Code (the only adapter registered
- * in slice #1). The output is a JSON object that, when written to stdout, makes
- * the Claude Code permission system block the tool call BEFORE the user's
- * permission prompt — un-bypassable, even under --dangerously-skip-permissions.
- */
-export const CLAUDE_CODE_DENY_SHAPE = {
-    hookSpecificOutput: {
-        hookEventName: 'PreToolUse',
-        permissionDecision: 'deny',
-        permissionDecisionReason: '__REASON__' // replaced at format time
-    }
-};
-export const CLAUDE_CODE_DENY_TRANSPORT = {
-    kind: 'stdout-json',
-    denyShape: CLAUDE_CODE_DENY_SHAPE
-};
-/**
- * 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: {
-        hookEventName: 'beforeToolCall',
-        permissionDecision: 'deny',
-        permissionDecisionReason: '__REASON__' // replaced at format time
-    }
-};
-export const TRAE_DENY_TRANSPORT = {
-    kind: 'stdout-json',
-    denyShape: TRAE_DENY_SHAPE
-};
-/**
- * Format a decision response for a given IDE. Slice #1 handles Claude Code;
- * slice #3 added Trae (1.x-assumption shape — see TRAE_DENY_SHAPE doc).
- * Future slices will add exit-code / both variants for IDEs that don't read
- * stdout.
- */
-export function formatDecisionResponse(ide, decision, reason) {
-    if (decision === 'allow') {
-        return { stdout: '', exitCode: 0 };
-    }
-    let shape;
-    if (ide === 'claude-code') {
-        shape = CLAUDE_CODE_DENY_SHAPE;
-    }
-    else if (ide === 'trae') {
-        shape = TRAE_DENY_SHAPE;
-    }
-    else {
-        throw new Error(`formatDecisionResponse: unsupported IDE ${ide} (not registered in adapter registry; future slice will add support)`);
-    }
-    const filled = JSON.stringify(shape).replace('"__REASON__"', JSON.stringify(reason ?? 'denied'));
-    return { stdout: filled, exitCode: 0 };
-}
-export function buildCanonicalHook(input) {
-    return {
-        schema: PEAKS_HOOK_SCHEMA,
-        event: input.event ?? 'pre-tool-use',
-        toolName: input.toolName,
-        toolInput: input.toolInput,
-        projectRoot: input.projectRoot,
-        rawIdeFormat: input.rawIdeFormat,
-        rawPayload: input.rawPayload
-    };
-}

package/dist/src/services/ide/hook-translator.d.ts

@@ -1,72 +0,0 @@
-import type { IdeId } from './ide-types.js';
-/**
- * hook-translator —— peaks 自有 hook 协议的核心。
- *
- * 单一职责:把 IDE 私有 stdin 形态归一化到 peaks canonical schema;把 peaks 决策
- * 格式化回 IDE 期望的 stdout/exit-code 形态。
- *
- * auto-detection 算法(优先级从高到低):
- *   1. env 变量:CLAUDE_PROJECT_DIR / TRAE_PROJECT_DIR / CODEX_PROJECT_DIR / ...
- *   2. stdin shape:`{ tool_name, tool_input }` 是 Claude / Trae;
- *                `{ toolName, toolInput }` 是 Cursor;
- *                `{ eventName, parameters }` 是 Trae 另形态
- *   3. cwd 启发式:存在 .claude / .trae / .codex / .cursor 目录
- *   4. fallback:`claude-code`(backward compat,见 PRD preserved behavior #10)
- */
-export interface DetectFromStdinInput {
-    readonly env: NodeJS.ProcessEnv;
-    readonly cwd: string;
-    /** 已解析的 stdin 形态;null = 空 stdin 或非 JSON */
-    readonly parsedStdin: unknown;
-}
-/**
- * Detect the originating IDE from env / stdin shape / cwd heuristics.
- * Falls back to 'claude-code' (PRD preserved behavior: backward compat).
- */
-export declare function detectIdeFromContext(input: DetectFromStdinInput): IdeId;
-/**
- * Pluck a string value at a nested path. Returns undefined if any segment is
- * missing or non-object. Used by adapter-driven stdin parsers.
- */
-export declare function pluckString(obj: unknown, path: readonly string[]): string | undefined;
-export declare function pluckObject(obj: unknown, path: readonly string[]): Record<string, unknown> | undefined;
-/**
- * Default stdin parser for adapters that follow the Claude Code shape
- * (most LLM-style IDEs do: tool_name at top, tool_input.{command} inside).
- */
-export declare function parseClaudeShapeStdin(parsed: unknown): {
-    toolName?: string;
-    command?: string;
-};
-/**
- * Trae stdin parser. UNVERIFIED — Trae 1.x's actual stdin envelope shape is
- * assumed to be Cursor-style (eventName at top, parameters nested), based on
- * slice #2's read of Trae as a "Cursor sibling". When a real Trae 1.x hook
- * payload is dogfooded, this parser is the seam to update.
- *
- * Shape (assumed):
- *   { eventName: 'beforeToolCall', parameters: { command: 'rm -rf /' } }
- *
- * Returns the same `{ toolName, command }` shape as parseClaudeShapeStdin so
- * downstream code (buildCanonicalHook, enforceBashCommand) does not need to
- * branch on IDE. The `toolName` here is the IDE-specific name (e.g.
- * 'terminal'); callers may normalize it to the canonical 'Bash' if needed.
- */
-export declare function parseTraeShapeStdin(parsed: unknown): {
-    toolName?: string;
-    command?: string;
-};
-/**
- * Per-adapter stdin parser dispatch. Returns the `{ toolName, command }` pair
- * for the given IDE, regardless of which stdin shape the IDE actually emits.
- *
- * The dispatch table is keyed on `IdeId` (not stdin shape) so an adapter can
- * change its wire format without breaking the hook-handle flow. Unknown IDEs
- * fall back to the Claude parser — that preserves the slice #1 "fail-open to
- * Claude" behavior so a future adapter that has not yet been added does not
- * crash the hook runtime.
- */
-export declare function parseAdapterStdin(ide: IdeId, parsed: unknown): {
-    toolName?: string;
-    command?: string;
-};