//! [`PostgresOutboxStore`]: construction, `enqueue`, and the `OutboxStore`/`OutboxEnqueue`/
//! `OutboxDeadLetters` implementations, split by concern (RELIAR-65) — `outbox_store` (the type,
//! construction, shared helpers, plus the `OutboxStore` trait impl itself), `schema`
//! (`search_path` verification), `enqueue` (the whole `OutboxEnqueue` impl), `claim` (`acquire`'s
//! body), `outcomes` (`complete`/`fail`/`release`/`extend_lease`'s bodies), `purge`
//! (`purge`/`stats`'s bodies), `dead_letters` (the whole `OutboxDeadLetters` impl). Only
//! `OutboxStore` follows the "impl in `outbox_store.rs`, body per method in its concern module"
//! shape, so a reader who wants "what does `acquire` return" starts there regardless of where the
//! body lives; `OutboxEnqueue` (`enqueue.rs`) and `OutboxDeadLetters` (`dead_letters.rs`) are
//! small enough that their whole impl — signature and body — lives in one concern module instead.
pub use PostgresOutboxStore;