peaks-loop 4.0.49 → 4.0.50

package/scripts/install-skills.mjs

@@ -256,10 +256,6 @@ function validateConfigPath(root, peaksRoot, configPath, label) {
   }
 }
 
-function validateProjectConfigPaths(projectRoot, peaksRoot, configPath) {
-  validateConfigPath(projectRoot, peaksRoot, configPath, 'Project');
-}
-
 function validateUserConfigPaths(userRoot, peaksRoot, configPath) {
   validateConfigPath(userRoot, peaksRoot, configPath, 'User');
 }
@@ -345,10 +341,6 @@ function writeFileAtomically(configPath, content, errorMessage, validateBeforeWr
   }
 }
 
-function writeProjectConfig(projectRoot, peaksRoot, configPath, content) {
-  writeFileAtomically(configPath, content, 'Project config path changed during write', () => validateProjectConfigPaths(projectRoot, peaksRoot, configPath));
-}
-
 function writeUserConfig(userRoot, peaksRoot, configPath, content) {
   writeFileAtomically(configPath, content, 'User config path changed during write', () => validateUserConfigPaths(userRoot, peaksRoot, configPath));
 }
@@ -374,6 +366,16 @@ function resolveProjectRoot(options) {
  * + emits a stderr warning. The dispatch is conservative: the env-var
  * overrides `PEAKS_CLAUDE_SKILLS_DIR` / `PEAKS_CLAUDE_OUTPUT_STYLES_DIR`
  * continue to work, and the legacy default is preserved.
+ *
+ * 2026-09-15 (D12 fix): `hermes` and `openclaw` have install profiles in
+ * `IDE_SKILL_INSTALL_PROFILES` but were absent from this table. A profile
+ * that no detector can ever return is reachable only through the
+ * every-platform fan-out — i.e. it is installed for users who do NOT have
+ * the tool and skipped for nobody. Both are listed here now, so detection
+ * and installation answer the same question with the same table.
+ *
+ * This table is ALSO the presence oracle for `isPlatformPresent` below: a
+ * directory here in the project root means the user has that tool.
  */
 export const IDE_DETECTION_DIRS = [
   { id: 'claude-code', dir: '.claude' },
@@ -384,23 +386,33 @@ export const IDE_DETECTION_DIRS = [
   { id: 'qoder', dir: '.qoder' },
   { id: 'tongyi-lingma', dir: '.tongyi-lingma' },
   { id: 'zcode', dir: '.zcode' },
+  { id: 'hermes', dir: '.hermes' },
+  { id: 'openclaw', dir: '.openclaw' },
 ];
 
 /**
  * Per-IDE skill install paths. Per peaks-loop tenet
  * "minimal-user-operation" (2026-06-11), the user should
  * never have to run a per-platform install command — the
- * `npm i -g peaks-loop` postinstall iterates ALL of these
- * and symlinks the peaks-* skill family to every platform
- * the user might be on.
+ * `npm i -g peaks-loop` postinstall iterates the platforms
+ * the user HAS and symlinks the peaks-* skill family into each
+ * (see `isPlatformPresent`; D9/2026-09-15 made "has" load-bearing).
  *
  * 1.x had only `claude-code` (the other 5 entries were
  * `null`); real Trae users reported the Trae skill
  * directory was never populated. 2.0 fixes this by giving
- * all 8 platforms canonical install paths.
+ * every platform a canonical install path.
  */
 export const IDE_SKILL_INSTALL_PROFILES = {
   'claude-code': {
+    // `alwaysPresent` — see `isPlatformPresent`. Declared HERE, in the
+    // vendor's own row, rather than as an `ideId === 'claude-code'` branch in
+    // the consumer: the guard at
+    // `tests/unit/runtime/vendor-neutral-identity-guard.test.ts` pins identity
+    // DECISIONS to the vendor declarations, and a comparison in the consumer
+    // is exactly the re-injection shape it exists to catch. A future vendor
+    // opts into the same policy by setting this field.
+    alwaysPresent: true,
     skillsDir: join(homedir(), '.claude', 'skills'),
     outputStylesDir: join(homedir(), '.claude', 'output-styles'),
     agentsDir: join(homedir(), '.claude', 'agents'),
@@ -489,6 +501,46 @@ function resolveIdeSkillInstallProfile(ideId) {
   return IDE_SKILL_INSTALL_PROFILES[ideId] ?? null;
 }
 
+/**
+ * Is this platform actually installed FOR? (D9 fix, 2026-09-15.)
+ *
+ * Before this gate, the postinstall ran `mkdirSync(targetRoot, {recursive:
+ * true})` for ALL 10 profiles unconditionally, so `npm i -g peaks-loop` created
+ * `~/.hermes`, `~/.openclaw`, `~/.qoder`, `~/.tongyi-lingma` and `~/.zcode` in
+ * the home of a user who has never installed those tools. The peaks-loop tenet
+ * is "the user never has to run a per-platform install command" — it is NOT
+ * "peaks-loop guesses which tools you have". Creating a directory for a tool
+ * the user does not own is the tenet misread, and it is visible on disk.
+ *
+ * Present means EITHER:
+ *   - the tool's marker directory exists in the project root (the same
+ *     directory `detectInstalledIdeId` consults above), OR
+ *   - the tool's own home directory (`~/.<tool>`, derived from its profile)
+ *     already exists on this machine.
+ *
+ * `claude-code` is unconditionally present: it is peaks-loop's primary runtime
+ * and the documented legacy install target, so a machine with no `~/.claude`
+ * yet still gets the trees the user is installing peaks-loop for. That fact is
+ * declared as `alwaysPresent: true` IN THE VENDOR'S OWN PROFILE ROW — not as an
+ * `ideId === 'claude-code'` branch here. This file sits outside the adapter
+ * layer, so an identity comparison in it is the re-injection shape
+ * `tests/unit/runtime/vendor-neutral-identity-guard.test.ts` pins; reading the
+ * vendor's declaration keeps the policy in one place and vendor-neutral.
+ *
+ * A named target bypasses this gate entirely — `options.targetRoot`,
+ * `options.ideId`, and the `PEAKS_<TOOL>_SKILLS_DIR` env vars are callers who
+ * have already said which platform they mean; guessing a second time there
+ * would break the 1.x back-compat contract that slice 2026-06-12 restored.
+ */
+function isPlatformPresent(ideId, profile, projectRoot) {
+  if (profile.alwaysPresent === true) return true;
+  const detection = IDE_DETECTION_DIRS.find((entry) => entry.id === ideId);
+  if (detection !== undefined && projectRoot !== null && existsSync(join(projectRoot, detection.dir))) {
+    return true;
+  }
+  return existsSync(dirname(profile.skillsDir));
+}
+
 function warnUnverifiedIde(ideId, projectRoot) {
   process.stderr.write(
     `peaks install-skills: IDE '${ideId}' has no skillInstall profile declared; ` +
@@ -540,29 +592,26 @@ export function installUserConfig(options = {}) {
   return writeMergedConfig(configPath, 'User', createConfigDefaults(options.packageRoot), (content) => writeUserConfig(userRoot, peaksRoot, configPath, content));
 }
 
-export function installProjectConfig(options = {}) {
-  if (process.env.PEAKS_SKIP_SKILL_INSTALL === '1' || process.env.PEAKS_SKIP_PROJECT_CONFIG_INSTALL === '1') {
-    return createConfigResult({ skipped: true });
-  }
-
-  const projectRoot = resolveProjectRoot(options);
-  if (!projectRoot) {
-    return createConfigResult({ skipped: true });
-  }
-
-  const peaksRoot = resolve(projectRoot, '.peaks');
-  const configPath = resolve(peaksRoot, 'config.json');
-  if (!isInsidePath(configPath, projectRoot)) {
-    throw new Error('Project config path must stay inside the project root');
-  }
-
-  if (!existsSync(peaksRoot)) {
-    mkdirSync(peaksRoot, { recursive: true });
-  }
-  validateProjectConfigPaths(projectRoot, peaksRoot, configPath);
-
-  return writeMergedConfig(configPath, 'Project', createConfigDefaults(options.packageRoot), (content) => writeProjectConfig(projectRoot, peaksRoot, configPath, content));
-}
+/*
+ * D11 (2026-09-15): `installProjectConfig` — plus its two private helpers
+ * `writeProjectConfig` and `validateProjectConfigPaths` — was DELETED here.
+ *
+ * It was dead: definition + `export`, and zero call sites in the whole repo
+ * (verified by a repo-wide grep for the identifier, excluding node_modules
+ * and dist). The `PEAKS_SKIP_PROJECT_CONFIG_INSTALL` env var existed only to
+ * disable it.
+ *
+ * Deleted rather than wired, because wiring it would be the bigger defect:
+ * `npm i -g peaks-loop` executed from inside a user's repo would write
+ * `<project>/.peaks/config.json` as a side effect of a GLOBAL install. The
+ * project-level config is owned by `peaks workspace init` and the config
+ * service at runtime; a postinstall reaching into the current working
+ * directory to create project state is the opposite of the "minimal user
+ * operation" tenet — an operation the user never asked for.
+ *
+ * The user-config sibling (`installUserConfig`, below) is live and is what
+ * the postinstall actually calls.
+ */
 
 export function installBundledSkills(options = {}) {
   const packageRoot = resolvePackageRoot(options);
@@ -684,6 +733,40 @@ export function installBundledSkills(options = {}) {
   return { installed, skipped };
 }
 
+/**
+ * DISPATCH STRATEGY — the three paths in this file, and why they differ
+ * (D10, written down 2026-09-15).
+ *
+ * This script installs three kinds of asset, and each one resolves its target
+ * by a different rule. That was undocumented and untested; it is now
+ * documented here and each rule is stated with its reason.
+ *
+ *   1. SKILLS  (`installBundledSkillsForAllPlatforms`)
+ *      Fan out to every platform the user HAS (`isPlatformPresent`).
+ *      Reason: a skill directory is per-tool; the same skill is legitimately
+ *      wanted in several tools at once, and peaks cannot know which tool the
+ *      user will open next. Fan-out is the tenet; presence is the licence.
+ *
+ *   2. AGENTS  (`installBundledAgentsForAllPlatforms`)
+ *      Fan out to present platforms, INTERSECTED with the profiles that
+ *      declare `agentsDir`. Reason: sub-agent loaders are not a universal
+ *      concept — only 6 of 10 profiles have one. The intersection is the fan
+ *      of (1) with a capability filter, not a third rule.
+ *
+ *   3. OUTPUT STYLES (`installBundledOutputStyles`, this function)
+ *      ONE target: the IDE detected in the project root, else the legacy
+ *      `~/.claude/output-styles`. Reason: an output style is not a
+ *      per-tool asset — it is registered as THE active style for the
+ *      session by writing a single `outputStyle` key into
+ *      `~/.claude/settings.json` (`installBundledOutputStyleDefault`). A
+ *      second copy in `~/.trae/output-styles` would be a file nothing reads
+ *      and a setting no one consults; fanning it out would be storing the
+ *      same answer in ten places and reading it from one.
+ *
+ * So: (1) and (2) share one predicate and differ only by capability; (3) is
+ * deliberately single-target, and this comment is the reason the brief asked
+ * for. If a future platform needs a different rule, state it here.
+ */
 export function installBundledOutputStyles(options = {}) {
   const packageRoot = resolvePackageRoot(options);
   const outputStylesRoot = join(packageRoot, 'output-styles');
@@ -1034,12 +1117,18 @@ export function installBundledAgents(options = {}) {
 }
 
 /**
- * Per-platform fan-out — iterate ALL 8 IdeIds and call
- * `installBundledAgents` for each platform that has an `agentsDir` profile
- * field. Only `claude-code` ships with `agentsDir` set today; the other 7
- * platforms return `installed: []` from their profile lookup. Future
- * platforms can add an `agentsDir` field to their `IDE_SKILL_INSTALL_PROFILES`
- * entry to opt in.
+ * Per-platform fan-out — iterate the platforms the user HAS and call
+ * `installBundledAgents` for each one that also declares an `agentsDir`
+ * profile field. 6 of the 10 profiles declare `agentsDir` today
+ * (claude-code, trae, trae-cn, codex, cursor, zcode); the other 4 have no
+ * sub-agent loader to write into and are skipped by construction. A future
+ * platform opts in by adding `agentsDir` to its
+ * `IDE_SKILL_INSTALL_PROFILES` entry.
+ *
+ * D9/D10 fix (2026-09-15): the platform set is filtered by
+ * `isPlatformPresent` (same predicate as the skills fan-out), so this no
+ * longer creates `~/.trae/agents`, `~/.codex/agents`, … for tools the user
+ * does not have.
  *
  * Per peaks-loop tenet "minimal-user-operation" (2026-06-11): the user
  * should never have to run a per-platform install command. Symlink /
@@ -1047,8 +1136,10 @@ export function installBundledAgents(options = {}) {
  * failure doesn't block the others.
  */
 export function installBundledAgentsForAllPlatforms(options = {}) {
+  const projectRoot = resolveProjectRoot(options);
   const platforms = Object.entries(IDE_SKILL_INSTALL_PROFILES)
-    .filter(([, profile]) => typeof profile.agentsDir === 'string');
+    .filter(([, profile]) => typeof profile.agentsDir === 'string')
+    .filter(([ideId, profile]) => isPlatformPresent(ideId, profile, projectRoot));
   const perPlatform = [];
   for (const [ideId, profile] of platforms) {
     try {
@@ -1091,29 +1182,37 @@ export function installBundledAgentsForAllPlatforms(options = {}) {
 }
 
 /**
- * Per-platform fan-out — iterate ALL 8 IdeIds and call
+ * Per-platform fan-out — iterate the platforms the user actually HAS and call
  * `installBundledSkills` for each. Per peaks-loop tenet
  * "minimal-user-operation" (2026-06-11): the user should
  * never have to run a per-platform install command. The
  * 1.x postinstall only handled the auto-detected single
  * IDE; 2.0 fixes this so the peaks-* skill family is
- * symlinked to every platform the user might be on.
+ * symlinked to every platform the user is on.
+ *
+ * D9/D10 fix (2026-09-15): the set is filtered by `isPlatformPresent`, not
+ * "all 10 profiles". See that helper for why, and see the DISPATCH STRATEGY
+ * note above `installBundledOutputStyles` for how this fan-out relates to the
+ * other two dispatch paths in this file.
  *
  * Returns an array of { ideId, skillsDir, installed, skipped }
  * per platform. Symlink failures are soft (logged to stderr,
  * never throw) so one platform's failure doesn't block the
- * other 7.
+ * others.
  */
 export function installBundledSkillsForAllPlatforms(options = {}) {
-  const platforms = Object.keys(IDE_SKILL_INSTALL_PROFILES);
+  const projectRoot = resolveProjectRoot(options);
+  const platforms = Object.keys(IDE_SKILL_INSTALL_PROFILES).filter((ideId) =>
+    isPlatformPresent(ideId, IDE_SKILL_INSTALL_PROFILES[ideId], projectRoot)
+  );
   const perPlatform = [];
   // Back-compat precedence (regression fix 2026-06-12,
   // slice 2026-06-12-postinstall-1x-detector-tdd):
-  // when iterating the 8 platforms, the claude-code install
+  // when iterating the present platforms, the claude-code install
   // must still honor the PEAKS_CLAUDE_SKILLS_DIR env var
-  // (the legacy back-compat surface from 1.x). The other 7
+  // (the legacy back-compat surface from 1.x). The other
   // platforms use their per-IDE profile paths unconditionally.
-  // Without this fix the 8-IDE fan-out regresses the
+  // Without this fix the fan-out regresses the
   // `peaks install-skills` env-var override contract that
   // user CI / 1.x → 2.0 migration scripts depend on.
   const claudeEnv = process.env.PEAKS_CLAUDE_SKILLS_DIR;
@@ -1298,10 +1397,12 @@ export async function autoUpgrade1xProjectIfPresent(options = {}) {
 if (process.argv[1] !== undefined && import.meta.url === pathToFileURL(resolve(process.argv[1])).href) {
   try {
     // 2.0 fix for the 1.x Trae bug (per real user feedback
-    // 2026-06-11): iterate ALL 8 platforms, not just the
-    // auto-detected one. Per the "minimal-user-operation"
-    // tenet, the user should never have to run a
-    // per-platform install command.
+    // 2026-06-11): iterate every platform the user HAS, not just the
+    // one auto-detected in the project root. Per the
+    // "minimal-user-operation" tenet, the user should never have to run a
+    // per-platform install command — S6 (2026-09-15) narrowed "every" from
+    // "all 10 profiles" to `isPlatformPresent`, because creating a home
+    // directory for a tool the user does not own is that tenet misread.
     const perPlatform = installBundledSkillsForAllPlatforms();
     let totalInstalled = 0;
     for (const p of perPlatform) {

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

@@ -258,7 +258,6 @@ Index of every `references/` file in this skill. Read on demand.
 | `references/artifact-per-request.md` | QA 3-file per-request artifact contract. |
 | `references/browser-validation-contracts.md` | Browser contracts (1) + (2) + AskUserQuestion. |
 | `references/codegraph-regression-focus.md` | Codegraph regression-surface evidence. |
-| `references/command-migration.md` | Legacy command migration map. |
 | `references/external-capability-guidance.md` | Playwright / Chrome DevTools / Agent Browser. |
 | `references/openspec-validation-gate.md` | OpenSpec validation + archive gate. |
 | `references/qa-compact-handoff.md` | QA compact handoff capsule. |

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

@@ -315,7 +315,6 @@ Index of every `references/` file in this skill. Read on demand.
 | `references/artifact-per-request.md` | RD per-request artifact + per-slice vs per-session scope. |
 | `references/browser-self-test-contracts.md` | Browser self-test contracts (1) + (2). |
 | `references/codegraph-project-analysis.md` | Codegraph local analysis (untrusted evidence). |
-| `references/command-migration.md` | Legacy command migration map. |
 | `references/compact-handoff.md` | RD compact handoff capsule. |
 | `references/external-references.md` | External 3rd-party inventory. |
 | `references/frontend-project-generation.md` | React + Vite + shadcn/ui default. |

package/skills/peaks-code/SKILL.md

@@ -44,8 +44,9 @@ denied again after a long pause. That is the gate resetting, not you regressing.
 
 `peaks-code` is a **code-domain long-task loop engineering orchestrator; not a general-purpose orchestrator.**
 
-This is RL-8 from the Loop Engineering crystallization design
-(`docs/superpowers/specs/2026-07-07-peaks-loop-loop-engineering-crystallization-design.md` §0.4 and §10 RL-8).
+This is RL-8, stated in `.peaks/standards/loop-engineering-guidelines.md` (the 2026-07-07
+crystallization design spec that first wrote it, §0.4 and §10, was retired from the tree in
+commit `e6e35842`).
 The boundary is closed under this slice:
 
 - **In scope:** end-to-end code-domain workflows — repository scanning, RD planning, code implementation via RD, QA verification, UI changes inside a code repo, source-control handoff, and code-repo context packaging. Coordinated role skills: `peaks-prd`, `peaks-rd`, `peaks-qa`, `peaks-ui`, `peaks-sc`, `peaks-txt`.
@@ -123,7 +124,7 @@ STOP. Run:
 peaks sub-agent dispatch rd --prompt '<your task>' --graph-node <nid> --workflow-id <wid> --request-id <rid> --project . --batch-id <uuid> --json
 ```
 
-`--graph-node <nid>` is REQUIRED (RD §4 D4c). Prepare the node first: `peaks workflow init --skill peaks-code`, then `peaks workflow node prepare --workflow <wid> --node <nid> --kind dispatch`. The RD sub-agent owns the actual `Edit`/`Write`/`MultiEdit` tool calls against source code. The orchestrator only emits the dispatch request.
+`--graph-node <nid>` and `--workflow-id <wid>` are OPTIONAL. Slice 4.0.8 RD §4 D4c made `--graph-node` required; it was relaxed again in `provisionDispatchNode` (`src/services/workflow/provision-dispatch-node.ts`) because the requirement was enforced but never validated — nothing downstream read the node, the record writer's graph transition is best-effort, and the documented "prepare a node first" ritual had no viable first step (`peaks workflow node prepare` never persisted the node). Passing neither flag now provisions the node and the graph on demand, so a dispatch works in a project with no graph infrastructure. When you DO pass a node, the binding is real: `provisionDispatchNode` writes it into `graphs/<wid>.json`. The RD sub-agent owns the actual `Edit`/`Write`/`MultiEdit` tool calls against source code. The orchestrator only emits the dispatch request.
 
 **Anti-pattern:** directly calling `Edit`/`Write`/`MultiEdit` on `src/**` from the orchestrator session because "the change is tiny" / "it's just one line" / "the dispatch overhead is too high" / "the LLM feels confident". None of these override the Code-Gate; the probe + the hook both fail-closed.
 
@@ -138,7 +139,7 @@ peaks sub-agent dispatch rd --prompt '<your task>' --graph-node <nid> --workflow
 **Integration surfaces:** `peaks code run --24h` / `peaks dashboard long-run --since 24h` / `peaks session 24h-mode state|transition|attempts|reset`.
 
 **Red lines (peaks-code side):**
-- No auto-compact prose ban: never write "ask the user to compact" / "prompt the user to run `/compact`" / "the user should run `peaks code auto-compact` manually" / "the user is responsible for context management" / legacy 50/75/90 percent tiers. **0.85 / 0.95 contract is mandatory.**
+- No auto-compact prose ban: never write "ask the user to compact" / "prompt the user to run `/compact`" / "the user should run `peaks code auto-compact` manually" / "the user is responsible for context management" / legacy 50/75/90 percent tiers. **Tier contract (standard mode): `auto-fire` ≥ 0.80 / `pre-compact` ≥ 0.85 / `red-line` ≥ 0.95. Compact on the FIRST of these to arrive — 0.80, not 0.85.**
 - SquabbyZ sole-author rule: no `Co-Authored-By: Claude/Anthropic` trailer.
 - 24h mode is a flag on `peaks-code`; MUST NOT introduce a sibling `peaks-24h` skill or competing top-level verb.
 
@@ -185,7 +186,7 @@ Before the first planning action, run `peaks fresh-context preflight --prompt "<
 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` AND `progress.json` exist, 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.
-4. **Forced auto-compact — `peaks code context-now`.** It returns `action: 'auto-compact-now'` at ≥ 0.85. **≥ 0.85 is MANDATORY auto-compact in every mode (single-rid included)** — Code MUST call `peaks code auto-compact` without confirmation. `--enforce-job-mode` (v3.1.2) only labels the run `jobMode=true`; the ≥ 0.85 downgrade that used to apply to single-rid sessions was removed 2026-09-12.
+4. **Forced auto-compact — two probes, two thresholds.** `peaks skill presence` (the every-turn probe) reports `action: 'auto-fire'` at ≥ 0.80 and `action: 'pre-compact'` at ≥ 0.85; `peaks code context-now` reports `action: 'auto-compact-now'` at ≥ 0.85 — it has no 0.80 tier. **The earlier of the two governs: at ≥ 0.80 the run is already MANDATORY auto-compact in every mode (single-rid included)** — Code MUST call `peaks code auto-compact` without confirmation, and MUST NOT wait for 0.85. `--enforce-job-mode` (v3.1.2) only labels the run `jobMode=true`; the ≥ 0.85 downgrade that used to apply to single-rid sessions was removed 2026-09-12.
 
 **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.
 
@@ -197,24 +198,25 @@ Before the first planning action, run `peaks fresh-context preflight --prompt "<
 
 > **Zero-pause contract.** When context usage crosses the pre-compact threshold, peaks-loop **automatically fires `peaks code auto-compact` — the LLM does NOT prompt the user to run `/compact` manually**. Stale prose that says "ask the user to compact" silently stalls the 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):**
+**Thresholds (standard mode, replacing legacy 50/75/90; `partial` / 24h mode moves every line down to 0.65 / 0.70 / 0.85):**
 
 | ratio zone | zone name | action |
 |---|---|---|
-| `< 0.85` | normal | skip — LLM keeps working |
-| `0.85 ≤ ratio < 0.95` | **pre-compact zone** | `peaks code auto-compact` fires **automatically** (deferred only when in-flight sub-agent batch is running; fires the moment the batch lands). The LLM does not prompt the user. |
+| `< 0.80` | normal | skip — LLM keeps working |
+| `0.80 ≤ ratio < 0.85` | **auto-fire zone** | `peaks skill presence` returns `action: 'auto-fire'` here: peaks-loop preempts on its own, without asking the LLM to decide. The LLM MUST run `peaks code auto-compact` and MUST NOT wait for 0.85. **This is the tier that fires first, so this row — not the 0.85 row — is the real trigger line.** `peaks code context-now` has no 0.80 tier and still reports `soft-warn` here, so its `action` alone under-reports this band. |
+| `0.85 ≤ ratio < 0.95` | **pre-compact zone** | `peaks code auto-compact` fires **automatically** (deferred only when in-flight sub-agent batch is running; fires the moment the batch lands). The LLM does not prompt the user. In practice peaks-loop already fired at the 0.80 tier above, so this band is today the "already fired" zone; `peaks code context-now` reports `action: 'auto-compact-now'` from 0.85 up. |
 | `ratio ≥ 0.95` | **red-line (Karpathy §4)** | `peaks code auto-compact` invoked immediately; `peaks code context-now` returns `action: 'red-line'`. **Since 4.0.47 the red line REQUESTS the compaction and says it is waiting — it does NOT block sub-agent dispatch, and it does not refuse to advance.** Keep working and re-probe with `peaks code context-now`; the harness performs the compaction, and nothing peaks-loop can do lowers the ratio on its own, so blocking here was a deadlock rather than a gate. If the ratio keeps climbing and no compaction lands, report that and hand control back — do not stall. `--bypass-red-line` is a no-op. |
 
 **Probe primitive (single source of truth):** `peaks code context-now --json`. Do NOT use `peaks context check --prompt-size` (deprecated, will silently under-report ratio). Returns `{ ratio, action: 'ok' | 'soft-warn' | 'auto-compact-now' | 'red-line' }` — Code reads `action` and dispatches `peaks code auto-compact` on `auto-compact-now` or `red-line` without user confirmation.
 
 **Enforcement layers (defense in depth):**
 1. `src/services/code/auto-compact-orchestrator.ts` — `evaluateAutoCompactDecision` default-returns `shouldCompact: true` for both `pre-compact` and `red-line`. Only deferral is `inFlightBatch.hasInFlightBatch` (D6.e); no LLM/human approval branch.
-2. `peaks code context-now` — ≥ 0.85 is MANDATORY (`auto-compact-now`) in every mode; `--enforce-job-mode` no longer gates that (2026-09-12). Only an in-flight sub-agent batch defers it.
+2. `peaks skill presence` — ≥ 0.80 is MANDATORY (`auto-fire`) in every mode; this probe runs every turn, so it is the one that cannot be forgotten. `peaks code context-now` — ≥ 0.85 is MANDATORY (`auto-compact-now`) in every mode; `--enforce-job-mode` no longer gates that (2026-09-12). Only an in-flight sub-agent batch defers it.
 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. Karpathy §4 exception: `peaks code auto-compact` is fired *by the orchestrator*, not by the user. If you find yourself about to write "ask the user to compact" / "prompt the user to run `/compact`", STOP — that is the regression.
 
 **Anti-pattern (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 code auto-compact` manually" / "the user is responsible for context management" / legacy mid/seventy-five/ninety percent tiers (current is 0.85 / 0.95).
+- "ask the user to compact" / "prompt the user to run `/compact`" / "the user should run `peaks code auto-compact` manually" / "the user is responsible for context management" / legacy mid/seventy-five/ninety percent tiers (current is 0.80 auto-fire / 0.85 pre-compact / 0.95 red-line).
 
 If the prose audit (`peaks audit red-lines`) flags any of the above, the slice is **blocked** until the prose is rewritten.
 

package/skills/peaks-code/references/periodic-checkpoint.md

@@ -72,10 +72,10 @@ This step is strictly IDE-agnostic. The LLM calls the peaks CLI; no IDE-specific
 
 ## Companion surface — auto-compact (zero-pause)
 
-When the runner crosses the v2.13.0 auto-compact thresholds (0.85 pre-compact / 0.95 red-line), `peaks session checkpoint` is NOT enough on its own — the LLM must also fire `peaks code auto-compact` (or wait for the in-band PreToolUse hook at ratio ≥ 0.95 to compact the runner itself). See:
+When the runner crosses the v2.13.0 auto-compact thresholds (0.80 auto-fire / 0.85 pre-compact / 0.95 red-line), `peaks session checkpoint` is NOT enough on its own — the LLM must also fire `peaks code auto-compact` (or wait for the in-band PreToolUse hook at ratio ≥ 0.95 to compact the runner itself). See:
 
 - `peaks code auto-compact` — orchestrator that writes the convergence plan + dispatches the compact pathway
 - `peaks code auto-compact` — the PreToolUse hook entrypoint fired by `.claude/settings.local.json` (slice 2026-07-02-auto-compact-zero-pause)
 - `.peaks/memory/2026-06-27-auto-compact-design.md` — zero-human-intervention design rationale
 
-The two surfaces compose: `peaks session checkpoint` persists the context state, `peaks code auto-compact` collapses the runner's window. The LLM fires both in the 0.85–0.95 zone; the hook fires alone at ≥ 0.95.
+The two surfaces compose: `peaks session checkpoint` persists the context state, `peaks code auto-compact` collapses the runner's window. The LLM fires both from the 0.80 auto-fire line up (that is the tier `peaks skill presence` reports first); the 0.85–0.95 band is the "already fired" zone, and the hook fires alone at ≥ 0.95.

package/skills/peaks-code/references/runbook.md

@@ -299,6 +299,9 @@ peaks code emit-handoff --project <repo> --job-id <jid> --json
 
 # v3.1.2 forced auto-compact: when --enforce-job-mode is set OR
 # job-shape.json says isJob=true, ≥0.85 is MANDATORY auto-compact.
+# The trigger line is actually 0.80, not 0.85: `peaks skill presence`
+# reports action='auto-fire' from ≥0.80 and that tier is already mandatory
+# in every mode, so context-now's 0.85 is the *second* line to arrive.
 # Code MUST call this without confirmation under Job mode.
 peaks code context-now --project <repo> --enforce-job-mode --json
 peaks code auto-compact --project <repo> --json

package/skills/peaks-code/references/session-overload-signal-index.md

@@ -15,8 +15,8 @@ the lookup table the LLM must consult in lieu of intuition.
 
 | # | Signal source | Threshold | File / CLI | LLM action |
 |---|---|---|---|---|
-| 1 | prompt size (main session) | 50% / 75% / 80% / 90% | `src/services/context/threshold.ts`; probe via `peaks code context-now` | soft-warn at 50%; consider compact at 75%; MUST NOT auto-compact mid-batch (D6.e); Job mode ≥ 0.85 ⇒ MANDATORY `peaks code auto-compact` |
-| 2 | auto-compact zone | 0.85 pre-compact / 0.95 red-line | `src/services/code/auto-compact-orchestrator.ts`; `--enforce-job-mode` flag | Auto-fires `peaks code auto-compact`; LLM MUST NOT prompt user to compact (zero-pause contract v2.13.0) |
+| 1 | prompt size (main session) | 50% / 75% / 80% / 90% | `src/services/context/threshold.ts`; probe via `peaks code context-now` | soft-warn at 50%; consider compact at 75%; MUST NOT auto-compact mid-batch (D6.e); ≥ 0.80 (`auto-fire`) ⇒ MANDATORY `peaks code auto-compact` |
+| 2 | auto-compact zone | 0.80 auto-fire / 0.85 pre-compact / 0.95 red-line | `src/services/code/auto-compact-orchestrator.ts`; `--enforce-job-mode` flag | Auto-fires `peaks code auto-compact`; the 0.80 `auto-fire` tier is the one that fires first (`peaks skill presence` reports it); LLM MUST NOT prompt user to compact (zero-pause contract v2.13.0) |
 | 3 | sub-agent dispatch prompt size | 50% / 75% / 80% | `src/services/context/context-guard.ts`; `peaks sub-agent-dispatch-guard` PreToolUse hook | soft-warn at 50%; CONTEXT_NEAR_LIMIT at 75%; hard-reject at 80% (CLI + hook double-guard) |
 | 4 | statusline compact bar | visual | `src/services/compact-statusline/compact-statusline-service.ts` | ambient UI; surfaces queued/preparing/compacting/verifying/completed/failed/stalled |
 | 5 | in-flight batch deferral | D6.e | `src/services/code/auto-compact-modes.ts` | defer compact until batch lands (NOT "new session") |
@@ -44,6 +44,8 @@ LLM senses context pressure
   │   ├─ 0.75 ≤ ratio < 0.85 → compact-zone candidate
   │   │     ├─ Job mode → MUST auto-compact now
   │   │     └─ non-Job  → wait for next idle turn, then compact
+  │   ├─ 0.80 ≤ ratio < 0.85 → auto-fire zone; `peaks skill presence` reports
+  │   │     `action: 'auto-fire'` → auto-compact MUST fire (do NOT wait for 0.85)
   │   ├─ 0.85 ≤ ratio < 0.95 → pre-compact zone; auto-compact MUST fire
   │   └─ ratio ≥ 0.95       → red-line; compact REQUESTED, dispatch NOT blocked (Karpathy §4)
   │                                 keep working, re-probe, do not stall

package/skills/peaks-code/references/startup-sequence.md

@@ -31,7 +31,7 @@ After autonomous work (RD, QA, security, perf), invoke peaks-final-review for 4-
 
 ### Peaks-Loop Step N+2: Main-session context monitor (D6 + slice 2026-07-02)
 
-After every 4th tool call, probe via `peaks code context-now --project <repo> --json`. Thresholds: 50% / **0.85 pre-compact / 0.95 red-line** (v2.13.0). **In Job mode ≥ 0.85 is MANDATORY auto-compact** (`peaks code auto-compact`). Pass `--enforce-job-mode` for single-rid. **≥ 0.95** red line: next Bash/Task fires `peaks code auto-compact`. **Karpathy §4 exception**: compact red line keeps runner alive — zero-intervention wins; LLM MUST NOT ask user to run `/compact`. Honor `--in-flight-batch` (D6.e).
+After every 4th tool call, probe via `peaks code context-now --project <repo> --json`. Thresholds: 50% / **0.80 auto-fire / 0.85 pre-compact / 0.95 red-line** (v2.13.0). **At ≥ 0.80 (`auto-fire`, the tier `peaks skill presence` reports every turn) auto-compact is MANDATORY in every mode** (`peaks code auto-compact`). Pass `--enforce-job-mode` for single-rid. **≥ 0.95** red line: next Bash/Task fires `peaks code auto-compact`. **Karpathy §4 exception**: compact red line keeps runner alive — zero-intervention wins; LLM MUST NOT ask user to run `/compact`. Honor `--in-flight-batch` (D6.e).
 
 ### Peaks-Loop Step 0: Anchor the workflow (MANDATORY FIRST ACTIONS — no bail-out)
 
@@ -65,7 +65,7 @@ The CLI is a **recorder + gate** for job-shape (the LLM judges). LLM calls `peak
 
 **v3.1.2 mechanical gates** (recorder-only was bypassed twice):
 
-PreToolUse hook on `peaks code gate-step-08`; size-fear ban on `peaks code emit-handoff`; forced auto-compact at ≥ 0.85 in Job mode; on-disk slice progress via `peaks job checkpoint` (canonical reader `peaks job progress --job-id <jid>`). Full mechanics (judgement criteria, hook table, backup-regex rationale, hook wiring) at `references/step-0-8-gate.md`.
+PreToolUse hook on `peaks code gate-step-08`; size-fear ban on `peaks code emit-handoff`; forced auto-compact from ≥ 0.80 (`auto-fire`, every mode); on-disk slice progress via `peaks job checkpoint` (canonical reader `peaks job progress --job-id <jid>`). Full mechanics (judgement criteria, hook table, backup-regex rationale, hook wiring) at `references/step-0-8-gate.md`.
 
 ### Peaks-Loop Step 0.81 — per-slice 收尾
 

package/skills/peaks-code/references/step-0-8-gate.md

@@ -45,7 +45,7 @@ Refuses to emit a final handoff while `remaining > 0` under Job mode. Pass `--fo
 
 ### 3. Forced auto-compact — `--enforce-job-mode`
 
-`peaks code context-now --enforce-job-mode` (auto-enabled when `job-shape.json` says `isJob=true`) returns `action: 'auto-compact-now'` at ≥ 0.85; Code MUST call `peaks code auto-compact` without confirmation.
+`peaks code context-now --enforce-job-mode` (auto-enabled when `job-shape.json` says `isJob=true`) returns `action: 'auto-compact-now'` at ≥ 0.85; Code MUST call `peaks code auto-compact` without confirmation. Note the earlier line: `peaks skill presence` reports `auto-fire` from ≥ 0.80, and that tier is already mandatory — the 0.80 line, not 0.85, is the one that fires first.
 
 ### 4. On-disk slice progress — `progress.json`
 

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

@@ -39,22 +39,22 @@ stays IDE-agnostic.
 **Command**:
 
 ```
-peaks sub-agent dispatch <role> --prompt <text> --graph-node <nid> [--workflow-id <wid>] [--request-id <rid>] [--session-id <sid>] [--project <repo>] [--batch-id <uuid>] --json
+peaks sub-agent dispatch <role> --prompt <text> [--graph-node <nid>] [--workflow-id <wid>] [--request-id <rid>] [--session-id <sid>] [--project <repo>] [--batch-id <uuid>] --json
 ```
 
-> **`--graph-node` is REQUIRED (RD §4 D4c, effective 4.0.8).** Every
-> single dispatch must bind to a prepared workflow graph node. Prepare
-> one first:
+> **`--graph-node` is OPTIONAL (relaxed from the 4.0.8 RD §4 D4c requirement).**
+> Slice 4.0.8 made it a `.requiredOption`; `provisionDispatchNode`
+> (`src/services/workflow/provision-dispatch-node.ts`) relaxed it because the
+> requirement was enforced but never validated and the recovery it prescribed
+> was unwalkable: `peaks workflow node prepare` never calls `writeGraph`, so
+> the node it reports is never persisted, and no CLI verb created the graph it
+> reads. Its only observable effect was to block dispatch in every project
+> without graph infrastructure.
 >
-> ```
-> peaks workflow init --skill peaks-code                    # → returns <wid>
-> peaks workflow node prepare --workflow <wid> --node <nid> --kind dispatch
-> ```
->
-> then dispatch with `--graph-node <nid> --workflow-id <wid>`. Omitting
-> `--graph-node` rejects with `PEAKS_GRAPH_NODE_REQUIRED`; a node that is
-> not prepared (or has the wrong kind) rejects with
-> `PEAKS_GRAPH_NODE_NOT_PREPARED` / `PEAKS_GRAPH_NODE_KIND_INVALID`.
+> Omitting both flags now provisions a `dispatch-<role>-<stamp>` node and the
+> graph on demand, so **plain `peaks sub-agent dispatch rd --prompt '<task>' --request-id <rid> --project . --json` succeeds**. Passing
+> `--graph-node <nid> --workflow-id <wid>` binds to a node you control and
+> persists it into `graphs/<wid>.json`.
 
 **Envelope** (AC-8) — **2.1.0** (slice 2026-06-23-audit-4th #E1):
 
@@ -356,13 +356,13 @@ grown unboundedly without this fix).
 When writing a SKILL.md that fans out sub-agents:
 
 1. Use `peaks sub-agent dispatch <role>` (never `Task(...)`).
-2. Prepare the graph node first (RD §4 D4c — `--graph-node` is required):
-   `peaks workflow init --skill peaks-code`, then
-   `peaks workflow node prepare --workflow <wid> --node <nid> --kind dispatch`.
+2. Graph binding is OPTIONAL — omit `--graph-node` and the CLI provisions a
+   node on demand. Pass `--graph-node <nid> --workflow-id <wid>` only when you
+   need the dispatch bound to a node you control (and note the node is
+   persisted by `provisionDispatchNode`, not by `peaks workflow node prepare`).
 3. Issue all dispatches in a single message; the LLM will fire all
    returned toolCalls in parallel.
-4. Pass `--graph-node <nid> --workflow-id <wid>` on every dispatch, plus
-   `--request-id` and `--session-id` (or omit and let the CLI resolve the
+4. Pass `--request-id` and `--session-id` (or omit and let the CLI resolve the
    active session).
 5. The sub-agent prompt **must** include the heartbeat instruction
    (30 s cadence; override via `heartbeatIntervalSec` if needed).
@@ -445,7 +445,7 @@ peaks skill presence:set peaks-code --project <repo> --mode <mode> --gate swarm-
 
 ## Detached Mode (Phase A, slice 2026-08-10)
 
-`peaks sub-agent dispatch <role> --prompt <text> --graph-node <nid> --workflow-id <wid> --request-id <rid> --mode detached --vendor claude|codex|copilot [--no-throttle --max-concurrent <N>] --json` spawns a real OS process independent of the orchestrator IDE session. `--graph-node` remains required here (RD §4 D4c).
+`peaks sub-agent dispatch <role> --prompt <text> --graph-node <nid> --workflow-id <wid> --request-id <rid> --mode detached --vendor claude|codex|copilot [--no-throttle --max-concurrent <N>] --json` spawns a real OS process independent of the orchestrator IDE session. `--graph-node` is optional here too — the relaxation is on the shared option table, not on the in-process path only.
 
 - **Cross-platform spawn**: Windows uses `DETACHED_PROCESS` + `CREATE_NEW_PROCESS_GROUP`; POSIX uses `setsid` + `nohup`. Implementation: `packages/peaks-loop-internal-runtime/src/process-supervisor.ts`.
 - **Minimum-context prompt**: `PromptBuilder` emits a 5–8KB slice `{rid, role, vendor, files, refs}` plus the verbatim `<peaks-auto-compact>` marker. The forbidden marker `@@@ORCHESTRATOR_SESSION_HISTORY_BOUNDARY@@@` MUST NOT appear in any prompt (unit-tested; regression fails vitest).

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

@@ -1,11 +0,0 @@
-/**
- * `peaks context <sub>` — CLI surface for the ContextBuilder.
- * Per spec §4.1 — these commands are the only sanctioned entry point;
- * peaks-rd / peaks-qa / peaks-mut invoke them programmatically.
- */
-import { Command } from 'commander';
-import type { DocFetcher } from '../../services/context/doc-retriever.js';
-export interface ContextCommandsOptions {
-    readonly fetcher: DocFetcher;
-}
-export declare function createContextCommands(options: ContextCommandsOptions): Command;