peaks-loop 3.0.0 → 3.0.2

package/dist/src/services/compact/suggest-service.js

@@ -0,0 +1,203 @@
+/**
+ * `peaks compact suggest` — strategic-compact service layer.
+ *
+ * Mirrors the ECC `suggest-compact.js` PreToolUse hook's two-signal
+ * suggestion logic but as a deterministic, machine-enforced CLI
+ * primitive. Two signals:
+ *
+ *   1. Context size (primary) — read latest usage row from
+ *      `.peaks/_runtime/<sid>/usage.jsonl`. Suggest at
+ *      COMPACT_CONTEXT_THRESHOLD (default 160k on 200k window, 250k
+ *      on 1M window) and re-remind every COMPACT_CONTEXT_INTERVAL
+ *      tokens (default 60k). A 1M window is detected when observed
+ *      tokens exceed 200k AND the `modelKind: '1m'` marker is on
+ *      the latest usage row, or when PEAKS_MODEL_KIND=1m is set.
+ *
+ *   2. Tool-call count (secondary) — read latest tool-call counter
+ *      from the same usage.jsonl. Suggest at COMPACT_THRESHOLD
+ *      (default 50) and re-remind every 25 calls.
+ *
+ * If usage.jsonl is absent (no peaks-loop session yet), fall back to
+ * PEAKS_CONTEXT_TOKENS / PEAKS_TOOL_CALLS env vars. If neither signal
+ * is available, the primitive returns `shouldSuggest: false` and a
+ * `dataUnavailable: true` flag — never throws.
+ */
+import { existsSync, readFileSync } from 'node:fs';
+import { join } from 'node:path';
+import { lookupPhaseTransition, buildSuggestedCompactMessage, SURVIVAL_TABLE } from './decision-tables.js';
+/** Snapshot of the survival table for the dry-run envelope. */
+const SURVIVAL_TABLE_PERSISTS = SURVIVAL_TABLE.persists;
+const SURVIVAL_TABLE_LOST = SURVIVAL_TABLE.lost;
+/** Default tool-call threshold before first suggestion. */
+export const DEFAULT_TOOL_CALL_THRESHOLD = 50;
+/** Default additional tool calls before the suggestion repeats. */
+export const TOOL_CALL_REMIND_STEP = 25;
+/** Default context-size threshold on a 200k window. */
+export const DEFAULT_CONTEXT_THRESHOLD_200K = 160_000;
+/** Default context-size threshold on a 1M window. */
+export const DEFAULT_CONTEXT_THRESHOLD_1M = 250_000;
+/** Default re-remind interval for context size. */
+export const DEFAULT_CONTEXT_INTERVAL = 60_000;
+function readLatestUsageRow(projectRoot, sessionId) {
+    const path = join(projectRoot, '.peaks', '_runtime', sessionId, 'usage.jsonl');
+    if (!existsSync(path))
+        return null;
+    try {
+        const raw = readFileSync(path, 'utf8');
+        const lines = raw.split(/\r?\n/).filter((l) => l.length > 0);
+        if (lines.length === 0)
+            return null;
+        const last = lines[lines.length - 1];
+        if (last === undefined)
+            return null;
+        return JSON.parse(last);
+    }
+    catch { // TODO(g2): legacy silent catch — grace: 1 minor release (v2.14.0)
+        return null;
+    }
+}
+function parseIntEnv(env, key, fallback) {
+    const raw = env[key];
+    if (typeof raw !== 'string' || raw.length === 0)
+        return fallback;
+    const parsed = Number.parseInt(raw, 10);
+    return Number.isFinite(parsed) ? parsed : fallback;
+}
+function detectWindowKind(env, observedTokens, rowModelKind) {
+    if (rowModelKind === '1m')
+        return '1m';
+    if (env['PEAKS_MODEL_KIND'] === '1m')
+        return '1m';
+    // Heuristic from SKILL.md: a `[1m]` model marker OR observed tokens
+    // already exceed the 200k window. We use observed as the second
+    // signal only.
+    if (observedTokens > DEFAULT_CONTEXT_THRESHOLD_200K)
+        return '1m';
+    return '200k';
+}
+export function suggestCompact(options) {
+    const env = options.env ?? process.env;
+    const contextThreshold = parseIntEnv(env, 'COMPACT_CONTEXT_THRESHOLD', 0);
+    const contextInterval = parseIntEnv(env, 'COMPACT_CONTEXT_INTERVAL', DEFAULT_CONTEXT_INTERVAL);
+    const toolCallThreshold = parseIntEnv(env, 'COMPACT_THRESHOLD', DEFAULT_TOOL_CALL_THRESHOLD);
+    let tokensUsed = 0;
+    let toolCalls = 0;
+    let modelKind;
+    let source = 'none';
+    if (options.sessionId !== null) {
+        const row = readLatestUsageRow(options.projectRoot, options.sessionId);
+        if (row !== null) {
+            if (typeof row.tokens === 'number' && Number.isFinite(row.tokens))
+                tokensUsed = row.tokens;
+            if (typeof row.toolCalls === 'number' && Number.isFinite(row.toolCalls))
+                toolCalls = row.toolCalls;
+            if (typeof row.modelKind === 'string')
+                modelKind = row.modelKind;
+            source = 'usage-jsonl';
+        }
+    }
+    if (source === 'none') {
+        const envTokens = env['PEAKS_CONTEXT_TOKENS'];
+        if (typeof envTokens === 'string' && envTokens.length > 0) {
+            const parsed = Number.parseInt(envTokens, 10);
+            if (Number.isFinite(parsed) && parsed >= 0) {
+                tokensUsed = parsed;
+                source = 'env-vars';
+            }
+        }
+        const envCalls = env['PEAKS_TOOL_CALLS'];
+        if (typeof envCalls === 'string' && envCalls.length > 0) {
+            const parsed = Number.parseInt(envCalls, 10);
+            if (Number.isFinite(parsed) && parsed >= 0) {
+                toolCalls = parsed;
+                source = 'env-vars';
+            }
+        }
+    }
+    const windowKind = detectWindowKind(env, tokensUsed, modelKind);
+    const windowCapacity = windowKind === '1m' ? 1_000_000 : 200_000;
+    const effectiveContextThreshold = contextThreshold > 0
+        ? contextThreshold
+        : (windowKind === '1m' ? DEFAULT_CONTEXT_THRESHOLD_1M : DEFAULT_CONTEXT_THRESHOLD_200K);
+    const ratio = windowCapacity > 0 ? tokensUsed / windowCapacity : 0;
+    const dataUnavailable = tokensUsed === 0 && toolCalls === 0;
+    // Two-signal suggestion. The context signal is primary: the LLM
+    // gets a real "/compact" recommendation only when context-size OR
+    // tool-count crosses the threshold AND we have non-zero data.
+    let shouldSuggest = false;
+    let reason = 'below-threshold';
+    if (!dataUnavailable) {
+        if (contextThreshold !== 0 && tokensUsed >= effectiveContextThreshold) {
+            shouldSuggest = true;
+            const overBy = tokensUsed - effectiveContextThreshold;
+            reason = `context >= ${effectiveContextThreshold} on ${windowKind} window (over by ${overBy} tokens)`;
+        }
+        else if (toolCalls >= toolCallThreshold) {
+            shouldSuggest = true;
+            reason = `tool-calls >= ${toolCallThreshold} (count=${toolCalls})`;
+        }
+    }
+    return {
+        shouldSuggest,
+        reason,
+        ratio,
+        windowKind,
+        tokensUsed,
+        toolCalls,
+        thresholds: {
+            contextTokens: effectiveContextThreshold,
+            contextInterval,
+            toolCalls: toolCallThreshold
+        },
+        dataUnavailable,
+        source
+    };
+}
+export function dryRunCompact(options) {
+    const suggest = suggestCompact({
+        projectRoot: options.projectRoot,
+        sessionId: options.sessionId,
+        ...(options.env !== undefined ? { env: options.env } : {})
+    });
+    const hasPhase = options.from !== undefined && options.to !== undefined;
+    const recommend = hasPhase
+        ? buildRecommendEnvelope(options.from, options.to)
+        : {
+            from: null,
+            to: null,
+            shouldCompact: false,
+            severity: null,
+            rationale: null,
+            suggestedMessage: null
+        };
+    // Action threshold: either suggest-signal OR recommend=yes. The LLM
+    // is the final arbiter; the primitive just surfaces the composite
+    // signal.
+    const action = suggest.shouldSuggest || recommend.shouldCompact ? 'compact' : 'skip';
+    return {
+        action,
+        suggest,
+        recommend,
+        survival: { persists: SURVIVAL_TABLE_PERSISTS, lost: SURVIVAL_TABLE_LOST }
+    };
+}
+function buildRecommendEnvelope(from, to) {
+    const lookup = lookupPhaseTransition(from, to);
+    const shouldCompact = lookup.severity === 'yes' || lookup.severity === 'maybe';
+    return {
+        from,
+        to,
+        shouldCompact,
+        severity: lookup.severity,
+        rationale: lookup.rationale,
+        suggestedMessage: buildSuggestedCompactMessage(from, to, lookup.severity)
+    };
+}
+export function buildRecommendEnvelopePure(from, to) {
+    return buildRecommendEnvelope(from, to);
+}
+// Re-export phase primitives for callers that don't want to traverse
+// decision-tables. The CLI command file imports `isPhase` from here
+// to keep the validation path co-located with the recommend envelope
+// builder.
+export { PHASE_TRANSITIONS, lookupPhaseTransition, buildSuggestedCompactMessage, PHASES, isPhase, SURVIVAL_TABLE } from './decision-tables.js';

package/dist/src/services/config/config-migration.js

@@ -132,7 +132,7 @@ export function executeMigration(opts) {
     //    Per the 2.0.1 slim spec, the on-disk `~/.peaks/config.json` is
     //    `{ "version": "2.0.1", "ocr": { "llm": { ... } } }`. Legacy fields
     //    (language, model, economyMode, swarmMode, tokens, providers,
-    //    proxy) live in <project>/.peaks/preferences.json. peaks-cli writes
+    //    proxy) live in <project>/.peaks/preferences.json. peaks-loop writes
     //    the `ocr.llm.*` placeholders so the user has a discoverable spot
     //    to paste their endpoint; the placeholders are empty strings, not
     //    auto-configured values, so the post-migration file MUST contain

package/dist/src/services/config/config-safety.d.ts

@@ -5,7 +5,7 @@ export declare function resolveProjectRootForConfig(startPath: string): string;
 /**
  * Canonicalise a user-supplied project root path against git's view of the
  * repository root. This is the fix for the nested-directory regression
- * where peaks-cli would write `.peaks/` under a nested sub-folder
+ * where peaks-loop would write `.peaks/` under a nested sub-folder
  * (e.g. `prompt-project/prompt-project/.peaks/`) because the LLM passed
  * `$(pwd)` from inside a sub-directory of a real git repo. Without
  * canonicalisation, peaks accepted the cwd as-is, built the .peaks/

package/dist/src/services/config/config-safety.js

@@ -93,7 +93,7 @@ export function resolveProjectRootForConfig(startPath) {
 /**
  * Canonicalise a user-supplied project root path against git's view of the
  * repository root. This is the fix for the nested-directory regression
- * where peaks-cli would write `.peaks/` under a nested sub-folder
+ * where peaks-loop would write `.peaks/` under a nested sub-folder
  * (e.g. `prompt-project/prompt-project/.peaks/`) because the LLM passed
  * `$(pwd)` from inside a sub-directory of a real git repo. Without
  * canonicalisation, peaks accepted the cwd as-is, built the .peaks/

package/dist/src/services/config/config-service.d.ts

@@ -38,7 +38,7 @@ export declare function setMiniMaxProviderConfig(input: MiniMaxProviderConfig):
  * `~/.peaks/config.json`. The user populates this themselves by
  * pasting the `peaks code-review config-template` output (or by
  * running `peaks config set --key ocr.llm.url --value '...'`).
- * peaks-cli never auto-writes these values.
+ * peaks-loop never auto-writes these values.
  */
 export declare function getOcrConfig(): OcrConfig;
 /**

package/dist/src/services/config/config-service.js

@@ -512,7 +512,7 @@ function toOcrConfig(value) {
  * `~/.peaks/config.json`. The user populates this themselves by
  * pasting the `peaks code-review config-template` output (or by
  * running `peaks config set --key ocr.llm.url --value '...'`).
- * peaks-cli never auto-writes these values.
+ * peaks-loop never auto-writes these values.
  */
 export function getOcrConfig() {
     const userConfig = readUserJsonFile() ?? {};

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

@@ -9,22 +9,22 @@
  *
  * Pathway dispatch:
  *
- *   - `shell-exec`     — peaks-cli spawns the adapter's
+ *   - `shell-exec`     — peaks-loop spawns the adapter's
  *                        `compactCommand` via `child_process.spawn`.
  *                        Works for any IDE that accepts a slash
  *                        command via a shell-spawnable entry point
  *                        (Claude Code MVP: `/compact`).
- *   - `ide-native`     — peaks-cli writes the compact intent to
+ *   - `ide-native`     — peaks-loop writes the compact intent to
  *                        the IDE's hook file (per
  *                        `IdeSettingsLocation`). Used when the IDE
  *                        requires a registered hook rather than a
  *                        runtime command.
- *   - `llm-self-compress` — peaks-cli records the intent and
+ *   - `llm-self-compress` — peaks-loop records the intent and
  *                        returns `ok: true` with `pathway` echoed.
  *                        The LLM does its own context summarization
  *                        on the next turn. Always available; least
  *                        precise fallback.
- *   - `noop`           — adapter explicitly opted out. peaks-cli
+ *   - `noop`           — adapter explicitly opted out. peaks-loop
  *                        returns `ok: false` with `message: 'noop'`.
  *                        Used by legacy / unverified adapters.
  */

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

@@ -1,11 +1,11 @@
 /**
  * Auto-compact shared types (v2.13.0 AC-1..AC-4).
  *
- * Two-tier threshold model — peaks-cli is project-aware and the LLM
+ * Two-tier threshold model — peaks-loop is project-aware and the LLM
  * is the decision-maker:
  *
  *   - 50%  soft warn          — log a one-line info row; continue.
- *   - 85%  pre-compact zone   — peaks-cli prepares the convergence
+ *   - 85%  pre-compact zone   — peaks-loop prepares the convergence
  *                                toolkit (checkpoint + convergence
  *                                plan + auto-decisions log +
  *                                IDE-compact dispatcher). The LLM
@@ -14,7 +14,7 @@
  *                                toolkit is "ready to use" so the
  *                                LLM doesn't lose context to a
  *                                last-second `/compact` panic.
- *   - 95%  RED LINE           — peaks-cli refuses to dispatch any
+ *   - 95%  RED LINE           — peaks-loop refuses to dispatch any
  *                                further sub-agent and synchronously
  *                                triggers IDE-side compact. At 95%+
  *                                the context window is too tight to
@@ -25,9 +25,9 @@
  *
  * Why 0.85 / 0.95 split: the LLM uses the 0.85–0.95 zone to do
  * intelligent convergence — wait for in-flight sub-agents, finish
- * the current todo row, persist a checkpoint, then compact. peaks-cli
+ * the current todo row, persist a checkpoint, then compact. peaks-loop
  * provides the toolkit; the LLM picks the moment. At 0.95 the window
- * is gone and peaks-cli takes over synchronously to keep the runner
+ * is gone and peaks-loop takes over synchronously to keep the runner
  * alive.
  */
 export declare const AUTO_COMPACT_SOFT_WARN_RATIO = 0.5;
@@ -49,7 +49,7 @@ export type CompactTrigger = {
     message: string;
     toolkitReady: true;
 }
-/** Red line (ratio ≥ 0.95): peaks-cli forces synchronous compact; LLM cannot opt out. */
+/** Red line (ratio ≥ 0.95): peaks-loop forces synchronous compact; LLM cannot opt out. */
  | {
     kind: 'red-line';
     ratio: number;

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

@@ -1,11 +1,11 @@
 /**
  * Auto-compact shared types (v2.13.0 AC-1..AC-4).
  *
- * Two-tier threshold model — peaks-cli is project-aware and the LLM
+ * Two-tier threshold model — peaks-loop is project-aware and the LLM
  * is the decision-maker:
  *
  *   - 50%  soft warn          — log a one-line info row; continue.
- *   - 85%  pre-compact zone   — peaks-cli prepares the convergence
+ *   - 85%  pre-compact zone   — peaks-loop prepares the convergence
  *                                toolkit (checkpoint + convergence
  *                                plan + auto-decisions log +
  *                                IDE-compact dispatcher). The LLM
@@ -14,7 +14,7 @@
  *                                toolkit is "ready to use" so the
  *                                LLM doesn't lose context to a
  *                                last-second `/compact` panic.
- *   - 95%  RED LINE           — peaks-cli refuses to dispatch any
+ *   - 95%  RED LINE           — peaks-loop refuses to dispatch any
  *                                further sub-agent and synchronously
  *                                triggers IDE-side compact. At 95%+
  *                                the context window is too tight to
@@ -25,9 +25,9 @@
  *
  * Why 0.85 / 0.95 split: the LLM uses the 0.85–0.95 zone to do
  * intelligent convergence — wait for in-flight sub-agents, finish
- * the current todo row, persist a checkpoint, then compact. peaks-cli
+ * the current todo row, persist a checkpoint, then compact. peaks-loop
  * provides the toolkit; the LLM picks the moment. At 0.95 the window
- * is gone and peaks-cli takes over synchronously to keep the runner
+ * is gone and peaks-loop takes over synchronously to keep the runner
  * alive.
  */
 export const AUTO_COMPACT_SOFT_WARN_RATIO = 0.5;

package/dist/src/services/dispatch/sub-agent-dispatcher.js

@@ -15,7 +15,7 @@
  *
  * Why this exists:
  * - Prior SKILL.md hardcoded `Task(subagent_type="general-purpose", ...)`
- * which made peaks-cli depend on Claude Code's specific sub-agent
+ * which made peaks-loop depend on Claude Code's specific sub-agent
  * tool name. Adding a new IDE (Trae, future Cursor, etc.) required
  * editing every SKILL.md that mentioned sub-agent dispatch.
  * - This file (plus the per-IDE adapter wiring) collapses all

package/dist/src/services/dispatch/test-tool-detection.d.ts

@@ -2,7 +2,7 @@
  * Slice 2026-06-24-test-tool-detection-injection.
  *
  * The Test Tool Detection block is prepended to every sub-agent prompt
- * dispatched by peaks-cli (both the single-dispatch chokepoint in
+ * dispatched by peaks-loop (both the single-dispatch chokepoint in
  * `src/cli/commands/dispatch-commands.ts` and the DAG-dispatch chokepoint
  * in `src/services/solo/dag-orchestrator.ts`). It tells the sub-agent
  * to read `package.json#scripts.test` first and use the project-local

package/dist/src/services/dispatch/test-tool-detection.js

@@ -2,7 +2,7 @@
  * Slice 2026-06-24-test-tool-detection-injection.
  *
  * The Test Tool Detection block is prepended to every sub-agent prompt
- * dispatched by peaks-cli (both the single-dispatch chokepoint in
+ * dispatched by peaks-loop (both the single-dispatch chokepoint in
  * `src/cli/commands/dispatch-commands.ts` and the DAG-dispatch chokepoint
  * in `src/services/solo/dag-orchestrator.ts`). It tells the sub-agent
  * to read `package.json#scripts.test` first and use the project-local

package/dist/src/services/doctor/doctor-service.d.ts

@@ -46,7 +46,7 @@ export type WorkspaceLayoutInspection = {
 export type WorkspaceLayoutProbe = () => WorkspaceLayoutInspection;
 /**
  * 2026-06-10 — `gateguard-fact-force` (a third-party PreToolUse hook,
- * NOT peaks-cli) fires on Edit / Write and demands a 4-fact questionnaire
+ * NOT peaks-loop) fires on Edit / Write and demands a 4-fact questionnaire
  * before allowing the edit. When the LLM is in a peaks-qa flow and tries
  * to update `.peaks/_runtime/<sid>/qa/requests/*.md` via the Edit/Write
  * tool, the hook demands facts that are inapplicable to QA envelope

package/dist/src/services/doctor/doctor-service.js

@@ -272,11 +272,11 @@ function findDestructiveApplyLines(section) {
     return lines.filter((line) => DESTRUCTIVE_APPLY_PATTERNS.some((pattern) => pattern.test(line)));
 }
 // ---------------------------------------------------------------------------
-// 2026-06-10 — gateguard-fact-force integration check (NOT a peaks-cli hook).
+// 2026-06-10 — gateguard-fact-force integration check (NOT a peaks-loop hook).
 //
 // The `gateguard-fact-force` hook is a third-party PreToolUse hook that
 // fires on Edit / Write / MultiEdit and demands a 4-fact questionnaire
-// before allowing the edit. It is unrelated to peaks-cli, but when the
+// before allowing the edit. It is unrelated to peaks-loop, but when the
 // LLM is in a peaks-qa flow and edits `.peaks/_runtime/<sid>/qa/requests/
 // *.md`, the questionnaire demands facts that do not apply (no
 // importers, no public API, no data files, user instruction already
@@ -293,7 +293,7 @@ const GATEGUARD_HOOK_NEEDLES = ['gateguard', 'fact-force', 'fact_force'];
 /** Token the gateguard hook exposes for "skip these paths" — the check
  *  treats any match against `.peaks` (path or globs) as a routed
  *  configuration. We accept a few common spellings because the third-
- *  party hook's CLI surface is not part of peaks-cli's contract. */
+ *  party hook's CLI surface is not part of peaks-loop's contract. */
 const GATEGUARD_PEAKS_SKIP_NEEDLES = [
     '.peaks',
     'peaks-skip',
@@ -603,7 +603,7 @@ export async function runDoctor(options = {}) {
         checks.push({
             id: 'statusline:runtime',
             ok: true,
-            message: `peaks ${CLI_VERSION} (win32): if the statusLine shows nothing in git bash, verify \`peaks\` resolves on PATH in the shell Claude Code uses (run \`peaks -v\` there), reinstall globally with \`npm i -g peaks-cli@latest\` if the version is older than ${CLI_VERSION}, then re-run \`peaks statusline install\` and reload Claude Code`
+            message: `peaks ${CLI_VERSION} (win32): if the statusLine shows nothing in git bash, verify \`peaks\` resolves on PATH in the shell Claude Code uses (run \`peaks -v\` there), reinstall globally with \`npm i -g peaks-loop@latest\` if the version is older than ${CLI_VERSION}, then re-run \`peaks statusline install\` and reload Claude Code`
         });
     }
     else {
@@ -768,7 +768,7 @@ export async function runDoctor(options = {}) {
                 checks.push({
                     id: 'integration:gateguard-peaks-conflict',
                     ok: false,
-                    message: `gateguard-fact-force PreToolUse hook is installed (${sources}, matcher: ${matchers}) with no .peaks/** skip pattern; every Edit/Write of a peaks-qa envelope (.peaks/_runtime/<sid>/qa/requests/*.md) will be intercepted and demand a 4-fact questionnaire that does not apply to QA templates. Workaround: set \`ECC_DISABLED_HOOKS=pre:edit-write:gateguard-fact-force\` for the session, OR add a paired PreToolUse entry whose matcher restricts the hook to non-.peaks paths. peaks-cli is NOT the source of this hook.`
+                    message: `gateguard-fact-force PreToolUse hook is installed (${sources}, matcher: ${matchers}) with no .peaks/** skip pattern; every Edit/Write of a peaks-qa envelope (.peaks/_runtime/<sid>/qa/requests/*.md) will be intercepted and demand a 4-fact questionnaire that does not apply to QA templates. Workaround: set \`ECC_DISABLED_HOOKS=pre:edit-write:gateguard-fact-force\` for the session, OR add a paired PreToolUse entry whose matcher restricts the hook to non-.peaks paths. peaks-loop is NOT the source of this hook.`
                 });
             }
         }

package/dist/src/services/hooks/presence-marker-detector.js

@@ -6,7 +6,7 @@ import { resolve } from 'node:path';
  * Background: the consumer-facing CLAUDE.md template (rendered by
  * `peaks standards init` / `peaks standards update`) instructs the LLM
  * to display a compact status header
- *   `Peaks-Cli Skill: <skill> | Peaks-Cli Gate: <gate> | Next: <one short action>`
+ *   `Peaks-Loop Skill: <skill> | Peaks-Loop Gate: <gate> | Next: <one short action>`
  * on every turn while a peaks skill is active. If the LLM forgets (e.g.
  * because of context compaction or a fresh session), the user is left
  * without an at-a-glance signal that peaks is orchestrating the work.
@@ -20,21 +20,21 @@ import { resolve } from 'node:path';
  *   - `active`:      whether an active-skill marker was found on disk.
  *   - `skill?`:      the active skill name, if any.
  *   - `markerFound`: whether the latest assistant message carries the
- *                    expected `Peaks-Cli Skill:` / `Peaks-Cli Gate:`
+ *                    expected `Peaks-Loop Skill:` / `Peaks-Loop Gate:`
  *                    marker. Always `false` when `active` is `false`.
  *   - `warning?`:    a human-readable warning emitted when the marker
  *                    is missing while the presence is active.
  *
  * The function is pure: it does not write to disk, does not clear the
  * presence file, and does not depend on `process.cwd()`. The caller is
- * expected to provide the absolute project root (peaks-cli convention
+ * expected to provide the absolute project root (peaks-loop convention
  * from the standards-commands family — see dev-preference rule
  * `project-option-is-canonical-project-root-source`).
  */
 const PRESENCE_CANONICAL_PATH = '.peaks/_runtime/active-skill.json';
 const PRESENCE_LEGACY_PATH = '.peaks/.active-skill.json';
-const MARKER_PRIMARY = 'Peaks-Cli Skill:';
-const MARKER_SECONDARY = 'Peaks-Cli Gate:';
+const MARKER_PRIMARY = 'Peaks-Loop Skill:';
+const MARKER_SECONDARY = 'Peaks-Loop Gate:';
 const SKILL_NAME_RE = /"skill"\s*:\s*"([^"\\]*(?:\\.[^"\\]*)*)"/;
 export const PRESENCE_MARKER_WARNING = [
     'Peaks skill context may have been lost from this conversation; please re-invoke /peaks-<skill>.'

package/dist/src/services/ide/adapters/claude-code-adapter.d.ts

@@ -1,6 +1,6 @@
 import type { IdeAdapter } from '../ide-types.js';
 /**
- * Claude Code adapter —— peaks-cli 的"起源 IDE"。
+ * Claude Code adapter —— peaks-loop 的"起源 IDE"。
  *
  * 该 adapter 从原 `src/services/skills/hooks-settings-service.ts` 提取,保持
  * 字节级兼容:用户在 Claude Code 环境下跑 `peaks hooks install` 产出的

package/dist/src/services/ide/adapters/claude-code-adapter.js

@@ -2,7 +2,7 @@ import { homedir } from 'node:os';
 import { join, resolve } from 'node:path';
 import { claudeCodeSubAgentDispatcher } from '../../dispatch/sub-agent-dispatcher.js';
 /**
- * Claude Code adapter —— peaks-cli 的"起源 IDE"。
+ * Claude Code adapter —— peaks-loop 的"起源 IDE"。
  *
  * 该 adapter 从原 `src/services/skills/hooks-settings-service.ts` 提取,保持
  * 字节级兼容:用户在 Claude Code 环境下跑 `peaks hooks install` 产出的
@@ -50,7 +50,7 @@ export const CLAUDE_CODE_ADAPTER = {
     // v2.13.0 AC-1 + AC-3 MVP: Claude Code is the first IDE to fill
     // the `compact` profile. Future adapters (trae / codex / cursor /
     // qoder / tongyi-lingma / hermes / openclaw) follow the same
-    // shape — peaks-cli reads the env-var and dispatches the
+    // shape — peaks-loop reads the env-var and dispatches the
     // command via `IdeAdapter.compact`, with zero hard-coded IDE
     // names anywhere in the orchestrator. If your IDE exposes a
     // context-percent env-var and a slash-style compact command,

package/dist/src/services/ide/adapters/codex-adapter.d.ts

@@ -1,6 +1,6 @@
 import type { IdeAdapter } from '../ide-types.js';
 /**
- * Codex (OpenAI CLI IDE) adapter —— peaks-cli 的第四个内置 IDE 适配器(slice #13, 2.4.0)。
+ * Codex (OpenAI CLI IDE) adapter —— peaks-loop 的第四个内置 IDE 适配器(slice #13, 2.4.0)。
  *
  * 不可消除的 per-IDE 字段(slice #1 锁定,same shape as trae-adapter.ts / cursor-adapter.ts):
  *   - settings.dirName = '.codex'        : Codex 项目根下的配置目录
@@ -10,7 +10,7 @@ import type { IdeAdapter } from '../ide-types.js';
  *   - toolMatcher = 'shell'         : Codex 的 shell command matcher
  *
  * Slice #13 status (2026-06-17, 2.4.0):
- *   - Adapter is the fourth built-in IDE in peaks-cli after Claude Code (#1),
+ *   - Adapter is the fourth built-in IDE in peaks-loop after Claude Code (#1),
  *     Trae (#2), and Cursor (#12). It further confirms the slice #1 + slice #2
  *     architecture scales linearly: registering a new IDE is a one-entry fill
  *     of the slim `IdeAdapter` shape with no dispatch-chokepoint changes.

package/dist/src/services/ide/adapters/codex-adapter.js

@@ -2,7 +2,7 @@ import { homedir } from 'node:os';
 import { join, resolve } from 'node:path';
 import { codexSubAgentDispatcher } from '../../dispatch/sub-agent-dispatcher.js';
 /**
- * Codex (OpenAI CLI IDE) adapter —— peaks-cli 的第四个内置 IDE 适配器(slice #13, 2.4.0)。
+ * Codex (OpenAI CLI IDE) adapter —— peaks-loop 的第四个内置 IDE 适配器(slice #13, 2.4.0)。
  *
  * 不可消除的 per-IDE 字段(slice #1 锁定,same shape as trae-adapter.ts / cursor-adapter.ts):
  *   - settings.dirName = '.codex'        : Codex 项目根下的配置目录
@@ -12,7 +12,7 @@ import { codexSubAgentDispatcher } from '../../dispatch/sub-agent-dispatcher.js'
  *   - toolMatcher = 'shell'         : Codex 的 shell command matcher
  *
  * Slice #13 status (2026-06-17, 2.4.0):
- *   - Adapter is the fourth built-in IDE in peaks-cli after Claude Code (#1),
+ *   - Adapter is the fourth built-in IDE in peaks-loop after Claude Code (#1),
  *     Trae (#2), and Cursor (#12). It further confirms the slice #1 + slice #2
  *     architecture scales linearly: registering a new IDE is a one-entry fill
  *     of the slim `IdeAdapter` shape with no dispatch-chokepoint changes.

package/dist/src/services/ide/adapters/cursor-adapter.d.ts

@@ -1,6 +1,6 @@
 import type { IdeAdapter } from '../ide-types.js';
 /**
- * Cursor IDE adapter —— peaks-cli 的第三个内置 IDE 适配器(slice #12, 2.4.0)。
+ * Cursor IDE adapter —— peaks-loop 的第三个内置 IDE 适配器(slice #12, 2.4.0)。
  *
  * 不可消除的 per-IDE 字段(slice #1 锁定,same shape as trae-adapter.ts):
  *   - settings.dirName = '.cursor'            : Cursor 项目根下的配置目录
@@ -10,7 +10,7 @@ import type { IdeAdapter } from '../ide-types.js';
  *   - toolMatcher = 'Bash'              : Cursor 的 shell execution tool matcher
  *
  * Slice #12 status (2026-06-17, 2.4.0):
- *   - Adapter is the third built-in IDE in peaks-cli after Claude Code (#1) and Trae (#2).
+ *   - Adapter is the third built-in IDE in peaks-loop after Claude Code (#1) and Trae (#2).
  *   - Confirms the slice #1 + slice #2 architecture scales linearly: registering
  *     a new IDE is genuinely a one-entry fill of the slim `IdeAdapter` shape.
  *   - 2 UNVERIFIED fields: `envVar` (Cursor's `CURSOR_PROJECT_DIR` is the

package/dist/src/services/ide/adapters/cursor-adapter.js

@@ -2,7 +2,7 @@ import { homedir } from 'node:os';
 import { join, resolve } from 'node:path';
 import { cursorSubAgentDispatcher } from '../../dispatch/sub-agent-dispatcher.js';
 /**
- * Cursor IDE adapter —— peaks-cli 的第三个内置 IDE 适配器(slice #12, 2.4.0)。
+ * Cursor IDE adapter —— peaks-loop 的第三个内置 IDE 适配器(slice #12, 2.4.0)。
  *
  * 不可消除的 per-IDE 字段(slice #1 锁定,same shape as trae-adapter.ts):
  *   - settings.dirName = '.cursor'            : Cursor 项目根下的配置目录
@@ -12,7 +12,7 @@ import { cursorSubAgentDispatcher } from '../../dispatch/sub-agent-dispatcher.js
  *   - toolMatcher = 'Bash'              : Cursor 的 shell execution tool matcher
  *
  * Slice #12 status (2026-06-17, 2.4.0):
- *   - Adapter is the third built-in IDE in peaks-cli after Claude Code (#1) and Trae (#2).
+ *   - Adapter is the third built-in IDE in peaks-loop after Claude Code (#1) and Trae (#2).
  *   - Confirms the slice #1 + slice #2 architecture scales linearly: registering
  *     a new IDE is genuinely a one-entry fill of the slim `IdeAdapter` shape.
  *   - 2 UNVERIFIED fields: `envVar` (Cursor's `CURSOR_PROJECT_DIR` is the

package/dist/src/services/ide/adapters/hermes-adapter.d.ts

@@ -1,5 +1,5 @@
 /**
- * Hermes IDE adapter (Slice #0.7) — peaks-cli 的第七个内置 IDE 适配器。
+ * Hermes IDE adapter (Slice #0.7) — peaks-loop 的第七个内置 IDE 适配器。
  *
  * 不可消除的 per-IDE 字段(slice #0.7 填表):
  *   - settings.dirName = '.hermes'          : Hermes 项目根下的配置目录

package/dist/src/services/ide/adapters/hermes-adapter.js

@@ -1,5 +1,5 @@
 /**
- * Hermes IDE adapter (Slice #0.7) — peaks-cli 的第七个内置 IDE 适配器。
+ * Hermes IDE adapter (Slice #0.7) — peaks-loop 的第七个内置 IDE 适配器。
  *
  * 不可消除的 per-IDE 字段(slice #0.7 填表):
  *   - settings.dirName = '.hermes'          : Hermes 项目根下的配置目录

package/dist/src/services/ide/adapters/openclaw-adapter.d.ts

@@ -1,5 +1,5 @@
 /**
- * OpenClaw IDE adapter (Slice #0.7) — peaks-cli 的第八个内置 IDE 适配器。
+ * OpenClaw IDE adapter (Slice #0.7) — peaks-loop 的第八个内置 IDE 适配器。
  *
  * 不可消除的 per-IDE 字段(slice #0.7 填表):
  *   - settings.dirName = '.openclaw'        : OpenClaw 项目根下的配置目录

package/dist/src/services/ide/adapters/openclaw-adapter.js

@@ -1,5 +1,5 @@
 /**
- * OpenClaw IDE adapter (Slice #0.7) — peaks-cli 的第八个内置 IDE 适配器。
+ * OpenClaw IDE adapter (Slice #0.7) — peaks-loop 的第八个内置 IDE 适配器。
  *
  * 不可消除的 per-IDE 字段(slice #0.7 填表):
  *   - settings.dirName = '.openclaw'        : OpenClaw 项目根下的配置目录

package/dist/src/services/ide/adapters/trae-adapter.d.ts

@@ -1,6 +1,6 @@
 import type { IdeAdapter } from '../ide-types.js';
 /**
- * Trae IDE adapter —— peaks-cli 的第二个内置 IDE 适配器。
+ * Trae IDE adapter —— peaks-loop 的第二个内置 IDE 适配器。
  *
  * 不可消除的 per-IDE 字段(slice #1 锁定):
  *   - settings.dirName = '.trae'            : Trae 项目根下的配置目录

package/dist/src/services/ide/adapters/trae-adapter.js

@@ -2,7 +2,7 @@ import { homedir } from 'node:os';
 import { join, resolve } from 'node:path';
 import { traeSubAgentDispatcher } from '../../dispatch/sub-agent-dispatcher.js';
 /**
- * Trae IDE adapter —— peaks-cli 的第二个内置 IDE 适配器。
+ * Trae IDE adapter —— peaks-loop 的第二个内置 IDE 适配器。
  *
  * 不可消除的 per-IDE 字段(slice #1 锁定):
  *   - settings.dirName = '.trae'            : Trae 项目根下的配置目录