Module version 

The version tool (spec/surface §4, 1.4): which engine and which versions — the serving binary’s own, every component crate’s, the spec versions they were built against, the database schema, the MCP protocol, the runtime, the build’s commit and time.

Who knows what. This crate knows the components (every omgbase-* crate and oqx are its dependencies, each with a VERSION and a SPEC_VERSION), the schema (the open store) and the protocol revision the catalog is written against. It does not know the binary: the omgbase crate depends on this one, not the other way round, so the host passes a BuildInfo — its version, its spec/cli version, the build’s commit and time (build.rs), the compiler. Without one (a library embedding) the tool answers with this crate’s own version and nulls, which is the shape the fixture runner records. Port of packages/core/src/version.ts.

Structs

BuildInfo

What the serving binary knows about itself.

Constants

MCP_PROTOCOL_VERSION

The MCP protocol revision the catalog (§4) is written against and the omgbase binary serves by default when a client names none (the reference’s SDK LATEST_PROTOCOL_VERSION). A client’s own revision is echoed at initialize; the four methods the server speaks are identical across revisions.

Functions

version_info

The version result: { engine, version, components, specs, schema, mcp, runtime, commit, built }. store supplies schema (its PRAGMA user_version; null without one).