Embedding contract (in-process)

oxc-runtime and oxc-serve are publish = false: there is no crates.io artifact, no semver guarantee, and no docs.rs. Embedding the runtime in-process from Rust means a git dependency on the workspace against APIs that are documented at intent level (the crates’ AGENTS.md nodes) but are not a stable, versioned contract. The semantic contract is the OxbinRuntime trait (The OxbinRuntime trait surface); the serving surface (Serving surface) is the supported boundary for everyone else. Prefer the HTTP surface unless you specifically need in-process embedding.

The in-process Store is the mem backend: durable Postgres serving is reached through the served async adapter (PgOxbinRuntime), via ox runtime serve --storage pg, not by constructing a Store and selecting pg. The HTTP serving surface (Serving surface) sits above the in-process surface — it uses the served pg adapter rather than in-process Store pg — so an integration over HTTP is the lower-risk path.