Every release,
every story.

The native connector told every client that all 300-odd tools reach outside your site

• fix The native connector told every client that all 300-odd tools reach outside your site. openWorldHint was hardcoded true, so update_page, which writes one row in your own database, was advertised exactly like a call out t
• fix idempotentHint was missing from every tool. A client had no way to tell whether repeating an interrupted call would create a second thing or land on the same state, which is exactly the question worth answering after a t

Every tool's read-only and destructive hints were delivered to nobody

• fix Every tool's read-only and destructive hints were delivered to nobody. The catalog carried readOnlyHint as a top-level property of the tool object, sitting next to name and description. MCP puts those hints inside annota

A site connected as read-only was not read-only

• fix A site connected as read-only was not read-only. Choosing that scope when connecting a site stored it, and the API keys screen in wp-admin showed the key as read-only, but nothing enforced it: the introspection that deci
• add A tool policy per site: full access, agency-safe, or read-only. Set it from the dashboard against a site, and it travels with that site's credential and is applied on the site itself, at the same checks that already gove
• add The stricter of the two settings always wins. A site's own governance profile and the policy on the credential are merged into one blocked set rather than one overriding the other, so a policy cannot widen what a site ad
• change Setting a policy no longer discards a site's approval overrides. Both live in the same stored object, and writing one replaced the whole thing. It merges now

A site that was connected and working was told it had no API key

• fix A site that was connected and working was told it had no API key. The status badge counted keys minted inside that WordPress install, and a site connected from the dashboard's MCP setup authenticates with a scoped token

A row nested inside a column was deleted by any write that rebuilt the page

• fix A row nested inside a column was deleted by any write that rebuilt the page. The shortcode parser found a module's closing tag with a non-greedy match on the same tag name, so an outer [et_pb_row] ended where the first i
• fix A page that never carried _builder_version had one written onto every module the first time any tool touched it. Divi stamps that attribute itself, so a page authored in the visual builder always has it, but a page assem
• fix A specialty section's column widths came back as full width when they were halves. column_structure="1_2,1_2" was rewritten to "4_4,4_4", silently, with the call reporting success. The widths were being inferred from the
• fix Respira's internal bookkeeping could end up written into the page. On a module carrying an attribute with no value, the attribute run ends early, the module never enters the tree, its parent row flattens to no children,
• add A write that would leave a Divi 4 page with fewer modules than it started with now says so, and for a settings-only edit refuses before writing anything. The existing dropped-children check compared the extracted tree ag
• known A Divi 4 attribute written with no value, such as sticky rather than sticky="on", still ends the attribute run, so that module does not appear in the tree and cannot be addressed by find_element or update_element. Its co

One edit to one heading on an Oxygen page deleted the body copy of every rich text element on that page

• fix One edit to one heading on an Oxygen page deleted the body copy of every rich text element on that page. Oxygen Classic writes by re-serialising the whole page tree, and the step that turns a tree node back into an Oxyge
• fix apply_builder_patch said it had applied a change it had dropped. The same page, a patch on a rich text element by id: success: true, applied: 1, changed: true, and the text byte-identical afterwards. Two separate problem
• fix The patch response reported the element's type from before the write. operations[].target.type was read off the pre-write tree, so on the write above it cheerfully said oxy_rich_text about an element that had just been t
• fix A one-attribute patch on a Divi 4 page quietly removed sixteen others. apply_builder_patch did not patch the document, it parsed the whole thing into a tree and wrote a new document back out. That round trip is lossy on
• fix delete_post returned an empty response and deleted nothing. The tool is approval-gated, and the gate answers with a token and HTTP 202. 202 is a success code, so the connector treated it as a normal reply, and the code p
• fix Creating a Theme Builder template without saying where it applied took over every page on the site. Divi records a site-wide template as an empty include list and an empty exclude list, which is byte-identical to a calle

An HTML document with a list in it could not be converted to Breakdance at all

• fix An HTML document with a list in it could not be converted to Breakdance at all. The converter mapped a list to EssentialElements\Checkmark_List, and Breakdance does not register that name. Its declared identifier is Chec
• fix The list text was never going to arrive either, so fixing the name alone would have shipped an empty list. The section mapper leaves the <li> elements as children of the list node rather than as its content, and the conv
• fix Lists now convert to BasicList rather than CheckmarkList. The adapter's own shortcut map already sent the generic list type to BasicList and reserved CheckmarkList for markup that actually asks for checkmarks, so the con
• change The bundled skills catalog was five releases behind. The Skills screen ships a snapshot of the catalog so it renders on a site with no outbound network, and that snapshot still listed 42 skills while 47 exist. Refreshed,

A write receipt said nothing had changed while the Yoast title it had just saved sat in the database

• fix A write receipt said nothing had changed while the Yoast title it had just saved sat in the database. The receipt fingerprinted three things: the post content, the builder slug, and the builder payload. Post meta was nev
• fix Approving an SEO-only duplicate moved the live page's modified date. The merge called wp_update_post() on every approval, including one where the only difference between the duplicate and the live post was a meta value.
• fix A Divi 4 page on a Divi 5 site came back as one opaque block that no targeted edit could reach. Every Divi routing decision asked the site's runtime rather than the page in front of it. On a site where Divi 5 is enabled,
• fix check_structured_data and analyze_aeo reported no schema on a page whose schema was fine. Both share one detector, and it read the stored post content rather than the page a visitor gets. Rank Math prints its @graph on w
• fix An Elementor widget with no type could still pass the render check. 8.6.28 stopped the emitter writing an untyped widget, which was the corruption itself. It did not teach the validator to see that shape, so the parser c
• add An uninstaller, with the destructive half switched off by default. Deleting the plugin left six tables, about a hundred options, five scheduled jobs and their transients behind, with no documented cleanup list. It now cl

delete_post answered with an empty response and deleted nothing

• fix delete_post answered with an empty response and deleted nothing. The tool is approval-gated on the site, and the gate replies with a token and HTTP 202. 202 is a success, so the request resolved normally rather than rais
• fix update_element and remove_element rejected the two things the ambiguity error told you to use. When several elements matched, the site refused to guess and suggested addressing the element by path or narrowing with match
• fix bulk_pages_operation documented a rate limit six times stricter than the real one. It said three runs an hour; the limit is twenty, and dry runs have never counted. Agents plan their work around that number. Corrected, a
• change create_theme_builder_template no longer assigns anything by default. Omitting assignments used to mean site-wide, which on a body template replaced the content of every page. It now creates the template unassigned, and s

html-to-breakdance

• add html-to-breakdance. The Breakdance counterpart to html-to-bricks, for bringing a Webflow, Framer or CodePen export into a Breakdance site. Breakdance keeps nothing in post_content: the page lives entirely in the _breakda

An update to a host that silently drops PUT now completes instead of hanging forever

• fix An update to a host that silently drops PUT now completes instead of hanging forever. 8.1.5 taught the client to retry a write as POST when a host *rejects* PUT, which fires on a status code. This host does not reject it
• fix The fallback cannot execute a write twice. The plugin's idempotency cache keys on the HTTP method, so a PUT that reached PHP and executed, and whose response was then dropped, would not have deduplicated against the retr
• fix diagnose_connection no longer reports a dropped request as "not blocked". It probed with OPTIONS and scored the result by status code, and a probe that times out has no status, so the comparison came out false and the ve
• add forceWriteMethod: "post" per site, alongside forceRestRoute, so a host that blocks PUT can be worked around in one line of config without waiting for a release
• add purge_cache. Purges one page or the whole site and reports which caching layers it found and exactly what it called, which it looked for and did not find, and what it skipped and why. Requires plugin 8.6.31
• add WooCommerce order reads carry customer_ip_address, customer_user_agent and meta_data, with credential-looking meta keys withheld, counted and named. Requires the WooCommerce add-on 4.0.4

Every add_* tool wrote straight to the live published page on sites that had turned direct editing off

• fix Every add_* tool wrote straight to the live published page on sites that had turned direct editing off. add_accordion, add_heading, add_image and the other 24 widget shortcuts went from parameters to the builder's inject
• fix Approving a duplicate could merge a customer's edits into an unrelated published page. The merge-target walk followed _respira_original_id off any post carrying it, including a page that had itself been a duplicate once
• fix A duplicate's base snapshot recorded an empty page, so rollback had nothing to roll back to. The baseline snapshot was captured before the post meta was copied onto the new duplicate, so builder detection looked at a pos
• fix Elementor widgets were stored with no type, which took the whole page down with a critical error. A tree that mixed simplified containers at the top with Elementor's native widgetType spelling underneath passed validatio
• fix Image alt text and Rank Math FAQ questions reported success and changed nothing. The shared update path treated attributes as a key that was already in the right place, which is true for the builders whose attribute buck
• fix A paragraph added to a Gutenberg page was written into a different builder entirely. On a page whose last block had just been removed, the content is empty, so the per-page builder check correctly reported nothing, and t

wordpress_deactivate_design_direction reaches npm

• add wordpress_deactivate_design_direction reaches npm. The tool was written and dispatching, but was never documented in the public tool list, and the parity check that guards every release refused to publish anything until
• fix A tool call with no site_id answered from the default site and said nothing about it. On a connection carrying more than one site, get_site_context, list_pages, list_posts and get_active_site now report which site answer
• fix Two MCP connections on the same machine shared one active-site pointer. The active site was persisted to ~/.respira/state.json under a single key with nothing identifying which connection wrote it, so switching sites in
• fix add_image advertised src as the only way to name an image. Passing a media library image_id was refused with a missing-parameter error. The schema now says either works, and add_testimonial gained the same for its author

The reset for a wrongly-inherited connection was locked behind the state it fixes

• fix The reset for a wrongly-inherited connection was locked behind the state it fixes. Respira_License::deactivate_license() already deleted exactly the options that make a cloned site believe it is connected, but it is reac

A cloned staging site inherited production's connection and hid its own setup screen

• fix A cloned staging site inherited production's connection and hid its own setup screen. WordPress keeps plugin options through deactivate, delete and reinstall, so a staging site cloned from a connected production site cam

Two Art Direction companions

• add Two Art Direction companions. wordpress_mint_design_preview returns a short lived signed link that lets the respira.press dashboard frame the real rendered page, drafts included, without changing caching, passwords or vi

wordpress_check_design gains rendered mode

• add wordpress_check_design gains rendered mode. rendered: true (with Respira for WordPress 8.6.20+) renders the real page at desktop and mobile widths through the respira.press render service and turns the five previously-un
• change The npm listing tells the truth about the numbers, and a test now keeps it that way. The README carried a 303-tool badge, a 16-builder heading over a table that was missing GreenShift entirely, a 103-tool WooCommerce hea

A site can now hold one design direction, and every builder obeys it

• add A site can now hold one design direction, and every builder obeys it. Nine new tools. wordpress_save_design_direction, wordpress_get_design_direction, wordpress_list_design_directions, wordpress_activate_design_direction
• add wordpress_import_design_tokens reads DTCG 2025.10, Tokens Studio exports, Tailwind configs, or a plain :root CSS block into the direction. Dry-run by default, so what would change is visible before anything is written
• add wordpress_apply_design_direction pushes the direction's tokens into each builder's own stores: Bricks global colors, the Elementor kit, Oxygen variables, nine builders in all. Approval-gated, with a per-builder report of
• add wordpress_check_design reads what a build produced and says whether it is done. Nine deterministic rules: colors and fonts outside the direction, filler copy, placeholder names, the familiar AI tells, and probes generate
• change Page builds stop treating the direction as advisory. build_page resolves hardcoded values against the active direction and reports anything that fell outside it, and the build skills run wordpress_check_design before cal

Ability category registration logged a notice on every request

• fix Ability category registration logged a notice on every request. Reported from a Kinsta multisite on WP 7.0.3, where the network Plugins screen drives the abilities hooks through admin-ajax and turned one notice per reque
• fix ability_id_is_read_only() warned on an unknown tool id. wp_get_ability() warns the same way for abilities, and every other getter call in the streamable endpoint was already paired with wp_has_ability(). This one was not

Client reports printed as dark text on a dark background

• fix Client reports printed as dark text on a dark background. The report is written into a blank window as a self-contained document, and it set a text colour but no background and no colour scheme. A blank document inherits
• fix The About screens described a release from June. All three still reported 7.1.0 "Roots" with sixteen builders while the plugin shipped through Canopy to 8.6.9 with seventeen. The version is now read from the live plugin
• fix The About item in the sidebar went unreadable while you were on About. Its muted colour is declared after the active state at equal specificity, so source order let it override: in light mode that left #50575e text on th
• change The client report is set like a document rather than a default print. Headings use Alan Sans, body text resolves to the platform's real UI face instead of falling through to Arial, and figures are tabular so columns line

A leftover config file could beat the credentials in your client entry, silently

• fix A leftover config file could beat the credentials in your client entry, silently. ~/.respira/config.json outranks WORDPRESS_URL and WORDPRESS_API_KEY, which is deliberate: an explicit file is the more considered of the t
• fix Six builders made get_page_outline unroutable on every site that used them. Display names with spaces were being sent where route slugs belong
• change A site that cannot be found now says which config the server actually read. RESPIRA_CONFIG_B64, RESPIRA_CONFIG_FILE, or the default file, named in the error, because "site not found" is unactionable when three sources ca
• change claude mcp add now suggests -s user, so a connection follows the machine rather than the folder it was created in

"REST route missing" now says which of two opposite things went wrong

• fix "REST route missing" now says which of two opposite things went wrong. rest_no_route is WordPress answering in JSON, which it can only do when REST routing already works, so it is never a permalink problem and retrying v
• change The ?rest_route= fallback stops sounding like a fault. Permalinks set to Plain mean WordPress does not serve /wp-json/ at all, which the connector already handles by falling back to ?rest_route=, core WordPress that work

The security tool descriptions named an advisory that had moved on

• fix The security tool descriptions named an advisory that had moved on. wordpress_update_core_security described its advisory_id as "currently wordpress-wp2shell-2026" and listed 6.8.6 / 6.9.5 / 7.0.2 as the targets. The plu

The security audit now reports application passwords

• add The security audit now reports application passwords. They are the one
• add Administrator rows carry the context that makes them answerable. Whether a
• fix A site could be told it was vulnerable and then refused the fix. The list
• fix Audit coverage now distinguishes checked-and-found-none from never-looked for

151 of 163 native abilities directed an agent straight into a 404

• fix 151 of 163 native abilities directed an agent straight into a 404. The abilities directory built each ability's advertised name by stripping a prefix and never converting underscores to hyphens; the plugin actually regis
• fix A Divi 4 targeted edit could silently land on the wrong element. find_element and update_element used two different matchers for the same identifier_type=content lookup: find_element searched a self-closing module's own
• fix A Divi 5 button's stale content alias couldn't be removed. apply_builder_patch rejected a structured unset operation outright (INVALID_ARGUMENT); update_element accepted it but wrote literal attributes.unset/attrs.unset
• fix A plugin update didn't always update what get_server_compatibility reported. Right after updating from 8.6.1 to 8.6.3, diagnose_connection's live probe correctly reported the new version while get_server_compatibility, c
• fix Two dead pointers into the abilities admin surface. inhale_admin_url pointed at an unregistered page slug (page=respira-inhale), and the error text on an un-inhaled ability told you to visit a WordPress submenu item, "MC

apply_builder_patch and update_element's unset operation had no valid shape a strict client could use

• fix apply_builder_patch and update_element's unset operation had no valid shape a strict client could use. The write-path handling for removing a stale attribute alias (e.g. a Divi 5 button's leftover content key) was alread

Agent identity is no longer guessed and reported as fact

• fix Agent identity is no longer guessed and reported as fact. The plugin
• fix Tool reads reported no agent at all. Usage reporting has two payload
• add tests/standalone/agent-source-provenance.php, the harness this code path

Elementor global classes can be read, reused and created without colliding

• add Elementor global classes can be read, reused and created without colliding. Respira styled an Elementor v4 element by creating a one-off style on that element. It rendered, but the section never joined the site's own cla
• fix Two malformed tool schemas were making every Respira tool unusable on Anthropic clients. create_design_token and update_design_token declared their value property as an empty array, which is not a JSON Schema object and

Respira's own abilities would have gone invisible to other AI clients on WordPress 7.1

• fix Respira's own abilities would have gone invisible to other AI clients on WordPress 7.1. Core is adding a single public flag that says an ability is meant for external clients, and the WordPress MCP Adapter starts honouri
• add The weekly snapshot now reports how many abilities on a site declare themselves public. Core held its Guidelines proposal for lack of real-world adoption evidence and is now shipping a flag with no way to watch it land,

A "Disconnect and reset" button, under Settings > Advanced, for a site that will not connect

• add A "Disconnect and reset" button, under Settings > Advanced, for a site that will not connect. A customer connected a site that had previously been on a different Respira account. It refused his key, so he uninstalled the
• fix add_html on Bricks now creates a real HTML element, unsigned, instead of a signed Code element. Bricks signs Code elements with a key derived from the site's own salts, and an SVG element built on Code has that signature
• fix Borders survive convert_html_to_builder on Bricks. Border width, style, colour and radius were being stored under Elementor's key names, which Bricks does not read. They saved without complaint, counted toward the fideli
• fix bricks_import_design_tokens hands back a way to undo itself. The importer writes two stores that only make sense together, since a token becomes both a global variable and a colour-palette swatch, and Bricks version-trac
• fix Four button settings on Divi 5 stopped being accepted and then ignored. button_font_size, button_font_weight, button_border_width and button_border_radius passed validation, reported success, and wrote nowhere. Two of th
• fix Every Divi 5 module type is registered, not two thirds of them. The list had been hand-maintained and had fallen behind at 67 of the 110 module types Divi 5.10.1 ships, so anything added since Divi 5.5 lost its settings

A host briefly refusing one request read as "your site is down"

• fix A host briefly refusing one request read as "your site is down". When a server in front of WordPress returned a 5xx, the message said the site might be down, misconfigured or behind a failing proxy, and told you to check
• add Three Figma conversion skills: figma-to-divi, figma-to-bricks and figma-to-gutenberg.

upload_media no longer turns raw SVG markup into a handful of unreadable bytes

• fix upload_media no longer turns raw SVG markup into a handful of unreadable bytes. The tool documents raw SVG as an accepted input and had no branch for it, so the markup fell through to the "assume base64" fallback. Node's
• fix bricks_import_design_tokens now tells you it can be undone. The tool returns a rollback handle covering the colour palette, the global variables and their categories, and the description now says so, since neither store

Bricks move, reorder and remove now operate on Bricks' real storage shape instead of assuming every builder nests the same way

• fix Bricks move, reorder and remove now operate on Bricks' real storage shape instead of assuming every builder nests the same way. Bricks stores a page as a flat list where each element points at a parent id and lists its c
• fix Bricks reorder_elements no longer silently reorders the wrong container. Passing an element id instead of a positional path used to intval() down to 0 and quietly reorder the first section on the page. It's now rejected
• fix Bricks accordions built through add_accordion now actually render. The cross-builder generic shape (settings.items: [{title, content}]) has no equivalent field on Bricks' own accordion element, which expects a repeater c
• fix A targeted single-element edit on a Divi 4 (shortcode) page no longer rewrites the whole page. Divi 5 got this fix in 8.2.2; Divi 4's shortcode storage path had the same disease underneath a different symptom. Nine separ
• fix A Divi page built by build_page no longer always shows as an opaque, non-editable block in Divi's own Visual Builder. A column's own width, and every module's admin_label, were only ever lifted when supplied under settin
• fix button_text_color on a Divi 5 button now actually renders. It wrote to the same JSON path as the button's background/border color, which Divi's own compiler doesn't read for text color; the value stored cleanly and never

A mistyped ability name now tells you the right one

• fix A mistyped ability name now tells you the right one. When an agent calls an ability that is not registered, the error used to list fifty registered abilities in whatever order the registry held them, which on a site with
• add The weekly adoption snapshot now names the third-party abilities a site registers, not just their vendors. The public directory of plugins that adopted the Abilities API is a hand-made list, and its weakness has always b

A partly-edited starter config was accepted as a real one, sending every request to example.com

• fix A partly-edited starter config was accepted as a real one, sending every request to example.com. The first run writes a placeholder config carrying a dummy address AND a dummy key, and isPlaceholderConfig() tested only t
• fix An API key pasted with the documentation brackets still around it is now rejected at startup. <respira_...> is not a valid key, but it is also not the placeholder key, so it defeated the same check above and pinned the s

A PUT request that a host blocks now retries as POST

• fix A PUT request that a host blocks now retries as POST, closing the gap for Elementor's global-colors and global-typography routes (403 on hosts like OVH that block PUT) and every other route built on the shared REST clien
• fix The four WooCommerce card tools' edit_target values now match the FSE tool family they actually route through (approval/live, the same vocabulary update_site_template uses), instead of the page-edit tools' live/duplicate
• fix redeem_token now activates sites in the running session immediately. A successful redeem wrote a config file and reported success, but the server kept using its boot-time site list until restarted, and under a sandboxed
• add diagnose_connection reports the actual running transport: bundle, npx cache, global npm install, project-local install, or source checkout, plus a flag when a differently-launched sibling Respira process is detected, clo

A site with more than forty guideline records reported forty

• fix A site with more than forty guideline records reported forty. The weekly snapshot walks guideline bodies to see which scopes a site populates, and that walk is capped so the report stays small. The count was being taken

Respira now reports, once a week, whether site memory is actually doing anything

• add Respira now reports, once a week, whether site memory is actually doing anything. Counts and booleans only: how many memory entries a site holds, how many of them are rules, and how often one of those rules refused an ag
• add Nothing about your content leaves the site. The snapshot carries no memory text, no guideline bodies, no post titles, no post IDs, and no slugs you wrote. The only strings in it are values fixed by code somewhere else: c

The other two dependency pins are gone, so a Composer install can now sit in a modern tree

• change The other two dependency pins are gone, so a Composer install can now sit in a modern tree. 8.5.8 widened symfony/deprecation-contracts, which was the quiet one. psr/log at ^1.1.4 was the loud one: psr/log 1 and 3 cannot
• change Respira calls none of these three. They arrive behind Sentry, which has always declared psr/log at ^1.0|^2.0|^3.0 and options-resolver up to ^8.0, so these pins were narrower than the package that actually depends on the
• change Nothing changes for the zip on respira.press. The release build pins its platform to PHP 7.4, so it still resolves psr/log 1.1.4, options-resolver 5.4.45 and deprecation-contracts 2.5.4, the same fourteen packages as 8.5

Composer-managed installs can keep their own Symfony 3.x line

• change Composer-managed installs can keep their own Symfony 3.x line. symfony/deprecation-contracts was pinned to ^2.5, so requiring Respira into a Bedrock, Kinsta or WP Engine root pulled that whole project back to the 2.x bra

The Observe profile now closes every write, which is what it always said it did

• sec The Observe profile now closes every write, which is what it always said it did. It computed its blocked list from a registry of eleven tool families, and a tool belonging to no family was never considered, so it closed
• sec Two WooCommerce badge tools were flagged read-only while writing. add-sale-badge and add-low-stock-badge insert blocks into a template through the same path as their siblings. The wrong flag meant a profile that closes w

Converting HTML on a site with no page builder no longer throws

• fix Converting HTML on a site with no page builder no longer throws. With builder omitted, auto-detect resolved correctly to a block library (GreenShift, Spectra, Kadence Blocks or GenerateBlocks) and the converter then buil
• fix Those four block libraries also get block-editor styling keys. They were falling through to the generic map, which is Elementor-shaped: the settings persisted, counted as matched, and emitted no CSS
• fix The fidelity report no longer calls the same token mapped and unmapped. A successful mapping came back with tokens_mapped: 1 and tokens_unmapped: ["--rwx-brand"] plus a warning, because the unmapped list compared token n
• fix A shape mismatch handed to the block adapter is refused rather than thrown on.
• add get-server-compatibility now says what a conversion would actually do here, not just that the feature exists. feature_detail.html_converter reports the builder a call with no builder would target on this site, whether th
• add The WooCommerce storefront write tools declare edit_target and verification_marker. The add-on's shared passthrough has always forwarded both to the template service; no schema ever declared them, on any surface, so they

A failed plugin activation now rolls back in a way that survives Redis

• fix A failed plugin activation now rolls back in a way that survives Redis. When the fresh-boot probe fails, Respira deactivates the plugin it just activated. But the active-plugins list lives inside WordPress's alloptions c

Tool governance lives in the new admin now, whole

• change Tool governance lives in the new admin now, whole. 8.5.3 surfaced the profile switch in Settings but sent you to the pre-7.1 page for the per-tool switches, which meant one click took you from the current design into the

The tool profiles from 8.4.0 are finally reachable

• add The tool profiles from 8.4.0 are finally reachable. Everything, Content and Observe shipped with the enforcement wired and the switch hidden: the selector lived on a governance page nothing in the admin linked to, so "Se
• fix The "Pair one now" link on the bridge banner goes somewhere. It was an anchor with no destination, so a site with no paired agent was invited to fix that and then left standing. It now opens the Connect screen

Converted headings, paragraphs and lists now carry their styling on the block editor

• fix Converted headings, paragraphs and lists now carry their styling on the block editor. 8.5.1 fixed this for sections, which own their wrapper and could be rebuilt from nothing. A heading or paragraph does not: its markup
• fix ChatGPT can connect again, on both the OAuth and the API-key method. Thirteen tools declared a list-shaped input without saying what the list contains. A strict client rejects the WHOLE tool list over one of those, not t

A converted section's background, padding and colour now reach the page on Divi 5, Beaver Builder and the block editor

• fix A converted section's background, padding and colour now reach the page on Divi 5, Beaver Builder and the block editor. Three separate faults with one symptom: the styling was stored, the write reported success, and no s
• fix The source element's CSS classes now reach block-editor groups as className, so theme and utility CSS applies to a converted section.
• fix Design tokens close the loop on the block editor: a converted section's wrapper references var(--wp--preset--color--{slug}) and the page declares it. 8.3.2 registered the preset and 8.5.0 kept the reference, but nothing

Design tokens now register on the other builders too, and the converted page references them

• add Design tokens now register on the other builders too, and the converted page references them. 8.3.2 did this for Gutenberg. Elementor, Bricks, Divi, Beaver Builder, Breakdance, Oxygen and Oxygen 6 now do it as well, each
• add A registered token stays a reference instead of becoming a copy. This is what makes the registration worth anything. The converter used to inline every var() before any builder setting was built, so a colour registered a
• add Honest about the gaps, per builder. Elementor 4.x has no stable global store for sizes, so sizes are skipped there rather than written into an option Elementor never reads. Divi 4 substitutes a global colour while render
• fix The last custom property in a :root block was dropped when it had no trailing semicolon, which is how minified CSS is normally written.

Access profiles: one switch that scopes what a connected agent may do

• add Access profiles: one switch that scopes what a connected agent may do. Governance has offered per-tool switches since 5.2.0, but scoping a site meant walking a list of checkboxes and knowing which ones matter. A profile

Design tokens are registered as theme.json presets

• add Design tokens are registered as theme.json presets. Converting a design used to write VALUES into blocks: a colour became #1a1a1a sitting in a block attribute. Values copied into many places drift, because an agent regen
• add Write receipts. Element operations and page-level writes now return a write_receipt: { changed, fingerprint_before, fingerprint_after }, hashed over the same payload the read snapshots already trust. The incident class t
• add Sealed audit log. Each audit row now carries seal_seq and a seal: an HMAC chained from the previous row's seal, keyed from the site's salt material, so editing or deleting a row breaks the chain at exactly that row. The
• fix The fidelity report conflated tokens referenced with tokens defined. tokens_total counts declarations in :root{}/html{}. A design system that ships markup and keeps its variables elsewhere produces zero, correctly — and
• fix responsive_mapped: false gave no reason. It did not distinguish "no media queries in the source" from "this builder branch does not emit responsive settings yet", so after passing responsive: true a bare false read as th

The HTML converter discarded every attribute it had just mapped

• fix The HTML converter discarded every attribute it had just mapped. The Gutenberg branch appended a second JSON object after the first in the block delimiter. A block comment carries exactly one attributes object, so WordPr
• fix Omitting the builder failed instead of auto-detecting. The schema documents auto-detect when the parameter is left out. The converter defaults to auto, but a PHP default only applies when an argument is omitted, and the
• fix Connected Apps told working customers nothing was connected. The page lists OAuth grants only, so a customer connected by setup code or Desktop bundle can never appear there. One had 76 tool calls over three weeks and re
• add diagnose_connection now reports the client's effective configuration, not just the site's. Which config source won (RESPIRA_CONFIG_B64, RESPIRA_CONFIG_FILE, or the default path), where it is, how many sites resolved and
• add redeem_token now verifies its own write. It reads the config back and reports what landed and whether the next start will actually read it, instead of reporting success for a file an environment variable already outranks
• add The four WooCommerce card tools now accept edit_target and verification_marker. The add-on has always forwarded both to the FSE layer; the tool schemas never declared them, and a client only sends what a schema declares.

Three real skills were missing from the public catalog and from npx skills / OpenCode installs

• fix Three real skills were missing from the public catalog and from npx skills / OpenCode installs. respira-builder-edits, respira-site-audit, and respira-woocommerce had shipped in the bundled skill set for a while but were

Gemini could not connect at all

• fix Gemini could not connect at all. Google's API validates tool schemas strictly and rejected the entire toolset with a 400 because one array property (the mega-menu columns) had no items definition. It was the only such ar

diagnose_connection reports the effective client configuration

• add diagnose_connection reports the effective client configuration. It already reported process facts (version, pid, binary path, sibling processes); it did not report the configuration those facts were operating on. It now
• add redeem_token verifies its own write. It writes the config, reads it back, and reports what landed and whether the next start will read it. Previously it wrote a file and reported success, which is true and useless when a
• add edit_target and verification_marker on the four WooCommerce card tools. Both were already forwarded to the FSE layer by the add-on; the schemas never declared them, so they could not be supplied

Site Memory

• add Site Memory. A capped per-site store (wp_respira_memory, 30 entries of 500 characters) of facts, preferences, and lessons your AI accumulates. Entries ride into /context/site-info and /context/builder-info on every sessi
• add Rules, enforced at the write path. A memory of type rule can protect content by post id or slug. Protected content refuses agent writes, deletes, element operations, patches, and agent-mediated approval of staged copies:
• add Memory screen in the admin. A native v7.1 rail item showing rules first, notes below, every entry labeled with who wrote it, read-only with an edit-in-dashboard action. A classic view ships as fallback
• add WordPress core Knowledge interop. On sites running the Gutenberg Knowledge experiment, published guideline scopes join the same memory block agents receive. Feature-detected; sites without the experiment skip it at the c
• add Entitlement. Included on Builder and Studio plans at no extra cost, not on Maker. The license validate heartbeat syncs entitlements.memory down to the plugin; until the first sync, licensed sites are treated as entitled.
• fix WebMCP browser bridge migrated to document.modelContext. Chromium removed navigator.modelContext entirely; the bridge now prefers the document surface and keeps the navigator path as a fallback for older builds

Resonance memory tools

• add Resonance memory tools. wordpress_remember, wordpress_forget, and wordpress_list_memory maintain a persistent per-site memory on the WordPress site itself (plugin 8.3+). The tool descriptions teach the loop: save durable
• add Memory-aware session priming. The handshake instructions gain a golden rule for honoring and growing Site Memory, and get_site_context carries the site_memory block through the compact detail: basic projection, so every
• fix claude.ai traffic is no longer mislabeled as Claude Code. Client-reported clientInfo now takes precedence over user-agent heuristics when resolving the agent label, with tests pinning the claude.ai versus claude-code spl

find_element returned no identifier you could use

• fix find_element returned no identifier you could use. The compact response built id, admin_label and _path, then filtered out nulls — and two of the three were always null on Divi 5, because admin_label read the Divi-4-only
• fix GreenShift reported version "unknown" on current installs. 8.2.2 added a plugin-header fallback, and it worked, but the directory list was one entry short: the live wp.org directory is greenshift-animation-and-page-build
• change Bricks structural operations now refuse rather than restructure. Bricks stores _bricks_page_content_2 as one flat array where every element carries a parent id and a children list of child id *strings*, not embedded node

A targeted edit re-injected, and restructured, the whole page

• fix A targeted edit re-injected, and restructured, the whole page. update_module and the v2 patcher both persist by re-injecting the full tree through inject_content, which re-ran the Divi 5 section scaffold over it. That sc
• fix A setting sent inside attributes was accepted and ignored. The alias lift only ran over keys at the top level of updates, and attributes is on the reserved list, so updates: {admin_label: "X"} lifted to its canonical pat
• fix admin_label lookups missed every Divi 5 module. The Divi adapter's own finder has known since 2026-07-28 that the label lives at attributes.module.meta.adminLabel.desktop.value; the shared tree utility checked only a fla
• fix apply_builder_patch returned 422 respira_patch_not_persisted on Divi 5. Downstream of the label lookup above, not a save fault: the identifier never resolved to the intended node, so nothing meaningful changed and the no
• fix Reported paths described a page shape that did not exist. build_path_string() labelled by depth, hardcoding depth 0 as sections[] and depth 1 as rows[], so a fullwidth module at depth 1 was announced as rows[0] on a page

include= silently dropped any token it did not recognise

• fix include= silently dropped any token it did not recognise. An unknown token was discarded and the read fell back to basic, so the caller got HTTP 200 and a plausible payload with no sign that part of the request had been
• fix Renewing a lapsed licence never re-enabled the API keys the lapse disabled. The lapse switches keys off from four places; nothing ever switched them back on, so renewal left them dead permanently and the only cure was no
• fix The Builders screen described primary-versus-not-primary in the vocabulary of intelligence-versus-detection. Both columns were ternaries on a string compare against the active builder, because the admin endpoint returned
• fix The Gutenberg-native family reported no intelligence layer. is_intelligence_available() derived its package directory from the builder's display name, so GreenShift went looking for a greenshift-intelligence/ that does n
• fix GreenShift reported "vunknown" on a correctly detected site. The plugin has shipped under at least two names with different version constants. The version now falls back to reading the plugin header, which survives whate
• fix An excerpt sent through the meta bag was written as post meta and rendered nowhere. create_custom_post had accepted an excerpt argument since 3.1.0, but none of the three update paths did, so the only way to set one on a

An authentication failure was reported as "respira/v2 is not available on this site"

• fix An authentication failure was reported as "respira/v2 is not available on this site". The version probe swallowed its own error and fell back to v1, so every failure mode reached you as the same message followed by four
• add excerpt on update_page, update_post and update_custom_post. There was no way to ask for it, so callers put it in meta, where it became a post meta row that reads back perfectly and renders nowhere. The description says a

GreenShift is the 17th supported page builder

• add GreenShift is the 17th supported page builder. GreenShift by Wpsoul (shipping as "GL - Page Builder", still greenshift-blocks/ internally) is Gutenberg-native, so reads, element operations and design tokens work through
• fix Nested blocks were silently dropped when children arrived under a key other than children or innerBlocks. The tree utility walks rows, cols, columns, modules and elements on the read side, so an agent could extract a pag
• fix The activity log recorded a kept write as a failure. A structural write that is applied and deliberately kept but cannot be confirmed on its public route returns stored_unverified with HTTP 502. The audit trail derived i

Updates now succeed on hosts that block PUT at the edge

• fix Updates now succeed on hosts that block PUT at the edge. Managed hosts and WAFs commonly allow GET and POST but reject PUT, PATCH and DELETE before the request ever reaches WordPress. The result was every update failing

wordpress/mcp-adapter now targets ^0.5

• change wordpress/mcp-adapter now targets ^0.5 (was ^0.4, resolving to v0.4.1). Plugins that bundle their own copy of the adapter end up sharing one set of loaded classes, so a plugin requiring 0.5+ (WP Rocket, for one) could fi

The Approvals screen called a kept write a failure

• fix The Approvals screen called a kept write a failure. Approving a structural proposal whose change cannot be seen on its verification route returns stored_unverified: the write was applied and was NOT rolled back, it simpl

The stored_unverified response added in 8.1.7 described itself wrongly

• fix The stored_unverified response added in 8.1.7 described itself wrongly. It returned HTTP 409, which is the status this same method uses for a rolled-back write, and it omitted mutation_performed, the one field that tells

A stored, structurally valid FSE template write was rolled back whenever the verification route could not display it

• fix A stored, structurally valid FSE template write was rolled back whenever the verification route could not display it. Frontend verification falls back to comparing a hash of the whole public page when no verification_mar

A masked API key copied from WP Admin now fails at config load instead of at the first tool call

• fix A masked API key copied from WP Admin now fails at config load instead of at the first tool call. The key shown in WP Admin is masked as respira_5f66e38d followed by bullet characters, and that text is selectable. Copyin

The npm listing now states the real tool counts and shows the current key visual

• change The npm listing now states the real tool counts and shows the current key visual. Three surfaces disagreed: the README said 169 core / 272 with WooCommerce, package.json said 197 / 302, and the canonical source (respira-

Version 8.1.2

• document Corrected the npm README heading from 12 to 16 supported page builders.
• document Added Spectra, Kadence Blocks, GenerateBlocks, and SeedProd to the support table, and corrected the stale Site Editor “Next release” label.

Version 8.1.1

• document Updated the npm package description to name MCP 2026-07-28 and legacy-client compatibility directly.
• document Added the 8.1 release summary to the top of the npm README and corrected the stale “Next release” heading.
• document Included CHANGELOG.md in the npm package so the complete version history ships with every installation.

MCP 2026-07-28 protocol support through the official TypeScript SDK 2 packages

• add MCP 2026-07-28 protocol support through the official TypeScript SDK 2 packages. New clients can negotiate the modern stateless protocol with server/discover, per-request metadata, typed results, server identity, and cach
• add Dual-era stdio serving. Existing MCP clients keep using the established initialize handshake, while compatible clients can pin or negotiate 2026-07-28. Existing Respira configuration, site keys, and connection commands d
• add Release coverage for both protocol generations. The packaged-server smoke test now proves both an exact 2026-07-28 negotiation and the legacy initialization path against the complete tool catalog
• sec Updated Axios, FormData, Sentry, and their OpenTelemetry runtime dependencies to patched releases. The production npm dependency audit reports zero known vulnerabilities.

A Divi 5 settings payload sent to update_element was silently discarded

• fix A Divi 5 settings payload sent to update_element was silently discarded. Every other Divi 5 entry point accepts a settings bag: build_page takes one, and patch_module's merge verb routes it through the translator so keys

update_element could report a different element as the result of your edit

• fix update_element could report a different element as the result of your edit. After writing, it re-extracted the page and read the result back by *position*, trusting the post-save tree to index exactly like the pre-edit o

Playbooks could be created but never corrected

• fix Playbooks could be created but never corrected. The connector exposed only list and create, so a mistyped step, a wrong template reference or an abandoned experiment was permanent: there was no way to read a playbook bac

Divi 5 patch_module could never resolve a node, at any depth

• fix Divi 5 patch_module could never resolve a node, at any depth. The lookup bound its result with $out = &$block, which in PHP is a reference *rebind* rather than a value assignment: it detaches the local variable from the
• fix Playbook steps no longer fail with respira_scope_denied. The executor runs each step as its own internal request, and that request was seeded with a key carrying no permissions at all, so every route guarded by a v2 scop

The connection screen was handing out an endpoint that does not exist

• fix The connection screen was handing out an endpoint that does not exist. The setup and settings screens told you to point your agent at https://yoursite.com/?respira=mcp, including inside the copyable npx add-mcp one-liner
• fix The API key panel now shows a rotated key and names it after the agent it belongs to. Rotating a key called the mint function without passing the agent's name, so every rotation produced a row literally called "first key
• change A stale admin bundle now fails the build instead of shipping silently. The plugin admin is compiled from admin/assets/v71/src/**.jsx into one committed bundle, and the release zip ships that bundle rather than the source

bulk_pages_operation's find_and_replace no longer corrupts escape sequences in post content

• fix bulk_pages_operation's find_and_replace no longer corrupts escape sequences in post content. The bulk write path called wp_update_post() directly without wp_slash() first, so WordPress's own unslashing step silently ate
• fix respira_update_option no longer 404s on option names containing a dot (e.g. litespeed.conf.optm-css_min). The write, read, and delete REST routes share one URL pattern, and that pattern didn't allow periods in the option
• fix create_menu_item with object_type: "page" (or any post type/taxonomy) now produces menu items that actually navigate. The menu item was stored with an invalid _menu_item_type value (the raw object slug instead of WordPre
• fix Oxygen style writes (color, background-color, etc.) to global Theme Builder templates now actually persist and render. The style-key lift that nests these properties under options.original (where Oxygen's renderer reads
• fix A patch with an explicit path no longer silently writes to a different element. When a path failed to resolve, the node finder fell back to matching on type, which returns the FIRST node of that type on the page. A targe
• fix Divi accepts the slash-form paths its own tools emit. apply_builder_patch calls carrying a path like /0/1/0/0/0 died in the path parser before reaching the writer, so the edit never happened even though the call reported

Safety & Security scanning for connected WordPress sites

• add Safety & Security scanning for connected WordPress sites. The read-only audit reports authoritative WordPress, WooCommerce, and reviewed extension versions; official core checksums; administrators; standard and must-use
• add Reviewed wp2shell evidence. Exact public-exploit account and plugin markers are separated from lower-confidence database and filesystem observations. The scanner inspects bounded oEmbed, customize changeset, navigation-o
• add Database and configuration posture. Receipts normalize the current database account's global FILE capability to available, absent, or not verifiable without exposing raw grants. DISALLOW_FILE_EDIT and DISALLOW_FILE_MODS
• add Approval-gated core security updates. Only catalog-approved patch targets on the running release branch are accepted. A recoverable-backup confirmation and second approval are required, followed by version, REST, fronten
• sec Broad SQL cleanup, automatic account deletion, and automatic plugin/file removal remain prohibited. Suspicious artifacts are evidence for owner review, not permission to destroy data.
• sec Audit receipts bind evidence to canonical target URLs and a site fingerprint, reject wrong-site results, expose truncation, and distinguish WordPress-visible evidence from host-only gaps.

Divi 5 text modules silently ignored body content

• fix Divi 5 text modules silently ignored body content. An update_module / apply_builder_patch call carrying content on a divi/text module reported success but never wrote the text, unless the module already happened to carry
• fix Partial attribute patches destroyed neighbouring attributes. Writing a nested attribute such as title.decoration.font replaced the entire title group, taking title.innerContent (the heading text) with it, while still ret
• fix batch_update diverged from every other writer on Divi. It routed through the generic patch builder, which replaces whole attribute groups and applies no Divi 5 translation, so flat keys never reached the paths the builde
• fix admin_label could never resolve on Divi 5. The label is stored at module.meta.adminLabel.desktop.value, but the resolver only read the flat admin_label key that exists on Divi 4 nodes, so the selector always returned res

The FSE writer gate now says how to turn it on, in the error message itself

• fix The FSE writer gate now says how to turn it on, in the error message itself. The respira_fse_writer_beta_disabled response already carried an enable_with hint in its data payload, but many MCP clients surface only messag
• fix build_page now actually halts on a Bricks page that references a global class ID absent from the live registry. The registry-verification added in 8.0.3 was gated on a flag that build_page always set the wrong way, so a
• fix Duplicate Bricks global class names are rejected instead of silently accepted. create_bricks_global_class (and update) now refuses an exact name collision with a 409 naming the existing ID, so two classes can no longer s
• fix An unmapped Bricks global-class setting key is now flagged. create_bricks_global_class (and update) checks each key against every Bricks element's real control schema and returns an unmapped_keys array for anything that
• fix HTML-to-Bricks conversion no longer writes Elementor-shaped keys into Bricks elements. Background colour, text colour, and typography properties (font family/size/weight, line height, letter spacing, text transform/decor
• fix Design-token re-import distinguishes "already imported" from "ignored your new value." Changing a token's value and re-importing previously reported the same "variable already exists" skip reason as a true no-op re-impor

Released 2026-07-16.

• change Released 2026-07-16.
• add Product configurator tools (STAGGS). 8 tools: configurator status, per-product enable/disable, attribute-group listing, option-items read and write (through the STAGGS/Carbon Fields helpers, so storage stays consistent), and an allow-listed
• add "What an agent could do here" card on the Respira ARC screen: eight copyable real prompts covering catalog fixes, pricing previews, cart links, agent-order reporting and storefront design.

Released 2026-07-16.

• change Released 2026-07-16.
• change the Respira ARC screen is light-only and matches the standard wp-admin chrome (the dark variant read as a foreign app and had contrast problems).
• add official platform logos (Google, OpenAI, Meta, Pinterest, TikTok) on the format chips and submit links.
• change the fix-prompt button is smaller ("Fix with AI") with a tooltip explaining what the prompt does and what Respira is.

Released 2026-07-16.

• change Released 2026-07-16.
• add Submit links on the feed table. Each feed row links to the right platform dashboard (Merchant Center, OpenAI merchants, Meta Commerce Manager, Pinterest, TikTok) with a one-line where-to-paste instruction on hover.
• add A quiet footer with credits and links (add-on, ARC, docs, support), and the agent-tools panel links to the full tool list.

Released 2026-07-16.

• change Released 2026-07-16.
• add Fix prompts on the quality card. Every failing readiness check now carries a copy-ready prompt for your AI assistant (Claude, ChatGPT, Cursor). Paste it into an assistant connected through Respira and the agent fixes what the check flags, s
• add Product picker for cart links. Choose products by name (variations grouped under their parent, prices shown) instead of typing product IDs. Large catalogs show the first 200 by name.
• add The page title now carries the Respira ARC wordmark, set in Alan Sans (bundled, no external font requests).

Released 2026-07-16.

• change Released 2026-07-16.
• add a small provenance line under the Respira ARC page title, so a screenshot instantly shows whether the screen is rendered by this add-on or by the free Respira ARC plugin.

Released 2026-07-16. Agent-Ready Commerce: AI assistants can now find, read, and sell from your store. 79 MCP tools (up from 56).

• change Released 2026-07-16. Agent-Ready Commerce: AI assistants can now find, read, and sell from your store. 79 MCP tools (up from 56).
• add Product feeds in six formats. Google Shopping XML (Merchant Center scheduled fetch; Bing accepts the same file), OpenAI/ChatGPT JSONL, Meta CSV, Pinterest CSV, TikTok CSV, and generic CSV, plus a store llms.txt at the site root. Built in th
• add Readiness becomes a fix loop. readiness_fixlist turns the AI-readiness scan into an ordered work queue mapping every failing check to the tool that fixes it; set_image_alt writes the alt text that fails most; update_product gains global_uni
• add Assisted checkout with attribution. create_cart_link builds signed multi-item cart URLs: the shopper's cart fills server-side and lands on your own checkout; tampered signatures are rejected. Orders are attributed via WooCommerce native att
• add Subscriptions, Bookings, Memberships write tools (14). Tested against the real extensions. Status transitions validated against what each extension allows, booking reschedules include a conflict scan, everything is dry-run by default with s
• add Respira ARC admin screen under WooCommerce &rarr; Respira ARC: feed URLs with copy buttons, catalog quality score, cart link generator, agent-origin orders, in light and dark admin schemes.

Released 2026-07-16.

• change Released 2026-07-16.
• fix revert_pricing works end to end for the first time. Two defects, both present since the pricing tools shipped in v2.0: the tool passed a numeric snapshot id to the UUID-keyed snapshot store (so the lookup could never match, and the error ob

Released 2026-07-16. The full commerce surface: 56 MCP tools (up from 21). Completes the v3.0 rollout that began in June: the release was built and published then, but the update was never offered to customer sites, which kept stores on the

• change Released 2026-07-16. The full commerce surface: 56 MCP tools (up from 21). Completes the v3.0 rollout that began in June: the release was built and published then, but the update was never offered to customer sites, which kept stores on the
• add 15 commerce tools now reachable over MCP. The catalog, pricing, inventory, and storefront endpoints (advanced product listing, natural-language product search, catalog health, bulk product/price/stock updates, sale scheduling, pricing rollb
• add Brand tools. list/get/create/update/delete-brand REST routes and MCP tools (the abilities existed since 2.2.0; now they're reachable everywhere).
• add Variations and attributes. set_product_attributes (global or custom, creates missing terms), generate_variations (cartesian product, skips existing, capped at 100/call), create_variation, set_variation_gallery (variation image + gallery whe
• add Coupons and customers. list/create/update_coupon (discount types, expiry, usage limits, product/email restrictions) and create/update_customer (billing and shipping addresses; passwords auto-generate and are never returned).
• add Order notes and refunds. add_order_note (private by default), get_order_refunds, and create_order_refund which is DRY-RUN BY DEFAULT: it previews the refund until you pass dry_run: false, and never touches the payment gateway unless refund_

Released 2026-05-27.

• change Released 2026-05-27.
• add Product brand support (product_brand taxonomy). The update-product and create-product abilities now accept brand_ids so an AI can assign or clear brands on a product the same way it already assigns categories and tags. Full CRUD endpoints l
• add Featured-image removal. The update-product ability now accepts image_id. Pass an attachment ID to set; pass 0 or null to remove the featured image. Previously the only image-related field on the response was a read-only URL; agents had no w
• schema Product response shape gains brand_ids, brands, and image_id. image is unchanged.

wp.org review fixes

• change Display name updated to "Inhale: MCP Abilities by Respira" so the author attribution is visible in wp-admin plugin lists. Slug inhale-mcp-abilities is unchanged.
• change Contributors field in readme.txt now lists urbankidro (the wp.org username that owns the plugin) instead of the brand string. The Author header still reads "Respira" so the visible attribution on the directory page is un
• change uninstall.php updated to remove the new primary key, the v0.4.0 migration flag, the canonical compat key, and every legacy key from v0.1.x and v0.2.x. Single-site and multisite sweep.

WordPress.org Plugin Directory submission

• change Canonical option key. v0.2.0+ stores the opted-in list under mcp_adapter_public_abilities — the same key proposed first-party in [WordPress/mcp-adapter#184](https://github.com/WordPress/mcp-adapter/pull/184). A one-shot
• change Brand-aligned chrome. Header with "by respira.press" Baskervville italic subtitle and a tiny version pill in the right-side toolbar. Light and dark themes both render with AA contrast
• change iOS-style toggle in the Status column for fast per-row inhale / exhale, on top of the standard wp-admin bulk-actions pattern
• change Foreign admin notices suppressed on the Inhale settings page only, so the screen stays focused on the one decision it exists to support
• change Hardened uninstall. Removes every option the plugin has ever written, single-site and multisite
• change Plugin Directory readiness pass. ABSPATH guards on every shipped PHP file. Every output escaped. Every state-changing request nonce-verified and capability-gated. No remote calls, no tracking, no obfuscation, no bundled

hardening pass

• change wp_die response code 403 + back link on the settings page permission denial path. Access logs and automated clients now see an authorization failure instead of a generic error
• change Row class escaping normalised: the abilities table's <tr class="…"> attribute is always rendered through esc_attr() instead of conditionally injecting the attribute fragment. No behavioral change, but conforms more stric

first public release

• change Discovers every ability registered via the WordPress Abilities API and lists them in a wp-admin native list table.
• change Standard wp-admin selection + bulk-action UX: row checkboxes are selection; Bulk Actions dropdown plus Apply commits Inhale or Exhale immediately. No save-changes step.
• change Row-hover quick actions for single-ability inhale or exhale.
• change Annotation badges on each ability (read-only, destructive, idempotent) sourced from the ability's declared meta; falls back to heuristic inference from the ability name when the registering plugin didn't tag it.
• change Filter views (All, Inhaled, Read-only, Destructive, Unannotated), a search box that matches across name / source / description, sortable columns, multi-select source filter, client-side pagination (20/50/100/All).
• change Sources summary card above the table listing every plugin or theme that registers abilities, with the count per source and deep-links to each source's wp-admin home.

Zero-touch Cowork onboarding (Open in Cowork)

• change .mcp.json sets RESPIRA_BOOTSTRAP_OK=1 so the npx server boots even without a config file present.
• change Existing RESPIRA_CONFIG_FILE, RESPIRA_AGENT_CLIENT, RESPIRA_AGENT_TRANSPORT env vars unchanged.
• change Version label bumped in plugin.json and README.md.
• change Server companion: [@respira/wordpress-mcp-server@6.11.6](https://github.com/webmyc/respira-wordpress/blob/main/mcp-server/CHANGELOG.md#6116---2026-05-11)
• change Zero-touch design doc: drafted 2026-05-10, shipping Family 3b

unified ~/.respira/config.json flow + connect-site rewrite

• change The skill-documented config shape ({url, apiKey}) crashed the MCP server silently on startup because the server required four fields (id, name, url, apiKey). User saw "MCP server still connecting…" forever.
• change The Cowork form echoed pasted API keys into the chat transcript, contradicting the skill's own privacy promise.
• change .mcp.json points RESPIRA_CONFIG_FILE at ~/.respira/config.json.
• change npm dependency pinned to @respira/wordpress-mcp-server@latest so the server schema fix lands immediately.
• change /respira:connect-site skill rewritten: check for ~/.respira/config.json, point user at the dashboard to download it if missing, restart Cowork, test. Includes a "if startup fails" branch that reads ~/.respira/last-startu
• change README.md and INSTALL.md updated to describe the unified flow.

audience-first README rewrite

• change Edit a page without opening WP admin ("Update the headline on my client's homepage to say 'spring collection arriving'", about thirty seconds end to end)
• change Migrate a client site between page builders (sixteen supported paths, week of work into an afternoon)
• change Audit a site before a client meeting (SEO, AI search visibility, accessibility, mobile, technical debt, WooCommerce, with one-click fixes)
• change Clean up a media library in one pass (alt text, compression, dimensions)
• change Manage ten client sites from one conversation (multi-site context follows the conversation naturally)
• change No code changes.

README accuracy pass: 30 skills

• change 8 slash commands for the most common workflows
• change 30 auto activating skills, broken down as:
• change 1 visual reviewer sub agent that shows what changed after every edit
• change Full access to all 180+ Respira MCP tools through the bundled @respira/wordpress-mcp-server
• change All 12 supported page builders: Elementor, Divi 4, Divi 5, Bricks, Oxygen, Breakdance, Beaver Builder, WPBakery, Flatsome UX Builder, Brizy, Thrive Architect, Gutenberg
• change Restructured "What you get" with the correct skill count.

README hero KV + signup copy accuracy

• change Add the canonical Respira-for-Cowork hero image to the top of the README.
• change Drop the "free Lite tier available" line (Lite is not shipped yet).
• change Restate the trial as Maker, 7 days, no credit card required.
• change Show current version and respira.press/cowork link in the README header.
• change Bump plugin.json to 1.0.7.
• change v1.0.6: bundle 26 skills from agent-skills-wordpress, revert to name=respira (slug validation enforces lowercase).

Self-updater fatal on every WP cron tick. class-updater.php:104 called \Respira_License::get_license_key() which has never existed on the core License class — every site that activated the add-on threw Uncaught Error: Call to undefined meth

• fix Self-updater fatal on every WP cron tick. class-updater.php:104 called \Respira_License::get_license_key() which has never existed on the core License class — every site that activated the add-on threw Uncaught Error: Call to undefined meth

drop keytar, fix whoami after login, unstick terminal, warm welcome

• 3. [@respira/cli 0.1.3](https://www.npmjs.com/package/@respira/cli)
• 3. [@respira/sdk 0.1.3](https://www.npmjs.com/package/@respira/sdk)
• 3. [@respira/cli-core 0.1.3](https://www.npmjs.com/package/@respira/cli-core)

fix 307 redirect breaking respira auth login

• change [@respira/cli 0.1.2](https://www.npmjs.com/package/@respira/cli)
• change [@respira/sdk 0.1.2](https://www.npmjs.com/package/@respira/sdk)
• change [@respira/cli-core 0.1.2](https://www.npmjs.com/package/@respira/cli-core)

per-package READMEs on npm

• change [@respira/cli](https://www.npmjs.com/package/@respira/cli) — 9.4 kB README: marketing-forward, WP-CLI comparison, architecture summary, quick start, 34-command reference, AI agent integration, pricing.
• change [@respira/sdk](https://www.npmjs.com/package/@respira/sdk) — 5.7 kB README: developer-focused, createRespiraClient usage, anonymous mode, seven namespaces, builder-native examples, error taxonomy.
• change [@respira/cli-core](https://www.npmjs.com/package/@respira/cli-core) — 6.3 kB README: advanced/builder-facing, documents every frozen v0.1 export (ExecutionCycle, FrameworkHook, ToolChainFunction, TraceEmitter, CycleErro

Foundation release

• change Six-phase execution cycle: LoadContext -> PreHooks -> Resolve -> Execute -> PostHooks -> Return. Deterministic. Traceable. Every command runs through every phase
• change Five framework hook contracts, frozen for v0.1: before_resolve, filter_plan, before_execute, filter_result, after_execute. In v0.1 no callbacks register. v0.2 populates them. NullHookRegistry swaps for ManifestBackedHook
• change Typed ToolChainFunction<T> abstraction for all 34 commands. Each function declares capability (read | write | destructive), domain tags, and prerequisites
• change File-organization convention: one BaseCommand subclass per file, one ToolChainFunction per file, always co-located. Named export <camelCasePath>Function
• change Structured JSON tracing via --verbose, written to ~/.respira/traces/{invocationId}.json. Hard cap 10,000 entries per invocation
• change [@respira/cli 0.1.0](https://www.npmjs.com/package/@respira/cli)

Added: order reads now return customer_ip_address, customer_user_agent and meta_data. Without the request fingerprint and the order meta, the order tools could not support payment-fraud triage at all, and the reporter kept a competing plugi

• change Added: order reads now return customer_ip_address, customer_user_agent and meta_data. Without the request fingerprint and the order meta, the order tools could not support payment-fraud triage at all, and the reporter kept a competing plugi
• change Fixed: the add-on's own test runner exited before printing its results, so a failing test could report success. Any test sorting before version-surfaces was swallowed and the suite still exited zero.

Fixed: the update notice for this add-on could never clear itself. 4.0.2 bumped the plugin header but not the version constant underneath it, and the constant is what the updater reports to the server as your installed version. So every sit

• change Fixed: the update notice for this add-on could never clear itself. 4.0.2 bumped the plugin header but not the version constant underneath it, and the constant is what the updater reports to the server as your installed version. So every sit

Fixed: a site running both Respira and this add-on printed "Ability category respira-woocommerce is already registered" on every request. Both plugins registered the same category, so with the add-on installed the collision was guaranteed r

• change Fixed: a site running both Respira and this add-on printed "Ability category respira-woocommerce is already registered" on every request. Both plugins registered the same category, so with the add-on installed the collision was guaranteed r

Fixed: an agent orders summary could 500 the whole site on hosts that answer plugin bootstrap before WooCommerce finishes waking up. It now waits for WooCommerce's own readiness signal before touching order data, and falls back to an honest

• change Fixed: an agent orders summary could 500 the whole site on hosts that answer plugin bootstrap before WooCommerce finishes waking up. It now waits for WooCommerce's own readiness signal before touching order data, and falls back to an honest
• change Fixed: the Observe governance profile closed only 42 of 277 tools despite its own description promising every write closed. It computed its blocked set from an eleven-family category registry, and a tool in no family was never considered; i
• change Fixed: add_sale_badge and add_low_stock_badge were flagged read-only while actually writing, which meant a governance profile closing writes left them open and the transport withheld the retry fields that make an interrupted write safe to r
• change Fixed: convert_html_to_builder with no builder specified threw a type error on any block-library site (GreenShift, Spectra, Kadence Blocks, GenerateBlocks) instead of converting, because auto-detection asked "is this Gutenberg" by name inst
• change Fixed: all five WooCommerce card/checkout tools now declare edit_target and verification_marker in their schemas; the backend has always forwarded both, but no schema advertised them, so they were unreachable from any client.

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 t

• change 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 t
• change 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
• change 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
• change 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.
• change The missing-changes error no longer advertises a parameter that does not exist. It names only the keys the handler reads.
• change 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.

Fatal error on HPOS stores (PHP 8). The daily license check, which also gathers a small agent-orders summary for the dashboard, could run on the plugins_loaded hook before WooCommerce initialized its order data store. On stores using High-P

• fix Fatal error on HPOS stores (PHP 8). The daily license check, which also gathers a small agent-orders summary for the dashboard, could run on the plugins_loaded hook before WooCommerce initialized its order data store. On stores using High-P

Thrive Architect product pages — description edits didn't appear on the frontend — bulk_update_products with description / short_description wrote to post_content via WooCommerce setters, but Thrive Architect renders from its own wp_postmet

• fix Thrive Architect product pages — description edits didn't appear on the frontend — bulk_update_products with description / short_description wrote to post_content via WooCommerce setters, but Thrive Architect renders from its own wp_postmet

Product category CRUD endpoints and MCP tools (list/get/create/update/delete).

• add Product category CRUD endpoints and MCP tools (list/get/create/update/delete).
• add Product tag CRUD endpoints and MCP tools (list/get/create/update/delete).
• change Product create/update now supports category and tag assignment payloads for safer taxonomy-aware catalog workflows.

Release pipeline reliability: ensures fresh tag/release creation behavior.

• change Release pipeline reliability: ensures fresh tag/release creation behavior.
• change Security hardening parity with experimental-feature gating patterns in core plugin.

Initial WooCommerce add-on release.

• change Initial WooCommerce add-on release.