peaks-loop 3.0.0 → 3.0.1

package/dist/src/cli/commands/upgrade-commands.js

@@ -8,12 +8,12 @@ import { fail, ok } from '../../shared/result.js';
 export function registerUpgradeCommands(program, io) {
     addJsonOption(program
         .command('upgrade')
-        .description('Upgrade a peaks-cli 1.x project to 2.0. Umbrella that orquestrates 7 sub-commands: config-migrate / standards-migrate / memory-extract / hooks-install / skill-sync / audit-verify + write-upgrade-record. Per the "one-key completion" tenet, prefer letting `npm i -g peaks-cli@2.0` postinstall run this for you. Use `--detect-1x` for a read-only probe (no file writes) that the peaks-solo skill uses to gate the 1.x → 2.0 AskUserQuestion.')
+        .description('Upgrade a peaks-loop 1.x project to 2.0. Umbrella that orquestrates 7 sub-commands: config-migrate / standards-migrate / memory-extract / hooks-install / skill-sync / audit-verify + write-upgrade-record. Per the "one-key completion" tenet, prefer letting `npm i -g peaks-loop@2.0` postinstall run this for you. Use `--detect-1x` for a read-only probe (no file writes) that the peaks-solo skill uses to gate the 1.x → 2.0 AskUserQuestion.')
         .option('--to <version>', 'target version (only "2.0" supported)', '2.0')
         .option('--project <path>', 'project root to upgrade (default: cwd)')
         .option('--auto', 'non-interactive: accept soft-fail on any sub-step (used by the postinstall hook)')
         .option('--detect-1x', 'read-only probe: returns the 1.x state as JSON (no file writes); consumed by peaks-solo Step 0.55 to gate the AskUserQuestion')
-        .option('--apply-init', 'slice 4 (slice 2026-06-13-selfheal-claude-settings-template): run initWorkspace so the drift-driven self-heal fires on the consumer-project .claude/settings.local.json and the offline .peaks/.claude-settings-template.json. Idempotent. Use after a peaks-cli version bump if you do not otherwise re-run init. Mutually exclusive with --detect-1x.')).action(async (options) => {
+        .option('--apply-init', 'slice 4 (slice 2026-06-13-selfheal-claude-settings-template): run initWorkspace so the drift-driven self-heal fires on the consumer-project .claude/settings.local.json and the offline .peaks/.claude-settings-template.json. Idempotent. Use after a peaks-loop version bump if you do not otherwise re-run init. Mutually exclusive with --detect-1x.')).action(async (options) => {
         const projectRoot = options.project ?? process.cwd();
         // Branch 1: --detect-1x (read-only probe)
         if (options.detect1x === true) {
@@ -39,13 +39,13 @@ export function registerUpgradeCommands(program, io) {
         // Branch 2: --apply-init (slice 4 — slice 2026-06-13-selfheal-claude-settings-template).
         //
         // The drift-driven self-heal inside initWorkspace only fires when
-        // the user invokes init. After a peaks-cli version bump, users who
+        // the user invokes init. After a peaks-loop version bump, users who
         // never re-run init are stuck with stale templates until they do.
         // This flag is the post-bump escape hatch: it triggers init for them.
         //
         // We do NOT pass --session-id (the CLI auto-generates / reuses an
         // existing binding). We do NOT pass --no-claude-hooks (the goal is to
-        // bring the project to the current peaks-cli baseline, including the
+        // bring the project to the current peaks-loop baseline, including the
         // consumer-project hook).
         if (options.applyInit === true) {
             try {
@@ -67,7 +67,7 @@ export function registerUpgradeCommands(program, io) {
                 // Surface the same self-heal messaging that workspace-init uses.
                 if (result.claudeSettings.offlineTemplate.action === 'refreshed') {
                     nextActions.push(`Self-healed .peaks/.claude-settings-template.json (action: refreshed) — ` +
-                        'the offline recovery anchor now matches the current peaks-cli template.');
+                        'the offline recovery anchor now matches the current peaks-loop template.');
                     nextActions.push('⚠️  If you had manually edited .peaks/.claude-settings-template.json, ' +
                         'those edits have been overwritten by the self-heal.');
                 }
@@ -77,7 +77,7 @@ export function registerUpgradeCommands(program, io) {
                 }
                 if (result.claudeSettings.action === 'refreshed') {
                     nextActions.push(`Refreshed .claude/settings.local.json (action: refreshed) — ` +
-                        'the consumer-project hook now matches the current peaks-cli template. ' +
+                        'the consumer-project hook now matches the current peaks-loop template. ' +
                         'Restart Claude Code so the hooks take effect.');
                 }
                 else if (result.claudeSettings.action === 'written') {

package/dist/src/cli/commands/workspace/init-command.js

@@ -183,7 +183,7 @@ export function registerWorkspaceInitCommand(workspace, io) {
             // Slice 2026-06-13-selfheal-claude-settings-template: surface
             // the self-heal outcome for the offline
             // `.peaks/.claude-settings-template.json` copy. When the offline
-            // file was refreshed (i.e. the previous peaks-cli release left
+            // file was refreshed (i.e. the previous peaks-loop release left
             // a stale version without the `node -e "..."` wrapper), the user
             // benefits from seeing that the manual-recovery anchor now
             // points at the corrected template. We surface `written` and
@@ -197,7 +197,7 @@ export function registerWorkspaceInitCommand(workspace, io) {
             // to make sure anyone who customised sees the prompt.
             if (report.claudeSettings.offlineTemplate.action === 'refreshed') {
                 nextActions.push(`Self-healed .peaks/.claude-settings-template.json (action: refreshed) — ` +
-                    'the offline recovery anchor now matches the current peaks-cli template. ' +
+                    'the offline recovery anchor now matches the current peaks-loop template. ' +
                     'No action required; future manual recoveries will copy the corrected wrapper.');
                 nextActions.push('⚠️  If you had manually edited .peaks/.claude-settings-template.json, ' +
                     'those edits have been overwritten by the self-heal. ' +

package/dist/src/cli/program.js

@@ -69,6 +69,11 @@ import { registerMutCommands } from './commands/mut-commands.js';
 import { registerFixtureCommands } from './commands/fixture-commands.js';
 import { registerReviewerCommands } from './commands/reviewer-commands.js';
 import { registerObservabilityCommands } from './commands/observability-commands.js';
+// Slice 2026-07-01-strategic-compact-cli: peaks compact
+// (suggest | recommend | survival | dry-run | force) — strategic-compact
+// CLI primitives. See src/services/compact/ and
+// src/cli/commands/compact-command.ts.
+import { registerCompactCommands } from './commands/compact-command.js';
 import { applyRetention } from '../services/log/retention.js';
 import { writeLogEntry, maybeWriteStderr } from '../services/log/logger.js';
 export { printResult } from './cli-helpers.js';
@@ -279,7 +284,7 @@ Run peaks (no arguments) for a quickstart. You likely want one of:
     // Slice #13: peaks swarm * — additional subcommands (pipeline /
     // dispatch / verify / loop) are added inline in workflow-commands.ts
     // alongside the existing swarm.plan. This avoids the duplicate top-level
-    // command conflict (peaks-cli-when-adding-a-new-subcommand-check-for-existing-top-level-first).
+    // command conflict (peaks-loop-when-adding-a-new-subcommand-check-for-existing-top-level-first).
     // Slice #14: peaks loop * + peaks goal compose — L4 Agent Loop sub-features.
     registerLoopCommands(program, io);
     // Slice v3.0.0 loop-eng-native-solo-a-b: peaks workflow run|plan|lint
@@ -332,5 +337,9 @@ Run peaks (no arguments) for a quickstart. You likely want one of:
     // (read-only queries over the JSONL metrics emitted from the
     // peaks request transition hook in Slice A).
     registerObservabilityCommands(program, io);
+    // Slice 2026-07-01-strategic-compact-cli: `peaks compact
+    // suggest|recommend|survival|dry-run|force` — strategic-compact CLI
+    // primitives. See src/cli/commands/compact-command.ts.
+    registerCompactCommands(program, io);
     return program;
 }

package/dist/src/services/agent/ecc-agent-service.js

@@ -2,16 +2,16 @@
  * ECC 64 agents soft-optional integration — `peaks agent run`.
  *
  * Per spec §7.2 line 818: "64 agents — Soft Optional — 装了 L3
- * 直接调; 不装 L3 退化到 peaks-cli 自有少数核心诊断". The
+ * 直接调; 不装 L3 退化到 peaks-loop 自有少数核心诊断". The
  * canonical ECC subprocess contract is:
  *
  *   npx ecc consult "<topic>" --target claude
  *   npx ecc agent run <agent-name> --target <path> --json
  *
- * The peaks-cli `peaks agent run <name> --target <path> --json`
+ * The peaks-loop `peaks agent run <name> --target <path> --json`
  * CLI shells out to the second form. When ECC is missing OR
  * `agentShieldEnabled: false`, the audit completes with a
- * peaks-cli-only envelope.
+ * peaks-loop-only envelope.
  *
  * Mirrors `static-service.ts` (the ECC AgentShield wrapper from
  * L2.3 P2-a): same `subprocessRunner` injection point, same
@@ -102,7 +102,7 @@ export function runEccAgent(input, runner = defaultSubprocessRunner) {
         reason = 'flag-enabled-but-ecc-missing';
         spawned = false;
         warnings.push('`npx ecc --version` failed. Run `npx ecc --help` to install ECC, ' +
-            'then re-run `peaks agent run`. The peaks-cli native diagnostic ' +
+            'then re-run `peaks agent run`. The peaks-loop native diagnostic ' +
             'still runs via `peaks doctor scan`.');
     }
     else {
@@ -123,7 +123,7 @@ export function runEccAgent(input, runner = defaultSubprocessRunner) {
                 parsed = JSON.parse(subResult.stdout);
             }
             catch {
-                // Non-JSON output is allowed; peaks-cli surfaces the raw
+                // Non-JSON output is allowed; peaks-loop surfaces the raw
                 // stdout for the human reader and treats the run as
                 // ok=true (the subprocess exited 0).
                 parsed = undefined;

package/dist/src/services/audit/artifact-writer.d.ts

@@ -3,7 +3,7 @@
  *
  * Generalizes the original `decision-writer.ts` (which only knew how to
  * persist a `RedLineAudit` snapshot) into a polymorphic writer that
- * handles the 4 artifact types produced during a peaks-cli audit:
+ * handles the 4 artifact types produced during a peaks-loop audit:
  *
  *   1. **decision**      — `RedLineAudit` snapshot             → audit-decisions/<slug>.md
  *   2. **prompt**        — methodology input (LLM-facing text) → audit-prompts/<slug>.md

package/dist/src/services/audit/artifact-writer.js

@@ -3,7 +3,7 @@
  *
  * Generalizes the original `decision-writer.ts` (which only knew how to
  * persist a `RedLineAudit` snapshot) into a polymorphic writer that
- * handles the 4 artifact types produced during a peaks-cli audit:
+ * handles the 4 artifact types produced during a peaks-loop audit:
  *
  *   1. **decision**      — `RedLineAudit` snapshot             → audit-decisions/<slug>.md
  *   2. **prompt**        — methodology input (LLM-facing text) → audit-prompts/<slug>.md

package/dist/src/services/audit/decision-writer.d.ts

@@ -21,7 +21,7 @@
  *    ephemeral state. The subdir is named for human discoverability; the
  *    memory service's recursive scan picks it up automatically.
  *
- * 3. **No new CLI subcommand.** Per `peaks-cli-when-adding-a-new-subcommand-…`
+ * 3. **No new CLI subcommand.** Per `peaks-loop-when-adding-a-new-subcommand-…`
  *    we extend the existing `peaks audit static` with a `--record` flag
  *    instead of adding `peaks audit record` (which would be a new
  *    top-level shape and conflict with the dev-preference red line

package/dist/src/services/audit/decision-writer.js

@@ -21,7 +21,7 @@
  *    ephemeral state. The subdir is named for human discoverability; the
  *    memory service's recursive scan picks it up automatically.
  *
- * 3. **No new CLI subcommand.** Per `peaks-cli-when-adding-a-new-subcommand-…`
+ * 3. **No new CLI subcommand.** Per `peaks-loop-when-adding-a-new-subcommand-…`
  *    we extend the existing `peaks audit static` with a `--record` flag
  *    instead of adding `peaks audit record` (which would be a new
  *    top-level shape and conflict with the dev-preference red line

package/dist/src/services/audit/enforcers/lint-output-style.js

@@ -1,8 +1,8 @@
 /**
  * P2-a Theme C — output style enforcers.
  *
- * The peaks-cli dogfood rule: every skill response carries a status
- * header (`Peaks-Cli Skill: <name> | Peaks-Cli Gate: <gate> | Next:
+ * The peaks-loop dogfood rule: every skill response carries a status
+ * header (`Peaks-Loop Skill: <name> | Peaks-Loop Gate: <gate> | Next:
  * <action>`), the SKILL.md body has no greeting/closing-prompt
  * flattery, and the status header is detectable in the recent
  * session transcript (test-only fixture).
@@ -32,7 +32,7 @@ const CLOSING_PROMPTS = [
     /\b随时(欢迎)?(联系|提问)/i,
     /\b随时 (欢迎 )?(联系|提问)/i
 ];
-const STATUS_HEADER_PATTERN = /Peaks-Cli Skill:\s*peaks-[a-z0-9-]+\s*\|\s*Peaks-Cli Gate:\s*[A-Za-z0-9_.-]+\s*\|\s*Next:\s*\S/;
+const STATUS_HEADER_PATTERN = /Peaks-Loop Skill:\s*peaks-[a-z0-9-]+\s*\|\s*Peaks-Loop Gate:\s*[A-Za-z0-9_.-]+\s*\|\s*Next:\s*\S/;
 export function lintNoFluff(skill) {
     const hits = [];
     for (const pattern of FLUFF_GREETINGS) {
@@ -84,10 +84,10 @@ export function lintStatusHeader(projectRoot, sessionId) {
     if (!STATUS_HEADER_PATTERN.test(body)) {
         return [{
                 catalogId: 'rl-output-style-status-header-001',
-                rule: 'Peaks-Cli status header on every response',
+                rule: 'Peaks-Loop status header on every response',
                 file: logPath,
                 line: 1,
-                matchedText: '(no Peaks-Cli Skill / Gate / Next header found in session.log)'
+                matchedText: '(no Peaks-Loop Skill / Gate / Next header found in session.log)'
             }];
     }
     return [];

package/dist/src/services/audit/enforcers/mock-placement.d.ts

@@ -6,7 +6,7 @@
  *
  * Per L2 redesign §5.4. Mocks belong in `tests/fixtures/`, not inline.
  * Per `references/mock-data-placement.md` from peaks-rd: framework-aware
- * mock placement. peaks-cli has no UI framework, but the rule still
+ * mock placement. peaks-loop has no UI framework, but the rule still
  * applies for non-fixture files.
  */
 export interface MockPlacementCheckInput {

package/dist/src/services/audit/enforcers/mock-placement.js

@@ -6,7 +6,7 @@
  *
  * Per L2 redesign §5.4. Mocks belong in `tests/fixtures/`, not inline.
  * Per `references/mock-data-placement.md` from peaks-rd: framework-aware
- * mock placement. peaks-cli has no UI framework, but the rule still
+ * mock placement. peaks-loop has no UI framework, but the rule still
  * applies for non-fixture files.
  */
 const MOCK_PATTERNS = [

package/dist/src/services/audit/enforcers/no-root-pollution.js

@@ -18,7 +18,7 @@ const ROOT_FILE_ALLOWLIST = new Set([
     'tsconfig.*.json', 'vitest.config.ts', 'vite.config.ts', '.npmrc', '.nvmrc',
     // VCS / editor
     '.gitignore', '.gitattributes', '.editorconfig', '.gitkeep',
-    // Project-local config dirs (peaks-cli convention)
+    // Project-local config dirs (peaks-loop convention)
     'openspec', '.peaks', '.claude', '.peaksrc',
     // Source dirs (writes into them are normal)
     'src', 'tests', 'bin', 'scripts', 'schemas', 'output-styles', 'docs',

package/dist/src/services/audit/red-line-catalog-p2-a.js

@@ -73,9 +73,9 @@ const FRONTMATTER_APPLICABLE_TASK_LEVELS = {
 /** Theme C — Output style (3 enforcers) */
 const OUTPUT_STYLE_STATUS_HEADER = {
     id: 'rl-output-style-status-header-001',
-    rule: 'Output style: Peaks-Cli status header on every response',
+    rule: 'Output style: Peaks-Loop status header on every response',
     markers: ['MANDATORY'],
-    phrases: ['peaks-cli skill:', 'peaks-cli gate:', 'peaks-cli next:', 'status header'],
+    phrases: ['peaks-loop skill:', 'peaks-loop gate:', 'peaks-loop next:', 'status header'],
     enforcerRef: 'src/services/audit/enforcers/lint-output-style.ts',
 };
 const OUTPUT_STYLE_NO_FLUFF = {

package/dist/src/services/audit/red-line-catalog-p2-b.js

@@ -118,7 +118,7 @@ const REF_NO_BASH_HEREDOC = {
 };
 const REF_NO_SUDO = {
     id: 'rl-ref-no-sudo-001',
-    rule: 'Reference inline shell: no `sudo` (peaks-cli is user-scope)',
+    rule: 'Reference inline shell: no `sudo` (peaks-loop is user-scope)',
     markers: ['MUST NOT'],
     phrases: ['no sudo', 'user-scope', 'sudo command'],
     enforcerRef: 'src/services/audit/enforcers/lint-reference-shape.ts',
@@ -147,7 +147,7 @@ const REF_NO_FAKE_PROMPT = {
 };
 const REF_NO_ABSOLUTE_PATHS = {
     id: 'rl-ref-no-absolute-paths-001',
-    rule: 'Reference code blocks: no `C:\\` or `/usr/local` (use peaks-cli primitives)',
+    rule: 'Reference code blocks: no `C:\\` or `/usr/local` (use peaks-loop primitives)',
     markers: ['MUST NOT'],
     phrases: ['absolute path', 'c:\\', '/usr/local', 'machine-specific'],
     enforcerRef: 'src/services/audit/enforcers/lint-reference-shape.ts',

package/dist/src/services/audit/static-service.d.ts

@@ -7,7 +7,7 @@
  * (102 lint rules) on a soft-optional basis. When ECC is installed
  * AND `agentShieldEnabled: true`, the audit subprocess spawns the
  * ECC scanner and merges its findings; when either is missing, the
- * audit completes with peaks-cli-only findings.
+ * audit completes with peaks-loop-only findings.
  *
  * The subprocess is **observability enhancement**, not a structural
  * gate — every soft-fail path returns a well-formed audit report.

package/dist/src/services/audit/static-service.js

@@ -7,7 +7,7 @@
  * (102 lint rules) on a soft-optional basis. When ECC is installed
  * AND `agentShieldEnabled: true`, the audit subprocess spawns the
  * ECC scanner and merges its findings; when either is missing, the
- * audit completes with peaks-cli-only findings.
+ * audit completes with peaks-loop-only findings.
  *
  * The subprocess is **observability enhancement**, not a structural
  * gate — every soft-fail path returns a well-formed audit report.
@@ -52,8 +52,8 @@ function isEccInstalled(runner) {
 function runEccScan(projectRoot, runner) {
     try {
         // Per spec §7.2 line 828: the canonical ECC subprocess call uses
-        // `--target <path>`, NOT `--project`. The peaks-cli CLI flag
-        // (`peaks audit static --project <path>`) follows peaks-cli
+        // `--target <path>`, NOT `--project`. The peaks-loop CLI flag
+        // (`peaks audit static --project <path>`) follows peaks-loop
         // convention; the inner ecc-agentshield call follows the
         // upstream ECC contract.
         const result = runner.run('npx', ['ecc-agentshield', 'scan', '--json', '--target', projectRoot], ECC_SCAN_TIMEOUT_MS);
@@ -104,7 +104,7 @@ export function runStaticAudit(input) {
     else if (!installed) {
         // Enabled but ECC missing — soft-fail with a warning.
         warnings.push('agentShieldEnabled is true but `npx ecc-agentshield --version` failed. ' +
-            'Run `npx ecc-agentshield --help` to install. Audit ran with peaks-cli findings only.');
+            'Run `npx ecc-agentshield --help` to install. Audit ran with peaks-loop findings only.');
         state = { spawned: false, installed: false, reason: 'flag-enabled-but-ecc-missing', findings: [] };
     }
     else {
@@ -112,7 +112,7 @@ export function runStaticAudit(input) {
         const findings = runEccScan(input.projectRoot, runner);
         state = { spawned: true, installed: true, reason: 'enabled-and-installed', findings };
     }
-    // Always run the peaks-cli lint layer; merge ECC findings.
+    // Always run the peaks-loop lint layer; merge ECC findings.
     const peaksResult = runRedLinesAudit({ projectRoot: input.projectRoot });
     const mergedAudit = {
         ...peaksResult.audit,

package/dist/src/services/audit/types.d.ts

@@ -1,7 +1,7 @@
 /**
  * Red-line audit framework — types.
  *
- * Spec: docs/superpowers/specs/2026-06-11-peaks-cli-l1-l2-l3-redesign.md §5
+ * Spec: docs/superpowers/specs/2026-06-11-peaks-loop-l1-l2-l3-redesign.md §5
  * PRD:  .peaks/_runtime/2026-06-11-session-f0312d/prd/requests/001-001-l2-1-redlines-audit.md
  * OpenSpec: openspec/changes/2026-06-11-l2-1-redlines-audit/
  *

package/dist/src/services/audit/types.js

@@ -1,7 +1,7 @@
 /**
  * Red-line audit framework — types.
  *
- * Spec: docs/superpowers/specs/2026-06-11-peaks-cli-l1-l2-l3-redesign.md §5
+ * Spec: docs/superpowers/specs/2026-06-11-peaks-loop-l1-l2-l3-redesign.md §5
  * PRD:  .peaks/_runtime/2026-06-11-session-f0312d/prd/requests/001-001-l2-1-redlines-audit.md
  * OpenSpec: openspec/changes/2026-06-11-l2-1-redlines-audit/
  *

package/dist/src/services/audit-independent/perf-audit-service.js

@@ -186,7 +186,7 @@ export function detectPerfAudit(input) {
             ],
             nextActions: [
                 'Verify the perf-audit skill prompt matches PRD AC-3.x output shape.',
-                'If the envelope shape is intentionally different, file a bug at the peaks-cli repo.'
+                'If the envelope shape is intentionally different, file a bug at the peaks-loop repo.'
             ]
         };
     }

package/dist/src/services/audit-independent/security-audit-service.js

@@ -197,7 +197,7 @@ export function detectSecurityAudit(input) {
             ],
             nextActions: [
                 'Verify the security-audit skill prompt matches PRD AC-2.x output shape.',
-                'If the envelope shape is intentionally different, file a bug at the peaks-cli repo.'
+                'If the envelope shape is intentionally different, file a bug at the peaks-loop repo.'
             ]
         };
     }

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

@@ -1,7 +1,7 @@
 /**
  * L1a task classification service.
  *
- * Spec: docs/superpowers/specs/2026-06-11-peaks-cli-l1-l2-l3-redesign.md §4
+ * Spec: docs/superpowers/specs/2026-06-11-peaks-loop-l1-l2-l3-redesign.md §4
  *
  * Hybrid mechanism: signal-based heuristic + user override + audit log.
  *

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

@@ -1,7 +1,7 @@
 /**
  * L1a task classification service.
  *
- * Spec: docs/superpowers/specs/2026-06-11-peaks-cli-l1-l2-l3-redesign.md §4
+ * Spec: docs/superpowers/specs/2026-06-11-peaks-loop-l1-l2-l3-redesign.md §4
  *
  * Hybrid mechanism: signal-based heuristic + user override + audit log.
  *

package/dist/src/services/classify/classify-types.d.ts

@@ -1,7 +1,7 @@
 /**
  * L1a task classification — types and per-level gate sets.
  *
- * Spec: docs/superpowers/specs/2026-06-11-peaks-cli-l1-l2-l3-redesign.md §4
+ * Spec: docs/superpowers/specs/2026-06-11-peaks-loop-l1-l2-l3-redesign.md §4
  *
  * Five task levels: typo / bug / feature / refactor / migration. Each
  * level has a gate set (the "配套 gate set" — L1b) that the slice

package/dist/src/services/classify/classify-types.js

@@ -1,7 +1,7 @@
 /**
  * L1a task classification — types and per-level gate sets.
  *
- * Spec: docs/superpowers/specs/2026-06-11-peaks-cli-l1-l2-l3-redesign.md §4
+ * Spec: docs/superpowers/specs/2026-06-11-peaks-loop-l1-l2-l3-redesign.md §4
  *
  * Five task levels: typo / bug / feature / refactor / migration. Each
  * level has a gate set (the "配套 gate set" — L1b) that the slice

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

@@ -6,7 +6,7 @@
  * Gate B3 already reads (`mustContain: ['## Findings', 'CRITICAL']`).
  *
  * Companion to `ocr-service.ts`: ECC is the in-skill agent option
- * (uses peaks-cli's own Agent tool surface), ocr is the external
+ * (uses peaks-loop's own Agent tool surface), ocr is the external
  * subprocess option. Both produce a second-opinion code review that
  * the parent RD loop aggregates alongside its own inline review.
  *
@@ -26,7 +26,7 @@
  *
  * ECC is shipped via the `everything-claude-code` plugin, not as a
  * separate npm package. The user installs the plugin (a one-time
- * marketplace step); peaks-cli does not write or read any LLM
+ * marketplace step); peaks-loop does not write or read any LLM
  * endpoint config for ECC. If a future ECC release needs user-
  * managed config (URL / token / model), add a `peaksConfig.ecc.*`
  * block then — not speculatively now.

package/dist/src/services/code-review/ecc-bridge.js

@@ -210,8 +210,8 @@ export function detectEcc(input) {
                 'ECC `code-review` agent returned a value that failed envelope validation (expected { passed, violations, gateAction }).'
             ],
             nextActions: [
-                'Verify the ECC plugin version is compatible with peaks-cli 2.11.0+ (this bridge).',
-                'If the envelope shape is intentionally different, file a bug at the peaks-cli repo.'
+                'Verify the ECC plugin version is compatible with peaks-loop 2.11.0+ (this bridge).',
+                'If the envelope shape is intentionally different, file a bug at the peaks-loop repo.'
             ]
         };
     }

package/dist/src/services/code-review/ocr-service.d.ts

@@ -6,9 +6,9 @@ export interface OcrDetectResult {
     readonly binaryPath: string | null;
     readonly version: string | null;
     /**
-     * The peaks-cli config path that holds `peaksConfig.ocr.llm`.
+     * The peaks-loop config path that holds `peaksConfig.ocr.llm`.
      * The user pastes the `peaks code-review config-template` output
-     * here. Empty string when peaks-cli has not been bootstrapped.
+     * here. Empty string when peaks-loop has not been bootstrapped.
      */
     readonly configPath: string;
     readonly configValid: boolean;
@@ -49,7 +49,7 @@ export interface SubprocessRunner {
 /**
  * Locate the ocr launcher script (`bin/ocr.js`) inside our own
  * node_modules tree. Returns null when the npm package is not
- * present (peaks-cli was installed but its dependency tree is
+ * present (peaks-loop was installed but its dependency tree is
  * corrupt, or the user removed it).
  *
  * Walks up from this file (dist/src/services/code-review/) to
@@ -58,7 +58,7 @@ export interface SubprocessRunner {
 export declare function resolveOcrLauncher(searchRoots: readonly string[]): string | null;
 /**
  * Resolve search roots for the ocr launcher. We look in two
- * places: (1) the peaks-cli install root (next to our own dist/),
+ * places: (1) the peaks-loop install root (next to our own dist/),
  * (2) the user's cwd.
  */
 export declare function defaultOcrSearchRoots(currentDirPath: string, cwd: string): readonly string[];
@@ -69,19 +69,19 @@ export declare function defaultOcrSearchRoots(currentDirPath: string, cwd: strin
  * the block is ready to drive the ocr subprocess.
  *
  * The block is independent of the OCR package's own
- * `~/.opencodereview/config.json` file. peaks-cli only ever reads
+ * `~/.opencodereview/config.json` file. peaks-loop only ever reads
  * from its own config; the env-var injection in `runOcrReview`
  * makes the legacy file irrelevant.
  */
 export declare function getOcrLlmMissingFields(llm: OcrLlmConfig | null): readonly string[];
 /**
- * Build the env-var overlay peaks-cli injects into the ocr
+ * Build the env-var overlay peaks-loop injects into the ocr
  * subprocess. Maps `peaksConfig.ocr.llm` onto the OCR package's
  * env-var surface (its highest-priority config source).
  */
 export declare function buildOcrEnv(llm: OcrLlmConfig): NodeJS.ProcessEnv;
 /**
- * The JSON template the user pastes into their peaks-cli config
+ * The JSON template the user pastes into their peaks-loop config
  * (`peaksConfig.ocr.llm`). Returned as a stable string so the
  * `peaks code-review config-template` CLI command can print it
  * verbatim, and so the detector's `nextActions` payload embeds
@@ -91,7 +91,7 @@ export declare function getOcrConfigTemplate(): string;
 export interface OcrDetectOptions {
     readonly cwd: string;
     /**
-     * The peaks-cli config path that holds `peaksConfig.ocr.llm`.
+     * The peaks-loop config path that holds `peaksConfig.ocr.llm`.
      * Surfaced in the detect result so the user knows where to
      * paste the template.
      */
@@ -123,7 +123,7 @@ export interface OcrReviewOptions extends OcrDetectOptions {
  * The LLM endpoint config from `peaksConfig.ocr.llm` is injected
  * as env vars (`OCR_LLM_URL` / `OCR_LLM_TOKEN` / ...), which the
  * ocr package treats as the highest-priority config source. This
- * is how peaks-cli wires the user-managed config into the ocr
+ * is how peaks-loop wires the user-managed config into the ocr
  * subprocess without ever writing `~/.opencodereview/config.json`.
  */
 export declare function runOcrReview(options: OcrReviewOptions): OcrReviewResult;