newton-core 0.4.16

newton protocol core sdk
//! Protocol-level JSON-RPC wire schemas shared between gateway and operator.
//!
//! Endpoints where the gateway forwards verbatim to operators
//! (per `.claude/rules/agent-guide.md` "Operator-Exposed RPC Endpoints")
//! ship their request/response types here in `core` because both crates
//! depend on `core` and neither should depend on the other:
//!
//! - `gateway -> operator` would force the gateway to pull every operator
//!   transitive dep (state-tree, IPFS host fetch, full WASM toolchain) just
//!   to read three structs.
//! - `operator -> gateway` would invert the orchestration / worker
//!   boundary.
//!
//! Operators own the handler implementation; the gateway forwards requests
//! through `broadcast_first_success` and overlays gateway-set fields on the
//! way out (e.g., promoting `status` to `Confirmed` and attaching
//! `commit_sig` from on-chain `StateCommitRegistry` for finalized reads).

pub mod signed_read;
pub mod state_commit;