peaks-cli 1.3.3 → 1.3.5

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

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

@@ -4,31 +4,39 @@ import type { IdeAdapter } from '../ide-types.js';
  *
  * 不可消除的 per-IDE 字段(slice #1 锁定):
  *   - settings.dirName = '.trae'            : Trae 项目根下的配置目录
- *   - settings.settingsFileName = 'settings.json'  (UNVERIFIED at slice time: Trae 实际叫什么待 Trae 1.x 文档确认,先按 Claude 风格)
+ *   - 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'  : UNVERIFIED — Trae 的 hook 数组 key(待 Trae 文档确认,先假设与 Cursor 同名)
- *   - toolMatcher = 'terminal'      : UNVERIFIED — Trae 的 bash 工具 matcher(待 Trae 文档确认)
+ *   - 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`(假设)
- *   - Trae 的 toolMatcher 是 `terminal` 而不是 `Bash`(假设)
- *   - Trae 的 settings 路径是 `.trae/settings.json`(同 Claude 风格,只是目录名不同)
+ *   - 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 风格)
  *
- * 等 Trae 真实文档/真实用户的 dogfood 之后,可能需要把 hookEvent /
- * toolMatcher 替换为 Trae 实际值。slice #2 的 tech-doc 里要明确"此 adapter
- * 是基于 1.x 假设,Trae 真实集成需要在 Trae 上 dogfood 验证"。
+ * 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.
- * Until a real Trae 1.x install dogfoods the byte-level output, treat the
- * UNVERIFIED fields as best-effort defaults.
  */
 export declare const TRAE_ADAPTER: IdeAdapter;

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

@@ -6,39 +6,47 @@ import { traeSubAgentDispatcher } from '../../dispatch/sub-agent-dispatcher.js';
  *
  * 不可消除的 per-IDE 字段(slice #1 锁定):
  *   - settings.dirName = '.trae'            : Trae 项目根下的配置目录
- *   - settings.settingsFileName = 'settings.json'  (UNVERIFIED at slice time: Trae 实际叫什么待 Trae 1.x 文档确认,先按 Claude 风格)
+ *   - 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'  : UNVERIFIED — Trae 的 hook 数组 key(待 Trae 文档确认,先假设与 Cursor 同名)
- *   - toolMatcher = 'terminal'      : UNVERIFIED — Trae 的 bash 工具 matcher(待 Trae 文档确认)
+ *   - 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`(假设)
- *   - Trae 的 toolMatcher 是 `terminal` 而不是 `Bash`(假设)
- *   - Trae 的 settings 路径是 `.trae/settings.json`(同 Claude 风格,只是目录名不同)
+ *   - 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 风格)
  *
- * 等 Trae 真实文档/真实用户的 dogfood 之后,可能需要把 hookEvent /
- * toolMatcher 替换为 Trae 实际值。slice #2 的 tech-doc 里要明确"此 adapter
- * 是基于 1.x 假设,Trae 真实集成需要在 Trae 上 dogfood 验证"。
+ * 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.
- * Until a real Trae 1.x install dogfoods the byte-level output, treat the
- * UNVERIFIED fields as best-effort defaults.
  */
 export const TRAE_ADAPTER = {
     id: 'trae',
     displayName: 'Trae',
     settings: {
         dirName: '.trae',
-        settingsFileName: 'settings.json', // UNVERIFIED — see slice #2 closeout code-review M-1
+        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');
@@ -46,13 +54,12 @@ export const TRAE_ADAPTER = {
         supportsScope: (scope) => scope === 'project' || scope === 'global'
     },
     envVar: 'TRAE_PROJECT_DIR',
-    hookEvent: 'beforeToolCall', // UNVERIFIED — see slice #2 closeout code-review M-1; will be validated when a real Trae 1.x install dogfoods the install path
-    toolMatcher: 'terminal', // UNVERIFIED — see slice #2 closeout code-review M-1
-    subAgentToolMatcher: 'Task', // UNVERIFIED — Trae's sub-agent tool name is unknown; matches the prior hardcoded 'Task' literal so byte-level install output is unchanged. Will be dogfooded when a real Trae 1.x install dispatches a sub-agent.
+    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 slice #008 `subAgentToolMatcher: 'Task'` install entry
-    // stays byte-stable. Awaiting real Trae 1.x dogfood to confirm/replace.
+    // design so the dispatcher shape is uniform across both adapters. Awaiting
+    // real Trae 1.x dogfood to confirm/replace.
     subAgentDispatcher: traeSubAgentDispatcher,
     // Slice #010 G9: Trae supports `beforeToolCall` which can wrap
     // `peaks sub-agent-dispatch-guard`. Opt in (matches the byte-stable
@@ -63,8 +70,27 @@ export const TRAE_ADAPTER = {
     ],
     capabilities: {
         gateEnforce: true,
-        progressStart: true,
         statusline: true,
-        mcpInstall: false // Trae 的 MCP 集成尚未确定,先关掉避免误导
+        // Slice #007-007-2026-06-07-mcp-decouple: mcpInstall is LOAD-BEARING.
+        // The 4 MCP capabilities (playwright, chrome-devtools, figma, context7)
+        // are installed via `peaks mcp plan/apply` which writes to the global
+        // `~/.claude/settings.json` file. Trae 1.x's MCP integration is
+        // UNVERIFIED (the Trae fixture did not dogfood the MCP install path),
+        // so the 6 SKILL.md files must surface a Trae-specific path (manual
+        // install + manual tool invocation) rather than promising `peaks mcp
+        // apply` will work on Trae. Skill bodies consume this flag through
+        // the IDE adapter's `capabilities.mcpInstall`; setting it to true
+        // without a real Trae MCP install dogfood would be a regression.
+        // Cross-reference: .peaks/memory/trae-adapter-sets-mcpinstall-false-trae-mcp-integration-is-unverified.md
+        // and the 4 per-capability memos under .peaks/memory/mcp-decouple-*.md.
+        mcpInstall: false
     }
+    // Standards: UNVERIFIED — see slice #012+ (Trae real-install dogfood for
+    // the `standardsProfile` and `skillInstall` fields). The slice #011
+    // framework lands; per-IDE values for Trae are a follow-up gated on
+    // the user's real Trae 1.x install. Until then, `peaks standards init`
+    // on a Trae-detected project falls back to the Claude Code path
+    // (CLAUDE.md + .claude/rules/**) with a stderr warning, and the
+    // postinstall script writes skills + output-styles to the legacy
+    // `~/.claude/{skills,output-styles}` paths with a stderr warning.
 };

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

@@ -11,10 +11,13 @@ export declare const CLAUDE_CODE_DENY_SHAPE: Record<string, unknown>;
 export declare const CLAUDE_CODE_DENY_TRANSPORT: PeaksDecisionTransport;
 /**
  * Compute the deny decision shape for Trae (Cursor-style sibling IDE).
- * UNVERIFIED — Trae 1.x's actual response envelope is a 1.x assumption
- * (see src/services/ide/adapters/trae-adapter.ts). Slice #3 ships a
- * Cursor-style envelope as the best-effort default; if a future slice
- * confirms Trae's actual shape, update this constant and the related test.
+ * VERIFIED against Trae 1.x fixture — slice 009-009-2026-06-07-trae-dogfood (2026-06-07).
+ * Shape is the standard Cursor/Claude sibling envelope: `hookSpecificOutput`
+ * with `hookEventName`, `permissionDecision`, `permissionDecisionReason`.
+ * The hookEventName is `'beforeToolCall'` for Trae vs `'PreToolUse'` for
+ * Claude Code — the only field that differs between the two siblings.
+ * Fixture: tests/fixtures/trae/trae-1x-payload.json. Constant NAME preserved
+ * (per slice 009 PRD R-3); only the shape was already correct from slice #3.
  */
 export declare const TRAE_DENY_SHAPE: Record<string, unknown>;
 export declare const TRAE_DENY_TRANSPORT: PeaksDecisionTransport;

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

@@ -19,10 +19,13 @@ export const CLAUDE_CODE_DENY_TRANSPORT = {
 };
 /**
  * Compute the deny decision shape for Trae (Cursor-style sibling IDE).
- * UNVERIFIED — Trae 1.x's actual response envelope is a 1.x assumption
- * (see src/services/ide/adapters/trae-adapter.ts). Slice #3 ships a
- * Cursor-style envelope as the best-effort default; if a future slice
- * confirms Trae's actual shape, update this constant and the related test.
+ * VERIFIED against Trae 1.x fixture — slice 009-009-2026-06-07-trae-dogfood (2026-06-07).
+ * Shape is the standard Cursor/Claude sibling envelope: `hookSpecificOutput`
+ * with `hookEventName`, `permissionDecision`, `permissionDecisionReason`.
+ * The hookEventName is `'beforeToolCall'` for Trae vs `'PreToolUse'` for
+ * Claude Code — the only field that differs between the two siblings.
+ * Fixture: tests/fixtures/trae/trae-1x-payload.json. Constant NAME preserved
+ * (per slice 009 PRD R-3); only the shape was already correct from slice #3.
  */
 export const TRAE_DENY_SHAPE = {
     hookSpecificOutput: {

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

@@ -16,8 +16,6 @@ export type IdeId = 'claude-code' | 'trae' | 'codex' | 'cursor' | 'qoder' | 'ton
 export interface IdeCapabilities {
     /** peaks gate enforce 是否适用该 IDE(必备) */
     readonly gateEnforce: true;
-    /** peaks progress start(sub-agent 派发)是否适用 */
-    readonly progressStart: boolean;
     /** peaks statusline 状态栏是否适用 */
     readonly statusline: boolean;
     /** peaks mcp install 是否适用 */
@@ -48,23 +46,10 @@ export interface IdeAdapter {
     readonly hookEvent: string;
     /** hook 数组元素的 matcher 字段(工具名匹配),例如 'Bash' / 'Task' / 'terminal' */
     readonly toolMatcher: string;
-    /**
-     * The tool name used by this IDE to invoke a sub-agent (e.g. Claude Code
-     * uses 'Task' to dispatch a sub-agent, Trae may use a different name).
-     * Consumed by the `peaks progress start` hook entry so each IDE self-
-     * reports its sub-agent tool name. Additive on `toolMatcher`: the
-     * `toolMatcher` field still drives the gate-enforce hook entry, this
-     * one drives the sub-agent-progress hook entry.
-     *
-     * Added in slice 2026-06-06-sub-agent-spawn-bug-and-decouple.
-     */
-    readonly subAgentToolMatcher: string;
     /**
      * Per-IDE sub-agent dispatcher. The `peaks sub-agent dispatch` CLI reads
      * this field, calls `supportsRole` + `buildToolCall`, and returns the
-     * resulting tool-call descriptor in the JSON envelope. Additive on
-     * `subAgentToolMatcher`: the matcher still drives the gate-enforce hook
-     * entry; this field drives the runtime sub-agent dispatch surface.
+     * resulting tool-call descriptor in the JSON envelope. Encapsulates the per-IDE sub-agent dispatch surface (slice #009). The dispatcher's `buildToolCall` returns the IDE-native tool-call descriptor at runtime.
      *
      * Added in slice 2026-06-07-sub-agent-dispatch-decouple. See PRD #002
      * G1 (AC-1, AC-2) + [[slim-ideadapter-shape-is-the-contract]].
@@ -90,6 +75,66 @@ export interface IdeAdapter {
     readonly installHints: readonly string[];
     /** 该 IDE 在 peaks 上可启用的能力(用于在不支持的 IDE 上软警告) */
     readonly capabilities: IdeCapabilities;
+    /**
+     * Where this IDE reads its project-level agent instructions from.
+     * When undefined, the postinstall + `peaks standards init` codepath falls
+     * back to the legacy Claude Code path (CLAUDE.md + .claude/rules/**)
+     * AND emits a stderr warning. Adapters in slice 1.3.2 declare this
+     * value (Claude Code), are annotated UNVERIFIED for future slices
+     * (Trae, slice #012+), or omit it entirely (not-yet-registered IDEs).
+     *
+     * Added in slice 011-2026-06-07-ide-adapter-resource-profile.
+     */
+    readonly standardsProfile?: IdeStandardsProfile;
+    /**
+     * Where `scripts/install-skills.mjs` symlinks the bundled skills +
+     * output styles. When undefined, the postinstall falls back to
+     * `~/.claude/skills` + `~/.claude/output-styles` (legacy) AND emits
+     * a stderr warning. Adapters that opt into the dispatch layer fill
+     * this; adapters that don't (Trae in slice 1.3.2) leave it undefined
+     * and follow the legacy path with a warning.
+     *
+     * Added in slice 011-2026-06-07-ide-adapter-resource-profile.
+     */
+    readonly skillInstall?: IdeSkillInstall;
+}
+/**
+ * Per-IDE standards-file location + format profile. Used by the
+ * `peaks standards init` dispatch layer (slice 011) to write the
+ * project-level standards files at the IDE-specific path, not the
+ * Claude Code hardcoded one. Adapters that omit this field trigger
+ * the legacy Claude Code path with a stderr warning.
+ */
+export interface IdeStandardsProfile {
+    /** Filename for the project-root constitution (e.g. 'CLAUDE.md'), or null if the IDE has no equivalent. */
+    readonly rootFile: string | null;
+    /** Directory for module-level rules (e.g. '.claude/rules'), or null if the IDE has no equivalent. */
+    readonly rulesDir: string | null;
+    /** Glob under rulesDir to enumerate rule files. */
+    readonly rulesFileGlob: string;
+    /** True if the IDE auto-loads these files at session start. */
+    readonly autoLoaded: boolean;
+    /** Output format. markdown = plain text; markdown+frontmatter = adds YAML frontmatter to each rule file. */
+    readonly format: 'markdown' | 'markdown+frontmatter';
+    /** Human-readable hint surfaced in the fallback warning. */
+    readonly migrationHint?: string;
+}
+/**
+ * Per-IDE postinstall target roots. The `scripts/install-skills.mjs`
+ * script consumes this to symlink the bundled skills + output styles
+ * to the IDE-specific install location, with back-compat for the
+ * legacy `PEAKS_CLAUDE_SKILLS_DIR` / `PEAKS_CLAUDE_OUTPUT_STYLES_DIR`
+ * env vars (precedence: explicit option > env var > IDE profile > legacy default).
+ */
+export interface IdeSkillInstall {
+    /** Absolute path under which the postinstall script symlinks the bundled `skills/` directory. */
+    readonly skillsDir: string;
+    /** Absolute path under which the postinstall script writes the bundled `output-styles/`. Null if the IDE has no equivalent. */
+    readonly outputStylesDir: string | null;
+    /** Symlink strategy. */
+    readonly installStrategy: 'symlink' | 'copy';
+    /** Back-compat env var name (e.g. PEAKS_CLAUDE_SKILLS_DIR). Null if no env var is supported. */
+    readonly envVarOverride: string | null;
 }
 /** peaks canonical hook schema 版本标识 */
 export declare const PEAKS_HOOK_SCHEMA: "peaks-hook/v1";

package/dist/src/services/ide/resource-profile.d.ts

@@ -0,0 +1,52 @@
+/**
+ * Resource profile accessors for the per-IDE dispatch layer.
+ *
+ * Slice #011-2026-06-07-ide-adapter-resource-profile introduced two new
+ * optional fields on the `IdeAdapter` interface:
+ *
+ *   - `standardsProfile` — where the IDE reads its project-level
+ *     agent instructions (root file + rules directory + format).
+ *   - `skillInstall`     — where the postinstall script symlinks the
+ *     bundled skills + output styles.
+ *
+ * These accessors are the single chokepoint for "given an IdeId, where
+ * does the IDE read X from?". The two consumers that consume them:
+ *
+ *   1. `src/services/standards/ide-aware-standards-service.ts` —
+ *      wraps `peaks standards init/update` to dispatch on the detected
+ *      IDE rather than always writing CLAUDE.md + .claude/rules/**.
+ *   2. `scripts/install-skills.mjs` (loaded via dynamic import) — the
+ *      postinstall script dispatches on detected IDEs to install
+ *      skills at the IDE-specific target root.
+ *
+ * Future slices add Cursor / Codex / Qoder / Tongyi Lingma by filling
+ * the per-IDE values on the adapter; the accessors and the dispatch
+ * layer do not change.
+ */
+import type { IdeId, IdeSkillInstall, IdeStandardsProfile } from './ide-types.js';
+/** Result of `detectAllResourceTargets` — one entry per registered adapter. */
+export interface ResourceTarget {
+    readonly ideId: IdeId;
+    readonly standardsProfile: IdeStandardsProfile | null;
+    readonly skillInstall: IdeSkillInstall | null;
+}
+/**
+ * Look up the standards-file profile for a given IDE. Returns `null`
+ * if the adapter is registered but does not declare a standards profile
+ * (Trae in slice #011 — annotated `Standards: UNVERIFIED` for slice #012+).
+ * Throws if the IDE id is not registered at all.
+ */
+export declare function getStandardsProfile(ideId: IdeId): IdeStandardsProfile | null;
+/**
+ * Look up the skill-install profile for a given IDE. Returns `null`
+ * if the adapter does not declare one (Trae in slice #011). Throws
+ * if the IDE id is not registered.
+ */
+export declare function getSkillInstall(ideId: IdeId): IdeSkillInstall | null;
+/**
+ * Enumerate all registered adapters and return their resource profiles.
+ * Used by `install-skills.mjs` (and any future fan-out consumer) that
+ * needs to install across multiple IDEs at once. Returns the profiles
+ * in adapter insertion order.
+ */
+export declare function detectAllResourceTargets(): readonly ResourceTarget[];

package/dist/src/services/ide/resource-profile.js

@@ -0,0 +1,33 @@
+import { getAdapter, listAdapterIds } from './ide-registry.js';
+/**
+ * Look up the standards-file profile for a given IDE. Returns `null`
+ * if the adapter is registered but does not declare a standards profile
+ * (Trae in slice #011 — annotated `Standards: UNVERIFIED` for slice #012+).
+ * Throws if the IDE id is not registered at all.
+ */
+export function getStandardsProfile(ideId) {
+    const adapter = getAdapter(ideId);
+    return adapter.standardsProfile ?? null;
+}
+/**
+ * Look up the skill-install profile for a given IDE. Returns `null`
+ * if the adapter does not declare one (Trae in slice #011). Throws
+ * if the IDE id is not registered.
+ */
+export function getSkillInstall(ideId) {
+    const adapter = getAdapter(ideId);
+    return adapter.skillInstall ?? null;
+}
+/**
+ * Enumerate all registered adapters and return their resource profiles.
+ * Used by `install-skills.mjs` (and any future fan-out consumer) that
+ * needs to install across multiple IDEs at once. Returns the profiles
+ * in adapter insertion order.
+ */
+export function detectAllResourceTargets() {
+    return listAdapterIds().map((ideId) => ({
+        ideId,
+        standardsProfile: getStandardsProfile(ideId),
+        skillInstall: getSkillInstall(ideId),
+    }));
+}

package/dist/src/services/memory/project-context-service.js

@@ -1,6 +1,7 @@
 import { existsSync, mkdirSync, readdirSync, readFileSync, writeFileSync } from 'node:fs';
 import { join } from 'node:path';
 import { listSessionMetas } from '../session/session-manager.js';
+import { getSessionDir } from '../session/getSessionDir.js';
 const PROJECT_CONTEXT_FILE = '.peaks/PROJECT.md';
 const CONTEXT_HEADER = `# Peaks Project Context
 
@@ -89,7 +90,7 @@ function buildSessionHistory(projectRoot) {
         const title = (meta.title ?? 'Untitled').slice(0, 40);
         const skill = meta.skill ?? '-';
         // Extract one-line summary from artifacts for the "What" column
-        const sessionRoot = join(projectRoot, '.peaks', meta.sessionId);
+        const sessionRoot = getSessionDir(projectRoot, meta.sessionId);
         const summary = extractOneLineSummary(sessionRoot);
         const brief = summary ? summary.slice(0, 70) : skill;
         body += `| ${date} | \`${dir}\` | ${title} | ${brief} |\n`;

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

@@ -2,6 +2,7 @@ import { closeSync, constants, copyFileSync, existsSync, lstatSync, mkdirSync, o
 import { dirname, basename, isAbsolute, join, relative, resolve } from 'node:path';
 import { isInsidePath, isWindowsAbsolutePath, normalizePath, resolveInputPath, stablePath, stableRealPath } from '../../shared/path-utils.js';
 import { containsSensitiveConfigValue, isSensitiveConfigPath } from '../config/config-service.js';
+import { getSessionDir } from '../session/getSessionDir.js';
 // Hot kinds: full body kept in index for always-available context
 const HOT_KINDS = new Set(['feedback', 'decision', 'rule', 'convention', 'module', 'lesson']);
 // ---------------------------------------------------------------------------
@@ -237,13 +238,13 @@ function summarizeMemoryBody(body) {
 function assertSafeSessionDir(projectRoot, sessionId) {
     const normalizedRoot = normalizeRoot(projectRoot);
     const realRoot = normalizeRealRoot(projectRoot);
-    const sessionDir = join(normalizedRoot, '.peaks', sessionId);
+    const sessionDir = getSessionDir(normalizedRoot, sessionId);
     if (!existsSync(sessionDir)) {
         // Distinguish "not found" (caller will treat as no-op) from "escapes project
         // root" (caller must surface a hard error). We probe by checking whether the
         // joined path, after realpath, would still be inside the project root.
-        if (isAbsolute(join(normalizedRoot, '.peaks', sessionId))) {
-            const realJoined = safeRealpath(join(normalizedRoot, '.peaks', sessionId));
+        if (isAbsolute(getSessionDir(normalizedRoot, sessionId))) {
+            const realJoined = safeRealpath(getSessionDir(normalizedRoot, sessionId));
             if (realJoined && !isInsidePath(realJoined, realRoot)) {
                 throw new Error('Session directory must stay inside the project root');
             }

package/dist/src/services/perf/perf-baseline-service.js

@@ -39,6 +39,7 @@ import { mkdir, writeFile } from 'node:fs/promises';
 import { existsSync } from 'node:fs';
 import { join } from 'node:path';
 import { getSessionId } from '../session/session-manager.js';
+import { getSessionDir } from '../session/getSessionDir.js';
 import { findProjectRoot } from '../config/config-safety.js';
 const README_BODY = `# Performance baseline
 
@@ -117,7 +118,7 @@ function renderBaselineTemplate() {
 function buildPlan(projectRoot, apply) {
     const sessionId = getSessionId(projectRoot);
     const sessionRoot = sessionId !== null
-        ? join(projectRoot, '.peaks', sessionId)
+        ? getSessionDir(projectRoot, sessionId)
         : null;
     const perfBaselinePath = sessionRoot !== null
         ? join(sessionRoot, 'rd', 'perf-baseline.md')