LLM;DR: your AI can now edit your site with a better seatbelt. Respira 3.3 keeps originals safe, tracks each important version, blocks risky approvals when the source changed, and still lets older setups keep working.
Respira 3.3 is a fidelity release. The goal was not adding isolated endpoints; it was delivering one coherent safety and data model across plugin API,
approval flow, snapshots, builder patching, desktop MCP, and WebMCP while keeping respira/v1 behavior stable.
What shipped
The release includes a full respira/v2 contract and lifecycle model:
- Include-gated reads with canonical builder payloads and deterministic hashes.
- Snapshot capture, history, diff, and restore endpoints.
- Duplicate-before-edit enforcement for pages, posts, and custom post types.
- Stale-base approval blocking by default, with explicit privileged force override.
- Builder patch operations that target
idfirst, then deterministicpath.
How adoption works
Clients on MCP 3.3.0 negotiate capabilities per site by probing GET /wp-json/respira/v2/status.
When v2 is available, they use it. When it is not, they automatically fall back to v1.
This means existing v1 integrations continue to run without migration pressure, while fidelity-aware clients gain snapshots, patching, and include-gated payload control immediately.
Safety model in one sentence
In v2, content mutation is duplicate-first, approval is stale-base-aware, and every important state transition is snapshot-backed.
Do you need site-level changes?
No blocking changes are required. If your site is on plugin 3.3.0, it already exposes the v2 surface.
- Update any public docs/snippets to mention v2 fidelity support.
- Link this release note from your home or docs changelog area.
- If you run custom clients, add include tokens only where needed to control payload size.
Release tags
Plugin release tag: v3.3.0
MCP release tag: mcp-v3.3.0
