peaks-loop 4.0.0-beta.12 → 4.0.0-beta.15

package/dist/services/workflow/workflow-router-service.js

@@ -78,30 +78,32 @@ function annotateSteps(steps, codeMode) {
         };
     });
 }
-function createSoloSteps(executionModelId, strongestModelId) {
+function createSoloSteps(executionModelId, strongestModelId, economyMode) {
+    const executionTier = economyMode === false ? 'top-tier' : 'mid-tier';
     return [
         step({ id: 'code-product-direction', stage: 'product-direction', owner: 'peaks-code', modelTier: 'top-tier', reason: 'Product direction needs strong judgment before execution work is delegated.', dependsOn: [] }, executionModelId, strongestModelId),
         step({ id: 'code-design-direction', stage: 'design-direction', owner: 'peaks-code', modelTier: 'top-tier', reason: 'Design direction uses the recommended default before cheaper implementation work.', dependsOn: ['code-product-direction'] }, executionModelId, strongestModelId),
         step({ id: 'code-tech-direction', stage: 'tech-direction', owner: 'peaks-tech', modelTier: 'top-tier', reason: 'Technical boundaries and approval gates use the recommended default with high-confidence planning.', dependsOn: ['code-design-direction'] }, executionModelId, strongestModelId),
         step({ id: 'code-tech-review', stage: 'tech-review', owner: 'peaks-tech', modelTier: 'top-tier', reason: 'Tech artifacts and gate decisions require strong review and a recommended default path.', dependsOn: ['code-tech-direction'] }, executionModelId, strongestModelId),
         step({ id: 'code-rd-planning', stage: 'rd-planning', owner: 'peaks-rd', modelTier: 'top-tier', reason: 'RD task decomposition and acceptance criteria use the recommended default before execution delegation.', dependsOn: ['code-tech-review'] }, executionModelId, strongestModelId),
-        step({ id: 'code-coding-execution', stage: 'coding-execution', owner: 'peaks-rd', modelTier: executionModelId === strongestModelId ? 'top-tier' : 'mid-tier', reason: `Coding and routine refactoring must use the configured execution worker model ${executionModelId}.`, dependsOn: ['code-rd-planning'] }, executionModelId, strongestModelId),
-        step({ id: 'code-unit-test-execution', stage: 'unit-test-execution', owner: 'peaks-rd', modelTier: executionModelId === strongestModelId ? 'top-tier' : 'mid-tier', reason: `Unit test authoring and focused test runs must use the configured execution worker model ${executionModelId}.`, dependsOn: ['code-coding-execution'] }, executionModelId, strongestModelId),
+        step({ id: 'code-coding-execution', stage: 'coding-execution', owner: 'peaks-rd', modelTier: executionTier, reason: `Coding and routine refactoring must use the configured execution worker model ${executionModelId}.`, dependsOn: ['code-rd-planning'] }, executionModelId, strongestModelId),
+        step({ id: 'code-unit-test-execution', stage: 'unit-test-execution', owner: 'peaks-rd', modelTier: executionTier, reason: `Unit test authoring and focused test runs must use the configured execution worker model ${executionModelId}.`, dependsOn: ['code-coding-execution'] }, executionModelId, strongestModelId),
         step({ id: 'code-quality-review', stage: 'quality-review', owner: 'peaks-code', modelTier: 'top-tier', reason: 'Reducer and final quality gates need strong synthesis and risk review.', dependsOn: ['code-unit-test-execution'] }, executionModelId, strongestModelId)
     ];
 }
-function createSoloStepsForMode(codeMode, executionModelId, strongestModelId) {
-    return annotateSteps(createSoloSteps(executionModelId, strongestModelId), codeMode);
+function createSoloStepsForMode(codeMode, executionModelId, strongestModelId, economyMode) {
+    return annotateSteps(createSoloSteps(executionModelId, strongestModelId, economyMode), codeMode);
 }
-function createTeamSteps(executionModelId, strongestModelId) {
+function createTeamSteps(executionModelId, strongestModelId, economyMode) {
+    const executionTier = economyMode === false ? 'top-tier' : 'mid-tier';
     return [
         step({ id: 'team-product-direction', stage: 'product-direction', owner: 'human', modelTier: 'top-tier', reason: 'Team product direction should stay on the governed planning path.', dependsOn: [] }, executionModelId, strongestModelId),
         step({ id: 'team-design-direction', stage: 'design-direction', owner: 'human', modelTier: 'top-tier', reason: 'Team design direction should preserve reviewability and accountability.', dependsOn: ['team-product-direction'] }, executionModelId, strongestModelId),
         step({ id: 'team-tech-direction', stage: 'tech-direction', owner: 'peaks-tech', modelTier: 'top-tier', reason: 'Team technical plans should remain strongly governed before RD execution.', dependsOn: ['team-design-direction'] }, executionModelId, strongestModelId),
         step({ id: 'team-tech-review', stage: 'tech-review', owner: 'peaks-tech', modelTier: 'top-tier', reason: 'Team tech approval requires strong review before execution.', dependsOn: ['team-tech-direction'] }, executionModelId, strongestModelId),
         step({ id: 'team-rd-planning', stage: 'rd-planning', owner: 'peaks-rd', modelTier: 'top-tier', reason: 'Team RD task decomposition remains on the governed strongest-model path.', dependsOn: ['team-tech-review'] }, executionModelId, strongestModelId),
-        step({ id: 'team-coding-execution', stage: 'coding-execution', owner: 'peaks-rd', modelTier: executionModelId === strongestModelId ? 'top-tier' : 'mid-tier', reason: `Bounded coding tasks must use the configured execution worker model ${executionModelId}.`, dependsOn: ['team-rd-planning'] }, executionModelId, strongestModelId),
-        step({ id: 'team-unit-test-execution', stage: 'unit-test-execution', owner: 'peaks-rd', modelTier: executionModelId === strongestModelId ? 'top-tier' : 'mid-tier', reason: `Unit-test tasks must use the configured execution worker model ${executionModelId}.`, dependsOn: ['team-coding-execution'] }, executionModelId, strongestModelId),
+        step({ id: 'team-coding-execution', stage: 'coding-execution', owner: 'peaks-rd', modelTier: executionTier, reason: `Bounded coding tasks must use the configured execution worker model ${executionModelId}.`, dependsOn: ['team-rd-planning'] }, executionModelId, strongestModelId),
+        step({ id: 'team-unit-test-execution', stage: 'unit-test-execution', owner: 'peaks-rd', modelTier: executionTier, reason: `Unit-test tasks must use the configured execution worker model ${executionModelId}.`, dependsOn: ['team-coding-execution'] }, executionModelId, strongestModelId),
         step({ id: 'team-quality-review', stage: 'quality-review', owner: 'peaks-rd', modelTier: 'top-tier', reason: 'Team RD outputs still need reducer and quality review gates.', dependsOn: ['team-unit-test-execution'] }, executionModelId, strongestModelId)
     ];
 }
@@ -201,7 +203,7 @@ export function createWorkflowRouterPlan(request) {
     const techStatus = getTechStatus({ sessionId: request.sessionId, ...sharedWorkspaceOptions });
     const techPlan = createTechPlan({ sessionId: request.sessionId, goal, swarm: swarmMode, dryRun: true, ...sharedWorkspaceOptions });
     const rdPlan = createRdSwarmPlan({ skill: 'rd', sessionId: request.sessionId, goal, maxWorkers, swarmMode, executionModelId, dryRun: true, ...sharedWorkspaceOptions });
-    const steps = codeMode ? createSoloStepsForMode(codeMode, executionModelId, strongestModelId) : createTeamSteps(executionModelId, strongestModelId);
+    const steps = codeMode ? createSoloStepsForMode(codeMode, executionModelId, strongestModelId, economyMode) : createTeamSteps(executionModelId, strongestModelId, economyMode);
     const blockedReasons = uniqueStrings([
         ...techStatus.blockedReasons,
         ...getTechPlanBlockedReasons(techPlan),

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

@@ -1,7 +1,7 @@
 import { execFileSync } from 'node:child_process';
 import { mkdir, readFile, readdir, rename, rm } from 'node:fs/promises';
 import { join } from 'node:path';
-import { isDirectory, pathExists } from '../../shared/fs.js';
+import { isDirectory, pathExists } from 'peaks-loop-shared/fs';
 import { isPathInsideArtifactRoot } from '../../shared/path-safety.js';
 const ROLE_DIRS = new Set(['prd', 'ui', 'rd', 'qa', 'sc', 'system']);
 /** Top-level dirs in `.peaks/` that are NEVER legacy session dirs

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

@@ -1,7 +1,7 @@
 import { mkdir } from 'node:fs/promises';
 import { existsSync, lstatSync, readdirSync } from 'node:fs';
 import { join } from 'node:path';
-import { isDirectory } from '../../shared/fs.js';
+import { isDirectory } from 'peaks-loop-shared/fs';
 import { getSessionId, setCurrentSessionBinding, setSessionMeta } from '../session/session-manager.js';
 /**
  * Slice 2026-06-29-change-id-root-removal: list the immediate children of

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "peaks-loop",
-  "version": "4.0.0-beta.12",
+  "version": "4.0.0-beta.15",
   "description": "Loop Engineering CLI — workflow primitive / loop guards / evaluators / slice orchestration",
   "author": "SquabbyZ",
   "license": "MIT",
@@ -26,6 +26,7 @@
     "dist/**/*.js",
     "dist/**/*.d.ts",
     "dist/**/*.md",
+    "dist/**/*.sql",
     "scripts/clean-dist.mjs",
     "scripts/copy-templates.mjs",
     "scripts/sync-version.mjs",
@@ -41,14 +42,10 @@
     "README.md",
     "README-en.md",
     "CHANGELOG.md",
-    "LICENSE",
-    "examples/video-demo/preview/peaks-loop-demo.mp4",
-    "examples/video-demo/preview/peaks-loop-demo-en.mp4",
-    "examples/video-demo/out/zh-closing-960.png",
-    "examples/video-demo/out/en-closing-960.png"
+    "LICENSE"
   ],
   "scripts": {
-    "build": "node ./scripts/sync-version.mjs && node ./scripts/clean-dist.mjs && tsc -p tsconfig.build.json && node ./scripts/copy-templates.mjs",
+    "build": "node ./scripts/sync-version.mjs && node ./scripts/clean-dist.mjs && pnpm -r --filter \"./packages/*\" run build && tsc -p tsconfig.build.json && node ./scripts/copy-templates.mjs",
     "prepack": "npm run build",
     "prepublishOnly": "node scripts/prepublish-build.mjs",
     "prepublish": "node ./scripts/sync-version.mjs",
@@ -70,7 +67,7 @@
     "test:ci": "node ./scripts/sync-version.mjs && node ./scripts/lint/silent-warning-detector.mjs && vitest run --coverage",
     "test:changed": "node scripts/test-changed.mjs",
     "lint:silent-warning": "node ./scripts/lint/silent-warning-detector.mjs",
-    "test:race": "vitest run --no-file-parallelism tests/unit/g8-shared-channel.test.ts tests/unit/dispatch-record-writer.test.ts tests/unit/services/retrospective/heartbeat.test.ts tests/unit/cli/commands/share-commands.test.ts",
+    "test:race": "vitest run --no-file-parallelism packages/peaks-loop-shared-channel/tests/shared-channel.test.ts tests/unit/dispatch-record-writer.test.ts tests/unit/services/retrospective/heartbeat.test.ts tests/unit/cli/commands/share-commands.test.ts",
     "test:replay": "node scripts/fixture-capture-setup.mjs && vitest run tests/unit/replay tests/unit/fixture",
     "fixture:capture-setup": "node scripts/fixture-capture-setup.mjs",
     "test:coverage": "vitest run --coverage",
@@ -97,6 +94,14 @@
     "commander": "^12.1.0",
     "fzf": "^0.5.2",
     "headroom-ai": "0.22.4",
+    "peaks-loop-audit-independent": "workspace:*",
+    "peaks-loop-crystallization": "workspace:*",
+    "peaks-loop-doctor": "workspace:*",
+    "peaks-loop-final-review": "workspace:*",
+    "peaks-loop-mut": "workspace:*",
+    "peaks-loop-job-snapshot": "workspace:*",
+    "peaks-loop-shared-channel": "workspace:*",
+    "peaks-loop-shared": "workspace:*",
     "yaml": "^2.9.0",
     "zod": "^3.25.76"
   },
@@ -109,6 +114,7 @@
     }
   },
   "devDependencies": {
+    "@changesets/cli": "2.31.1",
     "@jridgewell/trace-mapping": "^0.3.31",
     "@stryker-mutator/core": "^8.7.1",
     "@stryker-mutator/typescript-checker": "^8.7.1",

package/scripts/copy-templates.mjs

@@ -9,6 +9,15 @@
  * therefore only get the dynamically-generated `project-scan.md` and
  * the 4 audit/business templates would silently be missing.
  *
+ * D-019 (2026-07-16): also copy the SkillHub SQLite migrations
+ * (`src/services/skillhub/migrations/*.sql`) into dist/. Without this,
+ * the published `peaks-loop` tarball ships an empty
+ * `dist/services/skillhub/migrations/` and `openStateDb()` opens a
+ * schema-less database, breaking any `peaks skill sediment <verb>`
+ * on a fresh consumer install. Vitest tests still pass because they
+ * use tsx + the source tree directly, but downstream npm consumers
+ * see `no such table: bee_release` on the very first command.
+ *
  * Idempotent: safe to run multiple times. Run after `tsc` in `build`.
  */
 import { copyFileSync, mkdirSync, readdirSync, statSync } from 'node:fs';
@@ -44,6 +53,13 @@ const targets = [
     src: join(packageRoot, 'src/services/workspace/templates/project-scan'),
     dest: join(packageRoot, 'dist/services/workspace/templates/project-scan'),
     extensions: ['.md']
+  },
+  {
+    // D-019: SkillHub SQLite migrations must reach the published tarball
+    // so `openStateDb()` can apply the schema on first run.
+    src: join(packageRoot, 'src/services/skillhub/migrations'),
+    dest: join(packageRoot, 'dist/services/skillhub/migrations'),
+    extensions: ['.sql']
   }
 ];
 

package/scripts/sync-version.mjs

@@ -9,4 +9,11 @@ if (typeof version !== 'string' || version.length === 0) {
   throw new Error('package.json version must be a non-empty string');
 }
 
-writeFileSync(resolve('src/shared/version.ts'), `export const CLI_VERSION = ${JSON.stringify(version)};\n`);
+// Slice 3a — version.ts lives in the peaks-loop-shared workspace package.
+// The shared package is `private: true` and is consumed via workspace:*,
+// so its own package.json `version` field is irrelevant for downstream
+// consumers; we always emit the main peaks-loop version.
+writeFileSync(
+  resolve('packages/peaks-loop-shared/src/version.ts'),
+  `export const CLI_VERSION = ${JSON.stringify(version)};\n`,
+);

package/skills/bee/peaks-rd/SKILL.md

@@ -136,7 +136,20 @@ If any gate fails, return to development for fixes or hand off as blocked. Do no
 
 ## Parallel review fan-out (v2.12.0 3-way fanout — code-reviewer + qa-test-cases-writer + karpathy-reviewer)
 
-Full content extracted to **`references/parallel-review-fanout.md`** (3-way fan-out dispatch contract, when-to-fan-out rules, dispatch template, prereq gates). Read that file before issuing any 3-way fan-out.
+**v2.12.0 collapse (Group A — Tier 1+2+3):** the previous 5-way fan-out (slice 004 4-way + slice 5/6 `karpathy-reviewer` addition) totalled **5 sub-agents**. The `security-reviewer` and `perf-baseline-reviewer` slots moved out of the RD 3-way fan-out into two new standalone audit skills:
+
+- `peaks-security-audit` — CLI: `peaks security-audit run`. Writes `audit/security.md` (under `.peaks/_runtime/<sessionId>/audit/security.md`). Required RD-side prereq `AUDIT_SECURITY`.
+- `peaks-perf-audit` — CLI: `peaks perf-audit run`. Writes `audit/perf.md` (under `.peaks/_runtime/<sessionId>/audit/perf.md`). Required RD-side prereq `AUDIT_PERF`.
+
+Both audit skills consume the immutable peaks-prd handoff (`prd/handoff.md`) and the project-scoped audit templates under `.peaks/project-scan/{security-template, perf-template, audit-output-schema}.md`. The handoff presence is enforced by the `AUDIT_REQUIRES_HANDOFF` prereq. The 1-minor-release back-compat window (v2.12.0) keeps the old `rd/security-review.md` and `rd/perf-baseline.md` paths readable via `mustContainAny` — see `references/rd-fanout-contracts.md` §"Deprecated reviewer back-compat".
+
+**Current 3-way fan-out** (always runs for feature / refactor / bugfix; no fan-out for config / docs / chore):
+
+1. `code-reviewer` — writes `rd/code-review.md` (Gate B3).
+2. `qa-test-cases-writer` — writes `qa/test-cases/<rid>.md` (Gate C2).
+3. `karpathy-reviewer` — writes `rd/karpathy-review.md` (the **hard Karpathy-Gate**, KARPATHY_REVIEW prereq).
+
+Full dispatch contract (when-to-fan-out rules, dispatch template, prereq gates) lives in **`references/parallel-review-fanout.md`**. Read that file before issuing any 3-way fan-out.
 
 ## Refactor hard gates
 

package/skills/peaks-code/SKILL.md

@@ -48,6 +48,50 @@ This skill is the **primary surface**. The `peaks <cmd>` CLI is **auxiliary**
 
 Full content extracted to **`references/startup-sequence.md`** (Steps 0 / 0.5-0.87 / 1 / 2 / 2.3 / 2.5 / N / N+1 / N+2 + sub-agent sharing + boundaries). Read that file in full at session start; the sequence is MANDATORY.
 
+## Peaks-Loop Step 0.8 — Job-shape detection (BLOCKING on LLM judgement)
+
+> **BLOCKING on LLM judgement.** Before Step 1 mode selection, Code MUST surface a Job-shape decision via `peaks code detect-job` and persist it to `.peaks/_runtime/<sessionId>/job-shape.json`. The CLI is a recorder + gate — the LLM makes the judgement; downstream steps call `read-job-shape` and refuse if missing. See `references/step-0-8-gate.md` for the full contract (LLM criteria, action sequence, hard rule red-line #10). Failure mode: skipping `peaks code detect-job` blocks the workflow at the next `read-job-shape` call (`JOB_SHAPE_NOT_DECIDED`).
+
+**v3.1.2 mechanical gates** (the recorder-only design was bypassed twice under load; the gate must be un-bypassable):
+
+1. **PreToolUse hook — `peaks code gate-step-08`.** Installed by `peaks workspace init` on the `Bash` matcher; checks `job-shape.json` presence + fail-closed backup regex. If `job-shape.json` exists AND `progress.json` exists, surfaces `Next: slice #N of M (<currentSlice>)` so the LLM cannot wake up cold.
+2. **Size-fear ban — `peaks code emit-handoff`.** Refuses to emit a final handoff while `remaining > 0` under Job mode. Pass `--force-under-job` only with explicit user approval.
+3. **On-disk slice progress — `peaks job progress`.** `peaks job checkpoint --state done` writes `progress.json`. `peaks job progress --job-id <jid> [--allow-missing]` is the canonical reader; `peaks code gate-step-08` also surfaces it on every Bash call.
+4. **Forced auto-compact — `--enforce-job-mode`.** `peaks code context-now --enforce-job-mode` returns `action: 'auto-compact-now'` at ≥ 0.85. **Job mode at ≥ 0.85 is MANDATORY auto-compact** — Code MUST call `peaks session auto-compact --execute` without confirmation.
+
+**Step 0.7 resume rule (read-FIRST):** on resume, `peaks code gate-step-08` reads `progress.json` first and surfaces `Next: slice #N of M (<currentSlice>)` so the orchestrator picks up at the right slice without re-reading the artifact tree.
+
+### Peaks-Loop Step N+2: Auto-compact at the warning line (v2.13.0 zero-pause contract)
+
+> **Zero-pause contract.** When context usage crosses the pre-compact threshold, peaks-loop **automatically fires `peaks session auto-compact --execute` — the LLM does NOT prompt the user to run `/compact` manually**. This is the single biggest UX regression vector in the system: a stale prose that says "ask the user to compact" will silently send the LLM into "wait for human" mode and stall the entire workflow. The v2.13.0 contract makes auto-compact a system responsibility, not a user action.
+
+**Thresholds (v2.13.0, replacing legacy 50/75/90):**
+
+| ratio zone | zone name | action |
+|---|---|---|
+| `< 0.85` | normal | skip — LLM keeps working, no action |
+| `0.85 ≤ ratio < 0.95` | **pre-compact zone** | `peaks session auto-compact --execute` fires **automatically** (deferred only if an in-flight sub-agent batch is still running; fires the moment the batch lands). The LLM does not prompt the user. |
+| `ratio ≥ 0.95` | **red-line (Karpathy §4 compact-red-line exception)** | synchronous gate — `peaks session auto-compact --execute` is invoked immediately; `peaks code context-now` returns `action: 'red-line'` and refuses to advance until ratio drops below 0.85. **Karpathy §4 treats this as an automatic exception** — the LLM cannot opt out. |
+
+**Probe primitive (single source of truth):** `peaks code context-now --json`. Do NOT use `peaks context check --prompt-size` (deprecated, pre-v2.13.0 surface; will silently under-report ratio). The CLI returns `{ ratio, action: 'ok' | 'soft-warn' | 'auto-compact-now' | 'red-line' }` — Code reads `action` and dispatches `peaks session auto-compact --execute` on `auto-compact-now` or `red-line` without any user confirmation.
+
+**Enforcement layers (defense in depth — no single layer is the gate):**
+
+1. `src/services/code/auto-compact-orchestrator.ts` — `evaluateAutoCompactDecision` default-returns `shouldCompact: true` for both `pre-compact` and `red-line` zones. The only deferral is `inFlightBatch.hasInFlightBatch` (D6.e); no LLM / human approval branch.
+2. `--enforce-job-mode` (v3.1.2) — Job mode elevates ≥0.85 to MANDATORY regardless of in-flight batch (see Step 0.8 §4 above).
+3. `peaks code gate-step-08` (PreToolUse hook) — surfaces `auto-compact-now` on every Bash call when ratio is in the zone, so the LLM cannot wake up cold and forget.
+4. The Karpathy §4 exception: `peaks session auto-compact --execute` is fired *by the orchestrator*, not by the user running `/compact`. If you find yourself about to write prose that says "ask the user to compact" or "prompt the user to run `/compact`", STOP — that is the regression.
+
+**Anti-pattern (regression marker — DO NOT introduce):** any of these strings in skills/* or comments signals the zero-pause contract has been broken:
+
+- "ask the user to compact"
+- "prompt the user to run `/compact`"
+- "the user should run `peaks session auto-compact` manually"
+- "the user is responsible for context management"
+- legacy pre-v2.13.0 thresholds (mid / seventy-five / ninety percent tiers; current is 0.85 / 0.95)
+
+If the prose audit (`peaks audit red-lines`) flags any of the above, the slice is **blocked** until the prose is rewritten.
+
 ## CLI Drift Index (sediment 2026-07-09)
 
 > **Reading guide:** Verified against peaks-loop 4.0.0-beta.6. Each drift below is annotated inline at the relevant step with a `> CLI reality check`. On `error: unknown option ...`, **read the inline reality check first** before guessing.

package/skills/peaks-code/references/sub-agent-dispatch.md

@@ -248,6 +248,36 @@ once the poller has read them.
 - AC-25..AC-32: G5 resource lifecycle (RL-1 batch counter, dispatch record schema, reducer dispose, slice archive, cancel dispose)
 - AC-33..AC-37: G6 heartbeat CLI, schema, poller, status line, E2E
 
+## D21 — LLM-side completion signal (mandatory)
+
+`peaks sub-agent dispatch` writes the record in `queued` state. The
+dispatcher has no other way to learn that the spawned Task tool
+actually returned. **The LLM runner MUST call `peaks sub-agent finalize`
+once per dispatched Task, in the post-completion branch** (after the
+Task tool's `tool_result` has been received). Without it, the record
+stays `queued, no-execution` forever.
+
+```sh
+# After each Task tool returns:
+peaks sub-agent finalize --request-id <rid> --outcome done
+
+# On Task failure:
+peaks sub-agent finalize --request-id <rid> --outcome failed --error "<msg>"
+
+# Crash-recovery sweep (only if the runner was interrupted and many
+# records are stuck in queued):
+peaks sub-agent finalize --all-stale --outcome done
+```
+
+`finalize` calls `markCompleted` (in dispatch-record-writer.ts), which
+transitions the record to the chosen status and unregisters the path
+from `active-dispatches.json`. The next runner does not see a stale
+ghost.
+
+This was added in slice 2026-07-17-D21 after 13 stale records were
+observed in the peaks-loop repo (`active-dispatches.json` would have
+grown unboundedly without this fix).
+
 ## How to apply
 
 When writing a SKILL.md that fans out sub-agents:

package/dist/services/agent/ecc-cache-service.d.ts

@@ -1,97 +0,0 @@
-/**
- * ECC cache service — Slice 3 of 4.0.0-beta.11.
- *
- * Drop-in replacement for the deleted `ecc-agent-service.ts`. The
- * pre-Slice-3 implementation shelled out to `npx ecc agent run ...`,
- * but the upstream `affaan-m/everything-claude-code` v2.0.0 release
- * has NO `ecc` binary — the repo is `agents/*.md` flat files plus
- * SKILL.md descriptors. The peaks-loop path is therefore download
- * + cache only; the LLM consumes cached `agents/*.md` directly
- * through `peaks ecc show <name>`.
- *
- * Six exports per RD §2:
- *   - setCacheDirPermissions
- *   - downloadToCache
- *   - readCacheManifest
- *   - listCachedAgents
- *   - readAgentSkill
- *   - cleanupStaleCache
- *
- * The cache layout is `~/.peaks/cache/ecc-installed.json` (manifest)
- * + `~/.peaks/cache/ecc-<sha>/agents/<name>.md`. The manifest is
- * the active-cache pointer; cleanupStaleCache iterates the on-disk
- * sha directories and decides based on the manifest's `fetchedAt`
- * (active) vs `mtimeMs` (orphan).
- *
- * Hard contracts (Karpathy #2 Simplicity First):
- *  - No subprocess plumbing. Network is `fetch()` only.
- *  - No factory; one module, six functions, six dependencies.
- *  - Strict selective extract: agents/*.md only, no symlinks, no
- *    `..`, no absolute paths, no devices.
- *  - D-009 fallback: parseFrontmatter throws on malformed input —
- *    wrap it in try/catch and synthesize `{name, description}`
- *    from the file name + first non-empty body line.
- *  - D-010 fallback: PRD's `ecc.tar.gz` asset URL does NOT exist
- *    upstream; try PRD first, fall back to GitHub's `tarball_url`
- *    on the release JSON.
- */
-export declare const ECC_REPO_OWNER = "affaan-m";
-export declare const ECC_REPO_NAME = "everything-claude-code";
-export type CacheManifest = {
-    version: string;
-    sha: string;
-    fetchedAt: string;
-    agents: string[];
-};
-export type DownloadResult = {
-    sha: string;
-    agents: number;
-};
-/**
- * Cache dir resolution — single source of truth. Tests inject
- * via `dirOverride` on the functions that take one.
- */
-export declare function resolveEccCacheDir(): string;
-export declare function resolveManifestPath(dirOverride?: string): string;
-export declare function resolveShaDir(sha: string, dirOverride?: string): string;
-export declare function resolveAgentsDir(sha: string, dirOverride?: string): string;
-/**
- * Best-effort chmod 0o700 on POSIX; no-op on Windows (NTFS uses
- * ACLs, not POSIX mode bits). Swallows errors with WARN so a
- * permissions failure never blocks the CLI.
- */
-export declare function setCacheDirPermissions(cacheDir: string): void;
-/**
- * Download ECC into `~/.peaks/cache/ecc-<sha>/agents/`. Returns
- * the resolved SHA + the number of agents extracted.
- *
- * Throws `Error('fetch-failed')` on network failure so the CLI
- * layer can render the manual-install instructions.
- */
-export declare function downloadToCache({ ref }?: {
-    ref?: string;
-}): Promise<DownloadResult>;
-export declare function readCacheManifest(): CacheManifest | null;
-export declare function listCachedAgents(): {
-    name: string;
-    description: string;
-}[];
-export declare function readAgentSkill(name: string): string | null;
-/**
- * 7-day TTL sweep over `ecc-<sha>/` directories.
- *
- * - Active cache (per manifest `sha`): use `fetchedAt` as the
- *   age source; remove if older than `retentionDays`.
- * - Orphan caches (any other `ecc-<40hex>` directory): use
- *   directory `mtimeMs` as the age source.
- * - If the active cache is removed, invalidate the manifest.
- *
- * Returns the absolute paths of the removed directories.
- */
-export declare function cleanupStaleCache({ retentionDays, nowMs, dirOverride, }: {
-    retentionDays: number;
-    nowMs: number;
-    dirOverride?: string;
-}): {
-    removed: string[];
-};