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

modules/nextcloud/client.ts

@@ -1,4 +1,4 @@
-// Nextcloud's client — nextcloud's own code, living in the module (novox/hq ADR 0044). Both this
+// Nextcloud's client — nextcloud's own code, living in the module (novox/hq ADR 0039). Both this
 // module's tools and its events entrypoint import it, and nothing outside nextcloud does.
 //
 // Nextcloud is administered two ways, and this client speaks both:
@@ -25,7 +25,7 @@ export interface NextcloudShare {
   owner: string;
 }
 
-/** The settings-merged config the mesh delivers (novox/hq ADR 0051): { url, apiKey, token, password, user, ... }. */
+/** The settings-merged config the mesh delivers (novox/hq ADR 0046): { url, apiKey, token, password, user, ... }. */
 function meshConfig(file?: string): Record<string, string> {
   if (!file) return {};
   try { return JSON.parse(readFileSync(file, "utf8")) as Record<string, string>; }

modules/nextcloud/index.ts

@@ -1,7 +1,7 @@
 // nextcloud's events. The tool runtime imports this once the broker is bound. It watches the user
 // list and the share list and announces new arrivals.
 //
-// Emits (novox/hq ADR 0046/0047):
+// Emits (novox/hq ADR 0041/0042):
 //   module.nextcloud.user.created    — a user account appeared (occ user:list)
 //   module.nextcloud.share.created   — a share appeared (OCS shares)
 //

modules/nextcloud/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@novox/module-nextcloud",
   "version": "0.1.0",
-  "description": "nextcloud — file sync and share. Its client, tools and events live here (novox/hq ADR 0044).",
+  "description": "nextcloud — file sync and share. Its client, tools and events live here (novox/hq ADR 0039).",
   "type": "module",
   "private": true,
   "dependencies": {

modules/nextcloud/tools/index.ts

@@ -1,4 +1,4 @@
-// nextcloud's tools — importing nextcloud's own client (novox/hq ADR 0044). occ runs inside the
+// nextcloud's tools — importing nextcloud's own client (novox/hq ADR 0039). occ runs inside the
 // container; shares come over OCS. They return structured data; the mesh serves them through the
 // sdk's tool harness.