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

modules/umami/client.ts

@@ -1,5 +1,5 @@
 // The umami API client — moved here from the shared sdk, because it is umami's own code and
-// changes when umami's API does (novox/hq ADR 0044). Both this module's tools and its provisioner
+// changes when umami's API does (novox/hq ADR 0039). Both this module's tools and its provisioner
 // import it; nothing outside umami does.
 
 export interface Website {

modules/umami/provisioner/index.ts

@@ -1,11 +1,11 @@
 // umami's provisioner — the adapter that makes umami a provider of the mesh `analytics` interface.
 // The reconcile loop and the contributions file are the sdk harness's; this writes only the
-// per-service half: how umami creates and removes a tracked site (novox/hq ADR 0044/0045/0053).
+// per-service half: how umami creates and removes a tracked site (novox/hq ADR 0039/0040/0048).
 //
 // The `analytics` interface: a consumer contributes `{ domain }` (the site it wants tracked) and
 // receives `{ siteId, snippet, dashboard }`.
 //
-// **A note on scope (ADR 0053).** ADR 0053 corrects *credential* provisions: the mesh mints a secret
+// **A note on scope (ADR 0048).** ADR 0048 corrects *credential* provisions: the mesh mints a secret
 // and the provider creates a login with it. Analytics is not that shape — it mints no secret the
 // consumer authenticates with; what the consumer needs back is data umami *generates* (the siteId).
 // The credential-provisioner contract returns nothing, so the siteId does not travel back to the

modules/umami/tools/index.ts

@@ -1,4 +1,4 @@
-// umami's tools — moved here from the shared sdk (novox/hq ADR 0044). They import umami's own
+// umami's tools — moved here from the shared sdk (novox/hq ADR 0039). They import umami's own
 // client (../client) and plug into the mesh through the sdk's tool harness. Editing them rebuilds
 // umami and nothing else.