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

package/dist/services/hooks/output.d.ts

@@ -0,0 +1,92 @@
+/**
+ * Slice 003-2026-06-16-hook-governance — single source of truth for the
+ * peaks hook output contract. See `.claude/HOOKS.md` for the canonical doc.
+ *
+ * Three helpers, one job: enforce the stdout/stderr/exit-code discipline
+ * that every peaks-managed hook command MUST follow. Centralising the
+ * contract here lets us:
+ *   1. Pin the contract in cross-platform tests (tests/unit/hooks/contract.test.ts).
+ *   2. Add a new helper (e.g. emitAsk) without changing every call site.
+ *   3. Stop hand-rolling the deny JSON in gate-commands.ts / hook-handle.ts,
+ *      which historically drifted into "PreToolUse:Bash hook error" noise.
+ *
+ * The contract (intentionally redundant with the doc; the doc is for humans,
+ * this is for the type checker):
+ *
+ *   emitHint(io, text)
+ *     - Writes `text` to io.stderr with a trailing newline.
+ *     - Does NOT write to io.stdout (the host reads stdout as the decision
+ *       signal; a hint on stdout is interpreted as a malformed decision).
+ *     - Does NOT set a non-zero process.exitCode. A hint is diagnostic only;
+ *       it must not change the host's permission decision.
+ *     - Empty `text` is a no-op (skips both the write and the trailing
+ *       newline so we never pollute stderr with blank lines).
+ *
+ *   emitBlock(io, reason)
+ *     - Builds the Claude-Code-shaped deny JSON:
+ *         { "hookSpecificOutput": { "hookEventName": "PreToolUse",
+ *                                   "permissionDecision": "deny",
+ *                                   "permissionDecisionReason": <reason> } }
+ *       JSON.stringify is the canonical escape for the reason; quotes,
+ *       backslashes, and newlines inside the reason are preserved.
+ *     - Writes the serialized JSON to io.stdout with a trailing newline.
+ *     - Sets process.exitCode = 2. Claude Code treats exit-2 as the
+ *       "block" signal (see [Fact-Forcing Gate] note in .claude/HOOKS.md);
+ *       the JSON on stdout is the human-readable reason for the LLM.
+ *     - Surfaces the reason to io.stderr so an operator running the
+ *       hook command directly (or the LLM inspecting logs) can see
+ *       WHY the tool was blocked, not just THAT it was blocked.
+ *
+ *   emitDecision(io, decision)
+ *     - Writes the caller-provided decision JSON to io.stdout with a
+ *       trailing newline and returns the serialized string. Used by
+ *       IDE adapters that produce a different shape (e.g. Trae uses
+ *       hookEventName='beforeToolCall' instead of 'PreToolUse'). The
+ *       helper is intentionally shape-agnostic: the caller is the
+ *       adapter's `formatDecisionResponse`, which already knows the
+ *       IDE-specific shape.
+ *     - Does NOT set a non-zero process.exitCode. The decision is
+ *       communicated entirely via the stdout JSON; the host reads
+ *       permissionDecision='deny' to block. Setting exit=2 on top
+ *       of the JSON would be double-signaling.
+ *
+ * Platform notes:
+ *   - The contract is platform-independent. The helpers write to ProgramIO
+ *     (stdout / stderr) only; no path separators, no shell escaping, no
+ *     line-ending variants. The cross-platform contract test pins this.
+ *   - On win32, Node's process.stdout and process.stderr are binary-safe
+ *     and UTF-8; do not introduce \r\n anywhere. The contract is LF.
+ */
+import type { ProgramIO } from '../../cli/cli-helpers.js';
+/** Exit code the host treats as a hard block (Claude Code convention). */
+export declare const HOOK_BLOCK_EXIT_CODE = 2;
+/** Canonical Claude-Code hook event name. */
+export declare const CLAUDE_CODE_HOOK_EVENT = "PreToolUse";
+/** Permissive decision shape — anything JSON-serialisable. */
+export type DecisionShape = Record<string, unknown>;
+/**
+ * Hint — diagnostic, stderr-only, never affects the host decision.
+ * Returns the bytes written to stderr (or '' for an empty hint).
+ */
+export declare function emitHint(io: ProgramIO, text: string): string;
+/** Result of a block emission — the bytes written to stdout and the original reason. */
+export type EmitBlockResult = {
+    readonly stdout: string;
+    readonly reason: string;
+};
+/**
+ * Block — deny a tool call. Writes the Claude-Code-shaped deny JSON to
+ * stdout, sets process.exitCode = 2, and surfaces the reason to stderr.
+ */
+export declare function emitBlock(io: ProgramIO, reason: string): EmitBlockResult;
+/**
+ * Decision — write a caller-built decision object to stdout. Returns the
+ * serialized bytes so callers can log / assert on the exact string.
+ *
+ * Accepts either a plain object (canonical path; the helper does the
+ * JSON.stringify) or a pre-serialized string (used by adapter dispatch
+ * where `formatDecisionResponse` already serialized the IDE-shaped
+ * envelope). The string form is the legacy escape hatch and should not
+ * be used for new code.
+ */
+export declare function emitDecision(io: ProgramIO, decision: DecisionShape | string): string;

package/dist/services/hooks/output.js

@@ -0,0 +1,111 @@
+/**
+ * Slice 003-2026-06-16-hook-governance — single source of truth for the
+ * peaks hook output contract. See `.claude/HOOKS.md` for the canonical doc.
+ *
+ * Three helpers, one job: enforce the stdout/stderr/exit-code discipline
+ * that every peaks-managed hook command MUST follow. Centralising the
+ * contract here lets us:
+ *   1. Pin the contract in cross-platform tests (tests/unit/hooks/contract.test.ts).
+ *   2. Add a new helper (e.g. emitAsk) without changing every call site.
+ *   3. Stop hand-rolling the deny JSON in gate-commands.ts / hook-handle.ts,
+ *      which historically drifted into "PreToolUse:Bash hook error" noise.
+ *
+ * The contract (intentionally redundant with the doc; the doc is for humans,
+ * this is for the type checker):
+ *
+ *   emitHint(io, text)
+ *     - Writes `text` to io.stderr with a trailing newline.
+ *     - Does NOT write to io.stdout (the host reads stdout as the decision
+ *       signal; a hint on stdout is interpreted as a malformed decision).
+ *     - Does NOT set a non-zero process.exitCode. A hint is diagnostic only;
+ *       it must not change the host's permission decision.
+ *     - Empty `text` is a no-op (skips both the write and the trailing
+ *       newline so we never pollute stderr with blank lines).
+ *
+ *   emitBlock(io, reason)
+ *     - Builds the Claude-Code-shaped deny JSON:
+ *         { "hookSpecificOutput": { "hookEventName": "PreToolUse",
+ *                                   "permissionDecision": "deny",
+ *                                   "permissionDecisionReason": <reason> } }
+ *       JSON.stringify is the canonical escape for the reason; quotes,
+ *       backslashes, and newlines inside the reason are preserved.
+ *     - Writes the serialized JSON to io.stdout with a trailing newline.
+ *     - Sets process.exitCode = 2. Claude Code treats exit-2 as the
+ *       "block" signal (see [Fact-Forcing Gate] note in .claude/HOOKS.md);
+ *       the JSON on stdout is the human-readable reason for the LLM.
+ *     - Surfaces the reason to io.stderr so an operator running the
+ *       hook command directly (or the LLM inspecting logs) can see
+ *       WHY the tool was blocked, not just THAT it was blocked.
+ *
+ *   emitDecision(io, decision)
+ *     - Writes the caller-provided decision JSON to io.stdout with a
+ *       trailing newline and returns the serialized string. Used by
+ *       IDE adapters that produce a different shape (e.g. Trae uses
+ *       hookEventName='beforeToolCall' instead of 'PreToolUse'). The
+ *       helper is intentionally shape-agnostic: the caller is the
+ *       adapter's `formatDecisionResponse`, which already knows the
+ *       IDE-specific shape.
+ *     - Does NOT set a non-zero process.exitCode. The decision is
+ *       communicated entirely via the stdout JSON; the host reads
+ *       permissionDecision='deny' to block. Setting exit=2 on top
+ *       of the JSON would be double-signaling.
+ *
+ * Platform notes:
+ *   - The contract is platform-independent. The helpers write to ProgramIO
+ *     (stdout / stderr) only; no path separators, no shell escaping, no
+ *     line-ending variants. The cross-platform contract test pins this.
+ *   - On win32, Node's process.stdout and process.stderr are binary-safe
+ *     and UTF-8; do not introduce \r\n anywhere. The contract is LF.
+ */
+/** Exit code the host treats as a hard block (Claude Code convention). */
+export const HOOK_BLOCK_EXIT_CODE = 2;
+/** Canonical Claude-Code hook event name. */
+export const CLAUDE_CODE_HOOK_EVENT = 'PreToolUse';
+/**
+ * Hint — diagnostic, stderr-only, never affects the host decision.
+ * Returns the bytes written to stderr (or '' for an empty hint).
+ */
+export function emitHint(io, text) {
+    if (text.length === 0) {
+        return '';
+    }
+    const line = text.endsWith('\n') ? text : `${text}\n`;
+    io.stderr(line);
+    return line;
+}
+/**
+ * Block — deny a tool call. Writes the Claude-Code-shaped deny JSON to
+ * stdout, sets process.exitCode = 2, and surfaces the reason to stderr.
+ */
+export function emitBlock(io, reason) {
+    const safeReason = reason.length > 0 ? reason : 'denied by peaks';
+    const payload = {
+        hookSpecificOutput: {
+            hookEventName: CLAUDE_CODE_HOOK_EVENT,
+            permissionDecision: 'deny',
+            permissionDecisionReason: safeReason
+        }
+    };
+    const serialized = JSON.stringify(payload);
+    io.stdout(serialized);
+    io.stdout('\n');
+    io.stderr(`peaks: ${safeReason}\n`);
+    process.exitCode = HOOK_BLOCK_EXIT_CODE;
+    return { stdout: serialized, reason: safeReason };
+}
+/**
+ * Decision — write a caller-built decision object to stdout. Returns the
+ * serialized bytes so callers can log / assert on the exact string.
+ *
+ * Accepts either a plain object (canonical path; the helper does the
+ * JSON.stringify) or a pre-serialized string (used by adapter dispatch
+ * where `formatDecisionResponse` already serialized the IDE-shaped
+ * envelope). The string form is the legacy escape hatch and should not
+ * be used for new code.
+ */
+export function emitDecision(io, decision) {
+    const serialized = typeof decision === 'string' ? decision : JSON.stringify(decision);
+    io.stdout(serialized);
+    io.stdout('\n');
+    return serialized;
+}

package/dist/services/hooks/presence-marker-detector.d.ts

@@ -0,0 +1,16 @@
+export type DetectPresenceMarkerInput = {
+    project: string;
+    latestAssistantMessage: string;
+};
+export type DetectPresenceMarkerResult = {
+    active: boolean;
+    skill?: string;
+    markerFound: boolean;
+    warning?: string;
+};
+export type PresenceMarkerWarning = (typeof PRESENCE_MARKER_WARNING)[number];
+export declare const PRESENCE_MARKER_WARNING: readonly ["Peaks skill context may have been lost from this conversation; please re-invoke /peaks-<skill>."];
+/**
+ * Pure read-only presence-marker detection. No I/O side effects.
+ */
+export declare function detectPresenceMarker(input: DetectPresenceMarkerInput): DetectPresenceMarkerResult;

package/dist/services/hooks/presence-marker-detector.js

@@ -0,0 +1,105 @@
+import { existsSync, readFileSync } from 'node:fs';
+import { resolve } from 'node:path';
+/**
+ * Slice 028 (Q1=A): hook-based skill-presence marker detection.
+ *
+ * Background: the consumer-facing CLAUDE.md template (rendered by
+ * `peaks standards init` / `peaks standards update`) instructs the LLM
+ * to display a compact status header
+ *   `Peaks-Loop Skill: <skill> | Peaks-Loop Gate: <gate> | Next: <one short action>`
+ * on every turn while a peaks skill is active. If the LLM forgets (e.g.
+ * because of context compaction or a fresh session), the user is left
+ * without an at-a-glance signal that peaks is orchestrating the work.
+ *
+ * This service is the read-only side of the slice-028 detection
+ * mechanism. The PostToolUse hook (or any other consumer, e.g.
+ * `peaks skill detect-marker-loss`) calls
+ * `detectPresenceMarker({ project, latestAssistantMessage })`
+ * and gets back:
+ *
+ *   - `active`:      whether an active-skill marker was found on disk.
+ *   - `skill?`:      the active skill name, if any.
+ *   - `markerFound`: whether the latest assistant message carries the
+ *                    expected `Peaks-Loop Skill:` / `Peaks-Loop Gate:`
+ *                    marker. Always `false` when `active` is `false`.
+ *   - `warning?`:    a human-readable warning emitted when the marker
+ *                    is missing while the presence is active.
+ *
+ * The function is pure: it does not write to disk, does not clear the
+ * presence file, and does not depend on `process.cwd()`. The caller is
+ * expected to provide the absolute project root (peaks-loop convention
+ * from the standards-commands family — see dev-preference rule
+ * `project-option-is-canonical-project-root-source`).
+ */
+const PRESENCE_CANONICAL_PATH = '.peaks/_runtime/active-skill.json';
+const PRESENCE_LEGACY_PATH = '.peaks/.active-skill.json';
+const MARKER_PRIMARY = 'Peaks-Loop Skill:';
+const MARKER_SECONDARY = 'Peaks-Loop Gate:';
+const SKILL_NAME_RE = /"skill"\s*:\s*"([^"\\]*(?:\\.[^"\\]*)*)"/;
+export const PRESENCE_MARKER_WARNING = [
+    'Peaks skill context may have been lost from this conversation; please re-invoke /peaks-<skill>.'
+];
+function readPresenceFile(absolutePath) {
+    if (!existsSync(absolutePath))
+        return null;
+    let raw;
+    try {
+        raw = readFileSync(absolutePath, 'utf8');
+    }
+    catch { // TODO(g2): legacy silent catch — grace: 1 minor release (v2.14.0)
+        return null;
+    }
+    let parsed;
+    try {
+        parsed = JSON.parse(raw);
+    }
+    catch { // TODO(g2): legacy silent catch — grace: 1 minor release (v2.14.0)
+        return null;
+    }
+    if (parsed === null || typeof parsed !== 'object')
+        return null;
+    const skillMatch = SKILL_NAME_RE.exec(JSON.stringify(parsed));
+    if (skillMatch === null)
+        return null;
+    if (typeof skillMatch[1] !== 'string' || skillMatch[1].length === 0)
+        return null;
+    return { skill: skillMatch[1] };
+}
+function readPresenceBackCompat(project) {
+    const projectRoot = resolve(project);
+    const canonicalPath = resolve(projectRoot, PRESENCE_CANONICAL_PATH);
+    const legacyPath = resolve(projectRoot, PRESENCE_LEGACY_PATH);
+    for (const candidate of [canonicalPath, legacyPath]) {
+        const parsed = readPresenceFile(candidate);
+        if (parsed === null)
+            continue;
+        return { skill: parsed.skill, path: candidate };
+    }
+    return null;
+}
+function messageHasMarker(message) {
+    if (message.length === 0)
+        return false;
+    return message.includes(MARKER_PRIMARY) || message.includes(MARKER_SECONDARY);
+}
+/**
+ * Pure read-only presence-marker detection. No I/O side effects.
+ */
+export function detectPresenceMarker(input) {
+    const project = input.project;
+    const message = input.latestAssistantMessage ?? '';
+    const presence = readPresenceBackCompat(project);
+    if (presence === null) {
+        return { active: false, markerFound: false };
+    }
+    const markerFound = messageHasMarker(message);
+    if (markerFound) {
+        return { active: true, skill: presence.skill, markerFound: true };
+    }
+    return {
+        active: true,
+        skill: presence.skill,
+        markerFound: false,
+        warning: PRESENCE_MARKER_WARNING[0]
+    };
+}

package/dist/services/ide/adapters/claude-code-adapter.d.ts

@@ -0,0 +1,18 @@
+import type { IdeAdapter } from '../ide-types.js';
+/**
+ * Claude Code adapter —— peaks-loop 的"起源 IDE"。
+ *
+ * 该 adapter 从原 `src/services/skills/hooks-settings-service.ts` 提取,保持
+ * 字节级兼容:用户在 Claude Code 环境下跑 `peaks hooks install` 产出的
+ * `.claude/settings.json` 与 refactor 前逐字节相同。
+ *
+ * 字段解释(见 PRD AC-1):
+ *   - dirName = '.claude'           : Claude Code 项目根下的 settings 目录
+ *   - settingsFileName = 'settings.json'
+ *   - envVar = 'CLAUDE_PROJECT_DIR' : Claude Code 注入的 env 变量,用于 ${...} 占位
+ *   - hookEvent = 'PreToolUse'      : Claude Code hook 数组 key
+ *   - toolMatcher = 'Bash' | 'Task' : PreToolUse 数组元素的 matcher 字段
+ *
+ * 不可消除的 per-IDE 字段(见 tech-doc.md §1.3)。
+ */
+export declare const CLAUDE_CODE_ADAPTER: IdeAdapter;

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

@@ -0,0 +1,103 @@
+import { homedir } from 'node:os';
+import { join, resolve } from 'node:path';
+import { claudeCodeSubAgentDispatcher } from '../../dispatch/sub-agent-dispatcher.js';
+/**
+ * Claude Code adapter —— peaks-loop 的"起源 IDE"。
+ *
+ * 该 adapter 从原 `src/services/skills/hooks-settings-service.ts` 提取,保持
+ * 字节级兼容:用户在 Claude Code 环境下跑 `peaks hooks install` 产出的
+ * `.claude/settings.json` 与 refactor 前逐字节相同。
+ *
+ * 字段解释(见 PRD AC-1):
+ *   - dirName = '.claude'           : Claude Code 项目根下的 settings 目录
+ *   - settingsFileName = 'settings.json'
+ *   - envVar = 'CLAUDE_PROJECT_DIR' : Claude Code 注入的 env 变量,用于 ${...} 占位
+ *   - hookEvent = 'PreToolUse'      : Claude Code hook 数组 key
+ *   - toolMatcher = 'Bash' | 'Task' : PreToolUse 数组元素的 matcher 字段
+ *
+ * 不可消除的 per-IDE 字段(见 tech-doc.md §1.3)。
+ */
+export const CLAUDE_CODE_ADAPTER = {
+    id: 'claude-code',
+    displayName: 'Claude Code',
+    settings: {
+        dirName: '.claude',
+        settingsFileName: 'settings.json',
+        resolveSettingsFile: (scope, projectRoot) => {
+            const root = scope === 'global' ? homedir() : resolve(projectRoot ?? homedir());
+            return join(root, '.claude', 'settings.json');
+        },
+        supportsScope: () => true,
+    },
+    envVar: 'CLAUDE_PROJECT_DIR',
+    hookEvent: 'PreToolUse',
+    toolMatcher: 'Bash',
+    // 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.
+    subAgentDispatcher: claudeCodeSubAgentDispatcher,
+    // Slice #010 G9: Claude Code supports the PreToolUse hook event in a
+    // form that can wrap `peaks sub-agent-dispatch-guard` as a sub-command.
+    // Opt in to the G9 hook install.
+    promptSizeAware: true,
+    installHints: [
+        'Restart Claude Code (or reload the window) so the PreToolUse hooks take effect.'
+    ],
+    capabilities: {
+        gateEnforce: true,
+        statusline: true,
+    },
+    // v2.13.0 AC-1 + AC-3 MVP, slice 2026-07-02-auto-compact-zero-pause:
+    // Claude Code is the first IDE to fill the `compact` profile.
+    // Future adapters (trae / codex / cursor / qoder / tongyi-lingma /
+    // hermes / openclaw) follow the same shape — peaks-loop reads the
+    // env-var and dispatches the command via `IdeAdapter.compact`, with
+    // zero hard-coded IDE names anywhere in the orchestrator. If your
+    // IDE exposes a context-percent env-var and a slash-style compact
+    // command, register `compact` here and the auto-compact protocol
+    // activates.
+    //
+    // Pathway = 'ide-native' (not 'shell-exec') so the dispatcher
+    // routes main-session compacts through the PreToolUse hook in
+    // `.claude/settings.local.json`. The hook fires
+    // `peaks session auto-compact-hook` on the NEXT Bash/Task tool
+    // call from the runner, which in-band spawns `claude --compact`
+    // against the CURRENT runner — not a child process (the
+    // shell-exec spawn-new-claude bug documented in
+    // `.peaks/memory/2026-06-27-auto-compact-design.md:139-152`).
+    // Sub-agent shells still get the legacy shell-exec pathway via
+    // `dispatchIdeCompact({ target: 'sub-agent' })`.
+    compact: {
+        envVarForContextPercent: 'CLAUDE_CONTEXT_USAGE_PERCENT',
+        compactCommand: 'claude --compact',
+        compactPathway: 'ide-native',
+        postCompactDetectCommand: 'peaks context now --json'
+    },
+    // Slice #011: standards profile. Claude Code reads its constitution at
+    // CLAUDE.md + module-level rules under .claude/rules/**. The values mirror
+    // the hardcoded paths in `src/services/standards/project-standards-service.ts`
+    // (line 147 = '.claude', line 417/421 = 'CLAUDE.md' + '.claude/rules/...')
+    // and the postinstall target in `scripts/install-skills.mjs` (line 427 =
+    // '~/.claude/skills'). Filling the profile here makes the dispatch layer
+    // route to the SAME paths, so byte-stability on `peaks standards init` for
+    // Claude Code projects is preserved.
+    standardsProfile: {
+        rootFile: 'CLAUDE.md',
+        rulesDir: '.claude/rules',
+        rulesFileGlob: '**/*.md',
+        autoLoaded: true,
+        format: 'markdown',
+        migrationHint: 'Standards live at CLAUDE.md + .claude/rules/** for Claude Code.',
+    },
+    // Slice #011: skill install profile. The postinstall script symlinks
+    // bundled skills to `~/.claude/skills` and writes output-styles to
+    // `~/.claude/output-styles`, matching the existing hardcoded
+    // install-skills.mjs lines 427 + 488. The env-var back-compat name
+    // matches the legacy `PEAKS_CLAUDE_SKILLS_DIR` / `PEAKS_CLAUDE_OUTPUT_STYLES_DIR`.
+    skillInstall: {
+        skillsDir: join(homedir(), '.claude', 'skills'),
+        outputStylesDir: join(homedir(), '.claude', 'output-styles'),
+        installStrategy: 'symlink',
+        envVarOverride: 'PEAKS_CLAUDE_SKILLS_DIR',
+    },
+};

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

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

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;