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.

AGENTS.md

@@ -1,15 +1,15 @@
 # Agent instructions — Novox HQ
 
-This repository is the source of truth for the HAL mesh's mission, research, design and
-decisions. Implementation lives in the code repositories (see
+This repository is the source of truth for Novox's mission, research, design and decisions —
+today almost entirely those of **Novox Mesh**, its first product ([ADR 0028](02-DECISIONS/0028-hq-is-company-scoped.md)). Implementation lives in the code repositories (see
 [`00-META/repos.md`](00-META/repos.md)).
 
 Before changing anything here, read the playbooks in
 [`00-META/process/`](00-META/process/) — every workflow (research, graduation, design
 amendment, issues, build handoff, constitution sync) is documented there, and agents operate
 through them. Thin skills in `.claude/skills/` wrap these playbooks for invocation
-(`hal-new-research`, `hal-graduate`, `hal-new-issue`, `hal-diagnose`, `hal-amend-design`,
-`hal-handoff`, `hal-sync-constitution`, `hal-status`); each defers to its playbook as
+(`hq-new-research`, `hq-graduate`, `hq-new-issue`, `hq-diagnose`, `hq-amend-design`,
+`hq-handoff`, `hq-sync-constitution`, `hq-status`); each defers to its playbook as
 authoritative and adds only the mechanical scaffolding.
 
 ## Ground rules