@hegemonart/get-design-done 1.57.1 → 1.57.2

package/reference/config-schema.md

@@ -122,7 +122,7 @@ Agents never read config directly - the profile is always injected at spawn time
 
 ## .design/budget.json Schema (Phase 10.1)
 
-Governs the optimization layer introduced in Phase 10.1. Read by every `Agent` tool spawn via `hooks/budget-enforcer.js` (PreToolUse). Bootstrap writes defaults if the file is missing.
+Governs the optimization layer introduced in Phase 10.1. Read by every `Agent` tool spawn via `hooks/budget-enforcer.ts` (PreToolUse). Bootstrap writes defaults if the file is missing.
 
 ## Full Schema
 
@@ -215,11 +215,11 @@ If `.design/budget.json` is missing when any `/gdd:*` command runs, `scripts/boo
 
 ## .design/telemetry/costs.jsonl + .design/agent-metrics.json (Phase 10.1)
 
-Phase 10.1 introduces two measurement artifacts written by `hooks/budget-enforcer.js` (PreToolUse on `Agent` spawns) and `scripts/aggregate-agent-metrics.ts` (detached child of the hook + refresh step of `/gdd:optimize`). Both files live under the gitignored `.design/` directory - they are local session state, not committed.
+Phase 10.1 introduces two measurement artifacts written by `hooks/budget-enforcer.ts` (PreToolUse on `Agent` spawns) and `scripts/aggregate-agent-metrics.ts` (detached child of the hook + refresh step of `/gdd:optimize`). Both files live under the gitignored `.design/` directory - they are local session state, not committed.
 
 ### .design/telemetry/costs.jsonl
 
-Append-only ledger. One JSON object per line. Written by `hooks/budget-enforcer.js` on every PreToolUse decision: spawn allowed, spawn blocked by cap, tier downgraded, cache-hit short-circuit, lazy-gate skip. Consumed by the Phase 11 reflector (`agents/design-reflector.md`) and by `/gdd:optimize`.
+Append-only ledger. One JSON object per line. Written by `hooks/budget-enforcer.ts` on every PreToolUse decision: spawn allowed, spawn blocked by cap, tier downgraded, cache-hit short-circuit, lazy-gate skip. Consumed by the Phase 11 reflector (`agents/design-reflector.md`) and by `/gdd:optimize`.
 
 **Row schema** (verbatim from ROADMAP criterion 7):
 
@@ -292,11 +292,11 @@ Both files sit inside `.design/`, which is already `.gitignore`d at the project
 
 ### Refresh cadence
 
-The aggregator is invoked as a detached child process by `hooks/budget-enforcer.js` after every telemetry row write. It is also invoked directly by `/gdd:optimize` before analysis. There is no cron, no daemon, and no scheduled task - metrics are always at most one spawn stale.
+The aggregator is invoked as a detached child process by `hooks/budget-enforcer.ts` after every telemetry row write. It is also invoked directly by `/gdd:optimize` before analysis. There is no cron, no daemon, and no scheduled task - metrics are always at most one spawn stale.
 
 ## .design/cache-manifest.json Schema (Phase 10.1)
 
-Authored and maintained by `skills/cache-manager/SKILL.md`. Read by `hooks/budget-enforcer.js` (PreToolUse on Agent spawns) for short-circuiting cached spawns per D-05. Layer B of the D-08 two-layer cache. Flat KV shape - keys are SHA-256 hex of the deterministic input-hash, values are entry objects. Schema version 1.
+Authored and maintained by `skills/cache-manager/SKILL.md`. Read by `hooks/budget-enforcer.ts` (PreToolUse on Agent spawns) for short-circuiting cached spawns per D-05. Layer B of the D-08 two-layer cache. Flat KV shape - keys are SHA-256 hex of the deterministic input-hash, values are entry objects. Schema version 1.
 
 ## Full Schema
 
@@ -357,22 +357,22 @@ String - ISO-8601 UTC timestamp equal to `written_at + ttl_seconds`. Precomputed
 - TTL is copied into each entry at write time - **not** recomputed on read. Budget.json changes do not retroactively affect existing entries.
 - `expires_at` = `written_at + ttl_seconds`, computed once, stored in the entry.
 - Stale entries are **not** actively purged (lazy cleanup): they remain in the file until overwritten by a new write with the same key, or pruned manually. A proactive reaper is out of v1 scope.
-- Readers (`hooks/budget-enforcer.js`) check `Date.now() / 1000 > Date.parse(expires_at) / 1000`; if true, return miss.
+- Readers (`hooks/budget-enforcer.ts`) check `Date.now() / 1000 > Date.parse(expires_at) / 1000`; if true, return miss.
 
 ## Read/Write contract
 
 - **Single writer**: `skills/cache-manager/SKILL.md` Phase 4 (`write-result-on-completion`). Other code must not write this file directly.
-- **Multiple readers**: `hooks/budget-enforcer.js`, any orchestrator that runs Phase 2 (`lookup`) for dry-run planning. Readers treat malformed JSON as "manifest absent" (empty cache) - do not throw.
+- **Multiple readers**: `hooks/budget-enforcer.ts`, any orchestrator that runs Phase 2 (`lookup`) for dry-run planning. Readers treat malformed JSON as "manifest absent" (empty cache) - do not throw.
 - **Concurrency**: Claude Code agent spawns are serialized at the hook level (PreToolUse is synchronous). No file locking is needed at v1 scale. Concurrent writes from parallel orchestrators are theoretically possible but exceedingly rare; last-writer-wins is acceptable (cache miss on next read re-populates).
 
 ## Bootstrap behavior
 
-If `.design/cache-manifest.json` is missing when `hooks/budget-enforcer.js` reads it, the hook treats every lookup as a miss and the spawn proceeds normally. No bootstrap action is required - the manifest is created lazily on first successful spawn when `skills/cache-manager/SKILL.md` Phase 4 fires. Unlike `.design/budget.json`, missing cache-manifest.json is the **correct** initial state on a fresh repo.
+If `.design/cache-manifest.json` is missing when `hooks/budget-enforcer.ts` reads it, the hook treats every lookup as a miss and the spawn proceeds normally. No bootstrap action is required - the manifest is created lazily on first successful spawn when `skills/cache-manager/SKILL.md` Phase 4 fires. Unlike `.design/budget.json`, missing cache-manifest.json is the **correct** initial state on a fresh repo.
 
 ## Cross-references
 
 - `skills/cache-manager/SKILL.md` - producer; documents the four-phase contract.
-- `hooks/budget-enforcer.js` (Plan 10.1-01) - reader; short-circuits spawns on hit.
+- `hooks/budget-enforcer.ts` (Plan 10.1-01) - reader; short-circuits spawns on hit.
 - `.design/budget.json` - provides `cache_ttl_seconds` default.
 - `.design/telemetry/costs.jsonl` (Plan 10.1-05) - records `cache_hit: true` rows with zero tokens and zero cost when the short-circuit fires.
 - D-05, D-08, D-09 in `.planning/phases/10.1-optimization-layer-cost-governance/10.1-CONTEXT.md` - decision lineage.

package/reference/i18n.md

@@ -465,7 +465,7 @@ The auditor catches a missed 3.1.2 by scanning for untranslated quotes, proper n
 
 ## Verifier Integration Spec
 
-This section specifies two probes for [agents/design-verifier.md](../agents/design-verifier.md). 28-06 implements; this file owns the spec. Both probes attach to a new `### i18n probes` subsection at the end of Phase 1 - Re-Audit + Category Scoring (after the existing `### Category Scores` subsection), and both classify findings under the orthogonal lens-tag `i18n_readiness` (per D-03 / D-07 - no new pillar, no audit-format change).
+This section specifies two probes for [agents/design-verifier.md](../agents/design-verifier.md). The verifier agent implements; this file owns the spec. Both probes attach to a new `### i18n probes` subsection at the end of Stage 1 - Re-Audit + Category Scoring (after the existing `### Category Scores` subsection), and both classify findings under the orthogonal lens-tag `i18n_readiness` (no new pillar, no audit-format change).
 
 ### Probe 1: Hardcoded-string scan
 

package/reference/intel-schema.md

@@ -8,8 +8,11 @@ Path: `.design/intel/` (gitignored - runtime data only)
 The intel store is a set of flat JSON files (slices) that index the design surface.
 Each slice is an independent file. Agents read slices they need; the updater rewrites only changed slices.
 
-Slices are rebuilt by `scripts/build-intel.cjs` (full initial build) and kept current by the
-`gdd-intel-updater` agent (incremental updates triggered by file changes).
+Slices are rebuilt by `scripts/build-intel.cjs` (full initial build) and refreshed on-demand
+by the `gdd-intel-updater` agent (incremental updates when run by the user or a skill that
+spawns it). The store is **not auto-current**: it reflects the last invocation of build-intel
+or the updater. Skills that depend on fresh intel should invoke the updater first or treat
+slice timestamps as best-effort.
 
 ## Slice Definitions
 
@@ -244,6 +247,38 @@ Cross-reference graph: nodes are files, edges are dependency relationships from
 }
 ```
 
+---
+
+### agent-tiers.json
+
+Runtime-neutral tier index per agent; populated by `gdd-intel-updater` so downstream
+tooling reads tier information without re-parsing every agent's markdown frontmatter.
+Both the model-tier (`opus|sonnet|haiku`) and the equivalent runtime-neutral
+reasoning class (`high|medium|low`) are emitted side-by-side using the locked
+equivalence map (opus↔high, sonnet↔medium, haiku↔low).
+
+```json
+{
+  "generated": "<ISO-8601>",
+  "agents": [
+    {
+      "name": "design-planner",
+      "default_tier": "opus",
+      "reasoning_class": "high"
+    },
+    {
+      "name": "design-verifier-gate",
+      "default_tier": "haiku",
+      "reasoning_class": "low"
+    }
+  ]
+}
+```
+
+Consumers: router, budget enforcer, multi-runtime tier resolver.
+Validation: every agent in `agents/*.md` (except README.md) MUST appear exactly once.
+Written atomically (.tmp + rename) when the updater runs; absent on a fresh checkout.
+
 ## Incremental Update Rules
 
 1. On each run, compare current file `mtime` and `git_hash` against `files.json` entries.

package/reference/meta-rules.md

@@ -14,7 +14,7 @@ When the orchestrator's prompt contains a `<required_reading>` block, you MUST r
 
 Only write files declared in your frontmatter `writes:` list. Agents with `reads-only: true` must never call `Write` or `Edit` on any file. If the task appears to require writing outside your declared scope, stop and return a `<blocker>` in STATE.md rather than expanding your write surface.
 
-If your agent runs in a phase that enforces atomic commits (most do), commit only files in your declared `writes:` list. Use the repo commit convention: `docs(phase-N-P): short imperative description` for documentation-class changes, `feat(phase-N-P): ...` for new capability, `fix(phase-N-P): ...` for bug fixes. Phase and plan numbers come from `.design/STATE.md` `phase:` and the invoking plan's frontmatter.
+If your agent runs in a context that enforces atomic commits (most do), commit only files in your declared `writes:` list. Use the repo's conventional-commit convention: `feat(<scope>): ...` for new capability, `fix(<scope>): ...` for bug fixes, `docs(<scope>): ...` for documentation. The `<scope>` should match a recognisable subsystem in the downstream project (e.g. `feat(verify): ...`, `fix(planner): ...`); do not propagate any internal plugin-development numbering.
 
 ## Deviation Handling
 
@@ -43,7 +43,7 @@ The orchestrator detects failure by reading STATE.md for a `<blocker>`, not by t
 
 ## Context-Exhaustion & Budget Awareness
 
-A PostToolUse hook at `hooks/context-exhaustion.js` watches your tool output for the string `<context-exhaustion>` in your response. If you determine you cannot finish the task in the remaining context, emit:
+A PostToolUse hook at `hooks/context-exhaustion.ts` watches your tool output for the string `<context-exhaustion>` in your response. If you determine you cannot finish the task in the remaining context, emit:
 
 ```xml
 <context-exhaustion>
@@ -54,12 +54,12 @@ resume-hint: <one-sentence instruction for a resumption spawn>
 
 …before your completion marker. The hook captures this into STATE.md so the orchestrator can re-spawn you with a narrower scope. Do not guess when you're near exhaustion - only emit when a concrete obstacle (file too large to read, required diff too wide) forced the call.
 
-A PreToolUse hook at `hooks/budget-enforcer.js` intercepts every `Task` spawn (including the one that invoked you). The hook may:
+A PreToolUse hook at `hooks/budget-enforcer.ts` intercepts every `Task` spawn (including the one that invoked you). The hook may:
 - **Short-circuit** your spawn with a cached result from `.design/cache-manifest.json` (transparent - you never run).
 - **Downgrade** your tier to Haiku at the 80% per-task cap soft-threshold, silently (`auto_downgrade_on_cap: true` in `.design/budget.json`, D-03).
 - **Hard-block** your spawn at the 100% per-task or per-phase cap with an actionable error (D-02).
 
-Implication for you as the agent: **do not assume a specific model tier is live.** Your output must be correct whether you run on Haiku, Sonnet, or Opus. If a task genuinely requires reasoning density beyond Haiku, the `size_budget` + `default-tier` combination should have been set at authoring time so the router routes it correctly - the remedy is a frontmatter update (a Phase 11 reflector proposal), not a mid-run assumption.
+Implication for you as the agent: **do not assume a specific model tier is live.** Your output must be correct whether you run on Haiku, Sonnet, or Opus. If a task genuinely requires reasoning density beyond Haiku, the `size_budget` + `default-tier` combination should have been set at authoring time so the router routes it correctly - the remedy is a frontmatter update via the reflector loop, not a mid-run assumption.
 
 ---
 

package/reference/model-tiers.md

@@ -82,7 +82,7 @@ When the budget-enforcer hook resolves which tier to spawn an agent at, it walks
 
 1. **`.design/budget.json.tier_overrides[{agent_name}]`** - per-project configuration. Wins over frontmatter. Use this knob when the project has budget constraints that differ from the plugin defaults.
 2. **Agent frontmatter `default-tier`** (this file's per-agent map) - plugin default. Set at authoring time.
-3. **Hardcoded fallback `"sonnet"`** - belt-and-suspenders in `hooks/budget-enforcer.js` for agents that somehow lack the frontmatter field. Should never fire in practice after Phase 10.1.
+3. **Hardcoded fallback `"sonnet"`** - belt-and-suspenders in `hooks/budget-enforcer.ts` for agents that somehow lack the frontmatter field. Should never fire in practice after Phase 10.1.
 
 Plus two modifiers that can override the above at spawn time:
 
@@ -108,7 +108,7 @@ Phase 11's reflector encodes these heuristics. This section documents the philos
 
 ## Integration Points
 
-- **`hooks/budget-enforcer.js`** (Plan 10.1-01 Task 04) - implements the precedence chain above. `resolveTier(agent, agentDefaultTier, overrides)` is the concrete function.
+- **`hooks/budget-enforcer.ts`** (Plan 10.1-01 Task 04) - implements the precedence chain above. `resolveTier(agent, agentDefaultTier, overrides)` is the concrete function.
 - **`skills/router/SKILL.md`** (Plan 10.1-01 Task 03) - consults this file's tier map + `reference/model-prices.md` to produce `estimated_cost_usd` pre-spawn.
 - **`skills/optimize/SKILL.md`** (Plan 10.1-04) - advisory command; may suggest tier moves based on telemetry + this doc's heuristics.
 - **`agents/design-reflector.md`** (Phase 11, already merged) - may propose edits to this file + paired frontmatter updates. Proposals land in `.design/reflections/` for user review.