peaks-loop 4.1.0 → 4.1.2

package/dist/services/workspace/migrate-service.js

@@ -36,8 +36,6 @@ function dirToRole(subdir) {
  * 4-digit year prefixes (e.g. `2026-...`) are part of the change-id,
  * NOT a sequence number, so they don't trigger tier 1.
  *
- * `001-2026-05-29-custom-sop-gate-metering.md`  →  `2026-05-29-custom-sop-gate-metering`
- * `2026-05-29-default-session.md`               →  null  (4-digit prefix; fall through to H1 / frontmatter)
  * `tech-doc.md`                                →  null  (no number prefix; fall through)
  */
 const FILENAME_CHANGE_ID_RE = /^\d{1,3}-([A-Za-z0-9][A-Za-z0-9._-]*)\.md$/;
@@ -69,7 +67,6 @@ const H1_CHANGE_ID_PATTERNS = [
         extract: (h) => /^#\s*Bug\s+Analysis[\s:—–-]+(.+)$/i.exec(h)?.[1]?.trim() ?? null
     },
     // "# Performance Baseline" / "# Perf Baseline" / "# Perf Baseline: <slice>"
-    //   → cross-cutting, NOT a per-slice change-id (return null)
     { test: (h) => /^#\s*(?:Performance|Perf)\s+Baseline(?:\s*:.*)?$/i.test(h), extract: () => null },
     // "# Project Scan: <name>" → cross-cutting, returns the name but caller treats as cross-cutting
     { test: (h) => /^#\s*Project\s+Scan(?:\s*:.*)?$/i.test(h), extract: () => null },
@@ -150,7 +147,6 @@ async function collectFilesRecursive(basePath, role, relativeBase, out) {
 }
 /** Try the 4 tiers in order and return the first non-null result. */
 function extractChangeId(fileName, content, fallbackChangeId) {
-    // Slice 2026-06-29-change-id-root-removal: `validateChangeIdOrThrow`
     // was removed with the change-id axis. The structural regex check
     // it ran against the matched identifier is no longer enforced at
     // this site — callers accept any identifier shape that the tier-1
@@ -219,7 +215,6 @@ function isCrossCuttingFile(relativePath) {
     // variant with a space — observed in some downstream trees) are
     // cross-cutting artifacts. They belong at the TOP of `.peaks/`
     // (e.g. `.peaks/project-scan/rd/project-scan.md`), not under
-    // retrospective/. They never carry a per-slice change-id.
     if (relativePath === 'rd/project-scan.md')
         return true;
     if (relativePath === 'rd/perf-baseline.md')
@@ -350,7 +345,6 @@ async function planSession(sessionId, sessionPath, peaksRoot) {
     };
 }
 /**
- * Slice 003 (2026-06-06-session-layout-canonicalize): one-shot
  * consolidation of every top-level `.peaks/_runtime/<sid>/` into
  * `.peaks/_runtime/<sid>/`. Idempotent:
  *
@@ -506,7 +500,6 @@ export async function migrateWorkspace(options) {
         sessionPlans.push(plan);
         discoveredSessions.add(entry.name);
     }
-    // Slice 003 (canonical): also discover sessions under `.peaks/_runtime/<sid>/`.
     // The pre-canonical legacy walker above already handles legacy layouts;
     // this branch handles the post-canonical layout where every session
     // lives under `_runtime/`. We dedupe by session id so a session that
@@ -628,7 +621,6 @@ export async function migrateWorkspace(options) {
             deletedSessions.push(session.sessionId);
         }
     }
-    // Slice 003: the `--to-runtime` step. When set, move every
     // top-level `.peaks/_runtime/<sid>/` to `.peaks/_runtime/<sid>/`. Idempotent.
     // The F15 carve-out (rd/project-scan.md) is honored: when the
     // top-level `<sid>/rd/project-scan.md` differs from the runtime

package/dist/services/workspace/migrate-types.d.ts

@@ -3,7 +3,6 @@
  *
  * The migrate command is the downstream-project counterpart to the
  * one-time Phase 5 migration script that ran on the peaks-loop self-host
- * for slice 2026-06-05-change-id-as-unit-of-work. Where
  * `peaks workspace reconcile` only handles the top-level runtime state
  * files (`.peaks/.session.json`, `.peaks/.active-skill.json`,
  * `.peaks/sop-state/` → `.peaks/_runtime/`), `peaks workspace migrate`
@@ -58,7 +57,6 @@ export type MigrateOptions = {
     /** When true, actually `git mv` the files + `rm -rf` the emptied session dirs. */
     apply: boolean;
     /**
-     * Slice 003 (2026-06-06-session-layout-canonicalize): when true, the
      * command performs the **session-dir consolidation** — moves every
      * top-level `.peaks/_runtime/<sid>/` to `.peaks/_runtime/<sid>/`. Idempotent;
      * conflicts (target exists with different content) are logged but
@@ -66,7 +64,6 @@ export type MigrateOptions = {
      * lists what WOULD move + the conflicts.
      *
      * Mutually exclusive with the reviewable-content migration: the
-     * `--to-runtime` step is the data side of slice 003, while the
      * default `migrate` step is the cross-cutting content side
      * (reviewable files → retrospective). Both run when both flags are
      * set; the order is `--to-runtime` first (so the cross-cutting
@@ -111,7 +108,6 @@ export type MigrateResult = {
     /** Total files moved or scheduled to move. */
     totalFilesMoved: number;
     /**
-     * Slice 003: per-session-dir move plans for the `--to-runtime` step.
      * Empty when `toRuntime` was not set. Conflicts include both the
      * top-level/<sid>/ → _runtime/<sid>/ collisions AND the F15 carve-out
      * for `rd/project-scan.md`.

package/dist/services/workspace/migrate-types.js

@@ -3,7 +3,6 @@
  *
  * The migrate command is the downstream-project counterpart to the
  * one-time Phase 5 migration script that ran on the peaks-loop self-host
- * for slice 2026-06-05-change-id-as-unit-of-work. Where
  * `peaks workspace reconcile` only handles the top-level runtime state
  * files (`.peaks/.session.json`, `.peaks/.active-skill.json`,
  * `.peaks/sop-state/` → `.peaks/_runtime/`), `peaks workspace migrate`

package/dist/services/workspace/reconcile-migrate.d.ts

@@ -1,10 +1,8 @@
 /**
  * Migration helpers extracted from `reconcile-service.ts`
- * (slice 2026-09-06-split-batch-b) so the service stays under the
  * 800-line cap. Behaviour-preserving verbatim move.
  */
 /**
- * One-time migration step (added in slice 2026-06-05-peaks-runtime-layer).
  *
  * Move the legacy runtime files at:
  *   - `.peaks/.session.json`
@@ -40,7 +38,6 @@ export declare function migrateOldRuntimeState(projectRoot: string): {
     }>;
 };
 /**
- * One-time sub-agent state migration (slice 2026-06-06-sub-agent-spawn-bug-and-decouple).
  *
  * Move the legacy per-session sub-agent state files at:
  *   - `.peaks/_runtime/<sid>/system/subagent-progress.json`

package/dist/services/workspace/reconcile-migrate.js

@@ -1,6 +1,5 @@
 /**
  * Migration helpers extracted from `reconcile-service.ts`
- * (slice 2026-09-06-split-batch-b) so the service stays under the
  * 800-line cap. Behaviour-preserving verbatim move.
  */
 import { copyFileSync, existsSync, lstatSync, mkdirSync, readdirSync, renameSync, rmSync, rmdirSync, unlinkSync } from 'node:fs';
@@ -10,7 +9,6 @@ import { dirname, join, resolve } from 'node:path';
 // only at call time (after both modules have fully evaluated), so the
 // value-level circular import is safe under ESM live bindings.
 import { discoverSessions } from './reconcile-service.js';
-// Sub-agent state file basenames (slice 2026-06-06-sub-agent-spawn-bug-and-decouple).
 // The legacy location was `.peaks/_runtime/<sid>/system/<filename>`; the canonical new
 // location is `.peaks/_sub_agents/<sid>/<filename>`. `migrateSubAgentState`
 // moves the two files between these homes on every `reconcileWorkspace` run.
@@ -19,7 +17,6 @@ const SUB_AGENT_MIGRATION_FILES = [
     'progress-spawn.json'
 ];
 const SUB_AGENTS_DIR = '_sub_agents';
-// As of slice 2026-06-05-peaks-runtime-layer these old paths are the
 // back-compat read-only fallbacks; the canonical new home is
 // `.peaks/_runtime/`. `migrateOldRuntimeState` moves them to the new
 // location on disk. The leading dot is dropped when computing the
@@ -43,7 +40,6 @@ function runtimeNewBasename(oldBasename) {
     return oldBasename;
 }
 /**
- * One-time migration step (added in slice 2026-06-05-peaks-runtime-layer).
  *
  * Move the legacy runtime files at:
  *   - `.peaks/.session.json`
@@ -146,7 +142,6 @@ function copyDirRecursiveSync(src, dest) {
     }
 }
 /**
- * One-time sub-agent state migration (slice 2026-06-06-sub-agent-spawn-bug-and-decouple).
  *
  * Move the legacy per-session sub-agent state files at:
  *   - `.peaks/_runtime/<sid>/system/subagent-progress.json`

package/dist/services/workspace/reconcile-service.d.ts

@@ -8,7 +8,6 @@
  * and (optionally, with apply === true) deletes empty / abandoned
  * session dirs older than olderThanMs.
  *
- * As of slice 2026-06-05-peaks-runtime-layer the top-level orchestrator
  * also runs `migrateOldRuntimeState` at the start so pre-migration
  * trees have their `.peaks/.session.json` / `.peaks/.active-skill.json`
  * / `.peaks/sop-state/` files moved into `.peaks/_runtime/`.
@@ -78,7 +77,6 @@ export declare function applyDeletions(candidates: SessionEntry[], apply: boolea
 /**
  * Sync the single `change/<canonicalSessionId>/` live marker under
  * `.peaks/_runtime/change/`. The marker is an EMPTY directory (no
- * symlinks, no manifest, no content). Slice 006 collapses the F3
  * per-change-id symlink layer to a single live marker so the
  * `change/` layer is a single sentinel — easy for the LLM to
  * navigate, easy for tests to assert on.
@@ -110,7 +108,6 @@ export declare function syncChangeMarker(projectRoot: string, canonicalSessionId
 };
 /**
  * Top-level orchestrator. Wires migration (added in slice
- * 2026-06-05-peaks-runtime-layer), discovery, canonical pick, re-point,
  * deletion-candidate selection, and deletion into a single result.
  */
 export declare function reconcileWorkspace(options: ReconcileOptions): ReconcileResult;

package/dist/services/workspace/reconcile-service.js

@@ -8,7 +8,6 @@
  * and (optionally, with apply === true) deletes empty / abandoned
  * session dirs older than olderThanMs.
  *
- * As of slice 2026-06-05-peaks-runtime-layer the top-level orchestrator
  * also runs `migrateOldRuntimeState` at the start so pre-migration
  * trees have their `.peaks/.session.json` / `.peaks/.active-skill.json`
  * / `.peaks/sop-state/` files moved into `.peaks/_runtime/`.
@@ -35,7 +34,6 @@ const META_FILE = 'session.json';
 export function discoverSessions(projectRoot) {
     const runtimeRoot = join(projectRoot, '.peaks', '_runtime');
     const peaksRoot = join(projectRoot, '.peaks');
-    // As of slice 003, the canonical home for session dirs is
     // `.peaks/_runtime/<sid>/`. The legacy top-level layout is
     // read for back-compat (one minor release) so pre-migration
     // trees keep working. Both are scanned; duplicates (same sid
@@ -265,7 +263,6 @@ export function applyDeletions(candidates, apply) {
 }
 /**
  * Read the orchestrator's active-skill marker and extract the
- * session id. As of slice 2026-06-05-peaks-runtime-layer the
  * canonical home is `.peaks/_runtime/active-skill.json`; the legacy
  * `.peaks/.active-skill.json` is consulted as a one-minor-release
  * back-compat fallback (the new path wins when both exist).
@@ -296,7 +293,6 @@ function readActiveSkillSessionId(projectRoot) {
 /**
  * Sync the single `change/<canonicalSessionId>/` live marker under
  * `.peaks/_runtime/change/`. The marker is an EMPTY directory (no
- * symlinks, no manifest, no content). Slice 006 collapses the F3
  * per-change-id symlink layer to a single live marker so the
  * `change/` layer is a single sentinel — easy for the LLM to
  * navigate, easy for tests to assert on.
@@ -365,7 +361,6 @@ export function syncChangeMarker(projectRoot, canonicalSessionId) {
 }
 /**
  * Top-level orchestrator. Wires migration (added in slice
- * 2026-06-05-peaks-runtime-layer), discovery, canonical pick, re-point,
  * deletion-candidate selection, and deletion into a single result.
  */
 export function reconcileWorkspace(options) {
@@ -414,7 +409,6 @@ export function reconcileWorkspace(options) {
     }
     const deletionCandidates = findDeletionCandidates(sessions, ageThresholdMs);
     const deletionResult = applyDeletions(deletionCandidates, apply);
-    // Slice 006: sync the single `change/<canonicalSessionId>/` live
     // marker (replaces the F3 per-change-id symlink layer). The marker
     // is an empty dir; the function removes every other entry under
     // `.peaks/_runtime/change/`. Idempotent. This step is independent
@@ -427,7 +421,6 @@ export function reconcileWorkspace(options) {
             error: 'no canonical session'
         }
         : syncChangeMarker(projectRoot, canonical.sessionId);
-    // Slice 006: clean up the F3-introduced `.peaks/_runtime/<sid>/system/`
     // subdir under EVERY session dir (not just the canonical one). The
     // subdir was created eagerly by `initWorkspace` (F3) but was never
     // used. The cleanup is idempotent: re-running on a tree without the

package/dist/services/workspace/reconcile-types.d.ts

@@ -61,7 +61,6 @@ export type ReconcileResult = {
      * ".peaks/.active-skill.json", ".peaks/sop-state"). Empty when the
      * tree is already on the new layout (idempotent re-runs return []).
      *
-     * Added in slice 2026-06-05-peaks-runtime-layer; additive — older
      * consumers can ignore this field.
      */
     migratedFiles: string[];
@@ -70,7 +69,6 @@ export type ReconcileResult = {
      * `.peaks/_runtime/<sid>/system/{subagent-progress,progress-spawn}.json` into
      * `.peaks/_sub_agents/<sid>/` during this reconcile run.
      *
-     * Added in slice 2026-06-06-sub-agent-spawn-bug-and-decouple. The
      * detailed list of moved files is not surfaced here (the count is
      * what the CLI summary and QA test assert on); the underlying
      * `migrateSubAgentState` helper returns the full path list for
@@ -91,7 +89,6 @@ export type ReconcileResult = {
         message: string;
     }>;
     /**
-     * Slice 006 (2026-06-06-change-folder-simplify-and-lazy-role-subdirs):
      * result of syncing the single `change/<canonicalSessionId>/` live
      * marker under `.peaks/_runtime/change/`. The marker is an empty
      * directory; every other entry under `change/` is removed. The
@@ -108,9 +105,7 @@ export type ReconcileResult = {
         error: string | null;
     };
     /**
-     * Slice 006: list of absolute paths to `.peaks/_runtime/<sid>/system/`
      * subdirs that were removed by this reconcile run. The F3
-     * `initWorkspace` eagerly created the `system/` subdir; slice 006
      * deletes it during reconcile. Empty when the canonical session
      * had no `system/` subdir. Additive.
      */

package/dist/services/workspace/sid-naming-guard.d.ts

@@ -5,7 +5,6 @@
  *
  * Spec §8.7 — bare forms (sid-3 / sid-h / sid-r / unknown-sid) are
  * blocked at write time, NOT tolerated. After slice
- * 2026-06-27-archive-feature-removal the quarantine dir was removed;
  * bare sids are now rejected by callers using `assertValidSessionId`
  * instead.
  */

package/dist/services/workspace/sid-naming-guard.js

@@ -5,7 +5,6 @@
  *
  * Spec §8.7 — bare forms (sid-3 / sid-h / sid-r / unknown-sid) are
  * blocked at write time, NOT tolerated. After slice
- * 2026-06-27-archive-feature-removal the quarantine dir was removed;
  * bare sids are now rejected by callers using `assertValidSessionId`
  * instead.
  */

package/dist/services/workspace/templates/project-scan/index.d.ts

@@ -1,7 +1,6 @@
 /**
  * Bundled project-scan templates for `peaks workspace init`.
  *
- * Slice 2026-07-15-project-scan-bootstrap (PRD G4b / AC9 / R4):
  *   4 audit/business templates are bundled in the repo at
  *   `src/services/workspace/templates/project-scan/*.md` and copied
  *   verbatim to `<projectRoot>/.peaks/project-scan/` on every
@@ -9,10 +8,8 @@
  *   already exists; `--force-project-scan-templates` overrides).
  *
  *   `project-scan.md` is NOT bundled here — it is generated dynamically
- *   by `bootstrapProjectScan` (slice 2026-07-15-project-scan-bootstrap).
  *
  * Template-integrity guarantee:
- *   The vitest test `tests/unit/workspace/templates/template-integrity.test.ts`
  *   asserts byte-for-byte equality between these 4 files and the
  *   canonical sources at `.peaks/project-scan/{4 files}`. Any drift
  *   fails the suite (R4 engineering guard against template drift).

package/dist/services/workspace/templates/project-scan/index.js

@@ -1,7 +1,6 @@
 /**
  * Bundled project-scan templates for `peaks workspace init`.
  *
- * Slice 2026-07-15-project-scan-bootstrap (PRD G4b / AC9 / R4):
  *   4 audit/business templates are bundled in the repo at
  *   `src/services/workspace/templates/project-scan/*.md` and copied
  *   verbatim to `<projectRoot>/.peaks/project-scan/` on every
@@ -9,10 +8,8 @@
  *   already exists; `--force-project-scan-templates` overrides).
  *
  *   `project-scan.md` is NOT bundled here — it is generated dynamically
- *   by `bootstrapProjectScan` (slice 2026-07-15-project-scan-bootstrap).
  *
  * Template-integrity guarantee:
- *   The vitest test `tests/unit/workspace/templates/template-integrity.test.ts`
  *   asserts byte-for-byte equality between these 4 files and the
  *   canonical sources at `.peaks/project-scan/{4 files}`. Any drift
  *   fails the suite (R4 engineering guard against template drift).

package/dist/services/workspace/workspace-claude-settings-materializer.d.ts

@@ -36,7 +36,6 @@ export declare const PEAKS_GITIGNORE_FOOTER = "# <<< peaks-loop managed snippet"
  * documented in
  * `skills/peaks-code/references/anchoring-and-session-info.md`.
  *
- * Slice 2026-06-13-selfheal-claude-settings-template: the offline copy
  * is now ALSO drift-checked (via `templateContentMatches`) so stale
  * on-disk copies from earlier peaks-loop releases (which lacked the
  * `node -e "..."` wrapper) get refreshed automatically on the next

package/dist/services/workspace/workspace-claude-settings-materializer.js

@@ -77,7 +77,6 @@ function readEnvObject(serialized) {
  * `installAutoCompactHook` (`src/services/hooks/auto-compact-hook-install.ts`),
  * reached from `peaks code auto-compact` on an adapter declaring
  * `compactPathway: 'ide-native'` — which `claude-code` does. Measured on a
- * throwaway project root (rid 2026-09-13-two-decisions item ②):
  *
  *   init (written, 3 PreToolUse entries: Write|Edit|MultiEdit, Bash, Bash)
  *   → installAutoCompactHook (installed, 4: … | Bash|Task)
@@ -201,7 +200,6 @@ const PEAKS_GITIGNORE_SNIPPET = [
  * documented in
  * `skills/peaks-code/references/anchoring-and-session-info.md`.
  *
- * Slice 2026-06-13-selfheal-claude-settings-template: the offline copy
  * is now ALSO drift-checked (via `templateContentMatches`) so stale
  * on-disk copies from earlier peaks-loop releases (which lacked the
  * `node -e "..."` wrapper) get refreshed automatically on the next
@@ -283,7 +281,6 @@ export async function materializeClaudeSettingsLocal(projectRoot, noClaudeHooks)
  * (the file is regenerated); or copy the template straight from
  * peaks-loop source (`src/services/workspace/claude-settings-template.ts`).
  *
- * Slice 2026-06-13-selfheal-claude-settings-template: drift-check via
  * `templateContentMatches` BEFORE writing. If the on-disk copy's
  * parsed hooks tree matches the current `buildClaudeSettingsLocalJson()`
  * output, the write is skipped (`already-current`). If the file is
@@ -297,7 +294,6 @@ export async function materializeClaudeSettingsLocal(projectRoot, noClaudeHooks)
  * envelope. Read failures are treated as drift so a malformed
  * on-disk file always self-heals on the next init.
  *
- * WHAT IS COMPARED (rid 2026-09-13-two-decisions item ②): the copy is checked
  * against the TEMPLATE'S OWN entries — `buildClaudeSettingsLocalJson()` — not
  * against `serialized`, the merged LOCAL file content it is written from. This
  * file is a copy of the template (its name and this doc both say so), so

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

@@ -19,7 +19,6 @@ export type WorkspaceInitOptions = {
      */
     noClaudeHooks?: boolean;
     /**
-     * Slice 2026-06-16-peaks-code-auto-scaffold (RD#7): opt-in flag for
      * auto-applying `peaks standards init` when the consumer project's
      * `.claude/rules/` is missing or empty. Default (`false`) only emits
      * the diagnostic; set to `true` to also scaffold the rules tree via
@@ -54,13 +53,11 @@ export type WorkspaceInitReport = {
      * The LLM and the user both see this in the JSON envelope so they
      * can decide whether the bypass is in effect.
      *
-     * Slice 2026-06-13-selfheal-claude-settings-template: adds the
      * `offlineTemplate` sub-field, which describes the self-heal action
      * taken on the offline `.peaks/.claude-settings-template.json` copy.
      * The offline copy is ALWAYS written/checked (regardless of
      * noClaudeHooks) because it is the manual-recovery anchor — see
      * `skills/peaks-code/references/anchoring-and-session-info.md`.
-     *   - written:        the file did not exist; it was created
      *   - refreshed:      the file existed but its parsed hooks tree
      *                     diverged from the current `buildClaudeSettingsLocalJson()`;
      *                     it was rewritten
@@ -75,7 +72,6 @@ export type WorkspaceInitReport = {
         };
     };
     /**
-     * Slice 2026-06-16-peaks-code-auto-scaffold (RD#7): structured
      * diagnostic for missing or empty `.claude/rules/{common,<language>}/`.
      * Always present (the detector runs on every init); `missing: false`
      * means the project's rules tree is already populated and no action is
@@ -84,7 +80,6 @@ export type WorkspaceInitReport = {
      */
     standardsMissing: MissingProjectStandardsDiagnostic;
     /**
-     * Slice 2026-06-16-peaks-code-auto-scaffold (RD#7): when the caller
      * passed `initStandards: true` AND the detector reported `missing:
      * true`, this field lists the files written by
      * `executeProjectStandardsInit({ projectRoot, apply: true })`.
@@ -97,7 +92,6 @@ export type WorkspaceInitReport = {
     };
 };
 /**
- * Slice C10 (2026-06-24-legacy-change-id-sibling): the relative path
  * patterns under `.peaks/_runtime/<sessionId>/` that the lazy WRITER (peaks-qa,
  * peaks-rd, peaks-prd, peaks-txt, peaks-sc) creates via
  * `mkdir(parent, { recursive: true })` immediately before a write. When
@@ -147,7 +141,6 @@ export declare function validateSessionId(sessionId: string): void;
 export declare function initWorkspace(options: WorkspaceInitOptions): Promise<WorkspaceInitReport>;
 export { materializeClaudeSettingsLocal } from './workspace-claude-settings-materializer.js';
 /**
- * Slice C10 (2026-06-24-legacy-change-id-sibling): whole-dir shape check
  * for the legacy sibling `.peaks/_runtime/<sessionId>/`. Returns `true` ONLY when
  * every leaf path under the sibling matches one of
  * `WRITER_ALLOWED_RELATIVE_PATTERNS` AND no entry is a symlink (anywhere

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

@@ -8,7 +8,6 @@ import { resolveCallerProjection } from '../session/resolve-caller-id.js';
 import { normalizePath } from '../../shared/path-utils.js';
 import { assertWritableProjectRoot } from '../config/config-safety.js';
 /**
- * Slice 2026-09-10 (rid=rebind-must-update-caller-binding): repoint the
  * calling process's own per-caller binding at the session id this init just
  * bound. `getSessionIdCanonical` reads `callers/<callerId>.json` FIRST, so a
  * binding left behind by an earlier session shadows every explicit rebind.
@@ -31,7 +30,6 @@ function rebindCurrentCallerBinding(projectRoot, sessionId) {
     return updateCallerBindingSessionId(projectRoot, callerId, sessionId);
 }
 /**
- * Slice 2026-06-29-change-id-root-removal: list the immediate children of
  * `.peaks/` so the legacy sibling-dir guard can enumerate date-stamped
  * residue dirs without re-implementing `readdirSync` inline. Returns
  * `[]` when the `.peaks/` dir does not exist (legitimate first-run
@@ -49,7 +47,6 @@ function listPeaksRuntimeSiblings(projectRoot) {
     }
 }
 /**
- * Slice 2026-06-29-change-id-root-removal: list the immediate children of
  * `.peaks/_runtime/` so the legacy sibling-dir guard can enumerate
  * date-stamped residue dirs at the runtime layer. Returns `[]` when
  * the `.peaks/_runtime/` dir does not exist.
@@ -66,7 +63,6 @@ function listRuntimeSiblings(projectRoot) {
     }
 }
 /**
- * Slice 2026-06-29-change-id-root-removal: returns `true` when the
  * basename matches the auto-generated session-id shape
  * `YYYY-MM-DD-<slug>` (the v2.8.3 hard-ban target). Bare dates
  * (`YYYY-MM-DD`) are NOT auto-generated and are kept as plain dates.
@@ -78,7 +74,6 @@ function isDateStampedSiblingId(name) {
         return false;
     return true;
 }
-// Slice 2026-06-29-change-id-root-removal: `setCurrentChangeId` and
 // `validateChangeIdOrThrow` were removed with the change-id axis. Init
 // preserves the legacy-sibling-dir guard via inline `lstatSync`; the
 // path-safety helpers moved to `shared/path-safety.ts` but this module
@@ -97,7 +92,6 @@ const PROHIBITED_SUFFIXES = [
 // Auto-generated session ID pattern: YYYY-MM-DD-session-<6位hex>
 const AUTO_SESSION_PATTERN = /^\d{4}-\d{2}-\d{2}-session-[a-f0-9]{6}$/;
 /**
- * Slice C10 (2026-06-24-legacy-change-id-sibling): the relative path
  * patterns under `.peaks/_runtime/<sessionId>/` that the lazy WRITER (peaks-qa,
  * peaks-rd, peaks-prd, peaks-txt, peaks-sc) creates via
  * `mkdir(parent, { recursive: true })` immediately before a write. When
@@ -194,11 +188,8 @@ export async function initWorkspace(options) {
     // is `$HOME`) resolved to `$HOME` and did exactly that — `.peaks/`,
     // `.gitignore`, `.claude/settings.local.json` and a codegraph index, all in
     // the user's home. Enforced here as well as at the CLI so a non-CLI caller
-    // (`peaks upgrade`) cannot reach the same write by another door.
+    // cannot reach the same write by another door.
     assertWritableProjectRoot(options.projectRoot);
-    // Phase 6 refactor (slice 2026-06-05-change-id-as-unit-of-work) +
-    // slice 006 (2026-06-06-change-folder-simplify-and-lazy-role-subdirs) +
-    // slice 2026-06-22-top-level-change-id-cleanup (2.8.3):
     //   - Reviewable artifacts (rd/, qa/, prd/, txt/) live at
     //     `.peaks/_runtime/<change-id>/<role>/` (tracked in git) when a change-id
     //     is given. The role subdirs are NOT pre-created — the writer
@@ -206,7 +197,6 @@ export async function initWorkspace(options) {
     //     dirs on demand via `mkdirSync(..., { recursive: true })`.
     //   - The session dir `.peaks/_runtime/<session-id>/` (gitignored)
     //     now holds ONLY the canonical `session.json` metadata. The
-    //     F3-introduced `system/` subdir is gone — slice 006 removes
     //     it via `peaks workspace reconcile`; new init calls do not
     //     pre-create it.
     //   - The change-id dir is NOT created at top level when `--change-id`
@@ -227,7 +217,6 @@ export async function initWorkspace(options) {
     const alreadyExisted = [];
     // 1. Create the session dir (canonical location `.peaks/_runtime/<sid>/`)
     //    with NO subdirs. The session dir is gitignored; the role
-    //    subdirs and the `system/` subdir are gone entirely (slice 006).
     if (await isDirectory(sessionRoot)) {
         alreadyExisted.push('.');
     }
@@ -235,13 +224,11 @@ export async function initWorkspace(options) {
         await mkdir(sessionRoot, { recursive: true });
         created.push('.');
     }
-    // 1a. Write the per-session metadata file. Slice 006 makes
     //     `.peaks/_runtime/<sid>/session.json` the durable session
     //     metadata (the body's source of truth, the `peaks workspace
     //     reconcile` discovery source). The file is created on first
     //     init and refreshed on every subsequent init. Idempotent.
     setSessionMeta(options.projectRoot, options.sessionId, {});
-    // 2. Slice 2026-06-29-change-id-root-removal: the change-id axis is
     //    gone. The session id IS the binding — there is no separate
     //    `.peaks/_runtime/current-change` file. The v2.8.3 hard-ban on
     //    `.peaks/<YYYY-MM-DD-*>/` siblings still fires via the inline
@@ -339,7 +326,6 @@ export async function initWorkspace(options) {
         // Either: existing session dir is empty (true leftover, no user data),
         // or the caller explicitly authorised a rebind. Overwrite.
         setCurrentSessionBinding(options.projectRoot, options.sessionId);
-        // Slice 2026-09-10 (rid=rebind-must-update-caller-binding): an
         // explicit rebind must ALSO repoint this caller's per-caller binding.
         // `getSessionIdCanonical` prefers `callers/<callerId>.json`, so leaving
         // it untouched shadowed the rebind for every command resolving through
@@ -350,7 +336,6 @@ export async function initWorkspace(options) {
         rebindCurrentCallerBinding(options.projectRoot, options.sessionId);
         bound = true;
     }
-    // Slice 2026-06-16-peaks-code-auto-scaffold (RD#7):
     //   - Always run the detector and surface the descriptor so the CLI can
     //     put it on stderr + into the JSON envelope's `data.standardsMissing`.
     //   - When `initStandards: true` AND the detector reports missing, run
@@ -404,7 +389,6 @@ import { materializeClaudeSettingsLocal } from './workspace-claude-settings-mate
 export { materializeClaudeSettingsLocal } from './workspace-claude-settings-materializer.js';
 import { writeGeneratedArtifactsStamp } from './generated-artifacts-stamp.js';
 /**
- * Slice C10 (2026-06-24-legacy-change-id-sibling): whole-dir shape check
  * for the legacy sibling `.peaks/_runtime/<sessionId>/`. Returns `true` ONLY when
  * every leaf path under the sibling matches one of
  * `WRITER_ALLOWED_RELATIVE_PATTERNS` AND no entry is a symlink (anywhere

package/dist/services/worktree/playwright-profile.js

@@ -2,7 +2,6 @@
  * playwright-profile — deterministic Chromium user-data-dir +
  * profile-name pair generator for a (session, dispatch) tuple.
  *
- * Slice 2026-08-01-subagent-merge-and-e2e (Task 2). Each sub-agent
  * dispatch with `--isolation worktree` MUST land its Playwright MCP
  * browser session in a unique Chromium profile so concurrent
  * dispatches do not share cookies / localStorage / IndexedDB. The

package/dist/services/worktree/worktree-lease-types.d.ts

@@ -2,7 +2,6 @@
  * worktree-lease-types — the pure declaration surface of the worktree lease
  * store (`worktree-lease.ts`).
  *
- * Slice 2026-07-29-worktree-l2-extended Part 1 owns the lease behavior; this
  * module owns only the shapes (lifecycle status, lease record, creation draft,
  * and the list-read result). `worktree-lease.ts` imports and re-exports every
  * name here, so importers keep resolving them from the original path.

package/dist/services/worktree/worktree-lease-types.js

@@ -2,7 +2,6 @@
  * worktree-lease-types — the pure declaration surface of the worktree lease
  * store (`worktree-lease.ts`).
  *
- * Slice 2026-07-29-worktree-l2-extended Part 1 owns the lease behavior; this
  * module owns only the shapes (lifecycle status, lease record, creation draft,
  * and the list-read result). `worktree-lease.ts` imports and re-exports every
  * name here, so importers keep resolving them from the original path.

package/dist/services/worktree/worktree-lease.d.ts

@@ -1,7 +1,6 @@
 /**
  * worktree-lease — pure-function lease store for `peaks worktree spawn`.
  *
- * Slice 2026-07-29-worktree-l2-extended Part 1. This is the Layer 2
  * governance complement to Layer 3 (`permissions.deny` for the superpowers
  * chain) and Layer 1 (sub-agent dispatch prompt refusal). Together the
  * three layers close the superpowers-chain jailbreak that previously
@@ -11,7 +10,6 @@
  * directory path as an argument and returns structured data. Atomic
  * filesystem writes happen at the call site (CLI command), keeping the
  * helpers trivially testable. The CLI surface lives in
- * `src/cli/commands/worktree-spawn-commands.ts`.
  *
  * Why a separate lease (vs reusing `peaks worktree auth grant`):
  * - `auth grant` is a single-shot, short-lived token file consulted by

package/dist/services/worktree/worktree-lease.js

@@ -1,7 +1,6 @@
 /**
  * worktree-lease — pure-function lease store for `peaks worktree spawn`.
  *
- * Slice 2026-07-29-worktree-l2-extended Part 1. This is the Layer 2
  * governance complement to Layer 3 (`permissions.deny` for the superpowers
  * chain) and Layer 1 (sub-agent dispatch prompt refusal). Together the
  * three layers close the superpowers-chain jailbreak that previously
@@ -11,7 +10,6 @@
  * directory path as an argument and returns structured data. Atomic
  * filesystem writes happen at the call site (CLI command), keeping the
  * helpers trivially testable. The CLI surface lives in
- * `src/cli/commands/worktree-spawn-commands.ts`.
  *
  * Why a separate lease (vs reusing `peaks worktree auth grant`):
  * - `auth grant` is a single-shot, short-lived token file consulted by

package/dist/shared/format-md-compact.d.ts

@@ -2,7 +2,6 @@
  * format-md-compact — single source of truth for whitespace / decoration
  * normalization across every CLI body-output path.
  *
- * Slice 023 (R3) — `peaks project memories:show`, `peaks retrospective show`,
  * and `peaks request show` (per-artifact) all funnel their `body` field through
  * this helper so the LLM-consumed output is free of blank-line padding,
  * decorative `---` rules, and frontmatter `description:` field-name repeats
@@ -11,7 +10,6 @@
  * inline emphasis, code spans).
  *
  * Pure function: no fs, no I/O. Easy to unit-test (see
- * `tests/unit/shared/format-md-compact.test.ts`).
  */
 export interface FormatMdCompactOptions {
     /** Preserve code-fence (``` ... ```) and frontmatter (--- ... ---) content. Default true. */

package/dist/shared/format-md-compact.js

@@ -2,7 +2,6 @@
  * format-md-compact — single source of truth for whitespace / decoration
  * normalization across every CLI body-output path.
  *
- * Slice 023 (R3) — `peaks project memories:show`, `peaks retrospective show`,
  * and `peaks request show` (per-artifact) all funnel their `body` field through
  * this helper so the LLM-consumed output is free of blank-line padding,
  * decorative `---` rules, and frontmatter `description:` field-name repeats
@@ -11,7 +10,6 @@
  * inline emphasis, code spans).
  *
  * Pure function: no fs, no I/O. Easy to unit-test (see
- * `tests/unit/shared/format-md-compact.test.ts`).
  */
 import { ATX_HEADING_RE, collapseMultiBlanks, computeSetextUnderlines, isDecorativeHorizontalRule, isFenceCloseLine, isFenceOpenLine, isTableLine, splitFrontmatter } from './format-md-compact-internals.js';
 const FENCE_TRIPLE_BACKTICK = '```';

package/dist/shared/incrementing-number.d.ts

@@ -19,7 +19,6 @@ export declare function getNextNumber(dirPath: string): number;
  * Exported separately so lookup paths (e.g. `request-artifact-service.ts`)
  * can compute the SAME slug the writer produced and match on-disk filenames
  * case-insensitively — the writer lowercases, so a mixed-case request id
- * like `2026-09-06-split-batchA` lands as `...-split-batcha.md`.
  */
 export declare function slugifyDescription(description: string): string;
 export declare function buildNumberedFilename(number: number, description: string): string;

package/dist/shared/incrementing-number.js

@@ -52,7 +52,6 @@ const MAX_FILENAME_SLUG_LENGTH = MAX_FILENAME_LENGTH - 7;
  * Exported separately so lookup paths (e.g. `request-artifact-service.ts`)
  * can compute the SAME slug the writer produced and match on-disk filenames
  * case-insensitively — the writer lowercases, so a mixed-case request id
- * like `2026-09-06-split-batchA` lands as `...-split-batcha.md`.
  */
 export function slugifyDescription(description) {
     return description