//! kasl-server as a library.
//!
//! The binary is a thin wrapper: configuration, a pool, migrations, then
//! `app::router`. Everything else lives here so integration tests can drive
//! the real router and the real provisioning path instead of a copy that
//! drifts from what ships.
/// The embedded migrations, applied on startup and by the tests.
///
/// Declared here rather than at each call site so there is one answer to "what
/// schema does this build carry" - the binary and the test suite cannot end up
/// migrating differently.