@hegemonart/get-design-done 1.42.0 → 1.44.0

package/dist/claude-code/.claude/skills/analyze-dependencies/SKILL.md

@@ -6,7 +6,7 @@ tools: Bash, Read, Glob, Grep
 
 # /gdd:analyze-dependencies
 
-**Role:** Surface dependency relationships, token usage spread, component graphs, and decision traceability using `.design/intel/`. All queries are O(1) reads against pre-built JSON slices — no file greps. See `./reference/heuristics.md` for the underlying dependency-analysis heuristics (fan-out thresholds, orphan-token criteria, cycle-detection bias).
+**Role:** Surface dependency relationships, token usage spread, component graphs, and decision traceability using `.design/intel/`. All queries are O(1) reads against pre-built JSON slices - no file greps. See `./reference/heuristics.md` for the underlying dependency-analysis heuristics (fan-out thresholds, orphan-token criteria, cycle-detection bias).
 
 ## Pre-flight
 
@@ -26,13 +26,13 @@ Then re-run /gdd:analyze-dependencies.
 
 ## Usage modes
 
-- `/gdd:analyze-dependencies` — run all four analyses and print a combined report
-- `/gdd:analyze-dependencies tokens` — token fan-out only
-- `/gdd:analyze-dependencies components` — component call-graph only
-- `/gdd:analyze-dependencies decisions` — decision traceability only
-- `/gdd:analyze-dependencies circular` — circular dependency detection only
+- `/gdd:analyze-dependencies` - run all four analyses and print a combined report
+- `/gdd:analyze-dependencies tokens` - token fan-out only
+- `/gdd:analyze-dependencies components` - component call-graph only
+- `/gdd:analyze-dependencies decisions` - decision traceability only
+- `/gdd:analyze-dependencies circular` - circular dependency detection only
 
-## Analysis 1 — Token fan-out
+## Analysis 1 - Token fan-out
 
 Surfaces tokens referenced in many files + orphans (referenced exactly once).
 
@@ -42,7 +42,7 @@ Surfaces tokens referenced in many files + orphans (referenced exactly once).
 
 Header: `━━━ Token fan-out ━━━` … `(top 20 shown)` … `Orphaned tokens (referenced in exactly 1 file):` … footer rule.
 
-## Analysis 2 — Component call-graph
+## Analysis 2 - Component call-graph
 
 Surfaces widely-referenced components and the files referencing each.
 
@@ -52,7 +52,7 @@ Surfaces widely-referenced components and the files referencing each.
 
 Header: `━━━ Component call-graph ━━━` … footer rule.
 
-## Analysis 3 — Decision traceability
+## Analysis 3 - Decision traceability
 
 Maps decisions to skill/agent files that cite them.
 
@@ -64,7 +64,7 @@ Maps decisions to skill/agent files that cite them.
 
 Empty-state: `No decisions indexed. Run node scripts/build-intel.cjs after creating .design/DESIGN-CONTEXT.md.`
 
-## Analysis 4 — Circular dependency detection
+## Analysis 4 - Circular dependency detection
 
 Detects cycles in the `@`-reference graph (File A → File B → File A). DFS with path-tracking detects back-edges; algorithm + adjacency-map shape detailed in `./reference/heuristics.md` §"Dependency-cycle detection".
 

package/dist/claude-code/.claude/skills/apply-reflections/SKILL.md

@@ -45,14 +45,14 @@ Change: ...
 If `--dry-run`: print `[dry-run — would prompt here]` and continue to next proposal without prompting.
 
 Based on user choice:
-- **a** — apply (see Apply Logic below)
-- **s** — mark proposal as `**Reviewed: skipped**` in the reflections file; continue
-- **e** — show the Change text, ask user to provide edited version, then apply the edited version
-- **q** — stop processing; print "Stopped at proposal N. Resume with `/gdd:apply-reflections --cycle <slug>`."
+- **a** - apply (see Apply Logic below)
+- **s** - mark proposal as `**Reviewed: skipped**` in the reflections file; continue
+- **e** - show the Change text, ask user to provide edited version, then apply the edited version
+- **q** - stop processing; print "Stopped at proposal N. Resume with `/gdd:apply-reflections --cycle <slug>`."
 
 ### 4. Apply Logic by Proposal Type
 
-After the user chooses `a` (apply) or `e` (edit-then-apply), branch on the proposal's bracketed type tag and follow the per-type apply procedure in `./apply-reflections-procedure.md` — one numbered procedure each for `[FRONTMATTER]`, `[REFERENCE]`, `[BUDGET]`, `[QUESTION]`, `[GLOBAL-SKILL]`. All branches end with `**Applied**: <date>` appended to the proposal block in the reflections file.
+After the user chooses `a` (apply) or `e` (edit-then-apply), branch on the proposal's bracketed type tag and follow the per-type apply procedure in `./apply-reflections-procedure.md` - one numbered procedure each for `[FRONTMATTER]`, `[REFERENCE]`, `[BUDGET]`, `[QUESTION]`, `[GLOBAL-SKILL]`. All branches end with `**Applied**: <date>` appended to the proposal block in the reflections file.
 
 ### 5. Summary
 
@@ -73,12 +73,12 @@ Incubator drafts authored by `scripts/lib/incubator-author.cjs` (Phase 29-04) ap
 1. `discoverIncubatorDrafts()` → list pending drafts.
 2. `renderProposal(draft)` → show full body + diff + origin signals.
 3. User chooses **accept** | **reject** | **defer** | **edit**.
-4. **accept** — scope-guard runs FIRST (`validateScope` from `scripts/validate-incubator-scope.cjs`); `applyAccept` then promotes draft → `agents/<slug>.md` or `skills/<slug>/SKILL.md` and appends a registry entry. Single-step per D-04.
-5. **reject** — `applyReject` removes the incubator subdir.
-6. **defer** — no-op; draft re-surfaces next run.
-7. **edit** — `applyEdit` opens `$EDITOR`; re-prompt user on close.
+4. **accept** - scope-guard runs FIRST (`validateScope` from `scripts/validate-incubator-scope.cjs`); `applyAccept` then promotes draft → `agents/<slug>.md` or `skills/<slug>/SKILL.md` and appends a registry entry. Single-step per D-04.
+5. **reject** - `applyReject` removes the incubator subdir.
+6. **defer** - no-op; draft re-surfaces next run.
+7. **edit** - `applyEdit` opens `$EDITOR`; re-prompt user on close.
 
-**Stage-1 gate.** At session start, call `checkStage1Gate()`. If `thresholdMet && !optInRecorded`, display the opt-in prompt once. NEVER auto-flip per D-01 — recording opt-in requires explicit user confirmation via `recordOptIn()`. Full procedure: `./apply-reflections-procedure.md` §[INCUBATOR].
+**Stage-1 gate.** At session start, call `checkStage1Gate()`. If `thresholdMet && !optInRecorded`, display the opt-in prompt once. NEVER auto-flip per D-01 - recording opt-in requires explicit user confirmation via `recordOptIn()`. Full procedure: `./apply-reflections-procedure.md` §[INCUBATOR].
 
 ## [KFM-CANDIDATE]
 
@@ -87,6 +87,6 @@ KFM-catalogue proposals authored by `scripts/lib/reflector-kfm-proposer.cjs` (Ph
 ## Do Not
 
 - Do not apply any proposal without the user explicitly choosing `a` or `e`.
-- Do not modify source code files (`.ts`, `.tsx`, `.css`, `.js`) — only agent files, reference files, budget.json, discussant questions, global skills, and incubator drafts.
-- Do not re-run the reflector — this skill only applies existing proposals.
-- Do not bypass the scope guard or auto-flip Stage-1 — both are non-negotiable per D-05 / D-01.
+- Do not modify source code files (`.ts`, `.tsx`, `.css`, `.js`) - only agent files, reference files, budget.json, discussant questions, global skills, and incubator drafts.
+- Do not re-run the reflector - this skill only applies existing proposals.
+- Do not bypass the scope guard or auto-flip Stage-1 - both are non-negotiable per D-05 / D-01.

package/dist/claude-code/.claude/skills/apply-reflections/apply-reflections-procedure.md

@@ -7,7 +7,7 @@ tags: [apply-reflections, proposal, frontmatter, reference, budget, question, gl
 last_updated: 2026-05-21
 ---
 
-# Apply-Reflections — Per-Type Procedure
+# Apply-Reflections - Per-Type Procedure
 
 Extracted from `skills/apply-reflections/SKILL.md` per Phase 28.5 D-10 (extract-then-link,
 never delete content). The orchestrator loop in `apply-reflections` (resolve file → parse →
@@ -64,7 +64,7 @@ the proposal's bracketed type tag.
    <content>
    ```
 
-5. Print: "Global skill written to ~/.claude/gdd/global-skills/<name>.md — auto-loads in all future gdd sessions"
+5. Print: "Global skill written to ~/.claude/gdd/global-skills/<name>.md - auto-loads in all future gdd sessions"
 6. Append `**Applied**: <date>` to proposal in reflections file
 
 ### [INCUBATOR]
@@ -82,33 +82,33 @@ Use `scripts/lib/apply-reflections/incubator-proposals.cjs` for all actions.
 
 **Per-action behavior:**
 
-1. **accept** — call `applyAccept(draft, { registryPath, repoRoot })`.
+1. **accept** - call `applyAccept(draft, { registryPath, repoRoot })`.
    - The helper calls `validateScope(draft.target_path)` from `scripts/validate-incubator-scope.cjs` **before** any write. Out-of-scope paths throw and the registry stays untouched. This is the non-bypassable scope guard (D-05).
-   - On success: target artifact written, `reference/registry.json` appended with `{ slug, path, added, origin: 'incubator' }`, incubator subdir removed last (T-29.05-04 — partial-failure leaves draft retryable).
-   - Print: "Accepted — promoted to <target_path>; registered."
+   - On success: target artifact written, `reference/registry.json` appended with `{ slug, path, added, origin: 'incubator' }`, incubator subdir removed last (T-29.05-04 - partial-failure leaves draft retryable).
+   - Print: "Accepted - promoted to <target_path>; registered."
    - Append `**Applied**: <date>` to the proposal block.
 
-2. **reject** — call `applyReject(draft)`. Only the incubator subdir is removed; registry is untouched. Append `**Reviewed: rejected**` to the reflections file.
+2. **reject** - call `applyReject(draft)`. Only the incubator subdir is removed; registry is untouched. Append `**Reviewed: rejected**` to the reflections file.
 
-3. **defer** — no-op. Print "Deferred — draft re-surfaces next run." Append `**Reviewed: deferred**`.
+3. **defer** - no-op. Print "Deferred - draft re-surfaces next run." Append `**Reviewed: deferred**`.
 
-4. **edit** — call `applyEdit(draft)` (uses `$EDITOR` or the `editorCmd` array option). On clean exit, the helper reloads the draft and the caller re-runs `renderProposal` + the prompt. On non-zero exit, the original draft is preserved unchanged.
+4. **edit** - call `applyEdit(draft)` (uses `$EDITOR` or the `editorCmd` array option). On clean exit, the helper reloads the draft and the caller re-runs `renderProposal` + the prompt. On non-zero exit, the original draft is preserved unchanged.
 
-**Stage-1 gate (D-01 — no auto-flip):**
+**Stage-1 gate (D-01 - no auto-flip):**
 
-1. At the start of the cycle, call `checkStage1Gate({ gateSpecPath, statePath, registryPath })`. The call is **read-only** — never mutates state. The returned `{ thresholdMet, summary, optInRecorded }` is informational.
+1. At the start of the cycle, call `checkStage1Gate({ gateSpecPath, statePath, registryPath })`. The call is **read-only** - never mutates state. The returned `{ thresholdMet, summary, optInRecorded }` is informational.
 2. If `thresholdMet && !optInRecorded`, surface a one-time prompt:
    ```
    Stage-1 capability-gap authoring threshold met: <summary>
    Enable incubator-draft promotion?  (y/N)
    ```
-3. **Only on explicit `y`**, call `recordOptIn({ statePath, confirmedBy })`. The function is idempotent — a second call detects the existing record and returns `{ alreadyRecorded: true }`. Never call it on any other input.
+3. **Only on explicit `y`**, call `recordOptIn({ statePath, confirmedBy })`. The function is idempotent - a second call detects the existing record and returns `{ alreadyRecorded: true }`. Never call it on any other input.
 
 **Why this is gated.** The `[INCUBATOR]` proposal class can write executable surface (agents + skills) into the plugin runtime. Both Phase 29 D-01 (no auto-flip) and D-05 (scope guard) exist because that surface has integration-test and security implications that exceed reflector autonomy. `validateScope` keeps the file landing zone confined to `agents/<slug>.md` or `skills/<slug>/SKILL.md`. The Stage-1 gate keeps the *whether* of opting in to incubator authoring under explicit user control even after the data threshold says we have enough signal.
 
 **Bandit-fairness gate on `accept` (Phase 29 Plan 06 / CONTEXT D-04).**
 
-When the `accept` action promotes an incubator draft, the bandit-router arms for the freshly-promoted agent/skill MUST be bootstrapped with `prior_class: 'promoted_incubator'`. This invokes a conservative `Beta(2, 8)` bootstrap prior (posterior mean 0.2) instead of the optimistic Phase 23.5 informed prior — the bandit-fairness gate IS the staging mechanism (D-04: no separate two-step ratify split). The conservative prior suppresses preferential selection until ~8-10 successful pulls accumulate.
+When the `accept` action promotes an incubator draft, the bandit-router arms for the freshly-promoted agent/skill MUST be bootstrapped with `prior_class: 'promoted_incubator'`. This invokes a conservative `Beta(2, 8)` bootstrap prior (posterior mean 0.2) instead of the optimistic Phase 23.5 informed prior - the bandit-fairness gate IS the staging mechanism (D-04: no separate two-step ratify split). The conservative prior suppresses preferential selection until ~8-10 successful pulls accumulate.
 
 Call shape (whether eagerly invoked on promotion or via first-pull lazy bootstrap):
 
@@ -133,7 +133,7 @@ bandit.updateWithDelegate({
 });
 ```
 
-Omitting `prior_class` reverts to Phase 23.5 informed-prior bootstrap (non-breaking). The reward math is unchanged — `prior_class` only affects bootstrap.
+Omitting `prior_class` reverts to Phase 23.5 informed-prior bootstrap (non-breaking). The reward math is unchanged - `prior_class` only affects bootstrap.
 
 ### [KFM-CANDIDATE]
 
@@ -141,7 +141,7 @@ Known-failure-mode catalogue proposals come from `scripts/lib/reflector-kfm-prop
 
 Two upstream signals share this draft surface (D-06):
 - `capability_gap` clusters of size ≥3 with no existing-entry match (Phase 29-03 aggregator + `failure-mode-matcher.match()`).
-- `kfm-candidate` events from the Phase 30.5-03 Task 2 authority-watcher whitelist (D-06 — single events bypass the ≥3 gate).
+- `kfm-candidate` events from the Phase 30.5-03 Task 2 authority-watcher whitelist (D-06 - single events bypass the ≥3 gate).
 
 Use `scripts/lib/reflector-kfm-proposer.cjs` for all actions:
 
@@ -153,18 +153,18 @@ Use `scripts/lib/reflector-kfm-proposer.cjs` for all actions:
 
 **Per-action behavior:**
 
-1. **accept** — call `applyAccept(draftPath, { repoRoot })`.
+1. **accept** - call `applyAccept(draftPath, { repoRoot })`.
    - The helper re-stamps the proposed `id` with the next available `KFM-NNN` from the catalogue (avoids collisions when multiple drafts promote in the same run).
    - Appends a `### KFM-NNN — <symptom heading>` section into `reference/known-failure-modes.md` with the yaml block intact.
    - Appends a `reference/registry.json` entry: `{ name: 'known-failure-modes/kfm-NNN', path: 'reference/known-failure-modes.md', type: 'failure-mode', phase: 30.5, origin: 'incubator-kfm', added: '<ISO date>' }`.
    - Removes the incubator subdir LAST (partial-failure leaves the draft retryable).
-   - Print: "Accepted — promoted to KFM-NNN in reference/known-failure-modes.md."
+   - Print: "Accepted - promoted to KFM-NNN in reference/known-failure-modes.md."
    - Append `**Applied**: <date>` to the proposal entry (when surfaced from a reflections file).
 
-2. **reject** — call `applyReject(draftPath)`. Only the incubator subdir is removed; catalogue + registry untouched. Print: "Rejected — draft removed."
+2. **reject** - call `applyReject(draftPath)`. Only the incubator subdir is removed; catalogue + registry untouched. Print: "Rejected - draft removed."
 
-3. **defer** — call `applyDefer(draftPath, { deferredUntil })` where `deferredUntil` is an ISO date (default: today + 30d). The helper stamps `deferred_until: <ISO>` into the draft body. Print: "Deferred — draft re-surfaces next run."
+3. **defer** - call `applyDefer(draftPath, { deferredUntil })` where `deferredUntil` is an ISO date (default: today + 30d). The helper stamps `deferred_until: <ISO>` into the draft body. Print: "Deferred - draft re-surfaces next run."
 
-4. **edit** — call `applyEdit(draftPath)` which returns the draft path. The caller opens `$EDITOR` on the path; on clean exit, re-discover the draft and re-prompt. Typical edits: replace `pattern: 'TODO: ...'` with a conservative regex, replace `fix: 'TODO: ...'` with a step-by-step user-runnable remedy, set `severity` if `medium` default is wrong.
+4. **edit** - call `applyEdit(draftPath)` which returns the draft path. The caller opens `$EDITOR` on the path; on clean exit, re-discover the draft and re-prompt. Typical edits: replace `pattern: 'TODO: ...'` with a conservative regex, replace `fix: 'TODO: ...'` with a step-by-step user-runnable remedy, set `severity` if `medium` default is wrong.
 
-**Why this is gated.** `reference/known-failure-modes.md` feeds Phase 30's `triage-matcher.cjs` BEFORE the consent prompt — a bad entry could mute legitimate issue reports. The user-review gate is non-negotiable (D-05). The proposer is strictly proposal-only; the canonical catalogue only changes via the accept action.
+**Why this is gated.** `reference/known-failure-modes.md` feeds Phase 30's `triage-matcher.cjs` BEFORE the consent prompt - a bad entry could mute legitimate issue reports. The user-review gate is non-negotiable (D-05). The proposer is strictly proposal-only; the canonical catalogue only changes via the accept action.

package/dist/claude-code/.claude/skills/audit/SKILL.md

@@ -7,7 +7,7 @@ tools: Read, Write, Task, Glob, Bash
 
 # /gdd:audit
 
-Wraps the existing `design-auditor`, `design-verifier`, and `design-integration-checker` agents — no new auditor logic here. Parses flags, spawns the right combination, prints summary.
+Wraps the existing `design-auditor`, `design-verifier`, and `design-integration-checker` agents - no new auditor logic here. Parses flags, spawns the right combination, prints summary.
 
 For the 6-pillar scoring rubric this skill aggregates, see `../../reference/audit-scoring.md`. For the shared design-quality pillar set that frames the score categories, see `../../reference/shared-preamble.md`.
 
@@ -16,7 +16,7 @@ For the 6-pillar scoring rubric this skill aggregates, see `../../reference/audi
 ### Default
 Spawn `design-auditor` (6-pillar scoring 1–4) in parallel with `design-integration-checker`. After both finish, read `.design/DESIGN-AUDIT.md` and `.design/DESIGN-INTEGRATION.md` and print a consolidated summary (scores + top 3 findings each).
 
-After the auditor and integration checker complete, check if `.design/learnings/` exists and contains at least one `.md` file. If so — and unless `--no-reflect` is passed — spawn `design-reflector` for the current cycle. Append the reflection proposal count to the audit summary: "Reflection: N proposals → review with `/gdd:apply-reflections`".
+After the auditor and integration checker complete, check if `.design/learnings/` exists and contains at least one `.md` file. If so - and unless `--no-reflect` is passed - spawn `design-reflector` for the current cycle. Append the reflection proposal count to the audit summary: "Reflection: N proposals → review with `/gdd:apply-reflections`".
 
 ### `--retroactive`
 Spawn `design-verifier` with cycle-span scope. Verifier reads all tasks completed in the current cycle (from STATE.md `<completed_tasks>` list for the active `cycle:` ID) and uses `DESIGN-PLAN.md` goals as the reference baseline for what "should have been done." Output: `.design/DESIGN-VERIFICATION.md` with per-task pass/fail.
@@ -37,7 +37,7 @@ Run only `design-auditor` (skip `design-integration-checker`). Faster health che
    - Check if `.design/learnings/` exists and has ≥1 `.md` file
    - If yes: spawn `design-reflector` for the current cycle slug (read from STATE.md)
    - After completion: count proposal types and append to summary
-6. Recommend next action based on findings (e.g., "Score 2/4 on typography — run `/gdd:discuss typography` to gather decisions").
+6. Recommend next action based on findings (e.g., "Score 2/4 on typography - run `/gdd:discuss typography` to gather decisions").
 
 ## Registered Audit Agents
 
@@ -53,7 +53,7 @@ Run only `design-auditor` (skip `design-integration-checker`). Faster health che
 - Do not modify source files.
 - Do not rerun stages; this is a read-only audit.
 
-## Step 7 — Update notice (post-closeout surface)
+## Step 7 - Update notice (post-closeout surface)
 
 After the consolidated audit summary has been printed (and any reflection-proposal count appended), emit the plugin-update banner if one is present:
 
@@ -63,17 +63,17 @@ After the consolidated audit summary has been printed (and any reflection-propos
 
 Written by `hooks/update-check.sh`; suppressed mid-pipeline and when the latest release is dismissed.
 
-## Rationalizations — Thought to Reality
+## Rationalizations - Thought to Reality
 
 The excuses an agent reaches for to skip or thin out an audit, and the drift each one misses:
 
 | Thought | Reality |
 |---------|---------|
 | "The audit passed last cycle, I can skip it this cycle." | Per-cycle audit catches drift the prior pass couldn't see; a skipped review is exactly where regressions accumulate unnoticed. |
-| "`--quick` is fine, integration isn't the concern here." | Dropping the integration-checker hides orphaned decisions — wiring breaks even when the 6-pillar score looks healthy. |
+| "`--quick` is fine, integration isn't the concern here." | Dropping the integration-checker hides orphaned decisions - wiring breaks even when the 6-pillar score looks healthy. |
 | "I can eyeball the scores instead of spawning the auditor." | The auditor's rubric scores six pillars consistently; an eyeballed review drifts toward whatever the agent already believes. |
 | "Reflection proposals are optional polish, skip the reflector." | The reflector turns this cycle's learnings into next-cycle improvements; skipping it lets the same mistakes repeat. |
 | "I'll modify the source while I'm in here fixing findings." | Audit is read-only by contract; editing source mid-audit invalidates the very scores you're producing. |
-| "Retroactive mode is overkill for a finished cycle." | Retroactive verification is the only check on tasks that shipped without per-task verify — skipping it leaves a completed cycle unaudited. |
+| "Retroactive mode is overkill for a finished cycle." | Retroactive verification is the only check on tasks that shipped without per-task verify - skipping it leaves a completed cycle unaudited. |
 
 ## AUDIT COMPLETE

package/dist/claude-code/.claude/skills/bandit-status/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: gdd-bandit-status
-description: "Surface read-only per-(agent, bin, delegate) bandit posterior snapshot — alpha/beta/mean/stddev/count/last-used per arm. Phase 27.5 (v1.27.5) diagnostic. Use when investigating 'why did the bandit pick tier X for agent Y?' or when verifying posterior convergence after enabling adaptive_mode: full."
+description: "Surface read-only per-(agent, bin, delegate) bandit posterior snapshot - alpha/beta/mean/stddev/count/last-used per arm. Phase 27.5 (v1.27.5) diagnostic. Use when investigating 'why did the bandit pick tier X for agent Y?' or when verifying posterior convergence after enabling adaptive_mode: full."
 argument-hint: ""
 tools: Read, Bash
 ---
@@ -9,7 +9,7 @@ tools: Read, Bash
 
 ## Role
 
-You are a deterministic, read-only diagnostic skill. You do not spawn agents and do not modify the posterior. You read `.design/telemetry/posterior.json` (path declared by `scripts/lib/bandit-router.cjs`'s `DEFAULT_POSTERIOR_PATH`), aggregate per-`(agent, bin, delegate, tier)` arm state, and emit a single Markdown table. Read-only per Phase 27.5 D-11 — to reset, use `/gdd:bandit-reset` (Phase 23.5). See `./reference/bandit-integration.md` for setup, interpretation, and convergence guidance.
+You are a deterministic, read-only diagnostic skill. You do not spawn agents and do not modify the posterior. You read `.design/telemetry/posterior.json` (path declared by `scripts/lib/bandit-router.cjs`'s `DEFAULT_POSTERIOR_PATH`), aggregate per-`(agent, bin, delegate, tier)` arm state, and emit a single Markdown table. Read-only per Phase 27.5 D-11 - to reset, use `/gdd:bandit-reset` (Phase 23.5). See `./reference/bandit-integration.md` for setup, interpretation, and convergence guidance.
 
 ## Invocation Contract
 
@@ -51,7 +51,7 @@ Schema:
 }
 ```
 
-The `delegate` field is optional — absent = Phase 23.5 legacy slice (rendered as `-` in the table).
+The `delegate` field is optional - absent = Phase 23.5 legacy slice (rendered as `-` in the table).
 
 ### 3. Render the table
 
@@ -81,7 +81,7 @@ Total arms: <count>
 
 Precision: alpha/beta 2 decimals; mean/stddev 3 decimals; count integer; `last_used` truncated to minute (`YYYY-MM-DDTHH:MM`); null `last_used` renders `-`.
 
-After the table, surface a per-`(agent, bin)` best-arm summary: for each unique pair, identify highest-mean arm (tie-broken by `count` DESC) — answers "why did the bandit pick tier X?" at a glance.
+After the table, surface a per-`(agent, bin)` best-arm summary: for each unique pair, identify highest-mean arm (tie-broken by `count` DESC) - answers "why did the bandit pick tier X?" at a glance.
 
 ### 4. Record
 
@@ -89,6 +89,6 @@ Append one JSONL line to `.design/skill-records.jsonl`: `{"skill":"gdd-bandit-st
 
 ## Cross-references
 
-- `./reference/bandit-integration.md` — operator guide; interpretation patterns.
-- `scripts/lib/bandit-router.cjs` (Phase 23.5) — posterior shape, `DEFAULT_POSTERIOR_PATH`, `loadPosterior()`.
-- `scripts/lib/bandit-router/integration.cjs` (27.5-01), `hooks/budget-enforcer.ts` (27.5-02), `scripts/lib/session-runner/index.ts` (27.5-03), `scripts/lib/bandit-arbitrage.cjs` (27.5-04), `/gdd:bandit-reset` (Phase 23.5) — only surface that mutates the posterior.
+- `./reference/bandit-integration.md` - operator guide; interpretation patterns.
+- `scripts/lib/bandit-router.cjs` (Phase 23.5) - posterior shape, `DEFAULT_POSTERIOR_PATH`, `loadPosterior()`.
+- `scripts/lib/bandit-router/integration.cjs` (27.5-01), `hooks/budget-enforcer.ts` (27.5-02), `scripts/lib/session-runner/index.ts` (27.5-03), `scripts/lib/bandit-arbitrage.cjs` (27.5-04), `/gdd:bandit-reset` (Phase 23.5) - only surface that mutates the posterior.

package/dist/claude-code/.claude/skills/benchmark/SKILL.md

@@ -18,22 +18,22 @@ conventions are at `../../reference/shared-preamble.md#output-contract-reminders
 |------------|--------|
 | `/gdd:benchmark <component>` | Harvest + synthesize a single component |
 | `/gdd:benchmark --wave <N>` | Run a full wave (1 = Inputs, 2 = Containers, etc.) |
-| `/gdd:benchmark --list` | Show corpus coverage — which specs exist, which are pending |
+| `/gdd:benchmark --list` | Show corpus coverage - which specs exist, which are pending |
 | `/gdd:benchmark --refresh <component>` | Re-harvest a spec (for design-system version bumps) |
 
 ## Single-Component Flow (`/gdd:benchmark <component>`)
 
-1. **Check if spec exists** — `Glob("reference/components/<component>.md")`. If found and `--refresh` was not passed, confirm before overwriting.
+1. **Check if spec exists** - `Glob("reference/components/<component>.md")`. If found and `--refresh` was not passed, confirm before overwriting.
 
-2. **Harvest** — spawn `component-benchmark-harvester` with required-reading `@connections/design-corpora.md`, target component, raw-output path `.planning/benchmarks/raw/<component>.md`, and a salvage hint to `.planning/research/impeccable-salvage/`. Acceptance: raw harvest exists with ≥4 source sections.
+2. **Harvest** - spawn `component-benchmark-harvester` with required-reading `@connections/design-corpora.md`, target component, raw-output path `.planning/benchmarks/raw/<component>.md`, and a salvage hint to `.planning/research/impeccable-salvage/`. Acceptance: raw harvest exists with ≥4 source sections.
 
-3. **Synthesize** — spawn `component-benchmark-synthesizer` with required-reading `@.planning/benchmarks/raw/<component>.md`, `@reference/components/TEMPLATE.md`, `@reference/anti-patterns.md`. Output: `reference/components/<component>.md`. Also update `reference/components/README.md` (add entry in correct category). Acceptance: spec ≤350 lines, cites ≥4 systems, follows `TEMPLATE.md` sections, has a WAI-ARIA keyboard contract + a failing-example block.
+3. **Synthesize** - spawn `component-benchmark-synthesizer` with required-reading `@.planning/benchmarks/raw/<component>.md`, `@reference/components/TEMPLATE.md`, `@reference/anti-patterns.md`. Output: `reference/components/<component>.md`. Also update `reference/components/README.md` (add entry in correct category). Acceptance: spec ≤350 lines, cites ≥4 systems, follows `TEMPLATE.md` sections, has a WAI-ARIA keyboard contract + a failing-example block.
 
-4. **Report** — print spec path, line count, systems cited.
+4. **Report** - print spec path, line count, systems cited.
 
 ## Wave Mode (`/gdd:benchmark --wave <N>`)
 
-Read the wave definition from `reference/components/README.md` and run each component sequentially (not parallel — each harvest is network-bound and the raw files are large).
+Read the wave definition from `reference/components/README.md` and run each component sequentially (not parallel - each harvest is network-bound and the raw files are large).
 
 | Wave | Components |
 |------|-----------|
@@ -52,7 +52,7 @@ Same as single-component flow but skips the "already exists" guard. Use when a d
 
 ## Source List
 
-`../../connections/design-corpora.md` — 18 design systems with canonical URLs, licensing, and fallback chain (canonical → archive.org → Refero MCP → Pinterest MCP).
+`../../connections/design-corpora.md` - 18 design systems with canonical URLs, licensing, and fallback chain (canonical → archive.org → Refero MCP → Pinterest MCP).
 
 ## Output Artifacts
 

package/dist/claude-code/.claude/skills/bootstrap-ds/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: gdd-bootstrap-ds
-description: "Bootstraps a design system for a GREENFIELD project that has none — no Figma, no tokens, no component library. Takes a brand input (primary color + optional secondary + tone tags + target framework) and emits a coherent OKLCH token system (color tints, modular type scale, 4pt/8pt spacing, radius + motion defaults) in 3 variants to pick from, then scaffolds proof components (button/input/card). Use at the start of a brand-new project, or when /gdd:discover finds no existing design system. Never invents a brand; never overwrites an existing DS."
+description: "Bootstraps a design system for a GREENFIELD project that has none - no Figma, no tokens, no component library. Takes a brand input (primary color + optional secondary + tone tags + target framework) and emits a coherent OKLCH token system (color tints, modular type scale, 4pt/8pt spacing, radius + motion defaults) in 3 variants to pick from, then scaffolds proof components (button/input/card). Use at the start of a brand-new project, or when /gdd:discover finds no existing design system. Never invents a brand; never overwrites an existing DS."
 argument-hint: "[--primary <color>] [--secondary <color>] [--tone <tags>] [--framework web|native-ios|native-android|flutter]"
 user-invocable: true
 tools: Read, Write, Bash, Glob, Grep, AskUserQuestion, Task
@@ -8,31 +8,31 @@ tools: Read, Write, Bash, Glob, Grep, AskUserQuestion, Task
 
 # /gdd:bootstrap-ds
 
-Greenfield design-system bootstrap. Closes the gap that GDD's `design-context-builder` assumes a design system already exists (in code or Figma) — a brand-new project has none. This skill is the **front door**: it collects a brand input and hands it to `agents/ds-generator.md`, which emits the token system + proof components per `reference/ds-bootstrap-rubric.md` (deterministic math in `scripts/lib/ds/token-scale.cjs`).
+Greenfield design-system bootstrap. Closes the gap that GDD's `design-context-builder` assumes a design system already exists (in code or Figma) - a brand-new project has none. This skill is the **front door**: it collects a brand input and hands it to `agents/ds-generator.md`, which emits the token system + proof components per `reference/ds-bootstrap-rubric.md` (deterministic math in `scripts/lib/ds/token-scale.cjs`).
 
 ## When to use
 
 - At the start of a brand-new project (no `tailwind.config`, no token file, no DS).
 - When `/gdd:discover` / `design-context-builder` reports **no existing design system** and the user opts to bootstrap one.
 
-If a design system **already exists**, do NOT run this — defer to `design-context-builder` (it maps the existing one). State that and stop.
+If a design system **already exists**, do NOT run this - defer to `design-context-builder` (it maps the existing one). State that and stop.
 
 ## Steps
 
 1. **Collect the brand input.** From flags, or via `AskUserQuestion` for anything missing:
-   - **primary** (required) — the brand color (hex / rgb / `oklch()`).
-   - **secondary** (optional) — a second brand color (emitted only if supplied — the rubric's ≤2-brand-colors rule).
-   - **tone tags** (optional) — `calm` / `corporate` / `editorial` / `playful` / `bold` (maps to the type ratio + chroma treatment).
-   - **target framework** (optional) — `web` (default) / `native-ios` / `native-android` / `flutter`. Detect from the project if absent (Phase 34 routing).
+   - **primary** (required) - the brand color (hex / rgb / `oklch()`).
+   - **secondary** (optional) - a second brand color (emitted only if supplied - the rubric's ≤2-brand-colors rule).
+   - **tone tags** (optional) - `calm` / `corporate` / `editorial` / `playful` / `bold` (maps to the type ratio + chroma treatment).
+   - **target framework** (optional) - `web` (default) / `native-ios` / `native-android` / `flutter`. Detect from the project if absent (Phase 34 routing).
 2. **Delegate to `ds-generator`** (via `Task`): it resolves the primary to OKLCH, runs `token-scale.cjs` for **3 variants** (conservative / balanced / bold), and presents them.
 3. **Pick a variant.** Surface the 3 variants (primary `500`, type ratio, spacing baseline, radius, feel); the user picks ONE.
 4. **Emit + scaffold (proposal → confirm).** `ds-generator` emits the chosen token set (role-named CSS custom properties + the framework mapping) and scaffolds **button / input / card** as a coherence proof. Nothing is written to `src/` without confirmation.
 
 ## Do Not
 
-- Do not invent a brand (no logomark, no typeface choice, no third brand color) — emit a token *system*, not an identity.
-- Do not overwrite an existing design system — defer to `design-context-builder`.
-- Do not add a color-conversion dependency — `token-scale.cjs` emits native CSS `oklch()`.
+- Do not invent a brand (no logomark, no typeface choice, no third brand color) - emit a token *system*, not an identity.
+- Do not overwrite an existing design system - defer to `design-context-builder`.
+- Do not add a color-conversion dependency - `token-scale.cjs` emits native CSS `oklch()`.
 
 ## Output
 

package/dist/claude-code/.claude/skills/brief/SKILL.md

@@ -5,7 +5,7 @@ argument-hint: "[--re-brief to redo intake on existing project]"
 tools: Read, Write, AskUserQuestion, mcp__gdd_state__frontmatter_update, mcp__gdd_state__set_status, mcp__gdd_state__update_progress, mcp__gdd_state__get
 ---
 
-# Get Design Done — Brief
+# Get Design Done - Brief
 
 **Role:** You are the Brief stage. Stage 1 of 5 in the get-design-done pipeline.
 
@@ -13,7 +13,7 @@ tools: Read, Write, AskUserQuestion, mcp__gdd_state__frontmatter_update, mcp__gd
 
 ---
 
-## Step 1 — Check for existing BRIEF.md
+## Step 1 - Check for existing BRIEF.md
 
 1. Read `.design/BRIEF.md` if it exists.
 2. Parse it into sections: Problem, Audience, Constraints, Success Metrics, Scope.
@@ -21,19 +21,19 @@ tools: Read, Write, AskUserQuestion, mcp__gdd_state__frontmatter_update, mcp__gd
 4. If `--re-brief` flag is passed, ignore existing answers and ask all five questions.
 5. Otherwise, only ask questions for unanswered sections.
 
-## Step 2 — Interview
+## Step 2 - Interview
 
 Ask the following one at a time using `AskUserQuestion`, only for unanswered sections:
 
-1. **Problem** — "What design problem are we solving? (user-facing outcome)"
-2. **Audience** — "Who is the primary audience? (role, device, context)"
-3. **Constraints** — "What constraints apply? (tech stack, brand, time, a11y requirements)"
-4. **Success Metrics** — "How will we measure success? (specific metrics or outcomes)"
-5. **Scope** — "What is in/out of scope for this cycle?"
+1. **Problem** - "What design problem are we solving? (user-facing outcome)"
+2. **Audience** - "Who is the primary audience? (role, device, context)"
+3. **Constraints** - "What constraints apply? (tech stack, brand, time, a11y requirements)"
+4. **Success Metrics** - "How will we measure success? (specific metrics or outcomes)"
+5. **Scope** - "What is in/out of scope for this cycle?"
 
 Do not proceed to the next question until the current one is answered.
 
-## Step 3 — Write .design/BRIEF.md
+## Step 3 - Write .design/BRIEF.md
 
 Write the brief with these sections, preserving any pre-existing answers:
 
@@ -62,15 +62,15 @@ Write the brief with these sections, preserving any pre-existing answers:
 </prior-research>
 ```
 
-Leave the `<prior-research>` block empty on a greenfield brief — it is filled by `/gdd:research-sync` (the `user-research-synthesizer`) when a research source is connected, and re-checked at verify. See `reference/design-variants.md` for the outcome loop.
+Leave the `<prior-research>` block empty on a greenfield brief - it is filled by `/gdd:research-sync` (the `user-research-synthesizer`) when a research source is connected, and re-checked at verify. See `reference/design-variants.md` for the outcome loop.
 
-## Step 4 — Bootstrap STATE.md (if missing)
+## Step 4 - Bootstrap STATE.md (if missing)
 
 <!-- BOOTSTRAP EXCEPTION: STATE.md does not exist yet — MCP tools require it to exist. Direct Write is intentional. All subsequent mutations use MCP. -->
 
-If `.design/STATE.md` does not exist, copy the template block from `reference/STATE-TEMPLATE.md` (between `==== BEGIN TEMPLATE ====` and `==== END TEMPLATE ====`) to `.design/STATE.md` via `Write`. Leave the `<ISO 8601 timestamp>` placeholders in-place — Step 5 stamps them via MCP. If STATE.md already exists, skip to Step 5.
+If `.design/STATE.md` does not exist, copy the template block from `reference/STATE-TEMPLATE.md` (between `==== BEGIN TEMPLATE ====` and `==== END TEMPLATE ====`) to `.design/STATE.md` via `Write`. Leave the `<ISO 8601 timestamp>` placeholders in-place - Step 5 stamps them via MCP. If STATE.md already exists, skip to Step 5.
 
-## Step 5 — Commit STATE.md initialization
+## Step 5 - Commit STATE.md initialization
 
 With `.design/STATE.md` seeded from the template:
 
@@ -78,16 +78,16 @@ With `.design/STATE.md` seeded from the template:
 2. Mark brief progress: call `mcp__gdd_state__update_progress` with `task_progress: "5/5"`, `status: "brief_complete"`.
 3. Set handoff status: call `mcp__gdd_state__set_status` with `status: "brief_complete"`.
 
-Do NOT call `mcp__gdd_state__transition_stage` from brief — explore calls it on entry, keeping the transition atomic with the stage that owns the new state.
+Do NOT call `mcp__gdd_state__transition_stage` from brief - explore calls it on entry, keeping the transition atomic with the stage that owns the new state.
 
-## Step 6 — Inline glossary (CONTEXT.md) + ADR pointer
+## Step 6 - Inline glossary (CONTEXT.md) + ADR pointer
 
 When a fuzzy phrase is resolved or a new domain concept is named during the briefing
 interview: write to `./CONTEXT.md` IMMEDIATELY per `./../../reference/context-md-format.md`
 (H2 heading + body; lazy-create on first term; no batching). Glossary entries compound
-across cycles — token savings + naming consistency.
+across cycles - token savings + naming consistency.
 
-Project-shaping decisions surfaced in briefing can be promoted to an ADR — see
+Project-shaping decisions surfaced in briefing can be promoted to an ADR - see
 `./../../reference/adr-format.md` for the 3-criteria gate (hard-to-reverse AND
 surprising-without-context AND real-tradeoff). Routine choices stay in STATE.md.
 
@@ -112,16 +112,16 @@ Run this final spec-quality pass over `.design/BRIEF.md` before the brief→expl
 Do NOT transition to explore (or invoke `/gdd:explore`) until the brief artifact (default `.design/BRIEF.md`) is committed AND the user has approved it. If this project uses a custom `.design` location, read the artifact path from `.design/STATE.md` rather than assuming the default.
 </HARD-GATE>
 
-## Rationalizations — Thought to Reality
+## Rationalizations - Thought to Reality
 
 The excuses an agent invents to skip or shortcut the brief, and what each one actually costs the cycle:
 
 | Thought | Reality |
 |---------|---------|
 | "This brief is too simple to need a problem statement." | Skip the brief = guess at requirements, then redesign mid-design when the real problem surfaces. |
-| "The user told me what to build, I can skip the interview." | Unasked constraints (a11y, brand, stack) become rework — the five questions exist because each one has blown a past cycle. |
+| "The user told me what to build, I can skip the interview." | Unasked constraints (a11y, brand, stack) become rework - the five questions exist because each one has blown a past cycle. |
 | "I'll capture success metrics later in verify." | Verify has nothing to check against; an un-metricked brief produces an un-verifiable cycle. |
-| "Scope is obvious, I don't need an in/out line." | Undeclared scope is scope creep waiting to happen — the explore scan widens to fill the vacuum. |
+| "Scope is obvious, I don't need an in/out line." | Undeclared scope is scope creep waiting to happen - the explore scan widens to fill the vacuum. |
 | "I can answer all five questions for the user from context." | AskUserQuestion one-at-a-time exists because batched/assumed answers smuggle in wrong premises that compound downstream. |
 | "STATE.md bootstrap can wait." | Every later MCP mutation requires STATE.md to exist; skipping the bootstrap hard-blocks explore on entry. |
 

package/dist/claude-code/.claude/skills/budget/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: gdd-budget
-description: "Forecasts GDD design-cycle spend before the bill arrives. Reads .design/telemetry/costs.jsonl (cost per cycle) + .design/budget.json (the project_cap), runs the pure cost-forecast model via agents/cost-forecaster.md, and projects the next N cycles — surfacing 'at the current rate you'll hit your $X project cap in Y cycles.' Supports --scenario best|typical|worst and --cycles N. Read-only — it forecasts and warns; it never spends, edits budget.json, or halts (the budget-enforcer hook halts). Use to sanity-check spend trajectory before a long run."
+description: "Forecasts GDD design-cycle spend before the bill arrives. Reads .design/telemetry/costs.jsonl (cost per cycle) + .design/budget.json (the project_cap), runs the pure cost-forecast model via agents/cost-forecaster.md, and projects the next N cycles - surfacing 'at the current rate you'll hit your $X project cap in Y cycles.' Supports --scenario best|typical|worst and --cycles N. Read-only - it forecasts and warns; it never spends, edits budget.json, or halts (the budget-enforcer hook halts). Use to sanity-check spend trajectory before a long run."
 argument-hint: "[--cycles N] [--scenario best|typical|worst]"
 user-invocable: true
 tools: Read, Bash, Grep, Glob, ToolSearch, Task
@@ -10,7 +10,7 @@ tools: Read, Bash, Grep, Glob, ToolSearch, Task
 
 Closes the long-horizon cost gap: Phase 10.1 per-task caps + Phase 26 per-runtime telemetry track
 *cost*, but nothing **forecasts** it. This skill projects the next N cycles of spend and tells you how
-many cycles you have before you hit your `project_cap`. **Read-only** — it forecasts and warns; it
+many cycles you have before you hit your `project_cap`. **Read-only** - it forecasts and warns; it
 never spends, never edits `budget.json`, and never halts (the Phase 25 budget-enforcer hook is the
 only thing that blocks a spawn). Contract: `../../reference/cost-governance.md`.
 
@@ -30,11 +30,11 @@ only thing that blocks a spawn). Contract: `../../reference/cost-governance.md`.
    `scripts/lib/budget/cost-forecast.cjs` model for the requested `--scenario`/`--cycles`, reads
    `project_cap_usd` from `.design/budget.json`, and computes cycles-to-cap.
 3. **Render.** Show: the scenario + its per-cycle rate, the best↔worst band, the projected total over
-   N cycles, and — when `project_cap_usd > 0` — **"at the `<scenario>` rate (~$X/cycle) you'll reach
+   N cycles, and - when `project_cap_usd > 0` - **"at the `<scenario>` rate (~$X/cycle) you'll reach
    your $`<cap>` project cap in `<Y>` cycles"** (or "not at this rate" when the trend is flat/down).
    When no cap is set, show the trajectory and note that `project_cap_usd` is unset (so the hook won't
    halt).
-4. **Do not act.** Never raise/lower the cap, never spend — GDD forecasts; the human sets the budget.
+4. **Do not act.** Never raise/lower the cap, never spend - GDD forecasts; the human sets the budget.
 
 ## Output
 

package/dist/claude-code/.claude/skills/cache-manager/SKILL.md

@@ -10,14 +10,14 @@ disable-model-invocation: true
 
 ## Role
 
-You are the deterministic cache-key computer and cache-manifest writer for the optimization layer. You do not spawn agents, and you do not make model calls. You read agent paths, input file paths, and input file contents; you compute a stable SHA-256 key; you look that key up in `.design/cache-manifest.json`; you return a hit (cached result + `cache_hit: true`) or a miss. On spawn completion, the orchestrator calls you again to persist the result. You are Layer B of the two-layer cache (D-08). Layer A — Anthropic's 5-min prompt cache — is not owned by you; it's owned by the shared-preamble ordering convention in `agents/README.md`.
+You are the deterministic cache-key computer and cache-manifest writer for the optimization layer. You do not spawn agents, and you do not make model calls. You read agent paths, input file paths, and input file contents; you compute a stable SHA-256 key; you look that key up in `.design/cache-manifest.json`; you return a hit (cached result + `cache_hit: true`) or a miss. On spawn completion, the orchestrator calls you again to persist the result. You are Layer B of the two-layer cache (D-08). Layer A - Anthropic's 5-min prompt cache - is not owned by you; it's owned by the shared-preamble ordering convention in `agents/README.md`.
 
 ## Invocation Contract
 
 ### Phase 1: compute-key
 
-- **Input**: `{agent_path: string, input_file_paths: string[]}` — `agent_path` is the absolute or repo-relative path to the `agents/<name>.md` file; `input_file_paths` is the sorted-unique list of files the agent will read.
-- **Output**: `{input_hash: string}` — 64-character lowercase SHA-256 hex.
+- **Input**: `{agent_path: string, input_file_paths: string[]}` - `agent_path` is the absolute or repo-relative path to the `agents/<name>.md` file; `input_file_paths` is the sorted-unique list of files the agent will read.
+- **Output**: `{input_hash: string}` - 64-character lowercase SHA-256 hex.
 - **Algorithm**: canonicalize inputs, concat with newline separators, SHA-256 (see Deterministic Input-Hash Algorithm below).
 
 ### Phase 2: lookup
@@ -33,18 +33,18 @@ You are the deterministic cache-key computer and cache-manifest writer for the o
 
 ### Phase 4: write-result-on-completion
 
-- **Input**: `{input_hash: string, agent: string, result: string, ttl_seconds: number}` — `ttl_seconds` defaults to `.design/budget.json.cache_ttl_seconds` (3600 if budget.json absent).
+- **Input**: `{input_hash: string, agent: string, result: string, ttl_seconds: number}` - `ttl_seconds` defaults to `.design/budget.json.cache_ttl_seconds` (3600 if budget.json absent).
 - **Behavior**: open `.design/cache-manifest.json` (create if missing), set key `input_hash` → `{agent, result, written_at, ttl_seconds, expires_at}`, write file. `written_at` is `new Date().toISOString()`. `expires_at` is `written_at + ttl_seconds` as ISO.
 
 ## Deterministic Input-Hash Algorithm
 
-The canonical reference implementation (single source of truth; `hooks/budget-enforcer.js` imports the same primitive via a shared helper) lives in `./cache-policy.md#deterministic-input-hash-algorithm-layer-b` — it documents the JS implementation, the maintainer notes (sorted-unique paths, MISSING-file sentinel, agent-path bust behavior), the manifest shape, and TTL semantics in one place. Conform to the algorithm exactly so the hook and any orchestrator agree byte-for-byte.
+The canonical reference implementation (single source of truth; `hooks/budget-enforcer.js` imports the same primitive via a shared helper) lives in `./cache-policy.md#deterministic-input-hash-algorithm-layer-b` - it documents the JS implementation, the maintainer notes (sorted-unique paths, MISSING-file sentinel, agent-path bust behavior), the manifest shape, and TTL semantics in one place. Conform to the algorithm exactly so the hook and any orchestrator agree byte-for-byte.
 
 ## Integration Points
 
 - **`hooks/budget-enforcer.js`** (Plan 10.1-01) reads the manifest on every Agent spawn. The hook already calls `cacheLookup(agent, inputHash)` against `.design/cache-manifest.json`. This skill is the authority on how `inputHash` is computed so the hook and any orchestrator agree byte-for-byte.
 - **Orchestrators** (e.g., `skills/map/`, `skills/discover/`, `skills/plan/`) invoke Phase 1 (compute-key) + Phase 4 (write-result-on-completion) around each Agent spawn they launch. Phase 2 + Phase 3 are executed by the hook.
-- **Warm-cache command** (`skills/warm-cache/SKILL.md`, Task 02) does not touch Layer B — it only primes Anthropic's 5-min prompt cache (Layer A). Do not confuse the two.
+- **Warm-cache command** (`skills/warm-cache/SKILL.md`, Task 02) does not touch Layer B - it only primes Anthropic's 5-min prompt cache (Layer A). Do not confuse the two.
 
 ## Failure Modes