Resync hq ADR references 0044-0054 -> 0039-0049 after the hq record reconciliation

modules/unifi/client.ts

@@ -1,4 +1,4 @@
-// The UniFi controller API client — unifi's own code, living in the module (novox/hq ADR 0044).
+// The UniFi controller API client — unifi's own code, living in the module (novox/hq ADR 0039).
 // Moved out of the shared hal sdk, where a change to the UniFi API rebuilt everything; here it
 // rebuilds only unifi. This module's tools import it, and nothing outside unifi does.
 //
@@ -112,7 +112,7 @@ function uniFetch(url: string, init?: UniInit): Promise<UniReply> {
   });
 }
 
-/** The settings-merged config the mesh delivers (novox/hq ADR 0051): { url, username, password,
+/** The settings-merged config the mesh delivers (novox/hq ADR 0046): { url, username, password,
  *  site }. Read from MESH_UNIFI_CONFIG_FILE; absent or unreadable is an empty config, not a throw. */
 function meshConfig(file?: string): Record<string, string> {
   if (!file) return {};

modules/unifi/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@novox/module-unifi",
   "version": "0.1.0",
-  "description": "unifi — the UniFi network controller. Its API client and tools live here (novox/hq ADR 0044).",
+  "description": "unifi — the UniFi network controller. Its API client and tools live here (novox/hq ADR 0039).",
   "type": "module",
   "private": true,
   "dependencies": {

modules/unifi/tools/index.ts

@@ -1,4 +1,4 @@
-// unifi's tools — its own code (novox/hq ADR 0044), importing unifi's own client. They return
+// unifi's tools — its own code (novox/hq ADR 0039), importing unifi's own client. They return
 // structured data; the mesh serves them through the sdk's tool harness. unifi is tools-only (no
 // events entrypoint): the controller does not push lifecycle events the mesh consumes, so this
 // module reads its resources — port forwards, devices, clients — and exposes them, and stops there.