Remove two disclosures, and record Nox as the answer to 006

Found by a full scan before making the repository public, which is the
moment the public rule stops being aspirational.

A module name identified a specific laptop model — hardware inventory,
which is operational detail about one installation rather than a lesson
that travels. Generalised.

ADR 0028 named a forge username in a repository path, which the public
rule forbids, and the sentence had also gone stale: the repository it
described was subsequently verified empty of anything unique and removed.
Rewritten to state what happened without the username. Removing a
disclosure from a record is the same class as fixing a path — the rule
that permits it outranks the one that forbids editing.

Issue 006 gains its proposed direction: Nox works from within this
repository rather than these documents being synced into the knowledge
base. Better on three counts — no copy, so no drift; no fourth knowledge
system, which was the original objection; always current.

But it changes the promise, and the issue says so. ADR 0019 promised these
documents would surface BESIDE everything else in a symptom search. An
agent that must be asked is reachable, not surfacing, and the two differ
in precisely the case the operational memory exists for — someone
debugging an error with no reason to suspect HQ knows anything about it.
The question narrows to whether a symptom search finds this content
without the searcher already suspecting it.

02-DECISIONS/0028-hq-is-company-scoped.md

@@ -75,9 +75,9 @@ is the ceremony option 2 was rejected for.
   trigger ([ADR 0025](0025-hq-is-the-source-of-the-constitution.md)): the moment something
   outside the mesh must be governed by the same rules, product-level content moves down a level
   and this repository becomes what its name already claims.
-- A new repository was created rather than the old one transferred — the forge predates the
-  transfer API. `jschoubben/hq` is left in place untouched; it is not the source of truth and
-  nothing points at it.
+- A new repository was created rather than the old one transferred, because the forge predates
+  the transfer API. The original was verified to contain nothing the new one lacks — every ref
+  an ancestor, no tags, issues, pull requests, releases or wiki content — and then removed.
 - The mesh's own documents now live one conceptual level below the repository they are in. A
   reader arriving at `01-RESEARCH` should understand it as the mesh's research, not Novox's.
   Nothing in the folder names says so, and that is the cost of not restructuring.