@onlineapps/mq-client-core 4.2.0 → 5.0.0

package/src/transports/rabbitmqClient.js

@@ -7,14 +7,22 @@
  */
 
 const amqp = require('amqplib');
+// amqplib's own class for "this handle is in a terminal state". It is what
+// `close()` on a closed connection and `createChannel()` on one answer with, and it
+// is read instead of the sentence those answers carry (d.696).
+const { IllegalOperationError } = require('amqplib');
 const EventEmitter = require('events');
 const {
+  AMQP_NOT_FOUND,
+  AMQP_PRECONDITION_FAILED,
   TransientPublishError,
   PermanentPublishError,
   QueueNotFoundError,
   classifyPublishError,
+  collateralCloseMessage,
   missingInfrastructureQueueMessage,
   missingQueueDefinitionMessage,
+  refusedSendMessage,
 } = require('../utils/publishErrors');
 const {
   ConnectionError,
@@ -28,7 +36,6 @@ const {
 } = require('../utils/errorHandler');
 const { assertLogger } = require('@onlineapps/logger-contract');
 const PublishLayer = require('../layers/PublishLayer');
-const RecoveryWorker = require('../workers/RecoveryWorker');
 const PublishMonitor = require('../monitoring/PublishMonitor');
 const runtimeCfg = require('../config');
 const defaultConfig = require('../config/defaultConfig');
@@ -278,6 +285,10 @@ class RabbitMQClient extends EventEmitter {
     this._channel = null; // ConfirmChannel for publish operations
     this._queueChannel = null; // Regular channel for queue operations (assertQueue, checkQueue)
     this._consumerChannel = null; // Dedicated channel for consume operations
+    // A SECOND ConfirmChannel, for the client's own telemetry (d.724). It is created on
+    // the first telemetry publish and never before: a client that publishes no telemetry
+    // must not hold a channel for it. See `_ensurePublisherChannel()` § roles.
+    this._telemetryChannel = null;
     
     // Track active consumers for re-registration after channel recreation
     this._activeConsumers = new Map(); // queue -> { handler, options, consumerTag }
@@ -413,16 +424,6 @@ class RabbitMQClient extends EventEmitter {
       },
     });
 
-    // Recovery worker — connection recovery, and the report of a queue that does
-    // not exist. It creates none: queue creation left it with the two callbacks
-    // that fed it (d.419) and with `recoveryScope`, the permission they were
-    // filtered by (d.514). Which rule the report names is decided by the
-    // ownership class in the error, not by who built this client.
-    this._recoveryWorker = new RecoveryWorker({
-      client: this,
-      logger: this._logger,
-    });
-
     // Publish monitor (metriky) — counts only, reports through return values,
     // takes no logger (see PublishMonitor's header).
     this._publishMonitor = new PublishMonitor();
@@ -456,16 +457,12 @@ class RabbitMQClient extends EventEmitter {
       this._publishMonitor.trackBuffered();
     });
 
-    // Recovery worker - handle QueueNotFoundError via error event
-    this.on('error', async (err) => {
-      if (err instanceof QueueNotFoundError) {
-        try {
-          await this._recoveryWorker.handleQueueNotFound(err, { queue: err.queueName });
-        } catch (recoveryErr) {
-          // Recovery failed - error already thrown
-        }
-      }
-    });
+    // A missing queue is answered ONCE, by the refusal of the publish (d.971): the
+    // caller gets `PublishError` with the `QueueNotFoundError` as its `cause`, which
+    // names the queue, its ownership class and the Fix. Until d.971 a second worker
+    // listened on this client's `error` channel for the same verdict and repeated it
+    // into the log; d.419 had taken its only other job (creating the queue) and
+    // d.811b its input.
   }
 
   /**
@@ -483,8 +480,14 @@ class RabbitMQClient extends EventEmitter {
   }
 
   /**
-   * Get current channel state
-   * @returns {Object} Channel state information
+   * The state of every channel this client holds — the keys ARE the list:
+   * `publisher`, `queue`, `consumer` and `telemetry` (the client's own events,
+   * d.724), each as `{ exists, closed, ready }`. The telemetry channel opens on the
+   * first telemetry publish and not before; until then it reads the way any channel
+   * not yet opened reads, `{ exists: false, closed: true, ready: false }`. It was
+   * missing from this report until d.1007.
+   *
+   * @returns {{publisher: Object, queue: Object, consumer: Object, telemetry: Object}}
    */
   getChannelState() {
     return {
@@ -502,6 +505,11 @@ class RabbitMQClient extends EventEmitter {
         exists: !!this._consumerChannel,
         closed: !this._isChannelAlive(this._consumerChannel),
         ready: this._isChannelAlive(this._consumerChannel)
+      },
+      telemetry: {
+        exists: !!this._telemetryChannel,
+        closed: !this._isChannelAlive(this._telemetryChannel),
+        ready: this._isChannelAlive(this._telemetryChannel)
       }
     };
   }
@@ -524,6 +532,32 @@ class RabbitMQClient extends EventEmitter {
     return !!channel && channel._alive === true;
   }
 
+  /**
+   * Did this failure to open a channel only report the connection going away?
+   *
+   * THE rule for "a refused channel open is transient" (d.1000, d.1003, d.1003b, d.1003c)
+   * — one body, read by `_ensurePublisherChannel()` and by the consumer and queue
+   * channels' close handlers. Two carriers, neither of them a sentence:
+   *
+   *   - amqplib's CLASS: on a closing or closed connection `createChannel()` /
+   *     `createConfirmChannel()` answer `IllegalOperationError` (`'Connection closing'`,
+   *     `'Connection closed (…)'`), no `code` — measured on amqplib 0.10.9 over a live
+   *     broker (d.1000);
+   *   - this client's STATE: a connection that dies WHILE the channel opens rejects the
+   *     pending RPC with a bare `Error('Channel ended, no reply will be forthcoming')`,
+   *     no class, no code — but by then the connection has already emitted `'close'`
+   *     and `_onConnectionDied()` has dropped `_connectionAlive`, the one liveness
+   *     source (measured over a live broker, d.1003: 8 of 12 broker-side closes during
+   *     the open).
+   *
+   * @param {*} amqpError - the error amqplib answered the open with
+   * @returns {boolean}
+   * @private
+   */
+  _connectionIsGoingAway(amqpError) {
+    return amqpError instanceof IllegalOperationError || !this._connectionAlive;
+  }
+
   /**
    * THE definition of "this client's consumer is attached to that queue".
    *
@@ -549,6 +583,37 @@ class RabbitMQClient extends EventEmitter {
     return typeof consumerInfo?.consumerTag === 'string' && consumerInfo.consumerTag !== '';
   }
 
+  /**
+   * The tracked queues whose consumer is NOT attached (`_isConsumerAttached()`), in
+   * tracking order — what a recreate summary names (d.1003d).
+   *
+   * @returns {string[]}
+   * @private
+   */
+  _unattachedConsumerQueues() {
+    const unattached = [];
+    for (const [queue, consumerInfo] of this._activeConsumers.entries()) {
+      if (!this._isConsumerAttached(consumerInfo)) {
+        unattached.push(queue);
+      }
+    }
+    return unattached;
+  }
+
+  /**
+   * `_ensureConsumerChannel()`'s answer for a channel that is already alive: every
+   * tracked consumer is counted by whether it is ATTACHED, not assumed re-registered
+   * (d.1003d). `failed` is a tracked consumer without an attachment — the state a
+   * refused re-registration leaves (d.262 keeps it tracked, d.386b drops its tag).
+   *
+   * @returns {{reRegistered: number, failed: number}}
+   * @private
+   */
+  _consumerAttachmentCounts() {
+    const failed = this._unattachedConsumerQueues().length;
+    return { reRegistered: this._activeConsumers.size - failed, failed };
+  }
+
   /**
    * Get current consumer state.
    *
@@ -575,17 +640,32 @@ class RabbitMQClient extends EventEmitter {
   }
 
   /**
-   * Get current buffer state
-   * @returns {Object} Buffer state information
+   * Get current buffer state.
+   *
+   * ONE buffer, read ONCE. `MessageBuffer.size()` IS `_inMemory.size()`
+   * (`buffer/MessageBuffer.js`), so both numbers describe the same messages and
+   * both come from the same call.
+   *
+   * Until d.645 the second one came off `_buffer._inMemory?.size() || 0`, and
+   * neither operator could do anything but hide: the `?.` cannot fire, because
+   * `MessageBuffer`'s constructor always builds `_inMemory` and the line above
+   * already calls `_buffer.size()` without a guard — a buffer that is not there
+   * has thrown before this expression runs. What the pair DID produce, for a
+   * buffer whose internals were not the assumed ones, was `inMemory: 0` beside a
+   * non-zero `size`: "held, but nowhere", a state no real buffer can be in,
+   * reported without a word and indistinguishable from an empty buffer for
+   * whoever reads it (`architecture-principles.md` §3 No Fallbacks, §8 Explicit
+   * Over Implicit; `automation-gates.md` §5).
+   *
+   * @returns {{size: number, inMemory: number}} How many messages are held
    */
   getBufferState() {
-    return {
-      size: this._publishLayer._buffer.size(),
-      // No `persistent` count. There is one buffer, so a second number could
-      // only ever be 0 — a field that reports a mechanism that does not exist
-      // (d.343, `automation-gates.md` §5).
-      inMemory: this._publishLayer._buffer._inMemory?.size() || 0
-    };
+    // No `persistent` count. There is one buffer, so a second number could
+    // only ever be 0 — a field that reports a mechanism that does not exist
+    // (d.343, `automation-gates.md` §5).
+    const held = this._publishLayer._buffer.size();
+
+    return { size: held, inMemory: held };
   }
 
   /**
@@ -648,11 +728,31 @@ class RabbitMQClient extends EventEmitter {
    * @private
    */
   _connectionSocketOptions() {
-    const connectionName =
-      this._config.connectionName ||
-      this._config.clientName ||
-      `oa-client:${runtimeCfg.get('serviceName')}:${process.pid}`;
-    return { clientProperties: { connection_name: connectionName } };
+    const explicit = this._config.connectionName || this._config.clientName;
+
+    if (explicit) {
+      return { clientProperties: { connection_name: explicit } };
+    }
+
+    // Composed from THIS CLIENT'S OWN config, not from the runtime config (d.770). The
+    // name is the caller's fact and the constructor already resolved it — asking the
+    // runtime config here was a second reader of it, and the one that answered the
+    // fabricated module default `oa-service` when the caller had named itself properly.
+    if (typeof this._config.serviceName !== 'string' || this._config.serviceName === '') {
+      throw new ValidationError(
+        '[RabbitMQClient] Missing configuration - the connection has no name and no '
+          + 'serviceName to compose one from. '
+          + 'Expected: connectionName, clientName or serviceName in this client\'s config '
+          + '(BaseClient resolves serviceName from the explicit key or ENV SERVICE_NAME). '
+          + 'Fix: pass serviceName to the client, or set SERVICE_NAME in env-active/*.env.'
+      );
+    }
+
+    return {
+      clientProperties: {
+        connection_name: `oa-client:${this._config.serviceName}:${process.pid}`
+      }
+    };
   }
 
   /**
@@ -670,8 +770,17 @@ class RabbitMQClient extends EventEmitter {
    * @private
    */
   _attachConnectionHandlers(connection) {
+    // A fault is RECORDED on the connection, the way `_attach*ChannelHandlers()` has
+    // recorded a channel's since d.264 — and for the same reason (d.696). Once a
+    // connection is closed, amqplib answers every operation on it with the same
+    // `IllegalOperationError`, whether it got there by our `close()` or by a broker
+    // fault; the only difference is a sentence it composes (`Connection.toClosed()`, `lib/connection.js`).
+    // Which of the two happened is this client's own knowledge, so it is kept as state
+    // rather than read back out of a message (`error-handling.md` §6).
+    connection._closeError = null;
     connection.on('error', (err) => {
       this._connectionAlive = false;
+      connection._closeError = err;
       this._logger.error('[RabbitMQClient] Connection error:', err.message);
       this.emit('error', err);
     });
@@ -732,6 +841,15 @@ class RabbitMQClient extends EventEmitter {
   _isBrokerRefusal(err) {
     if (!err) return false;
     if (REFUSAL_REPLY_CODES.includes(err.code)) return true;
+    // THE ONE TEXT READING THIS FILE KEEPS, and it is kept because amqplib leaves nothing
+    // else. A refused HANDSHAKE is the carrier: measured 2026-09-20 against the dev broker
+    // with a wrong password, amqplib answers `connect()` with a plain `Error` whose own
+    // properties are `stack` and `message` — NO `code`, no class of its own — and whose
+    // sentence is `'Handshake terminated by server: 403 (ACCESS-REFUSED) with message …'`.
+    // The branch above cannot see it, so without this one a refused login would read as a
+    // transient connection fault and the client would retry credentials that can never
+    // work. Do not "finish the d.677 work" by deleting it: measure first, and if amqplib
+    // ever puts a code on that error, the branch above already covers it (d.696).
     const message = typeof err.message === 'string' ? err.message : '';
     return REFUSAL_REPLY_CODES.some((code) => message.includes(`server: ${code} (`));
   }
@@ -1273,6 +1391,7 @@ class RabbitMQClient extends EventEmitter {
   _onConnectionDied() {
     this._connectionAlive = false;
     this._channel = null;
+    this._telemetryChannel = null;
     this._queueChannel = null;
     this._consumerChannel = null;
     this._connection = null;
@@ -1416,6 +1535,38 @@ class RabbitMQClient extends EventEmitter {
     }
   }
 
+  /**
+   * Helper to set a trackable interval — the SAME evidence, the other kind of timer.
+   *
+   * A repeating timer is the one that most needs to be in it: `_setTimeout()` deletes its
+   * handle when it fires, an interval never fires last, so nothing ever removes it by
+   * itself. Until d.759e the two repeating timers this client arms — the health monitor
+   * and the prefetch monitor — were armed with the bare global, so `_activeTimers` could
+   * not see them and `_clearAllTimers()` could not end them. Measured (d.759d): a client
+   * that had consumed held a live `setInterval(10000)` which only `disconnect()` could
+   * end; a unit suite that left four behind never let its runner exit, while
+   * `expect(client._activeTimers.size).toBe(0)` — the assertion five suites of this
+   * package read — stayed green throughout.
+   *
+   * @private
+   */
+  _setInterval(callback, ms) {
+    const timer = setInterval(callback, ms);
+    this._activeTimers.add(timer);
+    return timer;
+  }
+
+  /**
+   * Helper to clear a trackable interval
+   * @private
+   */
+  _clearInterval(timer) {
+    if (timer) {
+      clearInterval(timer);
+      this._activeTimers.delete(timer);
+    }
+  }
+
   /**
    * Race an `amqp.connect()` handshake against its `connectTimeout`, and own the
    * handshake the timeout abandons.
@@ -1482,9 +1633,21 @@ class RabbitMQClient extends EventEmitter {
 
   /**
    * Clear all active timers
+   *
+   * The repeating ones go through their own owners first, because each of them holds a
+   * REFERENCE that has to be dropped together with the handle: a sweep that ended the
+   * timer and left `_healthCheckInterval` / `_prefetchCheckTimer` pointing at the dead
+   * handle would make the next `_start*Monitoring()` return early ("already started") and
+   * monitoring would be off for the rest of the client's life, silently. The rest is a
+   * plain sweep — `clearTimeout()` ends an interval handle as well (measured on this
+   * runtime: a `setInterval` cleared with `clearTimeout` never ticks and reports
+   * `_destroyed`), so one loop covers both kinds.
+   *
    * @private
    */
   _clearAllTimers() {
+    this._stopHealthMonitoring();
+    this._stopPrefetchMonitoring();
     for (const timer of this._activeTimers) {
       clearTimeout(timer);
     }
@@ -1544,7 +1707,7 @@ class RabbitMQClient extends EventEmitter {
       this._channel._type = 'publisher';
       
       // Attach event handlers
-      this._attachPublisherChannelHandlers(this._channel);
+      this._attachPublisherChannelHandlers(this._channel, 'publisher');
       
       // Create a separate regular channel for queue operations (assertQueue, checkQueue)
       // This avoids RPC reply queue issues with ConfirmChannel.assertQueue()
@@ -1609,7 +1772,11 @@ class RabbitMQClient extends EventEmitter {
       throw err;
     } finally {
       if (connectTimeoutTimer) {
-        clearTimeout(connectTimeoutTimer);
+        // Through the evidence, like every other ending of this timer: a bare
+        // `clearTimeout()` here left the handle in `_activeTimers`, so after a FAILED
+        // connect the client reported one armed timer it no longer had (měřeno d.759e:
+        // size 1 with nothing armed).
+        this._clearTimeout(connectTimeoutTimer);
         connectTimeoutTimer = null;
       }
     }
@@ -1727,13 +1894,49 @@ class RabbitMQClient extends EventEmitter {
   }
 
   /**
-   * Ensure publisher channel exists and is open
-   * Auto-recreates if closed
+   * The ConfirmChannel of one ROLE, open — recreated when the last one died.
+   *
+   * TWO ROLES, TWO CHANNELS (d.724):
+   *
+   *  - `'publisher'` — the caller's messages. `this._channel`, created at connect time
+   *    with everything else.
+   *  - `'telemetry'` — the client's OWN events, the ones nobody asked it to send
+   *    (`src/monitoring-publish.js`, reached through `BaseClient.publishTelemetry()`).
+   *    `this._telemetryChannel`, created on the first such publish and not before.
+   *
+   * WHY THEY MAY NOT SHARE ONE (measured d.711, 3 of 7 runs of an unrelated suite red):
+   * a channel dies of the FIRST refusal it meets, and takes every unconfirmed publish on
+   * it along. The client's dead-letter telemetry publishes through
+   * `monitoring.workflow.fanout`; in a vhost where that exchange is not declared the
+   * broker answers `404` and closes the channel — and the caller's business message,
+   * still waiting for its confirm on the same channel, died with it. d.723 stopped that
+   * from being reported as the business message's own refusal; this separation stops it
+   * from happening at all. The module that sends the telemetry states the rule it could
+   * not keep on its own: "Fail-safe about PUBLISHING" (`src/monitoring-publish.js`
+   * § Principles) — fail-safe for the event is worth nothing if it is not also fail-safe
+   * for everything beside it.
+   *
+   * IT IS A CONFIRM CHANNEL, NOT A PLAIN ONE, because the telemetry's answer to its
+   * caller is `true`/`false`, and only a confirm can tell those apart: on a plain channel
+   * `publish()` returns as soon as the bytes are written, so every event would be
+   * reported as sent — including the ones the broker refuses, which is exactly the case
+   * this separation exists for.
+   *
+   * @param {'publisher'|'telemetry'} [role] - Whose channel to ensure.
    * @private
    * @returns {Promise<void>}
    */
-  async _ensurePublisherChannel() {
-    if (this._isChannelAlive(this._channel)) {
+  async _ensurePublisherChannel(role = 'publisher') {
+    if (role !== 'publisher' && role !== 'telemetry') {
+      throw new Error(
+        '[RabbitMQClient] Unknown send channel role - '
+          + `Expected: 'publisher' (the caller's messages) or 'telemetry' (the client's own events), `
+          + `got ${JSON.stringify(role)}. `
+          + 'Fix: publish through publish() or publishTelemetry(); nothing else picks a channel.'
+      );
+    }
+
+    if (this._isChannelAlive(this._sendChannelOf(role))) {
       return; // Channel is good
     }
 
@@ -1748,7 +1951,7 @@ class RabbitMQClient extends EventEmitter {
         await this._waitForReconnection();
 
         // After reconnection, try again
-        if (this._isChannelAlive(this._channel)) {
+        if (this._isChannelAlive(this._sendChannelOf(role))) {
           return; // Channel was recreated during reconnection
         }
         // If still no channel, connection might have failed - check again
@@ -1776,26 +1979,47 @@ class RabbitMQClient extends EventEmitter {
     
     try {
       // Create new ConfirmChannel
-      this._channel = await this._connection.createConfirmChannel();
-      
+      const channel = await this._connection.createConfirmChannel();
+
       // Track channel metadata for debugging
-      this._channel._createdAt = new Date().toISOString();
-      this._channel._closeReason = null;
-      this._channel._lastOperation = 'Recreated via _ensurePublisherChannel()';
-      this._channel._type = 'publisher';
-      
+      channel._createdAt = new Date().toISOString();
+      channel._closeReason = null;
+      channel._lastOperation = `Recreated via _ensurePublisherChannel('${role}')`;
+      channel._type = role;
+
+      this._setSendChannelOf(role, channel);
+
       // Attach event handlers
-      this._attachPublisherChannelHandlers(this._channel);
-      
-      this._logger.info('[RabbitMQClient] [mq-client-core] ✓ Publisher channel recreated');
+      this._attachPublisherChannelHandlers(channel, role);
+
+      this._logger.info(`[RabbitMQClient] [mq-client-core] ✓ ${role} channel recreated`);
     } catch (err) {
-      this._channel = null;
+      this._setSendChannelOf(role, null);
 
       const msg = err && err.message ? err.message : String(err);
 
-      // Pokud se connection právě zavírá, považujeme to za přechodný stav – explicitně vyhodíme
-      // TransientPublishError, aby vyšší vrstva (retry / worker) věděla, že má počkat na reconnect.
-      if (msg.includes('Connection closing') || msg.includes('Connection closed')) {
+      // Spojení odchází — rozhoduje TŘÍDA amqplibu, ne věta (d.1000, poslední textová
+      // větev po d.676–d.711). Změřeno nad amqplib 0.10.9 a živým brokerem:
+      // `createConfirmChannel()` nad spojením, jehož `close()` začalo, odpoví
+      // `IllegalOperationError('Connection closing')`, nad zavřeným
+      // `IllegalOperationError('Connection closed (…)')` — bez `code`, jiný nosič
+      // nemá (`lib/connection.js` `invalidateSend()` / `toClosed()`). Uvnitř
+      // `createConfirmChannel()` tu třídu nevydá nic jiného než odcházející spojení
+      // (`'Channel closed'` nového kanálu jen přes spojení, které zavírá své kanály).
+      //
+      // Druhý nosič je STAV (d.1003): spadne-li spojení UPROSTŘED otevírání,
+      // amqplib odmítne čekající RPC holým `Error('Channel ended, no reply will be
+      // forthcoming')` (`_rejectPending()`, `lib/channel.js`) — bez třídy, bez `code`.
+      // Změřeno nad živým brokerem: zavření brokerem (management API) během
+      // `createConfirmChannel()` 8× z 12, `close()` o `setImmediate` později 3× ze 3;
+      // pokaždé spojení UŽ ohlásilo `'close'`, takže `_onConnectionDied()` shodil
+      // `_connectionAlive` — jediný zdroj živosti (d.260) — dřív, než sem odmítnutí
+      // doběhlo. Věta nerozhoduje: táž věta nad živým spojením zůstává trvalá.
+      //
+      // Stav je přechodný: PublishLayer publikaci podrží a zopakuje po reconnectu.
+      // Pravidlo má jedno tělo, `_connectionIsGoingAway()` — čte ho i obnova
+      // consumer kanálu (d.1003b).
+      if (this._connectionIsGoingAway(err)) {
         this._logger.warn(
           `[RabbitMQClient] [mq-client-core] Failed to recreate publisher channel (connection closing): ${msg}`
         );
@@ -1809,7 +2033,7 @@ class RabbitMQClient extends EventEmitter {
 
       // Ostatní chyby považujeme za permanentní problém na úrovni kanálu/spojení.
       throw new PermanentPublishError(
-        `[RabbitMQClient] Failed to recreate publisher channel: ${msg} - `
+        `[RabbitMQClient] Failed to recreate ${role} channel: ${msg} - `
           + 'Expected: createConfirmChannel() to succeed on an open connection. '
           + 'Fix: read error.cause for the broker reason; a channel-level refusal here is not retried, so the connection must be re-established.',
         err
@@ -1870,12 +2094,16 @@ class RabbitMQClient extends EventEmitter {
    * Ensure consumer channel exists and is open
    * Auto-recreates and re-registers all consumers if closed
    * @private
-   * @returns {Promise<{reRegistered: number, failed: number}>} - Number of consumers re-registered and failed
+   * @returns {Promise<{reRegistered: number, failed: number}>} - how many tracked
+   *   consumers are attached, and how many are tracked without being attached. On a
+   *   channel that was already alive both are MEASURED (`_consumerAttachmentCounts()`,
+   *   d.1003d), never assumed: until d.1003d this branch answered
+   *   `_activeConsumers.size` as re-registered, counting a consumer whose
+   *   re-registration the broker had refused (tracked, no tag — d.262, d.386b).
    */
   async _ensureConsumerChannel() {
     if (this._isChannelAlive(this._consumerChannel)) {
-      // Channel is good - return current consumer state
-      return { reRegistered: this._activeConsumers.size, failed: 0 };
+      return this._consumerAttachmentCounts();
     }
 
     if (!this._connectionAlive) {
@@ -1898,8 +2126,9 @@ class RabbitMQClient extends EventEmitter {
       }
 
       if (this._isChannelAlive(this._consumerChannel)) {
-        // The recovery recreated it and re-registered what was tracked.
-        return { reRegistered: this._activeConsumers.size, failed: 0 };
+        // The recovery recreated it and ran the re-registration; what it attached is
+        // measured, not assumed (d.1003d).
+        return this._consumerAttachmentCounts();
       }
       if (!this._connectionAlive) {
         return { reRegistered: 0, failed: this._activeConsumers.size };
@@ -1921,8 +2150,20 @@ class RabbitMQClient extends EventEmitter {
       
       // Re-register all active consumers
       const { reRegistered, failed } = await this._reRegisterConsumers();
-      
-      this._logger.info(`[RabbitMQClient] [mq-client-core] ✓ Consumer channel recreated (re-registered: ${reRegistered}, failed: ${failed})`);
+
+      // A recreate that left a consumer unattached is not a success line (d.1003d):
+      // the ✓ at INFO read as "all good" while a queue had nobody reading it. The
+      // refusal itself is already an ERROR per queue (`_reRegisterConsumer()`); this
+      // summary names which queues are left without a consumer.
+      if (failed > 0) {
+        const unattached = this._unattachedConsumerQueues();
+        this._logger.warn(
+          `[RabbitMQClient] [mq-client-core] Consumer channel recreated, but ${unattached.length} consumer(s) are not attached: `
+            + `${unattached.join(', ')} (re-registered: ${reRegistered}, failed: ${failed})`
+        );
+      } else {
+        this._logger.info(`[RabbitMQClient] [mq-client-core] ✓ Consumer channel recreated (re-registered: ${reRegistered}, failed: ${failed})`);
+      }
       return { reRegistered, failed };
     } catch (err) {
       this._consumerChannel = null;
@@ -2128,7 +2369,7 @@ class RabbitMQClient extends EventEmitter {
       return; // Already started
     }
     
-    this._healthCheckInterval = setInterval(async () => {
+    this._healthCheckInterval = this._setInterval(async () => {
       try {
         await this._performHealthCheck();
       } catch (err) {
@@ -2147,7 +2388,7 @@ class RabbitMQClient extends EventEmitter {
    */
   _stopHealthMonitoring() {
     if (this._healthCheckInterval) {
-      clearInterval(this._healthCheckInterval);
+      this._clearInterval(this._healthCheckInterval);
       this._healthCheckInterval = null;
       this._logger.info('[RabbitMQClient] [mq-client-core] Health monitoring stopped');
     }
@@ -2287,7 +2528,7 @@ class RabbitMQClient extends EventEmitter {
             health.issues.push(`Queue ${queue} does not exist`);
           }
         } catch (err) {
-          if (err.code === 404) {
+          if (err.code === AMQP_NOT_FOUND) {
             health.queues.missing.push(queue);
             health.healthy = false;
             health.issues.push(`Queue ${queue} does not exist (404)`);
@@ -2465,6 +2706,23 @@ class RabbitMQClient extends EventEmitter {
     }
     socketUnanswered = socketUnanswered || queueOutcome.status === 'unanswered';
 
+    // The telemetry channel exists only when this client published telemetry (d.724);
+    // `_closeWithinTeardownBudget()` takes `null` as "nothing to close", so the client
+    // that never sent an event pays nothing for this line.
+    const telemetryOutcome = await this._closeWithinTeardownBudget(
+      'telemetry channel',
+      this._telemetryChannel,
+      remaining()
+    );
+    this._telemetryChannel = null;
+    if (telemetryOutcome.status === 'refused') {
+      // Reported, never raised: the client's own events are not the caller's business,
+      // and a telemetry channel that would not close is not a reason to fail a disconnect
+      // the caller asked for.
+      this._logger.warn('[RabbitMQClient] Error closing telemetry channel:', telemetryOutcome.error.message);
+    }
+    socketUnanswered = socketUnanswered || telemetryOutcome.status === 'unanswered';
+
     const publisherOutcome = await this._closeWithinTeardownBudget(
       'publisher channel',
       this._channel,
@@ -2483,9 +2741,14 @@ class RabbitMQClient extends EventEmitter {
     );
     this._connection = null;
     if (connectionOutcome.status === 'refused') {
-      // Don't emit error for expected connection closure during disconnect
-      // This is a predictable, intentional closure
-      if (connectionOutcome.error.message && connectionOutcome.error.message.includes('Connection closed (by client)')) {
+      // An EXPECTED refusal is two facts, and both are first-hand (d.696): amqplib
+      // answered with its terminal-state class — the connection was already closed — and
+      // this client recorded no fault on it, so what closed it was a `close()`. A fault
+      // recorded here means the connection died on its own and the refusal is worth
+      // raising, exactly as it was while this read the sentence `'Connection closed (by
+      // client)'` (amqplib composes that in `toClosed()`, `lib/connection.js`, and a
+      // fault gets `'Connection closed (<the error>)'` instead).
+      if (connectionOutcome.error instanceof IllegalOperationError && !connection._closeError) {
         this._logger.info('[RabbitMQClient] Connection closed during disconnect (expected)');
       } else {
         this.emit('error', connectionOutcome.error);
@@ -2512,7 +2775,7 @@ class RabbitMQClient extends EventEmitter {
    *
    * PUBLIC: this is the one operation a collaborator needs in order to declare a
    * queue on this client — higher-level routing libraries (cookbook-router's
-   * QueueManager) and `workers/RecoveryWorker.js` alike. It owns the whole
+   * QueueManager) alike. It owns the whole
    * sequence, so nobody has to assemble it out of private members: ensure the
    * queue channel, refuse a channel that is not alive, resolve the arguments
    * from the central `queueConfig`, declare.
@@ -2729,6 +2992,322 @@ class RabbitMQClient extends EventEmitter {
     );
   }
 
+  /**
+   * The broker's REFUSAL of this send, when that is what killed the channel — or `null`
+   * when the channel died without the broker saying anything about this message.
+   *
+   * A send the broker refuses closes the channel with a numbered close frame. amqplib
+   * puts that object on the channel's `error` event (`lib/channel.js`, `Channel.accept()`, case `ChannelClose`) and
+   * answers the publish callback with the bare `new Error('channel closed')`
+   * (the `Channel` constructor's `'close'` listener, `lib/channel.js`) — so the callback cannot see the reason, but the channel can:
+   * `_attachPublisherChannelHandlers()` records it as `channel._closeError`, and does so
+   * BEFORE the callback runs, because amqplib emits `error` first and only then `close`,
+   * which is what rejects the unconfirmed publishes.
+   *
+   * WHOSE ANSWER IT IS, THOUGH, IS A SECOND QUESTION (d.723). A ConfirmChannel carries
+   * more than one unconfirmed publish, and a numbered frame is an answer about exactly
+   * ONE of them; amqplib answers all of them with that same object. Until d.723 this
+   * method's own JSDoc called the reading "a fact about THIS send, first-hand" — it is
+   * that only while this send is the only unconfirmed one on the channel. Measured
+   * 2026-09-20, two publishes on one channel in a vhost of its own: one to an exchange
+   * nobody declared, one to a `good.fanout` the same client had just declared. Both came
+   * back `PermanentPublishError … Cannot publish to exchange "good.fanout": 404 NOT-FOUND
+   * - nothing declares it`, while the frame underneath named `no exchange
+   * 'no.such.exchange'`. A message the broker never refused was dropped, and its
+   * publisher was sent to declare an exchange that was already there.
+   *
+   * So `_closeFrameNamesThisSend()` decides attribution before the class is decided at
+   * all, and the sends it cannot claim get the collateral verdict
+   * (`_collateralSendTransient()`), which is transient: they were never answered, so they
+   * were never refused, and republishing them is right.
+   *
+   * So the reading is a fact about the send the frame is about:
+   *   - a NUMBER is an answer about this request. Measured against the dev broker,
+   *     `classId 60 / methodId 40` — `basic.publish` itself: `403 ACCESS-REFUSED` (an
+   *     account without `write` in the vhost) and `406 PRECONDITION-FAILED` (a `user_id`
+   *     property that is not the authenticated user). Repeating the request repeats the
+   *     answer, so it is PERMANENT — the same reading the queue-existence pre-check has
+   *     used for `405 RESOURCE_LOCKED` since d.683;
+   *   - `404 NOT-FOUND` is one of them, since d.693 (carrier B1: a publish through an
+   *     exchange nobody declared, measured `classId 60` on the send). It says something
+   *     the other codes do not — nothing DECLARED what was published to — but the
+   *     consequence is the same, because a publisher declares nothing and no reconnect
+   *     creates an exchange: `config/queueConfig.js` declares it and its owning service
+   *     asserts it. Retrying and buffering only held the message until its TTL dropped it.
+   *     It is NOT a `QueueNotFoundError`: that class belongs to the queue-existence
+   *     pre-check, and it carries a `queueName` and an ownership `kind` that
+   *     the caller reads from the refusal's `cause` — an exchange is neither;
+   *   - anything that is not a number is not a broker reply code. A socket error's
+   *     `'ECONNRESET'` says nothing about whether the message was stored, and reading it
+   *     as a refusal would drop messages a reconnect would have delivered.
+   *
+   * Until d.685a neither send leg read it. Both answered with their own `PublishError`,
+   * which the classification reads as transient (`utils/publishErrors.js`), so a message
+   * the broker refuses every single time was retried `publishMaxRetries` times and then
+   * buffered — and `InMemoryBuffer.flush()` returns an unsuccessful flush to the buffer,
+   * so it was re-offered on every reconnect until its TTL dropped it.
+   *
+   * @param {Object|null} channel - The channel that CARRIED the send, read before it was
+   *   replaced: `this._channel` may already be the successor by callback time.
+   * @param {'queue'|'exchange'} kind - Which leg is asking, so the message names what the
+   *   publish was addressed to (`architecture-principles.md` §5).
+   * @param {string} target - That queue or exchange.
+   * @returns {PermanentPublishError|null}
+   * @private
+   */
+  _refusedSendPermanent(channel, kind, target) {
+    const closeError = channel ? channel._closeError : null;
+    const code = closeError ? closeError.code : undefined;
+
+    if (typeof code !== 'number') {
+      return null;
+    }
+
+    if (!this._closeFrameNamesThisSend(channel, target)) {
+      return null;
+    }
+
+    return new PermanentPublishError(refusedSendMessage(kind, target, code), closeError);
+  }
+
+  /**
+   * The verdict for a send that was on the channel when SOMEBODY ELSE'S refusal closed
+   * it — or `null` when there was no numbered frame, or the frame was this send's own.
+   *
+   * Transient, and that is the whole point: the broker answered one message and never
+   * answered this one, so nothing about this message was decided. `PublishLayer` retries
+   * a `TransientPublishError` and buffers it meanwhile, which republishes it over the
+   * channel's successor; the permanent verdict would have dropped it on the first attempt
+   * (`src/layers/PublishLayer.js`).
+   *
+   * @param {Object|null} channel - The channel that CARRIED the send.
+   * @param {'queue'|'exchange'} kind - Which leg is asking.
+   * @param {string} target - That queue or exchange.
+   * @returns {TransientPublishError|null}
+   * @private
+   */
+  /**
+   * Say out loud what the broker answered about a send whose promise had already given up.
+   *
+   * The publish callback is not guarded by the attempt's `settled` flag, so when the
+   * confirmation budget has already rejected, the callback still runs and still builds the
+   * right verdict — and then hands it to a settled promise, where `reject()` is a no-op.
+   * The frame is not lost (it stays on `channel._closeError`) and the verdict is not
+   * overwritten; it simply reached nobody, while `PublishLayer` went on retrying and
+   * buffering a message the broker had refused for good.
+   *
+   * Silence is a defect of the same severity as a wrong result
+   * (`automation-gates.md` §5), so the verdict is REPORTED — and only reported. Nothing
+   * here changes the promise's outcome, the retry policy or the budget: making a late
+   * verdict DECIDE is a change of what happens to a message, which goes with the major
+   * wave (d.801).
+   *
+   * Measured (d.801, dev broker): a refused send is answered in tens of milliseconds —
+   * `404` median 13 ms idle and 31 ms (max 126 ms) under load 32 — so this path is not the
+   * ordinary one. It is what a budget set below that latency produces.
+   *
+   * @param {PermanentPublishError|TransientPublishError} verdict - What the frame decided.
+   * @param {'queue'|'exchange'} kind - Which leg is reporting.
+   * @param {string} target - The queue or exchange the send was addressed to.
+   * @param {string} queue - The queue the caller named (the exchange leg routes by it).
+   * @param {Object} options - The publish options, which carry the retry layer's `attempt`.
+   * @private
+   */
+  _reportLateSendVerdict(verdict, kind, target, queue, options) {
+    const code = verdict && verdict.cause ? verdict.cause.code : undefined;
+    const attempt = options && typeof options.attempt === 'number' ? options.attempt : null;
+
+    this._logger.warn(
+      `[RabbitMQClient] [mq-client-core] [PUBLISH] The broker refused this send and said so AFTER `
+        + `the confirmation budget of ${this._brokerAnswerTimeout}ms had already answered the caller - `
+        + `${kind} "${target}", broker code ${code}, verdict ${verdict.constructor.name}. `
+        + 'Expected: an answer within brokerAnswerTimeout, so the caller hears the broker rather '
+        + 'than the timeout. '
+        + 'Fix: the publish layer has already treated this message as unconfirmed and may retry it; '
+        + `raise brokerAnswerTimeout above the broker's answer latency for this route, or read `
+        + 'the publish:refused-late event to see how often it happens.'
+    );
+
+    this.emit('publish:refused-late', {
+      queue,
+      exchange: kind === 'exchange' ? target : undefined,
+      target,
+      kind,
+      code,
+      verdict: verdict.constructor.name,
+      // The verdict OBJECT, not only its name: since d.801c the retry layer acts on this
+      // event — it ends its loop with this very error instead of publishing again — and a
+      // listener that must act needs the thing, not a description of it.
+      error: verdict,
+      attempt,
+      budgetMs: this._brokerAnswerTimeout
+    });
+  }
+
+  _collateralSendTransient(channel, kind, target) {
+    const closeError = channel ? channel._closeError : null;
+    const code = closeError ? closeError.code : undefined;
+
+    if (typeof code !== 'number') {
+      return null;
+    }
+
+    if (this._closeFrameNamesThisSend(channel, target)) {
+      return null;
+    }
+
+    return new TransientPublishError(collateralCloseMessage(kind, target, code), closeError);
+  }
+
+  /**
+   * Is the broker's close frame on `channel` an answer about the send addressed to
+   * `target`?
+   *
+   * TWO READINGS, IN THIS ORDER, and the second only when the first cannot answer:
+   *
+   *  1. **How many sends the frame could be about.** When exactly one publish was
+   *     unconfirmed at the moment the frame arrived, the frame is about that one and
+   *     nothing else is possible. This is the case every earlier batch measured — d.685a
+   *     (403, 406), d.693 (404 on an undeclared exchange) — and it is why those verdicts
+   *     do not move. The count is the client's own (`_countSendInFlight()`), snapshotted
+   *     by `_attachPublisherChannelHandlers()` when it records the frame, because amqplib
+   *     emits `error` BEFORE `close` and it is `close` that rejects the callbacks: by
+   *     callback time the channel's own bookkeeping is already unwound.
+   *  2. **Whether the frame NAMES this target.** The broker quotes the subject of its
+   *     refusal in the reply text, and amqplib keeps that text inside the close error's
+   *     `message` — measured live 2026-09-20, the close error's own properties are
+   *     `["code","classId","methodId"]` and there is no `replyText` member, so the
+   *     sentence is where the name is:
+   *     `Channel closed by server: 404 (NOT-FOUND) with message "NOT_FOUND - no exchange
+   *     'no.such.exchange' in vhost 'mq-client-core-probe-…'"`.
+   *
+   * READING A SENTENCE IS NOT HOW THE CLASS IS DECIDED, and this does not change that
+   * (`docs/biz/70-contracts/error-handling.md` §6): the CODE still says what the answer
+   * means. The name only says WHOSE answer it is, and it is read in the one direction
+   * that is safe to get wrong — a name this cannot find, or a rewording that hides it,
+   * means "not claimed", so the send falls to the transient collateral verdict and the
+   * message is republished. The failure mode of a broker that rewords its text is a
+   * message sent twice, never a message dropped on a refusal that was not about it.
+   *
+   * @param {Object} channel - The channel carrying the recorded frame.
+   * @param {string} target - The queue or exchange THIS send was addressed to.
+   * @returns {boolean}
+   * @private
+   */
+  _closeFrameNamesThisSend(channel, target) {
+    const unconfirmed = channel._unconfirmedAtCloseFrame;
+
+    // The frame was recorded by `_attachPublisherChannelHandlers()`, which takes the
+    // snapshot in the same statement — so a missing number means the channel was never
+    // prepared by this client, and an unprepared channel is not one whose sends this may
+    // speak for. Not claimed, therefore transient: the safe direction.
+    if (typeof unconfirmed !== 'number') {
+      return false;
+    }
+
+    if (unconfirmed <= 1) {
+      return true;
+    }
+
+    const named = this._nameInCloseFrame(channel._closeError);
+    return named !== null && named === target;
+  }
+
+  /**
+   * The name the broker quoted in its close frame, or `null` when it quoted none.
+   *
+   * The first single-quoted token of the reply text is its subject — `no exchange 'X' in
+   * vhost 'Y'`, `no queue 'X' in vhost 'Y'`, `cannot obtain exclusive access to locked
+   * queue 'X' in vhost 'Y'`. A frame that quotes nothing (`PRECONDITION_FAILED - unknown
+   * delivery tag 999999`, measured d.698) answers with `null`, which is a real answer
+   * here: "this frame names nobody".
+   *
+   * @param {Error} closeError - The recorded close frame.
+   * @returns {string|null}
+   * @private
+   */
+  _nameInCloseFrame(closeError) {
+    const text = closeError && typeof closeError.message === 'string' ? closeError.message : '';
+    const quoted = /'([^']*)'/.exec(text);
+    return quoted ? quoted[1] : null;
+  }
+
+  /**
+   * Count one send as unconfirmed on `channel`, and hand back the ONE way to stop
+   * counting it.
+   *
+   * The count exists for `_closeFrameNamesThisSend()`: it is what says whether a numbered
+   * close frame can only be about this send. It is the client's own rather than amqplib's
+   * `unconfirmed` array, because that array is emptied by the very event this has to
+   * measure — `toClosed()` rejects every pending publish, and only then do the callbacks
+   * that ask this question run.
+   *
+   * A closure rather than a bare decrement at each site, because a send ends in three
+   * places (the callback, a synchronous throw, and nowhere at all when neither happens),
+   * and a count that is decremented twice or not at all makes the reading above answer
+   * for the wrong number of messages.
+   *
+   * @param {Object} channel - The channel the send is going out on.
+   * @returns {function(): void} Idempotent; call it when the send is no longer unconfirmed.
+   * @private
+   */
+  /**
+   * The channel of one send role, as it stands NOW.
+   *
+   * A getter rather than a captured value, because the member is replaced when the
+   * channel dies (`_attachPublisherChannelHandlers()` clears it, the next publish
+   * recreates it), and a caller holding the previous one would be sending on a corpse.
+   *
+   * @param {'publisher'|'telemetry'} role
+   * @returns {Object|null}
+   * @private
+   */
+  _sendChannelOf(role) {
+    return role === 'telemetry' ? this._telemetryChannel : this._channel;
+  }
+
+  /**
+   * The one place a send channel is assigned — so "which member does this role live in"
+   * is written once rather than at every site that creates, clears or tears one down.
+   *
+   * @param {'publisher'|'telemetry'} role
+   * @param {Object|null} channel
+   * @private
+   */
+  _setSendChannelOf(role, channel) {
+    if (role === 'telemetry') {
+      this._telemetryChannel = channel;
+    } else {
+      this._channel = channel;
+    }
+  }
+
+  /**
+   * Which channel a publish goes out on, from the options it was given.
+   *
+   * Explicit, never derived from the queue name (`architecture-principles.md` §8, §9): a
+   * telemetry publish says so because `BaseClient.publishTelemetry()` says so, and a name
+   * that merely looks like a monitoring queue does not move a caller's message onto
+   * another channel.
+   *
+   * @param {Object} options - The publish options as the caller handed them over.
+   * @returns {'publisher'|'telemetry'}
+   * @private
+   */
+  _sendRoleFor(options) {
+    return options && options.channelRole === 'telemetry' ? 'telemetry' : 'publisher';
+  }
+
+  _countSendInFlight(channel) {
+    channel._unconfirmedSends = (channel._unconfirmedSends || 0) + 1;
+    let counted = true;
+    return () => {
+      if (!counted) return;
+      counted = false;
+      channel._unconfirmedSends -= 1;
+    };
+  }
+
   /**
    * Declare an exchange.
    *
@@ -2961,11 +3540,16 @@ class RabbitMQClient extends EventEmitter {
    * @private
    */
   async _publishOnce(queue, buffer, options = {}) {
-    // Ensure publisher channel exists and is open (auto-recreates if closed)
-    await this._ensurePublisherChannel();
-    
+    // Whose channel this send goes out on (d.724). Read once, here: the role cannot
+    // change inside one attempt, and the channel it names can — so everything below asks
+    // `_sendChannelOf(sendRole)` rather than holding a member.
+    const sendRole = this._sendRoleFor(options);
+
+    // Ensure the send channel exists and is open (auto-recreates if closed)
+    await this._ensurePublisherChannel(sendRole);
+
     // Track operation for debugging
-    this._trackChannelOperation(this._channel, `publish to ${queue}`);
+    this._trackChannelOperation(this._sendChannelOf(sendRole), `publish to ${queue}`);
     
     // Asked with `=== undefined`, not with `||`: the empty string IS a value here
     // — it names the default exchange — and the third leg was a third copy of a
@@ -3018,13 +3602,16 @@ class RabbitMQClient extends EventEmitter {
         // If queue doesn't exist (404), we should NOT auto-create it - infrastructure queues must be created explicitly
         // This prevents creating queues with wrong arguments (no TTL) which causes 406 errors later
         if (!skipQueueExistencePrecheck) {
+        // Declared OUTSIDE the `try`, because the `catch` below has to ask whether
+        // the channel that CARRIED the RPC is still alive — that reading is what
+        // tells "the broker answered" from "the answer never came" (d.683).
+        let queueChannel = null;
         try {
           // The queue channel comes from the ONE rail (d.282): ensure it, refuse
           // it unless it is ALIVE, record the operation. Until d.284 this site
           // assembled that sequence itself — `_ensureQueueChannel()` plus
           // `_isChannelAlive()` by hand — differing from the rail in nothing but
           // the error type, which is `_publishPathTransient()`'s job below.
-          let queueChannel;
           try {
             queueChannel = await this._requireQueueChannel('checkQueue', queue);
           } catch (railErr) {
@@ -3045,7 +3632,7 @@ class RabbitMQClient extends EventEmitter {
           //   → QueueNotFoundError(kind='business'). Publisher je nikdy nevytváří.
           // - Ostatní jména (ani infra, ani business vzor) nemá kdo vlastnit, takže
           //   je nezakládá nikdo → QueueNotFoundError(kind='unowned'), d.419.
-          if (checkErr.code === 404) {
+          if (checkErr.code === AMQP_NOT_FOUND) {
             // `queueConfig` is loaded once at the top of this module. It used to be
             // required here, inside a try/catch whose `catch` re-implemented
             // `isInfrastructureQueue` as an inline prefix list — a fallback
@@ -3067,7 +3654,7 @@ class RabbitMQClient extends EventEmitter {
             // registration; a publisher that creates it is a programming error.
             //
             // The rule and this exact wording came from
-            // `conn-infra-mq/src/transports/rabbitmqClient.js:264-277` — a transport
+            // `conn-infra-mq/src/transports/rabbitmqClient.js` — a transport
             // that nothing in `src/` instantiated, so the guard protected nobody
             // while this file, the one every client actually runs, auto-created the
             // queue and only printed a warning.
@@ -3075,7 +3662,7 @@ class RabbitMQClient extends EventEmitter {
               throw new QueueNotFoundError(queue, false, checkErr, 'business');
             }
           // Nobody owns this name. Until d.419 that opened a THIRD case beside
-          // the two above: the publish path asked `RecoveryWorker` whether this
+          // the two above: the publish path asked the recovery worker whether this
           // client might declare it and, when the answer was yes, declared it —
           // `durable=true, arguments={}`, no TTL, no dead-letter route (measured
           // live, d.410). The concept had already ruled that out: "queues come
@@ -3100,6 +3687,34 @@ class RabbitMQClient extends EventEmitter {
           // "nothing declares this name", and the publish path must not flatten the
           // two into one message.
           throw new QueueNotFoundError(queue, false, checkErr, 'unowned');
+          } else if (
+            !(checkErr instanceof TransientPublishError)
+            && checkErr.code === undefined
+            && !this._isChannelAlive(queueChannel)
+          ) {
+            // THE RPC NEVER GOT AN ANSWER. amqplib answers the request that was in
+            // flight when a channel closed with the broker's own close frame — a
+            // NUMBER in `code` — and rejects whatever was queued behind it with a
+            // bare `new Error('Channel ended, no reply will be forthcoming')`
+            // (`_rejectPending`, `node_modules/amqplib/lib/channel.js`), whose
+            // only own properties are `stack` and `message`. Until d.683 that object
+            // travelled untouched to `classifyPublishError()`, which had to keep its
+            // verdict by matching the sentence — the one text branch d.677 could not
+            // remove from where it stood, because the sentence was all there was.
+            //
+            // This site does not have to read it: it knows which channel carried the
+            // RPC and can see that the channel is gone, so it answers in the dialect
+            // every other leg of this path already speaks. The three conditions are
+            // each doing work:
+            //   - `code === undefined` — a numbered refusal is an ANSWER about this
+            //     request (405 RESOURCE_LOCKED, measured), and repeating the request
+            //     repeats it. It stays permanent;
+            //   - the channel is dead — a failure on a LIVE channel did get through
+            //     to the broker and back, whatever it says;
+            //   - not already typed — `_publishPathTransient()` above throws into
+            //     this same `catch`, and wrapping a verdict in itself would bury the
+            //     rail's own sentence one level deeper for no reader.
+            throw this._publishPathTransient('checkQueue', queue, checkErr);
           } else {
             // Other error - rethrow
             throw checkErr;
@@ -3123,8 +3738,16 @@ class RabbitMQClient extends EventEmitter {
           let timeout = null;
           let safetyTimer = null;
           let settled = false;
+          // Assigned once the send is on its way (below), and released here with the
+          // timers: the attempt ends in five places — the callback, a synchronous throw,
+          // the confirmation timeout, the liveness check before the send, and the
+          // watchdog — and a send still counted after its attempt has ended would make
+          // the next close frame on this channel look as if it could be about two
+          // messages (`_closeFrameNamesThisSend()`, d.723).
+          let sendSettled = () => {};
           const disarm = () => {
             settled = true;
+            sendSettled();
             this._clearTimeout(timeout);
             this._clearTimeout(safetyTimer);
             timeout = null;
@@ -3147,7 +3770,7 @@ class RabbitMQClient extends EventEmitter {
           // during the awaits above (queue existence pre-check), so this is not
           // a repeat of `_ensurePublisherChannel()` — it is the last reading
           // before the payload leaves, and it reads the one liveness source.
-          if (!this._isChannelAlive(this._channel)) {
+          if (!this._isChannelAlive(this._sendChannelOf(sendRole))) {
             disarm();
             reject(new ConnectionError(
               `[RabbitMQClient] Cannot publish: channel is closed for queue "${queue}" - `
@@ -3158,9 +3781,13 @@ class RabbitMQClient extends EventEmitter {
           }
           
           // Track original channel to detect if it was closed/recreated during publish
-          const originalChannel = this._channel;
+          const originalChannel = this._sendChannelOf(sendRole);
           let callbackInvoked = false;
-          
+          // This send is unconfirmed from the moment it is handed over until the broker
+          // answers it, the channel dies under it, or amqplib refuses it outright — and
+          // that number is what decides whose answer a close frame is (d.723).
+          sendSettled = this._countSendInFlight(originalChannel);
+
           // Send message with callback
           try {
             originalChannel.sendToQueue(
@@ -3169,14 +3796,45 @@ class RabbitMQClient extends EventEmitter {
               buildAmqpMessageProperties(options, persistent, headers),
               (err, ok) => {
               callbackInvoked = true;
+              // Read BEFORE `disarm()`, which sets it: the question is whether the budget
+              // had already answered the caller, and after `disarm()` nobody can tell.
+              const answeredAlready = settled;
               disarm();
-              
+
               // CRITICAL: the delivery tag belongs to the channel that SENT the
               // message, so that channel's liveness is the whole question. One
               // reading answers it: a channel that was replaced is a channel that
               // died first (`_ensurePublisherChannel()` recreates only a dead one),
               // so identity and `_createdAt` comparisons said nothing this does not.
               if (!this._isChannelAlive(originalChannel)) {
+                // WHY the channel died decides first. A numbered close frame is the
+                // broker's answer about THIS message, and no reconnect changes it
+                // (`_refusedSendPermanent()`, d.685a) — so it is asked before the
+                // reconnect wait below, which would otherwise re-offer a message the
+                // broker will refuse again.
+                const refused = this._refusedSendPermanent(originalChannel, 'queue', queue);
+                if (refused) {
+                  if (answeredAlready) {
+                    this._reportLateSendVerdict(refused, 'queue', queue, queue, options);
+                  } else {
+                    this._logger.error(`[RabbitMQClient] [mq-client-core] [PUBLISH] ${refused.message}`);
+                  }
+                  reject(refused);
+                  return;
+                }
+                // The frame was there but it was about a DIFFERENT send on this channel
+                // (d.723): this message was never answered, so it is republished rather
+                // than dropped on somebody else's refusal.
+                const collateral = this._collateralSendTransient(originalChannel, 'queue', queue);
+                if (collateral) {
+                  if (answeredAlready) {
+                    this._reportLateSendVerdict(collateral, 'queue', queue, queue, options);
+                  } else {
+                    this._logger.warn(`[RabbitMQClient] [mq-client-core] [PUBLISH] ${collateral.message}`);
+                  }
+                  reject(collateral);
+                  return;
+                }
                 // Channel was closed or recreated - delivery tag is invalid
                 this._logger.warn(`[RabbitMQClient] [mq-client-core] [PUBLISH] Channel closed/recreated during publish to queue "${queue}", ignoring callback`);
                 // If we're reconnecting, wait and retry
@@ -3200,29 +3858,24 @@ class RabbitMQClient extends EventEmitter {
               }
               
               if (err) {
-                // Check if error is about invalid delivery tag (channel was closed)
-                if (err.message && (err.message.includes('unknown delivery tag') || err.message.includes('PRECONDITION_FAILED'))) {
-                  this._logger.warn(`[RabbitMQClient] [mq-client-core] [PUBLISH] Delivery tag invalid (channel may have been closed) for queue "${queue}"`);
-                  // If we're reconnecting, wait and retry
-                  if (this._reconnecting) {
-                    this._waitForReconnection().then(() => {
-                      // Retry publish after reconnection
-                      return this.publish(queue, buffer, options);
-                    }).then(resolve).catch(reject);
-                  } else {
-                    // Not reconnecting - delivery tag is invalid, message delivery not guaranteed
-                    reject(new PublishError(
-                      `[RabbitMQClient] Delivery tag invalid for queue "${queue}" (channel closed) and not reconnecting - message delivery not guaranteed. `
-                        + 'Expected: the delivery tag to stay valid until the broker confirms, or a reconnect to be in flight. '
-                        + 'Fix: republish the message — the confirm never arrived, so it may or may not have been stored.',
-                      queue,
-                      null
-                    ));
-                  }
-                } else {
-                  this._logger.error(`[RabbitMQClient] [mq-client-core] [PUBLISH] Send callback error for queue "${queue}":`, err.message);
-                  reject(err);
-                }
+                // A confirm callback is handed ONE of three things by amqplib, and this is
+                // the whole list: `null` (the broker confirmed), `new Error('message
+                // nacked')` and `new Error('channel closed')` — composed in
+                // `lib/channel.js` (the `Channel` constructor's confirm listeners) and
+                // `lib/channel_model.js` (`ConfirmChannel.waitForConfirms()`), with no `code` on
+                // either. The callback cannot see WHY the channel died; the channel can,
+                // and the branch above reads it (`_refusedSendPermanent()`, d.685a).
+                //
+                // So there is no delivery-tag case to catch here, and until d.698 one was
+                // written anyway: a substring test for the words a 406 reply text carries.
+                // It matched none of the three, and what it did was not neutral: it
+                // answered with a `PublishError`, which the
+                // classification reads as TRANSIENT, so a message would have been retried
+                // `publishMaxRetries` times and then buffered on the strength of a wording.
+                // The live carrier of that sentence is a 406 close frame on the channel's
+                // `error` event (measured d.693/d.698), never an argument to this callback.
+                this._logger.error(`[RabbitMQClient] [mq-client-core] [PUBLISH] Send callback error for queue "${queue}":`, err.message);
+                reject(err);
               } else {
                 // Structured log: publish confirmed
                 const wfId = workflowIdOf(headers);
@@ -3257,8 +3910,27 @@ class RabbitMQClient extends EventEmitter {
             }
           } catch (sendErr) {
             disarm();
-            // If channel is closed, try to wait for reconnection and retry
-            if (sendErr.message && (sendErr.message.includes('Channel ended') || sendErr.message.includes('Channel closed'))) {
+            // THE CHANNEL ANSWERS, NOT THE SENTENCE (d.685c). A synchronous throw from
+            // `sendToQueue()` means amqplib refused to send at all, and the one question
+            // that decides what to do with the message is whether the channel it was
+            // handed is still alive: a dead one will be replaced by the reconnect, so the
+            // message is republished over its successor; a live one did accept the call
+            // and failed for its own reason, which no reconnect changes.
+            //
+            // Until this batch the question was asked of the message text
+            // (`includes('Channel ended') || includes('Channel closed')`), which is the
+            // defect d.677 removed from the classification: a wording decided whether a
+            // message was re-offered to the broker. It was also matching a sentence that
+            // cannot arrive here — `'Channel ended, no reply will be forthcoming'` is
+            // built for an RPC awaiting a REPLY (`_rejectPending()`, amqplib
+            // `lib/channel.js`), and a send is not an RPC.
+            //
+            // Measured carrier, live against the dev broker: amqplib invalidates a dead
+            // channel's send methods (`invalidateSend()`, `lib/channel.js`), so
+            // what arrives is its `IllegalOperationError` with `'Channel closed'` — no
+            // code, and `channel._closeError` null. Liveness from the one source
+            // (`_isChannelAlive`, d.260), like the two callbacks above.
+            if (!this._isChannelAlive(originalChannel)) {
               this._logger.warn(`[RabbitMQClient] [mq-client-core] [PUBLISH] Channel closed during sendToQueue, will retry after reconnection`);
               // Wait for reconnection and retry
               if (this._reconnecting) {
@@ -3302,8 +3974,20 @@ class RabbitMQClient extends EventEmitter {
         
         // Use callback-based confirmation - kanály jsou spolehlivé
         const confirmPromise = new Promise((resolve, reject) => {
+          // Assigned once the send is on its way (below). It is declared HERE because the
+          // count has to be released on EVERY ending of this attempt, and the earliest of
+          // them — the confirmation timeout — is armed before the send exists. A send
+          // still counted after its attempt has ended would make the next close frame on
+          // this channel look as if it could be about two messages (d.723).
+          let sendSettled = () => {};
+          // Whether the budget has already answered the caller — read by the callback, so
+          // a verdict that arrives afterwards can be REPORTED instead of handed to a
+          // settled promise (d.801b). The queue leg keeps the same fact in `settled`.
+          let answeredAlready = false;
           // Set timeout for exchange publish confirmation
           const timeout = this._setTimeout(() => {
+            answeredAlready = true;
+            sendSettled();
             reject(new PublishError(
               `[RabbitMQClient] Exchange publish confirmation timeout for exchange "${exchange}" after ${this._brokerAnswerTimeout}ms - `
                 + 'Expected: the broker to confirm the message within brokerAnswerTimeout. '
@@ -3313,14 +3997,79 @@ class RabbitMQClient extends EventEmitter {
             ));
           }, this._brokerAnswerTimeout);
           
-          this._channel.publish(
+          // The channel that SENDS is the channel whose liveness answers the
+          // callback below — read once here, like the queue leg does, because
+          // the member may already hold the replacement by the time the
+          // callback runs.
+          const sendingChannel = this._sendChannelOf(sendRole);
+          // Unconfirmed until answered — the same count the queue leg keeps, and for the
+          // same reason: it is what decides whose answer a close frame is (d.723).
+          sendSettled = this._countSendInFlight(sendingChannel);
+
+          sendingChannel.publish(
             exchange,
             routingKey,
             buffer,
             buildAmqpMessageProperties(options, persistent, headers),
             (err, ok) => {
+            sendSettled();
             this._clearTimeout(timeout);
             if (err) {
+              // THE CONFIRM NEVER CAME. amqplib answers every unconfirmed publish of
+              // a channel that has just closed with a bare `new Error('channel
+              // closed')` (the `Channel` constructor's `'close'` listener, `node_modules/amqplib/lib/channel.js`) — class `Error`,
+              // no code, own properties `stack` and `message`. The broker's own
+              // numbered refusal is NOT what arrives here: it goes to the channel's
+              // `error` event (measured d.677, carrier B1 — a publish through an
+              // exchange nobody declared).
+              //
+              // The queue leg above has read the sending channel's liveness since
+              // long before this batch, which is why a refused send already reached
+              // the classification as this package's own `PublishError` (carrier E1).
+              // This leg had no such reading, so its bare sentinel travelled untouched
+              // and `classifyPublishError()` had to keep its verdict by the sentence.
+              // Now both legs answer the same way, and the sentinel is kept in `cause`
+              // rather than read (d.683).
+              //
+              // A live channel means the broker DID answer — a nack is the measured
+              // case (carrier G, `'message nacked'`, amqplib `lib/channel.js`, the `Channel` constructor's `'nack'` listener) —
+              // and that answer is about this message, so it stays what it was.
+              if (!this._isChannelAlive(sendingChannel)) {
+                // The same question this leg's sibling asks one branch up: did the broker
+                // REFUSE this send, or did the channel merely die under it (d.685a)?
+                const refused = this._refusedSendPermanent(sendingChannel, 'exchange', exchange);
+                if (refused) {
+                  if (answeredAlready) {
+                    this._reportLateSendVerdict(refused, 'exchange', exchange, queue, options);
+                  } else {
+                    this._logger.error(`[RabbitMQClient] [mq-client-core] [PUBLISH] ${refused.message}`);
+                  }
+                  reject(refused);
+                  return;
+                }
+                // Somebody else's refusal closed the channel under this send (d.723) —
+                // never answered, therefore never refused, therefore republished.
+                const collateral = this._collateralSendTransient(sendingChannel, 'exchange', exchange);
+                if (collateral) {
+                  if (answeredAlready) {
+                    this._reportLateSendVerdict(collateral, 'exchange', exchange, queue, options);
+                  } else {
+                    this._logger.warn(`[RabbitMQClient] [mq-client-core] [PUBLISH] ${collateral.message}`);
+                  }
+                  reject(collateral);
+                  return;
+                }
+                this._logger.warn(`[RabbitMQClient] [mq-client-core] [PUBLISH] Channel closed during publish to exchange "${exchange}", classifying as transient`);
+                reject(new PublishError(
+                  `[RabbitMQClient] Channel closed during publish to exchange "${exchange}" - message delivery not guaranteed. `
+                    + 'Expected: the channel to stay open until the broker confirms. '
+                    + 'Fix: republish the message — the confirm never arrived, so it may or may not have been routed; '
+                    + 'read error.cause for what amqplib said.',
+                  exchange,
+                  err
+                ));
+                return;
+              }
               this._logger.error(`[RabbitMQClient] [mq-client-core] [PUBLISH] Exchange publish callback error:`, err.message);
               reject(err);
             } else {
@@ -3338,9 +4087,19 @@ class RabbitMQClient extends EventEmitter {
       // Pokud channel closed, vyhodíme TransientPublishError a necháme PublishLayer řešit retry
       
       // Všechny chyby projdou jednotnou klasifikací do Transient/Permanent/QueueNotFound
-      const classifiedErr = classifyPublishError(err, queue);
-      this.emit('error', classifiedErr);
-      throw classifiedErr;
+      //
+      // A VERDICT ABOUT A MESSAGE GOES ONE WAY: to whoever sent it. Until d.811b this line
+      // also put the classified failure on the client's `error` channel, which is the
+      // channel the rest of this client uses for the CONNECTION. Measured (d.811): it
+      // fired for every classification, transient as well as permanent; nobody read it
+      // (no `.on('error')` on this client anywhere in `shared/**` or `infra/**`, and zero
+      // callers of `onError()` in production code); the concept never asked for it
+      // (`docs/architecture/mq-publish-reliability.md` does not mention the channel); and
+      // the only rail that ever met it had to learn to IGNORE it, because one concurrent
+      // publish failing while the link came back rejected every reconnect waiter
+      // (`_waitForReconnection()`, d.435/d.435b). It made work for another rail instead of
+      // serving a reader.
+      throw classifyPublishError(err, queue);
     }
   }
 
@@ -3378,7 +4137,11 @@ class RabbitMQClient extends EventEmitter {
       this._prefetchTracking.set(queue, {
         prefetchCount: prefetch,
         inFlight: 0,
-        lastCheck: Date.now()
+        lastCheck: Date.now(),
+        // Which side of the threshold this queue was on when the verdict was last
+        // taken. It is what makes the alarm an EPISODE rather than a line per tick
+        // — see `_checkPrefetchUtilization()`.
+        utilizationHigh: false
       });
     }
 
@@ -3496,7 +4259,7 @@ class RabbitMQClient extends EventEmitter {
     //
     // The ONE queue this demand cannot be made of is the one at the END of a
     // chain: a queue something else dead-letters TO. `workflow.failed` is named
-    // in `x-dead-letter-routing-key` by `workflow.init` and `workflow.control`,
+    // in `x-dead-letter-routing-key` by `workflow.init`,
     // `<service>.dlq` by every business template — and the confirmed topology
     // leaves exactly those without a route of their own, because a dead-letter
     // route on a dead-letter queue is a loop or a chain with no end
@@ -3566,7 +4329,7 @@ class RabbitMQClient extends EventEmitter {
         await queueChannel.checkQueue(queue);
         this._logger.debug(`[RabbitMQClient] [mq-client-core] [CONSUMER] ✓ Infrastructure queue ${queue} exists (consumer will proceed)`);
       } catch (checkErr) {
-        if (checkErr.code === 404) {
+        if (checkErr.code === AMQP_NOT_FOUND) {
           // Typed and coded since d.297: a bare `Error` lost the queue AND the
           // class, so the layer above could not tell "this queue does not exist"
           // from "the policy refused this queue" and told the reader the wrong
@@ -3582,8 +4345,7 @@ class RabbitMQClient extends EventEmitter {
       }
     } else {
       // Business queue (or unknown) — declared on the ONE public rail, the same
-      // `assertQueue()` the publish path's 404 branch (d.281) and
-      // `RecoveryWorker.createQueue()` (d.277b) go through. It ensures the queue
+      // `assertQueue()` every collaborator that declares a queue goes through. It ensures the queue
       // channel, refuses one that is not alive (d.282) and resolves the arguments
       // from `queueConfig.declarationOptions()` — so a declaration made here and a
       // declaration made anywhere else are the same declaration by construction,
@@ -3649,56 +4411,14 @@ class RabbitMQClient extends EventEmitter {
     // `false` = the budget is one attempt, so the first failure rejects into
     // `<svc>.dlq` — exactly what a `permanent` classification already does.
     // `true` or absent = the budget configuration decides. There is no third
-    // meaning, and the combination that would need one is refused below rather
+    // meaning, and the combination that would need one is refused rather
     // than resolved by silently preferring one of the two.
-    if (options.requeueOnError !== undefined && typeof options.requeueOnError !== 'boolean') {
-      throw new ValidationError(
-        '[RabbitMQClient] Invalid requeueOnError - Expected: true or false, got '
-          + `${JSON.stringify(options.requeueOnError)}. Fix: pass consume(queue, handler, `
-          + '{ requeueOnError: false }) to dead-letter on the first failure, or leave it out and '
-          + 'let the delivery budget decide.'
-      );
-    }
-
-    const noRequeue = options.requeueOnError === false;
-
-    if (noRequeue && options.maxAttempts !== undefined && options.maxAttempts !== 1) {
-      throw new ValidationError(
-        '[RabbitMQClient] Contradictory delivery policy - requeueOnError: false means one attempt, '
-          + `but maxAttempts says ${JSON.stringify(options.maxAttempts)}. Expected: one statement about `
-          + 'how many times a handler may run. Fix: drop requeueOnError to keep the budget, or drop '
-          + 'maxAttempts to dead-letter on the first failure.'
-      );
-    }
-
-    const maxAttempts = noRequeue
-      ? 1
-      : options.maxAttempts === undefined
-        ? runtimeCfg.get('maxDeliveryAttempts', this._config.maxDeliveryAttempts)
-        : options.maxAttempts;
-
-    if (!Number.isInteger(maxAttempts) || maxAttempts < 1) {
-      throw new ValidationError(
-        '[RabbitMQClient] Invalid delivery budget - maxAttempts must be an integer >= 1, got '
-          + `${JSON.stringify(maxAttempts)}. Fix: pass consume(queue, handler, { maxAttempts: <integer >= 1> }), `
-          + 'or leave it out and let the module default (defaults.js maxDeliveryAttempts, '
-          + 'env RABBITMQ_MAX_DELIVERY_ATTEMPTS) decide.'
-      );
-    }
-
-    const classify = options.classify === undefined
-      ? deliveryPolicy.defaultClassification
-      : options.classify;
-
-    if (typeof classify !== 'function') {
-      throw new ValidationError(
-        '[RabbitMQClient] Invalid error classifier - classify must be a function returning '
-          + `'transient' or 'permanent', got ${typeof options.classify}. Fix: pass consume(queue, handler, `
-          + '{ classify: (error) => … }), or leave it out and every error is treated as transient.'
-      );
-    }
-
-    const policy = { maxAttempts, classify };
+    // The rules have ONE owner, exported for every consumer's test double
+    // (d.1005): `deliveryPolicy.validateConsumeOptions`.
+    const policy = deliveryPolicy.validateConsumeOptions(
+      options,
+      () => runtimeCfg.get('maxDeliveryAttempts', this._config.maxDeliveryAttempts)
+    );
     const onDeadLetter = options.onDeadLetter;
     if (onDeadLetter !== undefined && typeof onDeadLetter !== 'function') {
       throw new ValidationError(
@@ -3786,120 +4506,162 @@ class RabbitMQClient extends EventEmitter {
           }
         });
         
-        // Track in-flight message (increment)
+        // ONE delivery raises this counter once and lowers it once. The
+        // `finally` at the end of this callback is that second half, and since
+        // d.680 it is the ONLY place the counter goes down
+        // (`change-discipline.md` § One rail per concern).
+        //
+        // MEASURED on production (d.680, 2026-09-20, the dispatcher):
+        //
+        //     Prefetch utilization high: queue 'workflow.completed' has 43/5
+        //     messages in-flight (860%)
+        //
+        // — and the number grew with every workflow, never falling. Until d.680
+        // the decrement lived in the branches that settle a message HERE: the
+        // auto-ack, the delivery policy, and the rejection of an unreadable
+        // counter. Every OTHER way a delivery can end left the increment
+        // standing — a handler that settles the message itself (the public
+        // `ack()`/`nack()` set `msg._mqProcessed`, which is exactly what makes
+        // the auto-ack branch stand down), a `noAck` consumer, and the two early
+        // returns taken when the channel died under a running handler.
+        //
+        // Nothing stalled, because the window is enforced by the BROKER and not
+        // by this number. The only casualty was the alarm, which from then on
+        // fired for every delivery whatever the load — the warning that cannot
+        // fail to happen that d.550 removed for prefetch 1, and that
+        // `automation-gates.md` §5 counts as a defect of its own.
+        //
+        // The counter is therefore bound to the DELIVERY, not to the branch that
+        // settles it: it measures what this consumer is holding, and it stops
+        // holding a delivery when this callback returns — whoever settled it,
+        // and however many times.
         const tracking = this._prefetchTracking.get(queue);
         if (tracking) {
           tracking.inFlight++;
           tracking.lastCheck = Date.now();
           this._checkPrefetchUtilization(queue, tracking);
         }
-        
-        // Which attempt this delivery is, read from the header this library
-        // writes (`../config/deliveryPolicy.js`). `null` = the header carries a
-        // value this library never wrote, so the message cannot be bounded and
-        // the handler is NOT run for it; it is rejected below.
-        const attemptsMade = deliveryPolicy.readAttemptsMade(msgHeaders);
-        const attempt = attemptsMade === null ? null : attemptsMade + 1;
-
-        if (attempt === null) {
-          this._logger.error(
-            '[RabbitMQClient] Unreadable delivery counter - the '
-              + `${deliveryPolicy.ATTEMPTS_HEADER} header of a message on "${queue}" holds `
-              + `${JSON.stringify(msgHeaders[deliveryPolicy.ATTEMPTS_HEADER])}, which is not a `
-              + 'non-negative integer. Expected: only this library writes that header. '
-              + 'Fix: the message is rejected into the dead-letter queue unread — reading a '
-              + 'malformed counter as zero would make the redelivery loop unbounded again.',
-            { queue }
-          );
-          await this._rejectDelivery({
-            msg,
-            queue,
-            channelForMsg,
-            noAck,
-            error: new Error(
-              `[RabbitMQClient] Message on "${queue}" carries an unreadable `
-                + `${deliveryPolicy.ATTEMPTS_HEADER} header`
-            ),
-            classification: deliveryPolicy.UNCLASSIFIABLE,
-            attempts: null,
-            maxAttempts: policy.maxAttempts,
-            onDeadLetter
-          });
-          if (tracking) {
-            tracking.inFlight = Math.max(0, tracking.inFlight - 1);
-            tracking.lastCheck = Date.now();
-          }
-          return;
-        }
 
         try {
-          // The handler is told WHICH attempt it is on, so a side effect that
-          // must happen once — the RPC error reply above all — happens on the
-          // last attempt only, instead of once per redelivery. A handler that
-          // takes one argument ignores the second.
-          await onMessage(msg, {
-            attempt,
-            maxAttempts: policy.maxAttempts,
-            isFinalAttempt: attempt >= policy.maxAttempts
-          });
-          // Acknowledge message after successful processing
-          if (!noAck && !msg._mqProcessed) {
-            // Liveness comes from the ONE source the channel handlers set
-            // first-hand (`_isChannelAlive()`, d.260). The reading this
-            // replaced, `channelForMsg.closed`, asked amqplib for a property it
-            // does not define, so it answered "alive" for the channel the
-            // broker had just killed and handed the corpse an `ack`.
-            if (!this._isChannelAlive(channelForMsg)) {
-              this._logger.warn('[RabbitMQClient] [mq-client-core] [CONSUMER] Cannot ack - consumer channel is closed/recreated (message will be requeued by broker)');
-              return;
-            }
-            try {
-              channelForMsg.ack(msg);
-              msg._mqProcessed = true;
-            } catch (ackErr) {
-              const m = ackErr && ackErr.message ? ackErr.message : '';
-              if (m.includes('unknown delivery tag') || m.includes('PRECONDITION_FAILED') || m.includes('Channel closed')) {
-                msg._mqProcessed = true;
-                this._logger.warn('[RabbitMQClient] [mq-client-core] [CONSUMER] Ack failed due to invalid delivery tag / closed channel (message delivery will be handled by broker)', { error: m });
+          // Which attempt this delivery is, read from the header this library
+          // writes (`../config/deliveryPolicy.js`). `null` = the header carries a
+          // value this library never wrote, so the message cannot be bounded and
+          // the handler is NOT run for it; it is rejected below.
+          const attemptsMade = deliveryPolicy.readAttemptsMade(msgHeaders);
+          const attempt = attemptsMade === null ? null : attemptsMade + 1;
+
+          if (attempt === null) {
+            this._logger.error(
+              '[RabbitMQClient] Unreadable delivery counter - the '
+                + `${deliveryPolicy.ATTEMPTS_HEADER} header of a message on "${queue}" holds `
+                + `${JSON.stringify(msgHeaders[deliveryPolicy.ATTEMPTS_HEADER])}, which is not a `
+                + 'non-negative integer. Expected: only this library writes that header. '
+                + 'Fix: the message is rejected into the dead-letter queue unread — reading a '
+                + 'malformed counter as zero would make the redelivery loop unbounded again.',
+              { queue }
+            );
+            await this._rejectDelivery({
+              msg,
+              queue,
+              channelForMsg,
+              noAck,
+              error: new Error(
+                `[RabbitMQClient] Message on "${queue}" carries an unreadable `
+                  + `${deliveryPolicy.ATTEMPTS_HEADER} header`
+              ),
+              classification: deliveryPolicy.UNCLASSIFIABLE,
+              attempts: null,
+              maxAttempts: policy.maxAttempts,
+              onDeadLetter
+            });
+            return;
+          }
+
+          try {
+            // The handler is told WHICH attempt it is on, so a side effect that
+            // must happen once — the RPC error reply above all — happens on the
+            // last attempt only, instead of once per redelivery. A handler that
+            // takes one argument ignores the second.
+            await onMessage(msg, {
+              attempt,
+              maxAttempts: policy.maxAttempts,
+              isFinalAttempt: attempt >= policy.maxAttempts
+            });
+            // Acknowledge message after successful processing
+            if (!noAck && !msg._mqProcessed) {
+              // Liveness comes from the ONE source the channel handlers set
+              // first-hand (`_isChannelAlive()`, d.260). The reading this
+              // replaced, `channelForMsg.closed`, asked amqplib for a property it
+              // does not define, so it answered "alive" for the channel the
+              // broker had just killed and handed the corpse an `ack`.
+              if (!this._isChannelAlive(channelForMsg)) {
+                this._logger.warn('[RabbitMQClient] [mq-client-core] [CONSUMER] Cannot ack - consumer channel is closed/recreated (message will be requeued by broker)');
                 return;
               }
-              throw ackErr;
+              try {
+                channelForMsg.ack(msg);
+                msg._mqProcessed = true;
+              } catch (ackErr) {
+                // A REFUSED CALL IS A CLASS, NOT A SENTENCE (d.698). amqplib replaces a
+                // dead channel's send methods with one that throws its own
+                // `IllegalOperationError` (`invalidateSend()`/`invalidOp()`,
+                // `lib/channel.js`), so that class IS "the channel would not take
+                // this ack" — and it is the only thing `ack()` ever throws.
+                //
+                // The sentence branch this replaced listed `'unknown delivery tag'`,
+                // `'PRECONDITION_FAILED'` and `'Channel closed'`. The first two cannot
+                // arrive: an ack with a tag the broker does not hold does not throw at all
+                // — the broker answers by closing the channel with a 406 frame on its
+                // `error` event (measured live, d.698). The third is only ONE of amqplib's
+                // two wordings, so the other, `'Channel closing'` (`toClosing()`, `:167`),
+                // was rethrown — into the handler's own catch, which republished a RETRY
+                // COPY of a message whose handler had already succeeded.
+                if (ackErr instanceof IllegalOperationError) {
+                  msg._mqProcessed = true;
+                  this._logger.warn('[RabbitMQClient] [mq-client-core] [CONSUMER] Ack refused by a closed/closing channel (message delivery will be handled by broker)', { error: ackErr.message });
+                  return;
+                }
+                throw ackErr;
+              }
+              this._logger.debug('[RabbitMQClient] MSG_ACKED', {
+                workflow_id: wfId,
+                action: 'MSG_ACKED',
+                handler: 'consume',
+                function: 'RabbitMQClient.consume',
+                input: { queue },
+                output: { status: 'acknowledged', queue }
+              });
             }
-            this._logger.debug('[RabbitMQClient] MSG_ACKED', {
-              workflow_id: wfId,
-              action: 'MSG_ACKED',
-              handler: 'consume',
-              function: 'RabbitMQClient.consume',
-              input: { queue },
-              output: { status: 'acknowledged', queue }
+          } catch (handlerErr) {
+            // The dead-letter policy decides what a failed handler costs: one more
+            // attempt (a copy carrying the advanced counter, then an ack of the
+            // original) or a rejection into `<svc>.dlq`. Until 2026-09-11 this
+            // branch was an unconditional `nack(msg, false, true)` with no counter,
+            // so a permanently failing message was redelivered for ever and the DLQ
+            // the topology declares was never reached from the client side
+            // (`docs/governance/confirmations/mq-consumer-contract.md` 002 point 3).
+            await this._applyDeliveryPolicy({
+              msg,
+              queue,
+              channelForMsg,
+              noAck,
+              error: handlerErr,
+              attempt,
+              policy,
+              onDeadLetter
             });
-
-            if (tracking) {
-              tracking.inFlight = Math.max(0, tracking.inFlight - 1);
-              tracking.lastCheck = Date.now();
-            }
           }
-        } catch (handlerErr) {
-          // The dead-letter policy decides what a failed handler costs: one more
-          // attempt (a copy carrying the advanced counter, then an ack of the
-          // original) or a rejection into `<svc>.dlq`. Until 2026-09-11 this
-          // branch was an unconditional `nack(msg, false, true)` with no counter,
-          // so a permanently failing message was redelivered for ever and the DLQ
-          // the topology declares was never reached from the client side
-          // (`docs/governance/confirmations/mq-consumer-contract.md` 002 point 3).
-          await this._applyDeliveryPolicy({
-            msg,
-            queue,
-            channelForMsg,
-            noAck,
-            error: handlerErr,
-            attempt,
-            policy,
-            onDeadLetter
-          });
+        } finally {
           if (tracking) {
             tracking.inFlight = Math.max(0, tracking.inFlight - 1);
             tracking.lastCheck = Date.now();
+            // The verdict is taken on BOTH edges (d.736a). Until this call the
+            // window was measured only while it FILLED, so "the queue came back
+            // under the threshold" was a fact nothing ever stated — measured in
+            // `api_delivery_endpoint`'s log on 2026-09-18: three warnings about
+            // one standing condition in 68 ms, and no line of any kind about its
+            // end. See `_checkPrefetchUtilization()`.
+            this._checkPrefetchUtilization(queue, tracking);
           }
         }
       };
@@ -4079,7 +4841,19 @@ class RabbitMQClient extends EventEmitter {
           // Re-register all consumers - use internal helper to avoid the "channel already open" check
           consumerReRegResult = await this._reRegisterConsumers();
           channelState.consumer = true;
-          this._logger.info('[RabbitMQClient] ✓ Consumer channel recreated');
+          // The same summary rule as `_ensureConsumerChannel()` (d.1003d, d.1003e): a
+          // recovery that left a consumer unattached is not a ✓ line.
+          if (consumerReRegResult.failed > 0) {
+            const unattached = this._unattachedConsumerQueues();
+            this._logger.warn(
+              `[RabbitMQClient] Consumer channel recreated, but ${unattached.length} consumer(s) are not attached: `
+                + `${unattached.join(', ')} (re-registered: ${consumerReRegResult.reRegistered}, failed: ${consumerReRegResult.failed})`
+            );
+          } else {
+            this._logger.info(
+              `[RabbitMQClient] ✓ Consumer channel recreated (re-registered: ${consumerReRegResult.reRegistered}, failed: ${consumerReRegResult.failed})`
+            );
+          }
         } catch (err) {
           this._logger.error('[RabbitMQClient] Failed to recreate consumer channel:', err.message);
           this._consumerChannel = null;
@@ -4187,7 +4961,7 @@ class RabbitMQClient extends EventEmitter {
    * Attach event handlers to publisher channel
    * @private
    */
-  _attachPublisherChannelHandlers(channel) {
+  _attachPublisherChannelHandlers(channel, role) {
     // One closure, one notification. amqplib announces a broker-side channel
     // death TWICE — `error` first, then `close` (measured against amqplib 0.10.9
     // on the live broker, 2026-09-12: a `checkQueue()` on a missing queue yields
@@ -4200,6 +4974,13 @@ class RabbitMQClient extends EventEmitter {
     // without a preceding `error`. The `error` handler only records WHY the
     // channel is dying, here, for the one notification to carry.
     channel._closeError = null;
+    // The publishes this channel is still carrying, and the snapshot of that number taken
+    // when a close frame arrives — `_closeFrameNamesThisSend()` is the one reader of both
+    // (d.723). Declared here because this is the one place a PUBLISHER channel is
+    // prepared, and a member nobody declared would make that reading answer for
+    // `undefined` instead of for a number.
+    channel._unconfirmedSends = 0;
+    channel._unconfirmedAtCloseFrame = null;
     channel._alive = true;
     channel.on('error', async (err) => {
       channel._alive = false;
@@ -4208,19 +4989,46 @@ class RabbitMQClient extends EventEmitter {
       }
       const reason = `Publisher channel error: ${err.message} (code: ${err.code || 'unknown'})`;
       channel._closeReason = reason;
+      // How many publishes this frame could possibly be an answer about (d.723). Taken
+      // HERE and nowhere else: amqplib emits `error` before `close`, and it is `close`
+      // that rejects the unconfirmed publishes — by the time their callbacks ask, the
+      // count has already been unwound. `_closeFrameNamesThisSend()` reads it.
+      channel._unconfirmedAtCloseFrame = channel._unconfirmedSends;
+      // WHY the channel is dying is recorded FIRST, for every reason there is.
+      //
+      // Since d.685a the publish path answers a refused send from this member
+      // (`_refusedSendPermanent()`), so a branch that returns before writing it leaves the
+      // publish path blind: the send reads a channel that died for no stated reason and
+      // calls it transient — retried `publishMaxRetries` times and then buffered, for a
+      // message the broker refused. The `'unknown delivery tag'` branch below did exactly
+      // that until d.696, and the frame it catches is a NUMBERED refusal like any other
+      // (measured live, d.693: `Error` with `code: 406`, arriving on this very event).
+      // Recording first and branching afterwards changes what the branch DOES in nothing.
+      channel._closeError = err;
 
-      // "unknown delivery tag" errors occur when channel closes during publish
-      // This is expected - the publish callback will handle retry
-      // We still log it but don't try to recreate channel (it's already closing)
-      if (err.message && err.message.includes('unknown delivery tag')) {
-        this._logger.warn(`[RabbitMQClient] [mq-client-core] Publisher channel error (channel closing during publish): ${err.message}`);
+      // A 406 ON THE PUBLISHER CHANNEL IS THE PUBLISH PATH'S BUSINESS, and the CODE is
+      // what says so (d.698).
+      //
+      // The publisher channel is a ConfirmChannel; this client sends no `basic.ack` on it,
+      // so the sentence this branch read until d.698 — `'unknown delivery tag'` — never
+      // reached it. What does reach it is the broker refusing the SEND with 406: a
+      // `user_id` property that is not the authenticated user (measured d.685a, `classId
+      // 60 / methodId 40`). That refusal is already answered where it belongs — the send
+      // reads this very `_closeError` and rejects the caller with a `PermanentPublishError`
+      // (`_refusedSendPermanent()`) — so raising it a second time as a client fault would
+      // report one event twice, once to the publisher and once to everybody.
+      //
+      // Only 406. A `404 NOT-FOUND` says nothing declares the exchange, which no publisher
+      // can fix and no caller of THIS message is the right audience for, and a codeless
+      // death is not an answer about any request at all: both stay raised, below.
+      if (err.code === AMQP_PRECONDITION_FAILED) {
+        this._logger.warn(`[RabbitMQClient] [mq-client-core] Publisher channel refused the send with ${AMQP_PRECONDITION_FAILED} (answered to the publisher): ${err.message}`);
         // Don't try to recreate - channel is already closing
-        // Don't emit error - publish callback will handle retry
+        // Don't emit error - the publish path answers the caller from `_closeError`
         return;
       }
-      
+
       this._logger.error(`[RabbitMQClient] [mq-client-core] ${reason}`);
-      channel._closeError = err;
       // Recovery is NOT started here — one rail, the `close` handler (d.261).
       this.emit('error', err);
     });
@@ -4242,15 +5050,37 @@ class RabbitMQClient extends EventEmitter {
       if (this._channel === channel) {
         this._channel = null;
       }
+      // The same obituary for the other send role (d.724). Without this line a dead
+      // telemetry channel would stay in its member and every later telemetry publish
+      // would be handed a corpse — `_ensurePublisherChannel('telemetry')` recreates only
+      // what it finds cleared.
+      if (this._telemetryChannel === channel) {
+        this._telemetryChannel = null;
+      }
       
       // Only try to recreate if connection is available
       // If connection is closed, reconnection logic will handle channel recreation
+      //
+      // Obnovuje se ROLE, která zemřela (d.1003b): tenhle handler visí na obou send
+      // kanálech a do d.1003b volal `_ensurePublisherChannel()` bez role — po smrti
+      // telemetry kanálu tedy „obnovil" živý publisher (no-op) a telemetry zůstal
+      // prázdný až do příští události.
       if (this._connectionAlive) {
         try {
-          await this._ensurePublisherChannel();
+          await this._ensurePublisherChannel(role);
         } catch (err) {
-          // Ignore errors during channel recreation if connection is closing
-          this._logger.warn(`[RabbitMQClient] [mq-client-core] Failed to recreate publisher channel (connection may be closing): ${err.message}`);
+          // Přechodné selhání obnovy (spojení odchází — d.1000/d.1003) je jen `warn`:
+          // kanál zůstane prázdný a příští publish ho po reconnectu obnoví sám
+          // (`_ensurePublisherChannel()`). Cokoli jiného je nehlášené selhání, a to
+          // má v tomhle klientovi kolej `error` (viz `_reportRecoveryFailure()`) —
+          // do d.1003 ho tenhle catch polykal jako `warn`, takže se o trvale
+          // nepoužitelném kanálu dozvěděl až první, kdo zkusil publikovat.
+          if (err instanceof TransientPublishError) {
+            this._logger.warn(`[RabbitMQClient] [mq-client-core] Failed to recreate ${role} channel (connection may be closing): ${err.message}`);
+          } else {
+            this._logger.error(`[RabbitMQClient] [mq-client-core] Failed to recreate ${role} channel after it closed: ${err.message}`);
+            this.emit('error', err);
+          }
         }
       }
     });
@@ -4305,12 +5135,27 @@ class RabbitMQClient extends EventEmitter {
         try {
           await this._ensureQueueChannel();
         } catch (err) {
-          // If connection is closing, this is expected - don't throw
-          if (err.message && err.message.includes('Connection closed')) {
+          // The connection is going away — amqplib's terminal-state class, measured
+          // live (d.693 step b): `createChannel()` on a closed connection answers
+          // `IllegalOperationError('Connection closed (by client)')`. The class is the
+          // fact; the sentence was only carrying it (d.696).
+          //
+          // It is read from `cause`, because the rail this failure travels wraps it:
+          // `_ensureQueueChannel()` answers with a `ConnectionError` naming the fix and
+          // keeps amqplib's object underneath. One level, and first-hand — that IS the
+          // wrapper's own cause, not a chain walked in hope. The rule itself has one
+          // body, `_connectionIsGoingAway()` (d.1003c), shared with the send and the
+          // consumer channel.
+          //
+          // Anything else is an unannounced failure and goes to `error` (d.1003c) —
+          // until then it was a `warn`, like the transient case. Recovery is NOT added
+          // here: the channel stays cleared and the next queue operation recreates it
+          // (`_requireQueueChannel()`), exactly as before.
+          if (this._connectionIsGoingAway(err.cause)) {
             this._logger.warn(`[RabbitMQClient] [mq-client-core] Queue channel close during connection closure (expected - reconnection will handle)`);
           } else {
-            // Log but don't throw - channel will be recreated on next use or during reconnection
-            this._logger.warn(`[RabbitMQClient] [mq-client-core] Failed to recreate queue channel: ${err.message} (will be recreated on next use)`);
+            this._logger.error(`[RabbitMQClient] [mq-client-core] Failed to recreate queue channel after it closed: ${err.message} (the next queue operation tries again)`);
+            this.emit('error', err);
           }
         }
       } else {
@@ -4365,8 +5210,19 @@ class RabbitMQClient extends EventEmitter {
         try {
           await this._ensureConsumerChannel();
         } catch (err) {
-          // Ignore errors during channel recreation if connection is closing
-          this._logger.warn(`[RabbitMQClient] [mq-client-core] Failed to recreate consumer channel (connection may be closing): ${err.message}`);
+          // Táž kolej jako u send kanálu (d.1003b): selhání, které jen hlásí odcházející
+          // spojení, je `warn` — reconnect kanál obnoví a konzumenty zaregistruje znovu.
+          // Cokoli jiného je nehlášené selhání a jde na `error`; do d.1003b ho tenhle
+          // catch polykal jako `warn`, takže konzumenti tiše přestali dostávat zprávy.
+          // `_ensureConsumerChannel()` odpovídá `ConnectionError` s chybou amqplibu
+          // v `cause` — jeden článek, vlastní příčina obalu (vzor obnovy frontového
+          // kanálu níž, d.696).
+          if (this._connectionIsGoingAway(err.cause)) {
+            this._logger.warn(`[RabbitMQClient] [mq-client-core] Failed to recreate consumer channel (connection may be closing): ${err.message}`);
+          } else {
+            this._logger.error(`[RabbitMQClient] [mq-client-core] Failed to recreate consumer channel after it closed: ${err.message}`);
+            this.emit('error', err);
+          }
         }
       }
     });
@@ -4389,6 +5245,42 @@ class RabbitMQClient extends EventEmitter {
    * The threshold itself is unchanged and no new one is introduced: a window
    * larger than one message is measured exactly as before.
    *
+   * THE VERDICT IS TAKEN ON THE TRANSITION, BOTH WAYS (d.736a). Until this batch
+   * the check ran only while the window FILLED, and it spoke every time it found
+   * the condition standing. MEASURED (`api_delivery_endpoint`, 2026-09-18,
+   * one consumer):
+   *
+   *     08:00:10.928 WARN … queue 'delivery.health.events' has 8/10 … (80%)
+   *     08:00:10.995 WARN … queue 'delivery.health.events' has 8/10 … (80%)
+   *     08:00:10.996 WARN … queue 'delivery.health.events' has 9/10 … (90%)
+   *
+   * — three lines in 68 ms about ONE standing condition, and never a line saying
+   * the queue came back under the threshold. The operator reading that log can
+   * see an alarm start and can never see it end, which makes the line unusable
+   * for the only question it exists to answer.
+   *
+   * The shape is the one the monitoring concept settled the same day: a rail that
+   * says a standing condition ONCE — OPEN states it, everything after it is the
+   * same episode, and the end is a RECORD rather than a second alarm
+   * (`infra/api_monitoring`, `c996215c` telemetry-intake rejections, `1b1c3912`
+   * registry health events; `watchers/alertLifecycle.js`
+   * § closeRecoveredInfrastructureAlerts: "each episode's one message went out
+   * when it opened"). This library keeps no episode store, so its record is the
+   * log: the onset stays a `warn`, the return is one `info`.
+   *
+   * WHAT DOES NOT CHANGE: the callback and the `prefetch:high-utilization` event
+   * still announce the onset, with the same payload — they simply fire once per
+   * episode now. The return gets no callback and no event of its own: both would
+   * be a declaration with no consumer anywhere in this workspace
+   * (`change-discipline.md` § Removing something removes its declaration), while
+   * the log line has a measured reader.
+   *
+   * NO HYSTERESIS is introduced. Monitoring damps a flapping subject with a floor
+   * taken from configuration, and it needs one because a notification stands
+   * behind each of its episodes; here the episode is a log line, and a floor
+   * written into this file would be a number with no owner
+   * (`architecture-principles.md` §2). The edge alone removes the repetition.
+   *
    * @private
    * @param {string} queue - Queue name
    * @param {Object} tracking - Prefetch tracking object
@@ -4399,38 +5291,65 @@ class RabbitMQClient extends EventEmitter {
     }
 
     if (tracking.prefetchCount <= 1) {
-      return; // One-message window: 0 % or 100 %, and 100 % is the working state.
+      // One-message window: 0 % or 100 %, and 100 % is the working state. There is
+      // no condition to stand, so an episode carried over from a larger window
+      // (the prefetch of a re-registered consumer can change) ends here — silently,
+      // because what it was measured against no longer exists.
+      tracking.utilizationHigh = false;
+      return;
     }
 
     const utilization = tracking.inFlight / tracking.prefetchCount;
-    
-    if (utilization >= this._prefetchUtilizationThreshold) {
-      const message = `Prefetch utilization high: queue '${queue}' has ${tracking.inFlight}/${tracking.prefetchCount} messages in-flight (${Math.round(utilization * 100)}%, threshold: ${Math.round(this._prefetchUtilizationThreshold * 100)}%)`;
-      this._logger.warn(`[RabbitMQClient] [mq-client-core] ⚠️ ${message}`);
-      
-      // Call alert callback if provided
-      if (this._prefetchAlertCallback) {
-        try {
-          this._prefetchAlertCallback(queue, utilization, tracking.inFlight, tracking.prefetchCount);
-        } catch (alertErr) {
-          this._logger.error(`[RabbitMQClient] [mq-client-core] Prefetch alert callback error:`, alertErr.message);
-        }
+    const high = utilization >= this._prefetchUtilizationThreshold;
+
+    if (high === tracking.utilizationHigh) {
+      return; // The same condition as at the last verdict — it has already been said.
+    }
+
+    tracking.utilizationHigh = high;
+
+    const state = `queue '${queue}' has ${tracking.inFlight}/${tracking.prefetchCount} messages in-flight (${Math.round(utilization * 100)}%, threshold: ${Math.round(this._prefetchUtilizationThreshold * 100)}%)`;
+
+    if (!high) {
+      // The end of the episode: a record, not an alarm.
+      this._logger.info(`[RabbitMQClient] [mq-client-core] Prefetch utilization back below threshold: ${state}`);
+      return;
+    }
+
+    const message = `Prefetch utilization high: ${state}`;
+    this._logger.warn(`[RabbitMQClient] [mq-client-core] ⚠️ ${message}`);
+
+    // Call alert callback if provided
+    if (this._prefetchAlertCallback) {
+      try {
+        this._prefetchAlertCallback(queue, utilization, tracking.inFlight, tracking.prefetchCount);
+      } catch (alertErr) {
+        this._logger.error(`[RabbitMQClient] [mq-client-core] Prefetch alert callback error:`, alertErr.message);
       }
-      
-      // Emit event for external listeners
-      this.emit('prefetch:high-utilization', {
-        queue,
-        utilization,
-        inFlight: tracking.inFlight,
-        prefetchCount: tracking.prefetchCount,
-        threshold: this._prefetchUtilizationThreshold,
-        timestamp: new Date().toISOString()
-      });
     }
+
+    // Emit event for external listeners
+    this.emit('prefetch:high-utilization', {
+      queue,
+      utilization,
+      inFlight: tracking.inFlight,
+      prefetchCount: tracking.prefetchCount,
+      threshold: this._prefetchUtilizationThreshold,
+      timestamp: new Date().toISOString()
+    });
   }
 
   /**
    * Start periodic prefetch monitoring
+   *
+   * WHAT IS LEFT FOR THIS TICK TO SAY since d.736a: the verdict is taken on both
+   * edges of every delivery (`consume()`), and `_checkPrefetchUtilization()` returns
+   * in silence when the condition is the one already announced — so a tick that sees
+   * the same `inFlight` and the same `prefetchCount` says nothing. It speaks only
+   * where the verdict changed without a delivery in between, and the one quantity
+   * that can move that way is `prefetchCount`: a consumer re-registered with a
+   * different window (`_applyConsumerPrefetch()`).
+   *
    * @private
    */
   _startPrefetchMonitoring() {
@@ -4438,7 +5357,7 @@ class RabbitMQClient extends EventEmitter {
       return; // Already started
     }
     
-    this._prefetchCheckTimer = setInterval(() => {
+    this._prefetchCheckTimer = this._setInterval(() => {
       const now = Date.now();
       for (const [queue, tracking] of this._prefetchTracking.entries()) {
         // Only check if we have recent activity (within last 30s)
@@ -4457,7 +5376,7 @@ class RabbitMQClient extends EventEmitter {
    */
   _stopPrefetchMonitoring() {
     if (this._prefetchCheckTimer) {
-      clearInterval(this._prefetchCheckTimer);
+      this._clearInterval(this._prefetchCheckTimer);
       this._prefetchCheckTimer = null;
     }
   }
@@ -4736,10 +5655,12 @@ class RabbitMQClient extends EventEmitter {
       this._consumerChannel.ack(msg);
       msg._mqProcessed = true;
     } catch (err) {
-      const m = err && err.message ? err.message : '';
-      if (m.includes('unknown delivery tag') || m.includes('PRECONDITION_FAILED') || m.includes('Channel closed')) {
+      // The same reading as the auto-ack inside `consume()` — see the note there (d.698).
+      // amqplib's terminal-state class is the only thing `ack()` throws; anything else
+      // reaching this catch came from outside amqplib and is a defect that must be heard.
+      if (err instanceof IllegalOperationError) {
         msg._mqProcessed = true;
-        this._logger.warn('[RabbitMQClient] [mq-client-core] Cannot ack - consumer channel is closed/recreated (delivery tag invalid)', { error: m });
+        this._logger.warn('[RabbitMQClient] [mq-client-core] Cannot ack - consumer channel is closed/closing (the broker returns the unacked delivery)', { error: err.message });
         return;
       }
       this.emit('error', err);
@@ -4777,10 +5698,10 @@ class RabbitMQClient extends EventEmitter {
       this._consumerChannel.nack(msg, false, requeue);
       msg._mqProcessed = true;
     } catch (err) {
-      const m = err && err.message ? err.message : '';
-      if (m.includes('unknown delivery tag') || m.includes('PRECONDITION_FAILED') || m.includes('Channel closed')) {
+      // The same reading as `ack()` above (d.698): the class amqplib refuses a call with.
+      if (err instanceof IllegalOperationError) {
         msg._mqProcessed = true;
-        this._logger.warn('[RabbitMQClient] [mq-client-core] Cannot nack - consumer channel is closed/recreated (delivery tag invalid)', { error: m });
+        this._logger.warn('[RabbitMQClient] [mq-client-core] Cannot nack - consumer channel is closed/closing (the broker returns the unacked delivery)', { error: err.message });
         return;
       }
       this.emit('error', err);