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/005-pipeline-test-harness-unbuildable/00-report.md

@@ -29,13 +29,13 @@ coverage was assumed, not checked.
 ## Evidence
 
 - The workspace was removed by pull request #240 on 2026-06-04
-  ([ADR 0007](../../adr/0007-no-npm-workspace.md)).
+  ([ADR 0007](../../02-DECISIONS/0007-no-npm-workspace.md)).
 - The harness has not built since that date.
 - Recorded in the knowledge base as a standing entry, not as a fixed incident.
 
 ## Relationship to the lab
 
-[`02-DESIGN/01-to-be/01-end-to-end-testing.md`](../../02-DESIGN/01-to-be/01-end-to-end-testing.md)
+[`03-DESIGN/01-to-be/01-end-to-end-testing.md`](../../03-DESIGN/01-to-be/01-end-to-end-testing.md)
 designs end-to-end testing on a lab mesh, which would replace this harness rather than repair
 it. That is a reason to decide its fate deliberately, not a reason to leave it broken and
 unmentioned: until the lab exists, this is the coverage the pipeline is presumed to have.