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.

04-ISSUES/001-failed-package-install-reports-success/00-report.md

@@ -31,14 +31,14 @@ exists to catch — a step that failed, reported success, and left the next step
 state that was never produced.
 
 It is also a direct violation of a decision already taken and recorded:
-[ADR 0008](../../adr/0008-a-failed-step-fails-the-job.md) says a step that fails must fail the
+[ADR 0008](../../02-DECISIONS/0008-a-failed-step-fails-the-job.md) says a step that fails must fail the
 job. That record notes the rule is applied instance by instance and enforced by no mechanism.
 This is an instance where it was never applied.
 
 ## Evidence
 
 - Observed 2026-08-22 while declaring the virtualisation package required by
-  [ADR 0016](../../adr/0016-a-lab-node-is-a-virtual-machine.md).
+  [ADR 0016](../../02-DECISIONS/0016-a-lab-node-is-a-virtual-machine.md).
 - A fix is written and open as a pull request, unmerged since 2026-08-20.
 
 ## Open questions