Release v0.11.0 - 2026-05-09

Highlights

Added an interactive Akuma query endpoint that wraps HTTP 200 responses in a typed { status, result } envelope so clients can branch on an explicit status field instead of inspecting the result body.
Updated the public SDKs and MCP server with typed methods, request/response schemas, and tool definitions for the new interactive query surface.
Surfaced structured response bodies on SDK errors so callers can read the JSON returned by the API, including auth and rate-limit errors, directly off the typed error.

Added an interactive query endpoint at /v1/akuma/queries/interactive. The existing /v1/akuma/query endpoint and SDK methods continue to work for current callers and are not deprecated by this release.
Interactive HTTP 200 responses carry an envelope whose status is currently completed or rejected. Completed envelopes carry a result body and never carry result.error; rejected envelopes carry a result body whose error is non-empty. If a rejected envelope includes result.sql, callers must not treat that SQL as verified or executable.
Non-2xx responses from the interactive endpoint are not wrapped in the envelope. The body may be either a standard error response or an Akuma query response with an application-level error, so clients should not rely on HTTP status alone when parsing non-2xx interactive bodies.

Added a typed queryInteractive method that returns the { status, result } envelope. The full raw HTTP 200 envelope is also exposed on the response object so callers can inspect any fields the SDK does not model directly.

Added an interactive Akuma query service method with a typed envelope dataclass. Unrecognized fields on the HTTP 200 envelope are preserved on the returned object for inspection.
Strict response validation raises a typed KaizenError when the envelope does not satisfy the documented status / result / error contract.

Added a QueryInteractive client method that returns the { status, result } envelope. The full raw HTTP 200 envelope is exposed alongside the typed fields so callers can inspect any fields the SDK does not model directly.

Added an akuma.query_interactive tool. HTTP 200 envelopes whose status is anything other than completed are returned with the tool result error flag set, and the full envelope is mirrored into structured content so callers can branch on the dispatched shape.

Updated the public API docs, SDK docs, and MCP docs for the new interactive Akuma query endpoint, MCP tool, and request/response shapes.