Crate spt_runtime 

spt-core harness contract — outbound half (M2a).

spt-runtime makes spt-core drivable by a manifest-described harness with zero Claude Code (or any harness) conventions in-repo. It is the fourth layer in the acyclic stack (spt-proto -> spt-store -> spt-msg -> spt-runtime).

Two surfaces land here across M2a:

• the runtime-manifest schema + parse/validate (manifest, T1), and
• the AgentRuntime trait + default ManifestRuntime (opaque-template substitution + spawn-session seam, T2).

The inbound half (the spt api subcommand surface) lives in the spt binary over this crate. See M2a-PLAN.md.

Re-exports

pub use manifest::Manifest;

pub use manifest::ManifestError;

pub use profile::merge_leaf_replace;

pub use profile::split_option;

pub use runtime::run_bounded_command;

pub use runtime::AgentRuntime;

pub use runtime::BoundedOutput;

pub use runtime::ManifestRuntime;

pub use runtime::RuntimeError;

pub use runtime::Spawned;

Modules

manifest

Runtime-manifest schema — the typed form of [docs/MANIFEST.md].

profile

Adapter-profile overlay merge — leaf-replace semantics (CONTEXT.md §adapter profile).

registry

Adapter registration lifecycle (M5-D2, REQ-INSTALL-4) — the node-local registered-adapter set under {SPT_HOME}/adapters/.

runtime

The outbound contract: turn a parsed Manifest role template into a real process. Two surfaces: