peaks-loop 4.1.1 → 4.1.2

package/dist/services/loop/loop-bee-relation-store.js

@@ -8,13 +8,12 @@
  *
  * Defense in depth:
  *   - FK constraints enforce loop_release and bee_release referential
- *     integrity (better-sqlite3 + foreign_keys = ON).
+ *     integrity (foreign_keys = ON, applied by `openStateDb`).
  *   - Partial unique index `WHERE role = 'main'` enforces "at most one
  *     main bee per loop" at the storage layer (the service layer adds
  *     a friendlier error path on top).
  *   - UNIQUE (loop_release_id, bee_release_id) prevents accidental
  *     duplicate relations between the same loop and same bee release.
- *   - The migration does NOT touch any 4.x `bee_release` column (AC-3).
  *   - Lifecycle_status check on loop_release is NOT a DB-level constraint
  *     (the retirement rule is enforced in the service layer — see
  *     `LoopBeeRelationService.create`) so the DB stays decoupled from

package/dist/services/loop/loop-bee-relation-types.d.ts

@@ -41,7 +41,7 @@ export declare const LOOP_BEE_RELATION_ROLES: readonly LoopBeeRelationRole[];
  * `loop_release_id` must match the same kebab-case pattern as
  * `LoopRelease.id` — this is a defensive duplicate of the FK target's
  * shape, but the authoritative check is the FK constraint at insert
- * time (better-sqlite3 with `foreign_keys = ON`).
+ * time (with `foreign_keys = ON`, which `openStateDb` applies).
  *
  * `bee_release_id` is a positive integer; matching the
  * `bee_release.id` autoincrement INTEGER PK.

package/dist/services/loop/loop-bee-relation-types.js

@@ -40,7 +40,7 @@ export const LOOP_BEE_RELATION_ROLES = [
  * `loop_release_id` must match the same kebab-case pattern as
  * `LoopRelease.id` — this is a defensive duplicate of the FK target's
  * shape, but the authoritative check is the FK constraint at insert
- * time (better-sqlite3 with `foreign_keys = ON`).
+ * time (with `foreign_keys = ON`, which `openStateDb` applies).
  *
  * `bee_release_id` is a positive integer; matching the
  * `bee_release.id` autoincrement INTEGER PK.

package/dist/services/loop/loop-release-service.d.ts

@@ -1,4 +1,4 @@
-import type Database from 'better-sqlite3';
+import type { SqliteDatabase } from '../sqlite/sqlite-driver.js';
 import { type LoopRelease, type LoopReleaseInput, type LoopReleaseLifecycleStatus } from './loop-release-types.js';
 /**
  * Thin service wrapper around the loop_release store. M1 keeps the
@@ -7,7 +7,7 @@ import { type LoopRelease, type LoopReleaseInput, type LoopReleaseLifecycleStatu
  * deliberately deferred to M2 / M4 / M5 — shipping them here would
  * lock in an interface that the ratchet has not yet ratified.
  *
- * The constructor takes an open better-sqlite3 database (the existing
+ * The constructor takes an open SQLite database (the existing
  * `peaks state` boundary) so callers do not have to thread a path
  * through this layer; this matches the `retainRelease` pattern in
  * `src/services/skillhub/release-retain.ts`.
@@ -18,7 +18,7 @@ import { type LoopRelease, type LoopReleaseInput, type LoopReleaseLifecycleStatu
  */
 export declare class LoopReleaseService {
     private readonly db;
-    constructor(db: Database.Database);
+    constructor(db: SqliteDatabase);
     /**
      * Persist a new LoopRelease row. Re-validates the input via the
      * Zod schema; throws ZodError on failure.

package/dist/services/loop/loop-release-service.js

@@ -7,7 +7,7 @@ import { ensureLoopReleaseTable, insertLoopRelease, getLoopRelease, listLoopRele
  * deliberately deferred to M2 / M4 / M5 — shipping them here would
  * lock in an interface that the ratchet has not yet ratified.
  *
- * The constructor takes an open better-sqlite3 database (the existing
+ * The constructor takes an open SQLite database (the existing
  * `peaks state` boundary) so callers do not have to thread a path
  * through this layer; this matches the `retainRelease` pattern in
  * `src/services/skillhub/release-retain.ts`.

package/dist/services/loop/loop-release-store.d.ts

@@ -1,4 +1,4 @@
-import type Database from 'better-sqlite3';
+import type { SqliteDatabase } from '../sqlite/sqlite-driver.js';
 import type { LoopRelease, LoopReleaseLifecycleStatus } from './loop-release-types.js';
 /**
  * Low-level SQLite access for the `loop_release` table. The
@@ -17,7 +17,6 @@ import type { LoopRelease, LoopReleaseLifecycleStatus } from './loop-release-typ
  *     INDEX IF NOT EXISTS) so re-running it is safe.
  *   - The M3 migration (`004-loop-bee-extension.sql`) is non-breaking:
  *     it only adds new columns with DEFAULTs and does NOT touch any
- *     pre-existing column on `bee_release` (AC-3).
  */
 /**
  * Re-apply the loop_release table migration against an already-open
@@ -31,7 +30,7 @@ import type { LoopRelease, LoopReleaseLifecycleStatus } from './loop-release-typ
  * the columns will exist; for a freshly-built DB via this helper the
  * columns are baked in. Either way the schema converges.
  */
-export declare function ensureLoopReleaseTable(db: Database.Database): void;
+export declare function ensureLoopReleaseTable(db: SqliteDatabase): void;
 /**
  * Insert a LoopRelease row. The row's `schema_version` is taken from
  * the input (must equal `peaks.loop/1`); `archived_at` is stamped
@@ -41,15 +40,15 @@ export declare function ensureLoopReleaseTable(db: Database.Database): void;
  * same id throws a UNIQUE-constraint error; callers wanting upsert
  * semantics should use a separate path (M5 / crystallization event).
  */
-export declare function insertLoopRelease(db: Database.Database, row: LoopRelease): void;
+export declare function insertLoopRelease(db: SqliteDatabase, row: LoopRelease): void;
 /** Read a single LoopRelease row by id; returns undefined if absent. */
-export declare function getLoopRelease(db: Database.Database, id: string): LoopRelease | undefined;
+export declare function getLoopRelease(db: SqliteDatabase, id: string): LoopRelease | undefined;
 /** List LoopRelease rows filtered by lifecycle_status. */
-export declare function listLoopReleasesByStatus(db: Database.Database, status: LoopReleaseLifecycleStatus): LoopRelease[];
+export declare function listLoopReleasesByStatus(db: SqliteDatabase, status: LoopReleaseLifecycleStatus): LoopRelease[];
 /**
  * Search LoopRelease rows whose `scenario` contains the query string.
  * M1 uses a case-insensitive LIKE; FTS5 promotion is deferred. The
  * query is treated as a literal substring (no regex, no SQL
  * injection surface) — it is escaped via parameter binding.
  */
-export declare function searchLoopReleasesByScenario(db: Database.Database, query: string): LoopRelease[];
+export declare function searchLoopReleasesByScenario(db: SqliteDatabase, query: string): LoopRelease[];

package/dist/services/loop/loop-release-store.js

@@ -15,7 +15,6 @@
  *     INDEX IF NOT EXISTS) so re-running it is safe.
  *   - The M3 migration (`004-loop-bee-extension.sql`) is non-breaking:
  *     it only adds new columns with DEFAULTs and does NOT touch any
- *     pre-existing column on `bee_release` (AC-3).
  */
 /**
  * Re-apply the loop_release table migration against an already-open

package/dist/services/loop/monotonic-guard.d.ts

@@ -22,7 +22,6 @@ export declare function toScoreRow(evaluator: string, gateAction: 'pass' | 'warn
 export declare const DEFAULT_MONOTONIC_THRESHOLD = 0.05;
 /** Compare `previous` against `current` and report monotonicity.
  *
- *  Rules (reflected in `tests/unit/loop/monotonic-guard.test.ts`):
  *    - missing previous cycle → skip (`MONOTONIC_NO_PREVIOUS`)
  *    - evaluators not present in both cycles → skip that evaluator
  *    - score unchanged / up → ok

package/dist/services/loop/monotonic-guard.js

@@ -50,7 +50,6 @@ export function toScoreRow(evaluator, gateAction, degraded, observedAtIso = new
 export const DEFAULT_MONOTONIC_THRESHOLD = 0.05;
 /** Compare `previous` against `current` and report monotonicity.
  *
- *  Rules (reflected in `tests/unit/loop/monotonic-guard.test.ts`):
  *    - missing previous cycle → skip (`MONOTONIC_NO_PREVIOUS`)
  *    - evaluators not present in both cycles → skip that evaluator
  *    - score unchanged / up → ok

package/dist/services/memory/memory-ingest-service.js

@@ -2,7 +2,6 @@
 // `peaks memory ingest` — pull memories written by the IDE-side agent into
 // the peaks-owned store.
 //
-// Slice 2026-09-09-memory-system-overhaul (A). Before this, "沉淀记忆" in a
 // peaks-code workflow landed in Claude Code's own per-project memory dir
 // (`~/.claude/projects/<hash>/memory/`) and never reached `.peaks/memory/`
 // — a split-brain write path with no single authority.

package/dist/services/memory/project-context-service.d.ts

@@ -4,7 +4,6 @@ export type ProjectContextSection = {
     body: string;
 };
 /**
- * Slice 2026-07-15-project-scan-bootstrap (G1 + G2):
  * generateProjectContext now also bootstraps the project-level
  * `.peaks/project-scan/` artifact set. The envelope is returned
  * alongside the context so `peaks project context` can surface

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

@@ -151,7 +151,6 @@ export async function generateProjectContext(projectRoot) {
         content = header + '\n' + sessionHistory + '\n';
     }
     writeFileSync(contextPath, content, 'utf8');
-    // Slice 2026-07-15-project-scan-bootstrap (G1 + G2):
     // After writing PROJECT.md, also bootstrap `.peaks/project-scan/`
     // (project-scan.md + 4 bundled audit/business templates). Idempotent
     // — re-running this call does not overwrite existing files (unless

package/dist/services/memory/project-memory-service/index/reindex.d.ts

@@ -20,7 +20,6 @@ export interface ReindexUnclassified {
 export interface ReindexOrphanEntry {
     name: string;
     kind: string;
-    /** The `sourcePath` recorded in the previous index that no longer exists on disk. */
     sourcePath: string;
 }
 /**
@@ -49,7 +48,6 @@ export interface MemoryReindexReport {
     unclassified: ReindexUnclassified[];
     /** Distinct files that resolve to the same index name — reported, never overwritten. */
     nameConflicts: ReindexNameConflict[];
-    /** Previous index entries whose `sourcePath` no longer exists (error-class drift). */
     orphanIndex: ReindexOrphanEntry[];
     /** Files on disk that the rebuilt index does not contain (warn-class drift). */
     orphanDisk: string[];

package/dist/services/memory/project-memory-service/index/reindex.js

@@ -3,7 +3,6 @@
 // the markdown files on disk, plus regeneration of the human/LLM-facing
 // `MEMORY.md` index and a drift report.
 //
-// Why this exists (slice 2026-09-09-memory-system-overhaul, B):
 //   - `peaks memory extract` only ever wrote memories FROM artifacts; it
 //     never re-scanned files already on disk, and there was no rebuild
 //     command. 78 top-level files were absent from index.json.

package/dist/services/memory/project-memory-service/index/search.d.ts

@@ -29,6 +29,5 @@ export declare function readProjectMemories(projectRoot: string): ProjectMemoryR
  * Read a single project memory's full body by name. Returns null when
  * the memory does not exist. The on-disk body is returned verbatim
  * (pretty). The CLI layer applies `formatMdCompact` when `format: 'compact'`
- * is requested. Slice 023 (R3).
  */
 export declare function readProjectMemoryBody(projectRoot: string, name: string): ProjectMemoryShowResult | null;

package/dist/services/memory/project-memory-service/index/search.js

@@ -145,7 +145,6 @@ export function readProjectMemories(projectRoot) {
  * Read a single project memory's full body by name. Returns null when
  * the memory does not exist. The on-disk body is returned verbatim
  * (pretty). The CLI layer applies `formatMdCompact` when `format: 'compact'`
- * is requested. Slice 023 (R3).
  */
 export function readProjectMemoryBody(projectRoot, name) {
     const normalizedRoot = normalizeRoot(projectRoot);

package/dist/services/memory/project-memory-service/memory-kinds.d.ts

@@ -6,7 +6,6 @@
  * `--kind` help text all derive from this tuple. Adding a kind here is the
  * only edit required; TypeScript then forces `MEMORY_KIND_TIER` to cover it.
  *
- * Slice 2026-09-10-memory-vocab-and-rotate (E): the original 8 kinds are
  * unchanged. The 13 appended kinds were observed on disk with real values
  * that the index schema rejected (`peaks memory reindex` reported them as
  * `unrecognized kind value`). Accepting them moves those files into the

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

@@ -17,7 +17,6 @@
  * `--kind` help text all derive from this tuple. Adding a kind here is the
  * only edit required; TypeScript then forces `MEMORY_KIND_TIER` to cover it.
  *
- * Slice 2026-09-10-memory-vocab-and-rotate (E): the original 8 kinds are
  * unchanged. The 13 appended kinds were observed on disk with real values
  * that the index schema rejected (`peaks memory reindex` reported them as
  * `unrecognized kind value`). Accepting them moves those files into the

package/dist/services/memory/project-memory-service/parsers/frontmatter.d.ts

@@ -36,7 +36,6 @@ export interface ParsedMemoryFrontmatter {
  *   3. top-level `type:`        — tolerated by the pre-existing trim-based reader
  *   4. `none`                   — reported as unclassified; never invented
  *
- * Slice 2026-09-09-memory-system-overhaul (B): before this helper, files
  * using a top-level `kind:` were silently dropped by the reader (defect
  * #2). Falling through to `kind:` / `type:` is a strict superset of the
  * old behaviour — no previously-indexed file changes kind.

package/dist/services/memory/project-memory-service/parsers/frontmatter.js

@@ -35,7 +35,6 @@ export { parseBlock, parseBlockResult, renderMemoryFile, slugify, VALID_MEMORY_K
  *   3. top-level `type:`        — tolerated by the pre-existing trim-based reader
  *   4. `none`                   — reported as unclassified; never invented
  *
- * Slice 2026-09-09-memory-system-overhaul (B): before this helper, files
  * using a top-level `kind:` were silently dropped by the reader (defect
  * #2). Falling through to `kind:` / `type:` is a strict superset of the
  * old behaviour — no previously-indexed file changes kind.

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

@@ -2,7 +2,6 @@
 // Thin back-compat shim.
 //
 // The original 1032-line project-memory-service.ts was split on 2026-07-26
-// (rid-003) into the `./project-memory-service/` submodule:
 //
 //   - parsers/frontmatter.ts          — YAML frontmatter parse + render
 //   - parsers/markdown-pure.ts        — extract / summarize (pure)

package/dist/services/mode/mode-enforcement.js

@@ -5,7 +5,6 @@ const ASSISTED_CONFIRM_TRANSITIONS = new Set([
     'qa:verdict-issued'
 ]);
 export function requiresConfirmation(mode, transitionKey) {
-    // Slice 2026-09-09-mode-consolidation: `swarm` removed as a mode; the
     // two auto-proceed peers are `full-auto` and `24h`.
     if (mode === 'full-auto' || mode === '24h') {
         return false;

package/dist/services/mode/mode-status-service.d.ts

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-09-09-mode-consolidation (Slice D): one read for the whole
  * stacked mode picture.
  *
  * The autonomy model has two layers that used to be read by nothing in
@@ -82,7 +81,6 @@ export declare function resolvePresenceMode(projectRoot: string): ResolvedPresen
  * documented contract.
  *
  * The union is a superset of both the pre-2026-09-09 mapping (state
- * machine) and the 2026-09-09-mode-consolidation mapping (presence
  * mode): keep partial while the mode says `24h` even in
  * `WAITING_USER`, and keep it when only the state machine knows.
  * Nothing that resolved to `partial` before resolves to `standard`

package/dist/services/mode/mode-status-service.js

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-09-09-mode-consolidation (Slice D): one read for the whole
  * stacked mode picture.
  *
  * The autonomy model has two layers that used to be read by nothing in
@@ -95,7 +94,6 @@ function is24hRunEngaged(projectRoot) {
  * documented contract.
  *
  * The union is a superset of both the pre-2026-09-09 mapping (state
- * machine) and the 2026-09-09-mode-consolidation mapping (presence
  * mode): keep partial while the mode says `24h` even in
  * `WAITING_USER`, and keep it when only the state machine knows.
  * Nothing that resolved to `partial` before resolves to `standard`

package/dist/services/observability/aggregation.d.ts

@@ -7,10 +7,6 @@
  * them in. Tests pass synthetic events directly.
  *
  * Aggregations:
- *   - `aggregateStatus(events)`        → AC-1
- *   - `aggregateSlices(events)`        → AC-2
- *   - `aggregateFanout(events)`        → AC-3
- *   - `aggregateRepairCycles(events)`  → AC-4
  *
  * The dispatch / mode-gate / context / post-compact categories land
  * in Slice C (more hooks); for Slice B only `slice-transition` events

package/dist/services/observability/aggregation.js

@@ -7,10 +7,6 @@
  * them in. Tests pass synthetic events directly.
  *
  * Aggregations:
- *   - `aggregateStatus(events)`        → AC-1
- *   - `aggregateSlices(events)`        → AC-2
- *   - `aggregateFanout(events)`        → AC-3
- *   - `aggregateRepairCycles(events)`  → AC-4
  *
  * The dispatch / mode-gate / context / post-compact categories land
  * in Slice C (more hooks); for Slice B only `slice-transition` events
@@ -129,7 +125,6 @@ export function aggregateRepairCycles(events) {
         perSlice
     };
 }
-// ----- period rollup (AC-5 — Slice D, but helpers live here) -----
 export function periodStartIso(period, now = () => new Date()) {
     const d = now();
     if (period === 'day') {
@@ -151,7 +146,6 @@ export function filterByPeriod(events, period, now) {
     const start = periodStartIso(period, now);
     return events.filter((e) => e.ts >= start);
 }
-// ----- rid-030 F-direction: 5-metric dashboard summary -----
 /**
  * Aggregate the 5 dashboard metric classes for a single session, filtered
  * to events with `ts >= since`. Events with unparseable timestamps are

package/dist/services/observability/observability-schema.js

@@ -25,7 +25,6 @@ export const OBSERVABILITY_CATEGORIES = [
     'cycle',
     'token-usage',
     'monotonic-trigger',
-    // Slice 2026-07-29-worktree-l2-extended Part 4.A: lease lifecycle
     // metrics. Emitted by `peaks worktree spawn / renew / release /
     // gc` and by the auto-release hook in dispatch finalization (Part
     // 3.A). Read by `peaks lease metrics`. The `detail.kind` field

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

@@ -50,7 +50,6 @@ export declare function readObservabilityEvents(projectRoot: string, sessionId:
  */
 export declare function isCurrentSchemaVersion(record: unknown): record is ObservabilityEvent;
 /**
- * Slice 2026-07-29-worktree-l2-extended Part 4.A: lease lifecycle
  * observability. Each `peaks worktree spawn / renew / release /
  * gc` CLI emits a `lease` event; the auto-release hook in
  * dispatch finalization emits `autoRelease` (success) or
@@ -74,7 +73,6 @@ export declare function emitLeaseEvent(opts: {
     reason?: string;
 }): EmitResult;
 /**
- * rid-030 F-direction: per-cycle event (cycle started / completed / failed).
  * Fire-and-forget; never throws. Tagging `kind` for downstream dashboards.
  */
 export declare function emitCycleEvent(opts: {
@@ -84,7 +82,6 @@ export declare function emitCycleEvent(opts: {
     status: 'started' | 'completed' | 'failed';
 }): EmitResult;
 /**
- * rid-030 F-direction: per-token-usage event. `totalTokens` is the
  * sum the dashboard cares about; `inputTokens`/`outputTokens` are kept
  * for downstream drill-down.
  */
@@ -95,7 +92,6 @@ export declare function emitTokenUsageEvent(opts: {
     outputTokens: number;
 }): EmitResult;
 /**
- * rid-030 F-direction: per-monotonic-trigger event.
  */
 export declare function emitMonotonicTriggerEvent(opts: {
     sessionId: string;
@@ -104,7 +100,6 @@ export declare function emitMonotonicTriggerEvent(opts: {
     action: string;
 }): EmitResult;
 /**
- * rid-030 F-direction: per-subagent-dispatch event. Reuses the
  * existing `dispatch` category (rd/qa/reviewer/audit). Provides a
  * canonical emit helper so dashboards don't have to hand-author the
  * `ObservabilityEvent` envelope.

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

@@ -117,7 +117,6 @@ export function emitLeaseEvent(opts) {
     }, { projectRoot: opts.projectRoot });
 }
 /**
- * rid-030 F-direction: per-cycle event (cycle started / completed / failed).
  * Fire-and-forget; never throws. Tagging `kind` for downstream dashboards.
  */
 export function emitCycleEvent(opts) {
@@ -130,7 +129,6 @@ export function emitCycleEvent(opts) {
     }, { projectRoot: opts.projectRoot });
 }
 /**
- * rid-030 F-direction: per-token-usage event. `totalTokens` is the
  * sum the dashboard cares about; `inputTokens`/`outputTokens` are kept
  * for downstream drill-down.
  */
@@ -149,7 +147,6 @@ export function emitTokenUsageEvent(opts) {
     }, { projectRoot: opts.projectRoot });
 }
 /**
- * rid-030 F-direction: per-monotonic-trigger event.
  */
 export function emitMonotonicTriggerEvent(opts) {
     return emitObservabilityEvent({
@@ -161,7 +158,6 @@ export function emitMonotonicTriggerEvent(opts) {
     }, { projectRoot: opts.projectRoot });
 }
 /**
- * rid-030 F-direction: per-subagent-dispatch event. Reuses the
  * existing `dispatch` category (rd/qa/reviewer/audit). Provides a
  * canonical emit helper so dashboards don't have to hand-author the
  * `ObservabilityEvent` envelope.

package/dist/services/observability/report-formatter.d.ts

@@ -1,13 +1,11 @@
 /**
  * Markdown report formatter for slice topology observability.
  *
- * Slice D of v2.11.1 (AC-5). Pure functions: inputs are aggregations
  * from `aggregation.ts`, outputs are stable markdown strings suitable
  * for pasting into PR descriptions or `.peaks/PROJECT.md` timeline
  * entries. The CLI subcommand `peaks observability report` wires
  * the file read + aggregation + format pipeline.
  *
- * Format contract (per PRD AC-5):
  *   - Header: scope, period, generated-at timestamp
  *   - Slice table: rid | transitions | finalState | durationMs | success
  *   - Fanout table: role | count

package/dist/services/observability/report-formatter.js

@@ -1,13 +1,11 @@
 /**
  * Markdown report formatter for slice topology observability.
  *
- * Slice D of v2.11.1 (AC-5). Pure functions: inputs are aggregations
  * from `aggregation.ts`, outputs are stable markdown strings suitable
  * for pasting into PR descriptions or `.peaks/PROJECT.md` timeline
  * entries. The CLI subcommand `peaks observability report` wires
  * the file read + aggregation + format pipeline.
  *
- * Format contract (per PRD AC-5):
  *   - Header: scope, period, generated-at timestamp
  *   - Slice table: rid | transitions | finalState | durationMs | success
  *   - Fanout table: role | count

package/dist/services/openspec/artifact-boundary.d.ts

@@ -1,7 +1,6 @@
 /**
  * Artifact boundary helpers for peaks-loop.
  *
- * Slice rid-009:
  *   - sub-slice 1: change-id validation (`validateChangeId`).
  *   - sub-slice 2: artifact path planning (`planArtifactPath` + `isPathInsideArtifactRoot` re-export).
  *   - sub-slice 3: workspace-unavailable response (`buildWorkspaceUnavailable`).
@@ -61,7 +60,6 @@ export type BoundaryError = ChangeIdError | {
  * distinguishes "empty" / "format" / "reserved" so callers can branch on
  * the cause without re-parsing the message.
  *
- * Acceptance contract (rid-009 §3.3.1, task 1):
  *   - accepts `[A-Za-z0-9][A-Za-z0-9._-]*` (existing regex semantics)
  *   - rejects empty string with `change-id-empty`
  *   - rejects `.` and `..` with `change-id-reserved`
@@ -80,7 +78,6 @@ export declare function validateChangeId(id: string): Result<{
  *
  * Single source of truth: the primitive is owned by `src/shared/path-safety.ts`;
  * this module owns the *domain* helpers (change-id + path planner) that consume
- * the primitive. Tests in `tests/unit/services/openspec/artifact-boundary.test.ts`
  * exercise the RE-EXPORT wiring; the primitive's own correctness is covered by
  * its native test file.
  */
@@ -109,7 +106,6 @@ export type PlanArtifactPathOutput = {
 /**
  * Plan an artifact-relative path under the configured Peaks artifact workspace.
  *
- * Semantics (rid-009 §3.3.2, tasks 5–9):
  *   - Backslashes in the candidate path are normalized to forward slashes for
  *     JSON safety; empty segments (`foo//bar`) are collapsed by `posix.normalize`.
  *   - If the resolved absolute path is NOT contained under `workspaceRoot`

package/dist/services/openspec/artifact-boundary.js

@@ -1,7 +1,6 @@
 /**
  * Artifact boundary helpers for peaks-loop.
  *
- * Slice rid-009:
  *   - sub-slice 1: change-id validation (`validateChangeId`).
  *   - sub-slice 2: artifact path planning (`planArtifactPath` + `isPathInsideArtifactRoot` re-export).
  *   - sub-slice 3: workspace-unavailable response (`buildWorkspaceUnavailable`).
@@ -38,7 +37,6 @@ const CHANGE_ID_FORMAT_PATTERN = /^[A-Za-z0-9][A-Za-z0-9._-]*$/;
  * distinguishes "empty" / "format" / "reserved" so callers can branch on
  * the cause without re-parsing the message.
  *
- * Acceptance contract (rid-009 §3.3.1, task 1):
  *   - accepts `[A-Za-z0-9][A-Za-z0-9._-]*` (existing regex semantics)
  *   - rejects empty string with `change-id-empty`
  *   - rejects `.` and `..` with `change-id-reserved`
@@ -75,7 +73,6 @@ export function validateChangeId(id) {
  *
  * Single source of truth: the primitive is owned by `src/shared/path-safety.ts`;
  * this module owns the *domain* helpers (change-id + path planner) that consume
- * the primitive. Tests in `tests/unit/services/openspec/artifact-boundary.test.ts`
  * exercise the RE-EXPORT wiring; the primitive's own correctness is covered by
  * its native test file.
  */
@@ -90,7 +87,6 @@ function interpolateTemplate(template, changeId, role, requestId) {
 /**
  * Plan an artifact-relative path under the configured Peaks artifact workspace.
  *
- * Semantics (rid-009 §3.3.2, tasks 5–9):
  *   - Backslashes in the candidate path are normalized to forward slashes for
  *     JSON safety; empty segments (`foo//bar`) are collapsed by `posix.normalize`.
  *   - If the resolved absolute path is NOT contained under `workspaceRoot`

package/dist/services/openspec/coverage-evidence-reader.d.ts

@@ -1,7 +1,6 @@
 /**
  * Coverage Evidence reader for c8 `coverage-summary.json` (Fix-6B).
  *
- * Slice rid-Fix-6B / sub-slice T1:
  *   - pure helper module, no side effects beyond FS reads
  *   - reads the istanbul-reporter JSON shape emitted by `c8 --reporter=json-summary`
  *     (the project's coverage tool — see scripts/coverage-c8.mjs)

package/dist/services/openspec/coverage-evidence-reader.js

@@ -1,7 +1,6 @@
 /**
  * Coverage Evidence reader for c8 `coverage-summary.json` (Fix-6B).
  *
- * Slice rid-Fix-6B / sub-slice T1:
  *   - pure helper module, no side effects beyond FS reads
  *   - reads the istanbul-reporter JSON shape emitted by `c8 --reporter=json-summary`
  *     (the project's coverage tool — see scripts/coverage-c8.mjs)

package/dist/services/polyrepo/polyrepo-dispatcher.js

@@ -1,5 +1,4 @@
 /**
- * Polyrepo dispatcher — slice S2-b of RD-2.
  *
  * Takes a parent root + a list of target child ids + a PRD/RD/QA
  * artifact, and mirrors the artifact into each target child's

package/dist/services/polyrepo/polyrepo-scanner.js

@@ -1,5 +1,4 @@
 /**
- * Polyrepo scanner — slice S2-b of RD-2.
  *
  * Walks a parent directory looking for child git repos. A "child
  * git repo" is defined as: a directory that contains a `.git`

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

@@ -1,5 +1,4 @@
 /**
- * Polyrepo service — slice S2-b of RD-2.
  *
  * Thin orchestrator wrapping the scanner + dispatcher. CLI commands
  * call into this service so they don't need to know about the

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

@@ -1,5 +1,4 @@
 /**
- * Polyrepo types — slice S2-b of RD-2.
  *
  * Models a parent directory that hosts one or more child git repos,
  * each of which may carry its own `.peaks/` state. The root `.peaks/`

package/dist/services/prd/best-practice-auto-trigger.d.ts

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-08-12 best-practice-scan — auto-trigger post-step (Slice F).
  *
  * When peaks-prd's request artifact transitions to `handed-off`, this helper
  * extracts the `businessGoal` (first non-empty bullet under `## Goals` of the
@@ -18,7 +17,6 @@
  *   - Spawn 'spawn' event        → status: 'triggered' (resolved; child detached)
  *
  * Karpathy §1 (Think Before Coding): extracted from the QA verdict
- * `verdict-rid-best-practice-scan-qa-ship.md` AC-1 PARTIAL finding. The
  * `prd:handed-off` transition in `src/cli/commands/request-commands.ts`
  * is the canonical hook point — peaks-prd's contract in
  * `skills/bee/peaks-prd/SKILL.md` §"Step 2.5 sub-step" mandates this firing

package/dist/services/prd/best-practice-auto-trigger.js

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-08-12 best-practice-scan — auto-trigger post-step (Slice F).
  *
  * When peaks-prd's request artifact transitions to `handed-off`, this helper
  * extracts the `businessGoal` (first non-empty bullet under `## Goals` of the
@@ -18,7 +17,6 @@
  *   - Spawn 'spawn' event        → status: 'triggered' (resolved; child detached)
  *
  * Karpathy §1 (Think Before Coding): extracted from the QA verdict
- * `verdict-rid-best-practice-scan-qa-ship.md` AC-1 PARTIAL finding. The
  * `prd:handed-off` transition in `src/cli/commands/request-commands.ts`
  * is the canonical hook point — peaks-prd's contract in
  * `skills/bee/peaks-prd/SKILL.md` §"Step 2.5 sub-step" mandates this firing

package/dist/services/prd/gate-evidence-derivation.d.ts

@@ -1,10 +1,8 @@
 /**
  * Where `gateEvidence` comes FROM, and where its promise is checked.
  *
- * B2 (merged with the B1 repair), rid `rid-b2-gate-evidence-wiring`.
  *
  * B1 made the field real at the SERVICE layer and QA found the hole that
- * mattered (F1 of `rid-b1-qa`): all three frontmatter producers passed
  * nothing, so no capsule on disk ever carried the field — the dead surface
  * had moved one layer out, from "no producer function" to "no production
  * caller". This module closes that by DERIVING the map instead of accepting
@@ -56,7 +54,6 @@
  * For `docs`/`chore` nothing ever reads it, so it is not declared: keeping an
  * inert statement in every docs capsule would recreate, in miniature, the exact
  * defect this whole line of work exists to remove — a claim no one reads, which
- * is how the field was dead in the first place (F1 of `rid-b2-qa`). Scope, in
  * one sentence: **this map declares the evidence paths Gate C will check for
  * this slice**, so an empty declaration is the honest one when there is no such
  * gate.
@@ -99,7 +96,6 @@ export declare function deriveGateEvidence(opts: {
  * so a caller can tell "this slice has nothing to declare" apart from "the
  * artifact could not be read".
  *
- * F4 (`rid-f4-ceiling-breach`). This used to be `catch { return undefined }`,
  * which folded those two into one value — and the repository's own ratchet
  * caught it (`capability-guard-runner/contracts/J03.ts`, rule
  * `catch-return-null`; the ceiling was written for exactly this shape). Nothing