peaks-loop 4.1.0 → 4.1.2

package/dist/services/context/auto-compact-dispatcher.js

@@ -1,5 +1,4 @@
 /**
- * AC-3 — IDE-aware compact dispatcher.
  *
  * Reads the active IDE's `IdeAdapter.compact` profile and dispatches
  * compact via the adapter-declared pathway. No hard-coded IDE names
@@ -23,13 +22,11 @@
  *                        returns `ok: false` with `message: 'noop'`.
  *                        Used by legacy / unverified adapters.
  *
- * rid-031 (2026-07-28): `shell-exec` pathway is DEPRECATED. Real
  * callers must use `ide-native` (main session) or
  * `llm-self-compress`. No host CLI spawn occurs; the `case
  * 'shell-exec':` branch logs a deprecation warning and returns the
  * same envelope shape.
  *
- * Slice 2026-09-12-auto-compact-vendor-neutrality (defect #2 of the QA
  * pass): the paragraph above used to justify keeping that branch with
  * "the 2 currently-passing tests" it named by path and line (`:58` of
  * one file, `:102` of another, asserting `pathway: 'shell-exec'`).
@@ -37,7 +34,6 @@
  * deleted by `f17aa377 test(rebuild): delete 559 legacy unit tests and
  * reset vitest config`, and `grep -rn "shell-exec" tests/` now returns
  * nothing — no test in this repo asserts `pathway: 'shell-exec'`. The
- * branch is retained for the rid-031 ENVELOPE CONTRACT itself
  * (`pathway` is part of `CompactDispatchResult` and is echoed to
  * `peaks code auto-compact` callers), not for a test. Deleting it is a
  * contract change, deliberately out of this slice.
@@ -61,12 +57,10 @@ export async function dispatchIdeCompact(input) {
     // See auto-compact-reader.ts for the IdeKind→IdeId cast rationale.
     const ideId = (detected === 'unknown' ? 'claude-code' : detected);
     const adapter = getAdapter(ideId);
-    // Slice 2026-06-28-code-mode-bypass-fix (defect #4): default to
     // `'main'` so the orchestrator's auto-compact actually compresses
     // the main-session context. The orchestrator passes `'sub-agent'`
     // explicitly when a sub-agent shell dispatches the call.
     const target = input.target ?? 'main';
-    // Slice 2026-09-12-auto-compact-vendor-neutrality — the up-front
     // `target === 'main' && ideId !== 'claude-code'` refusal is GONE.
     //
     // It decided by adapter NAME what the adapter's own profile already
@@ -104,11 +98,8 @@ export async function dispatchIdeCompact(input) {
     const pathway = profile.compactPathway;
     switch (pathway) {
         case 'shell-exec':
-            // rid-031 (2026-07-28): `shell-exec` pathway is DEPRECATED.
             // No host CLI spawn occurs. The case marker is preserved for the
-            // rid-031 envelope contract (callers read `pathway`), NOT for a
             // test — see this file's header, defect #2 of the 2026-09-12 QA
-            // pass: the tests the previous comment named were deleted by
             // f17aa377 and no test asserts `pathway: 'shell-exec'` now.
             // Real callers must use `ide-native` (main session) or
             // `llm-self-compress`.
@@ -128,7 +119,6 @@ export async function dispatchIdeCompact(input) {
                 message: `shell-exec pathway is deprecated; no host CLI spawn for command '${profile.compactCommand}'. Use ide-native for main-session runner.`
             };
         case 'ide-native':
-            // Slice 2026-07-02-auto-compact-zero-pause: write the auto-compact
             // PreToolUse hook into the IDE's MACHINE-LOCAL settings layer,
             // resolved from the adapter (`settings.dirName` +
             // `settings.localSettingsFileName`) — never from a path literal
@@ -146,9 +136,7 @@ export async function dispatchIdeCompact(input) {
             // child claude process and the sub-agent's own runner doesn't
             // get a PreToolUse hook installed in the wrong place.
             if (target === 'sub-agent') {
-                // rid-031 (2026-07-28): legacy shell-spawn fallback is
                 // DEPRECATED. No host CLI spawn occurs. The envelope is
-                // returned with `pathway: 'shell-exec'` to preserve the rid-031
                 // contract for callers that read `pathway` (sub-agent shells
                 // historically relied on this path). The test the previous
                 // comment named was deleted by f17aa377 — see this file's
@@ -197,7 +185,6 @@ export async function dispatchIdeCompact(input) {
     }
 }
 /**
- * Slice 2026-07-02-auto-compact-zero-pause: implement the
  * `ide-native` pathway. Writes the auto-compact PreToolUse hook
  * into the IDE's MACHINE-LOCAL settings file (idempotent; the
  * install service is a no-op if the hook is already present). On
@@ -205,7 +192,6 @@ export async function dispatchIdeCompact(input) {
  * `peaks code auto-compact` which in-band spawns the adapter's
  * declared compact command against the CURRENT runner session.
  *
- * Slice 2026-09-12-auto-compact-vendor-neutrality: the settings path
  * AND the echoed `ide` are read off the adapter, so this function no
  * longer names a vendor. An adapter that declares
  * `compactPathway: 'ide-native'` and its own `settings` location gets

package/dist/services/context/auto-compact-reader-input.d.ts

@@ -18,7 +18,6 @@ export interface ReadContextPercentInput {
     readonly outerSessionId?: string | undefined;
     readonly env?: NodeJS.ProcessEnv | undefined;
     /**
-     * Slice 2026-07-31-rid-002: explicit byte count from `--prompt-size <bytes>`.
      * When set to a finite non-negative number, short-circuits the entire
      * env / statusline / transcript chain with `source: 'user-overridden'`.
      * Mac escape hatch — some IDEs (e.g. Claude Code on macOS) do NOT

package/dist/services/context/auto-compact-reader.d.ts

@@ -14,7 +14,6 @@ export type { ReadContextPercentInput };
  * so this module names no IDE and no settings literal — the vendor-neutrality
  * guard's shape-3 rule applies to every registry consumer, and this is one.
  *
- * Slice 2026-09-13-auto-compact-trigger-ownership.
  */
 export declare function resolveHarnessWindowLocation(input: {
     readonly projectRoot: string;
@@ -55,7 +54,6 @@ export declare function resolveHarnessRatioWindow(state: HarnessWindowReadResult
  * Materialize a window into the harness's own settings, so the number
  * peaks-loop divides by and the number the harness compacts against are one
  * value rather than two resolutions (slice
- * 2026-09-13-auto-compact-trigger-ownership).
  *
  * The caller passes the denominator it JUST USED (`probe.capacityTokens`), not
  * a re-derived one — that is what makes the two sides structurally identical.

package/dist/services/context/auto-compact-reader.js

@@ -1,5 +1,4 @@
 /**
- * AC-1 — auto context-percent probe.
  *
  * Reads the current AI CLI context-fill ratio without requiring the
  * LLM to pass `--prompt-size <bytes>` manually. Strategy: ask the
@@ -43,7 +42,6 @@ import { isHarnessWindowInRange, parseHarnessWindowTokens, readHarnessWindow, sy
  * so this module names no IDE and no settings literal — the vendor-neutrality
  * guard's shape-3 rule applies to every registry consumer, and this is one.
  *
- * Slice 2026-09-13-auto-compact-trigger-ownership.
  */
 export function resolveHarnessWindowLocation(input) {
     const env = input.env ?? process.env;
@@ -98,7 +96,6 @@ export function readHarnessWindowState(input) {
 export function resolveHarnessRatioWindow(state) {
     if (state === null)
         return undefined;
-    // E1 (rid 2026-09-13-defects-e): a value outside the band the harness accepts
     // is not a window, however well-formed an integer it is — the harness ignores
     // or caps it, so handing it over here would make the ratio's denominator a
     // number the harness is not compacting on. This is the read half of the same
@@ -121,7 +118,6 @@ export function resolveHarnessRatioWindow(state) {
  * Materialize a window into the harness's own settings, so the number
  * peaks-loop divides by and the number the harness compacts against are one
  * value rather than two resolutions (slice
- * 2026-09-13-auto-compact-trigger-ownership).
  *
  * The caller passes the denominator it JUST USED (`probe.capacityTokens`), not
  * a re-derived one — that is what makes the two sides structurally identical.
@@ -196,7 +192,6 @@ export function readContextPercent(input) {
         };
     }
     if (adapter.compact) {
-        // Slice 2026-09-13-auto-compact-trigger-ownership: the window peaks-loop
         // configured for the harness, read from the adapter's declared settings
         // path + key. `null` (no knob declared, or the key absent) leaves the
         // adapter's chain byte-identical to before this slice.
@@ -222,7 +217,6 @@ export function readContextPercent(input) {
         // transcript probe. When it returns a probe, honor it; otherwise
         // fall through to conservative-fallback.
         //
-        // Slice 2026-09-09-context-window-override: the generic reader also
         // hands the adapter the raw `context.windowTokens` config override, so
         // the adapter's window resolver can prefer an explicit user value over
         // its model-name heuristics (the env override arrives via `env`).
@@ -232,7 +226,6 @@ export function readContextPercent(input) {
             outerSessionId: input.outerSessionId,
             env,
             configWindowTokens: readContextWindowTokensOverride(input.projectRoot),
-            // Slice 2026-09-13-auto-compact-trigger-ownership: hand the adapter the
             // window peaks-loop configured for the harness, so the ratio it reports
             // divides by the very number the harness compacts against — plus whether
             // peaks-loop is the one that wrote it, so the adapter may self-correct

package/dist/services/context/auto-compact-types.d.ts

@@ -1,5 +1,4 @@
 /**
- * Auto-compact shared types (v2.13.0 AC-1..AC-4).
  *
  * Two-tier threshold model — peaks-loop is project-aware and the LLM
  * is the decision-maker:
@@ -28,7 +27,6 @@
  * provides the toolkit; the LLM picks the moment. At 0.95 peaks-loop
  * requests the compact outright and says it is waiting.
  *
- * Slice 2026-09-13-auto-compact-trigger-ownership corrected two claims that
  * used to head this file: the red line does NOT "refuse to dispatch any
  * further sub-agent" (peaks-loop has no way to compact a running session, so
  * such a refusal gated nothing and deadlocked the runner), and the window
@@ -55,7 +53,6 @@ export interface ConvergencePlan {
     readonly nextActions: readonly string[];
     readonly resumeHint: string;
 }
-/** Per-IDE compact pathway chosen by AC-3. */
 export interface CompactDispatchResult {
     readonly ok: boolean;
     readonly ide: string;
@@ -71,7 +68,6 @@ export interface CompactDispatchResult {
  * alias and its record cannot drift apart into two lists.
  *
  * `redLineGated` → `redLineRequested` (slice
- * 2026-09-13-auto-compact-trigger-ownership): nothing was ever gated. See
  * `redLineGated` on the dispatch branches for why the alias is kept rather
  * than deleted.
  */
@@ -101,7 +97,6 @@ export type AutoCompactResult = {
          */
         readonly decision: 'below-threshold' | 'in-flight-batch' | 'already-armed' | 'unresolved-session';
         /**
-         * rid `2026-09-14-compact-dispatch-backoff`, `already-armed` only: the
          * ratio the open run was dispatched at, and its id. `ratio` above is the
          * LIVE reading — the pair is what keeps "it is still high" legible after
          * the backoff drops the per-probe rows: the ask is at `armedAtRatio`, and
@@ -110,7 +105,6 @@ export type AutoCompactResult = {
         readonly armedAtRatio?: number;
         readonly armedRunId?: string;
         /**
-         * Slice 2026-09-13-auto-compact-trigger-ownership: what syncing the
          * harness auto-compact window did on this probe. `null` = the active
          * adapter declares no such knob. Present so the write is VISIBLE —
          * the harness reports an override silently, so peaks-loop must not.
@@ -129,7 +123,6 @@ export type AutoCompactResult = {
         readonly convergencePlan?: ConvergencePlan;
         readonly dispatch?: CompactDispatchResult;
         /**
-         * Slice 2026-06-28-code-mode-bypass-fix (defect #4): which
          * session the compact targeted. `'main'` (default) means the
          * main-session Claude Code window will fire `/compact` on its
          * next turn; `'sub-agent'` means the dispatcher shell-spawned
@@ -137,7 +130,6 @@ export type AutoCompactResult = {
          */
         readonly target?: 'main' | 'sub-agent';
         /**
-         * Slice 2026-07-28 (rid-027): which mode's threshold table
          * was used. Defaults to `'standard'` (0.85/0.95). `'partial'`
          * (0.70/0.85) is selected when 24h mode is active or the
          * caller passes `--mode partial`.
@@ -148,7 +140,6 @@ export type AutoCompactResult = {
          * the harness to compact.
          *
          * Renamed from `redLineGated` in slice
-         * 2026-09-13-auto-compact-trigger-ownership: nothing is gated. The
          * old name asserted a block peaks-loop cannot enforce (it has no
          * executor for a running session), and acting on that assertion is
          * what deadlocked the runner.
@@ -194,7 +185,6 @@ export type AutoCompactResult = {
     };
 };
 /**
- * Probe shape returned by AC-1 (`readContextPercent`). The source
  * field tells callers how the ratio was obtained (env-var, statusline
  * poller, IDE hook, conservative fallback) so the CLI can show
  * "context % (source: statusline-poll)" and the LLM can trust it.
@@ -245,7 +235,6 @@ export interface ContextPercentProbe {
      *   - `default`         — 200K safe default
      * Undefined for byte / percent sources (`user-overridden`, `${ideId}-env`,
      * `statusline-poll`), which have no token window. Slice
-     * 2026-09-09-context-window-override: lets a wrong window be diagnosed in
      * one read instead of guessing which heuristic fired.
      */
     readonly capacitySource?: string;

package/dist/services/context/auto-compact-types.js

@@ -8,7 +8,6 @@ export { AUTO_COMPACT_SOFT_WARN_RATIO, AUTO_COMPACT_AUTO_FIRE_RATIO, AUTO_COMPAC
  * alias and its record cannot drift apart into two lists.
  *
  * `redLineGated` → `redLineRequested` (slice
- * 2026-09-13-auto-compact-trigger-ownership): nothing was ever gated. See
  * `redLineGated` on the dispatch branches for why the alias is kept rather
  * than deleted.
  */

package/dist/services/context/build-dispatch-system-prompt.d.ts

@@ -1,7 +1,6 @@
 /**
  * buildDispatchSystemPrompt — pure-function prompt composer for sub-agent dispatch.
  *
- * Slice 2026-07-22-orchestrator-memory-preflight (Task 5). The orchestrator
  * dispatch flow (`src/cli/commands/dispatch-commands.ts`) calls
  * `MemoryPreflightService.fetchBlock` and feeds the result into this builder
  * so the memory block, when available, is prepended BEFORE the task brief.
@@ -19,7 +18,6 @@ export interface DispatchPromptInput {
     taskBody: string;
     memoryBlock: MemoryPreflightResult;
     /**
-     * Slice 2026-07-29-context-evaluation-accuracy: the live
      * context-fill probe. When provided, the composer prepends
      * a `## Context window` block with the authoritative ratio so
      * the dispatched sub-agent does NOT estimate context from
@@ -29,21 +27,19 @@ export interface DispatchPromptInput {
      */
     contextProbe?: ContextPercentProbe | null;
     /**
-     * Slice 2026-09-03-codegraph-preread (Option A): pre-composed
      * `## Codegraph structure` markdown block, read from the codegraph
      * index BEFORE the RD sub-agent's task body is composed so the RD
      * plans against real module/file topology, not LLM memory.
      *
      * - `undefined` → no codegraph block (legacy callers unchanged).
-     * - `null` → codegraph was attempted but is unavailable; the composer
-     *   renders a fixed "codegraph unavailable — proceeding on project-scan
-     *   only" note (fail-soft; never hard-blocks a dispatch).
-     * - `string` → the block, rendered verbatim between the context window
-     *   and the memory/task content.
+     * - `null` → codegraph was attempted and no reason was obtained; the
+     *   composer renders the fallback that SAYS the reason is missing.
+     * - `string` → the structure block, or the preflight's failure NOTE when the
+     *   index could not be read — the composer turns the note into an unavailable
+     *   block that QUOTES it, so the reason cannot be dropped on its own.
      */
     codegraphBlock?: string | null;
     /**
-     * Slice 2026-09-06-ui-lib-dispatch-priority: pre-composed
      * `## Project stack` markdown block, rendered from the detected
      * project context (component library + CSS framework + build tool) by
      * the dispatch site BEFORE the sub-agent's task body is composed so
@@ -57,7 +53,6 @@ export interface DispatchPromptInput {
      */
     projectStackBlock?: string | null;
     /**
-     * Slice 2026-09-07-search-first-preflight: the orchestrator-synthesized
      * `## Fresh context` block (≤5 binding directives from a Context7 →
      * WebSearch preflight), read from `.peaks/_runtime/<sessionId>/fresh-context.md`.
      *
@@ -69,7 +64,6 @@ export interface DispatchPromptInput {
      */
     freshContextBlock?: string | null;
     /**
-     * Slice 2026-09-10-dispatch-token-and-swarm §4: session capsule
      * published by the orchestrator through `peaks sub-agent share`.
      *
      * - `undefined` / `null` → no capsule pointer, no precedence line
@@ -86,7 +80,6 @@ export interface DispatchPromptInput {
     } | null;
 }
 /**
- * Slice 2026-07-29-worktree-l1: Layer 1 of the 3-layer worktree governance
  * defence. The block below is prepended to every sub-agent dispatch system
  * prompt so the LLM sees the superpowers-chain refusal BEFORE any task
  * content. The block mirrors the prose in
@@ -100,16 +93,13 @@ export interface DispatchPromptInput {
  *   orchestrator synthesizes a prompt without reading the per-role
  *   template (the orchestrator may run peaks-rd on a different rid and
  *   reuse the task body verbatim).
- * - Pure-function design (slice 2026-07-22) makes the appended block
  *   trivially testable.
  *
- * Fallback note: until rid-L2-extended ships `peaks worktree spawn`, the
  * fallback path is `peaks worktree auth grant --rid <id> --reason <text>
  * --ttl <5m>` (already shipped). Update the prose once `spawn` lands.
  */
 export declare const L1_WORKTREE_GOVERNANCE_BLOCK = "## Superpowers chain refusal (L1 worktree governance \u2014 locked 2026-07-29)\n\nYou MUST NOT follow the superpowers chain for worktree decisions:\n\n- superpowers:brainstorming \u2192 superpowers:writing-plans \u2192\n  superpowers:subagent-driven-development \u2192 superpowers:using-git-worktrees\n\nThat chain ends with `git worktree add` (superpowers:using-git-worktrees SKILL.md line 96), which bypasses peaks-loop's L2 hook gate and L3 IDE `permissions.deny`. L3 denial is NOT sufficient \u2014 by then the chain has already taught raw `git worktree add`.\n\nFor worktree operations, use ONLY:\n\n- `peaks worktree spawn --rid <rid> --ttl <duration> --purpose <text>` (after rid-L2-extended ships)\n- until then: `peaks worktree auth grant --rid <id> --reason <text> --ttl <5m>`\n\nSuperpowers skills remain REFERENCE material for brainstorming / planning techniques, but MUST NOT be used as a workflow. peaks-rd's own PRD/RD artifacts (`.peaks/_runtime/<sessionId>/rd/requests/<rid>.md`) are authoritative.\n\nIf the upstream superpowers chain suggests raw `git worktree add`:\n\n1. STOP\n2. Re-author the plan as a peaks-rd artifact\n3. Continue with `peaks worktree spawn` (or the auth-grant fallback)\n";
 /**
- * Slice 2026-08-01-subagent-merge-and-e2e (Task 8): the dispatch
  * system prompt gains three lifecycle rules. The sub-agent must:
  *
  *   1. Register any long-lived local process it starts (vite dev,
@@ -135,7 +125,6 @@ export declare const L1_WORKTREE_GOVERNANCE_BLOCK = "## Superpowers chain refusa
  */
 export declare const LIFECYCLE_RULES = "## Sub-agent lifecycle rules (locked 2026-08-01)\n\n- If you start a long-lived local service (vite dev, mock API, docker container, etc.), register it with `peaks sub-agent shutdown register --pid <pid> --name <label>` before you exit; the parent session best-effort-kills it before merge-back.\n- Do NOT run E2E. The parent session runs Playwright verification once after merge-back (Task 10); your E2E work is duplicate effort.\n- Do NOT call `git merge`, `git pull`, `git rebase`, or `peaks worktree release`. The parent session owns the merge-back step.\n";
 /**
- * Slice 2026-09-10-context-audit-and-discipline (Slice C): cap the sub-agent's
  * FINAL report.
  *
  * Why (measured, session 2026-09-07-session-245530): 20 sub-agent final
@@ -151,7 +140,6 @@ export declare const LIFECYCLE_RULES = "## Sub-agent lifecycle rules (locked 202
  */
 export declare const REPORT_CAP_BLOCK = "## Final report cap (mandatory)\n\nYour FINAL report to the parent MUST be \u2264 40 lines and \u2264 2 KB. Write any longer detail into the artifact file you already own \u2014 the parent can `Read` that file for the full detail, so nothing is lost. The report itself MUST still carry: changed files (one line each), the exact commands you ran, pass/fail counts, tsc status, and any blocker. Do NOT paste file contents, full tool output, or logs into the report.\n";
 /**
- * Slice 2026-09-10-fact-force-gate-adaptation: stand IN FRONT of an external
  * `PreToolUse` gate instead of explaining its denial after the fact.
  *
  * ECC (a third-party plugin under `~/.claude/plugins/`) registers
@@ -187,20 +175,16 @@ export declare function renderFactForceGateBlock(): string;
 /**
  * Compose the system-prompt body for a sub-agent dispatch.
  *
- * 2026-09-10-dispatch-block-d (Option D): the composer owns the Test Tool
  * Detection injection — ONE unified block for every role, prepended first.
  * Callers MUST NOT prepend `formatTestToolDetection()` themselves or the
  * block is injected twice.
  *
- * Byte-identical degradation contract (slice 2026-07-22-orchestrator-memory-preflight
  * controller brief): when the memory block is unavailable, the composed body is
  * exactly `formatTestToolDetection() + "\n\n" + L1 + "\n" + LIFECYCLE +
  * "\n" + REPORT_CAP + "\n" + FACT_FORCE_GATE + "\n" + contextBlock + taskBody`, so the unavailable
  * branch MUST return `taskBody` unwrapped (NOT a `# title\n\n` wrap).
  * (REPORT_CAP joined the stable prefix in slice
- * 2026-09-10-context-audit-and-discipline, Slice C.)
  * The contract holds for callers that do not pass `codegraphBlock` (all
- * non-RD roles). Slice 2026-09-03-codegraph-preread deliberately inserts a
  * codegraph structure block (or its fail-soft unavailable note) for RD
  * dispatches between the context window and the memory/task content.
  *
@@ -208,20 +192,19 @@ export declare function renderFactForceGateBlock(): string;
  * `## Project memory …` always sits above the task brief (never pushed below
  * it).
  *
- * Slice 2026-07-29-worktree-l1: every branch prepends the L1 worktree
  * governance block BEFORE the memory block / task body. The block is the
  * first thing the dispatched sub-agent sees, so the superpowers-chain
  * refusal is in scope before any task-specific prose arrives.
  */
 export declare function buildDispatchSystemPrompt(input: DispatchPromptInput): string;
 /**
- * Slice 2026-09-03-codegraph-preread: fixed degradation string emitted
- * when the RD dispatch preflight requested a codegraph structure read but
- * the index could not be resolved (absent + init failure, foreign schema,
- * unparseable output). Kept as a constant so the unavailable branch is
- * byte-stable and trivially testable.
+ * the truly reasonless fallback: rendered only when the caller passes `null`,
+ * i.e. a codegraph was attempted and NOTHING was learned about why it failed.
+ * It must never stand in for a reason that exists, which is why its text says
+ * the reason was not obtained rather than the bare "unavailable" that reads
+ * exactly like the success line it replaced.
  */
-export declare const CODEGRAPH_UNAVAILABLE_BLOCK = "## Codegraph structure\n\ncodegraph unavailable \u2014 proceeding on project-scan only.\n";
+export declare const CODEGRAPH_UNAVAILABLE_BLOCK: string;
 /** Binding phrases every dispatch prompt must contain, for every role. */
 export declare const BINDING_RULE_TOKENS: readonly string[];
 /**
@@ -232,7 +215,6 @@ export declare const BINDING_RULE_TOKENS: readonly string[];
  * runner without asking the user as a last resort, and prefer
  * `peaks test <file>` because it resolves the local binary Windows-aware.
  *
- * 2026-09-10-dispatch-block-d (Option D): there is no role split any more,
  * so this set is asserted IDENTICALLY for every role. The runner EXAMPLES
  * were removed as part of the unification — they were never rules.
  */

package/dist/services/context/build-dispatch-system-prompt.js

@@ -1,6 +1,6 @@
 import { formatTestToolDetection } from '../dispatch/test-tool-detection.js';
+import { resolveCodegraphBlock } from './codegraph-unavailable-block.js';
 /**
- * Slice 2026-07-29-worktree-l1: Layer 1 of the 3-layer worktree governance
  * defence. The block below is prepended to every sub-agent dispatch system
  * prompt so the LLM sees the superpowers-chain refusal BEFORE any task
  * content. The block mirrors the prose in
@@ -14,10 +14,8 @@ import { formatTestToolDetection } from '../dispatch/test-tool-detection.js';
  *   orchestrator synthesizes a prompt without reading the per-role
  *   template (the orchestrator may run peaks-rd on a different rid and
  *   reuse the task body verbatim).
- * - Pure-function design (slice 2026-07-22) makes the appended block
  *   trivially testable.
  *
- * Fallback note: until rid-L2-extended ships `peaks worktree spawn`, the
  * fallback path is `peaks worktree auth grant --rid <id> --reason <text>
  * --ttl <5m>` (already shipped). Update the prose once `spawn` lands.
  */
@@ -44,7 +42,6 @@ If the upstream superpowers chain suggests raw \`git worktree add\`:
 3. Continue with \`peaks worktree spawn\` (or the auth-grant fallback)
 `;
 /**
- * Slice 2026-08-01-subagent-merge-and-e2e (Task 8): the dispatch
  * system prompt gains three lifecycle rules. The sub-agent must:
  *
  *   1. Register any long-lived local process it starts (vite dev,
@@ -75,7 +72,6 @@ export const LIFECYCLE_RULES = `## Sub-agent lifecycle rules (locked 2026-08-01)
 - Do NOT call \`git merge\`, \`git pull\`, \`git rebase\`, or \`peaks worktree release\`. The parent session owns the merge-back step.
 `;
 /**
- * Slice 2026-09-10-context-audit-and-discipline (Slice C): cap the sub-agent's
  * FINAL report.
  *
  * Why (measured, session 2026-09-07-session-245530): 20 sub-agent final
@@ -94,7 +90,6 @@ export const REPORT_CAP_BLOCK = `## Final report cap (mandatory)
 Your FINAL report to the parent MUST be ≤ 40 lines and ≤ 2 KB. Write any longer detail into the artifact file you already own — the parent can \`Read\` that file for the full detail, so nothing is lost. The report itself MUST still carry: changed files (one line each), the exact commands you ran, pass/fail counts, tsc status, and any blocker. Do NOT paste file contents, full tool output, or logs into the report.
 `;
 /**
- * Slice 2026-09-10-fact-force-gate-adaptation: stand IN FRONT of an external
  * `PreToolUse` gate instead of explaining its denial after the fact.
  *
  * ECC (a third-party plugin under `~/.claude/plugins/`) registers
@@ -137,20 +132,16 @@ export function renderFactForceGateBlock() {
 /**
  * Compose the system-prompt body for a sub-agent dispatch.
  *
- * 2026-09-10-dispatch-block-d (Option D): the composer owns the Test Tool
  * Detection injection — ONE unified block for every role, prepended first.
  * Callers MUST NOT prepend `formatTestToolDetection()` themselves or the
  * block is injected twice.
  *
- * Byte-identical degradation contract (slice 2026-07-22-orchestrator-memory-preflight
  * controller brief): when the memory block is unavailable, the composed body is
  * exactly `formatTestToolDetection() + "\n\n" + L1 + "\n" + LIFECYCLE +
  * "\n" + REPORT_CAP + "\n" + FACT_FORCE_GATE + "\n" + contextBlock + taskBody`, so the unavailable
  * branch MUST return `taskBody` unwrapped (NOT a `# title\n\n` wrap).
  * (REPORT_CAP joined the stable prefix in slice
- * 2026-09-10-context-audit-and-discipline, Slice C.)
  * The contract holds for callers that do not pass `codegraphBlock` (all
- * non-RD roles). Slice 2026-09-03-codegraph-preread deliberately inserts a
  * codegraph structure block (or its fail-soft unavailable note) for RD
  * dispatches between the context window and the memory/task content.
  *
@@ -158,18 +149,15 @@ export function renderFactForceGateBlock() {
  * `## Project memory …` always sits above the task brief (never pushed below
  * it).
  *
- * Slice 2026-07-29-worktree-l1: every branch prepends the L1 worktree
  * governance block BEFORE the memory block / task body. The block is the
  * first thing the dispatched sub-agent sees, so the superpowers-chain
  * refusal is in scope before any task-specific prose arrives.
  */
 export function buildDispatchSystemPrompt(input) {
     const { taskBody, memoryBlock, contextProbe, codegraphBlock, projectStackBlock, freshContextBlock, capsule } = input;
-    // 2026-09-10-dispatch-block-d (Option D): ONE Test Tool Detection block
     // for every role — the composer owns the injection so callers MUST NOT
     // prepend `formatTestToolDetection()` themselves (double injection).
     const testToolText = `${formatTestToolDetection()}\n\n`;
-    // 2026-09-10-fact-force-gate-adaptation: always-on, both branches.
     const factForceGateText = renderFactForceGateBlock();
     const contextBlock = renderContextBlock(contextProbe ?? null);
     const codegraphText = renderCodegraphBlock(codegraphBlock);
@@ -182,7 +170,6 @@ export function buildDispatchSystemPrompt(input) {
     return `${testToolText}${L1_WORKTREE_GOVERNANCE_BLOCK}\n${LIFECYCLE_RULES}\n${REPORT_CAP_BLOCK}\n${factForceGateText}${contextBlock}${codegraphText}${projectStackText}${freshContextText}${capsuleText}${taskBody}`;
 }
 /**
- * Slice 2026-09-10-dispatch-token-and-swarm §4 — session capsule pointer.
  *
  * QUALITY GUARD: the capsule is BACKGROUND only. The precedence line below
  * is part of the contract, not decoration — anything the sub-agent must
@@ -195,13 +182,13 @@ function renderCapsulePointer(capsule) {
     return `## Shared session capsule (advisory background)\nBackground facts already established by the orchestrator (${capsule.bytes} bytes): read them with \`peaks sub-agent shared-read --batch ${capsule.batchId} --key ${capsule.key}\`. This capsule is ADVISORY BACKGROUND ONLY — it is not a task. Your task spec below is authoritative and wins on any conflict; anything you must act on is stated inline there.\n\n`;
 }
 /**
- * Slice 2026-09-03-codegraph-preread: fixed degradation string emitted
- * when the RD dispatch preflight requested a codegraph structure read but
- * the index could not be resolved (absent + init failure, foreign schema,
- * unparseable output). Kept as a constant so the unavailable branch is
- * byte-stable and trivially testable.
+ * the truly reasonless fallback: rendered only when the caller passes `null`,
+ * i.e. a codegraph was attempted and NOTHING was learned about why it failed.
+ * It must never stand in for a reason that exists, which is why its text says
+ * the reason was not obtained rather than the bare "unavailable" that reads
+ * exactly like the success line it replaced.
  */
-export const CODEGRAPH_UNAVAILABLE_BLOCK = '## Codegraph structure\n\ncodegraph unavailable — proceeding on project-scan only.\n';
+export const CODEGRAPH_UNAVAILABLE_BLOCK = resolveCodegraphBlock(null);
 /**
  * Render the codegraph insertion for a dispatch prompt.
  *
@@ -218,8 +205,7 @@ export const CODEGRAPH_UNAVAILABLE_BLOCK = '## Codegraph structure\n\ncodegraph
 function renderCodegraphBlock(codegraphBlock) {
     if (codegraphBlock === undefined)
         return '';
-    const text = codegraphBlock === null ? CODEGRAPH_UNAVAILABLE_BLOCK : codegraphBlock;
-    return `${text.replace(/\s+$/, '')}\n\n`;
+    return `${resolveCodegraphBlock(codegraphBlock).replace(/\s+$/, '')}\n\n`;
 }
 /**
  * Render the project-stack insertion for a dispatch prompt.
@@ -255,7 +241,6 @@ function renderFreshContextBlock(freshContextBlock) {
     return `${freshContextBlock.replace(/\s+$/, '')}\n\n`;
 }
 /**
- * Slice 2026-07-29-context-evaluation-accuracy: emit a
  * `## Context window` block with the authoritative ratio so the
  * dispatched sub-agent does not estimate from message length.
  *
@@ -300,7 +285,6 @@ No context-fill probe was captured before this dispatch. To evaluate context pre
 `;
 }
 /* ──────────────────────────────────────────────────────────────────────────
- * Slice 2026-09-10-dispatch-token-and-swarm §1 — rule-presence guard.
  *
  * The compression + role-scoping in this file is allowed to shorten prose.
  * It is NOT allowed to drop a binding rule. These token sets are the
@@ -330,14 +314,12 @@ export const BINDING_RULE_TOKENS = [
     'do NOT estimate yourself',
     '`peaks code context-now`',
     '`verdict: red-line`',
-    // final report cap (Slice 2026-09-10-context-audit-and-discipline, Slice C)
     '## Final report cap (mandatory)',
     '≤ 40 lines and ≤ 2 KB',
     'the parent can `Read` that file for the full detail',
     'changed files (one line each)',
     'pass/fail counts',
     'tsc status',
-    // fact-forcing gate (slice 2026-09-10-fact-force-gate-adaptation)
     '## Read before you edit (Fact-Forcing Gate)',
     'Read a file BEFORE your first `Edit` / `Write` / `MultiEdit` on it',
     'every path OUTSIDE `.peaks/**`',
@@ -362,7 +344,6 @@ export const BINDING_RULE_TOKENS = [
  * runner without asking the user as a last resort, and prefer
  * `peaks test <file>` because it resolves the local binary Windows-aware.
  *
- * 2026-09-10-dispatch-block-d (Option D): there is no role split any more,
  * so this set is asserted IDENTICALLY for every role. The runner EXAMPLES
  * were removed as part of the unification — they were never rules.
  */

package/dist/services/context/codegraph-unavailable-block.d.ts

@@ -0,0 +1,38 @@
+/** Opens every codegraph block; the discriminator between a block and a bare note. */
+export declare const CODEGRAPH_BLOCK_HEADING = "## Codegraph structure";
+/** The sentence shared by the reasonless fallback and the reason-bearing block. */
+export declare const CODEGRAPH_PROCEEDING = "codegraph unavailable \u2014 proceeding on project-scan only.";
+/**
+ * The sentence the TRULY reasonless fallback renders.
+ *
+ * Load-bearing, not decoration: the pre-fix block said only "codegraph
+ * unavailable", which is byte-for-byte what a reader saw whether upstream printed
+ * `unable to open database file` or printed nothing at all. Naming the missing
+ * reason makes "no reason exists" a claim the reader can check, and leaves "a
+ * reason exists but the dispatch dropped it" with nowhere to hide.
+ */
+export declare const CODEGRAPH_REASON_MISSING = "No failure reason was obtained from the codegraph preflight.";
+/** Opens the reason-bearing variant; asserted absent whenever no reason exists. */
+export declare const CODEGRAPH_REASON_SENTENCE = "Reason reported by the codegraph preflight: ";
+/**
+ * Render the block for an unavailable codegraph. `note` is the preflight's own
+ * failure note, quoted rather than paraphrased — the point is that the next
+ * reader sees `unable to open database file` instead of re-deriving it.
+ *
+ * The quote is whitespace-collapsed to one line so a multi-line upstream summary
+ * cannot forge a markdown heading further down the prompt; it is otherwise
+ * verbatim, upstream's own SGR color included. Rewriting the failure text here
+ * would put peaks-loop's words where the cause belongs.
+ */
+export declare function renderCodegraphUnavailableBlock(note?: string | null): string;
+/**
+ * The ONE place a `codegraphBlock` value becomes text.
+ *
+ * - `null` (preflight ran, no reason obtained) → the explicit fallback.
+ * - a string already opening with the heading → the pre-composed structure
+ *   block, verbatim.
+ * - any other string → an unavailable block quoting it as the reported reason.
+ *   `buildCodegraphPreflightBlock`'s `{ available: false, note }` arm is the only
+ *   production producer of that shape.
+ */
+export declare function resolveCodegraphBlock(value: string | null): string;