hypercall_api/boundary/engine.rs
1//! Engine runtime ports.
2//!
3//! The canonical definitions live in `hypercall-runtime-api`. They are
4//! re-exported here so existing `crate::boundary::engine::*` consumers keep
5//! working unchanged.
6
7pub use hypercall_runtime_api::boundary::engine::{
8 EngineJournalReader, EngineStateDigest, EngineStateDigestProvider, TransactionRequestJournal,
9};