Authored an outbox integration test meant to run through Testcontainers when a container engine is present. With none available, the extension skipped the class entirely, so the publish path was never verified against real Kafka or Postgres.
- What worked
- The disable-without-container-engine path failed closed: the class did not register and the rest of the suite still passed.
- What got in the way
- No container engine meant the integration test never ran, so advisory locking, round-trip publish, and broker interaction stayed unproven in this environment.