peaks-loop 3.0.0 → 3.0.1

package/dist/src/services/mut/production-stryker.js

@@ -1,20 +1,23 @@
+/**
+ * Production Stryker invoker. Uses @stryker-mutator/core programmatic API.
+ * Note: this is a thin wrapper — actual Stryker invocation requires the
+ * Stryker config in `stryker.conf.js` to live at the project root.
+ */
+import { relative, isAbsolute } from 'node:path';
 export function createProductionStrykerInvoker() {
-    return async ({ project, testFiles }) => {
+    return async ({ project, testFiles: _testFiles }) => {
         // Lazy-load Stryker so unit tests don't need it installed.
         // eslint-disable-next-line @typescript-eslint/no-require-imports
         const Stryker = (await import('@stryker-mutator/core')).Stryker;
-        const options = {
-            // Project-rooted config; explicit overrides here are minimal.
-            mutate: [...testFiles],
-        };
-        // Single cast derives from Stryker's actual constructor signature.
-        // Stryker 8's MutantResult extends our local StrykerMutant structurally.
-        const stryker = new Stryker(options);
+        // Mutation surface is owned by stryker.conf.js. testFiles is a runtime
+        // hint (consumed by the configured testRunner, not by Stryker's `mutate`
+        // field — `mutate` is source files to mutate, never test paths).
+        const stryker = new Stryker({});
         const mutants = (await stryker.runMutationTest());
         return normalize(mutants, project);
     };
 }
-function normalize(mutants, _project) {
+function normalize(mutants, project) {
     let mutantsKilled = 0;
     let mutantsSurvived = 0;
     let mutantsTimeout = 0;
@@ -31,7 +34,13 @@ function normalize(mutants, _project) {
     // empty (as v0 did) silently swallowed those followups in production.
     const byFile = new Map();
     for (const m of mutants) {
-        const file = m.fileName;
+        // Stryker 8 returns absolute paths in MutantResult.fileName. Strip the
+        // project root so byFile[].file is repo-relative (e.g. "src/services/loop/...").
+        // path.relative falls back to the absolute path when input is outside
+        // project, which is the safest failure mode.
+        const file = isAbsolute(m.fileName) && m.fileName.startsWith(project)
+            ? relative(project, m.fileName)
+            : m.fileName;
         let bucket = byFile.get(file);
         if (!bucket) {
             bucket = { killed: 0, survived: 0, survivedEntries: [] };

package/dist/src/services/openspec/openspec-propose-from-doctor-service.d.ts

@@ -4,7 +4,7 @@
  *
  * Per L1+L2+L3 redesign §5.4: "CRITICAL → proposal 草稿生成". The doctor
  * scans the project for issues; when a CRITICAL finding is surfaced,
- * peaks-cli generates a draft `openspec/changes/<id>/proposal.md` so the
+ * peaks-loop generates a draft `openspec/changes/<id>/proposal.md` so the
  * LLM doesn't have to start from scratch.
  *
  * The draft proposal is INFORMATIONAL — it requires the LLM to review +

package/dist/src/services/openspec/openspec-propose-from-doctor-service.js

@@ -4,7 +4,7 @@
  *
  * Per L1+L2+L3 redesign §5.4: "CRITICAL → proposal 草稿生成". The doctor
  * scans the project for issues; when a CRITICAL finding is surfaced,
- * peaks-cli generates a draft `openspec/changes/<id>/proposal.md` so the
+ * peaks-loop generates a draft `openspec/changes/<id>/proposal.md` so the
  * LLM doesn't have to start from scratch.
  *
  * The draft proposal is INFORMATIONAL — it requires the LLM to review +

package/dist/src/services/perf/perf-baseline-service.d.ts

@@ -16,7 +16,7 @@
  * `.peaks/_runtime/<sid>/rd/perf-baseline.md` so QA Gate A4 has a known-good
  * reference to diff against. The CLI itself only writes the scaffold
  * and records the path; the actual measurement is a project-local
- * concern that lives in the README, not in peaks-cli.
+ * concern that lives in the README, not in peaks-loop.
  *
  * The four-grounds check (per the skill-primary-CLI-auxiliary dev
  * preference):
@@ -33,7 +33,7 @@
  *                                     NOT add a lint gate here.
  *
  * Net: CLI is justified. The destructive --apply default is dry-run,
- * matching the rest of peaks-cli's scaffolding pattern.
+ * matching the rest of peaks-loop's scaffolding pattern.
  */
 export type PerfBaselineInitOptions = {
     projectRoot: string;

package/dist/src/services/perf/perf-baseline-service.js

@@ -16,7 +16,7 @@
  * `.peaks/_runtime/<sid>/rd/perf-baseline.md` so QA Gate A4 has a known-good
  * reference to diff against. The CLI itself only writes the scaffold
  * and records the path; the actual measurement is a project-local
- * concern that lives in the README, not in peaks-cli.
+ * concern that lives in the README, not in peaks-loop.
  *
  * The four-grounds check (per the skill-primary-CLI-auxiliary dev
  * preference):
@@ -33,7 +33,7 @@
  *                                     NOT add a lint gate here.
  *
  * Net: CLI is justified. The destructive --apply default is dry-run,
- * matching the rest of peaks-cli's scaffolding pattern.
+ * matching the rest of peaks-loop's scaffolding pattern.
  */
 import { mkdir, writeFile } from 'node:fs/promises';
 import { existsSync } from 'node:fs';

package/dist/src/services/prd/handoff-auto-regen.js

@@ -41,7 +41,7 @@ export async function autoRegenPrdHandoff(opts) {
     const sha256 = sha256OfBody(body);
     // v2.13.3 AC-4 — align with `AUDIT_REQUIRES_HANDOFF` prereq which
     // pins `mustContain: ['schemaVersion: 2', 'sha256:']`. The previous
-    // field name `handoffHash` made peaks-cli write a handoff that the
+    // field name `handoffHash` made peaks-loop write a handoff that the
     // own prereq resolver would reject with "missing section(s): sha256:".
     // Primary field is now `sha256`; `handoffHash` is kept as a literal
     // alias for back-compat with any consumer (UI / external scripts)

package/dist/src/services/prd/project-scan-sediment.js

@@ -307,9 +307,9 @@ function splitTableRow(row) {
 }
 function renderFreshAuditPatternBody(args) {
     const titleByKind = {
-        'security-audit': 'Security Audit Template (peaks-cli v2.12.0)',
-        'perf-audit': 'Performance Audit Template (peaks-cli v2.12.0)',
-        'audit-output-schema': 'Audit Output Schema (peaks-cli v2.12.0)'
+        'security-audit': 'Security Audit Template (peaks-loop v2.12.0)',
+        'perf-audit': 'Performance Audit Template (peaks-loop v2.12.0)',
+        'audit-output-schema': 'Audit Output Schema (peaks-loop v2.12.0)'
     };
     const appliesToByKind = {
         'security-audit': 'peaks-security-audit skill',

package/dist/src/services/prd/project-scan-types.d.ts

@@ -19,7 +19,7 @@
  */
 /** Tech-stack snapshot. `language` / `packageManager` are closed
  *  unions (Karpathy §2 — no string sprawl); `runtime` / `buildTool`
- *  are free-form (peaks-cli does not constrain them). */
+ *  are free-form (peaks-loop does not constrain them). */
 export interface ProjectScanTechStack {
     readonly language: 'typescript';
     readonly packageManager: 'pnpm';

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

@@ -1,9 +1,9 @@
 /**
- * peaks-cli 2.0 project-local preferences schema.
+ * peaks-loop 2.0 project-local preferences schema.
  * Per spec §8.4 — per-project state lives in `.peaks/preferences.json`,
  * NOT in `~/.peaks/config.json` (which is slim global).
  *
- * Spec reference: docs/superpowers/specs/2026-06-11-peaks-cli-l1-l2-l3-redesign.md §8.4
+ * Spec reference: docs/superpowers/specs/2026-06-11-peaks-loop-l1-l2-l3-redesign.md §8.4
  */
 export declare const PREFERENCES_SCHEMA_VERSION = "2.0.0";
 /**
@@ -110,7 +110,7 @@ export interface ProjectPreferences {
      *
      * When true, `peaks audit static` spawns `npx ecc-agentshield scan --json`
      * and merges its findings into the audit report. When false (default),
-     * the audit runs peaks-cli-only and the subprocess is never spawned.
+     * the audit runs peaks-loop-only and the subprocess is never spawned.
      *
      * The preference is independent of whether ECC is installed — i.e.
      * `agentShieldEnabled: true` with ECC missing surfaces a soft

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

@@ -1,9 +1,9 @@
 /**
- * peaks-cli 2.0 project-local preferences schema.
+ * peaks-loop 2.0 project-local preferences schema.
  * Per spec §8.4 — per-project state lives in `.peaks/preferences.json`,
  * NOT in `~/.peaks/config.json` (which is slim global).
  *
- * Spec reference: docs/superpowers/specs/2026-06-11-peaks-cli-l1-l2-l3-redesign.md §8.4
+ * Spec reference: docs/superpowers/specs/2026-06-11-peaks-loop-l1-l2-l3-redesign.md §8.4
  */
 export const PREFERENCES_SCHEMA_VERSION = '2.0.0';
 export const FANOUT_MODES = ['fan-out'];

package/dist/src/services/role/role-registry.d.ts

@@ -32,7 +32,7 @@ export declare function upsertRole(registry: RoleRegistry, role: Role): RoleRegi
 export declare function grantPermission(registry: RoleRegistry, roleName: string, permission: string): RoleRegistry;
 /** Check if a role has a permission. */
 export declare function roleHasPermission(registry: RoleRegistry, roleName: string, permission: string): boolean;
-/** Permission categories that align with the peaks-cli 12 Gaps memory. */
+/** Permission categories that align with the peaks-loop 12 Gaps memory. */
 export declare const DEFAULT_PERMISSIONS: readonly string[];
 /** Default role preset for a Senior FE on a 24h AI programmer team. */
 export declare const DEFAULT_SENIOR_FE_ROLE: Role;

package/dist/src/services/role/role-registry.js

@@ -59,7 +59,7 @@ export function roleHasPermission(registry, roleName, permission) {
         return false;
     return role.permissions.includes(permission);
 }
-/** Permission categories that align with the peaks-cli 12 Gaps memory. */
+/** Permission categories that align with the peaks-loop 12 Gaps memory. */
 export const DEFAULT_PERMISSIONS = [
     'prd.write',
     'prd.confirm',

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

@@ -23,7 +23,7 @@ const RETENTION_REQUIREMENTS = [
     ['txt', 'context-capsule.md']
 ];
 /**
- * "Modern" retention requirements for the current peaks-cli artifact
+ * "Modern" retention requirements for the current peaks-loop artifact
  * naming convention. The legacy `RETENTION_REQUIREMENTS` above assume
  * older `refactor-goal.md` / `slice-spec.md` / `coverage-report.md` /
  * `validation-report.md` / `change-impact.json` / `retention-boundary.md`
@@ -502,10 +502,10 @@ export function validateArtifactRetention(sliceId) {
     // If the legacy check is short (i.e. we're missing a lot of legacy-named
     // files) but the resolver landed on a real session, ALSO accept the
     // modern set. The legacy set was designed for an older workflow naming
-    // and a freshly-minted session in the current peaks-cli flow will not
+    // and a freshly-minted session in the current peaks-loop flow will not
     // have the legacy names. This keeps `peaks sc validate --slice-id <rid>`
     // returning `valid: true` for slices that completed under the current
-    // peaks-cli convention.
+    // peaks-loop convention.
     if (missingArtifacts.length > 0 && resolvedPeaksSessionDir !== null) {
         const modernMissing = modernRequirementRelativePaths(sliceId).filter((rel) => !resolvedPresent(...rel.split('/')));
         if (modernMissing.length === 0) {

package/dist/src/services/skill/resume-detector.js

@@ -1,8 +1,8 @@
 /**
- * Peaks-Cli Solo Step 0.7 — Resume-mode detector.
+ * Peaks-Loop Solo Step 0.7 — Resume-mode detector.
  *
  * Mirrors the classification table in
- * `skills/peaks-solo/SKILL.md` "Peaks-Cli Step 0.7: Detect unfinished work
+ * `skills/peaks-solo/SKILL.md` "Peaks-Loop Step 0.7: Detect unfinished work
  * and offer resume". The function is a pure read of session artifacts;
  * it performs no side effects and is safe to call from hooks, scripts,
  * and skills.

package/dist/src/services/skills/sync-service.d.ts

@@ -47,10 +47,10 @@ interface InstallResult {
 }
 type InstallerFn = (opts: InstallBundledSkillsOptions) => InstallResult;
 /**
- * Resolve the path of `install-skills.mjs` inside the peaks-cli
+ * Resolve the path of `install-skills.mjs` inside the peaks-loop
  * install root, walking up from `import.meta.url` until a
- * `package.json` with `"name": "peaks-cli"` is found. Returns
- * `null` when peaks-cli is not on the import path or the script
+ * `package.json` with `"name": "peaks-loop"` is found. Returns
+ * `null` when peaks-loop is not on the import path or the script
  * is absent (e.g. a partial install).
  */
 export declare function resolvePeaksCliInstallerPath(): string | null;

package/dist/src/services/skills/sync-service.js

@@ -9,13 +9,13 @@
  * is `scripts/install-skills.mjs::installBundledSkills` (dynamically
  * imported so this module does not require a build step).
  *
- * Slice 2.0.1-bug2-skill-sync-fallback: when peaks-cli is
+ * Slice 2.0.1-bug2-skill-sync-fallback: when peaks-loop is
  * installed from npm into a consumer project, that consumer's
  * CWD does not contain `scripts/install-skills.mjs`. The previous
  * hard-coded `join(process.cwd(), 'scripts', 'install-skills.mjs')`
  * therefore threw `ERR_MODULE_NOT_FOUND` in every consumer run.
  * The fix is a three-tier probe:
- *   1. peaks-cli's own install path (resolved from
+ *   1. peaks-loop's own install path (resolved from
  *      `import.meta.url` walking up to the package root, or
  *      from `process.argv[1]` for CJS-equivalent entrypoints),
  *   2. the consumer CWD (`<cwd>/scripts/install-skills.mjs`),
@@ -62,7 +62,7 @@ function noopInstaller(_opts) {
     return {
         installed: [],
         skipped: [
-            'install-skills.mjs not found in project; skill sync skipped — bundled skills are installed via peaks-cli postinstall',
+            'install-skills.mjs not found in project; skill sync skipped — bundled skills are installed via peaks-loop postinstall',
         ],
     };
 }
@@ -79,10 +79,10 @@ const services = {
     loadInstallerForTest,
 };
 /**
- * Resolve the path of `install-skills.mjs` inside the peaks-cli
+ * Resolve the path of `install-skills.mjs` inside the peaks-loop
  * install root, walking up from `import.meta.url` until a
- * `package.json` with `"name": "peaks-cli"` is found. Returns
- * `null` when peaks-cli is not on the import path or the script
+ * `package.json` with `"name": "peaks-loop"` is found. Returns
+ * `null` when peaks-loop is not on the import path or the script
  * is absent (e.g. a partial install).
  */
 export function resolvePeaksCliInstallerPath() {
@@ -154,7 +154,7 @@ export async function loadInstallerForTest(scriptPath) {
 }
 /**
  * Resolve and load the installer, memoizing the outcome.
- * Three-tier probe (peaks-cli install path → CWD → no-op),
+ * Three-tier probe (peaks-loop install path → CWD → no-op),
  * with the "not found" outcome memoized as a sentinel so the
  * warning is logged at most once per process.
  *
@@ -171,7 +171,7 @@ async function loadInstaller() {
     if (cachedInstaller !== null) {
         return cachedInstaller;
     }
-    // Tier 1: peaks-cli install path.
+    // Tier 1: peaks-loop install path.
     const peaksCliScript = services.resolvePeaksCliInstallerPath();
     if (peaksCliScript !== null) {
         const installer = await services.loadInstallerForTest(peaksCliScript);
@@ -191,7 +191,7 @@ async function loadInstaller() {
     cachedInstaller = NO_INSTALLER_SENTINEL;
     // eslint-disable-next-line no-console -- intentional user-visible signal
     console.warn('peaks skill sync: install-skills.mjs not found in project; ' +
-        'skipping (bundled skills come from peaks-cli postinstall).');
+        'skipping (bundled skills come from peaks-loop postinstall).');
     return noopInstaller;
 }
 /**

package/dist/src/services/slice/calibration-store.d.ts

@@ -10,7 +10,7 @@
  *   sample size >= 5 for a complexity bucket, switch to percentile-based
  *   estimate with confidence 'high'.
  *
- * v1 rationale: peaks-cli itself has fewer than 5 completed refactor slices
+ * v1 rationale: peaks-loop itself has fewer than 5 completed refactor slices
  * (per the design doc R3), so v1 cannot be calibrated yet. v1 ships the
  * heuristic AND records every estimate to `.peaks/_runtime/<sid>/sc/
  * slice-calibration/<rid>.json` so the next slice can use the prior data.

package/dist/src/services/slice/calibration-store.js

@@ -10,7 +10,7 @@
  *   sample size >= 5 for a complexity bucket, switch to percentile-based
  *   estimate with confidence 'high'.
  *
- * v1 rationale: peaks-cli itself has fewer than 5 completed refactor slices
+ * v1 rationale: peaks-loop itself has fewer than 5 completed refactor slices
  * (per the design doc R3), so v1 cannot be calibrated yet. v1 ships the
  * heuristic AND records every estimate to `.peaks/_runtime/<sid>/sc/
  * slice-calibration/<rid>.json` so the next slice can use the prior data.

package/dist/src/services/solo/auto-compact-orchestrator.d.ts

@@ -7,7 +7,7 @@ export interface AutoCompactInput {
     readonly inFlightBatch?: InFlightBatchProbe | undefined;
     /**
      * Force execute even when ratio < threshold (test seam). In
-     * production this is always `false` — peaks-cli drives compact
+     * production this is always `false` — peaks-loop drives compact
      * autonomously at 0.85+ with zero human / zero LLM intervention.
      */
     readonly force?: boolean | undefined;

package/dist/src/services/solo/auto-compact-orchestrator.js

@@ -2,29 +2,29 @@
  * Auto-compact orchestrator (v2.13.0 AC-2 + AC-3 + AC-4).
  *
  * Closes the loop between `peaks context now` (AC-1) and the IDE's
- * native compact capability (AC-3). peaks-cli is project-aware: it
+ * native compact capability (AC-3). peaks-loop is project-aware: it
  * knows the current plan, open questions, recent decisions, in-flight
  * batches, todo state, git status, and active skills. That context is
  * strictly more valuable than what `/compact` can synthesize from raw
- * conversation history — so peaks-cli drives the entire compaction:
+ * conversation history — so peaks-loop drives the entire compaction:
  *
  *   1. Read current context % (via IDE adapter's `readContextPercent`).
- *   2. If ratio ≥ 0.95 (RED LINE): synchronous gate — peaks-cli
+ *   2. If ratio ≥ 0.95 (RED LINE): synchronous gate — peaks-loop
  *      refuses sub-agent dispatch and forces IDE compact immediately.
  *      The LLM cannot opt out (compact red line — keeps the runner
  *      alive).
- *   3. If 0.85 ≤ ratio < 0.95 (pre-compact zone): peaks-cli prepares
+ *   3. If 0.85 ≤ ratio < 0.95 (pre-compact zone): peaks-loop prepares
  *      the convergence toolkit (checkpoint + auto-decisions log +
  *      IDE-dispatch handle) and surfaces it to the LLM. The LLM
  *      DECIDES when to fire `peaks solo auto-compact --execute`;
- *      peaks-cli does NOT auto-fire. The toolkit is ready so the
+ *      peaks-loop does NOT auto-fire. The toolkit is ready so the
  *      LLM doesn't lose context to a last-second `/compact` panic.
  *   4. If ratio < 0.85: skip — return a one-line info row.
  *
  * Why two tiers (vs. one): the LLM uses the 0.85–0.95 zone for
  * intelligent convergence — wait for in-flight sub-agents, finish
  * the current todo row, persist a checkpoint, then compact. At 0.95
- * the window is gone; peaks-cli takes over synchronously. Net effect:
+ * the window is gone; peaks-loop takes over synchronously. Net effect:
  * the LLM-runner keeps working with context < 95% without human
  * intervention.
  */
@@ -95,7 +95,7 @@ export function evaluateAutoCompactDecision(input) {
     if (input.force) {
         return { shouldCompact: true, reason: 'pre-compact', trigger };
     }
-    // Default: peaks-cli drives pre-compact autonomously.
+    // Default: peaks-loop drives pre-compact autonomously.
     return { shouldCompact: true, reason: 'pre-compact', trigger };
 }
 /**

package/dist/src/services/solo/dag-orchestrator.js

@@ -105,7 +105,7 @@ export function buildDispatchSpec(dag, sliceId, contracts, defaultPrompt) {
         '',
         `[slice-dag-dispatcher MVP 1.2] execute slice "${sliceId}" (role=${node.role})${labelFragment}.`,
         '',
-        'Scope: this is the 2.7.0 MVP dogfood of peaks-cli DAG-aware dispatch. You are one leaf in a multi-slice plan; the orchestrator has already validated the DAG, built a topological order, and injected your upstream contracts above.',
+        'Scope: this is the 2.7.0 MVP dogfood of peaks-loop DAG-aware dispatch. You are one leaf in a multi-slice plan; the orchestrator has already validated the DAG, built a topological order, and injected your upstream contracts above.',
         '',
         'Handoff protocol (REQUIRED — orchestrator depends on this):',
         '  1. Execute the slice to completion.',

package/dist/src/services/solo/mode-gate.d.ts

@@ -144,7 +144,7 @@ export declare function formatAutoProceedLogLine(opts: {
  *   - `git-tag`             → `git tag v2.15.0`, `git tag -a v2.15.0 -m ...`
  *   - `npm-publish`         → `npm publish`, `npm publish --access public`
  *   - `npm-install-global`  → `npm install -g <pkg>`, `npm i -g <pkg>`
- *   - `peaks-global-install`→ `npm install -g peaks-cli`, `pnpm add -g peaks-cli`
+ *   - `peaks-global-install`→ `npm install -g peaks-loop`, `pnpm add -g peaks-loop`
  *
  * These are coarse — false positives are fine (worst case: a
  * non-actionable command gets paused for confirmation; the user

package/dist/src/services/solo/mode-gate.js

@@ -164,7 +164,7 @@ export function formatAutoProceedLogLine(opts) {
  *   - `git-tag`             → `git tag v2.15.0`, `git tag -a v2.15.0 -m ...`
  *   - `npm-publish`         → `npm publish`, `npm publish --access public`
  *   - `npm-install-global`  → `npm install -g <pkg>`, `npm i -g <pkg>`
- *   - `peaks-global-install`→ `npm install -g peaks-cli`, `pnpm add -g peaks-cli`
+ *   - `peaks-global-install`→ `npm install -g peaks-loop`, `pnpm add -g peaks-loop`
  *
  * These are coarse — false positives are fine (worst case: a
  * non-actionable command gets paused for confirmation; the user
@@ -176,7 +176,7 @@ export const COMMIT_BOUNDARY_PATTERNS = {
     'git-tag': /\bgit\s+tag\b/,
     'npm-publish': /\bnpm\s+(publish|pub)\b/,
     'npm-install-global': /\bnpm\s+(install|i|add)\s+(-g|--global)\b/,
-    'peaks-global-install': /\b(peaks-cli)\b/
+    'peaks-global-install': /\b(peaks-loop)\b/
 };
 /**
  * v2.15.0 slice 002 AC-4: detect whether a Bash command matches any
@@ -190,8 +190,8 @@ export function detectCommitBoundaryAction(command) {
     if (typeof command !== 'string' || command.length === 0)
         return null;
     // Order matters: peaks-global-install is the most specific
-    // (matches only the peaks-cli package name). Test that FIRST so
-    // `npm install -g peaks-cli` is attributed correctly. Then
+    // (matches only the peaks-loop package name). Test that FIRST so
+    // `npm install -g peaks-loop` is attributed correctly. Then
     // git-push, git-tag, npm-publish, npm-install-global.
     if (COMMIT_BOUNDARY_PATTERNS['peaks-global-install'].test(command)) {
         return 'peaks-global-install';

package/dist/src/services/solo/user-touchpoint-classifier.js

@@ -141,5 +141,5 @@ export const COMMIT_BOUNDARY_ACTIONS_LIST = [
     { id: 'git-tag', description: 'git tag v2.15.0 / git tag -a ...' },
     { id: 'npm-publish', description: 'npm publish / npm pub' },
     { id: 'npm-install-global', description: 'npm install -g / npm i -g / npm add -g' },
-    { id: 'peaks-global-install', description: 'peaks-cli 全局安装 / npm install -g peaks-cli' }
+    { id: 'peaks-global-install', description: 'peaks-loop 全局安装 / npm install -g peaks-loop' }
 ];

package/dist/src/services/standards/migrate-claude-rules-service.js

@@ -2,7 +2,7 @@
  * peaks standards migrate — .claude/rules/ tree thinning.
  * Slice: 2026-06-12-standards-migrate-claude-rules.
  *
- * The 1.x peaks-cli install copied a thick .claude/rules
+ * The 1.x peaks-loop install copied a thick .claude/rules
  * tree (skill-first / CLI-auxiliary / dogfood / commit-trailer
  * rules) into consumer projects. In 2.0, the canonical rules
  * live at .peaks/standards/ and every markdown file under
@@ -23,7 +23,7 @@
  */
 import { existsSync, mkdirSync, readdirSync, readFileSync, statSync, writeFileSync } from 'node:fs';
 import { join } from 'node:path';
-const POINTER_TEXT = (canonicalPath) => `# Canonical peaks-cli 2.0 rules live at: ${canonicalPath}\n# This file is a 2-line pointer. Edit the canonical file instead.\n`;
+const POINTER_TEXT = (canonicalPath) => `# Canonical peaks-loop 2.0 rules live at: ${canonicalPath}\n# This file is a 2-line pointer. Edit the canonical file instead.\n`;
 function timestampSlug() {
     return new Date().toISOString().replace(/[:.]/g, '-');
 }
@@ -47,13 +47,13 @@ function isAlreadyPointer(filePath) {
         return false;
     try {
         const body = readFileSync(filePath, 'utf8');
-        return body.includes('Canonical peaks-cli 2.0 rules live at:');
+        return body.includes('Canonical peaks-loop 2.0 rules live at:');
     }
     catch {
         return false;
     }
 }
-const CANONICAL_2_0_DEV_PREFERENCE = `# Peaks-Cli dev preference (2.0 canonical)
+const CANONICAL_2_0_DEV_PREFERENCE = `# Peaks-Loop dev preference (2.0 canonical)
 
 > Project-local preference, captured from the 1.x install + re-rendered with the 2.0 vocabulary.
 > Scope: applies to every iteration, adjustment, fix, or tweak on this project.
@@ -61,7 +61,7 @@ const CANONICAL_2_0_DEV_PREFERENCE = `# Peaks-Cli dev preference (2.0 canonical)
 
 ## Rule 1 — Skill-first, CLI-auxiliary
 
-When designing or modifying a peaks-cli feature, default to the **skill-first** design. CLI commands are **invoked by the skill prompt** when they are the right primitive: a side effect that must be atomic, a gate that must be machine-enforced, a probe that needs structured JSON, or a backstop that prevents the LLM from skipping a step. Behaviour only an LLM in a skill prompt would use lives **in the relevant skill's SKILL.md**, not as a new CLI command. See \`.claude/rules/common/dev-preference.md\` for the decision template.
+When designing or modifying a peaks-loop feature, default to the **skill-first** design. CLI commands are **invoked by the skill prompt** when they are the right primitive: a side effect that must be atomic, a gate that must be machine-enforced, a probe that needs structured JSON, or a backstop that prevents the LLM from skipping a step. Behaviour only an LLM in a skill prompt would use lives **in the relevant skill's SKILL.md**, not as a new CLI command. See \`.claude/rules/common/dev-preference.md\` for the decision template.
 
 ## Rule 2 — Dogfood on every adjustment
 

package/dist/src/services/standards/migrate-service.d.ts

@@ -8,9 +8,9 @@
  *   2. required the LLM to invoke `peaks skill heartbeat:touch` and
  *      `peaks skill presence:clear` on every turn;
  *   3. ended with an `External reference: https://github.com/affaan-m/...`
- *      line that was peaks-cli-internal, not consumer-facing.
+ *      line that was peaks-loop-internal, not consumer-facing.
  *
- * The replacement text matches the post-slice-025 peaks-cli repo's own
+ * The replacement text matches the post-slice-025 peaks-loop repo's own
  * `CLAUDE.md`: route the LLM through `peaks skill presence --json` and
  * render a compact status header when a valid skill is active. This
  * service is the deterministic in-place rewriter that brings existing
@@ -27,7 +27,7 @@
  *   - File missing → `file: null`, no throw.
  *   - Legacy block not present → `foundOldBlock: false`, no write.
  */
-export declare const NEW_TEMPLATE_TEXT = "Active Peaks-Cli skill presence: at the start of every response, run `peaks skill presence --json` to read the active skill marker. The CLI handles canonical-path resolution (`.peaks/_runtime/active-skill.json` with back-compat fallback to `.peaks/.active-skill.json`); do not read those files directly. When the response includes a valid skill name, display the compact status header: `Peaks-Cli Skill: <skill> | Peaks-Cli Gate: <gate> | Next: <one short action>`. Display the header on every turn while the CLI returns an active skill; omit when the CLI returns no active skill.";
+export declare const NEW_TEMPLATE_TEXT = "Active Peaks-Loop skill presence: at the start of every response, run `peaks skill presence --json` to read the active skill marker. The CLI handles canonical-path resolution (`.peaks/_runtime/active-skill.json` with back-compat fallback to `.peaks/.active-skill.json`); do not read those files directly. When the response includes a valid skill name, display the compact status header: `Peaks-Loop Skill: <skill> | Peaks-Loop Gate: <gate> | Next: <one short action>`. Display the header on every turn while the CLI returns an active skill; omit when the CLI returns no active skill.";
 export type MigrateStandardsInput = {
     project: string;
     apply?: boolean;

package/dist/src/services/standards/migrate-service.js

@@ -10,9 +10,9 @@ import { isAbsolute, resolve } from 'node:path';
  *   2. required the LLM to invoke `peaks skill heartbeat:touch` and
  *      `peaks skill presence:clear` on every turn;
  *   3. ended with an `External reference: https://github.com/affaan-m/...`
- *      line that was peaks-cli-internal, not consumer-facing.
+ *      line that was peaks-loop-internal, not consumer-facing.
  *
- * The replacement text matches the post-slice-025 peaks-cli repo's own
+ * The replacement text matches the post-slice-025 peaks-loop repo's own
  * `CLAUDE.md`: route the LLM through `peaks skill presence --json` and
  * render a compact status header when a valid skill is active. This
  * service is the deterministic in-place rewriter that brings existing
@@ -29,8 +29,8 @@ import { isAbsolute, resolve } from 'node:path';
  *   - File missing → `file: null`, no throw.
  *   - Legacy block not present → `foundOldBlock: false`, no write.
  */
-export const NEW_TEMPLATE_TEXT = 'Active Peaks-Cli skill presence: at the start of every response, run `peaks skill presence --json` to read the active skill marker. The CLI handles canonical-path resolution (`.peaks/_runtime/active-skill.json` with back-compat fallback to `.peaks/.active-skill.json`); do not read those files directly. When the response includes a valid skill name, display the compact status header: `Peaks-Cli Skill: <skill> | Peaks-Cli Gate: <gate> | Next: <one short action>`. Display the header on every turn while the CLI returns an active skill; omit when the CLI returns no active skill.';
-const LEGACY_BLOCK_OPENER_LINE = 'Peaks-Cli 心跳检测 (heartbeat check)';
+export const NEW_TEMPLATE_TEXT = 'Active Peaks-Loop skill presence: at the start of every response, run `peaks skill presence --json` to read the active skill marker. The CLI handles canonical-path resolution (`.peaks/_runtime/active-skill.json` with back-compat fallback to `.peaks/.active-skill.json`); do not read those files directly. When the response includes a valid skill name, display the compact status header: `Peaks-Loop Skill: <skill> | Peaks-Loop Gate: <gate> | Next: <one short action>`. Display the header on every turn while the CLI returns an active skill; omit when the CLI returns no active skill.';
+const LEGACY_BLOCK_OPENER_LINE = 'Peaks-Loop 心跳检测 (heartbeat check)';
 const LEGACY_BLOCK_CLOSER = 'External reference: https://github.com/affaan-m/everything-claude-code';
 const LEGACY_MARKER_FALLBACK = 'Do NOT skip step 3-5. The CLI heartbeat:touch command';
 const FORBIDDEN_LEGACY_STRINGS = [
@@ -152,7 +152,7 @@ export function migrateStandards(input) {
                 applied: false,
                 before: { lines: original.split('\n').length },
                 after: null,
-                nextActions: ['CLAUDE.md has no peaks-cli block; nothing to migrate']
+                nextActions: ['CLAUDE.md has no peaks-loop block; nothing to migrate']
             },
             warnings: []
         };

package/dist/src/services/standards/project-standards-service.js

@@ -159,7 +159,7 @@ function renderClaudeMd(language, ctx) {
         '- Read `.claude/rules/common/security.md` before touching filesystem, user input, external calls, auth, or secrets.',
         `- Read .claude/rules/${language}/coding-style.md for language-specific standards when applicable.`,
         '',
-        'Active Peaks-Cli skill presence: at the start of every response, run `peaks skill presence --json` to read the active skill marker. The CLI handles canonical-path resolution (`.peaks/_runtime/active-skill.json` with back-compat fallback to `.peaks/.active-skill.json`); do not read those files directly. When the response includes a valid skill name, display the compact status header: `Peaks-Cli Skill: <skill> | Peaks-Cli Gate: <gate> | Next: <one short action>`. Display the header on every turn while the CLI returns an active skill; omit when the CLI returns no active skill.'
+        'Active Peaks-Loop skill presence: at the start of every response, run `peaks skill presence --json` to read the active skill marker. The CLI handles canonical-path resolution (`.peaks/_runtime/active-skill.json` with back-compat fallback to `.peaks/.active-skill.json`); do not read those files directly. When the response includes a valid skill name, display the compact status header: `Peaks-Loop Skill: <skill> | Peaks-Loop Gate: <gate> | Next: <one short action>`. Display the header on every turn while the CLI returns an active skill; omit when the CLI returns no active skill.'
     ].join('\n');
     const stack = renderProjectStackSection(ctx);
     return stack === '' ? head : `${head}\n${stack}`;

package/dist/src/services/upgrade/gitignore-migrate-service.d.ts

@@ -1,13 +1,13 @@
 /**
  * The 2.0 canonical ignore block. Mirrors the same paths
- * peaks-cli's own .gitignore uses; kept in lockstep manually
- * (the peaks-cli root .gitignore is the source of truth).
+ * peaks-loop's own .gitignore uses; kept in lockstep manually
+ * (the peaks-loop root .gitignore is the source of truth).
  *
  * Sentinel: every emitted line carries the marker comment so
  * the migration can detect "already-migrated" and stay
  * idempotent.
  */
-export declare const PEAKS_2_0_BLOCK_SENTINEL = "# peaks-cli 2.0 canonical ignore block \u2014 managed by `peaks upgrade --to 2.0`";
+export declare const PEAKS_2_0_BLOCK_SENTINEL = "# peaks-loop 2.0 canonical ignore block \u2014 managed by `peaks upgrade --to 2.0`";
 export declare const CANONICAL_2_0_PEAKS_BLOCK: string;
 /**
  * Returns true when `line` is a wholesale ignore of the entire

package/dist/src/services/upgrade/gitignore-migrate-service.js

@@ -30,7 +30,7 @@
  *
  * Idempotent: re-running on a migrated .gitignore is a no-op.
  *
- * Spec reference: docs/superpowers/specs/2026-06-11-peaks-cli-l1-l2-l3-redesign.md §8.4
+ * Spec reference: docs/superpowers/specs/2026-06-11-peaks-loop-l1-l2-l3-redesign.md §8.4
  * (per-project state in .peaks/preferences.json, durable
  * memories in .peaks/memory/*.md).
  */
@@ -38,14 +38,14 @@ import { existsSync, readFileSync, writeFileSync } from 'node:fs';
 import { join } from 'node:path';
 /**
  * The 2.0 canonical ignore block. Mirrors the same paths
- * peaks-cli's own .gitignore uses; kept in lockstep manually
- * (the peaks-cli root .gitignore is the source of truth).
+ * peaks-loop's own .gitignore uses; kept in lockstep manually
+ * (the peaks-loop root .gitignore is the source of truth).
  *
  * Sentinel: every emitted line carries the marker comment so
  * the migration can detect "already-migrated" and stay
  * idempotent.
  */
-export const PEAKS_2_0_BLOCK_SENTINEL = '# peaks-cli 2.0 canonical ignore block — managed by `peaks upgrade --to 2.0`';
+export const PEAKS_2_0_BLOCK_SENTINEL = '# peaks-loop 2.0 canonical ignore block — managed by `peaks upgrade --to 2.0`';
 export const CANONICAL_2_0_PEAKS_BLOCK = [
     PEAKS_2_0_BLOCK_SENTINEL,
     '.peaks/_runtime/',

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

@@ -2,7 +2,7 @@ export interface UpgradeInput {
     readonly projectRoot: string;
     /**
      * When true, the umbrella is being invoked from the
-     * `npm i -g peaks-cli` postinstall. Suppresses the
+     * `npm i -g peaks-loop` postinstall. Suppresses the
      * interactive prompts and accepts soft-fail on any
      * sub-step.
      */