v0.7.0

mentra v0.7.0 / mentra-provider v0.3.0

Mentra v0.7.0 is a provider and coding-agent release. It expands the runtime
with MCP support, safer shell execution primitives, provider-core embeddings,
custom compatible endpoints, and a fuller Responses API client for manual
coding-agent setups.

Highlights

MCP and Runtime Tooling

• Add a Model Context Protocol client, manager, protocol types, bridge, and test
  coverage so MCP tools can participate in Mentra runtimes.
• Add bash command validation for shell-tool execution.
• Add workspace-bounded runtime policies and sandbox detection helpers.
• Add Session::set_model(...) for runtime model switching.
• Emit usage-report events with token counts.

Provider-Core Improvements

• Add provider-core embedding contracts and a Responses embedding provider.
• Add custom provider-core endpoint registration so applications can target
  compatible OpenAI, Responses, and Anthropic-style services.
• Add Anthropic prompt caching controls through cache-control markers.
• Preserve and expose richer provider response metadata for runtime consumers.

Responses API and xipe

• Add ResponsesStateMode::{ReplayOnly, Hybrid, Stateful}.
• Track streamed response ids and send previous_response_id when provider
  state is enabled.
• Retry hybrid HTTP/SSE requests without previous_response_id when provider
  state is unavailable or rejected.
• Add first-class WebSocket transport for Responses streams.
• Send xipe-compatible WebSocket response.create frames with request fields at
  the top level.
• Default Responses function tools to strict: false unless a tool explicitly
  opts into strict mode.
• Refresh x-codex-turn-state across HTTP and WebSocket paths.
• Add a manual coding-agent guide for Mentra + Responses + xipe.

Compatibility and Migration

• Publish mentra-provider 0.3.0 before publishing mentra 0.7.0.
• mentra 0.7.0 depends on mentra-provider 0.3.0.
• HTTP/SSE remains the default Responses transport.
• ResponsesStateMode::Hybrid is the recommended coding-agent default because
  local transcript replay remains authoritative while provider-side state is
  used opportunistically.
• Existing built-in shell and files tool schemas stay flexible because
  Responses function tools serialize as non-strict by default.

Verification

This release is expected to pass:

• cargo fmt --all --check
• cargo clippy --workspace --all-targets -- -D warnings
• cargo test --workspace

Live xipe smoke testing also covered gpt-5.4-mini over HTTP/SSE and
WebSocket Responses transports.