docs(meta): repoint decisions/ paths to governance/ tree (pql migration)

Phase 1 follow-up: update the active instruction layer (CLAUDE.md, project
structure rule, DECISIONS.md redirect, agent personalities, skill docs) to
reference governance/{decisions,questions,rejected}/<domain>.md instead of the
retired flat decisions/*.md layout.

Path references only — command-surface references (tooling/db/decision*,
decisions-sync, Makefile targets, clerk) are repointed to the pql CLI in the
Phase 4 consumer cutover. Historical archives (docs/sprints, docs/discussions,
docs/workshops) keep their point-in-time decisions/ paths; the separate
whatsinagame/ template distribution is untouched. Agent-memory is gitignored
and out of scope.

The agent/skill repath was applied by tooling/pql-migrate/repath_references.py
(ordered, meaning-preserving replacements; bare-dir rule uses a negative
lookbehind so it can't corrupt a freshly-created governance/decisions/ path),
committed for provenance. CLAUDE.md, project-structure.md, and DECISIONS.md
were hand-edited (structural tree/table changes).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

CLAUDE.md

@@ -16,7 +16,7 @@ tests/                # Integration and end-to-end tests
 docs/                 # Architecture, design, briefings, workshops
 db/                   # Schema + seed data (connectors moved to tooling/db/)
 .claude/              # Agents, skills, rules
-decisions/            # Decision domain files (D-NNN confirmed, Q-NNN open, R-NNN rejected)
+governance/           # Decision records — decisions/ questions/ rejected/ per domain (pql DQR tree)
 ```
 
 Full annotated tree: `.claude/rules/project-structure.md`
@@ -82,7 +82,7 @@ The ticketing database (`settledreach.db`) is accessed via `SR_DB_PATH` env var
 1. Check active work: `tooling/db/ticket list --status in_progress`
 2. Check your ticket: `tooling/db/ticket show <id>`
 3. Check dependencies: `tooling/db/ticket deps <id>`
-4. Read relevant `decisions/*.md` domain file(s) referenced in the ticket
+4. Read relevant `governance/**/*.md` decision record(s) referenced in the ticket (`pql decisions show <id>`)
 5. Background context: `docs/briefings/{your-name}.md`, `docs/discussions/`
 
 ### CLI tools
@@ -127,7 +127,7 @@ The implant UI system — all diegetic neural overlay panels — lives at `clien
 `game_state.gd` (`character_visual_descriptor` field) and `sim_bridge.gd` (`harness` field) follow this pattern.
 
 ### File conventions
-- Decisions: domain files in `decisions/` (see `decisions/README.md` for index)
+- Decisions: records in `governance/{decisions,questions,rejected}/<domain>.md` (see `governance/README.md`; query via `pql decisions`)
 - Decision IDs: `D-NNN` (confirmed), `Q-NNN` (open questions), `R-NNN` (rejected)
 - **Claim IDs before writing:** `tooling/db/decision claim D <domain> "title"` — prevents ID collisions across parallel branches
 - Diagrams: `.d2` source + `.png` renders in `docs/diagrams/{category}/`. Create or update diagrams via `/d2-diagram` when D-records are added or modified.