peaks-loop 4.0.0-beta.8 → 4.0.1

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

@@ -0,0 +1,97 @@
+import { homedir } from 'node:os';
+import { join, resolve } from 'node:path';
+import { codexSubAgentDispatcher } from '../../dispatch/sub-agent-dispatcher.js';
+/**
+ * Codex (OpenAI CLI IDE) adapter —— peaks-loop 的第四个内置 IDE 适配器(slice #13, 2.4.0)。
+ *
+ * 不可消除的 per-IDE 字段(slice #1 锁定,same shape as trae-adapter.ts / cursor-adapter.ts):
+ *   - settings.dirName = '.codex'        : Codex 项目根下的配置目录
+ *   - settings.settingsFileName = 'settings.json'
+ *   - envVar = 'CODEX_PROJECT_DIR'  : Codex 注入的项目根 env 变量(用于 ${...} 占位)
+ *   - hookEvent = 'pre_tool_use'    : Codex 的 lowercase snake_case hook event(UNVERIFIED — see R-3)
+ *   - toolMatcher = 'shell'         : Codex 的 shell command matcher
+ *
+ * Slice #13 status (2026-06-17, 2.4.0):
+ *   - Adapter is the fourth built-in IDE in peaks-loop after Claude Code (#1),
+ *     Trae (#2), and Cursor (#12). It further confirms the slice #1 + slice #2
+ *     architecture scales linearly: registering a new IDE is a one-entry fill
+ *     of the slim `IdeAdapter` shape with no dispatch-chokepoint changes.
+ *   - 2 UNVERIFIED fields: `hookEvent` (Codex's `pre_tool_use` is the standard
+ *     lowercase snake_case pattern but not confirmed against a live Codex
+ *     install; see PRD R-3) and `envVar` (Codex's `CODEX_PROJECT_DIR` is the
+ *     most likely candidate). Both are annotated; the framework's fallback
+ *     path (legacy Claude Code install + stderr warning) handles UNVERIFIED
+ *     adapters without codepath changes.
+ *   - `promptSizeAware: false` — Codex's hook event semantics differ from
+ *     Claude's. Opt out of the G9 prompt-size gate until real-install
+ *     dogfood confirms hook layer compatibility (PRD R-3). The CLI 兜底
+ *     layer in `peaks sub-agent dispatch` still enforces the threshold
+ *     regardless — `promptSizeAware` only controls the hook layer.
+ *   - `capabilities.statusline: false` — Codex CLI does not have a
+ *     statusline UI surface. `peaks statusline install --ide codex` will
+ *     exit non-zero with a clear stderr message (CLI does NOT crash;
+ *     capability-check contract preserved per slice #008 P-5).
+ *   - 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 Codex's sub-agent
+ *     shape is confirmed to differ).
+ *   - `standardsProfile` and `skillInstall` are intentionally UNVERIFIED —
+ *     real Codex 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 Codex who
+ *     want skills visible to Codex's auto-loader must move the symlinks
+ *     to `~/.codex/skills/` manually (the warning text says so).
+ *   - L1 install scope default = `project` (writes to `<projectRoot>/.codex/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 CODEX_ADAPTER = {
+    id: 'codex',
+    displayName: 'Codex',
+    settings: {
+        dirName: '.codex',
+        settingsFileName: 'settings.json',
+        resolveSettingsFile: (scope, projectRoot) => {
+            const root = scope === 'global' ? homedir() : resolve(projectRoot ?? homedir());
+            return join(root, '.codex', 'settings.json');
+        },
+        supportsScope: (scope) => scope === 'project' || scope === 'global'
+    },
+    envVar: 'CODEX_PROJECT_DIR', // UNVERIFIED — see slice #13 PRD R-3; fallback path still works
+    hookEvent: 'pre_tool_use', // UNVERIFIED — Codex lowercase snake_case pattern; re-verify against Codex docs
+    toolMatcher: 'shell',
+    // Slice #13: Codex 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 Codex dogfood lands, replace the
+    // body of `claudeCodeSubAgentDispatcher.buildToolCall` (or add a
+    // `codexSubAgentDispatcher`) without changing the adapter contract.
+    // Slice 1.3: promoted from `claudeCodeSubAgentDispatcher` placeholder
+    // to `codexSubAgentDispatcher` (real file-polling awaitBatch, 45s
+    // default). The `buildToolCall` shape is still byte-identical to
+    // claude-code; only the awaitBatch wiring diverges.
+    subAgentDispatcher: codexSubAgentDispatcher,
+    // Slice #13: Codex's `pre_tool_use` event semantics differ from Claude's
+    // `PreToolUse`. Opt out of the G9 prompt-size gate until real-install
+    // dogfood confirms hook layer compatibility. The CLI 兜底 layer in
+    // `peaks sub-agent dispatch` still enforces the threshold regardless.
+    promptSizeAware: false,
+    installHints: [
+        'Restart Codex so the pre_tool_use hooks take effect.'
+    ],
+    capabilities: {
+        gateEnforce: true,
+        // Codex CLI does not have a statusline UI surface. Opt out of the
+        // statusline capability; `peaks statusline install --ide codex` will
+        // return a clear "not supported" stderr message (slice #008 P-5
+        // capability-check contract preserved).
+        statusline: false,
+    }
+    // Standards: UNVERIFIED — see slice #013+ (Codex real-install dogfood for
+    // the `standardsProfile` and `skillInstall` fields). Until then, `peaks
+    // standards init` on a Codex-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 Codex-specific paths must move the files manually.
+};

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

@@ -0,0 +1,36 @@
+import type { IdeAdapter } from '../ide-types.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 declare const CURSOR_ADAPTER: IdeAdapter;

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

@@ -0,0 +1,84 @@
+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/services/ide/adapters/hermes-adapter.d.ts

@@ -0,0 +1,21 @@
+/**
+ * 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/services/ide/adapters/hermes-adapter.js

@@ -0,0 +1,51 @@
+/**
+ * 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/services/ide/adapters/openclaw-adapter.d.ts

@@ -0,0 +1,14 @@
+/**
+ * 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/services/ide/adapters/openclaw-adapter.js

@@ -0,0 +1,42 @@
+/**
+ * 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/services/ide/adapters/qoder-adapter.d.ts

@@ -0,0 +1,25 @@
+/**
+ * Qoder IDE adapter (slice 2026-07-25-qoder-adapter-ship) — peaks-loop
+ * 第八个内置 IDE 适配器(填表)。
+ *
+ * 不可消除的 per-IDE 字段(本 slice 填表;字段值暂为占位):
+ *   - settings.dirName = '.qoder'          : Qoder 项目根下的配置目录(UNVERIFIED)
+ *   - settings.settingsFileName = 'settings.json'(UNVERIFIED)
+ *   - envVar = 'QODER_PROJECT_DIR'         : Qoder 注入的 env 变量(UNVERIFIED)
+ *   - hookEvent = 'PreToolUse'             : 现代 IDE 通用约定(UNVERIFIED — 待真实 Qoder 安装验证)
+ *   - toolMatcher = 'Bash'                 : 同上(UNVERIFIED)
+ *
+ * Slice 2026-07-25-qoder-adapter-ship 状态:
+ *   - Slim adapter shape 跟 hermes-adapter.ts / claude-code-adapter.ts 同型,
+ *     验证 slice #1 抽出的形状在第 8 个 IDE 上仍然可以"填表"接入。
+ *   - 5 fields (dirName / settingsFileName / envVar / hookEvent / toolMatcher)
+ *     均为占位值并标记 UNVERIFIED;待真实 Qoder 安装可用后再走 VERIFIED 路径
+ *     (见 PRD §3 step 5 + 多 IDE 治理政策
+ *     .peaks/memory/2026-07-24-multi-ide-adapter-policy.md)。
+ *   - 见 [[2026-07-24-multi-ide-adapter-policy]] 了解 UNVERIFIED → VERIFIED
+ *     的迁移路径与 7-step checklist。
+ *   - 本 slice 不修改 src/services/ide/ide-types.ts(IdeId union 已经在
+ *     line 21 包含 'qoder'),不修改既有 adapter 文件,不修改既有测试。
+ */
+import type { IdeAdapter } from '../ide-types.js';
+export declare const QODER_ADAPTER: IdeAdapter;

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

@@ -0,0 +1,57 @@
+/**
+ * Qoder IDE adapter (slice 2026-07-25-qoder-adapter-ship) — peaks-loop
+ * 第八个内置 IDE 适配器(填表)。
+ *
+ * 不可消除的 per-IDE 字段(本 slice 填表;字段值暂为占位):
+ *   - settings.dirName = '.qoder'          : Qoder 项目根下的配置目录(UNVERIFIED)
+ *   - settings.settingsFileName = 'settings.json'(UNVERIFIED)
+ *   - envVar = 'QODER_PROJECT_DIR'         : Qoder 注入的 env 变量(UNVERIFIED)
+ *   - hookEvent = 'PreToolUse'             : 现代 IDE 通用约定(UNVERIFIED — 待真实 Qoder 安装验证)
+ *   - toolMatcher = 'Bash'                 : 同上(UNVERIFIED)
+ *
+ * Slice 2026-07-25-qoder-adapter-ship 状态:
+ *   - Slim adapter shape 跟 hermes-adapter.ts / claude-code-adapter.ts 同型,
+ *     验证 slice #1 抽出的形状在第 8 个 IDE 上仍然可以"填表"接入。
+ *   - 5 fields (dirName / settingsFileName / envVar / hookEvent / toolMatcher)
+ *     均为占位值并标记 UNVERIFIED;待真实 Qoder 安装可用后再走 VERIFIED 路径
+ *     (见 PRD §3 step 5 + 多 IDE 治理政策
+ *     .peaks/memory/2026-07-24-multi-ide-adapter-policy.md)。
+ *   - 见 [[2026-07-24-multi-ide-adapter-policy]] 了解 UNVERIFIED → VERIFIED
+ *     的迁移路径与 7-step checklist。
+ *   - 本 slice 不修改 src/services/ide/ide-types.ts(IdeId union 已经在
+ *     line 21 包含 'qoder'),不修改既有 adapter 文件,不修改既有测试。
+ */
+import { homedir } from 'node:os';
+import { join, resolve } from 'node:path';
+import { traeSubAgentDispatcher } from '../../dispatch/sub-agent-dispatcher.js';
+export const QODER_ADAPTER = {
+    id: 'qoder',
+    displayName: 'Qoder',
+    settings: {
+        dirName: '.qoder', // UNVERIFIED — placeholder; pending real Qoder 1.x fixture
+        settingsFileName: 'settings.json', // UNVERIFIED — placeholder
+        resolveSettingsFile: (scope, projectRoot) => {
+            const root = scope === 'global' ? homedir() : resolve(projectRoot ?? homedir());
+            return join(root, '.qoder', 'settings.json');
+        },
+        supportsScope: (scope) => scope === 'project' || scope === 'global'
+    },
+    envVar: 'QODER_PROJECT_DIR', // UNVERIFIED
+    hookEvent: 'PreToolUse', // UNVERIFIED
+    toolMatcher: 'Bash', // UNVERIFIED
+    // Slice 2026-07-25-qoder-adapter-ship: Qoder sub-agent dispatcher UNVERIFIED —
+    // pending real Qoder dogfood. Reusing the Trae dispatcher as a uniform
+    // placeholder (same rationale as hermes-adapter.ts: byte-stable shape
+    // across placeholder adapters).
+    subAgentDispatcher: traeSubAgentDispatcher,
+    // Slice 2026-07-25-qoder-adapter-ship: Qoder PreToolUse is the assumed hook
+    // path. UNVERIFIED — will be re-evaluated against a real Qoder install.
+    promptSizeAware: true,
+    installHints: [
+        'Restart Qoder (or reload the workspace) so the PreToolUse hooks take effect.'
+    ],
+    capabilities: {
+        gateEnforce: true,
+        statusline: true
+    }
+};

package/dist/services/ide/adapters/tongyi-lingma-adapter.d.ts

@@ -0,0 +1,16 @@
+/**
+ * Tongyi Lingma IDE adapter (slice 2026-07-25-tongyi-lingma-adapter-ship) —
+ * peaks-loop 第九个内置 IDE 适配器(填表)。
+ *
+ * 不可消除的 per-IDE 字段(本 slice 填表;字段值暂为占位):
+ *   - settings.dirName = '.lingma'                 (UNVERIFIED)
+ *   - settings.settingsFileName = 'settings.json' (UNVERIFIED)
+ *   - envVar = 'TONGYI_LINGMA_PROJECT_DIR'         (UNVERIFIED)
+ *   - hookEvent = 'PreToolUse'                     (UNVERIFIED)
+ *   - toolMatcher = 'Bash'                         (UNVERIFIED)
+ *
+ * 这些字段在真实 Tongyi Lingma 安装 dogfood 完成前不得标记 VERIFIED。
+ * 见 [[2026-07-24-multi-ide-adapter-policy]] §3 step 5。
+ */
+import type { IdeAdapter } from '../ide-types.js';
+export declare const TONGYI_LINGMA_ADAPTER: IdeAdapter;

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

@@ -0,0 +1,45 @@
+/**
+ * Tongyi Lingma IDE adapter (slice 2026-07-25-tongyi-lingma-adapter-ship) —
+ * peaks-loop 第九个内置 IDE 适配器(填表)。
+ *
+ * 不可消除的 per-IDE 字段(本 slice 填表;字段值暂为占位):
+ *   - settings.dirName = '.lingma'                 (UNVERIFIED)
+ *   - settings.settingsFileName = 'settings.json' (UNVERIFIED)
+ *   - envVar = 'TONGYI_LINGMA_PROJECT_DIR'         (UNVERIFIED)
+ *   - hookEvent = 'PreToolUse'                     (UNVERIFIED)
+ *   - 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';
+import { traeSubAgentDispatcher } from '../../dispatch/sub-agent-dispatcher.js';
+export const TONGYI_LINGMA_ADAPTER = {
+    id: 'tongyi-lingma',
+    displayName: 'Tongyi Lingma',
+    settings: {
+        dirName: '.lingma', // UNVERIFIED — placeholder; pending real Tongyi Lingma fixture
+        settingsFileName: 'settings.json', // UNVERIFIED — placeholder
+        resolveSettingsFile: (scope, projectRoot) => {
+            const root = scope === 'global' ? homedir() : resolve(projectRoot ?? homedir());
+            return join(root, '.lingma', 'settings.json');
+        },
+        supportsScope: (scope) => scope === 'project' || scope === 'global'
+    },
+    envVar: 'TONGYI_LINGMA_PROJECT_DIR', // UNVERIFIED
+    hookEvent: 'PreToolUse', // UNVERIFIED
+    toolMatcher: 'Bash', // UNVERIFIED
+    // UNVERIFIED — reuse Trae's dispatcher until real-install dogfood confirms
+    // Tongyi Lingma's native sub-agent dispatch surface.
+    subAgentDispatcher: traeSubAgentDispatcher,
+    // UNVERIFIED — PreToolUse is the assumed hook path.
+    promptSizeAware: true,
+    installHints: [
+        'Restart Tongyi Lingma (or reload the workspace) so the PreToolUse hooks take effect.'
+    ],
+    capabilities: {
+        gateEnforce: true,
+        statusline: true
+    }
+};

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

@@ -0,0 +1,42 @@
+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/services/ide/adapters/trae-adapter.js

@@ -0,0 +1,83 @@
+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.
+};