@hegemonart/get-design-done 1.31.5 → 1.33.0

package/skills/router/router-pick-emitter.md

@@ -0,0 +1,78 @@
+# gdd-router — router_pick emitter (Phase 32-08 / D-02)
+
+Co-located reference for `skills/router/SKILL.md` — split out per the Phase 28.5
+contract (router SKILL ≤100 lines) and the Phase 28.6 co-location pattern (same
+convention as the sibling `./capability-gap-emitter.md`).
+
+## When to emit
+
+When the router resolves an intent to a concrete pick — i.e. it has selected the
+`path` / `complexity_class` / `resolved_models` decision and is about to return
+its decision JSON — emit ONE `router_pick` event recording WHICH skill/agent it
+auto-picked. Emit exactly once per resolved pick, as the LAST step before
+returning the decision JSON to the caller.
+
+This is the D-02 router_pick instrument: GDD routes by description-match but has
+no record of what the router actually reaches for, so there is no data on
+under-reached skills. Phase 33 reads these events from the chain file
+(`.design/gep/events.jsonl`) to baseline per-skill auto-pick rates (the
+"pick-rate regression" expansion in the ROADMAP).
+
+`router_pick` is NOT `capability_gap`: emit `router_pick` when the router DID
+resolve a pick; emit `capability_gap` (see `./capability-gap-emitter.md`) only
+when it could not resolve the intent at all. They are disjoint surfaces.
+
+## Synchronous emitter snippet
+
+Builds the 7-field `RouterPickPayload` and writes it via `appendChainEvent`.
+The intent is hashed — the raw prompt is NEVER stored (no PII). `picked_skill`,
+`rank`, and `alternatives` come from the router's resolved decision:
+
+```bash
+node -e '
+const { appendChainEvent } = require("./scripts/lib/event-chain.cjs");
+const { createHash, randomUUID } = require("node:crypto");
+const intent = process.env.GDD_INTENT || "";
+const payload = {
+  event_id: randomUUID(),
+  source: "router",
+  picked_skill: process.env.GDD_PICKED_SKILL || "",
+  context_hash: createHash("sha256").update(intent).digest("hex"),
+  rank: Number(process.env.GDD_PICK_RANK || 0),
+  alternatives: (process.env.GDD_ALTERNATIVES || "").split(",").filter(Boolean),
+  ts: new Date().toISOString(),
+};
+appendChainEvent({
+  agent: "router",
+  outcome: "router_pick",
+  payload,
+  type: "router_pick",
+  timestamp: new Date().toISOString(),
+  sessionId: process.env.GDD_SESSION_ID || "router-cli",
+});
+'
+```
+
+`GDD_PICKED_SKILL` is the resolved pick; `GDD_PICK_RANK` is its rank among
+candidates (0 = top pick); `GDD_ALTERNATIVES` is a comma-separated list of the
+OTHER candidate skill/agent names the router considered (names only — no scores,
+no prompt text). `GDD_INTENT` is hashed in-process and is never written to disk.
+
+## Notes
+
+- **No PII**: only `context_hash` (sha256 of the intent) is stored — never the
+  raw prompt or intent string. The `RouterPickPayload` is
+  `additionalProperties: false`, so a stray `raw_prompt` field would be rejected
+  by `events.schema.json` validation. This mirrors `capability_gap`'s hash
+  discipline.
+- **Router output JSON contract is UNCHANGED** — `router_pick` is a SIDE EFFECT,
+  not a new output field. Back-compat is preserved exactly as the existing
+  `## Output schema versioning` table in `SKILL.md` guarantees; the emitter runs
+  AFTER the decision is computed and does not alter the returned blob.
+- The 7-field payload flows through `appendChainEvent`'s opaque-extras pattern
+  verbatim; the chain row carries `type`, `timestamp`, `sessionId`, `payload` as
+  opaque extras and is projected back to the events-schema envelope by Phase 33
+  aggregation (same projection the capability_gap aggregation uses).
+- Validated against the additive `RouterPickPayload` branch (allOf[2]) in
+  `reference/schemas/events.schema.json` — see
+  `test/suite/router-pick-event.test.cjs`.

package/skills/using-gdd/SKILL.md

@@ -0,0 +1,78 @@
+---
+name: using-gdd
+description: "Use when starting any GDD session — establishes how to find and apply GDD skills."
+disable-model-invocation: true
+---
+<SUBAGENT-STOP>
+
+# Using GDD
+
+This is the bootstrap discipline contract for every Get Design Done session. Read it
+first; it tells you how to find and apply the right GDD skill before you act.
+
+## The 1% rule
+
+**If you think there is even a 1% chance a skill might apply, you ABSOLUTELY MUST invoke the skill.**
+
+In GDD, almost every request maps to a pipeline stage — brief, explore, plan, design,
+verify — or to a cross-cutting skill (discuss, audit, style, darkmode). When in doubt,
+search for and read the skill's body. The cost of reading a skill is trivial; the cost of
+free-handing a stage is rework, scope creep, and a broken pipeline state.
+
+## Red flags — Thought → Reality
+
+When you catch yourself thinking any of the following, STOP and check for a skill.
+
+| Thought | Reality |
+| --- | --- |
+| This is just a simple design question. | Questions are tasks. Check for a skill. |
+| I'll just tweak the CSS directly. | Token changes go through the pipeline — check /gdd:design. |
+| I already know the codebase, skip explore. | Explore probes connections you haven't re-checked this cycle. |
+| This change is too small to plan. | Plan-skipped tasks blow scope per cycle telemetry. Run /gdd:plan. |
+| I can write the brief later. | No brief means no shared problem statement — /gdd:brief comes first. |
+| The user clearly wants X, I'll skip discuss. | Ambiguity hides here. /gdd:discuss surfaces the real constraint. |
+| I'll verify by eyeballing it. | Verification is a stage with criteria — run /gdd:verify, don't guess. |
+| It's obviously a dark-mode tweak. | Color-scheme work has its own skill — check /gdd:darkmode. |
+| Let me just compare these two designs quickly. | Comparison is an audit task — /gdd:compare has the rubric. |
+| This is a one-off, no skill needed. | "One-off" is the most common rationalization in the telemetry. Check anyway. |
+| I'll refactor the style tokens by hand. | /gdd:style owns token edits so the pipeline stays consistent. |
+| The audit can wait until after I ship. | An un-audited cycle is an unverified cycle — /gdd:audit before close. |
+
+## Skill priority order
+
+When more than one skill could apply, resolve in this order:
+
+1. **Process** — brief / explore / discuss. Establish the problem and context first.
+2. **Implementation** — design / style / darkmode. Only after process is settled.
+3. **Audit** — verify / compare / audit. Close the loop before declaring done.
+
+Never run an Implementation skill before the Process skills that gate it have produced
+their artifact. Never declare a cycle complete without an Audit skill.
+
+## Instruction priority
+
+When instructions conflict, obey this precedence (highest first):
+
+1. **The user's CLAUDE.md** — project- and user-level directives always win.
+2. **GDD skills** — the skill body is the source of truth for how a stage runs.
+3. **Defaults** — your own general training and habits come last.
+
+If a GDD skill contradicts the user's CLAUDE.md, the CLAUDE.md wins and you flag the
+conflict. If your instinct contradicts a GDD skill, the skill wins.
+
+## GDD pipeline flow
+
+The core flow is **Brief → Explore → Plan → Design → Verify**, with branch points:
+
+- **Brief** captures the problem (`/gdd:brief`). Branch: a rough idea can sketch or spike
+  off the brief before exploration; a changed problem loops back via `--re-brief`.
+- **Explore** scans the codebase and connections (`/gdd:explore`) — even on a familiar
+  repo, because connections drift each cycle.
+- **Plan** decomposes work into tasks (`/gdd:plan`). Skipping it is the top cause of scope
+  blow-up; small tasks still get a plan.
+- **Design** implements (`/gdd:design`, with `/gdd:style` and `/gdd:darkmode` as
+  implementation peers). Implementation never runs ahead of an approved plan.
+- **Verify** checks against criteria (`/gdd:verify`), then `/gdd:audit` / `/gdd:compare`
+  close the loop. On pass the cycle completes; on fail it loops back to the failing stage.
+
+`/gdd:discuss` runs alongside any stage to resolve ambiguity before it propagates.

package/skills/verify/SKILL.md

@@ -93,4 +93,21 @@ Full prompts + branching: `./verify-procedure.md` §Step 3.
 
 Print the `=== Verify complete ===` summary (status, gap counts, agent paths, next-step suggestion) from `./verify-procedure.md` §After Completion.
 
+<HARD-GATE>
+Do NOT mark the cycle complete until the user has reviewed `.design/DESIGN-VERIFICATION.md`. 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
+
+The reasons an agent gives to skip or weaken verification, and what each one lets through:
+
+| Thought | Reality |
+|---------|---------|
+| "The implementation looks right, I can skip the verifier spawn." | Skipping verification ships unchecked must-haves; the 5-phase verifier exists to catch what "looks right" misses. |
+| "The integration-checker is redundant with the auditor." | The auditor scores quality; the integration-checker proves each D-XX is actually wired — an orphaned decision passes the audit but fails the product. |
+| "These gaps are minor, I'll accept-as-is without a blocker." | Accept-as-is without recording the unresolved gaps erases the trail; the next cycle re-discovers them from scratch. |
+| "The quality gate timed out, I'll treat that as a pass." | Timeout is a signal, not a pass — masking it lets a genuinely failing gate slip through to ship. |
+| "I'll loop the fixer a fourth time to clear the last gap." | The 3-iteration cap exists because a gap surviving three fixes is a design problem, not a code problem — save and escalate. |
+| "Post-handoff bundles don't need the faithfulness check." | Skipping the handoff-faithfulness section means a divergence from the source design ships unflagged. |
+
 ## VERIFY COMPLETE

package/scripts/lib/cli/index.ts

@@ -1,29 +0,0 @@
-// scripts/lib/cli/index.ts — GDD-DEPRECATION-SHIM (Plan 31-5-06, SDK-05, D-02).
-//
-// Thin deprecation shim. The real implementation moved to sdk/cli/index.ts
-// in Plan 31-5-04 (SDK consolidation). This file is re-created at the OLD
-// path so undocumented EXTERNAL importers (anyone who reached into
-// node_modules/@hegemonart/get-design-done/scripts/lib/cli/index.ts directly)
-// keep working for one minor grace window.
-//
-// REMOVED IN v1.33.0 (D-02). Grace window: 1.31.5 ships with shims →
-// 1.32.0 still has them → 1.33.0 removes them. Internal callers already use
-// the sdk/ path (Plan 31-5-04/05) — this shim is external-only; 31-5-10's
-// no-stale-internal-refs guard excludes files carrying the
-// GDD-DEPRECATION-SHIM marker above.
-//
-// Runs under --experimental-strip-types (the runtime `bin/gdd-sdk` and the
-// test suite both use it), so `export *` re-export is strip-types-clean.
-
-import { emitWarning } from 'node:process';
-
-let warned = false;
-if (!warned) {
-  warned = true;
-  emitWarning(
-    'scripts/lib/cli/index.ts is deprecated; import sdk/cli instead. Removed in v1.33.0.',
-    'DeprecationWarning',
-  );
-}
-
-export * from '../../../sdk/cli/index.ts';

package/scripts/lib/error-classifier.cjs

@@ -1,29 +0,0 @@
-'use strict';
-// scripts/lib/error-classifier.cjs — GDD-DEPRECATION-SHIM (Plan 31-5-06, SDK-05, D-02).
-//
-// Thin deprecation shim. The real implementation moved to
-// sdk/primitives/error-classifier.cjs in Plan 31-5-04 (SDK consolidation).
-// This file is re-created at the OLD path so undocumented EXTERNAL importers
-// (anyone who reached into node_modules/@hegemonart/get-design-done/scripts/
-// lib/error-classifier.cjs directly) keep working for one minor grace window.
-//
-// REMOVED IN v1.33.0 (D-02). Grace window: 1.31.5 ships with shims →
-// 1.32.0 still has them → 1.33.0 removes them. Internal callers already use
-// the sdk/ path (Plan 31-5-04/05) — this shim is external-only and 31-5-10's
-// no-stale-internal-refs guard excludes files carrying the GDD-DEPRECATION-SHIM
-// marker above.
-//
-// Emits a DeprecationWarning exactly ONCE per process: the module-level
-// `warned` flag plus Node's module cache (this file is evaluated once per
-// process regardless of how many times it is required).
-
-let warned = false;
-if (!warned) {
-  warned = true;
-  process.emitWarning(
-    'scripts/lib/error-classifier.cjs is deprecated; import sdk/primitives/error-classifier instead. Removed in v1.33.0.',
-    'DeprecationWarning',
-  );
-}
-
-module.exports = require('../../sdk/primitives/error-classifier.cjs');

package/scripts/lib/event-stream/index.ts

@@ -1,29 +0,0 @@
-// scripts/lib/event-stream/index.ts — GDD-DEPRECATION-SHIM (Plan 31-5-06, SDK-05, D-02).
-//
-// Thin deprecation shim. The real implementation moved to
-// sdk/event-stream/index.ts in Plan 31-5-04 (SDK consolidation). This file
-// is re-created at the OLD path so undocumented EXTERNAL importers (anyone
-// who reached into node_modules/@hegemonart/get-design-done/scripts/lib/
-// event-stream/index.ts directly) keep working for one minor grace window.
-//
-// REMOVED IN v1.33.0 (D-02). Grace window: 1.31.5 ships with shims →
-// 1.32.0 still has them → 1.33.0 removes them. Internal callers already use
-// the sdk/ path (Plan 31-5-04/05) — this shim is external-only; 31-5-10's
-// no-stale-internal-refs guard excludes files carrying the
-// GDD-DEPRECATION-SHIM marker above.
-//
-// Runs under --experimental-strip-types, so `export *` re-export is
-// strip-types-clean.
-
-import { emitWarning } from 'node:process';
-
-let warned = false;
-if (!warned) {
-  warned = true;
-  emitWarning(
-    'scripts/lib/event-stream/index.ts is deprecated; import sdk/event-stream instead. Removed in v1.33.0.',
-    'DeprecationWarning',
-  );
-}
-
-export * from '../../../sdk/event-stream/index.ts';

package/scripts/lib/gdd-errors/index.ts

@@ -1,29 +0,0 @@
-// scripts/lib/gdd-errors/index.ts — GDD-DEPRECATION-SHIM (Plan 31-5-06, SDK-05, D-02).
-//
-// Thin deprecation shim. The real implementation moved to sdk/errors/index.ts
-// in Plan 31-5-04 (SDK consolidation). This file is re-created at the OLD
-// path so undocumented EXTERNAL importers (anyone who reached into
-// node_modules/@hegemonart/get-design-done/scripts/lib/gdd-errors/index.ts
-// directly) keep working for one minor grace window.
-//
-// REMOVED IN v1.33.0 (D-02). Grace window: 1.31.5 ships with shims →
-// 1.32.0 still has them → 1.33.0 removes them. Internal callers already use
-// the sdk/ path (Plan 31-5-04/05) — this shim is external-only; 31-5-10's
-// no-stale-internal-refs guard excludes files carrying the
-// GDD-DEPRECATION-SHIM marker above.
-//
-// Runs under --experimental-strip-types, so `export *` re-export is
-// strip-types-clean.
-
-import { emitWarning } from 'node:process';
-
-let warned = false;
-if (!warned) {
-  warned = true;
-  emitWarning(
-    'scripts/lib/gdd-errors/index.ts is deprecated; import sdk/errors instead. Removed in v1.33.0.',
-    'DeprecationWarning',
-  );
-}
-
-export * from '../../../sdk/errors/index.ts';

package/scripts/lib/gdd-state/index.ts

@@ -1,29 +0,0 @@
-// scripts/lib/gdd-state/index.ts — GDD-DEPRECATION-SHIM (Plan 31-5-06, SDK-05, D-02).
-//
-// Thin deprecation shim. The real implementation moved to sdk/state/index.ts
-// in Plan 31-5-04 (SDK consolidation). This file is re-created at the OLD
-// path so undocumented EXTERNAL importers (anyone who reached into
-// node_modules/@hegemonart/get-design-done/scripts/lib/gdd-state/index.ts
-// directly) keep working for one minor grace window.
-//
-// REMOVED IN v1.33.0 (D-02). Grace window: 1.31.5 ships with shims →
-// 1.32.0 still has them → 1.33.0 removes them. Internal callers already use
-// the sdk/ path (Plan 31-5-04/05) — this shim is external-only; 31-5-10's
-// no-stale-internal-refs guard excludes files carrying the
-// GDD-DEPRECATION-SHIM marker above.
-//
-// Runs under --experimental-strip-types, so `export *` re-export is
-// strip-types-clean.
-
-import { emitWarning } from 'node:process';
-
-let warned = false;
-if (!warned) {
-  warned = true;
-  emitWarning(
-    'scripts/lib/gdd-state/index.ts is deprecated; import sdk/state instead. Removed in v1.33.0.',
-    'DeprecationWarning',
-  );
-}
-
-export * from '../../../sdk/state/index.ts';

package/scripts/lib/iteration-budget.cjs

@@ -1,29 +0,0 @@
-'use strict';
-// scripts/lib/iteration-budget.cjs — GDD-DEPRECATION-SHIM (Plan 31-5-06, SDK-05, D-02).
-//
-// Thin deprecation shim. The real implementation moved to
-// sdk/primitives/iteration-budget.cjs in Plan 31-5-04 (SDK consolidation).
-// This file is re-created at the OLD path so undocumented EXTERNAL importers
-// (anyone who reached into node_modules/@hegemonart/get-design-done/scripts/
-// lib/iteration-budget.cjs directly) keep working for one minor grace window.
-//
-// REMOVED IN v1.33.0 (D-02). Grace window: 1.31.5 ships with shims →
-// 1.32.0 still has them → 1.33.0 removes them. Internal callers already use
-// the sdk/ path (Plan 31-5-04/05) — this shim is external-only and 31-5-10's
-// no-stale-internal-refs guard excludes files carrying the GDD-DEPRECATION-SHIM
-// marker above.
-//
-// Emits a DeprecationWarning exactly ONCE per process: the module-level
-// `warned` flag plus Node's module cache (this file is evaluated once per
-// process regardless of how many times it is required).
-
-let warned = false;
-if (!warned) {
-  warned = true;
-  process.emitWarning(
-    'scripts/lib/iteration-budget.cjs is deprecated; import sdk/primitives/iteration-budget instead. Removed in v1.33.0.',
-    'DeprecationWarning',
-  );
-}
-
-module.exports = require('../../sdk/primitives/iteration-budget.cjs');

package/scripts/lib/jittered-backoff.cjs

@@ -1,29 +0,0 @@
-'use strict';
-// scripts/lib/jittered-backoff.cjs — GDD-DEPRECATION-SHIM (Plan 31-5-06, SDK-05, D-02).
-//
-// Thin deprecation shim. The real implementation moved to
-// sdk/primitives/jittered-backoff.cjs in Plan 31-5-04 (SDK consolidation).
-// This file is re-created at the OLD path so undocumented EXTERNAL importers
-// (anyone who reached into node_modules/@hegemonart/get-design-done/scripts/
-// lib/jittered-backoff.cjs directly) keep working for one minor grace window.
-//
-// REMOVED IN v1.33.0 (D-02). Grace window: 1.31.5 ships with shims →
-// 1.32.0 still has them → 1.33.0 removes them. Internal callers already use
-// the sdk/ path (Plan 31-5-04/05) — this shim is external-only and 31-5-10's
-// no-stale-internal-refs guard excludes files carrying the GDD-DEPRECATION-SHIM
-// marker above.
-//
-// Emits a DeprecationWarning exactly ONCE per process: the module-level
-// `warned` flag plus Node's module cache (this file is evaluated once per
-// process regardless of how many times it is required).
-
-let warned = false;
-if (!warned) {
-  warned = true;
-  process.emitWarning(
-    'scripts/lib/jittered-backoff.cjs is deprecated; import sdk/primitives/jittered-backoff instead. Removed in v1.33.0.',
-    'DeprecationWarning',
-  );
-}
-
-module.exports = require('../../sdk/primitives/jittered-backoff.cjs');

package/scripts/lib/lockfile.cjs

@@ -1,29 +0,0 @@
-'use strict';
-// scripts/lib/lockfile.cjs — GDD-DEPRECATION-SHIM (Plan 31-5-06, SDK-05, D-02).
-//
-// Thin deprecation shim. The real implementation moved to
-// sdk/primitives/lockfile.cjs in Plan 31-5-04 (SDK consolidation).
-// This file is re-created at the OLD path so undocumented EXTERNAL importers
-// (anyone who reached into node_modules/@hegemonart/get-design-done/scripts/
-// lib/lockfile.cjs directly) keep working for one minor grace window.
-//
-// REMOVED IN v1.33.0 (D-02). Grace window: 1.31.5 ships with shims →
-// 1.32.0 still has them → 1.33.0 removes them. Internal callers already use
-// the sdk/ path (Plan 31-5-04/05) — this shim is external-only and 31-5-10's
-// no-stale-internal-refs guard excludes files carrying the GDD-DEPRECATION-SHIM
-// marker above.
-//
-// Emits a DeprecationWarning exactly ONCE per process: the module-level
-// `warned` flag plus Node's module cache (this file is evaluated once per
-// process regardless of how many times it is required).
-
-let warned = false;
-if (!warned) {
-  warned = true;
-  process.emitWarning(
-    'scripts/lib/lockfile.cjs is deprecated; import sdk/primitives/lockfile instead. Removed in v1.33.0.',
-    'DeprecationWarning',
-  );
-}
-
-module.exports = require('../../sdk/primitives/lockfile.cjs');

package/scripts/mcp-servers/gdd-mcp/server.ts

@@ -1,35 +0,0 @@
-// scripts/mcp-servers/gdd-mcp/server.ts — GDD-DEPRECATION-SHIM (Plan 31-5-06, SDK-05, D-02).
-//
-// Thin deprecation shim. The real MCP `gdd-mcp` server moved to
-// sdk/mcp/gdd-mcp/server.ts in Plan 31-5-05 (SDK consolidation, D-08). This
-// file is re-created at the OLD path so undocumented EXTERNAL importers /
-// invokers (anyone who reached into node_modules/@hegemonart/get-design-done/
-// scripts/mcp-servers/gdd-mcp/server.ts directly) keep working for one minor
-// grace window.
-//
-// REMOVED IN v1.33.0 (D-02). Grace window: 1.31.5 ships with shims →
-// 1.32.0 still has them → 1.33.0 removes them. The canonical invocation is
-// now the `bin/gdd-mcp` trampoline (Plan 31-5-05); internal callers already
-// use the sdk/ path. This shim is external-only; 31-5-10's
-// no-stale-internal-refs guard excludes files carrying the
-// GDD-DEPRECATION-SHIM marker above.
-//
-// Re-exporting the sdk/ server keeps the library surface (buildServer,
-// runStdio, SERVER_NAME, SERVER_VERSION, TOOL_DESCRIPTIONS, TOOL_READONLY)
-// reachable via the old path. The sdk/ server's own isMain() entry guard
-// keys off process.argv[1] ending with its own sdk/ path, so a re-export
-// does NOT auto-start the server — direct execution should go through the
-// bin trampoline. Runs under --experimental-strip-types.
-
-import { emitWarning } from 'node:process';
-
-let warned = false;
-if (!warned) {
-  warned = true;
-  emitWarning(
-    'scripts/mcp-servers/gdd-mcp/server.ts is deprecated; use the bin/gdd-mcp trampoline or import sdk/mcp/gdd-mcp instead. Removed in v1.33.0.',
-    'DeprecationWarning',
-  );
-}
-
-export * from '../../../sdk/mcp/gdd-mcp/server.ts';

package/scripts/mcp-servers/gdd-state/server.ts

@@ -1,34 +0,0 @@
-// scripts/mcp-servers/gdd-state/server.ts — GDD-DEPRECATION-SHIM (Plan 31-5-06, SDK-05, D-02).
-//
-// Thin deprecation shim. The real MCP `gdd-state` server moved to
-// sdk/mcp/gdd-state/server.ts in Plan 31-5-04 (SDK consolidation). This file
-// is re-created at the OLD path so undocumented EXTERNAL importers / invokers
-// (anyone who reached into node_modules/@hegemonart/get-design-done/scripts/
-// mcp-servers/gdd-state/server.ts directly) keep working for one minor grace
-// window.
-//
-// REMOVED IN v1.33.0 (D-02). Grace window: 1.31.5 ships with shims →
-// 1.32.0 still has them → 1.33.0 removes them. The canonical invocation is
-// now the `bin/gdd-state-mcp` trampoline (Plan 31-5-05); internal callers
-// already use the sdk/ path. This shim is external-only; 31-5-10's
-// no-stale-internal-refs guard excludes files carrying the
-// GDD-DEPRECATION-SHIM marker above.
-//
-// Re-exporting the sdk/ server keeps the library surface (buildServer,
-// runStdio) reachable via the old path. The sdk/ server's own isMain()
-// entry guard keys off process.argv[1] ending with its own sdk/ path, so a
-// re-export does NOT auto-start the server — direct execution should go
-// through the bin trampoline. Runs under --experimental-strip-types.
-
-import { emitWarning } from 'node:process';
-
-let warned = false;
-if (!warned) {
-  warned = true;
-  emitWarning(
-    'scripts/mcp-servers/gdd-state/server.ts is deprecated; use the bin/gdd-state-mcp trampoline or import sdk/mcp/gdd-state instead. Removed in v1.33.0.',
-    'DeprecationWarning',
-  );
-}
-
-export * from '../../../sdk/mcp/gdd-state/server.ts';