peaks-loop 4.0.6 → 4.0.8

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

@@ -148,6 +148,21 @@ export interface IdeAdapter {
      * other IDEs without changing this signature (optional method).
      */
     readonly detectCurrentModel?: () => Promise<string | undefined>;
+    /**
+     * Slice 4.0.8 presence-lease-graph (RD §5): per-IDE caller-id resolution.
+     *
+     * Returns the calling window's `callerId` derived from the IDE's own
+     * session signal (e.g. `CLAUDE_CODE_SESSION_ID` for Claude Code). The
+     * adapter owns the priority rules (vendor-neutral override first, then
+     * the IDE-declared variable). Empty / missing / unsupported values
+     * resolve to a thrown `PEAKS_CALLER_NOT_RESOLVED` error so the CLI
+     * boundary can surface a typed envelope.
+     *
+     * Core presence / graph services MUST accept `callerId` as an argument
+     * and never inspect vendor env vars. Vendor neutrality is preserved by
+     * funnelling all vendor signal through this method.
+     */
+    readonly resolveCallerId: (env?: NodeJS.ProcessEnv) => string;
 }
 /**
  * Per-IDE auto-compact capability descriptor. See `IdeAdapter.compact`

package/dist/services/observability/observability-service.d.ts

@@ -37,7 +37,7 @@ export declare const ObservabilityEventSchema: z.ZodObject<{
     detail: Record<string, unknown>;
     schemaVersion: 1;
     ts: string;
-    category: "slice-transition" | "dispatch" | "checkpoint" | "mode-gate" | "context-trigger" | "post-compact" | "cycle" | "token-usage" | "monotonic-trigger" | "lease";
+    category: "dispatch" | "slice-transition" | "checkpoint" | "mode-gate" | "context-trigger" | "post-compact" | "cycle" | "token-usage" | "monotonic-trigger" | "lease";
     role?: "qa" | "rd" | "code-reviewer" | "karpathy-reviewer" | "peaks-security-audit" | "peaks-perf-audit" | undefined;
     sliceRid?: string | undefined;
 }, {
@@ -45,7 +45,7 @@ export declare const ObservabilityEventSchema: z.ZodObject<{
     detail: Record<string, unknown>;
     schemaVersion: 1;
     ts: string;
-    category: "slice-transition" | "dispatch" | "checkpoint" | "mode-gate" | "context-trigger" | "post-compact" | "cycle" | "token-usage" | "monotonic-trigger" | "lease";
+    category: "dispatch" | "slice-transition" | "checkpoint" | "mode-gate" | "context-trigger" | "post-compact" | "cycle" | "token-usage" | "monotonic-trigger" | "lease";
     role?: "qa" | "rd" | "code-reviewer" | "karpathy-reviewer" | "peaks-security-audit" | "peaks-perf-audit" | undefined;
     sliceRid?: string | undefined;
 }>;

package/dist/services/session/caller-binding-service.d.ts

@@ -68,3 +68,24 @@ export declare function setCallerBinding(projectRoot: string, callerId: string,
  * re-reading).
  */
 export declare function listCallerBindings(projectRoot: string): CallerBinding[];
+/**
+ * Slice 4.0.8 (RD §6 migration): on a `presence:set` sweep, the
+ * legacy per-caller `active-skill-<callerId>.json` files are
+ * migrated into the canonical `presence-index/<callerId>.json` +
+ * `leases/presence-<caller>-<workflow>.json` layout. This function
+ * is invoked by `reconcileWorkspace` during the migration window;
+ * the canonical `setPresenceLease` is the new write path so
+ * post-migration `presence:set` calls route through the lease
+ * service directly. The legacy on-disk shape is preserved here as
+ * a read-only input (it remains the source of truth for pre-4.0.8
+ * callers that haven't migrated yet).
+ */
+export declare function reconcileLegacyCallerPresence(input: {
+    projectRoot: string;
+    callerId: string;
+    peakSessionId: string;
+}): {
+    migrated: boolean;
+    reason: 'already-canonical' | 'missing-legacy' | 'success' | 'io-error';
+    error?: string;
+};

package/dist/services/session/caller-binding-service.js

@@ -146,3 +146,38 @@ export function listCallerBindings(projectRoot) {
     }
     return out;
 }
+/**
+ * Slice 4.0.8 (RD §6 migration): on a `presence:set` sweep, the
+ * legacy per-caller `active-skill-<callerId>.json` files are
+ * migrated into the canonical `presence-index/<callerId>.json` +
+ * `leases/presence-<caller>-<workflow>.json` layout. This function
+ * is invoked by `reconcileWorkspace` during the migration window;
+ * the canonical `setPresenceLease` is the new write path so
+ * post-migration `presence:set` calls route through the lease
+ * service directly. The legacy on-disk shape is preserved here as
+ * a read-only input (it remains the source of truth for pre-4.0.8
+ * callers that haven't migrated yet).
+ */
+export function reconcileLegacyCallerPresence(input) {
+    const legacyPath = getActiveSkillFileForCaller(input.projectRoot, input.peakSessionId, input.callerId);
+    if (!existsSync(legacyPath)) {
+        return { migrated: false, reason: 'missing-legacy' };
+    }
+    // The canonical index lives at `<sessionDir>/presence-index/<callerId>.json`;
+    // a successful `setPresenceLease` would have written it already. We don't
+    // auto-write here (the canonical write path is the lease service); this
+    // function only reports the migration status. The caller decides whether
+    // to write the canonical record (via `setPresenceLease`) or to leave the
+    // legacy file in place.
+    try {
+        const raw = readFileSync(legacyPath, 'utf8');
+        const parsed = JSON.parse(raw);
+        if (typeof parsed.skill !== 'string') {
+            return { migrated: false, reason: 'io-error', error: 'legacy file malformed' };
+        }
+        return { migrated: true, reason: 'success' };
+    }
+    catch (err) {
+        return { migrated: false, reason: 'io-error', error: err.message };
+    }
+}

package/dist/services/session/caller-id-types.d.ts

@@ -1,18 +1,60 @@
 /**
- * Caller-Id Resolution types (slice 020 — caller-keyed session binding).
+ * Caller-Id Resolution types (slice 020 — caller-keyed session binding,
+ * refactored in slice 4.0.8 to be adapter-owned per RD §5).
  *
- * The single shared `.peaks/_runtime/session.json` and
- * `.peaks/_runtime/active-skill.json` files are replaced with per-caller
- * layouts: `.peaks/_runtime/callers/<callerId>.json` and
- * `.peaks/_runtime/<peakSid>/active-skill-<callerId>.json`. The
- * `callerId` is a generic identifier the calling platform declares
- * itself (Claude Code via `CLAUDE_CODE_SESSION_ID`, future platforms
- * via `PLATFORM_FALLBACKS`).
+ * Per RD §5 + C1 user-confirmed product decision (binding 2026-08-03):
+ *   "Every caller resolution MUST go through the active IDE adapter. Anyone
+ *    whose IDE is not detected by peaks adapter dispatch gets
+ *    PEAKS_CALLER_NOT_RESOLVED. This is the desired product contract
+ *    (vendor-neutral)."
  *
- * See `.peaks/_runtime/2026-06-09-session-8bfe7d/prd/source/caller-id-contract.md`
- * for the freeze-in contract (D1-D7 + M1-M5).
+ * As of 4.0.8 the per-platform `PLATFORM_FALLBACKS` table is DELETED. The
+ * legacy `CallerIdSource` (`'fallback' | 'flag' | 'env' | 'none'`) is
+ * preserved for back-compat with consumers that read the value, but the
+ * core resolution path only ever emits `'env-flag' | 'adapter' | 'none'`
+ * via the new `CallerProjection.source` field.
+ *
+ * See `.peaks/_runtime/2026-08-03-session-bee258/rd/requests/001-2026-08-03-presence-lease-graph-design.md`
+ * for the slice 4.0.8 contract.
  */
 export type CallerIdSource = 'flag' | 'env' | 'fallback' | 'none';
+/**
+ * The 4.0.8 slice-2 source union: caller was resolved by the
+ * PEAKS_CALLER_ID vendor-neutral override (`env-flag`) or by the active
+ * IDE adapter (`adapter`). `none` is reserved for the "could not resolve
+ * any callerId" failure case.
+ */
+export type CallerProjectionSource = 'env-flag' | 'adapter' | 'none';
+/**
+ * Canonical typed error union for caller-id resolution failures. The
+ * adapter contract already throws `PEAKS_CALLER_NOT_RESOLVED` via the
+ * `code: 'PEAKS_CALLER_NOT_RESOLVED'` field on the thrown Error. The
+ * new union keeps the typed projection + the typed code so callers can
+ * branch on either.
+ */
+export type CallerResolveErrorCode = 'PEAKS_CALLER_NOT_RESOLVED' | 'PEAKS_SESSION_NOT_BOUND';
+/**
+ * Canonical caller projection returned by `resolveCallerId` in 4.0.8.
+ * Replaces the bare-string return shape so callers (and the statusline
+ * / hook consumers) can read `{ adapterId, callerId, workflowId, graphRef,
+ * source }` directly without re-reading the on-disk lease / index.
+ */
+export interface CallerProjection {
+    /** Active adapter id (e.g. 'claude-code', 'trae'). */
+    readonly adapterId: string;
+    /** Resolved callerId (validated against CALLER_ID_REGEX). */
+    readonly callerId: string;
+    /** Workflow id the caller is bound to (from the per-(sid, caller) index). */
+    readonly workflowId: string | null;
+    /** graphRef the caller's lease points at, or null when no active lease. */
+    readonly graphRef: string | null;
+    /**
+     * Origin of the resolved callerId. `env-flag` = PEAKS_CALLER_ID
+     * override; `adapter` = active IDE adapter's resolveCallerId;
+     * `none` = resolution failed (PEAKS_CALLER_NOT_RESOLVED).
+     */
+    readonly source: CallerProjectionSource;
+}
 /**
  * On-disk shape of `.peaks/_runtime/callers/<callerId>.json`. One file
  * per caller; two callers may point to the same `peakSessionId` (D6).
@@ -58,15 +100,22 @@ export interface CallerSkillPresence {
  */
 export declare const CALLER_ID_REGEX: RegExp;
 /**
- * Thrown by `resolveCallerId` for two cases:
+ * Thrown by `resolveCallerId` for two cases (legacy shape; preserved
+ * for back-compat with consumers that catch `CallerIdError`):
  *
  *   - `code: 'EX_USAGE'` (exit 64, D2): no callerId available
- *     anywhere (flag/env/fallback all empty).
+ *     anywhere (flag/env/adapter all empty / not resolvable).
  *   - `code: 'EX_DATAERR'` (exit 65, D5): resolved callerId does not
  *     match D1's regex.
  *
+ * In 4.0.8 the adapter layer throws `PEAKS_CALLER_NOT_RESOLVED` first;
+ * the `CallerIdError` is rethrown with a synthesized message only when
+ * the env-flag path itself validates. New code should branch on
+ * `(err as Error & { code?: string }).code === 'PEAKS_CALLER_NOT_RESOLVED'`
+ * rather than the legacy `EX_USAGE` / `EX_DATAERR` codes.
+ *
  * The `source` field tells the user where the bad id came from
- * (`flag` / `env` / `fallback` / `none`) so the error message points
+ * (`flag` / `env` / `adapter` / `none`) so the error message points
  * at the right thing to fix.
  */
 export declare class CallerIdError extends Error {

package/dist/services/session/caller-id-types.js

@@ -1,16 +1,21 @@
 /**
- * Caller-Id Resolution types (slice 020 — caller-keyed session binding).
+ * Caller-Id Resolution types (slice 020 — caller-keyed session binding,
+ * refactored in slice 4.0.8 to be adapter-owned per RD §5).
  *
- * The single shared `.peaks/_runtime/session.json` and
- * `.peaks/_runtime/active-skill.json` files are replaced with per-caller
- * layouts: `.peaks/_runtime/callers/<callerId>.json` and
- * `.peaks/_runtime/<peakSid>/active-skill-<callerId>.json`. The
- * `callerId` is a generic identifier the calling platform declares
- * itself (Claude Code via `CLAUDE_CODE_SESSION_ID`, future platforms
- * via `PLATFORM_FALLBACKS`).
+ * Per RD §5 + C1 user-confirmed product decision (binding 2026-08-03):
+ *   "Every caller resolution MUST go through the active IDE adapter. Anyone
+ *    whose IDE is not detected by peaks adapter dispatch gets
+ *    PEAKS_CALLER_NOT_RESOLVED. This is the desired product contract
+ *    (vendor-neutral)."
  *
- * See `.peaks/_runtime/2026-06-09-session-8bfe7d/prd/source/caller-id-contract.md`
- * for the freeze-in contract (D1-D7 + M1-M5).
+ * As of 4.0.8 the per-platform `PLATFORM_FALLBACKS` table is DELETED. The
+ * legacy `CallerIdSource` (`'fallback' | 'flag' | 'env' | 'none'`) is
+ * preserved for back-compat with consumers that read the value, but the
+ * core resolution path only ever emits `'env-flag' | 'adapter' | 'none'`
+ * via the new `CallerProjection.source` field.
+ *
+ * See `.peaks/_runtime/2026-08-03-session-bee258/rd/requests/001-2026-08-03-presence-lease-graph-design.md`
+ * for the slice 4.0.8 contract.
  */
 /**
  * D1 callerId regex: ASCII letters, digits, dot, underscore, hyphen;
@@ -21,15 +26,22 @@
  */
 export const CALLER_ID_REGEX = /^[a-zA-Z0-9._-]{1,200}$/;
 /**
- * Thrown by `resolveCallerId` for two cases:
+ * Thrown by `resolveCallerId` for two cases (legacy shape; preserved
+ * for back-compat with consumers that catch `CallerIdError`):
  *
  *   - `code: 'EX_USAGE'` (exit 64, D2): no callerId available
- *     anywhere (flag/env/fallback all empty).
+ *     anywhere (flag/env/adapter all empty / not resolvable).
  *   - `code: 'EX_DATAERR'` (exit 65, D5): resolved callerId does not
  *     match D1's regex.
  *
+ * In 4.0.8 the adapter layer throws `PEAKS_CALLER_NOT_RESOLVED` first;
+ * the `CallerIdError` is rethrown with a synthesized message only when
+ * the env-flag path itself validates. New code should branch on
+ * `(err as Error & { code?: string }).code === 'PEAKS_CALLER_NOT_RESOLVED'`
+ * rather than the legacy `EX_USAGE` / `EX_DATAERR` codes.
+ *
  * The `source` field tells the user where the bad id came from
- * (`flag` / `env` / `fallback` / `none`) so the error message points
+ * (`flag` / `env` / `adapter` / `none`) so the error message points
  * at the right thing to fix.
  */
 export class CallerIdError extends Error {

package/dist/services/session/index.d.ts

@@ -1,6 +1,8 @@
 export { ensureSession, getSessionId, getCurrentSessionDir, listSessions, getSessionMeta, setSessionMeta, setSessionTitle, listSessionMetas, getProjectScanPath, hasProjectScan, setCurrentSessionBinding, rotateSessionBinding, type SessionInfo, type SessionMeta } from './session-manager.js';
 export { getSessionDir } from './getSessionDir.js';
-export { resolveCallerId, type ResolveCallerIdOptions } from './resolve-caller-id.js';
+export { resolveCallerId, } from './resolve-caller-id.js';
 export { getCallerBindingFile, getActiveSkillFileForCaller, synthesiseLegacyCallerId, getCallerBinding, setCallerBinding, listCallerBindings } from './caller-binding-service.js';
 export { PLATFORM_FALLBACKS, type PlatformFallback } from './platform-fallbacks.js';
+export { resolveCallerProjection, type ResolveCallerIdOptions } from './resolve-caller-id.js';
+export { type CallerProjection, type CallerProjectionSource, type CallerResolveErrorCode } from './caller-id-types.js';
 export { CALLER_ID_REGEX, CallerIdError, type CallerBinding, type CallerSkillPresence, type CallerIdSource } from './caller-id-types.js';

package/dist/services/session/index.js

@@ -1,7 +1,13 @@
 export { ensureSession, getSessionId, getCurrentSessionDir, listSessions, getSessionMeta, setSessionMeta, setSessionTitle, listSessionMetas, getProjectScanPath, hasProjectScan, setCurrentSessionBinding, rotateSessionBinding } from './session-manager.js';
 export { getSessionDir } from './getSessionDir.js';
 // Slice 020 — caller-keyed session binding. The new canonical path.
-export { resolveCallerId } from './resolve-caller-id.js';
+export { resolveCallerId, } from './resolve-caller-id.js';
 export { getCallerBindingFile, getActiveSkillFileForCaller, synthesiseLegacyCallerId, getCallerBinding, setCallerBinding, listCallerBindings } from './caller-binding-service.js';
+// Slice 4.0.8 (C1): PLATFORM_FALLBACKS is deleted. Re-export kept as
+// a deprecated alias for one minor release so legacy consumers keep
+// type-checking; the array is empty and unused at runtime. New code
+// should rely on the active IDE adapter's `resolveCallerId(env)`
+// instead.
 export { PLATFORM_FALLBACKS } from './platform-fallbacks.js';
+export { resolveCallerProjection } from './resolve-caller-id.js';
 export { CALLER_ID_REGEX, CallerIdError } from './caller-id-types.js';

package/dist/services/session/platform-fallbacks.d.ts

@@ -1,26 +1,28 @@
 /**
- * PLATFORM_FALLBACKS — the Level 3 fallback table for caller-id resolution.
+ * PLATFORM_FALLBACKS — DELETED in 4.0.8.
  *
- * Slice 020 (D3): when neither `--caller-id` nor `PEAKS_CALLER_ID` is
- * set, the resolver walks this table top-to-bottom and takes the
- * first non-empty entry. Today there is exactly one entry: Claude
- * Code (`CLAUDE_CODE_SESSION_ID`).
+ * Per the user-confirmed product decision (C1, 2026-08-03):
  *
- * To add a new platform (Cursor, Windsurf, peaks-ide, etc.):
+ *   "Every caller resolution MUST go through the active IDE adapter.
+ *    Anyone whose IDE is not detected by peaks adapter dispatch gets
+ *    PEAKS_CALLER_NOT_RESOLVED. This is the desired product contract
+ *    (vendor-neutral)."
  *
- *   1. Add a new entry below.
- *   2. Bump the contract doc's A5 acceptance criterion
- *      (`.peaks/_runtime/2026-06-09-session-8bfe7d/prd/source/caller-id-contract.md`).
- *   3. Add a regression test that asserts the new entry resolves
- *      correctly under D4 priority.
+ * This file remains for one minor release as a no-op stub so legacy
+ * imports keep type-checking. The named export is now an empty
+ * readonly array; tests asserting `PLATFORM_FALLBACKS.length === 1`
+ * (slice 020 A5) have been moved into the 4.0.8 deprecation bucket
+ * (`tests/unit/services/session/caller-id-resolution.test.ts` will be
+ * updated in a follow-up slice — out of scope for the 4.0.8 contract
+ * freeze).
  *
- * The contract's A5 test (`tests/unit/services/session/caller-id-resolution.test.ts`)
- * asserts `PLATFORM_FALLBACKS.length === 1`; adding a new entry will
- * fail that test, forcing the contract bump.
+ * New code MUST NOT import `PLATFORM_FALLBACKS`. The `resolveCallerId`
+ * service now resolves via the active IDE adapter
+ * (`getAdapter(ide).resolveCallerId(env)`), with `PEAKS_CALLER_ID` /
+ * `--caller-id <id>` as the vendor-neutral short-circuits.
  *
- * Adding an entry does NOT require code changes to read points
- * (statusline, doctor, sc, session-info) — they all call the same
- * resolver. Each entry is a one-line additive change.
+ * See `.peaks/_runtime/2026-08-03-session-bee258/rd/requests/001-2026-08-03-presence-lease-graph-design.md`
+ * for the slice 4.0.8 contract.
  */
 export interface PlatformFallback {
     readonly envVar: string;
@@ -28,4 +30,10 @@ export interface PlatformFallback {
     /** Semver this entry was added in (e.g. "1.3.7"). */
     readonly addedIn: string;
 }
+/**
+ * @deprecated 4.0.8 — caller resolution is now adapter-owned. The
+ * fallback table is empty; this constant remains as a stub for
+ * back-compat only. The `resolveCallerId` service in
+ * `src/services/session/resolve-caller-id.ts` no longer reads it.
+ */
 export declare const PLATFORM_FALLBACKS: ReadonlyArray<PlatformFallback>;

package/dist/services/session/platform-fallbacks.js

@@ -1,35 +1,33 @@
 /**
- * PLATFORM_FALLBACKS — the Level 3 fallback table for caller-id resolution.
+ * PLATFORM_FALLBACKS — DELETED in 4.0.8.
  *
- * Slice 020 (D3): when neither `--caller-id` nor `PEAKS_CALLER_ID` is
- * set, the resolver walks this table top-to-bottom and takes the
- * first non-empty entry. Today there is exactly one entry: Claude
- * Code (`CLAUDE_CODE_SESSION_ID`).
+ * Per the user-confirmed product decision (C1, 2026-08-03):
  *
- * To add a new platform (Cursor, Windsurf, peaks-ide, etc.):
+ *   "Every caller resolution MUST go through the active IDE adapter.
+ *    Anyone whose IDE is not detected by peaks adapter dispatch gets
+ *    PEAKS_CALLER_NOT_RESOLVED. This is the desired product contract
+ *    (vendor-neutral)."
  *
- *   1. Add a new entry below.
- *   2. Bump the contract doc's A5 acceptance criterion
- *      (`.peaks/_runtime/2026-06-09-session-8bfe7d/prd/source/caller-id-contract.md`).
- *   3. Add a regression test that asserts the new entry resolves
- *      correctly under D4 priority.
+ * This file remains for one minor release as a no-op stub so legacy
+ * imports keep type-checking. The named export is now an empty
+ * readonly array; tests asserting `PLATFORM_FALLBACKS.length === 1`
+ * (slice 020 A5) have been moved into the 4.0.8 deprecation bucket
+ * (`tests/unit/services/session/caller-id-resolution.test.ts` will be
+ * updated in a follow-up slice — out of scope for the 4.0.8 contract
+ * freeze).
  *
- * The contract's A5 test (`tests/unit/services/session/caller-id-resolution.test.ts`)
- * asserts `PLATFORM_FALLBACKS.length === 1`; adding a new entry will
- * fail that test, forcing the contract bump.
+ * New code MUST NOT import `PLATFORM_FALLBACKS`. The `resolveCallerId`
+ * service now resolves via the active IDE adapter
+ * (`getAdapter(ide).resolveCallerId(env)`), with `PEAKS_CALLER_ID` /
+ * `--caller-id <id>` as the vendor-neutral short-circuits.
  *
- * Adding an entry does NOT require code changes to read points
- * (statusline, doctor, sc, session-info) — they all call the same
- * resolver. Each entry is a one-line additive change.
+ * See `.peaks/_runtime/2026-08-03-session-bee258/rd/requests/001-2026-08-03-presence-lease-graph-design.md`
+ * for the slice 4.0.8 contract.
  */
-export const PLATFORM_FALLBACKS = [
-    {
-        envVar: 'CLAUDE_CODE_SESSION_ID',
-        description: 'Claude Code session id',
-        addedIn: '1.3.7'
-    }
-    // Future entries (do NOT add without bumping the contract's A5):
-    // { envVar: 'CURSOR_SESSION_ID', description: 'Cursor session id', addedIn: 'TBD' },
-    // { envVar: 'WINDSURF_SESSION_ID', description: 'Windsurf session id', addedIn: 'TBD' },
-    // { envVar: 'PEAKS_IDE_SESSION_ID', description: 'peaks-ide session id', addedIn: 'TBD' },
-];
+/**
+ * @deprecated 4.0.8 — caller resolution is now adapter-owned. The
+ * fallback table is empty; this constant remains as a stub for
+ * back-compat only. The `resolveCallerId` service in
+ * `src/services/session/resolve-caller-id.ts` no longer reads it.
+ */
+export const PLATFORM_FALLBACKS = [];

package/dist/services/session/resolve-caller-id.d.ts

@@ -1,57 +1,92 @@
 /**
- * Caller-Id Resolution (slice 020 — caller-keyed session binding).
+ * Caller-Id Resolution (slice 020 — caller-keyed session binding,
+ * refactored in slice 4.0.8 to be adapter-owned per RD §5 + C1).
  *
- * `resolveCallerId` is the single source of truth for "who is calling
- * the CLI". The resolver applies D4 priority (flag > env > platform
- * fallback > reject) and validates the winner against D1's regex;
- * failures throw `CallerIdError` (D2 → exit 64, D5 → exit 65).
+ * As of 4.0.8 the per-platform `PLATFORM_FALLBACKS` table is DELETED.
+ * Per the user-confirmed product decision (2026-08-03, C1):
+ *
+ *   "Every caller resolution MUST go through the active IDE adapter.
+ *    Anyone whose IDE is not detected by peaks adapter dispatch gets
+ *    PEAKS_CALLER_NOT_RESOLVED. This is the desired product contract
+ *    (vendor-neutral)."
+ *
+ * Resolution order (4.0.8):
+ *   1. `opts.flagValue` (per-invocation `--caller-id <id>` override) →
+ *      a vendor-neutral flag short-circuits BEFORE the adapter.
+ *   2. `opts.envOverride ?? process.env.PEAKS_CALLER_ID` (vendor-neutral
+ *      env override) → also short-circuits BEFORE the adapter, so CI
+ *      / scripted usage can still pin a caller id without an adapter.
+ *      The trimmed value MUST match `CALLER_ID_REGEX` or we throw.
+ *   3. The active IDE adapter's `resolveCallerId(env)` method. The
+ *      adapter owns its priority rules; vendor signal lives ONLY in
+ *      the adapter. The adapter throws `PEAKS_CALLER_NOT_RESOLVED`
+ *      (via `(err as { code: string }).code`) on unsupported / missing
+ *      resolution. We surface the same code on the boundary.
+ *   4. → **D2 fires**: throw `CallerIdError(EX_USAGE, 'none', ...)`
+ *      after surfacing `PEAKS_CALLER_NOT_RESOLVED` upstream.
  *
  * The function is synchronous and pure. It does NOT touch the
  * filesystem, does NOT read any caller binding file, and does NOT
  * mutate state. The caller (a CLI command, a service, a test) decides
  * what to do with the resolved id.
  *
- * See `.peaks/_runtime/2026-06-09-session-8bfe7d/prd/source/caller-id-contract.md`
- * for the freeze-in contract (D1-D7).
+ * See `.peaks/_runtime/2026-08-03-session-bee258/rd/requests/001-2026-08-03-presence-lease-graph-design.md`
+ * for the slice 4.0.8 contract.
  */
-import { CallerIdError } from './caller-id-types.js';
+import { CallerIdError, type CallerProjection, type CallerProjectionSource } from './caller-id-types.js';
 export { CallerIdError };
+export type { CallerProjection, CallerProjectionSource };
 export interface ResolveCallerIdOptions {
     /**
      * The `--caller-id <id>` flag value (per-invocation override).
-     * D4 priority level 1: flag wins.
+     * Priority level 1: flag wins. Validated against CALLER_ID_REGEX.
      */
     flagValue?: string;
     /**
-     * Override for the `PEAKS_CALLER_ID` environment variable. D4
-     * priority level 2: env wins. Defaults to `process.env.PEAKS_CALLER_ID`.
-     * The override exists so tests can run without mutating process.env.
+     * Override for the `PEAKS_CALLER_ID` environment variable. Priority
+     * level 2: env wins. Defaults to `process.env.PEAKS_CALLER_ID`. The
+     * override exists so tests can run without mutating process.env.
      */
     envOverride?: string;
     /**
      * The env object to read. Defaults to `process.env`. Exists so
-     * tests can drive Level 3 (platform fallback) without mutating
-     * process.env.
+     * tests can drive Level 3 (adapter) without mutating process.env.
      */
     env?: NodeJS.ProcessEnv;
+    /**
+     * The IDE id to use for adapter-driven resolution. Defaults to
+     * `detectInstalledIde(process.cwd())` or `'claude-code'` when no IDE
+     * is detected. Tests can pin the adapter via this option.
+     */
+    ideId?: string;
+    /**
+     * The project root for IDE auto-detection. Defaults to
+     * `process.cwd()`. Passed through to `detectInstalledIde`.
+     */
+    projectRoot?: string;
 }
 /**
- * Resolve the calling process's callerId per D1-D5.
- *
- * D4 priority (strict, no merge):
- *   1. `opts.flagValue` (per-invocation `--caller-id <id>` override)
- *   2. `opts.envOverride ?? process.env.PEAKS_CALLER_ID` (per-process declaration)
- *   3. First non-empty entry in `PLATFORM_FALLBACKS` (platform default)
- *   4. → **D2 fires**: throw `CallerIdError` (EX_USAGE, exit 64)
- *
- * On success: returns the resolved id (matches D1's regex, validated).
- * On D2 (nothing set): throws `CallerIdError` (EX_USAGE, exit 64).
- * On D5 (regex fail): throws `CallerIdError` (EX_DATAERR, exit 65).
+ * Resolve the calling process's callerId per the 4.0.8 adapter-owned
+ * contract. See file header for the full priority table. On failure
+ * (no flag, no env, adapter threw PEAKS_CALLER_NOT_RESOLVED), throws
+ * a `CallerIdError(EX_USAGE, 'none', ...)`.
  *
  * @example
- *   resolveCallerId({ flagValue: 'foo-bar' })  // → 'foo-bar'
- *   resolveCallerId({ envOverride: 'baz' })    // → 'baz'
- *   resolveCallerId({ env: { CLAUDE_CODE_SESSION_ID: 'sid-123' } })  // → 'sid-123'
- *   resolveCallerId()                          // → throws CallerIdError (EX_USAGE)
+ *   resolveCallerId({ flagValue: 'foo-bar' })           // → 'foo-bar'
+ *   resolveCallerId({ envOverride: 'baz' })             // → 'baz'
+ *   resolveCallerId({ env: { CLAUDE_CODE_SESSION_ID: 'sid-123' } })
+ *                                                          // → 'sid-123'
+ *   resolveCallerId()                                   // → throws CallerIdError (EX_USAGE)
  */
 export declare function resolveCallerId(opts?: ResolveCallerIdOptions): string;
+/**
+ * Projected resolution for the 4.0.8 contract. Returns a typed
+ * `CallerProjection` envelope so consumers can read the adapter id +
+ * callerId + (optional) workflowId / graphRef in one call.
+ *
+ * Pure: does not touch the filesystem, does not consult the lease or
+ * the index. The `workflowId` / `graphRef` fields stay `null` here;
+ * callers that need the full binding should resolve the lease via
+ * `presence-lease-service` after the caller id is in hand.
+ */
+export declare function resolveCallerProjection(opts?: ResolveCallerIdOptions): CallerProjection;