Respira 8.0 Canopy: plugin, MCP server and WooCommerce add-on

Hi,

Until now Respira spoke sixteen page builders, and treated WordPress’s own Site Editor as a generic fallback. It now speaks that too: block templates, synced patterns, the block navigation menu and design tokens, on the same staged-safety contract as everything else.

A navigation link changes by exact block path rather than by rewriting your whole menu, and a write reports verified only after WordPress has actually rendered it. Structural writes to site-level objects are off by default and opt in per site, so nothing changes on your sites until you say so.

If you run a WooCommerce store on a block theme, the add-on is the part to read about. Its storefront tools used to look for page-builder markup and give up when they found none. They now try the native block path first.

What to update

• The WordPress plugin, to v8.0.1. Update from your Plugins screen.
• The MCP server, to v8.0.1. Most clients pick this up on restart.
• The WooCommerce add-on, to v4.0.0, if you use it. Update from your Plugins screen.

Update the plugin and the add-on first, then the MCP server. The newer server expects the newer plugin.

8.0.1 is a small follow-up on top of 8.0: OAuth discovery no longer depends on a path some managed hosts reserve, the admin header no longer reports a connection that is not there, and the config file path resolves correctly on Windows. The changelog below covers 8.0 itself.

Read the full release notes, with the visuals and every change: https://www.respira.press/canopy

Update or download: https://www.respira.press/dashboard/downloads

---

Full changelog

Plugin v8.0.0

• Native FSE structure service for templates and template parts with hierarchy/source discovery, exact block-path operations, stale-write fingerprints, structural proposals, snapshots, normalized diffs, cache invalidation, and stored/frontend verification.
• Native user-pattern and block-navigation editing on the same structural contract: registered theme/plugin patterns remain read-only; editable user patterns support synced/unsynced state; navigation responses include compact nested paths; referenced deletes are refused by default; and successful writes require read-back plus WordPress server-render verification.
• First-class Site Editor and Gutenberg design-token MCP surfaces.
• Agent-facing activity list/detail endpoints linking audit entries to snapshots, proposals, approvals, and rollbacks.
• Shared mutation-result contract for dry runs, pending approvals, verified writes, stored-but-unverified writes, rollbacks, and failures.
• Ability discovery now labels results as Respira-native, inhaled, unavailable, or replaced by a safer Respira workflow and returns the preferred next tool.
• Rewriting a Divi Theme Builder global layout now requires explicit confirmation. update_theme_builder_template refuses the first call with respira_tb_live_edit_confirmation_required, naming the layout and stating that the change hits every page using it and goes live rather than waiting for approval. Re-send with confirm_live_edit=true to proceed. Same handshake update_page and delete_page use for force-editing an original. This is a confirmation, not staging: a global layout cannot be staged on a duplicate the way a page can, because Divi resolves the assigned layout by id and a second copy would compete with the original rather than stand in for it. Creating a layout is deliberately not gated, since it already refuses to replace an existing global. Real staging for globals is next.
• Plugin activation now performs dependency and platform preflight, activates in a signed one-time fresh request, probes REST/frontend boot, and narrowly rolls back only the newly activated plugin on failure.

MCP server v8.0.0

• wordpress_update_theme_builder_template now advertises and requires confirm_live_edit. Rewriting a Divi global header, footer or body changes every page that uses it and goes live with no approval step, so the plugin refuses the first call. The tool schema advertises the parameter and the description states the blast radius, so a model can tell the user what is about to change before it calls. Requires plugin 8.0.0+; against an older plugin the parameter is simply ignored and behaviour is unchanged.
• upload_media accepts Windows paths and file:// URIs again. A C:\Users\...\photo.jpg path, or any file:// URI, was not recognised as a local file and fell through to the base64 branch, where it decoded to garbage and uploaded a corrupt file rather than failing. Restores the 7.5.x behaviour, which 8.0 had lost by carrying a narrower inline check than the one that shipped.
• Two WordPress installs on the same hostname stay two sites. A site id was derived from the hostname alone, so example.com and example.com/blog both became example-com and the second silently replaced the first: you configured two sites and saw one, with no error. The id now includes the port and the URL path. A config written by an older server is healed in place when the paths disambiguate it, and a genuine duplicate is refused rather than booted with ambiguous routing.
• The handshake that could not shake hands: respira_move_element, respira_reorder_elements, respira_remove_element, respira_duplicate_element and respira_batch_update now expose edit_target (and its editTarget alias) plus confirm_live_edit in their schemas. Previously the live-edit confirmation flow told agents to re-call with parameters the schemas did not advertise, so strict MCP clients rejected the retry and live writes through these five tools could never complete. respira_update_element already had the params; the other element ops now match it, including the same camelCase normalization toward the plugin. (Elementor, move + reorder).
• First-class FSE template/template-part and Gutenberg design-token tools.
• Ten Respira-native Site Editor tools for user patterns and block navigation: source-aware pattern discovery, synced/unsynced pattern creation, compact nested navigation traversal, exact block-path updates, stale/wrong-target protection, reference-aware deletion, structural proposals, snapshots, read-back checks, and explicit server-render verification.
• Bounded WooCommerce revenue, time-series, top-product, order, and customer reporting; safe store-configuration discovery; and approval-gated native webhook management.
• Agent-facing activity history with compact diffs and snapshot/proposal/rollback links.

WooCommerce add-on v4.0.0

• Storefront intelligence is now FSE-first with page-builder fallback. On a block theme, analysing a shop page returns real structural analysis against the native archive-product template instead of "no page builder detected". The two badge tools are FSE-only by design.
• Sale and low-stock badges are POSITIONED: they anchor inside the product image, matching WooCommerce's own card structure, instead of being appended after the add-to-cart button. If a badge is already present the write is refused as a no-op rather than duplicating it.
• Added product-card field addressing: discover the card's composition and set attributes on one named field, by canonical WooCommerce block name. Attributes are intersected with the installed block's registered attributes, so an unrecognised key is refused rather than written and reported as success.
• update_checkout_layout no longer returns "no page builder detected" on a block theme. It returns the honest capability error its sibling tools already returned.
• The missing-changes error no longer advertises a parameter that does not exist. It names only the keys the handler reads.
• The legacy woocommerce/product-query block is recognised during discovery, so a store on an older card block is no longer told it has no product grid.
• A "nothing matched" outcome is no longer labelled as a dry run. It has its own state and says plainly that re-running will not change the result.
• Added FSE-first storefront analysis and targeted product-card, checkout, native sale-badge, and live low-stock-badge mutations. Unsupported layouts now return a capability error instead of a false success.

If something looks wrong after updating, reply to this email and i will look at it.

Best, Mihai