integration.lssm-os-ingress-mqtt

LSSM OS MQTT ingress

This package accepts qualified MQTT 3.1.1/5.0 publications and normalizes them through an injected trusted normalizer into the durable LSSM OS inbox. MQTT is never a work queue or execution-authority source. Topic scope, QoS, session, expiry, authentication reference, payload bounds, and exact broker capability are validated before durable admission. Business execution still requires the ordinary Runtime Node operation, Connect decision, work order, claim, and fence.

Production composition uses createMqttIngressBrokerV2. It binds the MQTT transport profile separately from the authoritative durable-queue profile, requires both components to share exact scope/topology/generation, and accepts only a source-digest-bound durable admission receipt. The additive createDurableQueueIngressV1 runtime helper derives the outbox identity from the immutable publication digest and admits through the existing Durable Queue V2 port. PostgreSQL can therefore remain the complete queue and inbox authority while MQTT supplies only authenticated ingress.

createMqttIngressBrokerV1 remains available as a compatibility-only single-binding constructor. New deployments should not use it to claim an independently qualified MQTT transport and SQL durability component.