peaks-loop 4.1.1 → 4.1.3

package/dist/services/reviewer/selection-strategies.js

@@ -1,6 +1,5 @@
 /**
  * selection-strategies.ts — pick a provider per rid for the G4 third-party
- * reviewer. AC-4.6 requires:
  *   - `round-robin` cycles across providers across slices
  *   - `hash(rid)` is stable per rid (deterministic replay)
  *   - `random` is uniform over the provider set

package/dist/services/runtime/runtime-detector.js

@@ -1,5 +1,4 @@
 /**
- * Runtime detector — slice S2-a of RD-2.
  *
  * Given the current process environment, decide which vendor (if any)
  * is the active AI runtime. Detection order matters: Claude Code is

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

@@ -1,5 +1,4 @@
 /**
- * Runtime service — slice S2-a of RD-2.
  *
  * Orchestrator that wires the runtime detector + vendor adapter
  * registry into a small surface that the CLI commands call. The
@@ -12,7 +11,6 @@
  *  - The service is a thin orchestrator — it does NOT contain any
  *    vendor verb strings (claude / codex / copilot). All vendor verbs
  *    live in `src/services/runtime/vendors/<vendor>.ts`. Verified by
- *    AC-1.
  *  - When `compactVia(id)` is called with an unknown id, the service
  *    returns a "no-op" result with exitCode=0 and a warning instead of
  *    throwing — vendor-neutrality means peaks-loop MUST keep working

package/dist/services/runtime/vendor-adapter.d.ts

@@ -1,5 +1,4 @@
 /**
- * Vendor adapter contract — slice S2-a of RD-2 (2026-07-08 session).
  *
  * Each `VendorAdapter` is a thin wrapper around ONE AI runtime (Claude
  * Code / Codex / Copilot / custom) that knows how to:
@@ -25,11 +24,9 @@
  * orchestrates these adapters (runtime-service.ts) and the CLI commands
  * (`peaks runtime compact --via <id>`) MUST NOT contain vendor verbs.
  *
- * Slice 2026-09-12-auto-compact-vendor-neutrality widened AC-1's scope from
  * `src/services/code/` to ALL of `src/`, and had to change how it is
  * enforced. Both changes came from measurement:
  *
- *   - The old scope excluded the files that carried the defect AC-1
  *     describes — the compact dispatcher (`src/services/context/`) and the
  *     hook installer (`src/services/hooks/`) — so it returned 0 by
  *     construction. A grep over a directory that does not contain the code
@@ -40,15 +37,11 @@
  *     in `src/services/ide/adapters/claude-code-adapter.ts` — the one place
  *     the string is supposed to be. A text grep measures prose, not code.
  *
- * AC-1 is therefore enforced by the AST-based check in
  * `tests/unit/runtime/vendor-neutral-identity-guard.test.ts`: no vendor
  * verb in any STRING LITERAL of `src/` outside the adapter implementations.
  * Parsed, the count is 1 and the single hit is that adapter — which is the
- * property AC-1 was always about.
  *
- * AC-1 covers VERB STRINGS only. The compact path's defects were IDENTITY
  * COMPARISONS (`ideId !== 'claude-code'`), a second shape the same guard
- * file covers and AC-1 never could. Read that guard's header for what
  * neither check catches before treating vendor neutrality as proven.
  *
  * See `.peaks/_runtime/2026-07-08-session-17918f/prd/002-adapter-runtime-and-polyrepo.md`

package/dist/services/runtime/vendors/claude-code.js

@@ -1,5 +1,4 @@
 /**
- * Claude Code vendor adapter — slice S2-a.
  *
  * Stubs the compact verb to `claude --compact` (the canonical vendor
  * verb for Claude Code). The actual binary is invoked via spawn so

package/dist/services/runtime/vendors/codex.js

@@ -1,5 +1,4 @@
 /**
- * Codex vendor adapter — slice S2-a.
  *
  * Stub adapter (PRD out-of-scope: full implementation lands in a
  * future slice). The detect() heuristic is intentionally permissive:

package/dist/services/runtime/vendors/copilot.js

@@ -1,5 +1,4 @@
 /**
- * Copilot vendor adapter — slice S2-a.
  *
  * Stub adapter (PRD out-of-scope: full implementation lands in a
  * future slice). Copilot's compact verb is `copilot compact`

package/dist/services/sc/sc-service.js

@@ -87,7 +87,6 @@ function mapSyncState(syncStatus) {
 }
 function getCurrentArtifactDir(artifactWorkspacePath) {
     const peaksPath = getPeaksPath(artifactWorkspacePath);
-    // Slice 2026-06-29-change-id-root-removal: the `.peaks/_runtime/current-change`
     // binding file is gone. Resolve the active change-id from the workspace
     // session binding instead. When no session is bound, fall back to
     // `unknown-session` (matches the previous behaviour for an unbound workspace).
@@ -102,7 +101,6 @@ function getCurrentArtifactDir(artifactWorkspacePath) {
     };
 }
 function getRetentionChangeDir(artifactWorkspacePath, sliceId) {
-    // Slice 2026-06-29-change-id-root-removal: retention slice dirs
     // remain under the legacy `.peaks/<sliceId>/` shape (they're shipped
     // / frozen artifacts, not session-scoped workspace state). Only the
     // ACTIVE session-dir resolution uses `_runtime/` — retention slices
@@ -163,7 +161,6 @@ function readActiveSkillSessionId(projectRoot) {
  * Read the workspace session binding and return its `sessionId`,
  * or null when the file is missing / malformed.
  *
- * As of slice 2026-06-05-peaks-runtime-layer the canonical home is
  * `<projectRoot>/.peaks/_runtime/session.json`. The legacy
  * `<projectRoot>/.peaks/.session.json` is consulted as a
  * one-minor-release back-compat fallback: if the new path is
@@ -199,7 +196,6 @@ function readSessionJsonBinding(projectRoot) {
  * session does not own the slice.
  */
 function sessionOwnsSlice(projectRoot, sessionId, sliceId) {
-    // As of slice 2026-06-05-change-id-as-unit-of-work, the same
     // session id can live at multiple umbrella locations:
     //   - `.peaks/_runtime/<sessionId>/` (legacy or top-level active)
     //   - `.peaks/retrospective/<sessionId>/` (shipped slice)
@@ -238,7 +234,6 @@ function findSessionOwningSlice(projectRoot, sliceId) {
         return null;
     }
     topLevel.sort();
-    // As of slice 2026-06-05-change-id-as-unit-of-work, shipped slices
     // are archived under `.peaks/retrospective/<dir>/` and dogfood
     // evidence lives under `.peaks/_dogfood/<dir>/`. Both umbrellas host
     // scopes at one level deeper than the top-level `.peaks/_runtime/<dir>/`
@@ -369,7 +364,6 @@ export function getChangeTraceabilityStatus() {
         const artifactPath = resolve(changeDir, ...artifact.path);
         return {
             name: artifact.name,
-            // Slice 2026-06-29-change-id-root-removal: the reported path
             // matches the canonical single-axis layout
             // `.peaks/_runtime/<sid>/...`.
             path: resolve(peaksPath, '_runtime', sessionId ?? '<session-id>', ...artifact.path),

package/dist/services/scan/acceptance-coverage-service.js

@@ -107,10 +107,8 @@ export async function getAcceptanceCoverage(options) {
     if (prdArtifact === null) {
         return { kind: 'prd-not-found' };
     }
-    // As of slice 2026-06-05-change-id-as-unit-of-work, test-cases live
     // under the same change-id dir as the PRD itself (the on-disk scope),
     // not under the body's `- session:` line. Slice
-    // 2026-06-29-change-id-root-removal stripped the legacy
     // `.peaks/_runtime/change/<id>/` indirection — test-cases now live
     // under the canonical session dir `.peaks/_runtime/<sid>/qa/test-cases/`.
     // `prdArtifact.sessionId` is the bare session id (the dir the PRD was

package/dist/services/scan/api-diff-recorded.d.ts

@@ -3,7 +3,6 @@
  * plus the candidate name-grep.
  *
  *   1. `.peaks/_runtime/<sid>/rd/mock-plan.md`  (most recent by mtime)
- *   2. recorded `*-api.types.ts` interfaces     (from (1) + `src/services/types`)
  *   3. the `## API Migration` endpoint list in `.peaks/_runtime/<sid>/txt/*.md`
  *
  * All three are OPTIONAL: absence is reported in the report's `notes`, never

package/dist/services/scan/api-diff-recorded.js

@@ -3,7 +3,6 @@
  * plus the candidate name-grep.
  *
  *   1. `.peaks/_runtime/<sid>/rd/mock-plan.md`  (most recent by mtime)
- *   2. recorded `*-api.types.ts` interfaces     (from (1) + `src/services/types`)
  *   3. the `## API Migration` endpoint list in `.peaks/_runtime/<sid>/txt/*.md`
  *
  * All three are OPTIONAL: absence is reported in the report's `notes`, never

package/dist/services/scan/api-diff-service.d.ts

@@ -1,6 +1,5 @@
 /**
  * S1 / rid=api-diff-report — `peaks scan api-diff <doc>` (design
- * `docs/superpowers/specs/2026-09-12-frontend-acl-contract-design.md` §2.1/§2.3).
  *
  * Read-only. Parses an OpenAPI 3.x document (JSON or YAML — `yaml` is already a
  * runtime dependency) and diffs it against the three sources a consumer project

package/dist/services/scan/api-diff-service.js

@@ -1,6 +1,5 @@
 /**
  * S1 / rid=api-diff-report — `peaks scan api-diff <doc>` (design
- * `docs/superpowers/specs/2026-09-12-frontend-acl-contract-design.md` §2.1/§2.3).
  *
  * Read-only. Parses an OpenAPI 3.x document (JSON or YAML — `yaml` is already a
  * runtime dependency) and diffs it against the three sources a consumer project

package/dist/services/scan/api-diff-types.d.ts

@@ -1,6 +1,5 @@
 /**
  * S1 / rid=api-diff-report — shared types for `peaks scan api-diff <doc>`
- * (design `docs/superpowers/specs/2026-09-12-frontend-acl-contract-design.md`
  * §2.1/§2.3).
  *
  * GOVERNING PRINCIPLE (QA repair): exactness requires BOTH sides to be fully

package/dist/services/scan/api-diff-types.js

@@ -1,6 +1,5 @@
 /**
  * S1 / rid=api-diff-report — shared types for `peaks scan api-diff <doc>`
- * (design `docs/superpowers/specs/2026-09-12-frontend-acl-contract-design.md`
  * §2.1/§2.3).
  *
  * GOVERNING PRINCIPLE (QA repair): exactness requires BOTH sides to be fully

package/dist/services/scan/archetype-service.js

@@ -98,7 +98,6 @@ function decideArchetype(detected) {
     }
     // Monorepo detection runs BEFORE the backend check: a monorepo with
     // a packages/server dir is a fullstack-monorepo, NOT legacy-fullstack.
-    // Slice 2026-07-15 ice-cola hot-fix: previously a monorepo with a
     // backend sub-package fell through to `legacy-fullstack` because
     // `hasBackend` includes `backendDirsPresent.length > 0`, which the
     // L199 guard above couldn't handle. We now treat `hasMonorepoConfig`

package/dist/services/scan/file-size-policy.d.ts

@@ -26,7 +26,6 @@ export declare function inFileSizeScope(file: string): boolean;
  * of a scope extension. Both consumers read this instead of each carrying its own
  * half of the rule.
  *
- * WHY IT MATTERS (F3 of the repair cycle, rid `2026-09-30-cap-unify-01`). The
  * census enumerated its scope with `git ls-files <dirs>` plus the extension test,
  * while the scan measured EVERY changed non-exempt file at `fileSizeCapFor`'s
  * else-branch 300 — including paths in neither list. The two disagreed about the

package/dist/services/scan/file-size-policy.js

@@ -7,7 +7,6 @@
 // `scripts/lint/file-size-census.ts` (the whole-tree count the husky gate
 // ratchets). Neither may restate a number.
 //
-// WHY ONE MODULE (rid 2026-09-30-cap-unify-01). The policy was written twice,
 // in two units: `max-lines: [error, {max: 400, skipBlankLines, skipComments}]`
 // in `config/eslint/.peaks-rules.cjs` and a raw `DEFAULT_FILE_SIZE_THRESHOLD`
 // of 800 here. Two spellings of one decision drift by construction, and the only
@@ -30,7 +29,6 @@
 // A row that silently excluded them would not equal its own measurement — the
 // same class of hole as lint-gate §4b (a surface asserted but never counted).
 //
-// NUMBERS THIS MODULE DOES NOT OWN, DECIDED 2026-09-30 (F6 of the repair cycle).
 // A line-count constant elsewhere in the repo is a second copy of THIS policy only
 // if it decides the same question — "may this file be committed at this size?".
 // Three that do not, recorded here so the next reader does not re-litigate them:
@@ -43,7 +41,6 @@
 //     this cap and is NOT folded into it — folding it in would silently change what
 //     the legacy report says. Its name does not match the census's `CAP_NAME`
 //     second-copy rule on purpose; see lint-gate §4b row 7.
-//   - `src/services/skills/lint-reference-shape.ts` 800: the shape of an
 //     example lint report, not a cap.
 /** Raw-line cap for `src/`, `scripts/` and `packages/` — including a `tests` directory inside a package. */
 export const FILE_SIZE_CAP_DEFAULT = 300;
@@ -84,7 +81,6 @@ export function inFileSizeScope(file) {
  * of a scope extension. Both consumers read this instead of each carrying its own
  * half of the rule.
  *
- * WHY IT MATTERS (F3 of the repair cycle, rid `2026-09-30-cap-unify-01`). The
  * census enumerated its scope with `git ls-files <dirs>` plus the extension test,
  * while the scan measured EVERY changed non-exempt file at `fileSizeCapFor`'s
  * else-branch 300 — including paths in neither list. The two disagreed about the
@@ -128,7 +124,6 @@ export function fileSizeScopeBucket(file) {
 }
 // ---------------------------------------------------------------------------
 // THE SECOND SCOPE — `.husky/`, the directory the ratchet itself lives in
-// (backlog §2.32, rid 2026-10-02-hooks-size-rows)
 // ---------------------------------------------------------------------------
 //
 // WHAT WAS INVISIBLE. `FILE_SIZE_SCOPE_DIRS` names four directories, and `.husky`

package/dist/services/scan/file-size-scan.d.ts

@@ -49,7 +49,6 @@ export type FileSizeScanResult = {
      *  four scope directories, or with an extension it does not count. Reported
      *  rather than silently skipped, for the same reason `exemptFiles` is.
      *
-     *  WHY THEY ARE NOT VIOLATIONS (F3, rid 2026-09-30-cap-unify-01). Every file
      *  the scan checked used to be measured against `fileSizeCapFor`, whose
      *  else-branch is 300 — a number that is only defined for `src`/`packages`/
      *  `scripts`. So an out-of-scope path (a `.md`, a file under `.husky/`) could

package/dist/services/security/safe-settings-path.js

@@ -1,7 +1,6 @@
 /**
  * R-2 path-safety guard for sub-agent state files.
  *
- * Slice 2026-06-07-sub-agent-dispatch-decouple (G4) — reuses the same
  * R-2 symlink/junction guard as `assertSafeSettingsFile` for
  * `.peaks/_sub_agents/<sid>/dispatch-<rid>-<ts>.json` paths.
  *

package/dist/services/session/binding-store.d.ts

@@ -6,7 +6,6 @@
  *
  * v2.16.0 schema is a multi-instance registry with conflict-detection
  * sentinel fields (ownerHint, pid, lastHeartbeat, instances Map).
- * See PRD `001-2026-06-29-v2-16-0-change-id-axis-removal` AC-8.
  *
  * The store keeps a one-shot migration from the legacy schema:
  * legacy single-session binding → v2.16.0 instances Map with one entry,
@@ -80,13 +79,11 @@ export declare function registerInstance(projectRoot: string, opts: {
 };
 /**
  * Touch the `lastHeartbeat` for a specific instance. Used by the
- * Doctor periodic loop (AC-10) and by the Skill presence `startup`
  * gate.
  */
 export declare function heartbeat(projectRoot: string, sid: string): Binding | null;
 /**
  * Drop an instance entry from the binding. Used when the last peaks-*
- * skill on a Claude instance exits (AC-7: all skills inactive →
  * no record). Returns the updated binding (or null if no instances
  * remain and the caller wants to delete the binding entirely).
  */
@@ -94,7 +91,6 @@ export declare function dropInstance(projectRoot: string, sid: string): Binding
 /**
  * Drop stale instances (lastHeartbeat older than `ttlMs`). Returns
  * the list of dropped sid values so the caller can log them. Used
- * by AC-10 Doctor.
  */
 export declare function dropStale(projectRoot: string, ttlMs: number): {
     binding: Binding | null;

package/dist/services/session/binding-store.js

@@ -6,7 +6,6 @@
  *
  * v2.16.0 schema is a multi-instance registry with conflict-detection
  * sentinel fields (ownerHint, pid, lastHeartbeat, instances Map).
- * See PRD `001-2026-06-29-v2-16-0-change-id-axis-removal` AC-8.
  *
  * The store keeps a one-shot migration from the legacy schema:
  * legacy single-session binding → v2.16.0 instances Map with one entry,
@@ -60,7 +59,6 @@ function getCurrentOuterSessionId() {
  * both env vars unset returns the literal `'unknown'` sentinel
  * for every process. Suffixing with `process.pid` makes the
  * callerId process-unique without changing the surface (no new
- * env var, no new schema field), preserving the AC-5 hard rule
  * that "one Claude instance keeps one sid across multiple
  * peaks-* skill activations" — a single process keeps a constant
  * pid across the whole run, including `/compact`.
@@ -144,7 +142,6 @@ export function readBinding(projectRoot) {
         typeof legacyShape.createdAt === 'string' &&
         typeof legacyShape.projectRoot === 'string') {
         // Auto-migrate marks lastHeartbeat as `now` (not `createdAt`) so the
-        // migrated instance does NOT immediately appear stale to AC-10.
         // Legacy bindings date from the pre-v2.16.0 single-session era;
         // their createdAt predates the binding sentinel concept entirely.
         const migratedAt = nowIso();
@@ -226,7 +223,6 @@ export function registerInstance(projectRoot, opts) {
         }
         // Auto-resume: caller already has an instance in this scope —
         // append roles and refresh heartbeat instead of creating a new
-        // sid. This is the AC-5 Claude-instance-level hard rule: a
         // single Claude caller keeps one sid across multiple peaks-*
         // skill activations.
         const existingSidForCaller = Object.entries(existing.instances).find(([, inst]) => inst.callerId === callerId)?.[0];
@@ -283,7 +279,6 @@ export function registerInstance(projectRoot, opts) {
 }
 /**
  * Touch the `lastHeartbeat` for a specific instance. Used by the
- * Doctor periodic loop (AC-10) and by the Skill presence `startup`
  * gate.
  */
 export function heartbeat(projectRoot, sid) {
@@ -307,7 +302,6 @@ export function heartbeat(projectRoot, sid) {
 }
 /**
  * Drop an instance entry from the binding. Used when the last peaks-*
- * skill on a Claude instance exits (AC-7: all skills inactive →
  * no record). Returns the updated binding (or null if no instances
  * remain and the caller wants to delete the binding entirely).
  */
@@ -328,7 +322,6 @@ export function dropInstance(projectRoot, sid) {
 /**
  * Drop stale instances (lastHeartbeat older than `ttlMs`). Returns
  * the list of dropped sid values so the caller can log them. Used
- * by AC-10 Doctor.
  */
 export function dropStale(projectRoot, ttlMs) {
     const existing = readBinding(projectRoot);

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

@@ -1,5 +1,4 @@
 /**
- * Caller-Binding Service (slice 020 — caller-keyed session binding).
  *
  * Each caller has its own on-disk binding file at
  * `.peaks/_runtime/callers/<callerId>.json`. This service is the
@@ -33,7 +32,6 @@ export declare function getActiveSkillFileForCaller(projectRoot: string, peakSes
  * Resolve a stable, deterministic callerId for a legacy single-file
  * binding (M2). The hash input priority is:
  *
- *   1. `outerSessionId` (slice 018 stamped this on the per-peak
  *      session.json for sessions created after the slice shipped).
  *   2. `claudeSessionId` (legacy field name on pre-018 presence
  *      files; honour the read side so v1.2.x data does not lose its
@@ -59,11 +57,9 @@ export declare function getCallerBinding(projectRoot: string, callerId: string):
  *
  * `getCallerBinding` answers a SHAPE question: "is there a well-formed
  * binding file for this caller?". Session resolution needs a second
- * answer: "is that binding still USABLE?". Slice 2026-09-12
  * (rid=caller-binding-staleness) found it is not when the bound session's
  * directory is gone — the binding was still trusted, so a command
  * resolved the dead session id and `mkdir`'d a fresh tree under
- * `.peaks/_runtime/<gone-sid>/...` for a session that no longer exists.
  *
  * Returns a tagged result rather than `null` so the fall-through is
  * observable to the caller instead of silent:
@@ -88,7 +84,6 @@ export declare function resolveCallerBinding(projectRoot: string, callerId: stri
  * must be a valid session id, projectRoot is canonicalized). Idempotent:
  * re-writing the same callerId overwrites the file.
  *
- * Slice 2026-08-06-session-cacde8-A.5b: writes via `atomicWriteJson`
  * (temp-file-then-rename) so a power-loss mid-write cannot leave the
  * caller-binding file in a half-truncated state. `atomicWriteJson`
  * owns its own `mkdirSync(dir, { recursive: true })`, so the inline
@@ -99,7 +94,6 @@ export declare function setCallerBinding(projectRoot: string, callerId: string,
 /**
  * Repoint an EXISTING per-caller binding at a new peak session id.
  *
- * Slice 2026-09-10 (rid=rebind-must-update-caller-binding): an explicit
  * `peaks workspace init --session-id <X> --allow-session-rebind` rewrites
  * the project-global `.peaks/_runtime/session.json`. Without this call the
  * per-caller file keeps shadowing it for `getSessionIdCanonical`, so the

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

@@ -1,5 +1,4 @@
 /**
- * Caller-Binding Service (slice 020 — caller-keyed session binding).
  *
  * Each caller has its own on-disk binding file at
  * `.peaks/_runtime/callers/<callerId>.json`. This service is the
@@ -50,7 +49,6 @@ export function getActiveSkillFileForCaller(projectRoot, peakSessionId, callerId
  * Resolve a stable, deterministic callerId for a legacy single-file
  * binding (M2). The hash input priority is:
  *
- *   1. `outerSessionId` (slice 018 stamped this on the per-peak
  *      session.json for sessions created after the slice shipped).
  *   2. `claudeSessionId` (legacy field name on pre-018 presence
  *      files; honour the read side so v1.2.x data does not lose its
@@ -112,7 +110,6 @@ export function resolveCallerBinding(projectRoot, callerId) {
  * must be a valid session id, projectRoot is canonicalized). Idempotent:
  * re-writing the same callerId overwrites the file.
  *
- * Slice 2026-08-06-session-cacde8-A.5b: writes via `atomicWriteJson`
  * (temp-file-then-rename) so a power-loss mid-write cannot leave the
  * caller-binding file in a half-truncated state. `atomicWriteJson`
  * owns its own `mkdirSync(dir, { recursive: true })`, so the inline
@@ -133,7 +130,6 @@ export function setCallerBinding(projectRoot, callerId, binding) {
 /**
  * Repoint an EXISTING per-caller binding at a new peak session id.
  *
- * Slice 2026-09-10 (rid=rebind-must-update-caller-binding): an explicit
  * `peaks workspace init --session-id <X> --allow-session-rebind` rewrites
  * the project-global `.peaks/_runtime/session.json`. Without this call the
  * per-caller file keeps shadowing it for `getSessionIdCanonical`, so the

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

@@ -1,5 +1,4 @@
 /**
- * Caller-Id Resolution types (slice 020 — caller-keyed session binding,
  * refactored in slice 4.0.8 to be adapter-owned per RD §5).
  *
  * Per RD §5 + C1 user-confirmed product decision (binding 2026-08-03):
@@ -14,7 +13,6 @@
  * 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';
@@ -59,7 +57,6 @@ export interface CallerProjection {
  * On-disk shape of `.peaks/_runtime/callers/<callerId>.json`. One file
  * per caller; two callers may point to the same `peakSessionId` (D6).
  *
- * Slice 2026-09-12 (rid=caller-binding-staleness): the former
  * `lastActivityAt` field is REMOVED. It promised "bumped on every
  * `peaks <cmd>` that touches the binding" but was written only at first
  * bind and at an explicit rebind — never on reuse — so no freshness

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

@@ -1,5 +1,4 @@
 /**
- * Caller-Id Resolution types (slice 020 — caller-keyed session binding,
  * refactored in slice 4.0.8 to be adapter-owned per RD §5).
  *
  * Per RD §5 + C1 user-confirmed product decision (binding 2026-08-03):
@@ -14,7 +13,6 @@
  * 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.
  */
 /**

package/dist/services/session/getSessionDir.js

@@ -1,7 +1,6 @@
 /**
  * Canonical session-directory resolver.
  *
- * As of slice 2026-06-05-peaks-runtime-layer the per-session workspace
  * lives at `<root>/.peaks/_runtime/<sessionId>/`, NOT at the legacy
  * `<root>/.peaks/<sessionId>/` location. All **write** paths MUST route
  * through this helper. The legacy top-level path survives only as a

package/dist/services/session/index.js

@@ -1,6 +1,5 @@
 export { ensureSession, getSessionId, resolveCallerBoundSession, 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 { getCallerBindingFile, getActiveSkillFileForCaller, synthesiseLegacyCallerId, getCallerBinding, resolveCallerBinding, setCallerBinding, listCallerBindings } from './caller-binding-service.js';
 // Slice 4.0.8 (C1): PLATFORM_FALLBACKS is deleted. Re-export kept as

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

@@ -11,8 +11,6 @@
  * 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).
  *
@@ -21,7 +19,6 @@
  * (`getAdapter(ide).resolveCallerId(env)`), with `PEAKS_CALLER_ID` /
  * `--caller-id <id>` as the vendor-neutral short-circuits.
  *
- * 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 {

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

@@ -11,8 +11,6 @@
  * 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).
  *
@@ -21,7 +19,6 @@
  * (`getAdapter(ide).resolveCallerId(env)`), with `PEAKS_CALLER_ID` /
  * `--caller-id <id>` as the vendor-neutral short-circuits.
  *
- * 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.
  */
 /**

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

@@ -1,5 +1,4 @@
 /**
- * Caller-Id Resolution (slice 020 — caller-keyed session binding,
  * refactored in slice 4.0.8 to be adapter-owned per RD §5 + C1).
  *
  * As of 4.0.8 the per-platform `PLATFORM_FALLBACKS` table is DELETED.
@@ -30,7 +29,6 @@
  * mutate state. The caller (a CLI command, a service, a test) decides
  * what to do with the resolved id.
  *
- * 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, type CallerProjection, type CallerProjectionSource } from './caller-id-types.js';

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

@@ -1,5 +1,4 @@
 /**
- * Caller-Id Resolution (slice 020 — caller-keyed session binding,
  * refactored in slice 4.0.8 to be adapter-owned per RD §5 + C1).
  *
  * As of 4.0.8 the per-platform `PLATFORM_FALLBACKS` table is DELETED.
@@ -30,7 +29,6 @@
  * mutate state. The caller (a CLI command, a service, a test) decides
  * what to do with the resolved id.
  *
- * 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 { CALLER_ID_REGEX, CallerIdError } from './caller-id-types.js';

package/dist/services/session/session-binding-bridge.d.ts

@@ -48,7 +48,6 @@ export declare function ensureSession(projectRoot: string): Promise<string>;
 /**
  * Outer-session-aware wrapper around `ensureSession`.
  *
- * Slice 018 (auto-roll on outer-mismatch). When the current outer
  * session id (sourced from `PEAKS_OUTER_SESSION_ID` with
  * `CLAUDE_CODE_SESSION_ID` as the Claude-Code fallback) differs from
  * the outer session id recorded on the *bound* peaks session's
@@ -69,7 +68,6 @@ export declare function ensureSession(projectRoot: string): Promise<string>;
  *   3. The bound session's recorded outer session id matches the
  *      current one (reconnect within the same Claude session) — this
  *      is the common case, not a swap.
- *   4. Slice 2026-08-06-session-cacde8-A.3: same-process re-resolve —
  *      `lastResolvedOuter.value` was already set to `currentOuterSessionId`
  *      in this process and `boundOuter` equals that same value. Long-
  *      running presence-lease writers that re-resolve within a single