peaks-loop 4.1.0 → 4.1.2

package/dist/services/code/auto-compact-modes.js

@@ -1,12 +1,10 @@
 /**
- * Slice 2026-07-28 — auto-compact mode table for 24h long-run awareness.
  *
  * The default `'standard'` mode preserves the v2.13.0 zero-pause contract
  * thresholds (autoFire=0.80, preCompact=0.85, redLine=0.95). The `'partial'`
  * mode fires earlier for 24h long-run scenarios where the user has explicitly
  * opted into higher compaction cadence via `peaks session 24h-mode`.
  *
- * Slice 2026-07-29-context-evaluation-accuracy Part 22: a new
  * `autoFire` tier is added between soft-warn and preCompact. peaks-loop
  * preempts and runs `peaks code auto-compact` itself when
  * context crosses `autoFire`; the LLM is NOT asked to "decide"
@@ -37,7 +35,6 @@ function pct(ratio) {
  * Derived from `AUTO_COMPACT_THRESHOLDS` rather than hand-written. Diagnosis
  * 2026-09-15 (C1) found this string advertising `0.85/0.95` for `standard`
  * while the table had auto-fired at `0.80` since slice
- * 2026-07-29-context-evaluation-accuracy added the `autoFire` tier — the
  * description named only the two thresholds that were left over from the
  * v2.13.0 contract, and skipped the one that actually fires. Reading the
  * numbers out of the table makes that drift unrepresentable.

package/dist/services/code/auto-compact-orchestrator.d.ts

@@ -39,7 +39,6 @@ export interface AutoCompactInput {
      *
      * Why nothing reads it any more: it used to skip a gate that refused to
      * dispatch below 0.85. That gate was removed (slice
-     * 2026-09-13-auto-compact-trigger-ownership, T3/A1) — peaks-loop cannot
      * compact a running session, so the refusal could not shorten the wait it
      * was waiting for, and it deadlocked the runner at the worst moment. With the
      * gate gone, the red line still ASKS the harness to compact (when it always
@@ -54,7 +53,6 @@ export interface AutoCompactInput {
     /** Injectable clock for mtime checks (test seam). */
     readonly now?: Date | undefined;
     /**
-     * Slice 2026-06-28-code-mode-bypass-fix (defect #4): which session
      * the compact should target. Default `'main'` — the orchestrator
      * (peaks-code body) runs in the main-session Claude Code window and
      * wants to compress *its* context. Sub-agent shells pass
@@ -62,14 +60,12 @@ export interface AutoCompactInput {
      */
     readonly target?: CompactTarget | undefined;
     /**
-     * Slice 2026-07-28 (rid-027): auto-compact mode. Default
      * `'standard'` (v2.13.0 zero-pause contract, 0.85/0.95). `'partial'`
      * fires earlier (0.70/0.85) for 24h long-run scenarios. CLI flag
      * `--mode <mode>` overrides the 24h-mode auto-detection.
      */
     readonly mode?: AutoCompactMode | undefined;
     /**
-     * Slice 2026-08-01-compact-lifecycle (Task 5): observer fired on
      * every lifecycle stage this process actually proved. Telemetry
      * only — it can neither change the threshold decision nor the
      * dispatch outcome, and a throwing observer is swallowed.
@@ -109,7 +105,6 @@ export interface AutoCompactTestHooks {
  *   - ratio ≥ preCompact → 'pre-compact' (async-friendly path)
  *   - ratio ≥ redLine    → 'red-line' (ask the harness; dispatch continues)
  *
- * Slice 2026-07-28 (rid-027): `mode` selects the threshold table.
  * Default `'standard'` (0.85/0.95). `'partial'` (0.70/0.85) is used
  * when 24h long-run mode is active or `--mode partial` is passed.
  */
@@ -126,7 +121,6 @@ export declare function evaluateCompactTrigger(ratio: number, mode?: AutoCompact
  *   - ratio ≥ 0.95           → red-line; ask the harness to compact
  *                                regardless of in-flight batch. Nothing is
  *                                gated — dispatch is NOT blocked (slice
- *                                2026-09-13-auto-compact-trigger-ownership:
  *                                peaks-loop cannot compact a running session,
  *                                so a "block" gated nothing and deadlocked the
  *                                runner).
@@ -184,7 +178,6 @@ export declare function buildConvergencePlan(input: {
  *
  * Steps (orchestration):
  *   1. Resolve session id.
- *   2. Read current ratio via AC-1 (`readContextPercent`).
  *   3. Evaluate trigger via `evaluateCompactTrigger`.
  *   4. If trigger.kind === 'none' / 'soft-warn' → return skip.
  *   5. If trigger.kind === 'pre-compact' AND in-flight batch → wait.
@@ -203,7 +196,6 @@ export declare function runAutoCompact(input: AutoCompactInput): Promise<AutoCom
 /** Re-export for callers that need to surface the trigger shape. */
 export type { CompactTrigger, ConvergencePlan, InFlightBatchProbe, AutoCompactResult };
 /**
- * Slice 2026-07-30-compact-visibility: JSONL history of every
  * auto-compact dispatch. Appended at the end of `executeAutoCompact`
  * so the new 'peaks compact history' CLI + the
  * 'peaks statusline compact' indicator have a record. One file
@@ -222,7 +214,6 @@ export interface CompactHistoryEvent {
     readonly checkpointPath: string;
     readonly dispatchMessage: string;
     /**
-     * Slice 2026-09-13-auto-compact-trigger-ownership (T4): the calibration
      * instrument. `windowTokens` is the denominator peaks-loop divided by
      * (`probe.capacityTokens`), so `beforeRatio * windowTokens` is the exact
      * TOKEN POINT peaks-loop asked the harness to compact at. That number is

package/dist/services/code/auto-compact-orchestrator.js

@@ -1,8 +1,5 @@
 /**
- * Auto-compact orchestrator (v2.13.0 AC-2 + AC-3 + AC-4).
  *
- * Closes the loop between `peaks code auto-compact` (AC-1) and the IDE's
- * native compact capability (AC-3). peaks-loop is project-aware: it
  * knows the current plan, open questions, recent decisions, in-flight
  * batches, todo state, git status, and active skills. That context is
  * strictly more valuable than what `/compact` can synthesize from raw
@@ -12,7 +9,6 @@
  *   2. If ratio ≥ 0.95 (RED LINE): peaks-loop ASKS the harness to
  *      compact and reports that it is waiting. It does NOT block
  *      sub-agent dispatch (slice
- *      2026-09-13-auto-compact-trigger-ownership, T3): peaks-loop owns
  *      the *decision*, the harness owns the *capability*, and peaks-loop
  *      has no way to compact a running session itself — so a "gate"
  *      here gated nothing and deadlocked the runner at the worst
@@ -54,7 +50,6 @@ const PRE_COMPACT_REASON = 'pre-compact-auto';
  *   - ratio ≥ preCompact → 'pre-compact' (async-friendly path)
  *   - ratio ≥ redLine    → 'red-line' (ask the harness; dispatch continues)
  *
- * Slice 2026-07-28 (rid-027): `mode` selects the threshold table.
  * Default `'standard'` (0.85/0.95). `'partial'` (0.70/0.85) is used
  * when 24h long-run mode is active or `--mode partial` is passed.
  */
@@ -72,7 +67,6 @@ export function evaluateCompactTrigger(ratio, mode = 'standard') {
             };
     }
     if (ratio >= redLine) {
-        // Slice 2026-09-13-auto-compact-trigger-ownership (T3): the red line no
         // longer claims it blocks anything. It cannot: peaks-loop has no
         // executor for a running session (no `/compact` the model may invoke, no
         // hook-initiated compact, no `--compact` flag), so "refuse dispatch until
@@ -122,7 +116,6 @@ export function evaluateCompactTrigger(ratio, mode = 'standard') {
  *   - ratio ≥ 0.95           → red-line; ask the harness to compact
  *                                regardless of in-flight batch. Nothing is
  *                                gated — dispatch is NOT blocked (slice
- *                                2026-09-13-auto-compact-trigger-ownership:
  *                                peaks-loop cannot compact a running session,
  *                                so a "block" gated nothing and deadlocked the
  *                                runner).
@@ -154,7 +147,6 @@ export function evaluateAutoCompactDecision(input) {
     if (input.force) {
         return { shouldCompact: true, reason: 'pre-compact', trigger, action: 'auto-compact-now' };
     }
-    // Slice 2026-07-31-rid-mac-transcript-estimate-trigger: transcript-estimate
     // is the ONLY signal available on Mac Claude Code (no env-var, no statusline
     // poll). The gate above already returns shouldCompact: true at ratio ≥ 0.85,
     // but this forward-compat carve-out makes the source-aware rule explicit so
@@ -218,7 +210,6 @@ function appendAutoDecisionLog(input) {
     writeFileSync(logPath, `${existing}${row}`, 'utf8');
 }
 /**
- * Slice 2026-06-28-code-mode-bypass-fix (defect #4): write the
  * main-session compact intent so the main-session LLM picks it up on
  * its next turn and fires `/compact` in-band. Without this file the
  * orchestrator's "main-session compact" request is invisible to the
@@ -229,7 +220,6 @@ function appendAutoDecisionLog(input) {
  * is one-shot: the LLM should `mv` it to `.consumed` after firing
  * `/compact`. A re-run will overwrite.
  *
- * ZERO READERS as of slice 2026-09-13-auto-compact-trigger-ownership: the
  * write survives, but nothing consumes the file, and its `nextAction` asks
  * for a `/compact` the model cannot invoke (the Skill tool exposes only
  * `/init` and `/security-review`; hooks can observe or veto, never initiate).
@@ -291,8 +281,6 @@ function writePreCompactCheckpoint(input) {
     return path;
 }
 /**
- * Slice 2026-07-28 (rid-027), re-keyed by slice
- * 2026-09-09-mode-consolidation: resolve the auto-compact mode from
  * the PRESENCE MODE, not the 24h state machine. Returns `'partial'`
  * when the mode is `24h`, otherwise `'standard'`. The CLI flag
  * `--mode` takes precedence (caller passes `input.mode` directly), so
@@ -306,7 +294,6 @@ function resolveAutoCompactMode(projectRoot) {
  *
  * Steps (orchestration):
  *   1. Resolve session id.
- *   2. Read current ratio via AC-1 (`readContextPercent`).
  *   3. Evaluate trigger via `evaluateCompactTrigger`.
  *   4. If trigger.kind === 'none' / 'soft-warn' → return skip.
  *   5. If trigger.kind === 'pre-compact' AND in-flight batch → wait.
@@ -331,12 +318,9 @@ export async function runAutoCompact(input) {
             nextActions: ['Run `peaks workspace init --change-id <id>` to bind a session']
         };
     }
-    // Slice 2026-07-28 (rid-027): resolve mode. CLI flag `--mode` wins;
-    // slice 2026-09-09-mode-consolidation keys the default off the
     // presence MODE ('24h' → 'partial'); 'standard' preserves the
     // v2.13.0 zero-pause contract.
     const mode = input.mode ?? resolveAutoCompactMode(input.projectRoot);
-    // Lazy import to avoid the AC-1 module depending on the orchestrator.
     const { readContextPercent, syncHarnessWindowForProject } = await import('../context/auto-compact-reader.js');
     const outerSessionId = resolveOuterSessionId(input.projectRoot, sessionId, input.env ?? process.env);
     const probe = readContextPercent({
@@ -345,7 +329,6 @@ export async function runAutoCompact(input) {
         outerSessionId,
         env: input.env
     });
-    // Slice 2026-09-13-auto-compact-trigger-ownership (T1 + T2): write the very
     // denominator this probe divided by into the harness's own machine-local
     // settings, so "peaks-loop's 85%" and "the harness's trigger" are the same
     // point on one scale. Idempotent — an unchanged value performs no write, so
@@ -376,13 +359,11 @@ export async function runAutoCompact(input) {
         force: input.force,
         bypassRedLine: input.bypassRedLine,
         mode,
-        // Slice 2026-07-31-rid-mac-transcript-estimate-trigger: pipe the source
         // tag through so `evaluateAutoCompactDecision` can apply the
         // source-aware carve-out for Mac's `transcript-estimate` signal.
         source: probe.source
     });
     if (!decision.shouldCompact) {
-        // Slice 2026-08-01-compact-lifecycle (Task 5): this probe IS the
         // adapter's `postCompactDetectCommand`. A ratio that has fallen
         // back below the auto-fire threshold is the real, measured proof
         // that a previously-dispatched compact landed — so settle any run
@@ -409,7 +390,6 @@ export async function runAutoCompact(input) {
         const settled = settleRead !== null && !settleRead.lifecycleWritten
             ? null
             : (settleRead ??
-                // Repair R1 (`2026-09-13-compact-event-settle`): the HARNESS event may
                 // already have closed this run WITHOUT an honest post-compact number —
                 // in which case the call above finds nothing open, and without this the
                 // calibration pair stays blank for exactly the compactions the event path
@@ -420,7 +400,6 @@ export async function runAutoCompact(input) {
                     measuredRatio: probe.ratio,
                     source: probe.source
                 }));
-        // Slice 2026-09-13-auto-compact-trigger-ownership (T4): a settle means a
         // dispatched compact demonstrably landed. Append an `observed` row
         // carrying the measured ratio, so `peaks compact history` can show
         // "asked at R (intent) / landed by R' (observed)" once a real session has
@@ -480,7 +459,6 @@ export async function runAutoCompact(input) {
     }
     const isRedLine = decision.reason === 'red-line';
     const now = input.now ?? new Date();
-    // rid `2026-09-14-compact-dispatch-backoff`: ONE dispatch per compact
     // attempt.
     //
     // The decision above fires whenever the ratio is at or over the auto-fire
@@ -512,7 +490,6 @@ export async function runAutoCompact(input) {
     // Repair R6: `readOpenDispatchRun` answers in THREE states, not two. `none`
     // admits the dispatch; `unresolvable` means the backoff's question could not
     // be asked — the session id names no session directory, so no lifecycle
-    // record can exist under it and the gate used to read that as "nothing is
     // outstanding". Measured on ONE directory before this: a legal sid found the
     // open `armed` run and suppressed the dispatch; `./<legal sid>`, which joins
     // to the identical path, returned `null` and dispatched. A gate that reads a
@@ -559,7 +536,6 @@ export async function runAutoCompact(input) {
             }
         };
     }
-    // Slice 2026-08-01-compact-lifecycle (Task 5): the decision has now
     // committed to compacting, so the run is `queued`. One runId per
     // attempt; every later transition carries it forward.
     const lifecycle = new CompactLifecyclePublisher({
@@ -591,7 +567,6 @@ export async function runAutoCompact(input) {
                 'RED-LINE: harness compact requested — sub-agent dispatch is NOT blocked; keep working',
                 'Post-compact resume picks up the convergence plan from auto-decisions.md',
                 'Next `peaks code context-now` probe will confirm the ratio dropped; if it keeps climbing and the harness has not compacted, report that to the user and hand control back',
-                // Slice 2026-09-13-auto-compact-trigger-ownership: this command
                 // also rewrites the harness's own settings, so it says so too. The
                 // user accepted that write on the condition 要告知 — a write only
                 // one of the two syncing commands reports is not a notice.
@@ -639,14 +614,12 @@ export async function runAutoCompact(input) {
             }
         };
     }
-    // Lazy import to keep AC-3 (IDE dispatch) pluggable; tests mock this module.
     const { dispatchIdeCompact } = await import('../context/auto-compact-dispatcher.js');
     const target = input.target ?? 'main';
     let dispatch;
     try {
         if (input.testHooks?.failCompacting)
             throw new Error('IDE dispatch exploded');
-        // Slice 2026-06-28: when targeting the main session, write an
         // intent record so the next main-session LLM turn fires `/compact`
         // in-band. Without this record the LLM has no signal that the
         // orchestrator asked for compact; the dispatcher alone would have
@@ -690,7 +663,6 @@ export async function runAutoCompact(input) {
             }
         };
     }
-    // Slice 2026-09-12-compact-band-policy (defect B): the stage is
     // chosen from what the dispatch ACTUALLY did, never from the hope
     // that it compacted. `ide-native` on claude-code only installs a
     // PreToolUse hook that fires at ratio ≥ 0.95 — below that nothing is
@@ -707,7 +679,6 @@ export async function runAutoCompact(input) {
         // run looking like it is still in progress.
         lifecycle.fail(new Error(dispatch.message), 'compacting');
     }
-    // Slice 2026-07-30-compact-visibility: append a compact-history
     // event so the new 'peaks compact history' CLI and the
     // 'peaks statusline compact' indicator have a record. The
     // append is best-effort: a write failure must NOT block the

package/dist/services/code/batch-heartbeat-poller.js

@@ -8,7 +8,6 @@
  *   - a `dispatcherStatus` envelope to the renderer's `onStatus` callback
  *     (which formats the single-line status per G6.5)
  *   - a `stale` envelope to `onStale` if a record crosses the 5-min
- *     threshold (G6.2 / AC-35)
  *
  * The poller does **not**:
  *   - cancel, kill, or send SIGTERM to a sub-agent (RL-15)

package/dist/services/code/compact-event-settle.js

@@ -1,5 +1,4 @@
 /**
- * rid `2026-09-13-compact-event-settle` — what runs when the HARNESS says a
  * compaction completed.
  *
  * THE PROBLEM THIS EXISTS TO DELETE. Before this slice peaks-loop learned that

package/dist/services/code/dag-orchestrator.d.ts

@@ -54,7 +54,6 @@ export interface RunDagOptions {
      * Pre-existing contracts from upstream slices (e.g. already completed in
      * a prior `peaks sub-agent dispatch --from-dag` invocation). The
      * orchestrator splices these into downstream dispatch prompts via
-     * `formatContractInjection(ancestors)` — matching AC-4.c: "B / C / D
      * dispatch prompt 自动注入 A 契约".
      */
     readonly existingContracts?: readonly SliceContract[];

package/dist/services/code/dag-orchestrator.js

@@ -309,7 +309,6 @@ export async function runLayeredDag(dag, opts) {
     };
 }
 /* ──────────────────────────────────────────────────────────────────────────
- * Slice 2026-07-28 — DAG wave + barrier (rid-029 E direction).
  *
  * The original `runDag` + `runLayeredDag` above dispatch an ENTIRE
  * topological level in one `Promise.all` burst. For 24-hour scenarios

package/dist/services/code/mode-gate-types.d.ts

@@ -21,10 +21,9 @@ export declare const CODE_MODES: readonly CodeMode[];
  * "Inventory of unconditional confirmation gates" table. Each row
  * is the bare minimum needed to gate it through `shouldPauseAtGate`.
  */
-export type GatedStepId = 'step-0.5-openspec-opt-in' | 'step-0.6-audit-goal' | 'step-0.7-resume-detection' | 'step-0.55-1x-upgrade' | 'step-1-mode-select' | 'step-2.5-session-title' | 'phase-2-prd-confirm' | 'phase-3-swarm-gate-b' | 'phase-6-qa-gate-d' | 'phase-10-txt-memory-extract' | 'step-n+1-final-review' | 'frontend-only-mismatch' | 'step-0.75-checkpoint-resume' | 'standards-preflight';
+export type GatedStepId = 'step-0.5-openspec-opt-in' | 'step-0.6-audit-goal' | 'step-0.7-resume-detection' | 'step-1-mode-select' | 'step-2.5-session-title' | 'phase-2-prd-confirm' | 'phase-3-swarm-gate-b' | 'phase-6-qa-gate-d' | 'phase-10-txt-memory-extract' | 'step-n+1-final-review' | 'frontend-only-mismatch' | 'step-0.75-checkpoint-resume' | 'standards-preflight';
 export declare const GATED_STEPS: readonly GatedStepId[];
 /**
- * v2.15.0 slice 002 AC-4: the 5 action identifiers that qualify as
  * commit-boundary side effects. Matched by the LLM-side caller
  * (peaks-code body / peaks-rd fork agent) when it is about to run a
  * Bash command that maps to one of these. Set `commitBoundaryAction:
@@ -34,7 +33,6 @@ export declare const GATED_STEPS: readonly GatedStepId[];
 export type CommitBoundaryActionId = 'git-push' | 'git-tag' | 'npm-publish' | 'npm-install-global' | 'peaks-global-install';
 export declare const COMMIT_BOUNDARY_ACTIONS: readonly CommitBoundaryActionId[];
 /**
- * v2.15.0 slice 002 AC-4: regex matchers the LLM-side caller uses
  * to flag a Bash command as a commit-boundary action. Centralised
  * here so the test seam + the CLI wiring share one source of
  * truth. Each entry is an anchored pattern matched against the

package/dist/services/code/mode-gate-types.js

@@ -18,7 +18,6 @@ export const GATED_STEPS = [
     'step-0.5-openspec-opt-in',
     'step-0.6-audit-goal',
     'step-0.7-resume-detection',
-    'step-0.55-1x-upgrade',
     'step-1-mode-select',
     'step-2.5-session-title',
     'phase-2-prd-confirm',
@@ -38,7 +37,6 @@ export const COMMIT_BOUNDARY_ACTIONS = [
     'peaks-global-install'
 ];
 /**
- * v2.15.0 slice 002 AC-4: regex matchers the LLM-side caller uses
  * to flag a Bash command as a commit-boundary action. Centralised
  * here so the test seam + the CLI wiring share one source of
  * truth. Each entry is an anchored pattern matched against the

package/dist/services/code/mode-gate.d.ts

@@ -24,7 +24,6 @@ export { CODE_MODES, COMMIT_BOUNDARY_ACTIONS, COMMIT_BOUNDARY_PATTERNS, GATED_ST
 export type { CodeMode, CommitBoundaryActionId, GatedStepId } from './mode-gate-types.js';
 export type HardFloorCategory = 'irreversible-external-side-effect' | 'authentication-credential' | 'multi-day-investment'
 /**
- * v2.15.0 slice 002 AC-4: actions that are past the user's
  * explicit full-auto boundary = commit only. Per user-given rule
  * from `.peaks/memory/2026-06-28-full-auto-boundary.md`: full-auto
  * ends at commit. push / tag / npm publish / global install are
@@ -35,7 +34,6 @@ export type HardFloorCategory = 'irreversible-external-side-effect' | 'authentic
  | 'commit-boundary-side-effect';
 export declare const HARD_FLOOR_CATEGORIES: readonly HardFloorCategory[];
 /**
- * Slice 2026-06-28-code-mode-bypass-fix: the kind of gate that
  * produced this decision. The LLM-side caller (peaks-code body) reads
  * this to distinguish "you paused because the user must choose the
  * mode" (`mode-selection-itself`) from "you paused because the mode
@@ -73,7 +71,6 @@ export declare function isCommitBoundaryAction(value: string): value is CommitBo
  * AskUserQuestion round-trip). Mirrors D5.a: "recommended = chosen
  * in full-auto / 24h; always log, never silently skip".
  *
- * Slice 2026-09-09-mode-consolidation: `swarm` was removed as a mode
  * (parallel fan-out is now the default execution strategy in every
  * mode); `24h` replaces it as the second auto-proceed peer.
  */
@@ -83,7 +80,6 @@ export declare function shouldPauseAtGate(opts: {
     step: GatedStepId;
     hardFloorCategory?: HardFloorCategory | undefined;
     /**
-     * v2.15.0 slice 002 AC-4: when `true`, force a pause regardless of
      * mode. Reserved for the 5 commit-boundary side effects
      * (push/tag/publish/global install) that are past the user's
      * full-auto boundary. The hard-floor override ALWAYS wins — even
@@ -103,7 +99,6 @@ export declare function formatAutoProceedLogLine(opts: {
     hardFloorCategory?: HardFloorCategory | undefined;
 }): string;
 /**
- * v2.15.0 slice 002 AC-4: detect whether a Bash command matches any
  * commit-boundary action pattern. Returns the action id of the
  * first match, or `null` when none match. The CLI / LLM caller
  * passes the command through this function and forwards the

package/dist/services/code/mode-gate.js

@@ -45,7 +45,6 @@ export function isCommitBoundaryAction(value) {
  * AskUserQuestion round-trip). Mirrors D5.a: "recommended = chosen
  * in full-auto / 24h; always log, never silently skip".
  *
- * Slice 2026-09-09-mode-consolidation: `swarm` was removed as a mode
  * (parallel fan-out is now the default execution strategy in every
  * mode); `24h` replaces it as the second auto-proceed peer.
  */
@@ -61,7 +60,6 @@ export function shouldAutoProceed(mode) {
  * The hard-floor categories always win — even full-auto pauses for
  * irreversible external side effects, auth/credential usage,
  * multi-day investment decisions (D5.b), and commit-boundary side
- * effects (v2.15.0 slice 002 AC-4: push, tag, publish, global install).
  *
  * `hardFloorCategory` is optional on the `GateDecision` so callers can
  * stamp the override into the auto-decisions log without a second
@@ -74,19 +72,11 @@ export function shouldAutoProceed(mode) {
  * without user consent (defect #1: new Code session skipped Step 1
  * AskUserQuestion because `full-auto` mode triggered `shouldAutoProceed`
  * on `step-1-mode-select` itself).
- *
- * v2.18.4 slice 002-fix-first-run-step-gates: added
- * `step-0.55-1x-upgrade`. The 1.x → 2.0 upgrade is an irreversible
- * external side effect (migration rewrites config files and the
- * on-disk cache shape) — it must always pause, even in full-auto.
- * Without this, `full-auto` mode auto-proceeds and silently
- * downgrades a 1.x install to 2.0 without user consent.
  */
 const HARD_PAUSE_STEPS = new Set([
     'step-1-mode-select',
     'step-0.5-openspec-opt-in',
-    'step-0.7-resume-detection',
-    'step-0.55-1x-upgrade'
+    'step-0.7-resume-detection'
 ]);
 export function shouldPauseAtGate(opts) {
     if (opts.hardFloorCategory !== undefined && isHardFloorCategory(opts.hardFloorCategory)) {
@@ -97,7 +87,6 @@ export function shouldPauseAtGate(opts) {
             gateKind: 'hard-floor'
         };
     }
-    // Slice 002 (v2.15.0) AC-4: commit-boundary side effects override
     // every other decision. Per the user-given rule in
     // `.peaks/memory/2026-06-28-full-auto-boundary.md` ("full-auto 只
     // 做到 commit"), push / tag / npm publish / global install must
@@ -111,7 +100,6 @@ export function shouldPauseAtGate(opts) {
             gateKind: 'hard-floor'
         };
     }
-    // Slice 2026-06-28-code-mode-bypass-fix: hard-pause steps that
     // determine the active mode or session context MUST prompt the
     // user. Otherwise full-auto silently locks in `mode=full-auto` on
     // the first tool call, skipping the AskUserQuestion Step 1 mandates.
@@ -147,7 +135,6 @@ export function formatAutoProceedLogLine(opts) {
     return `auto-proceed (${opts.mode}): ${opts.step} → ${opts.recommendedOption}`;
 }
 /**
- * v2.15.0 slice 002 AC-4: detect whether a Bash command matches any
  * commit-boundary action pattern. Returns the action id of the
  * first match, or `null` when none match. The CLI / LLM caller
  * passes the command through this function and forwards the

package/dist/services/code/orchestrator-can-do-advisories.d.ts

@@ -7,9 +7,7 @@
  * strings below are the probe's wire contract, consumed by skill prose and by
  * the `pre-tool-code-gate` hook contract.
  */
-/** Slice 2026-08-05-orchestrator-can-do-probe: red-line threshold. */
 export declare const ORCHESTRATOR_REDLINE_RATIO = 0.95;
-/** Slice 2026-08-05-orchestrator-can-do-probe: pre-compact threshold. */
 export declare const ORCHESTRATOR_PRECOMPACT_RATIO = 0.85;
 /** The four Q signals that produce blockers / warnings / suggestions here. */
 export interface BoundarySignals {

package/dist/services/code/orchestrator-can-do-advisories.js

@@ -7,9 +7,7 @@
  * strings below are the probe's wire contract, consumed by skill prose and by
  * the `pre-tool-code-gate` hook contract.
  */
-/** Slice 2026-08-05-orchestrator-can-do-probe: red-line threshold. */
 export const ORCHESTRATOR_REDLINE_RATIO = 0.95;
-/** Slice 2026-08-05-orchestrator-can-do-probe: pre-compact threshold. */
 export const ORCHESTRATOR_PRECOMPACT_RATIO = 0.85;
 /**
  * Build the blockers / warnings / suggestions carried by Q1 (hard), Q2, Q4 and
@@ -19,7 +17,6 @@ export function boundaryAdvisories(signals) {
     const blockers = [];
     const warnings = [];
     const suggestions = [];
-    // Slice 2026-08-06-codegate-vendor-neutral — Q1 HARD BLOCKER. When
     // the slice-spec mentions any hard-blocked path family
     // (src/, tests/unit/, tests/integration/, config/, bin/, scripts/),
     // the orchestrator MUST refuse direct execution and force sub-agent
@@ -36,13 +33,11 @@ export function boundaryAdvisories(signals) {
         suggestions.push('verify peaks CLI is on PATH; check `peaks --version`');
     }
     // Q4 — context ratio. ≥0.95 → red-line; ≥0.85 → pre-compact. A WARNING, not
-    // a blocker, and the difference is deliberate (E3, rid 2026-09-13-defects-e).
     //
     // Why this is not a blocker any more, and why it is not an oversight:
     //
     //   The peak this answers is "can this slice run in the current session".
     //   Context ratio cannot answer "no" to it. The reason is the one the
-    //   T3 slice (2026-09-13-auto-compact-trigger-ownership) landed on the
     //   OTHER face of this same threshold: peaks-loop has no executor for a
     //   running session, so it cannot compact its way out of a high ratio —
     //   `evaluateCompactTrigger` therefore says of the red line "peaks-loop has

package/dist/services/code/orchestrator-can-do.d.ts

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-08-05-orchestrator-can-do-probe — service layer for
  * `peaks code orchestrator-can-do`.
  *
  * Encodes the 2026-08-05 lesson (`.peaks/memory/2026-08-05-peaks-code-
@@ -48,7 +47,6 @@ export type { ContextProbe };
 /** Source-code keywords that signal "do NOT Edit/Write directly". */
 export declare const SOURCE_CODE_KEYWORDS: readonly string[];
 /**
- * Slice 2026-08-06-codegate-vendor-neutral — hard-blocked path families.
  * When ANY of these substrings appears in the slice-spec, the orchestrator
  * MUST NOT Edit/Write directly; the probe returns `canDoInSession: false`
  * with `blockers: ["requires-sub-agent-dispatch"]` to force
@@ -83,7 +81,6 @@ export interface OrchestratorCanDoResult {
     readonly subAgentAvailable: boolean;
     /** Diagnostic — which of the 4 boundary questions fired. */
     readonly q1SourceCodeTouched: boolean;
-    /** Slice 2026-08-06-codegate-vendor-neutral: did the slice-spec mention a hard-blocked path family (src/, tests/unit/, ...)? When true the probe refuses direct execution. */
     readonly q1HardBlockedPath: boolean;
     readonly q2SubAgentAvailable: boolean;
     readonly q3RequiresUserDecision: boolean;
@@ -99,7 +96,6 @@ export declare class OrchestratorCanDoError extends Error {
  */
 export declare function detectSourceCodeTouched(sliceSpec: string): boolean;
 /**
- * Slice 2026-08-06-codegate-vendor-neutral — does the slice-spec mention
  * any hard-blocked path family? Pure substring match. When true, the
  * probe returns `canDoInSession: false` with `requires-sub-agent-dispatch`.
  * This is the LLM-side complement to the `pre-tool-code-gate.sh` hook

package/dist/services/code/orchestrator-can-do.js

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-08-05-orchestrator-can-do-probe — service layer for
  * `peaks code orchestrator-can-do`.
  *
  * Encodes the 2026-08-05 lesson (`.peaks/memory/2026-08-05-peaks-code-
@@ -65,7 +64,6 @@ export const SOURCE_CODE_KEYWORDS = [
     '.rs'
 ];
 /**
- * Slice 2026-08-06-codegate-vendor-neutral — hard-blocked path families.
  * When ANY of these substrings appears in the slice-spec, the orchestrator
  * MUST NOT Edit/Write directly; the probe returns `canDoInSession: false`
  * with `blockers: ["requires-sub-agent-dispatch"]` to force
@@ -112,7 +110,6 @@ export function detectSourceCodeTouched(sliceSpec) {
     return SOURCE_CODE_KEYWORDS.some((kw) => lower.includes(kw.toLowerCase()));
 }
 /**
- * Slice 2026-08-06-codegate-vendor-neutral — does the slice-spec mention
  * any hard-blocked path family? Pure substring match. When true, the
  * probe returns `canDoInSession: false` with `requires-sub-agent-dispatch`.
  * This is the LLM-side complement to the `pre-tool-code-gate.sh` hook

package/dist/services/code/status-line-renderer.js

@@ -61,7 +61,6 @@ function renderOne(record, now) {
     const view = viewSubAgent(record, now);
     const pct = view.progress !== null ? `${view.progress}%` : '?%';
     const ago = view.lastBeatAgoSec !== null ? `${view.lastBeatAgoSec}s ago` : 'no beat';
-    // Slice 2026-07-29-dispatch-stall-governance / S2 (AC-2.3) — render
     // never-started distinctly from stale so the orchestrator's eye can
     // tell a sub-agent that never picked up the work apart from one that
     // has gone quiet after starting.

package/dist/services/code/user-touchpoint-classifier.js

@@ -42,13 +42,6 @@ const RAW_CLASSIFICATION = [
         fullAutoCanProceed: false,
         userShouldReview: 'always'
     },
-    {
-        step: 'step-0.55-1x-upgrade',
-        kind: 'commit-floor',
-        description: '1.x → 2.0 升级检测。不可逆外部副作用(改写 config + cache schema),所有 mode 都必须 AskUserQuestion。full-auto 也暂停。',
-        fullAutoCanProceed: false,
-        userShouldReview: 'always'
-    },
     {
         step: 'step-0.75-checkpoint-resume',
         kind: 'tech',

package/dist/services/code-review/ecc-bridge.d.ts

@@ -21,12 +21,12 @@
  *
  * === Why no `peaksConfig.ecc.*` block ===
  *
- * ECC is shipped via the `everything-claude-code` plugin, not as a
- * separate npm package. The user installs the plugin (a one-time
- * marketplace step); peaks-loop does not write or read any LLM
- * endpoint config for ECC. If a future ECC release needs user-
- * managed config (URL / token / model), add a `peaksConfig.ecc.*`
- * block then — not speculatively now.
+ * ECC ships as the `ecc-universal` npm package — the same repository as
+ * github.com/affaan-m/ECC — and peaks-loop depends on it, so the agents are read
+ * from that dependency, not downloaded. ECC may ALSO be present as the
+ * `everything-claude-code` Claude Code plugin, the native path `detectEcc`
+ * prefers. Either way peaks-loop writes and reads no LLM endpoint config for ECC;
+ * add a `peaksConfig.ecc.*` block only when a release actually needs one.
  *
  * === Source: peaks-rd/references/parallel-review-fanout.md ===
  *
@@ -81,7 +81,6 @@ export declare const DEFAULT_NATIVE_ECC_AGENT_ID = "ecc:code-reviewer";
  *   - `dispatch-failed`     — Agent tool call threw before returning envelope
  *   - `envelope-malformed`  — returned value failed `isEccEnvelope` validation
  *
- * Fallback order (RD fan-out, 2026-09-09-ecc-dynamic): native plugin →
  * cache-backed generic agent → inline. The caller (peaks-rd's sub-agent 1
  * contract) inspects `state` and either proceeds with the envelope or records
  * a degradation note in the request artifact body

package/dist/services/codegraph/codegraph-autorefresh.js

@@ -1,6 +1,5 @@
 // src/services/codegraph/codegraph-autorefresh.ts
 //
-// Slice 2026-09-03-codegraph-autorefresh — Option 1: CLI-internal
 // auto codegraph refresh at the slice-complete boundary.
 //
 // `peaks codegraph index` is incremental + idempotent, so re-running it
@@ -29,7 +28,6 @@
 //     human-readable note.
 //   - Any unexpected error → return `unavailable` with a note.
 //
-// A2 (`2026-09-17-codegraph-msg-and-refresh`). The old header said
 // "FAIL-SILENT", and it was: both call sites discarded this result's `note`,
 // so a refresh that DID NOT HAPPEN and one that did were indistinguishable
 // to the operator — the same silent-failure class this job exists to close.
@@ -57,6 +55,7 @@ import { existsSync, statSync } from 'node:fs';
 import { join } from 'node:path';
 import { CODEGRAPH_DIR_NAME, CODEGRAPH_MARKER_NAME, createCodegraphInvocation, executeCodegraphInvocation, isCodegraphInitialized } from './codegraph-service.js';
 import { repairCodegraphExcludeFromProject } from './codegraph-exclude-repair.js';
+import { dropSqliteBackendAdvice } from './codegraph-backend-advice.js';
 /**
  * The operator-facing line for a refresh that did not happen, or `null` when
  * there is nothing to report. The ONE place the report/no-report rule lives,
@@ -109,7 +108,11 @@ function errorMessage(error) {
 // posture that warning already ships with).
 const REFRESH_REMEDY = 'Run `peaks codegraph index --project <root>` to refresh the codegraph index.';
 function firstMeaningfulLine(text) {
-    const trimmed = text.trim();
+    // Upstream writes its SQLite-backend block before anything
+    // else, so the raw first line of stderr is a box-drawing frame — and the
+    // line after it names a package this project removed. Neither is the
+    // failure cause, and this function exists to name the cause.
+    const trimmed = dropSqliteBackendAdvice(text).trim();
     if (trimmed.length === 0)
         return 'no upstream output';
     const first = trimmed.split(/\r?\n/)[0];
@@ -126,7 +129,6 @@ async function selfHealUninitializedCodegraph(projectRoot, runner) {
     // A `.codegraph/` dir without a `codegraph.db` is uninitialized:
     //   - NOT peaks-loop-managed → foreign schema, never touch it.
     //   - peaks-loop-managed → the dangling state left by the pre-fix
-    //     rid-CG-001 auto-stake (marker stamped, no upstream init). Run
     //     init (fast, offline-safe — no full index) so the subsequent
     //     index has a schema to write into.
     if (!isCodegraphInitialized(projectRoot)) {