unikit-gd-verify

# Game Design — Consistency & Impact Verification Answer **"is the design consistent with itself?"** — a mechanical, deterministic check of every document against the facts registry, plus the **changed-scope impact** of a recent edit. This is the design-side mirror of `unikit-verify` and a CI-linter to `unikit-gd-review`'s senior reviewer: cheap, binary, run after every edit. A **verify conflict cannot be declined** (unlike a review finding) — it is resolved. **`unikit-gd-verify` is fully read-only — it writes nothing** (no report file, no changelog line, no `doc_status` bump, no `[gen]`-map re-render). It **detects and prints**; every fix is performed by `unikit-gd-apply` (the entailed deltas) or the owning zones (authoring + the `[gen]`-map re-render on their next write — **B1**: the writer of `GD-IDS` re-renders the affected maps). Conflicts are **precise, but their fix is not always predetermined**, so each is sorted into one of **four tracks** — **freshness** (print-only; the owner re-renders the `[gen]` map on its next write), **entailed → apply-ready** (a named fix — incl. a status/version header correction — handed to `unikit-gd-apply`), **direction interview** (the user picks *which* fix, never *whether*), and **authoring → owner / explore**. The apply-ready set hands off **in one move** — inline prose (verify writes **no** handoff file, unlike `unikit-gd-review`'s durable report), recommend-only. The handoff + interview run **only on a standalone `/unikit-gd-veri...