The numbering is the flow: decisions are 02, design is 03

papa-hq reads 01 research -> 03 decision -> 02 design. The order is a
scar, not a choice: 02-DESIGN existed from its initial commit, and when
adr/ was finally promoted on 2026-07-13 it took the next free number
rather than its place in the sequence. By then design was too settled to
renumber.

hal-hq was three commits old, so it is not. adr/ becomes 02-DECISIONS and
02-DESIGN becomes 03-DESIGN, and following the folder numbers now walks
the process in the order it happens: research produces a decision, the
decision authorises a design.

00-GENESIS becomes 00-META, matching papa's rename from the same
restructure.

Every path reference rewritten across documents, frontmatter, playbooks
and skills. All links resolve; all 58 frontmatter blocks parse and their
path fields still point at files that exist.

.claude/skills/hal-diagnose/SKILL.md

@@ -6,7 +6,7 @@ description: Use when investigating an open hal-hq issue — finding which compo
 # hal-diagnose
 
 Investigates an open issue to the point where its owner is known. **Authoritative playbook:**
-[`00-GENESIS/process/03-issues.md`](../../../00-GENESIS/process/03-issues.md).
+[`00-META/process/03-issues.md`](../../../00-META/process/03-issues.md).
 
 ## Before forming a hypothesis
 
@@ -28,7 +28,7 @@ result is not "nothing to learn" — it is the reason the next person repeats th
    what was ruled out and how. Archaeology — which commit, which pull request, which date a
    behaviour changed — is the most valuable content here.
 3. When the owner is known, set `status: located` and fill `located-in:` with repositories or
-   modules from [`00-GENESIS/repos.md`](../../../00-GENESIS/repos.md).
+   modules from [`00-META/repos.md`](../../../00-META/repos.md).
 4. On resolution: `status: resolved`, fill `fixed-by:`. If the root cause was a design gap, run
    `hal-graduate` for the amendment and fill `amended-design:`.