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

modules/registry/client.ts

@@ -1,4 +1,4 @@
-// The Docker Registry v2 client — registry's own code, living in the module (novox/hq ADR 0044).
+// The Docker Registry v2 client — registry's own code, living in the module (novox/hq ADR 0039).
 // Ported from the shared hal sdk, where a change to the registry API rebuilt everything; here it
 // rebuilds only registry. Both this module's tools and its events entrypoint import it.
 

modules/registry/index.ts

@@ -1,6 +1,6 @@
 // registry's events. The tool runtime imports this once the broker is bound.
 //
-// Emits (novox/hq ADR 0046/0047):
+// Emits (novox/hq ADR 0041/0042):
 //   module.registry.image.pushed   — a new image (repo:tag) was published to the registry
 //
 // This is a genuinely useful signal: a build finished and its image is now pullable, so anything

modules/registry/package.json

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

modules/registry/tools/index.ts

@@ -1,4 +1,4 @@
-// registry's tools — moved here from the shared sdk (novox/hq ADR 0044), importing registry's own
+// registry's tools — moved here from the shared sdk (novox/hq ADR 0039), importing registry's own
 // client. They return structured data; the mesh serves them through the sdk's tool harness.
 
 import { registerModuleTools, type ToolDefinition } from "@novox/mesh-sdk/tools";