peaks-loop 4.1.0 → 4.1.2

package/dist/cli/commands/compact-command.js

@@ -305,7 +305,6 @@ export function registerCompactCommands(program, io) {
             process.exitCode = 1;
         }
     });
-    // 6. peaks compact history [--json] (slice 2026-07-30-compact-visibility)
     addJsonOption(compact
         .command('history')
         .description('Read the per-session compact-history.jsonl and emit a structured ' +
@@ -346,7 +345,6 @@ export function registerCompactCommands(program, io) {
                 return;
             }
             const summary = summarizeCompactHistory(result.events);
-            // Slice 2026-09-13-auto-compact-trigger-ownership (T4): the
             // intent-vs-observed record. `pairs[i].requestedTokens` is the token
             // point peaks-loop asked for; `observedTokens` is what the next real
             // session actually measured. Unmeasured pairs are reported as such —
@@ -369,7 +367,6 @@ export function registerCompactCommands(program, io) {
         }
     }));
     // 7. peaks compact harness-window [--reset | --disable | --reenable]
-    //    (slice 2026-09-13-auto-compact-trigger-ownership, T1 + T2)
     //
     // The window peaks-loop divides by and the window the harness compacts
     // against must be ONE number, or "95%" lands at two different token counts.
@@ -496,7 +493,6 @@ export function registerCompactCommands(program, io) {
         }
     }));
     // 8. peaks compact settle [--json]
-    //    (slice 2026-09-13-compact-event-settle)
     //
     // The `PostCompact` hook's transport. Before this command, peaks-loop knew a
     // compaction had landed only because a LATER probe measured a ratio that had

package/dist/cli/commands/container-commands.d.ts

@@ -1,5 +1,4 @@
 /**
- * `peaks container spawn | release` — slice 2026-07-29-worktree-l2-extended Part 12.
  *
  * L4 container isolation bridge: Part 8 landed the CLI contract
  * (`peaks sub-agent dispatch --isolation container` is accepted

package/dist/cli/commands/container-commands.js

@@ -1,5 +1,4 @@
 /**
- * `peaks container spawn | release` — slice 2026-07-29-worktree-l2-extended Part 12.
  *
  * L4 container isolation bridge: Part 8 landed the CLI contract
  * (`peaks sub-agent dispatch --isolation container` is accepted

package/dist/cli/commands/context-commands.d.ts

@@ -1,7 +1,6 @@
 /**
  * peaks context * CLI (Slice #3 L1c) — context 4-layer loader.
  *
- * Per docs/superpowers/specs/2026-06-11-peaks-loop-l1-l2-l3-redesign.md §4 L1c:
  *   - L0: full read (every SKILL.md in full)
  *   - L1: summary (one paragraph per skill + the skill list)
  *   - L2: index (just names + paths)

package/dist/cli/commands/context-commands.js

@@ -1,7 +1,6 @@
 /**
  * peaks context * CLI (Slice #3 L1c) — context 4-layer loader.
  *
- * Per docs/superpowers/specs/2026-06-11-peaks-loop-l1-l2-l3-redesign.md §4 L1c:
  *   - L0: full read (every SKILL.md in full)
  *   - L1: summary (one paragraph per skill + the skill list)
  *   - L2: index (just names + paths)

package/dist/cli/commands/core/doctor-command.d.ts

@@ -1,7 +1,6 @@
 import type { Command } from 'commander';
 import { type ProgramIO } from '../../cli-helpers.js';
 /**
- * Slice 2026-09-10-context-audit-and-discipline (Slice B): bounded view of
  * the doctor envelope. The `checks` array (one object per check, each with a
  * full message) and the stale-binding instance list collapse to counts +
  * names-of-first-N; the summary counters and log section are scalars and are

package/dist/cli/commands/core/doctor-command.js

@@ -40,7 +40,6 @@ function statusLineAlreadyInstalledForScope(scope, projectRoot) {
     }
 }
 /**
- * Slice 2026-09-10-context-audit-and-discipline (Slice B): bounded view of
  * the doctor envelope. The `checks` array (one object per check, each with a
  * full message) and the stale-binding instance list collapse to counts +
  * names-of-first-N; the summary counters and log section are scalars and are
@@ -98,11 +97,9 @@ function doctorStatusLineInstalledProbe() {
         return false;
     }
 }
-// Slice v2.16.0 AC-10: stale binding TTL is 5 minutes by default. The
 // threshold is exposed as a CLI flag so users can tune it for
 // long-running sessions.
 const STALE_TTL_MS = 5 * 60 * 1000;
-// Slice v2.16.0 AC-10: identify stale instances (lastHeartbeat > 5min)
 // in the project-level binding. Used by `peaks doctor` and surfaced as
 // a warning in the report. Returns the stale entry descriptors.
 function listStaleInstances(projectRoot, ttlMs = STALE_TTL_MS) {
@@ -119,7 +116,6 @@ function listStaleInstances(projectRoot, ttlMs = STALE_TTL_MS) {
     }
     return stale;
 }
-// Slice 2026-06-16-cli-logging (AC6) — `peaks doctor --log` section.
 //
 // `buildDoctorLogsSection` reads the on-disk log dir and returns the
 // metadata the doctor needs to render the "logs" block. It is
@@ -152,7 +148,6 @@ async function buildDoctorLogsSection() {
         level: process.env.PEAKS_LOG_LEVEL ?? 'info'
     };
 }
-// Slice 2026-06-16-cli-logging (AC6): `peaks doctor --log` adds a
 // "logs" section to the doctor output (logDir, today's file name,
 // size, retention policy, level). Useful for the user when they
 // want to attach a quick log snapshot to a bug report without
@@ -236,7 +231,6 @@ export function registerDoctorCommand(program, io) {
         if (options.log === true) {
             logsSection = await buildDoctorLogsSection();
         }
-        // v2.16.0 AC-10: scan binding for stale instances.
         const ttl = options.staleTtlMs !== undefined ? Number(options.staleTtlMs) : STALE_TTL_MS;
         const staleInstances = listStaleInstances(projectRoot, ttl);
         let droppedStale = [];
@@ -257,7 +251,6 @@ export function registerDoctorCommand(program, io) {
         // Slice B: `--summary` is opt-in and affects the JSON envelope only (the
         // human-readable path below already prints one line per check).
         const data = options.summary === true ? buildDoctorSummary(fullData) : fullData;
-        // Slice 2026-08-05-statusline-sid-only-marker-and-multi-binary-drift-guard
         // repair cycle: `report.summary.ok` already factors in the
         // severity-aware aggregation in `buildReport` (warnings do NOT
         // flip `ok`). Stale-binding is independent and still escalates.
@@ -273,7 +266,6 @@ export function registerDoctorCommand(program, io) {
         }
         else {
             // Human-readable: one line per check, green/red indicators, no JSON.
-            // Slice 2026-08-05-statusline-sid-only-marker-and-multi-binary-drift-guard
             // repair cycle: warn-only findings (severity: 'warning') surface
             // as `! check.ok` with the `! ` (warning) glyph so the operator
             // can tell them apart from real errors without reading JSON.
@@ -320,7 +312,6 @@ export function registerDoctorCommand(program, io) {
                 io.stdout(`\n  ${report.summary.warnings} warning(s) present — exit code 0 (warn-only).`);
             }
         }
-        // Slice 2026-08-05-statusline-sid-only-marker-and-multi-binary-drift-guard
         // repair cycle: `report.summary.ok` already factors in the
         // severity-aware aggregation in `buildReport` (warnings do NOT
         // flip `ok`). The exit-code gate remains `summary.ok &&

package/dist/cli/commands/core/memory-command.js

@@ -201,7 +201,6 @@ export function registerMemoryCommand(program, io) {
  * raised only because a memory TITLE contained a word like `authority`
  * (slice C0). There was no secret anywhere in that memory, so the one thing
  * the hint told the user to do was the one thing that could not help: it sent
- * them looking for a credential that did not exist. A remedy has to answer the
  * check that actually failed.
  *
  * `null` (a failure that is not a safety refusal — a path escape, a missing
@@ -217,5 +216,15 @@ function memoryExtractNextActions(refusal) {
             'Retitle the memory so it is not named after a credential term, then re-run memory extract'
         ];
     }
+    if (refusal.check === SENSITIVE_MEMORY_CHECKS.content) {
+        // Name the rule, not just the family. `matchedTerm` is a closed id
+        // (`credential-assignment`, `bearer-value`, `pem-private-key`, …), so the
+        // reader can tell a credential in the text from a sentence that merely has
+        // the shape of one — which is the difference between removing a value and
+        // rewording prose.
+        return [
+            `Remove the credential value the "${refusal.matchedTerm}" pattern matched, then re-run memory extract`
+        ];
+    }
     return ['Remove the credential value from the memory content, then re-run memory extract'];
 }

package/dist/cli/commands/core/session-command.js

@@ -5,7 +5,6 @@ import { resolveCanonicalProjectRoot } from '../../../services/config/config-ser
 import { findProjectRoot } from '../../../services/config/config-safety.js';
 import { fail, ok } from 'peaks-loop-shared/result';
 import { addJsonOption, getErrorMessage, printResult } from '../../cli-helpers.js';
-// Slice 2026-07-01-strategic-compact-cli fix: register the
 // `peaks session checkpoint` and `peaks session resume` subcommands
 // EAGERLY so they appear in `peaks session --help` output. The
 // previous lazy import ran AFTER commander had already produced
@@ -19,7 +18,6 @@ import { registerSessionResumeCommand } from '../session-resume-command.js';
 // `peaks session --help` for LLM `<TAB>`-discovery. See
 // src/services/migrate-skill-name/.
 import { registerSessionMigrateSkillNameCommand } from '../session-migrate-skill-name.js';
-// rid-020a: register `peaks session 24h-mode` eagerly so the
 // state-machine sub-actions (state / transition / attempts / reset)
 // appear in `peaks session --help` for LLM `<TAB>`-discovery.
 import { registerSession24hModeCommand } from '../session-24h-mode.js';
@@ -36,19 +34,16 @@ export function registerSessionCommand(program, io) {
         .description('Show full metadata for a session directory. Pass --active to resolve the canonical binding from .peaks/_runtime/session.json (the "one command a sub-agent runs to find the parent\'s sid" primitive). Slice 021: --active is the SOLE authoritative way to look up the active session id; the on-disk file path is internal and must NOT be `cat`-ed directly.')
         .option('--active', 'resolve the canonical session id from .peaks/_runtime/session.json (ignores [sessionId] when set)')
         .option('--project <path>', 'target project root (defaults to git root or cwd). Slice 021: lets sub-agents skip the cwd heuristic and look up the binding for a specific repo.')
-        // Slice 020 — caller-keyed session binding. The --caller-id flag
         // overrides the per-process PEAKS_CALLER_ID env var and the
         // PLATFORM_FALLBACKS table (D4 priority). The resolved callerId is
         // surfaced in the JSON envelope so callers can confirm what was
         // resolved without re-deriving it.
         .option('--caller-id <id>', 'Override the caller id for this invocation (D4 priority: flag beats env beats platform fallback). When set, the response envelope includes the resolved callerId.')).action(async (sessionId, options) => {
-        // Slice 021: --project wins; otherwise the git-root / cwd fallback
         // (matches the pre-021 behaviour so the existing slice-020 / slice-007
         // sub-agent flow keeps working unchanged).
         const projectRoot = options.project !== undefined
             ? resolveCanonicalProjectRoot(options.project)
             : (findProjectRoot(process.cwd()) ?? process.cwd());
-        // Slice 020 — resolve the callerId up front when the flag was passed.
         // We use `resolveCallerId` for D1/D5 validation; an invalid flag
         // throws CallerIdError (D5 → exit 65). A missing flag and no env
         // and no fallback also throws (D2 → exit 64). The resolved id is
@@ -79,7 +74,6 @@ export function registerSessionCommand(program, io) {
                 const { getCallerBinding } = await import('../../../services/session/caller-binding-service.js');
                 const activeSid = getSessionIdCanonical(projectRoot);
                 const callerBinding = getCallerBinding(projectRoot, callerId);
-                // Slice 021: source is the enum that the unified --active primitive
                 // reports. Callers / migration tooling can detect pre-migration trees
                 // by inspecting `source === 'legacy'`.
                 const bindingSource = existsSync(join(projectRoot, '.peaks', '_runtime', 'session.json'))
@@ -100,9 +94,7 @@ export function registerSessionCommand(program, io) {
             }), options.json);
             return;
         }
-        // Slice 007 + slice 021 — sub-agent session sharing. A sub-agent that
         // does not know the parent's sid reads it from the binding via
-        // `peaks session info --active`. Slice 021 turned this into the
         // SOLE authoritative discovery primitive: it composes on
         // getSessionIdCanonical (canonicalize-on-read; handles the stored
         // "projectRoot: '.'" vs caller-passed absolute realpath mismatch
@@ -138,16 +130,13 @@ export function registerSessionCommand(program, io) {
             }
             // 4. Determine the on-disk source so callers (and future
             //    migration tooling) can detect pre-migration trees. The
-            //    canonical file is preferred when both exist (slice 005
             //    contract).
             const bindingSource = existsSync(join(projectRoot, '.peaks', '_runtime', 'session.json'))
                 ? 'canonical'
                 : 'legacy';
-            // Slice 021: when only the legacy back-compat path is present,
             // surface a warning so callers (and humans tailing the JSON)
             // see "this tree has not been reconciled to the canonical
             // home yet". The warning is informational; the binding is
-            // still valid for one minor release (slice 005 / 006
             // contract). `warnings` is a top-level envelope field, not a
             // data field, so it goes through ok()'s 3rd positional arg.
             const legacyWarnings = bindingSource === 'legacy'
@@ -194,9 +183,7 @@ export function registerSessionCommand(program, io) {
             process.exitCode = 1;
         }
     });
-    // Slice 011: `peaks session checkpoint` and `peaks session resume`.
     // Skill-level primitives — the LLM is the decision-maker; CLI is the muscle.
-    // Slice 2026-07-01-strategic-compact-cli fix: register EAGERLY (not
     // via `void (async () => …)`) so commander walks the subcommand
     // tree synchronously and `peaks session --help` includes both
     // `checkpoint` and `resume`. The previous async-IIFE registered
@@ -211,7 +198,6 @@ export function registerSessionCommand(program, io) {
     // .peaks/_runtime/** for the rename; skipped paths recorded in
     // the response envelope. See src/services/migrate-skill-name/.
     registerSessionMigrateSkillNameCommand(session);
-    // rid-020a: peaks session 24h-mode — state machine backbone.
     registerSession24hModeCommand(session, io);
     registerSpillDemoCommand(session, io);
     addJsonOption(session

package/dist/cli/commands/core/skill-command.js

@@ -136,19 +136,17 @@ function generatedConfigNotice(projectRoot) {
         warnings: [
             `Generated config at '${projectRoot}' was produced by peaks-loop ${onDiskVersion} ` +
                 `but ${staleness.expected.packageVersion} is installed (${staleness.reasons.join(', ')}). ` +
-                `Re-run \`peaks workspace init\` (or the idempotent \`peaks upgrade --apply-init\`) ` +
+                `Re-run \`peaks workspace init\` ` +
                 `to regenerate .claude/settings.local.json and the offline template copy.`
         ]
     };
 }
 import { addJsonOption, getErrorMessage, printResult } from '../../cli-helpers.js';
-// Slice S0 (4.0.0-beta.5 peaks-solo dispatcher release):
 // `peaks skill search` is the CLI primitive that feeds the
 // peaks-solo dispatcher (S1). Adding a single import + register call
 // here keeps the change surgical and leaves all existing skill
 // subcommands (list / doctor / sync / runbook / presence / heartbeat)
 // untouched. See
-// docs/superpowers/specs/2026-07-08-peaks-solo-dispatcher-design.md §3.2
 // and the S0 plan under docs/superpowers/plans/.
 import { registerSkillSearchCommand } from '../skill-search-commands.js';
 export function registerSkillCommand(program, io) {
@@ -166,7 +164,6 @@ export function registerSkillCommand(program, io) {
         }
         else {
             const sorted = [...skills].sort((a, b) => {
-                // Slice S0 (4.0.0-beta.5): peaks-solo is the dispatcher (front
                 // door) — list it FIRST so users discover the dispatcher before
                 // any specific leaf. Followed by peaks-sop (current default
                 // runbook showcase) and peaks-code (canonical code-domain
@@ -291,7 +288,6 @@ export function registerSkillCommand(program, io) {
         // makes — in every mode and every consumer project.
         const verdict = contextVerdict(projectOption ?? process.cwd());
         if (options.checkStale === true) {
-            // Slice 002 (v2.15.0) AC-1: pair the read with a staleness
             // check so callers (peaks-code Step 1, statusline) get both
             // pieces of info from a single CLI invocation. The presence
             // is returned UNCHANGED — `--check-stale` is a read-only flag,
@@ -384,7 +380,6 @@ export function registerSkillCommand(program, io) {
         // and a still-running lease.
         const removed = clearSkillPresence(options.project);
         // Auto-update project context so future sessions have up-to-date history.
-        // Slice 2026-07-15-project-scan-bootstrap: generateProjectContext now also
         // bootstraps `.peaks/project-scan/` (idempotent). Await the async
         // signature; failure is still non-fatal so we don't block the clear.
         try {
@@ -472,7 +467,6 @@ export function registerSkillCommand(program, io) {
             process.exitCode = 1;
         }
     });
-    // Slice 002 (v2.15.0) — AC-1: presence staleness detector.
     // peaks-code Step 1 (and `peaks code should-pause --step
     // step-1-mode-select`) calls this to decide whether the recorded
     // `mode` field can be trusted or whether the LLM must AskUserQuestion.
@@ -483,7 +477,6 @@ export function registerSkillCommand(program, io) {
         'Pure read-only — does NOT clear the presence (use `peaks skill presence:clear` for that).')
         .option('--project <path>', 'project root (default: cwd)')
         .option('--current-outer <id>', 'override the current outer session id (test seam; default: read from PEAKS_OUTER_SESSION_ID / CLAUDE_CODE_SESSION_ID)')).action((options) => {
-        // v2.15.0 slice 002 repair: do NOT pass `currentOuter: undefined`
         // when the user omits the flag. The service-layer branch
         // `'currentOuter' in opts` returns true for an explicit
         // `undefined` (the key exists on the spread object literal),
@@ -498,7 +491,6 @@ export function registerSkillCommand(program, io) {
         }
         const result = checkStalePresence(checkOpts);
         // Always emit `currentOuterSessionId` in the JSON envelope (even
-        // when undefined → ''), per slice 002 AC-1 contract: downstream
         // tooling (statusline, sub-agent dispatch) reads the field by
         // name, never by `data.currentOuterSessionId ?? ''`. JSON.stringify
         // drops `undefined` properties, so we coerce to '' before
@@ -550,7 +542,6 @@ export function registerSkillCommand(program, io) {
         const result = detectPresenceMarker({ project: projectRoot, latestAssistantMessage: message });
         printResult(io, ok('skill.detect-marker-loss', result), options.json);
     });
-    // Slice S0 — register `peaks skill search`. Sibling subcommand to
     // list / runbook / presence; preserves the existing surface
     // (HC-10 — 老入口保留).
     registerSkillSearchCommand(program, io);

package/dist/cli/commands/core/standards-command.js

@@ -145,7 +145,7 @@ export function registerStandardsCommand(program, io) {
         .description('Rewrite a consumer project CLAUDE.md to drop the legacy heartbeat block (slice 028). Dry-run by default; pass --apply to write. With --from-claude-rules, thins the 1.x .claude/rules/ tree to 2-line pointers and scaffolds .peaks/standards/ (slice 2026-06-12-standards-migrate-claude-rules).')
         .option('--project <path>', 'target project root')
         .option('--apply', 'rewrite the legacy block in place; default is dry-run')
-        .option('--from-claude-rules', 'thin .claude/rules/ to pointers and scaffold .peaks/standards/ (used by `peaks upgrade --to 2.0`)')).action((options) => {
+        .option('--from-claude-rules', 'thin .claude/rules/ to pointers and scaffold .peaks/standards/')).action((options) => {
         const projectRoot = options.project ?? process.cwd();
         if (options.fromClaudeRules === true) {
             try {

package/dist/cli/commands/core-artifact-commands.d.ts

@@ -4,7 +4,6 @@ export type { DoctorLogsSection, BindingSource } from './core/doctor-command.js'
 /**
  * Top-level CLI command registrar for the "core + artifact" surface.
  *
- * Slice 2026-06-24-handoff-path-canonicalization split this orchestrator
  * out of a single 889-line file so each subcommand group lives in its
  * own module under `src/cli/commands/core/`. The orchestrator stays
  * thin (~this file) and forwards to the per-group registrars; the

package/dist/cli/commands/core-artifact-commands.js

@@ -10,7 +10,6 @@ import { registerStandardsCommand } from './core/standards-command.js';
 /**
  * Top-level CLI command registrar for the "core + artifact" surface.
  *
- * Slice 2026-06-24-handoff-path-canonicalization split this orchestrator
  * out of a single 889-line file so each subcommand group lives in its
  * own module under `src/cli/commands/core/`. The orchestrator stays
  * thin (~this file) and forwards to the per-group registrars; the

package/dist/cli/commands/cron-commands-actions.d.ts

@@ -17,7 +17,6 @@
  * throw, exit code, or emitted byte — and a new sibling must be clean outright.
  *
  * ONE thing has since been restructured, and it is not the verbatim move above:
- * rid `2026-10-01-cron-last-run-at-01` repair cycle 1 replaced `runCronTasks`'s
  * own fold-and-write (a `runTargets` that built the next file from the snapshot
  * read before the runs, stamping every record including killed ones) with the
  * scheduler's `persistLastRunAt`, so one rule and one write-time re-read cover

package/dist/cli/commands/cron-commands-actions.js

@@ -17,7 +17,6 @@
  * throw, exit code, or emitted byte — and a new sibling must be clean outright.
  *
  * ONE thing has since been restructured, and it is not the verbatim move above:
- * rid `2026-10-01-cron-last-run-at-01` repair cycle 1 replaced `runCronTasks`'s
  * own fold-and-write (a `runTargets` that built the next file from the snapshot
  * read before the runs, stamping every record including killed ones) with the
  * scheduler's `persistLastRunAt`, so one rule and one write-time re-read cover
@@ -100,7 +99,6 @@ function runCronTasks(io, options) {
         return;
     }
     const records = runTargets(projectRoot, targets);
-    // ONE rule, ONE writer (rid `2026-10-01-cron-last-run-at-01`, repair cycle 1).
     // This call is the third site of the `lastRunAt` fold, whose rule and platform
     // costs live in `cron-scheduler-persist.ts`. Two things it replaces: a fold that
     // stamped EVERY record, killed ones included (so the same killed fire went quiet

package/dist/cli/commands/cron-commands-schedule.d.ts

@@ -48,7 +48,6 @@ export type RunRecord = {
     /**
      * Present (and `true`) ONLY when the task was killed for exceeding its exec
      * timeout — i.e. when there is no child exit status behind `exitCode` and the
-     * work may have been mid-flight. Added by rid 2026-10-01-cron-task-tree-kill-01
      * so a killed run cannot be read as a clean `exitCode 1` failure.
      *
      * OPTIONAL on purpose: `appendHistory` is the only writer of
@@ -63,7 +62,6 @@ export declare function readSchedule(projectRoot: string): ScheduleFile;
 /**
  * The one "can this raw JSON entry be represented?" predicate. Exported because
  * a writer that must NOT lose an entry needs to know which ones the reader
- * dropped (rid `2026-10-01-cron-last-run-at-01`, repair cycle 1, F5 — see
  * `persistLastRunAt` in `cron-scheduler-persist.ts`).
  */
 export declare function toScheduleEntry(e: unknown): ScheduleEntry | null;
@@ -73,7 +71,6 @@ export declare function toScheduleEntry(e: unknown): ScheduleEntry | null;
  * `entries` is `ReadonlyArray<unknown>`, not `ReadonlyArray<ScheduleEntry>`, for one
  * caller: `persistLastRunAt` re-writes the raw JSON of entries `toScheduleEntry`
  * refused, so that a daemon write cannot delete an operator's hand-edited entry
- * (rid `2026-10-01-cron-last-run-at-01` repair cycle 1, F5). Every other caller
  * passes a `ScheduleFile`, which satisfies this shape.
  */
 export type ScheduleWrite = {

package/dist/cli/commands/cron-commands-schedule.js

@@ -76,7 +76,6 @@ function assertScheduleRoot(parsed) {
 /**
  * The one "can this raw JSON entry be represented?" predicate. Exported because
  * a writer that must NOT lose an entry needs to know which ones the reader
- * dropped (rid `2026-10-01-cron-last-run-at-01`, repair cycle 1, F5 — see
  * `persistLastRunAt` in `cron-scheduler-persist.ts`).
  */
 export function toScheduleEntry(e) {

package/dist/cli/commands/cron-commands.d.ts

@@ -1,5 +1,4 @@
 /**
- * `peaks cron` — slice 2026-07-29-worktree-l2-extended Part 14.
  *
  * Persistent scheduled-task system. Stores a JSON schedule at
  * `.peaks/cron/schedule.json` and lets the LLM-side runner

package/dist/cli/commands/cron-commands.js

@@ -1,5 +1,4 @@
 /**
- * `peaks cron` — slice 2026-07-29-worktree-l2-extended Part 14.
  *
  * Persistent scheduled-task system. Stores a JSON schedule at
  * `.peaks/cron/schedule.json` and lets the LLM-side runner
@@ -77,7 +76,6 @@ function truncateStderr(text) {
  * `exitCode 1 / "peaks-loop: internal module not found — the local build is
  * stale or incomplete"` on every fire. Measured in
  * `tests/unit/cli/commands/cron-task-tree-kill.test.ts` (F1, repair cycle 1 of
- * rid 2026-10-01-cron-task-tree-kill-01).
  */
 function isBootableTaskEntry(entry) {
     return existsSync(entry) && existsSync(resolve(dirname(entry), '..', 'dist', 'cli', 'index.js'));

package/dist/cli/commands/cron-scheduler-commands.d.ts

@@ -1,5 +1,4 @@
 /**
- * `peaks cron scheduler start|stop|status|run-once` — slice 2026-07-29 Part 15.
  *
  * Companion CLI to Part 14 (peaks cron init/list/run). The
  * scheduler is a long-running background daemon that wakes up

package/dist/cli/commands/cron-scheduler-commands.js

@@ -1,5 +1,4 @@
 /**
- * `peaks cron scheduler start|stop|status|run-once` — slice 2026-07-29 Part 15.
  *
  * Companion CLI to Part 14 (peaks cron init/list/run). The
  * scheduler is a long-running background daemon that wakes up

package/dist/cli/commands/cron-scheduler-persist.d.ts

@@ -1,5 +1,4 @@
 /**
- * The ONE writer of `lastRunAt` in this repo — rid `2026-10-01-cron-last-run-at-01`
  * (backlog §2.24), repair cycle 1 (review F1/F4/F5). Lives in its own file because
  * `cron-commands.ts` sits at 287 of its 300 raw-line cap and
  * `cron-scheduler-commands.ts` is already over its own; the rule below is small
@@ -23,7 +22,6 @@
  * invocations across 6 ticks** for one entry with `intervalMs` 86,400,000 at the
  * 60,000 ms daemon period — a 1440× rate error against the declared interval, and the
  * rate half of
- * `.peaks/docs/diagnosis-2026-10-01-worktree-list-population.md` §9. The same
  * test observes **1** once the write-back below runs.
  *
  * THE RULE (persist AFTER the run, from the record's `finishedAt`):
@@ -32,8 +30,6 @@
  *      exactly its own `intervalMs` and not one ms longer;
  *   2. a run carrying `killed: true` does NOT advance it, in EITHER entry point.
  *      Work cut off mid-flight is not a day's work, so the task stays due and is
- *      retried. What that costs is NOT uniform across platforms, and F3 of the
- *      review is the reason this paragraph is platform-shaped instead of global:
  *      - win32: the only fire shape that reaches `killed: true` here is the exec
  *        timeout (`cron-commands.ts:178-185`, spawnSync's `error.code ===
  *        'ETIMEDOUT'` branch), and that fire BLOCKS its caller for the whole
@@ -67,7 +63,6 @@
  *      running one…"); and entries `toScheduleEntry`
  *      (`cron-commands-schedule.ts:129-150`) REJECTS — a hand-edited entry missing
  *      `name`, say — are carried through as the raw JSON they were written as,
- *      appended after the parsed ones. F5 of the review: before this they were
  *      silently DELETED by the daemon's first write, which is data loss on a
  *      long-lived process nobody is watching. An unparseable entry with the same `id`
  *      as a parsed one is the one thing still dropped, because two entries under one

package/dist/cli/commands/cron-scheduler-persist.js

@@ -1,5 +1,4 @@
 /**
- * The ONE writer of `lastRunAt` in this repo — rid `2026-10-01-cron-last-run-at-01`
  * (backlog §2.24), repair cycle 1 (review F1/F4/F5). Lives in its own file because
  * `cron-commands.ts` sits at 287 of its 300 raw-line cap and
  * `cron-scheduler-commands.ts` is already over its own; the rule below is small
@@ -23,7 +22,6 @@
  * invocations across 6 ticks** for one entry with `intervalMs` 86,400,000 at the
  * 60,000 ms daemon period — a 1440× rate error against the declared interval, and the
  * rate half of
- * `.peaks/docs/diagnosis-2026-10-01-worktree-list-population.md` §9. The same
  * test observes **1** once the write-back below runs.
  *
  * THE RULE (persist AFTER the run, from the record's `finishedAt`):
@@ -32,8 +30,6 @@
  *      exactly its own `intervalMs` and not one ms longer;
  *   2. a run carrying `killed: true` does NOT advance it, in EITHER entry point.
  *      Work cut off mid-flight is not a day's work, so the task stays due and is
- *      retried. What that costs is NOT uniform across platforms, and F3 of the
- *      review is the reason this paragraph is platform-shaped instead of global:
  *      - win32: the only fire shape that reaches `killed: true` here is the exec
  *        timeout (`cron-commands.ts:178-185`, spawnSync's `error.code ===
  *        'ETIMEDOUT'` branch), and that fire BLOCKS its caller for the whole
@@ -67,7 +63,6 @@
  *      running one…"); and entries `toScheduleEntry`
  *      (`cron-commands-schedule.ts:129-150`) REJECTS — a hand-edited entry missing
  *      `name`, say — are carried through as the raw JSON they were written as,
- *      appended after the parsed ones. F5 of the review: before this they were
  *      silently DELETED by the daemon's first write, which is data loss on a
  *      long-lived process nobody is watching. An unparseable entry with the same `id`
  *      as a parsed one is the one thing still dropped, because two entries under one

package/dist/cli/commands/dashboard-summary.d.ts

@@ -1,5 +1,4 @@
 /**
- * rid-030 F-direction: `peaks dashboard summary --since <duration>`.
  *
  * Read-only 5-metric surface derived from raw observability events
  * (cycle / token / dispatch / compact / monotonic-trigger). Distinct

package/dist/cli/commands/dispatch-commands.d.ts

@@ -3,7 +3,6 @@ import { type ProgramIO } from '../cli-helpers.js';
 export declare function registerDispatchCommand(parent: Command, io: ProgramIO): void;
 /**
  * 2.7.0 slice-dag-dispatcher MVP — see `dispatch-from-dag.ts`.
- * The function was pulled out of this file in slice 2026-06-23-audit-3rd
  * #7 to honor the 800-line file cap and isolate the three heavy
  * module loads (slice-dag / dag-orchestrator / contract-store) to the
  * --from-dag codepath only.