@lssm-tech/integration.lssm-os-queue-rabbitmq
Optional RabbitMQ quorum-queue wake-up acceleration for an existing SQL-authoritative LSSM OS durable queue. The adapter requires publisher confirms, manual consumer acknowledgements, dead lettering, and an exact qualification-bound vhost/exchange/queue/routing identity.
SQL remains the only durable admission, claim, fence, reconciliation, and effect completion authority. RabbitMQ messages carry only immutable envelope and outbox identifiers/digests. A broker delivery is acknowledged only after the corresponding SQL acknowledgement is valid and durable. Malformed messages are negatively acknowledged without requeue so a qualified dead-letter policy can contain poison.
The package accepts a static structural channel. It does not load an AMQP SDK, connection URL, credential, or arbitrary module. Broker loss degrades to SQL polling; publisher-confirm ambiguity is reconciled from the SQL outbox.
Run bun run qualify:local after pulling
rabbitmq:4.3.5-management-alpine for exact standalone local-live evidence. The qualification-only amqplib client declares durable exchanges, a quorum work queue, a quorum dead-letter queue, manual acknowledgements, bounded prefetch, a delivery limit, and mandatory publishing. It proves confirmed publish, unroutable return, durable-ack ordering, unacked consumer-death redelivery, poison dead lettering, broker state restart persistence, dynamic Docker port recovery, and SQL-authoritative claim fallback while the broker is stopped.
The disposable broker binds only an ephemeral 127.0.0.1 AMQP port, uses an ephemeral generated credential and vhost, persists state in an exact temporary host directory, and removes both the container and directory on every exit path. This is single-node local-live evidence; multi-node quorum leader loss, minority partitions, TLS, production vhost/user policies, sustained scale, and managed operations remain release blockers.
