Retire the HAL name where it points forward

Skills take the hq- prefix: they are HQ process workflows, not mesh
workflows, and HQ is company-scoped now. hq-new-research, hq-graduate,
hq-new-issue, hq-diagnose, hq-amend-design, hq-handoff,
hq-sync-constitution, hq-status.

Forward-looking prose becomes Novox Mesh or simply the mesh — the root
README, AGENTS.md, the 00-META README, the mission's module example, and
one to-be document that addressed 'someone working on HAL'.

Three categories deliberately keep HAL, per ADR 0027:

The monorepo is still called hal on the forge. repos.md, every code: field
and every located-in: field name a repository that exists under that name,
and renaming them in prose would make them false.

The as-is layer and the research that measured it describe the system that
runs, and that system is called HAL. 124 modules, 9 daemons, a dead
containerised node — those are observations, not intentions.

Records 0001-0026 are immutable. A record says what was decided when it
was decided, and no record is edited for a name.

Also repoints ADR 0022's link at the renamed skill — a path fix, which the
immutability rule permits, not a change of meaning.

03-DESIGN/01-to-be/01-end-to-end-testing.md

@@ -138,7 +138,7 @@ has to suit both:
 | caller | wants |
 |---|---|
 | the coordinator | non-interactive, structured results it can record against a pipeline, a clean teardown, no prompts and no colour |
-| someone working on HAL | readable output, the failing mesh **left standing** to open a shell into, and a way to re-run one assertion without repeating the whole delivery |
+| someone working on the mesh | readable output, the failing mesh **left standing** to open a shell into, and a way to re-run one assertion without repeating the whole delivery |
 
 Hence at least two verbs: one that runs to a verdict and tears down, and one that stands a
 scenario up and leaves it there. The second is how a developer works *inside* a mesh —

03-DESIGN/README.md

@@ -38,7 +38,7 @@ Status changes when **implementation state** changes, never because design text
 `implemented` claim must be defensible from the owning repository's main branch, not from
 intent. If it cannot be checked, it is `in-progress`.
 
-Cross-cutting views are generated from this frontmatter by the `hal-status` skill and never
+Cross-cutting views are generated from this frontmatter by the `hq-status` skill and never
 written to disk.
 
 ## What belongs here