//! Deployment state management — trait, types, backends, and factory.
//!
//! WHY: The deployment engine needs persistent, backend-agnostic state to track
//! what's deployed, detect config changes, and coordinate rollbacks.
//!
//! WHAT: `StateStore` trait with six interchangeable backends (JSON files,
//! `SQLite`, libsql, Turso, Cloudflare R2, Cloudflare D1), plus helpers
//! and a factory for auto-detection.
//!
//! HOW: All backends implement the same `StateStore` trait. I/O methods return
//! `StateStoreStream<T>` (lazy iterators). The factory selects a backend
//! from environment variables.
// Re-exports for convenience
pub use FileStateStore;
pub use config_hash;
pub use ;
pub use StateStore;
pub use ;