{"version":"2.1.257","anchor":"command-queues-discardconsume-events-centralized-via-a-new","canonical_anchor":"command-queues-discardconsume-events-centralized-via-a-new","heading":"Command queue's discard\/consume events centralized via a new emitter registry","tier":"internal","area":"Teammates","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/command-queues-discardconsume-events-centralized-via-a-new","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### Command queue's discard\/consume events centralized via a new emitter registry\n\nCommand-queue events move to a shared registry, and peer-message admission failures are now recorded first.\n\nThe internal `dun()` command-queue constructor now gets its `commandsDiscarded`\/`commandsConsumed` event emitters from a shared `Z6e()` registry instead of module-level singletons. Peer-message admission failures are now also recorded through a `peer_loop_guard` telemetry call before falling back to the existing hop-chain\/queue-full admission checks.\n\n- Area: Teammates\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}