peaks-loop 4.0.0-beta.7 → 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/adapters/zcode-adapter.d.ts

@@ -1,40 +0,0 @@
-import type { IdeAdapter } from '../ide-types.js';
-/**
- * Helper exported for tests + internal use: the default location of the
- * z-code v2 config file on the host filesystem.
- */
-export declare function defaultZcodeConfigPath(): string;
-/**
- * Resolve the active model id from a parsed z-code config payload
- * (the `~/.zcode/v2/config.json` root object). Pure / exported for
- * unit tests so the file-IO seam and the resolution seam are
- * independently verifiable.
- *
- * Resolution order (Slice C §"z-code config 解析路径"):
- *   P1. env var `PEAKS_ZCODE_ACTIVE_PROVIDER_UUID` (test seam +
- *       manual pin for the user).
- *   P2. The provider whose top-level UUID key is NOT prefixed
- *       `builtin:` — this matches the user-installed provider
- *       pattern. Within that provider, prefer its `models` first
- *       key (insertion order — z-code writes the active model
- *       first in the picker).
- *   P3. The first provider with `enabled: true`.
- *   P4. The first provider in the object (insertion order) — last
- *       resort. Returns undefined if there are zero providers.
- *
- * Returns `undefined` when nothing matches.
- */
-export declare function resolveZcodeCurrentModel(config: unknown, envOverride?: string | undefined): string | undefined;
-/**
- * The async adapter method that `detectCurrentIdeModel()` calls.
- *
- * Resolution order:
- *   1. `PEAKS_ZCODE_ACTIVE_PROVIDER_UUID` env var override (test seam
- *      + manual pin).
- *   2. `PEAKS_ZCODE_CONFIG_PATH` env var override (test seam for a
- *      fixture file). Falls back to `~/.zcode/v2/config.json`.
- *   3. Returns `undefined` when the file is missing / malformed
- *      (consistent with the cross-IDE contract).
- */
-export declare function detectZcodeCurrentModel(): Promise<string | undefined>;
-export declare const ZCODE_ADAPTER: IdeAdapter;

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

@@ -1,220 +0,0 @@
-/**
- * z-code IDE adapter (slice 2026-07-09-add-zcode-adapter) — peaks-loop 的第九个
- * 内置 IDE 适配器。
- *
- * z-code 是一个 VS Code-style 的 Anthropic-compatible 桌面应用:
- *   - 不是 CLI,没有 `zcode` binary (`which zcode` 返回空)。
- *   - 桌面应用内置了 "导入 skills" 功能,user 手动触发后将本地 skills 目录
- *     与 `~/.zcode/skills` 双向同步 (实测 symlink)。
- *   - hook 协议、project-dir env var、compact command 均未公开。
- *
- * 设计前提 (RD-3 §2.2 D1 决策 + 现场实测,见
- * `.peaks/memory/2026-07-09-zcode-context-probe-handoff.md` §2):
- *   - `compact` 字段全部 undefined — 走 `llm-self-compress` fallback 路径。
- *   - `envVar` / `hookEvent` / `toolMatcher` 全部标注 UNVERIFIED,因为
- *     z-code 文档未公开,本 adapter 用 Anthropic-compatible 协议的合理
- *     假设占位。
- *   - `subAgentDispatcher` 用 `nullSubAgentDispatcher` 占位 — z-code
- *     桌面应用没有公开的 Task 工具 dispatch 协议。
- *   - `standardsProfile` 字段指向宪法文件根 + rules 目录 — z-code 的设计
- *     就是借用上游 "import skills" 目标目录,因此保留上游路径常量。
- *   - `skillInstall` 指向 `~/.zcode/skills` — 实测 z-code 已通过 user
- *     手动导入同步到这里。
- *   - 注:`standardsProfile` 中的常量子段是 z-code 借用的固定路径,属于
- *     架构事实,不算 vendor verb 泄漏。
- *
- * Vendor-neutrality 备注 (SC-3 §5 + RD-3 §2.4):
- *   本文件允许出现 vendor 字符串 (`zcode` / `ZCODE_PROJECT_DIR` 等),
- *   **不允许** 出现其他 vendor 字符串 / 模型名。`standardsProfile`
- *   中的 `CLAUDE.md` / `.claude/rules` 是 z-code 借用的上游路径常量,
- *   属于架构事实,不算 vendor verb 泄漏。
- */
-import { existsSync, readFileSync } from 'node:fs';
-import { homedir } from 'node:os';
-import { join, resolve } from 'node:path';
-import { nullSubAgentDispatcher } from '../../dispatch/sub-agent-dispatcher.js';
-/**
- * Helper exported for tests + internal use: the default location of the
- * z-code v2 config file on the host filesystem.
- */
-export function defaultZcodeConfigPath() {
-    return join(homedir(), '.zcode', 'v2', 'config.json');
-}
-/**
- * Read the z-code config from `path` (string-typed to keep this
- * swappable for tests). Synchronous + Node.js `fs` so adapter callers
- * stay async-only at the public surface (`detectCurrentModel` is
- * already declared `async`).
- */
-function readZcodeConfig(path) {
-    if (!existsSync(path))
-        return undefined;
-    try {
-        return JSON.parse(readFileSync(path, 'utf8'));
-    }
-    catch {
-        return undefined;
-    }
-}
-/**
- * Resolve the active model id from a parsed z-code config payload
- * (the `~/.zcode/v2/config.json` root object). Pure / exported for
- * unit tests so the file-IO seam and the resolution seam are
- * independently verifiable.
- *
- * Resolution order (Slice C §"z-code config 解析路径"):
- *   P1. env var `PEAKS_ZCODE_ACTIVE_PROVIDER_UUID` (test seam +
- *       manual pin for the user).
- *   P2. The provider whose top-level UUID key is NOT prefixed
- *       `builtin:` — this matches the user-installed provider
- *       pattern. Within that provider, prefer its `models` first
- *       key (insertion order — z-code writes the active model
- *       first in the picker).
- *   P3. The first provider with `enabled: true`.
- *   P4. The first provider in the object (insertion order) — last
- *       resort. Returns undefined if there are zero providers.
- *
- * Returns `undefined` when nothing matches.
- */
-export function resolveZcodeCurrentModel(config, envOverride) {
-    const providers = config?.provider;
-    if (!providers || typeof providers !== 'object')
-        return undefined;
-    // P1: env var override (vendor-neutral identifier: the provider UUID).
-    if (envOverride !== undefined && envOverride !== '') {
-        const target = providers[envOverride];
-        if (target && typeof target === 'object') {
-            const modelId = pickFirstModelId(target);
-            if (modelId)
-                return modelId;
-        }
-    }
-    // P2: prefer a non-builtin provider (the user-installed one).
-    for (const [uuid, entry] of Object.entries(providers)) {
-        if (uuid.startsWith('builtin:'))
-            continue;
-        if (!entry || typeof entry !== 'object')
-            continue;
-        const modelId = pickFirstModelId(entry);
-        if (modelId)
-            return modelId;
-    }
-    // P3: first enabled provider (legacy / fresh-install case).
-    for (const entry of Object.values(providers)) {
-        if (!entry || typeof entry !== 'object')
-            continue;
-        const enabled = entry.enabled;
-        if (enabled === true) {
-            const modelId = pickFirstModelId(entry);
-            if (modelId)
-                return modelId;
-        }
-    }
-    // P4: first provider at all.
-    for (const entry of Object.values(providers)) {
-        if (!entry || typeof entry !== 'object')
-            continue;
-        const modelId = pickFirstModelId(entry);
-        if (modelId)
-            return modelId;
-    }
-    return undefined;
-}
-function pickFirstModelId(provider) {
-    const models = provider.models;
-    if (!models || typeof models !== 'object')
-        return undefined;
-    for (const key of Object.keys(models)) {
-        if (typeof key === 'string' && key.trim().length > 0)
-            return key.trim();
-    }
-    return undefined;
-}
-/**
- * The async adapter method that `detectCurrentIdeModel()` calls.
- *
- * Resolution order:
- *   1. `PEAKS_ZCODE_ACTIVE_PROVIDER_UUID` env var override (test seam
- *      + manual pin).
- *   2. `PEAKS_ZCODE_CONFIG_PATH` env var override (test seam for a
- *      fixture file). Falls back to `~/.zcode/v2/config.json`.
- *   3. Returns `undefined` when the file is missing / malformed
- *      (consistent with the cross-IDE contract).
- */
-export async function detectZcodeCurrentModel() {
-    const overridePath = process.env.PEAKS_ZCODE_CONFIG_PATH;
-    const path = overridePath && overridePath.length > 0 ? overridePath : defaultZcodeConfigPath();
-    const config = readZcodeConfig(path);
-    if (config === undefined)
-        return undefined;
-    return resolveZcodeCurrentModel(config, process.env.PEAKS_ZCODE_ACTIVE_PROVIDER_UUID);
-}
-export const ZCODE_ADAPTER = {
-    id: 'zcode',
-    displayName: 'z-code',
-    settings: {
-        dirName: '.zcode', // VERIFIED — 实测 z-code 项目根目录是 `.zcode`
-        settingsFileName: 'settings.json',
-        resolveSettingsFile: (scope, projectRoot) => {
-            const root = scope === 'global' ? homedir() : resolve(projectRoot ?? homedir());
-            return join(root, '.zcode', 'settings.json');
-        },
-        supportsScope: (scope) => scope === 'project' || scope === 'global',
-    },
-    // UNVERIFIED — z-code 桌面应用未公开 `ZCODE_PROJECT_DIR` env var,这里
-    // 用占位符,RD 阶段假设 z-code 借用了 Anthropic-compatible 协议并可能
-    // 注入一个项目根 env 变量。若未注入,峰 router 会回退到 cwd 探测。
-    envVar: 'ZCODE_PROJECT_DIR',
-    // UNVERIFIED — z-code 未公开 hook event key,占位用 Anthropic-compatible
-    // 协议的常见命名 `PreToolUse`。若 z-code 用其他 key,peaks hooks install
-    // 钩子在此 IDE 上不生效,可由 user 通过手动导入绕过。
-    hookEvent: 'PreToolUse',
-    // UNVERIFIED — 同上,占位用 `Bash` matcher。
-    toolMatcher: 'Bash',
-    // Slice 2026-07-09: z-code 桌面应用没有公开 Task 工具 dispatch 协议,
-    // 用 `nullSubAgentDispatcher` 占位 — peaks sub-agent dispatch CLI 在
-    // z-code 上返回 SubAgentNotSupportedError,符合 slice #008 P-5 capability
-    // 检查契约 (CLI 不崩溃)。
-    subAgentDispatcher: nullSubAgentDispatcher,
-    // Slice #010 G9: 假设 z-code 支持 PreToolUse (UNVERIFIED)。Opt-in,等真实
-    // z-code 安装 dogfood 后再决定。若 z-code 不支持 G9 hook,CLI 兜底层仍会
-    // 强制执行 G9 阈值。
-    promptSizeAware: true,
-    installHints: [
-        'z-code 没有 CLI,因此无需重启 — skills symlink 已写入 ~/.zcode/skills/。',
-        '若 z-code 未自动加载 peaks-* skills,在 z-code 桌面应用里手动触发 "导入 skills" 功能即可。',
-    ],
-    capabilities: {
-        gateEnforce: true,
-        statusline: true,
-    },
-    // Standards profile: 路径常量保留 (z-code 的 "导入 skills" 功能
-    // 借用了上游 settings 目录,因此宪法文件路径常量同步保留)。
-    standardsProfile: {
-        rootFile: 'CLAUDE.md',
-        rulesDir: '.claude/rules',
-        rulesFileGlob: '**/*.md',
-        autoLoaded: true,
-        format: 'markdown',
-        migrationHint: 'z-code 借用了上游 standards 路径,无需迁移。',
-    },
-    // Skill install profile: 指向 `~/.zcode/skills` 系列 (实测 z-code 已通过
-    // user 手动 symlink 同步;peaks-loop 也直接支持)。
-    skillInstall: {
-        skillsDir: join(homedir(), '.zcode', 'skills'),
-        outputStylesDir: join(homedir(), '.zcode', 'output-styles'),
-        installStrategy: 'symlink',
-        envVarOverride: 'PEAKS_ZCODE_SKILLS_DIR',
-    },
-    // compact profile 留空 — z-code 没有 CLI binary (RD-3 §2.2 D1 决策)。
-    // peaks-loop 走 `llm-self-compress` fallback 路径 (LLM 自己总结 context),
-    // 不抛错、不警告 (符合 slice #008 P-5 capability-check contract)。
-    // Slice C (2026-07-09 add-zcode-adapter, C.2): runtime probe for
-    // the currently-active model id. Reads `~/.zcode/v2/config.json`
-    // and resolves the active provider via `resolveZcodeCurrentModel`.
-    // See `.peaks/_runtime/2026-07-08-session-17918f/qa/.../slice-C-completion.md`
-    // for the resolution priority chain (env override → non-builtin
-    // provider → first enabled → first provider). Returns undefined
-    // on any failure (consistent with the cross-IDE contract).
-    detectCurrentModel: detectZcodeCurrentModel,
-};

package/dist/src/services/ide/current-model-detector.d.ts

@@ -1,14 +0,0 @@
-/**
- * Probe every registered IDE adapter for its currently-active model
- * id. Returns the first non-empty value found in registration order,
- * or `undefined` when no adapter opts in / all opted-in adapters
- * return undefined.
- *
- * Registration order: see `ide-registry.ts` ADAPTERS Map. The IDE
- * adapter for `claude-code` is consulted first; only `zcode` opts in
- * to this slice's detection (other adapters will return undefined).
- *
- * Async because each IDE adapter's detectCurrentModel may read local
- * disk or env on a slow filesystem.
- */
-export declare function detectCurrentIdeModel(): Promise<string | undefined>;