Everruns 0.18.0: The 0.18 neutral-kernel boundary

Highlights

• The 0.18 neutral-kernel boundary: everruns-core is now a neutral execution kernel. Hosted platform records, sessions, agents and agent versions, harnesses, evals and observers, connectors, system email, feature flags, and OAuth/credential infrastructure, moved out to everruns-platform (and sibling crates), and the logic-free everruns-runtime compatibility crate was removed. REST/gRPC shapes and stored schema are unchanged; see the 0.18 migration guide and the Breaking notes below (#3160, #3101).
• Engine-owned sessions and unified execution: Engines now own the session lifecycle, and a single execution path serves both in-process and durable runs (#3179, #3173, #3167).
• Multi-head workspaces: Framework workspaces now support multiple heads (#3166).
• Metered embedding spend: Retrieval and knowledge-index embedding spend is now metered and ledgered against the organization (#3149, #3163).
• Chats as core functionality: Chats is always present in navigation and search for every organization with no feature opt-in, and now supports chat pinning.

In the changelog

• Chats is on for every organization, with pinned chats
• Session recordings split into Transcript, Timeline and Events
• Knowledge index embedding spend is metered and ledgered
• Framework workspaces gain multiple isolated Git heads
• everruns-core 0.18 becomes a neutral execution kernel

Before upgrading, read the breaking changes: everruns-core 0.18 becomes a neutral execution kernel.

See the GitHub release and the full release notes for every pull request in this version.