peaks-loop 4.0.28 → 4.0.30

package/dist/services/skills/hooks-codegate-superpowers.js

@@ -0,0 +1,204 @@
+/**
+ * Code-gate hook entries + superpowers-deny surface for the Peaks-managed
+ * hooks. Extracted from `hooks-settings-service.ts` to keep that file
+ * under the 800 LOC cap (mechanical verbatim move). Also carries the
+ * per-IDE hook-spec table (`resolveHookSpec` / `HOOK_COMMAND_BY_IDE`)
+ * and `HOOK_ENFORCE_SENTINEL`, which the entry/sentinel resolvers depend
+ * on, so this module is self-contained apart from the `PeaksHookEntry`
+ * type contract re-exported by the caller.
+ */
+import { getAdapter } from '../ide/ide-registry.js';
+import { HOOK_OUTER_CACHE_COMMAND, HOOK_OUTER_CACHE_EVENT, HOOK_OUTER_CACHE_SENTINEL, HOOK_WORKSPACE_INIT_COMMAND, HOOK_WORKSPACE_INIT_EVENT, HOOK_WORKSPACE_INIT_SENTINEL } from './session-start-hook-constants.js';
+/** Sentinel substring identifying a Claude-Code gate-enforce hook entry. */
+export const HOOK_ENFORCE_SENTINEL = 'peaks gate enforce';
+/**
+ * Per-IDE hook command + sentinel. The default (Claude Code) uses the
+ * legacy `peaks gate enforce` surface; Trae / Cursor / Codex (Cursor-style
+ * siblings with `before*` / `pre_*` hook events) use `peaks hook handle`,
+ * the new dispatcher. New adapters register by adding a single line here.
+ *
+ * Slice #12 + #13 (2.4.0) honor the framework's "fill the table" promise
+ * — adding a new IDE does NOT require editing this function's control
+ * flow, only adding a line to this table.
+ */
+const HOOK_COMMAND_BY_IDE = {
+    'claude-code': { command: 'peaks gate enforce', sentinel: 'peaks gate enforce' },
+    'trae': { command: 'peaks hook handle', sentinel: 'peaks hook handle' },
+    'cursor': { command: 'peaks hook handle', sentinel: 'peaks hook handle' },
+    'codex': { command: 'peaks hook handle', sentinel: 'peaks hook handle' },
+    'hermes': { command: 'peaks gate enforce', sentinel: 'peaks gate enforce' },
+    'openclaw': { command: 'peaks gate enforce', sentinel: 'peaks gate enforce' },
+    // qoder / tongyi-lingma are reserved IdeIds (slice #1) but not yet
+    // registered. When a slice adds them, add a HOOK_COMMAND_BY_IDE entry
+    // here — the function below fail-closes on missing entries.
+};
+export function resolveHookSpec(ide) {
+    // getAdapter throws on unregistered IDEs — the registry is the source of truth.
+    const adapter = getAdapter(ide);
+    const spec = HOOK_COMMAND_BY_IDE[ide];
+    if (!spec) {
+        // Defensive fallback: if an adapter is added to the registry without a
+        // HOOK_COMMAND_BY_IDE entry, fail-closed with a clear error instead of
+        // silently writing a Claude-shaped entry to a non-Claude settings.json.
+        throw new Error(`peaks hooks install: unsupported IDE '${ide}' (no HOOK_COMMAND_BY_IDE entry; add one to hooks-settings-service.ts)`);
+    }
+    return {
+        hookEnforceCommand: `${spec.command} --project "\${${adapter.envVar}}"`,
+        hookEnforceSentinel: spec.sentinel,
+        hookEnforceMatcher: adapter.toolMatcher,
+        hookEnforceEvent: adapter.hookEvent
+    };
+}
+/**
+ * Slice 2026-08-06-codegate-vendor-neutral — code-gate hook entry.
+ * Vendor-neutral command (`peaks code-gate --json`); the CLI adapter
+ * lives in `src/cli/commands/code-gate-command.ts` and the decision
+ * logic lives in `src/services/hooks/pre-tool-code-gate.ts`. The
+ * shell-script sibling (`src/services/hooks/pre-tool-code-gate.sh`)
+ * encodes the same logic for non-Node harnesses.
+ */
+export const HOOK_CODE_GATE_SENTINEL = 'peaks code-gate';
+export const HOOK_CODE_GATE_MATCHER = 'Edit|Write|MultiEdit';
+export const HOOK_CODE_GATE_EVENT = 'PreToolUse';
+export const HOOK_CODE_GATE_COMMAND = `peaks code-gate --json`;
+export function resolveHookEntries(ide, _skipProgress = false) {
+    const spec = resolveHookSpec(ide);
+    const entries = [
+        { sentinel: spec.hookEnforceSentinel, matcher: spec.hookEnforceMatcher, command: spec.hookEnforceCommand, event: spec.hookEnforceEvent }
+    ];
+    if (ide === 'claude-code') {
+        entries.push({
+            sentinel: HOOK_OUTER_CACHE_SENTINEL,
+            matcher: '',
+            command: HOOK_OUTER_CACHE_COMMAND,
+            event: HOOK_OUTER_CACHE_EVENT
+        });
+        // Slice rid-statusline-stale-ux AC-2: SessionStart outer-cache
+        // write is followed by `peaks session primer` entry so that
+        // rotation + presence cleanup fire BEFORE the first statusline
+        // render of a fresh session. The new subcommand is idempotent
+        // and short-circuits when the binding already matches — safe to
+        // call on every SessionStart. Order matters conceptually:
+        // outer-cache write must come first (the primer's
+        // ensureSessionWithRotation reads the current outer session id).
+        entries.push({
+            sentinel: HOOK_WORKSPACE_INIT_SENTINEL,
+            matcher: '',
+            command: HOOK_WORKSPACE_INIT_COMMAND,
+            event: HOOK_WORKSPACE_INIT_EVENT
+        });
+        // Slice 2026-08-06-codegate-vendor-neutral: code-gate entry on
+        // Edit|Write|MultiEdit matcher. Vendor-neutral command
+        // (`peaks code-gate --json`); the CLI adapter lives in
+        // `src/cli/commands/code-gate-command.ts` and the underlying
+        // decision logic is in `src/services/hooks/pre-tool-code-gate.ts`.
+        entries.push({
+            sentinel: HOOK_CODE_GATE_SENTINEL,
+            matcher: HOOK_CODE_GATE_MATCHER,
+            command: HOOK_CODE_GATE_COMMAND,
+            event: HOOK_CODE_GATE_EVENT
+        });
+    }
+    return entries;
+}
+/**
+ * Legacy sentinel set used by uninstall + status to find and remove stale
+ * progress-start entries written by pre-#014 installs. The progress-start
+ * sentinel is the literal substring that older installs emitted.
+ */
+const LEGACY_PROGRESS_START_SENTINEL = 'peaks progress start';
+export function resolveLegacySentinels(ide) {
+    if (ide === 'trae') {
+        return ['peaks hook handle', LEGACY_PROGRESS_START_SENTINEL];
+    }
+    // Slice 2026-08-06-session-outer-cache: include the SessionStart outer-cache
+    // sentinel so uninstall strips it alongside the gate-enforce entry.
+    // Slice 2026-08-06-codegate-vendor-neutral: also include the code-gate
+    // sentinel so uninstall strips the Edit|Write|MultiEdit entry alongside
+    // the rest of the peaks-managed entries.
+    const base = [HOOK_ENFORCE_SENTINEL, LEGACY_PROGRESS_START_SENTINEL, HOOK_CODE_GATE_SENTINEL];
+    if (ide === 'claude-code') {
+        // Slice rid-statusline-stale-ux AC-2: include the SessionStart
+        // workspace-init primer sentinel so uninstall strips it alongside
+        // the gate-enforce entry, and so hand-added entries matching this
+        // sentinel are recognized as peaks-managed (not stripped as
+        // non-Peaks).
+        return [...base, HOOK_OUTER_CACHE_SENTINEL, HOOK_WORKSPACE_INIT_SENTINEL];
+    }
+    return base;
+}
+// --- Slice 2026-07-29-worktree-layer3-deny -----------------------------------
+// Layer 3 of the Worktree Governance 3-layer design (see
+// .peaks/memory/2026-07-29-worktree-layer3-deny.md). The gateway is the IDE
+// native `permissions.deny` list — Claude Code refuses to invoke any Skill
+// listed there BEFORE the LLM even sees it. This is the strongest of the three
+// layers because it bypasses the LLM's tool-call decision entirely: the IDE
+// matches the deny entry against the Skill's namespace and returns a
+// permission error, so the LLM observes "skill not available" rather than
+// "skill denied" — true fail-closed.
+//
+// The list is intentionally tiny: only skills that the superpowers chain
+// *forces* downstream from peaks-loop work paths. We do NOT deny every
+// superpowers skill — only the one whose `description` field or SKILL.md body
+// recommends `git worktree add` / native worktree tools as a step. Anything
+// else stays available as a reference (peaks-code's
+// references/external-skill-invocation.md already describes every other
+// superpowers skill as informational).
+//
+// The IDE expects the deny entry in the form `UseSkill(<skill-id>)`. The
+// prefix is fixed; the skill id is the namespace-qualified name. We render
+// the entries at install time and at uninstall time so the sentinel list is
+// the single source of truth.
+/**
+ * The set of Skills whose use is denied at the IDE permissions layer for
+ * every `peaks hooks install` call. Each entry is the namespace-qualified
+ * skill id; the helper `formatSuperpowersDenyEntry` wraps it in the IDE's
+ * `UseSkill(...)` envelope.
+ *
+ * Slice 2026-07-29-worktree-layer3-deny: the list is empty-aware. To deny a
+ * new skill, append its id here and re-run `peaks hooks install`. The list
+ * is also the inverse for uninstall: `removeHookInstall` rebuilds the deny
+ * list by filtering out anything whose wrapped form matches one of these
+ * ids.
+ *
+ * Slice rid-skill-persistence-001 (2026-08-12): four additional skills
+ * denied so the superpowers chain cannot silently override peaks-code.
+ * All four are referenced by `superpowers:using-superpowers` as the
+ * "bug → systematic-debugging / TDD / verification-before-completion /
+ * recursion via using-superpowers" auto-routing pattern — denying the
+ * trigger removes the auto-routing surface while leaving all four
+ * still readable as reference material from
+ * `references/external-skill-invocation.md`.
+ */
+export const SUPERPOWERS_DENIED_SKILLS = [
+    // superpowers:using-git-worktrees is the chain's "ground zero" — its
+    // SKILL.md (lines 47-99) literally instructs the LLM to run
+    // `git worktree add`. Denying this Skill at the IDE layer prevents the
+    // LLM from ever receiving that prompt.
+    'superpowers:using-git-worktrees',
+    // Slice rid-skill-persistence-001: deny the "bug → systematic-debugging"
+    // auto-route. Without this entry the chain can preempt the current bee
+    // any time a bug report surfaces. Reference-only via
+    // references/external-skill-invocation.md §systematic-debugging.
+    'superpowers:systematic-debugging',
+    // Slice rid-skill-persistence-001: deny the TDD trigger that the chain
+    // pairs with bug reports (write-a-failing-test-first). Reference-only
+    // via references/external-skill-invocation.md §test-driven-development.
+    'superpowers:test-driven-development',
+    // Slice rid-skill-persistence-001: deny the verification-before-
+    // completion trigger that the chain uses to override "declare done"
+    // claims from peaks-code. Reference-only via
+    // references/external-skill-invocation.md §verification-before-completion.
+    'superpowers:verification-before-completion',
+    // Slice rid-skill-persistence-001: deny the recursive chain entrypoint
+    // itself. Without this entry the chain auto-spawns another
+    // "using-superpowers" Skill call right after the previous chain step,
+    // creating the recursive override pattern that peaks-loop's L1 guard
+    // cannot see through. Reference-only via
+    // references/external-skill-invocation.md §using-superpowers.
+    'superpowers:using-superpowers'
+];
+export function formatSuperpowersDenyEntry(skillId) {
+    return `UseSkill(${skillId})`;
+}
+export const SUPERPOWERS_DENY_SENTINELS = new Set(SUPERPOWERS_DENIED_SKILLS.map(formatSuperpowersDenyEntry));

package/dist/services/skills/hooks-settings-service.d.ts

@@ -1,5 +1,7 @@
 import type { IdeId } from '../ide/ide-types.js';
 import type { HookScope } from '../ide/shared/safe-path.js';
+import { type PeaksHookEntry } from './hooks-codegate-superpowers.js';
+export { HOOK_ENFORCE_SENTINEL, HOOK_CODE_GATE_SENTINEL, HOOK_CODE_GATE_MATCHER, HOOK_CODE_GATE_EVENT, HOOK_CODE_GATE_COMMAND, SUPERPOWERS_DENIED_SKILLS, type PeaksHookEntry } from './hooks-codegate-superpowers.js';
 /**
  * Install (and remove) the Peaks-managed hooks in an IDE's settings.json.
  *
@@ -64,8 +66,6 @@ export type HookInstallOptions = {
      */
     readonly skipProgress?: boolean;
 };
-/** Sentinel substring identifying a Claude-Code gate-enforce hook entry. */
-export declare const HOOK_ENFORCE_SENTINEL = "peaks gate enforce";
 /** Default (claude-code) hook command — kept as a stable export for tests. */
 export declare const HOOK_ENFORCE_COMMAND = "peaks gate enforce --project \"${CLAUDE_PROJECT_DIR}\" --json";
 export type HookInstallPlan = {
@@ -122,68 +122,6 @@ export declare function readInstalledEntriesFromSettings(settings: Record<string
     matcher: string;
     sentinel: string;
 }>;
-/** A typed descriptor for a single peaks-managed hook entry. */
-export type PeaksHookEntry = {
-    sentinel: string;
-    matcher: string;
-    command: string;
-    event: string;
-};
-/**
- * Compute the per-IDE peaks hook entries to merge into the settings file.
- * Replaces the slice #1 hardcoded `PEAKS_HOOK_ENTRIES` constant; the constant
- * remains exported (computed for claude-code) for backward compat.
- *
- * Slice #013 (`--no-progress` flag): when `skipProgress` is true, the
- * progress-start entry is omitted from the returned list. Install with this
- * flag will (a) NOT emit the progress hook entry, and (b) will idempotently
- * remove any previously-installed progress entry (sentinel-based merge).
- *
- * Slice #014 (refactor — full removal): only the gate-enforce entry is
- * ever emitted. The `skipProgress` parameter is kept for API stability
- * but is a no-op — the returned list is always single-entry. The progress
- * entry's sentinel is included in the legacy sentinel set so uninstall
- * can find + remove any stale progress-start entry that an older
- * `peaks hooks install` may have written before this slice.
- *
- * Slice 2026-08-06-session-outer-cache: a SessionStart outer-cache primer
- * entry is appended for Claude Code only (SessionStart is a Claude-Code-
- * specific event key today).
- */
-/**
- * Slice 2026-08-06-codegate-vendor-neutral — code-gate hook entry.
- * Vendor-neutral command (`peaks code-gate --json`); the CLI adapter
- * lives in `src/cli/commands/code-gate-command.ts` and the decision
- * logic lives in `src/services/hooks/pre-tool-code-gate.ts`. The
- * shell-script sibling (`src/services/hooks/pre-tool-code-gate.sh`)
- * encodes the same logic for non-Node harnesses.
- */
-export declare const HOOK_CODE_GATE_SENTINEL = "peaks code-gate";
-export declare const HOOK_CODE_GATE_MATCHER = "Edit|Write|MultiEdit";
-export declare const HOOK_CODE_GATE_EVENT = "PreToolUse";
-export declare const HOOK_CODE_GATE_COMMAND = "peaks code-gate --json";
-/**
- * The set of Skills whose use is denied at the IDE permissions layer for
- * every `peaks hooks install` call. Each entry is the namespace-qualified
- * skill id; the helper `formatSuperpowersDenyEntry` wraps it in the IDE's
- * `UseSkill(...)` envelope.
- *
- * Slice 2026-07-29-worktree-layer3-deny: the list is empty-aware. To deny a
- * new skill, append its id here and re-run `peaks hooks install`. The list
- * is also the inverse for uninstall: `removeHookInstall` rebuilds the deny
- * list by filtering out anything whose wrapped form matches one of these
- * ids.
- *
- * Slice rid-skill-persistence-001 (2026-08-12): four additional skills
- * denied so the superpowers chain cannot silently override peaks-code.
- * All four are referenced by `superpowers:using-superpowers` as the
- * "bug → systematic-debugging / TDD / verification-before-completion /
- * recursion via using-superpowers" auto-routing pattern — denying the
- * trigger removes the auto-routing surface while leaving all four
- * still readable as reference material from
- * `references/external-skill-invocation.md`.
- */
-export declare const SUPERPOWERS_DENIED_SKILLS: ReadonlyArray<string>;
 /**
  * Merge the peaks-managed Skill denylist into the existing settings object.
  * Preserves every other `permissions.deny` entry the user (or another tool)

package/dist/services/skills/hooks-settings-service.js

@@ -4,53 +4,14 @@ import { resolve } from 'node:path';
 import { assertSafeSettingsFile } from '../ide/shared/safe-path.js';
 import { atomicWriteJson, readJsonObjectFile } from '../ide/shared/atomic-json.js';
 import { getAdapter } from '../ide/ide-registry.js';
-import { HOOK_OUTER_CACHE_COMMAND, HOOK_OUTER_CACHE_EVENT, HOOK_OUTER_CACHE_SENTINEL, HOOK_WORKSPACE_INIT_COMMAND, HOOK_WORKSPACE_INIT_EVENT, HOOK_WORKSPACE_INIT_SENTINEL } from './session-start-hook-constants.js';
+import { resolveHookSpec, resolveHookEntries, resolveLegacySentinels, SUPERPOWERS_DENIED_SKILLS, formatSuperpowersDenyEntry, SUPERPOWERS_DENY_SENTINELS } from './hooks-codegate-superpowers.js';
+export { HOOK_ENFORCE_SENTINEL, HOOK_CODE_GATE_SENTINEL, HOOK_CODE_GATE_MATCHER, HOOK_CODE_GATE_EVENT, HOOK_CODE_GATE_COMMAND, SUPERPOWERS_DENIED_SKILLS } from './hooks-codegate-superpowers.js';
 // --- Module-level defaults (claude-code) -----------------------------------
 // These exports remain for backward compat — tests and downstream callers
 // that only care about Claude Code can keep importing them. The per-IDE
 // values are computed lazily inside each public function call.
-/** Sentinel substring identifying a Claude-Code gate-enforce hook entry. */
-export const HOOK_ENFORCE_SENTINEL = 'peaks gate enforce';
 /** Default (claude-code) hook command — kept as a stable export for tests. */
 export const HOOK_ENFORCE_COMMAND = `peaks gate enforce --project "\${CLAUDE_PROJECT_DIR}" --json`;
-/**
- * Per-IDE hook command + sentinel. The default (Claude Code) uses the
- * legacy `peaks gate enforce` surface; Trae / Cursor / Codex (Cursor-style
- * siblings with `before*` / `pre_*` hook events) use `peaks hook handle`,
- * the new dispatcher. New adapters register by adding a single line here.
- *
- * Slice #12 + #13 (2.4.0) honor the framework's "fill the table" promise
- * — adding a new IDE does NOT require editing this function's control
- * flow, only adding a line to this table.
- */
-const HOOK_COMMAND_BY_IDE = {
-    'claude-code': { command: 'peaks gate enforce', sentinel: 'peaks gate enforce' },
-    'trae': { command: 'peaks hook handle', sentinel: 'peaks hook handle' },
-    'cursor': { command: 'peaks hook handle', sentinel: 'peaks hook handle' },
-    'codex': { command: 'peaks hook handle', sentinel: 'peaks hook handle' },
-    'hermes': { command: 'peaks gate enforce', sentinel: 'peaks gate enforce' },
-    'openclaw': { command: 'peaks gate enforce', sentinel: 'peaks gate enforce' },
-    // qoder / tongyi-lingma are reserved IdeIds (slice #1) but not yet
-    // registered. When a slice adds them, add a HOOK_COMMAND_BY_IDE entry
-    // here — the function below fail-closes on missing entries.
-};
-function resolveHookSpec(ide) {
-    // getAdapter throws on unregistered IDEs — the registry is the source of truth.
-    const adapter = getAdapter(ide);
-    const spec = HOOK_COMMAND_BY_IDE[ide];
-    if (!spec) {
-        // Defensive fallback: if an adapter is added to the registry without a
-        // HOOK_COMMAND_BY_IDE entry, fail-closed with a clear error instead of
-        // silently writing a Claude-shaped entry to a non-Claude settings.json.
-        throw new Error(`peaks hooks install: unsupported IDE '${ide}' (no HOOK_COMMAND_BY_IDE entry; add one to hooks-settings-service.ts)`);
-    }
-    return {
-        hookEnforceCommand: `${spec.command} --project "\${${adapter.envVar}}"`,
-        hookEnforceSentinel: spec.sentinel,
-        hookEnforceMatcher: adapter.toolMatcher,
-        hookEnforceEvent: adapter.hookEvent
-    };
-}
 function resolveIde(options) {
     return options?.ide ?? 'claude-code';
 }
@@ -166,180 +127,6 @@ export function readInstalledEntriesFromSettings(settings, ide) {
     }
     return result;
 }
-/**
- * Compute the per-IDE peaks hook entries to merge into the settings file.
- * Replaces the slice #1 hardcoded `PEAKS_HOOK_ENTRIES` constant; the constant
- * remains exported (computed for claude-code) for backward compat.
- *
- * Slice #013 (`--no-progress` flag): when `skipProgress` is true, the
- * progress-start entry is omitted from the returned list. Install with this
- * flag will (a) NOT emit the progress hook entry, and (b) will idempotently
- * remove any previously-installed progress entry (sentinel-based merge).
- *
- * Slice #014 (refactor — full removal): only the gate-enforce entry is
- * ever emitted. The `skipProgress` parameter is kept for API stability
- * but is a no-op — the returned list is always single-entry. The progress
- * entry's sentinel is included in the legacy sentinel set so uninstall
- * can find + remove any stale progress-start entry that an older
- * `peaks hooks install` may have written before this slice.
- *
- * Slice 2026-08-06-session-outer-cache: a SessionStart outer-cache primer
- * entry is appended for Claude Code only (SessionStart is a Claude-Code-
- * specific event key today).
- */
-/**
- * Slice 2026-08-06-codegate-vendor-neutral — code-gate hook entry.
- * Vendor-neutral command (`peaks code-gate --json`); the CLI adapter
- * lives in `src/cli/commands/code-gate-command.ts` and the decision
- * logic lives in `src/services/hooks/pre-tool-code-gate.ts`. The
- * shell-script sibling (`src/services/hooks/pre-tool-code-gate.sh`)
- * encodes the same logic for non-Node harnesses.
- */
-export const HOOK_CODE_GATE_SENTINEL = 'peaks code-gate';
-export const HOOK_CODE_GATE_MATCHER = 'Edit|Write|MultiEdit';
-export const HOOK_CODE_GATE_EVENT = 'PreToolUse';
-export const HOOK_CODE_GATE_COMMAND = `peaks code-gate --json`;
-function resolveHookEntries(ide, _skipProgress = false) {
-    const spec = resolveHookSpec(ide);
-    const entries = [
-        { sentinel: spec.hookEnforceSentinel, matcher: spec.hookEnforceMatcher, command: spec.hookEnforceCommand, event: spec.hookEnforceEvent }
-    ];
-    if (ide === 'claude-code') {
-        entries.push({
-            sentinel: HOOK_OUTER_CACHE_SENTINEL,
-            matcher: '',
-            command: HOOK_OUTER_CACHE_COMMAND,
-            event: HOOK_OUTER_CACHE_EVENT
-        });
-        // Slice rid-statusline-stale-ux AC-2: SessionStart outer-cache
-        // write is followed by `peaks session primer` entry so that
-        // rotation + presence cleanup fire BEFORE the first statusline
-        // render of a fresh session. The new subcommand is idempotent
-        // and short-circuits when the binding already matches — safe to
-        // call on every SessionStart. Order matters conceptually:
-        // outer-cache write must come first (the primer's
-        // ensureSessionWithRotation reads the current outer session id).
-        entries.push({
-            sentinel: HOOK_WORKSPACE_INIT_SENTINEL,
-            matcher: '',
-            command: HOOK_WORKSPACE_INIT_COMMAND,
-            event: HOOK_WORKSPACE_INIT_EVENT
-        });
-        // Slice 2026-08-06-codegate-vendor-neutral: code-gate entry on
-        // Edit|Write|MultiEdit matcher. Vendor-neutral command
-        // (`peaks code-gate --json`); the CLI adapter lives in
-        // `src/cli/commands/code-gate-command.ts` and the underlying
-        // decision logic is in `src/services/hooks/pre-tool-code-gate.ts`.
-        entries.push({
-            sentinel: HOOK_CODE_GATE_SENTINEL,
-            matcher: HOOK_CODE_GATE_MATCHER,
-            command: HOOK_CODE_GATE_COMMAND,
-            event: HOOK_CODE_GATE_EVENT
-        });
-    }
-    return entries;
-}
-/**
- * Legacy sentinel set used by uninstall + status to find and remove stale
- * progress-start entries written by pre-#014 installs. The progress-start
- * sentinel is the literal substring that older installs emitted.
- */
-const LEGACY_PROGRESS_START_SENTINEL = 'peaks progress start';
-function resolveLegacySentinels(ide) {
-    if (ide === 'trae') {
-        return ['peaks hook handle', LEGACY_PROGRESS_START_SENTINEL];
-    }
-    // Slice 2026-08-06-session-outer-cache: include the SessionStart outer-cache
-    // sentinel so uninstall strips it alongside the gate-enforce entry.
-    // Slice 2026-08-06-codegate-vendor-neutral: also include the code-gate
-    // sentinel so uninstall strips the Edit|Write|MultiEdit entry alongside
-    // the rest of the peaks-managed entries.
-    const base = [HOOK_ENFORCE_SENTINEL, LEGACY_PROGRESS_START_SENTINEL, HOOK_CODE_GATE_SENTINEL];
-    if (ide === 'claude-code') {
-        // Slice rid-statusline-stale-ux AC-2: include the SessionStart
-        // workspace-init primer sentinel so uninstall strips it alongside
-        // the gate-enforce entry, and so hand-added entries matching this
-        // sentinel are recognized as peaks-managed (not stripped as
-        // non-Peaks).
-        return [...base, HOOK_OUTER_CACHE_SENTINEL, HOOK_WORKSPACE_INIT_SENTINEL];
-    }
-    return base;
-}
-// --- Slice 2026-07-29-worktree-layer3-deny -----------------------------------
-// Layer 3 of the Worktree Governance 3-layer design (see
-// .peaks/memory/2026-07-29-worktree-layer3-deny.md). The gateway is the IDE
-// native `permissions.deny` list — Claude Code refuses to invoke any Skill
-// listed there BEFORE the LLM even sees it. This is the strongest of the three
-// layers because it bypasses the LLM's tool-call decision entirely: the IDE
-// matches the deny entry against the Skill's namespace and returns a
-// permission error, so the LLM observes "skill not available" rather than
-// "skill denied" — true fail-closed.
-//
-// The list is intentionally tiny: only skills that the superpowers chain
-// *forces* downstream from peaks-loop work paths. We do NOT deny every
-// superpowers skill — only the one whose `description` field or SKILL.md body
-// recommends `git worktree add` / native worktree tools as a step. Anything
-// else stays available as a reference (peaks-code's
-// references/external-skill-invocation.md already describes every other
-// superpowers skill as informational).
-//
-// The IDE expects the deny entry in the form `UseSkill(<skill-id>)`. The
-// prefix is fixed; the skill id is the namespace-qualified name. We render
-// the entries at install time and at uninstall time so the sentinel list is
-// the single source of truth.
-/**
- * The set of Skills whose use is denied at the IDE permissions layer for
- * every `peaks hooks install` call. Each entry is the namespace-qualified
- * skill id; the helper `formatSuperpowersDenyEntry` wraps it in the IDE's
- * `UseSkill(...)` envelope.
- *
- * Slice 2026-07-29-worktree-layer3-deny: the list is empty-aware. To deny a
- * new skill, append its id here and re-run `peaks hooks install`. The list
- * is also the inverse for uninstall: `removeHookInstall` rebuilds the deny
- * list by filtering out anything whose wrapped form matches one of these
- * ids.
- *
- * Slice rid-skill-persistence-001 (2026-08-12): four additional skills
- * denied so the superpowers chain cannot silently override peaks-code.
- * All four are referenced by `superpowers:using-superpowers` as the
- * "bug → systematic-debugging / TDD / verification-before-completion /
- * recursion via using-superpowers" auto-routing pattern — denying the
- * trigger removes the auto-routing surface while leaving all four
- * still readable as reference material from
- * `references/external-skill-invocation.md`.
- */
-export const SUPERPOWERS_DENIED_SKILLS = [
-    // superpowers:using-git-worktrees is the chain's "ground zero" — its
-    // SKILL.md (lines 47-99) literally instructs the LLM to run
-    // `git worktree add`. Denying this Skill at the IDE layer prevents the
-    // LLM from ever receiving that prompt.
-    'superpowers:using-git-worktrees',
-    // Slice rid-skill-persistence-001: deny the "bug → systematic-debugging"
-    // auto-route. Without this entry the chain can preempt the current bee
-    // any time a bug report surfaces. Reference-only via
-    // references/external-skill-invocation.md §systematic-debugging.
-    'superpowers:systematic-debugging',
-    // Slice rid-skill-persistence-001: deny the TDD trigger that the chain
-    // pairs with bug reports (write-a-failing-test-first). Reference-only
-    // via references/external-skill-invocation.md §test-driven-development.
-    'superpowers:test-driven-development',
-    // Slice rid-skill-persistence-001: deny the verification-before-
-    // completion trigger that the chain uses to override "declare done"
-    // claims from peaks-code. Reference-only via
-    // references/external-skill-invocation.md §verification-before-completion.
-    'superpowers:verification-before-completion',
-    // Slice rid-skill-persistence-001: deny the recursive chain entrypoint
-    // itself. Without this entry the chain auto-spawns another
-    // "using-superpowers" Skill call right after the previous chain step,
-    // creating the recursive override pattern that peaks-loop's L1 guard
-    // cannot see through. Reference-only via
-    // references/external-skill-invocation.md §using-superpowers.
-    'superpowers:using-superpowers'
-];
-function formatSuperpowersDenyEntry(skillId) {
-    return `UseSkill(${skillId})`;
-}
-const SUPERPOWERS_DENY_SENTINELS = new Set(SUPERPOWERS_DENIED_SKILLS.map(formatSuperpowersDenyEntry));
 /**
  * Merge the peaks-managed Skill denylist into the existing settings object.
  * Preserves every other `permissions.deny` entry the user (or another tool)

package/dist/services/skills/skill-statusline-renderer.d.ts

@@ -2,6 +2,8 @@ import type { StatusLineModel, TwentyFourHourOverlay } from './skill-statusline-
 import { computeRootSuffix as computeRootSuffixImpl } from './skill-statusline-sid-suffix.js';
 export { formatShortSid } from './skill-statusline-sid-suffix.js';
 export declare const computeRootSuffix: typeof computeRootSuffixImpl;
+import { type StatusLineCapability, type StatusPalette } from './statusline-palette.js';
+export type { StatusLineCapability } from './statusline-palette.js';
 /**
  * Pure formatting layer for the Peaks statusLine. Takes the read-only status
  * model and produces the single line Claude Code paints at the bottom of the
@@ -13,43 +15,9 @@ export declare const computeRootSuffix: typeof computeRootSuffixImpl;
  * concrete string happens in one place. Adding a fourth capability (e.g. for
  * a future IDE) is a one-table change.
  */
-export type StatusLineCapability = 'ansi-unicode' | 'unicode' | 'ascii';
 export interface StatusLineRenderOptions {
     readonly capability: StatusLineCapability;
 }
-/**
- * Glyph palette per capability. Status glyphs (active / idle / warning),
- * separators (· / › / ▸ / ASCII variants), and the diagnostic marker
- * (`presence unreadable`). Unicode glyphs use widely-supported characters;
- * ASCII keeps byte-identical shape across encodings.
- *
- * Compact glyphs are the unicode quadrant marks ◐◑◒◓, the check ✓, and the
- * ballot ✕. ASCII uses bracket/plus/star/x. Bar characters are █/░ in
- * unicode and #/- in ASCII. Ratios are joined with `·` (` . ` for ASCII)
- * and the before→after arrow is `→` (-> for ASCII).
- */
-interface StatusPalette {
-    readonly active: string;
-    readonly idleStale: string;
-    readonly idle: string;
-    readonly warning: string;
-    readonly inlineSeparator: string;
-    readonly trailSeparator: string;
-    readonly idleLabel: string;
-    readonly invalidMessage: string;
-    readonly compact: CompactPalette;
-    readonly barFilled: string;
-    readonly barEmpty: string;
-    readonly ratioArrow: string;
-}
-interface CompactPalette {
-    readonly queued: string;
-    readonly preparing: string;
-    readonly compacting: string;
-    readonly verifying: string;
-    readonly completed: string;
-    readonly failed: string;
-}
 export declare function formatHumanAge(ageMs: number | null): string;
 /**
  * Slice rid-statusline-24h-overlay (2026-08-10): format the 24h-mode