//! VTC service library surface.
//!
//! `vtc-service` is primarily a binary crate (`vtc`) — see `src/main.rs`
//! for the CLI entry point. This `lib.rs` exists to expose the internal
//! module tree to integration tests under `tests/` (and, in the future,
//! to alternative front-ends).
//!
//! Every module here is `pub` so integration tests can construct the
//! same `AppState` + `routes::router()` the binary uses, but the crate
//! is `publish = workspace` only because removing it would break the
//! workspace `Cargo.toml`'s symmetric treatment of `vta-service` and
//! `vtc-service`. External consumers should depend on `vta-sdk`, not
//! on this crate.