v11.04 — 2026-08-06
Primary consumers: SPAs (for example React), mobile applications, and LLM/agent clients. The API contract should also convert cleanly into MCP/tool definitions without inventing a second API design.
Scope: API design first — goals, boundaries, routes, parameters, payloads, headers, status codes, errors, discovery, and machine-readable contracts. This is not general implementation, deployment, or authentication-infrastructure guidance. Narrow enforcement notes appear only when they are needed to preserve the prescribed wire contract consistently.