@onlineapps/mq-client-core 3.2.0 → 4.0.1

package/src/config/configSchema.js

@@ -387,22 +387,15 @@ module.exports = {
     },
 
     // ---------------------------------------------------------------------
-    // Which kind of service this client belongs to. `queueCreationFilter` and
-    // `queueCreationCallback` stood here until d.419: they were the two keys by
-    // which a client declared a queue nobody owns, and a queue now comes into
-    // being from a declaration or not at all
+    // `queueCreationFilter` and `queueCreationCallback` stood here until d.419,
+    // and `recoveryScope` — the permission they were filtered by — until d.514.
+    // They were how a client declared a queue nobody owns, and a queue now comes
+    // into being from a declaration or not at all
     // (`docs/governance/confirmations/mq-consumer-contract.md` 006). A config
-    // still carrying either is refused by name at construction — the schema is
-    // CLOSED, which is what makes the removal visible to the caller instead of
-    // silently ignored.
+    // still carrying any of the three is refused by name at construction — the
+    // schema is CLOSED, which is what makes the removal visible to the caller
+    // instead of silently ignored.
     // ---------------------------------------------------------------------
-    recoveryScope: {
-      type: 'string',
-      enum: ['infrastructure', 'business'],
-      description:
-        'Which kind of service this client belongs to. It decides nothing about queue '
-        + 'creation: no client declares a queue (workers/RecoveryWorker.js).',
-    },
   },
   required: ['type', 'host'], // Only type and host required
 

package/src/config/defaultConfig.js

@@ -186,11 +186,7 @@ module.exports = {
   criticalHealthShutdown: true,
   criticalHealthShutdownDelay: 60000,
 
-  // ---------------------------------------------------------------------
-  // Which kind of service this client belongs to. It decides nothing about queue
-  // creation: this client declares no queue at all, and the two callbacks that
-  // used to let it — `queueCreationFilter` and `queueCreationCallback` — left
-  // with that door (d.419, conf mq-consumer-contract 006).
-  // ---------------------------------------------------------------------
-  recoveryScope: 'infrastructure',
+  // `recoveryScope` stood here until d.514, with the two callbacks it filtered
+  // (`queueCreationFilter`, `queueCreationCallback`, d.419) one batch ahead of
+  // it. This client declares no queue at all, so there is no permission to give.
 };

package/src/config/queueConfig.js

@@ -648,7 +648,10 @@ module.exports = {
      * InfrastructureHealthTracker publishes service status changes
      * Message format includes event_type: 'service.registered' | 'service.validation.completed' | 
      *   'service.version.changed' | 'service.deregistered' | 'service.status.changed'
-     * NOTE: Heartbeats are NOT published here (too frequent, every 10s)
+     * NOTE: Heartbeats are NOT published here - they are too frequent. The cadence
+     *   is not a number this file owns: see the `heartbeatInterval` constructor option
+     *   of RegistryClient (@onlineapps/conn-orch-registry), which ServiceWrapper feeds
+     *   from BIZ_HEARTBEAT_INTERVAL_MS.
      * NOTE: Healthcheck messages go to infrastructure.health.events exchange
      */
     'services': {
@@ -715,6 +718,17 @@ module.exports = {
      * onward route — because the operator's dashboard matches `*.dlq` and a message
      * that expired there is a message nobody got to decide about (confirmation
      * `mq-consumer-contract` 002 point 2, 003 point 1).
+     *
+     * **A declaration is not a creation instruction. The terminal is brought into being
+     * by the owner of the prefix that NAMES it.** `initInfrastructureQueues()` derives
+     * the whole list from these sections only when its caller passes no `queues` list;
+     * every caller passes one, and the gateway's names exactly the five `workflow.*`
+     * queues it owns (`infra/api_gateway/index.js`). `monitoring.dlq` therefore belongs
+     * to the monitoring service's own call, beside the queues it consumes. Until that
+     * call names it, a `nack(requeue=false)` on a queue of this family dead-letters onto
+     * a routing key no queue carries and the broker DROPS the message — measured
+     * 2026-09-16 on the dev broker: 78 queues, and the only `.dlq` among them
+     * `workflow.dlq` and `delivery.dlq`.
      */
     dlq: {
       durable: true,
@@ -784,6 +798,10 @@ module.exports = {
      * `workflow.dlq`, `delivery.dlq` and `monitoring.dlq` — durable, capped at 50k, no
      * TTL, no onward route. A telemetry record the intake cannot process is the one an
      * operator most needs to look at, and a TTL here would delete it before they did.
+     *
+     * Brought into being by the owner of the `telemetry.` prefix, the same rule as
+     * `monitoring.dlq` above: declared here, created by the service whose
+     * `initInfrastructureQueues()` call names it.
      */
     dlq: {
       durable: true,
@@ -891,7 +909,9 @@ module.exports = {
      * CRITICAL: This is the ONLY queue used for service-to-Registry communication.
      * Registry listener processes different message types based on msg.type:
      * - type: 'register'   - Service registration requests (full spec + operations)
-     * - type: 'heartbeat'  - Periodic health check messages (sent every 10s)
+     * - type: 'heartbeat'  - Periodic health check messages (cadence owned by the
+     *   `heartbeatInterval` constructor option of RegistryClient,
+     *   @onlineapps/conn-orch-registry - not declared here)
      * - type: 'deregister' - Voluntary shutdown notice
      * (The legacy 'apiDescription' / 'apiDescriptionRequest' types are no
      *  longer supported — see operations-registry-contract.md §2.)