//! The caller-owned resume-state boundary, in frame vocabulary.
//!
//! The F-0c characterization proved cursor/resume-state persistence is
//! CALLER-owned while the substrate owns barrier ordering (commit-seal →
//! persist → release) — F-0c-FINDINGS §R4. This trait is that boundary at
//! frame-conv's seam; the crate adapts it to the substrate internally so no
//! substrate type appears in the public surface.
use crateStoreError;
/// Durable storage for a participant's canonical resume-state bytes.
///
/// Implementations must durably replace the previously committed bytes
/// before returning `Ok(())` — the substrate's write-ahead barrier releases
/// operation authority only after this boundary succeeds.