Every release, in detail.

• New: Kirki specialization. AI agents can build and edit Kirki pages, symbols, popups and templates, manage global classes, page settings and SEO, model and fill content collections, and export form submissions (requires Kirki 6.4.0 or newer). A companion skill covers its features and workflows.
• Fix: Novamira Pro license activation with an empty license key field now asks you to enter your key, instead of reporting it as invalid.
• Minor Fixes

• New: Ollie specialization (requires the Ollie theme 1.4.8 or newer, and Ollie Pro 2.8.3 or newer for its editor extensions): AI agents can explore a site's templates, patterns, styles and the block settings Ollie Pro adds. A companion skill covers the workflows.
• New: MyListing specialization (requires the MyListing theme 3.0 or newer): AI agents can set up listing types, add and maintain listings with their locations and opening hours, and organize categories, regions and tags. A companion skill covers the workflows.
• Minor Fixes

• New: WPML specialization (requires WPML 5.0 or newer). AI agents can translate pages, posts, categories, theme and plugin texts and media themselves, manage languages and what gets translated, or send content to your translators and to WPML's automatic translation, asking before they spend WPML credits. A companion skill covers the workflows.
• Tweak: Read Mode can now be turned on by AI agents and by Novamira HQ when you ask for it. Turning it off stays on the Read Mode page or with WP-CLI.
• Tweak: GenerateBlocks Pro Design Tokens can now be read, created, changed and deleted by AI agents, with values per breakpoint, and used to style blocks (requires GenerateBlocks Pro 2.8.0 or newer). A token that may still be in use is only deleted after you confirm.
• Fix: ACF field groups created by AI agents are now saved on sites that also run WPML, where ACF Pro 6.8 previously removed them.
• Fix: ACF values written by AI agents in a format the field does not take, and display rules with no condition, are now refused with a clear reply, where they were previously saved broken.
• Fix: ACF field groups set up with ACF Multilingual keep their translation mode when AI agents save them.
• Fix: Bricks sites running PHP 8.0 now load Novamira Pro normally, including WP-CLI commands that use PHP 8.0, where Novamira Pro previously stopped with a fatal error.
• Fix: Breakdance elements can now be edited by AI agents on sites running PHP 8.0.
• Fix: Divi sections, rows, columns and groups that AI agents create now use Divi's default flex layout, like the ones built in the Visual Builder, and keep a layout the agent sets explicitly. Pages built by AI agents before this update look exactly as they did.

• New: Read Mode. It is production ready and lets AI agents inspect a site without Novamira's write abilities: turn it on from the Read Mode page under Novamira or with WP-CLI (requires a Novamira version with Read Mode). While it is on, agents can read files and site details through Novamira, and posts, terms, users, comments, options and the database schema, and run read-only SQL queries, through read abilities Novamira Pro adds. On the Read Mode page you can also allow the read abilities of the Novamira Pro specializations, which are on by default, and the read abilities other plugins declare read only, which are off by default; in the Abilities Hub you can turn single abilities off and on. Skills are not available to agents.
• Tweak: GeneratePress: `generatepress-list-sites` reads the cached catalogue of Site Library templates, and the new `generatepress-refresh-sites` fetches it again.
• Tweak: AI agents are now guided to flag potentially overlapping ability groups and suggest choosing one in Abilities Hub. Novamira recommends its own abilities while preserving your choice.
• Fix: Novamira Pro now provides a setup page when the base Novamira plugin is missing or inactive, with a download link and guidance to activate it before setting up the Pro license.
• Minor Fixes

• Fix: Meta Box sites now load Novamira Pro normally again, where version 1.11.1 stopped the REST API, the MCP connection and the block editor from working while the Pro license was active.

• Tweak: ACPT custom field values on comments can now be read and written by AI agents, and the guidance covers tabbed layouts, required fields and values such as prices, measurements, date ranges and files.
• Tweak: ACPT option pages can now be placed under a WordPress admin menu (such as Settings) by AI agents on ACPT 2.1 or newer, the first version that offers this placement.
• Tweak: ACPT field groups can now be read in full by AI agents, including choices, field settings, sub-fields and flexible layouts, to check or repair their setup.
• Fix: Divi pages whose Post Filter holds its filter items inside a text or group module, as the Divi editor allows since Divi 5.13, can now be edited by AI agents, where those pages were previously refused.
• Fix: Weglot API keys defined as constants in wp-config.php (requires Weglot 6.3 or newer) are now used by AI agents, where the setup check, status and cloud sync previously reported a missing key or used an older saved one.
• Fix: Weglot guidance for AI agents now matches what the plugin does with translated URLs and lists every error an agent can receive.
• Fix: ACPT option pages placed under a WordPress admin menu now stay there when an AI agent edits them.
• Fix: ACPT field groups edited by AI agents keep the choices, default choices, sub-fields and field settings the edit does not touch, and groups with dropdowns can be edited on every supported ACPT version.
• Fix: ACPT field groups created or edited by AI agents no longer take fields from other groups, and agents report the field names ACPT actually saved and any part of a change it did not store.
• Fix: Mosaic background, box-shadow and text-shadow variables can now be created by AI agents, where those requests previously failed.
• Fix: Mosaic loops built by AI agents now follow the requested sort order, and blog post loops can show the post excerpt.
• Fix: Mosaic pages built by AI agents now bind templates to single pages and apply theme width and spacing settings as Mosaic expects, and variable references in custom CSS keep working after a variable or collection is renamed.
• Minor fixes

• New: Ghost Mode. Run Novamira on client sites without it showing up for the client's administrators: only the administrators you choose see its interface. It is not a security feature.
• Tweak: Novamira Pro licenses can now be activated, checked and deactivated with WP-CLI.
• Tweak: Elementor Theme Builder display conditions can now be read and set by AI agents (requires Elementor Pro), so a template can be assigned to specific pages without opening the Elementor editor.
• Tweak: Elementor templates created by AI agents are now published by default, and agents report the fields and text Elementor does not keep as written.
• Tweak: WPBakery Page Builder settings set by AI agents are now checked against the choices your version accepts, with a clear reply when a setting does not exist or no longer applies.
• Tweak: All in One SEO guidance for AI agents now matches what the plugin does on sites without All in One SEO Pro.
• Fix: Elementor work by AI agents is more reliable: variable tools stay available on recent releases, dynamic tags bind again on the new page-building surface, and agents no longer claim the site lacks loops, forms or accordions.
• Fix: Divi global presets that carry an id attribute are now flagged to AI agents, since every module using such a preset shares that id.
• Fix: WPBakery Page Builder pages built by AI agents keep their links, grids, custom CSS and layout, including on WPBakery Page Builder 9.0.
• Fix: All in One SEO site-wide settings can now be read by AI agents on sites without All in One SEO Pro.
• Minor fixes

• Tweak: Elementor saved templates can now be created, listed, inspected, renamed, deleted and switched to another template type by AI agents.
• Fix: Memories saved by AI agents or from the Memory admin page now keep their text exactly as written, where code snippets and anything that looked like an HTML tag were previously removed on save while the save still reported success.
• Fix: Elementor templates rewritten by AI agents keep their template type, so a Loop Item, header, footer or other Theme Builder template stays what it was instead of becoming a plain page.
• Fix: Elementor template types set by AI agents are now checked against the types Elementor allows for that page or template, and a template switched to another type moves to the matching group in the Templates list.
• Fix: Elementor templates whose type comes from an inactive plugin (headers, footers and Loop Items while Elementor Pro is off) are left untouched when an AI agent edits them, and the agent is asked to reactivate that plugin first.
• Fix: Elementor's Site Settings (global colors, fonts and other site-wide settings) are no longer turned into a template by AI agents, and a template edit that fails to save leaves the template's type as it was.
• Fix: Elementor Pro Global Widgets edited by AI agents keep holding the same widget: an agent can change its content and style, including the items inside tabs and accordions, and a request to swap the widget or place another one beside it is declined with a pointer to the Elementor editor.
• Fix: Bricks dynamic data tags written without a space before @fallback (for example {post_title@fallback:'Untitled'}) are now reported to AI agents as the plain text the page shows, and the agent is asked to add the space. The Bricks skills now cover the fallback syntax.
• Fix: Bricksforge tools added in Bricksforge 4.0 (Animation Panel, Node Editor, Builder Customizer, White Label and Global Classes) can now be turned on and off by AI agents, and the setup check recognizes them instead of listing them as unknown. On earlier Bricksforge versions they are reported as not available.
• Minor fixes

• New: Dynamic Content for Elementor specialization gives AI agents dedicated guidance for working with the plugin and lets them manage its PDF templates. A companion skill covers its features and workflows.
• New: JetElements specialization gives AI agents dedicated guidance for working with the plugin in Elementor. A companion skill covers its features and workflows.
• New: Ultimate Addons for Elementor specialization gives AI agents dedicated guidance for working with the plugin in Elementor. A companion skill covers its features and workflows.
• New: Happy Addons specialization gives AI agents dedicated guidance for working with the plugin in Elementor. A companion skill covers its features and workflows.
• New: Unlimited Elements for Elementor specialization gives AI agents dedicated guidance for working with the plugin in Elementor. A companion skill covers its features and workflows.
• New: Qi Addons for Elementor specialization gives AI agents dedicated guidance for working with the plugin in Elementor. A companion skill covers its features and workflows.
• New: Element Pack specialization gives AI agents dedicated guidance for working with the plugin in Elementor. A companion skill covers its features and workflows.
• New: HT Mega specialization gives AI agents dedicated guidance for working with the plugin in Elementor. A companion skill covers its features and workflows.
• New: PowerPack for Elementor specialization gives AI agents dedicated guidance for working with the plugin in Elementor. A companion skill covers its features and workflows.
• New: Piotnet Addons for Elementor specialization gives AI agents dedicated guidance for working with the plugin in Elementor. A companion skill covers its features and workflows.
• New: Xpro Elementor Addons specialization gives AI agents dedicated guidance for working with the plugin in Elementor. A companion skill covers its features and workflows.
• New: Bricks changes made by AI agents can be undone. Every content change is saved into a WordPress revision before it is written, so you can roll it back from the post's revision history, and a change is held back while someone else has that post open in the builder unless you ask for it to go through anyway.
• New: Bricks pages are checked on the site before an AI agent reports them as done. It loads the page the way a visitor would, so one that errors, comes out blank or loses its styles is caught and reported as a problem rather than handed over as finished.
• New: AI agents can manage Mosaic sub classes, Variants and variant sub classes, not just top-level Classes, and pick a Variant only from the ones an element supports. Class names are saved exactly as Mosaic would save them from its editor, including its automatic renaming when a name is already taken, and deleting a Class also removes it from the elements that used it, as in the editor.
• Tweak: The Elementor page building tools now offer the new atomic element types only on sites where Elementor has them enabled, so an agent no longer builds a page out of elements the site cannot render. Reading a page that already contains such elements now reports which ones are not registered, instead of returning a tree that looks complete while the page renders empty.
• Tweak: The Elementor page building tools now describe the shape of an element inside their own input schema — which keys a node takes, which of them accept a second spelling, and which are refused — instead of leaving it to the surrounding prose. An agent reading the tools no longer has to guess the shape of the content it is about to write.
• Tweak: An AI agent that pastes a whole section's markup into a single Bricks text element is now stopped and told to build the section out of separate elements, so what it hands over stays editable in the builder rather than arriving as one block of text. Empty sections and containers are reported the same way.
• Tweak: Bricks styles lead on Bricks sites. With an active Novamira design the agent works from your Bricks classes, variables and theme styles first and uses the design to fill gaps or when you ask for it; without one, Bricks is the single source of truth and no design document is created unless you ask for it.
• Tweak: A Divi layout the builder itself would not accept is now saved with a warning naming what that container does take, instead of being refused, and changing a setting that alters what a container may contain now rechecks its contents and reports anything that no longer fits. Divi error messages also name the container's actual variant and only ever suggest something Divi accepts there.
• Tweak: On a Mosaic install that still uses its older class storage, the class and variant tools explain that Mosaic needs updating, while themes, templates, page elements, components, collections and variables keep working.
• Tweak: Memory can now be turned on or off from the Novamira Features page, and its admin menu follows that setting.
• Fix: An Elementor page built with the new atomic elements on a site where Elementor does not have them enabled now comes back as an error naming the feature to turn on, instead of a success reply that leaves the page empty. Elementor silently drops element types it cannot build and saves nothing in their place, so everything an agent sent that way was lost while the write still reported success.
• Fix: Elementor writes are now checked against what was actually stored down to the nested elements, so content dropped below the top level comes back as an error instead of passing as saved.
• Fix: Listing Elementor widgets filtered by the atomic source now returns those widgets, where it previously came back empty on every site, including sites that have the new elements enabled.
• Fix: Narrowing an Elementor widget's controls to a single tab or section now returns those controls, where both filters previously came back empty for every widget on every site. On sites where the tools cannot confirm a widget's controls were handed over in full, narrowing by tab is now refused with an explanation instead of returning a partial list that looked complete.
• Fix: Inserting a ready-made Elementor subtree now accepts either spelling of an element's type, the same as writing a whole page. Inserting used to accept only one spelling, so a subtree an agent had just written could come back refused when it tried to insert that same content again.
• Fix: An Elementor element written without a type is now refused wherever it appears in a subtree, not only when it is the outermost one. Such an element still rendered on the page, but Elementor itself stopped counting it as an element: exporting the page, saving it as a template, and Elementor's own content clean-up all walked straight past it and logged PHP warnings on the way.
• Fix: Reading an Elementor page no longer hands back content the writing tools would then refuse. Any misspelled element keys found on the page are now listed separately instead, so nothing is lost, and rewriting the page clears them for good.
• Fix: An Elementor element that names a widget but no element type is now understood instead of refused, wherever it appears in a subtree — the widget name already says what the element is. This also makes pages that were saved earlier with that gap editable again through either writing tool.
• Fix: The short one-line form for an element's styles now works when writing a page or inserting a subtree, as it already did when adding or editing a single element. The same styles were valid in one tool and rejected by another.
• Fix: The Elementor page building skill now spells out the whole widget discovery call, so building a page no longer stops at that first step. Two of its instructions left out something the discovery tool requires, and an agent that followed either one was turned back with an input error before it could look up a single widget.
• Fix: Elementor content is no longer written to posts that cannot hold an Elementor page, such as another plugin's own template store. A write aimed at such a post now comes back as an error naming the post and its post type, instead of reporting success and leaving behind content nothing ever reads.
• Fix: Elementor's dynamic tags now keep working on the new element types when an AI agent applies one, storing the choice the way Elementor records it so the element shows what it should and the page still saves in the editor. A tag aimed at something no longer on the site, or a value Elementor would reject, is now refused with an explanation before anything is written.
• Fix: An Elementor element that has no link keeps it that way when an AI agent edits anything else on it. Editing only the text used to fill the empty link setting in with a default target and tag, which changed the element on every edit and made an empty link impossible to set back.
• Fix: Elementor settings that hold a structure rather than a single value, such as a link, a form field's options, an element's extra attributes, and display conditions, are accepted in the exact form Elementor stores them in again. A malformed or generically typed value that Elementor would reject anyway is now refused up front, instead of being saved in a shape the editor rejects.
• Fix: Adding or editing a single Elementor atomic element now runs Elementor's own validation over its settings before saving, the same check writing a whole page already had. A setting that used to save and report success, only for Elementor to refuse the element on its next save, now comes back as an error naming the setting, and nothing is saved.
• Fix: An Elementor image setting is no longer offered to AI agents as a place to attach a dynamic tag. The tag belongs on the image source inside the setting, not on the setting itself, so attaching it there was stored in a form Elementor does not read and the image stayed empty; the agent is now told so and pointed at the settings that do take a tag.
• Fix: Elementor elements an AI agent has just added to a page now arrive with their own styling, because the page's stylesheet is rebuilt from the content that was saved. A new icon now keeps the size it was given and a new grid stays a grid, where either could previously come out at default size or collapsed into a single column.
• Fix: The tool that refreshes a page's cached output no longer suggests it also rebuilds the stylesheet: it clears the cached markup only, as it always has.
• Fix: Bricks pages built by AI agents arrive styled on sites that serve CSS from files. The page's stylesheet is now written as part of the change, where it previously stayed empty or out of date until someone opened the page in the builder and saved it again.
• Fix: Bricks typography set up by AI agents loads and applies on the front end, so headings and body text use the family you asked for, and turning a single font option off no longer switches Google Fonts off across the site.
• Fix: Bricks sections built by AI agents stay editable in the builder. Element identifiers are generated by the site and a repeated one is refused before anything is saved, so a section no longer contains elements that cannot be selected, edited or deleted.
• Fix: New Bricks element identifiers must contain exactly six characters before they reach a page or template, while identifiers already stored remain editable through the same tools. Component bodies replace non-six-character identifiers automatically and report each replacement.
• Fix: Top-level Bricks elements written as a whole page, inserted subtree, or new template — plus component instances placed beside a top-level sibling — now store the root parent marker in the integer form its Duplicate command requires.
• Fix: Bricks content changes are read back before an agent reports them as saved, and reported together with the number of elements the page now holds, so work that did not land comes back as a problem instead of a success.
• Fix: Bricks layout settings applied by AI agents take effect on every element type. Spacing and direction are offered per element in the form Bricks accepts there, so values set on headings, buttons, images and the rest apply instead of being dropped.
• Fix: Bricks warnings raised while an agent builds now match your site. Working layout settings on a site with theme styles, and the data Bricks records on the elements themselves — element metadata, global elements and the protected parts of its nested elements — are no longer reported as problems, so a warning is worth acting on.
• Fix: Bricks component properties can be added and changed on an existing component, without rebuilding it and re-pointing the pages that use it. Instances placed before a new property existed keep rendering with that property's default.
• Fix: Bricks component styling reaches every page that uses the component. Editing a component refreshes the stored stylesheet of each page it appears on, and the reply names any page that could not be updated together with the call that finishes it.
• Fix: Bricks components are safe from an AI agent's clean-up. A component you have placed on a page is no longer reported to the agent as an empty band to remove, and a component nothing uses is no longer protected from deletion by pages that exist only as revisions.
• Fix: Bricks global settings can all be changed by AI agents, including the ones your site adds, where anything outside a short built-in list used to be refused as unknown.
• Fix: Bricks variables deleted by an AI agent go to the Bricks trash on sites that keep one, so you can restore them from the Variable Manager the way you would after deleting one yourself.
• Fix: Bricks global classes and theme styles edited with a shorter list drop the entries you removed, so a gradient renders with the stops you kept and a theme style stops applying where you removed its condition.
• Fix: Bricks settings written by AI agents are checked against what your version of Bricks accepts. An interaction trigger or action your build cannot run is refused instead of stored and reported as done, and a setting that holds a list, such as a form's actions, is caught before a single value written there can stop the page rendering.
• Fix: Many Bricks refusals now say what is actually wrong instead of looking like the site had broken. Sending a value Bricks does not accept, naming a setting or post type it does not know, asking for something the site is not set up for, or writing to a page someone else has open in the builder each come back as the specific problem, where before they all read as “the server broke, try again” and an agent could repeat the same impossible call. Refusals whose cause is still ambiguous — chiefly those that report something as not found — are deliberately left as they were rather than labelled with a guess.
• Fix: Applying a Bricks global class to a post that does not exist now says the post was not found, where it previously reported that the post had no content and invited the agent to add some to a page that was not there. Patching an area whose stored content is not a Bricks element tree is likewise reported as damaged content, rather than as an empty area to fill — which would have written over whatever is still stored there.
• Fix: A Bricks page whose stored elements were already broken before an agent touched it is now reported as exactly that, naming what is wrong with the stored page, instead of the failure being attributed to the change the agent was making. Nothing is saved either way, but the agent is now pointed at repairing the page rather than at rewriting a request that was never the problem.
• Fix: Dynamic images and button links bound by AI agents in Divi now show their real values without replacing other image or button details, and custom fields inside loops resolve correctly.
• Fix: Divi Theme Builder templates created by AI agents are now registered through Divi's own storage, so they appear reliably in the builder and apply to their assigned pages. Assignment-only edits preserve unrelated layout bindings, and an invalid assignment is refused instead of applied.
• Fix: Divi interactions created by AI agents now use the trigger names Divi's front end recognizes, so their configured effects run. They are also saved with Divi's enabled field and shown as enabled in the builder.
• Fix: A Divi page with a row nested inside a column can be changed again. Divi's builder lets you nest a row that way, but the tools refused to write such a page back, so a page an agent could read came back as an invalid layout on save; nesting a row inside a column now works from the tools too.
• Fix: Divi fullwidth sections, along with groups, inner columns, and other container modules, can now be built and changed by AI agents, where a page holding one of these previously could not be edited at all. Specialty sections stay partly out of reach: their side-by-side columns cannot be created or replaced, so those writes are refused and the page has to be finished in the Divi builder.
• Fix: Creating an ACF field group now refuses a payload it does not recognize instead of storing it. A malformed or misspelled payload used to silently produce an empty field group with no title, no fields, and no location rules while still reporting success; it now comes back as an error naming the keys at fault.
• Fix: Creating or editing an ACF field group can no longer overwrite an unrelated post. A payload carrying a post id, the shape an agent gets from reading an existing group, used to make ACF rewrite that post instead of writing the field group; post ids in a field group payload are now ignored, and reading a field group's schema no longer includes one.
• Fix: A saved ACF field group is now read back and checked against what was asked for before the write is reported as done, so a group that did not fully persist comes back as an error instead of a false success.
• Fix: Creating an ACF field group that fails this new check is now rolled back, including any fields already written, without touching any other plugin's field groups.
• Fix: Editing an ACF field group that fails this new check is now reported rather than undone: the reply says what did not match and which fields the group holds afterwards, so you can decide what to do.
• Fix: Editing an ACF field group now requires the field group's key and refuses a post id. A number is not meaningless to ACF — it looks the post up by id — so a request that passed one could edit a field group it was never pointed at and then overwrite that group's key with the number, leaving the group unreachable by the key all of its fields still pointed at.
• Fix: The Mosaic tools work again on sites running the latest Mosaic. Mosaic changed where it keeps its classes, and on an updated site every Novamira Mosaic tool used to disappear without a word, including the setup check.
• Fix: Classes an AI agent applies to Mosaic elements now render with their styles, where they previously went into the element's plain CSS class list and lost their styling. A Mosaic class name sent to that plain list is now refused, and the design-system check flags any page that still carries one there.
• Fix: Renaming or deleting a Mosaic variable goes through Mosaic itself, so the variable's CSS name stays unique and a later save in the Mosaic editor no longer fails on a name left behind by an earlier change. Variable listings now also report the CSS variable name each one actually emits.
• Fix: The GenerateBlocks and GeneratePress build skills now send GenerateBlocks content, including GeneratePress Block Element bodies, through the Block Editor Queue and let GenerateBlocks produce each block's CSS itself. They previously told agents to hand-write block markup and CSS and to rebuild the page stylesheet by hand, which could leave blocks invalid in the editor or pages unstyled.
• Fix: Adding, editing or deleting a Fluent Forms field, or replacing a form's fields, no longer throws away the rest of what the form has stored. On a multi-step form the step configuration was silently deleted while the call still reported success, and the form kept rendering and submitting, so nothing pointed at the loss. Everything these tools do not change is now saved back exactly as it was.
• Fix: Tools whose inputs are all optional now accept omitted input through the WordPress abilities route and direct calls.
• Fix: When an AI agent gets a request wrong against the WordPress content tools or the Elementor page tools — an id that does not exist, a value the site will not accept, a page already in the trash, a featured image that is not an image — the reply now says the request was the problem, instead of reporting a server failure. Told the server had failed, an agent would keep retrying the same call unchanged rather than correcting it. Failures that really are the site's own are still reported as such.
• Minor fixes

• New: Blocksy specialization (requires the Blocksy theme 2.1.47 or newer, with Blocksy Companion and Companion Pro also supported): AI agents can set up the theme's global design, per-page layout, header and footer, and Companion features. A companion skill walks agents through the workflows.
• Tweak: Divi modules are now written through the dedicated Divi tools, so what an agent builds saves and renders as expected.
• Tweak: Kadence pages on a site where the block editor cannot run now come back with that as the reason, so the agent reports it instead of working around it.
• Tweak: Novamira Pro specializations can now be turned on or off with their related abilities and skills from the Novamira Features page (requires Novamira 1.12.0 or newer).
• Tweak: Uninstalling Novamira Pro now deactivates its license and cleans up after itself, handing any Context instructions over to the base Novamira plugin and removing its own settings, caches, scheduled checks, and admin notices.
• Fix: Elementor pages now open in the editor showing the content an agent has just written, instead of an older editor autosave. Writes aimed at a revision or autosave id are refused with a message naming the parent post to target.
• Fix: An Elementor write that does not persist now comes back as an error instead of a success reply, so the agent can act on it rather than carry on with a page that never changed.
• Fix: Elementor content and styles that arrive in the wrong shape are now refused with a validation error that names the offending element and the shape expected there, instead of being saved as a style that does nothing.
• Fix: Divi 5 pages composed one section at a time now open complete in the Divi builder, which previously showed only the first section even though the front end rendered them all. Pages built before this release are put back together on the next write.
• Fix: The Divi 5 tools now appear on sites that run Divi through a child theme whose parent theme folder was renamed.
• Fix: Meta Box post types can now be kept off the public site while staying editable in wp-admin, through the standard WordPress visibility settings.
• Fix: The Code Snippets tools work again on Code Snippets 3.10 (free and Pro), and the supported older versions keep working unchanged. AI agents are also told when a snippet is locked, when an edit was not applied, and which snippets a deleted Pro condition was gating.
• Minor fixes

• New: Spectra Blocks specialization (requires the Spectra Blocks plugin 0.0.8 or newer; the Spectra Blocks Pro add-on is detected when present). AI agents can check the install state and version pair, browse the block catalogue with its activation state, read the plugin settings including reCAPTCHA configuration and Global Block Styles, and inspect Popup Builder popups down to their block markup. A companion skill covers the workflows and keeps the legacy Spectra (UAGB) plugin clearly separate.
• Tweak: The Kadence, GenerateBlocks, and GeneratePress build skills now teach agents about editor-assigned block settings (per-block style IDs and layout markers). With the upcoming Novamira release the Block Editor Queue fills them in automatically at finalization; on Novamira 1.11.3 and earlier the skills instruct agents to supply them by hand, so composed blocks no longer save unstyled or with a row's columns collapsed while the queue reports success.
• Fix: The Spectra build and integration skills now walk agents through the real Block Editor Queue pipeline for composing uagb/* content, where they previously pointed at per-block editing tools that do not exist, stopping every Spectra page build at the first step. They also cover Spectra's editor-assigned block_id, so composed blocks no longer save unstyled on Novamira 1.11.3 and earlier.
• Minor fixes

• New: Voxel specialization (requires the Voxel theme 1.7.8.3 or newer). AI agents can build a Voxel site's content model, create and edit listings, set up the templates each post type renders through, and read its commerce and community data
• Fix: WordPress admin pages keep loading normally on sites where the license status is refreshed while the page is being built, instead of ending in a critical error.
• Minor fixes

• New: Oxygen 6 specialization (requires Oxygen 6.0 or newer): AI agents can build pages and templates, style them through the global design system, bind live content and loops, and manage form submissions. A companion skill walks agents through the workflow.
• Tweak: Feedback reports on Novamira now have a place to go: the agent points you to https://novamira.ai/feedback, where you send the report yourself after reviewing it. The agent also offers to prepare one when the same problem keeps coming back after it has genuinely tried to fix it, instead of waiting for you to ask.
• Minor fixes

• New: Weglot specialization (requires Weglot 5.0 or newer). AI agents can set up the connection, configure the original and translated languages, style the language switcher, and control which pages are translated and under which web addresses. A companion skill covers the boundaries.
• Fix: AI agents can now call the tools that take no required input, whatever MCP client they run in. Those tools previously came back with an input error unless the client sent an empty object explicitly.
• Fix: The Elementor editor keeps working inside the Novamira Visual workspace on Elementor 4.1 and newer. Novamira Visual now turns off Elementor's editor isolation policy so the workspace can drive the editor, and site owners who prefer Elementor's isolation can restore it with the novamira/visual/use_elementor_document_isolation filter.
• Fix: Bricks operations that fail now come back to AI agents as real errors instead of replies that look like success, so an agent no longer carries on after a failed color palette, global class, variable, theme style, or dynamic data operation.
• Fix: Bricks template display conditions written by AI agents are always stored in the array form Bricks reads, on every supported Bricks version: recoverable scalar values are normalized to arrays with a warning, while malformed condition containers or entries are rejected with a clear error before anything is saved (Bricks 2.4 skips malformed scalar values entirely).
• Fix: Bricks code elements written by AI agents now honor the BRICKS_LOCK_CODE_SIGNATURES constant on sites that lock code-signature generation, on every supported Bricks version: a write that needs new code signatures comes back with a clear error naming the affected code elements and how to unlock. On Bricks 2.4 this also keeps unsigned code, which would render empty, off the page.
• Fix: Breakdance pages built by AI agents now come out styled without reopening the builder, because Breakdance's CSS cache is rebuilt after every write to the page.
• Fix: Breakdance element design controls are now fully visible to AI agents, including the grouped ones (the Posts Loop list, the Div layout and background) that previously came back as a single "Error" placeholder, so those elements can be styled instead of left at their defaults.
• Fix: Breakdance elements that cannot render until they are configured, such as a form element with no form picked or a checkout element outside checkout, no longer block later edits to the same page. The element is still added and the agent is told the page will not display it until it is set up.
• Fix: Breakdance raw code elements, and raw page content written straight into WordPress on a Breakdance site, now need your explicit confirmation before an AI agent writes them.
• Fix: Beaver Builder pages written by AI agents no longer fail just because the page contains a column group nested inside a column, a normal Beaver Builder structure that reads always accepted. Column group nodes now allow a row or a column as parent.
• Fix: Mosaic Builder design-system variables can now have their value set by AI agents (color, length, font, etc.), not just their name, so recoloring or restyling no longer requires deleting and recreating variables or falling back to inline styles.
• Fix: Mosaic Builder utility classes can now be styled by AI agents per state (hover, focus, etc.) and breakpoint directly, instead of falling back to raw PHP or database edits that could put the site in a critical error.
• Fix: Mosaic Builder HTML attributes (data-*, aria-*, role, etc.) written by AI agents now carry the identifier Mosaic's own validation expects, so they survive a theme export and import instead of silently disappearing.
• Fix: Mosaic Builder component instances can now have their per-instance override edited or cleared directly by AI agents, instead of falling back to raw database writes that could corrupt the design system.

• Tweak: Fluent Forms listing and form building are cleaner for AI agents: listing notifications returns compact rows by default (expandable on request), listing submissions hides trashed entries and searches the IP and browser, and building a form now warns when a setting is passed at the wrong level or a form is left with no fields.
• Fix: If the license server was unreachable, admin pages could slow to a crawl. This no longer happens.
• Fix: Fluent Forms forms and fields built by AI agents now render reliably on the page and in the editor. Newly created forms, all field types (including Address, Name, and choice fields), field settings like placeholder, max length and number min/max/step, and the published or unpublished status now take effect instead of silently producing empty output.
• Fix: A range of Fluent Forms robustness fixes: notifications added by AI agents now send on submission without overwriting hand-made ones, per-form permission checks are enforced, confirmation redirects and email headers reject unsafe values, list filters written as text work, concurrent settings edits no longer overwrite each other, and listing or exporting large submission sets no longer risks exhausting memory.
• Minor fixes

• New: Astra specialization (requires Astra 4.13.5+, free theme plus optional Astra Pro Addon). AI agents can edit the theme settings, color palettes, Header/Footer Builder, and per-page overrides, with more areas unlocked by Astra Pro; a companion skill covers the two tiers.
• New: Avada theme specialization (requires Avada 7.15+). AI agents can edit a curated set of Fusion Theme Options and manage the Global Colors and Global Typography presets; a companion skill covers the boundaries.
• New: Avada Fusion Slider support (requires Fusion Core 5.15.5 or newer, bundled with Avada). AI agents can list the site's sliders and edit their display settings and slides.
• New: OceanWP specialization (requires OceanWP 4.1+, plus the optional Ocean Extra companion). AI agents can edit a curated set of Customizer settings and per-page layout, and with Ocean Extra mount Library templates and turn the Ocean Extra modules on or off; a companion skill covers the boundaries.
• New: Spectra specialization (requires Spectra 2.19+, free plus Spectra Pro). AI agents can browse the block library, manage Popup Builder popups end to end, and turn individual blocks on or off; a companion skill covers the workflow.
• New: Spectra One specialization (requires Spectra One 1.2.2+). AI agents can edit the Global Styles, navigation, and template parts, apply a style variation, and export the whole design as a reusable snapshot.
• Tweak: WooCommerce abilities now register only when WooCommerce is active and at the minimum version, so sites without a store no longer list the WooCommerce category or its setup check.
• Tweak: The Bricks page-building skill now covers query filters and pagination, and the setup check reports whether Bricks' query filters are enabled.
• Tweak: Divi 5 content written by AI agents can no longer carry inline style attributes, since those cannot be edited from the Divi builder controls. The agent gets a clear error pointing to the module's native settings, and inline styles go through only with an explicit opt-in.
• Tweak: Bricks native dark mode can now be set up by AI agents (requires Bricks 2.2 or newer): palette colors accept a dark variant, and reading the palette reports whether the site is ready for Bricks' toggle-mode element.
• Tweak: Meta Box value writes by AI agents can now be scoped to a field group, so a field that does not belong to the group is declined up front instead of being saved as a stray custom field.
• Fix: Elementor pages that AI agents build now import cleanly on any Elementor site, so a page saved as a template moves between sites without errors.
• Fix: GeneratePress Elements now let AI agents read and set their display, exclude, and user conditions, completing the path to building an Element end to end.
• Fix: The Bricks page-building skill now teaches the correct query-loop grid pattern (the loop goes on the card, not the grid container), where Bricks previously rendered one grid per post.
• Fix: Bricks trees written by AI agents now keep parent and children references consistent in every case, and a write repairs any inconsistent link already stored on the page and says so in a warning.
• Fix: Meta Box field groups saved by AI agents no longer fail on Meta Box 2.6.0 and newer when a field carries datalist suggestions.
• Fix: Meta Box field-group reads by AI agents now return the values for every field in the group, where they previously came back empty.
• Fix: Meta Box post types and taxonomies created or edited by AI agents now get working permalinks right away, with no need to re-save the WordPress Permalinks screen.
• Fix: Breakdance Pro licenses are now recognized by AI agents, so a Pro site works with the Pro feature set instead of the free one.
• Fix: Breakdance elements now expose their Settings tab options to AI agents (custom CSS classes, display conditions, draft state), so those can be read and edited like any other element option.
• Fix: Breakdance template abilities now accept the post id in the same form the element abilities use, so AI agents no longer hit input errors when moving between templates and elements.
• Minor fixes

• New: Bricksforge specialization (requires Bricksforge 3.1.8 or newer). AI agents can set up and manage the Bricksforge add-on for Bricks. They turn Bricksforge tools and custom elements on or off (Pro Forms, Popups, Maintenance Mode, Mega Menu, and more), and build Pro Forms through the Bricks page tools, with the field, choice, multi-step, condition, and layout details handled for them. They create and manage Bricksforge popups (opened on page load, click, or scroll, with a Bricks template as the content), and manage the Email Designer templates that restyle WordPress and WooCommerce emails: which emails each template replaces, its subject, whether it is active, and its theme. A companion skill teaches the form recipe and the Bricksforge specifics, and points agents to a live browser workspace for the visual parts (email layout, animations).
• Fix: Responsive style overrides (tablet and phone) that AI agents set on Divi 5 modules now take effect on the page. When an agent provides a breakpoint override, it is stored in the nested shape Divi 5 reads, whether the agent writes it as a nested object or as a single dotted path, so mobile and tablet spacing, sizing, and typography land as intended. This applies when editing a module, adding a module, and setting a page's content, and the agent is told the native nested shape so its next write matches what the builder stores.
• Minor fixes

• New: Dynamic Shortcodes specialization (requires Dynamic Shortcodes 1.9.0 or newer). AI agents can build and troubleshoot Dynamic Shortcodes on your site: they can validate and compose shortcode strings, evaluate them against the live site to preview the real value, discover the fields available for each type, and create, edit, list, and delete reusable Power Shortcodes. A companion skill set teaches the syntax with real examples and shows how to place a Dynamic Shortcode inside each supported page builder (Elementor, Bricks, Breakdance, Oxygen, WPBakery, and the block and classic editors).
• New: AI agents can add interactions (motion) to Divi 5 modules. A trigger on a module (a click, hover, scroll, page load, mouse move, entering the viewport, form submit, or a responsive breakpoint change) runs an effect on it: toggle its visibility, scroll to it, or mirror the mouse for a parallax feel. Agents discover the available triggers and effects and set them per module, and the module stays editable in the Divi builder.
• Tweak: Divi 5 pages that AI agents build and style stay editable in the Divi builder. Agents style through Divi's native module settings, global presets, colors, and variables in a clear order, so a page opens and edits normally in Divi rather than relying on custom CSS. When an agent writes page content, the page stays marked as a Divi builder page, so its layout is preserved the first time it is opened for editing.
• Tweak: When an AI agent edits an Elementor page, only that page's compiled CSS is refreshed. Other pages keep their cached styles and any open editor canvas stays intact, and the site skips a full site-wide CSS recompile on every edit.
• Tweak: AI agents building pages with GenerateBlocks now confirm the finished page renders with its styles before treating the work as done, since GenerateBlocks generates the page CSS from the blocks.
• Fix: Elementor v4 Global Classes that AI agents create or edit now show their base styles as explicitly defined on the desktop class controls in the editor, the same way classes made by hand do. Agents write the base style variant with the "desktop" breakpoint the Elementor editor expects, so the values read as set on the class and stay easy to maintain in the Elementor UI.
• Fix: Breakdance color variables, global classes, and global settings that AI agents create or edit are now saved in Breakdance's native format, so they load correctly in the builder and stay editable in Breakdance's own design-system UI. Tokens saved by an earlier version are still read correctly and rewritten cleanly on the next change.
• Minor fixes

• New: Novamira Visual support for Elementor and Bricks. Novamira Visual is the new live browser workspace in the free Novamira plugin where you watch your AI agent work on your site in real time. Inside it, AI agents can now build and edit Elementor and Bricks pages right in the open editor, so you watch the work happen. This is an early, experimental integration, separate from the standard Elementor and Bricks specializations, so the output is different. For development and staging sites. We would love your feedback in the community group: https://www.facebook.com/groups/novamira
• Minor fixes

• New: Contact Form 7 specialization (requires Contact Form 7 5.8+). AI agents can list, read, create, edit, duplicate, and delete contact forms, and have a built-in reference of the Contact Form 7 form-tag syntax so they author fields correctly. Submitted entries are not included, because Contact Form 7 does not store them.
• New: WPForms specialization (Lite and Pro, requires WPForms 1.8+). AI agents can find forms, create and edit forms and their fields, and manage notifications and confirmations. With WPForms Pro they can also read and manage form entries.
• New: Gravity Forms specialization (requires Gravity Forms 2.7+). AI agents can find forms, create and edit forms and their fields, manage notifications and confirmations, and read and manage entries.
• New: Fluent Forms specialization (free and Pro, requires Fluent Forms 6.0+). AI agents can create and edit forms and their fields, manage form settings, notifications, and confirmations, and read submissions. With Fluent Forms Pro they can also work with payment transactions, subscriptions, draft submissions, and quiz reports.
• New: Formidable Forms specialization (free and Pro, requires Formidable Forms 6.0+). AI agents can create and edit forms, fields, and entries, manage notifications and form actions, and work with form styles. With Formidable Pro they can also read application data and Stripe payment information.
• New: Ninja Forms specialization (requires Ninja Forms 3.13+). AI agents can find, create, edit, duplicate, and delete forms, manage their fields and notifications, and read and delete submissions. Ninja forms can also be migrated to and from the other supported form plugins through the shared form format.
• New: Form migration playbook. A guided, confirmable workflow that helps AI agents move a form's structure from one supported form plugin to another, for example from Contact Form 7 to WPForms, using a shared form format as the common ground. It works across Contact Form 7, WPForms, Gravity Forms, Fluent Forms, Formidable Forms, and Ninja Forms. It covers the form structure only, not submitted entries.
• Fix: Meta Box specialization. Custom taxonomies created or edited by an AI agent are now attached to the post types it specifies, so they appear on the post edit screen and can be queried on the front end. The abilities store and read the post-type link the same way Meta Box's own registrar does, and reading a taxonomy back reflects its real attachment.
• Fix: Meta Box specialization. AI agents can now create, edit, and delete Meta Box relationships that connect your content, and the relationships are saved and stay editable in Meta Box, just like ones set up by hand. This applies when the Meta Box relationships builder is available.
• Tweak: Etch specialization. AI agents can now put hover and focus effects, responsive (mobile) styles, and rules for nested elements into an element's own class styles in Etch, so the whole design stays editable in Etch instead of in a separate global stylesheet. Agents can also create many class styles in one go, which makes styling a full page practical.
• Minor fixes

• Tweak: Elementor pages and templates edited by AI agents now show their changes on the front end even with Elementor Pro's element cache enabled. When reading a page or template the agent can see whether a live element cache is in effect and when it expires, and it can clear the rendered-element cache for one or more documents, including nested templates (which cache independently), so a content or dynamic-data edit takes effect on the next view.
• Tweak: Bricks global variables created by AI agents now stay individually selectable in the Bricks editor. Agents create and edit them, along with the color palette, classes, and theme styles, through Bricks' own design-system tools, which give each entry a unique internal id, so selecting a variable in the editor affects only that variable.
• Tweak: Etch pages built by AI agents now keep their class-based styling editable in Etch. When an agent puts a class on an element that has a matching per-class style record, the abilities connect the record to the element, so the styling shows on the front end and stays editable in Etch's style editor.
• Fix: The two Bricks tools an AI agent reads first when building a page, the setup check and the theme-styles list, now declare a parameter in their input schema, so the agent can always call them.
• Fix: Bricks layout elements (section, container, block, div) built by AI agents are now stored the same way as the ones created in the Bricks builder, so Bricks and its builder add-ons handle them the same way. The page renders exactly as before.
• Fix: Code Snippets specialization. When an AI agent edits an active PHP snippet whose new code fails Code Snippets' on-save validation, the result now flags the snippet as deactivated and includes the validation error, so the agent sees why it went inactive and can fix the code or re-enable it.
• Minor fixes

• New: Beaver Builder specialization (requires Beaver Builder 2.9+). AI agents can build and edit Beaver Builder pages end to end: the row, column, and module tree with native module settings and styling, query loops through the native Posts modules, and Beaver Themer theme layouts and dynamic data. They can also manage the site's Global Colors and global typography, and save and reuse templates, rows, and modules.
• New: JetEngine specialization. AI agents can now create, list, edit, and delete JetEngine custom post types, registered through JetEngine, so a type shows up under JetEngine → Post Types and behaves as a normal WordPress post type, letting an agent scaffold a content type and then fill it with posts (requires JetEngine 3.8.6.2+).
• Tweak: Etch pages built by AI agents now keep their styling editable inside Etch. Agents can create, edit, and delete the per-class CSS records that Etch surfaces in its style editor (the ones shown when you select a class on an element), so the section, component, button, and text styling lives on the element's own class records, editable in Etch's style editor (requires Etch 1.4.19 or newer).
• Tweak: AI agents can now use Divi 5's design system and advanced building features. They can create and reuse global module presets (and set per-module-type defaults), manage the brand color palette and reusable design variables (tokens for spacing, sizes, and more), set the site's global fonts, show or hide modules with display conditions, build Theme Builder templates (custom headers, footers, and body/archive/404 layouts) and control where they apply, and save sections, rows, modules, or whole pages to the Divi Library to reuse across pages, including live-linked Global items that update everywhere when edited. They can also set each module's advanced options (CSS ID and class, link, column gutter, text-shadow), and have clearer guidance for building query loops. Brand colors and tokens bind to modules through CSS variables, so changing one restyles every element that uses it.
• Fix: Disconnecting one item from another in a JetEngine relation via an AI agent now removes the link reliably.
• Fix: Bricks pages built by AI agents can now reliably show JetEngine values on native Bricks elements. JetEngine's dynamic tags appear when the agent lists Bricks' dynamic data, and the agent is pointed to the tag that renders correctly (applies when both Bricks and JetEngine are active).
• Fix: Etch pages edited by AI agents now keep an element's class (and any other HTML attributes the agent did not resend) when the agent changes just one attribute, so class-based styling keeps applying. Untouched attributes are preserved.
• Fix: Divi 5 rows with several columns built by AI agents now display their columns side by side. Laying out a row with multiple columns (a feature grid, stat counters, pricing tiers) produces an even multi-column layout automatically, and adding or removing a column rebalances it; deliberately uneven column widths are honored when set explicitly.
• Minor fixes

• New: SeoPress and SeoPress Pro specialization (requires SeoPress 8.0+; redirects and structured-data schema require SeoPress Pro). AI agents can read and set the SEO of any page, post, category, or tag (the SEO title, meta description, canonical, and search-results visibility), and read your site-wide SEO settings. On SeoPress Pro they can also manage redirects and per-post structured-data schema.
• Tweak: Etch custom fields filled in by AI agents now show on the page immediately. Agents can set the per-post values of Etch's native custom fields, not just create the field definitions, so a value appears right away instead of only after the post is opened and saved in the Etch editor (requires Etch 1.5.0 or newer; older Etch is unaffected).
• Tweak: Etch custom fields created by AI agents can now use the date, time, and select (dropdown) types, in addition to text, textarea, number, and boolean (the three new types require Etch 1.5.0 or newer; on older Etch only the original four are offered, so nothing breaks).
• Tweak: Mosaic pages built by AI agents now stay inside the theme's design system, reusing utility classes and color and font variables instead of hardcoding colors and fonts as one-off custom CSS, and the agent can check its own work and correct anything that drifted outside the design system before finishing.
• Fix: Mosaic pages edited by AI agents now keep an element's existing styling when the agent updates just one part of it. A partial edit used to overwrite the whole element, wiping the classes, colors, fonts, and other settings the agent did not resend, and the same could reset a theme's global settings such as its font and spacing. Untouched settings are now preserved.
• Fix: Divi 5 pages built by AI agents now open in the Divi builder without being wiped. The agent marks the page as builder-built, so the first time it is opened Divi no longer runs its classic-content conversion, which used to replace the layout with an empty placeholder and set the original content aside.
• Fix: Divi 5 modules now display the dynamic content (such as the post title) that AI agents bind to a structured field, like a Blurb's title, instead of coming out blank, because the value is now placed in the field's text where Divi reads it.
• Fix: Elementor v4 global classes created by AI agents now show up styled in the editor itself, not only on the live page. They were written for the front end only, so opening the page in the Elementor editor could load slowly and unstyled with raw class ids showing; the classes are now mirrored into the editor's own context the way the Elementor editor does.
• Fix: Elementor v4 pages no longer fail to save when AI agents set an HTML anchor (CSS ID) on a section. The value used to be stored in a shape the editor rejected on Publish ("_cssid: invalid_value"), so the whole page could not be saved at all, even for unrelated edits; it is now stored as the plain string Elementor expects, and the same setting also works when an agent builds the layout in one pass.
• Fix: Elementor Global Color and Global Typography presets deleted by AI agents are now actually removed. The action used to report success while the entry stayed in the site's Elementor Kit and kept appearing, because the saved list was merged rather than replaced; deletions now persist.
• Minor fixes

• New: Yoast SEO and Yoast SEO Premium specialization (requires Yoast SEO 21.0+; redirects require Yoast SEO Premium). AI agents can read and set the SEO of any page, post, category, or tag: the SEO title, meta description, focus keyphrase, canonical, social sharing preview, and whether it appears in search results, with the indexing choice always applied the right way so a page is never accidentally hidden from or forced into search results. They can also read your site-wide SEO settings, and on Premium create, edit, and remove redirects, including regex patterns.
• New: Rank Math SEO specialization (requires Rank Math 1.0.200+). AI agents can read and set the SEO of any page, post, category, or tag: the SEO title, meta description, focus keywords, canonical, cornerstone, social sharing preview, the schema type, and whether it appears in search results, with the indexing choice always applied the right way so a page is never accidentally hidden from or forced into search results. They can also read your site-wide SEO settings.
• New: All in One SEO specialization (requires All in One SEO 4.0+; term SEO and redirects require All in One SEO Pro). AI agents can read and set the SEO of any page, post, category, or tag: the SEO title, meta description, focus keyphrase, canonical, social sharing preview, cornerstone content, the schema type, and whether it appears in search results, with the indexing choice always applied the right way so a page is never accidentally hidden from or forced into search results. They can also read your site-wide SEO settings, and on Pro create, edit, and remove redirects, including regex patterns.
• Tweak: Custom instructions are now provided by the base Novamira plugin, with a Pro fallback only for sites that have not updated Novamira yet.
• Tweak: Bricks pages built by AI agents now stick to native Bricks elements and reusable global classes instead of reaching for raw Code elements or scattered, hard-to-edit custom CSS, and a raw code/HTML element is no longer added on its own during a build — using one now takes a deliberate, explicit opt-in.
• Minor fixes

• Tweak: Breakdance pages built by AI agents now come out properly styled, because the agent can discover the available elements and their design controls instead of leaving them unstyled.
• Tweak: Breakdance pages can now be built or fully replaced by AI agents in a single pass, with element names validated and auto-corrected as the page is written, so a page comes out complete and editable instead of as a blank canvas or with "Missing Element" placeholders.
• Fix: Breakdance pages built by AI agents now place the correct elements (sections, columns, headings, the modern Image, query loops) instead of failing with "This element is missing" on the canvas, and no longer fall back to the deprecated Image V1. A mistyped or wrong-cased element name is auto-corrected, or rejected with a suggestion, so a page no longer ships broken.
• Fix: Breakdance template visibility conditions set by AI agents no longer corrupt the Breakdance Templates screen, and conditions configured in the Breakdance editor are now read back correctly instead of appearing empty.
• Fix: Breakdance templates built by AI agents can now be scoped to a custom post type, not just the built-in ones, because the right template type for each post type is now discoverable.
• Fix: Bricks pages built by AI agents now render Media Library SVGs and inline-code elements that previously saved but came out blank (inline code still requires Bricks code execution to be enabled, and the agent is now told clearly when it is off), and query loops on layout containers (block, div, section, container) no longer raise a spurious validation warning.
• Fix: Bricks theme styles built by AI agents now flag a setting placed outside its group, which previously saved but produced no styling, so the mistake is caught instead of silently doing nothing.
• Fix: Bricks pages edited by AI agents now keep every section's existing layout order. A change to one section no longer silently reorders the contents of other, untouched sections.
• Fix: Elementor pages built by AI agents in the new v4 editor now correctly attach Global Classes to an element, instead of producing a state the editor rejected with "classes: invalid value" when you went to save the page.
• Fix: ASE (Admin and Site Enhancements) Pro specialization. Custom field groups created by AI agents now register correctly with ASE, so their fields read and write values immediately, instead of the group saving but every field coming back empty.
• Minor fixes

• Important: requires Novamira 1.6.0 or newer.
• New: Etch specialization (requires Etch 1.4.19+). AI agents can build and edit Etch pages end to end: element tree, reusable components, templates, loops, conditional visibility, dynamic data, and global styles, plus Etch registered post types, taxonomies, and custom fields.
• New: Divi 5 specialization (requires Divi 5.0+). AI agents can build and edit pages on Divi's new block based engine: module tree, sections and modules, design options, and loops over CMS content.
• New: Breakdance specialization (requires Breakdance 2.7+). AI agents can build and edit Breakdance pages: element tree, element and page settings, query loops, templates, and global blocks.
• New: Mosaic specialization (requires Mosaic 1.0.3+). AI agents can build and edit Mosaic pages end to end: element tree, loops, and the builder's design system.
• New: WPBakery Page Builder specialization (requires WPBakery Page Builder 6.5+). AI agents can build and edit pages end to end: element tree (including grid items), custom CSS, page settings, and templates with append, prepend, and replace modes; they can also register custom WPBakery elements.
• New: GeneratePress specialization (requires GeneratePress 3.0+; some abilities also need GenerateBlocks or GP Premium 2.0+). AI agents can build pages with GenerateBlocks and manage GeneratePress global styles and design tokens, with query loops for CMS content.
• New: Kadence specialization (requires the Kadence theme 1.2.0+). AI agents can build pages with Kadence Blocks and manage Kadence theme design settings.
• New: WooCommerce specialization (requires WooCommerce 9.0+). AI agents can discover and manage your catalog end to end: list and read products with rich filters, create and edit simple and variable products and their variations (pricing, stock, SKU, dimensions, images), organize categories, tags, global attributes, and shipping classes, and read store settings. Force deletes cascade safely to variations and attribute references.
• New: Code Snippets and Code Snippets Pro specializations (requires Code Snippets 3.6+). AI agents can list, read, create, edit, activate, deactivate, and delete PHP, JavaScript, CSS, and HTML snippets.
• Minor fixes

• Fix: Meta Box specialization. Field groups created or edited by AI agents now open correctly in the MB Builder admin editor, with all choices on select / radio / checkbox-list / advanced-select / autocomplete fields preserved regardless of whether the agent supplies them as a `{value: label}` map or as a list of `{value, label}` objects. The list form used to collapse to a single empty-keyed entry in storage, hiding every choice except the last one.
• Tweak: Meta Box specialization. AI agents now detect which Meta Box extensions are installed (term meta, comment meta, user meta, group field, custom table) and refuse operations that would silently no-op without the right extension, naming which one is missing. When custom-table storage is in use, the agent is told to warn you that reads and writes through this integration do not address the custom table.
• Minor fixes

• Fix: Elementor's Site Settings typography set by AI agents now scales smoothly with the screen size. Responsive sizes like `clamp()` used to be flattened to a single fixed value.
• Fix: Elementor v4 Global Variables of type "size" now accept fluid CSS expressions (`clamp()`, `calc()`, `min()`, `max()`, `var()`) when AI agents create or edit them, so fluid design tokens can live in one place instead of being inlined into every style that uses them.
• Fix: Bricks global classes set by AI agents now support the `%root%` placeholder in custom CSS, matching the Bricks editor convention. Custom CSS rules that used to be silently dropped now render correctly.
• Tweak: Bricks pages, theme styles, and global classes built by AI agents now follow the conventions a human would use in the editor: typed controls instead of opaque CSS, the conventional section > container > block-level nesting on content sections, and the semantic `p` tag for body text. Theme styles and classes built this way stay editable from the Bricks UI.
• Tweak: Bricks pages built by AI agents now use a Query Loop for sections that show repeated CMS content (blog grids, portfolio listings, services, team members, rentals, anything you manage from the WordPress admin), so the section updates as you add or edit entries. Static cards are still used for fixed UI sections like pricing tiers, feature pillars, and hero blocks.
• Tweak: Elementor pages built by AI agents now use a query widget for sections of repeated CMS content (blog grids, portfolio lists, services, team members, rentals, anything you manage from the WordPress admin), so the section updates as you add or edit entries. Works with Elementor Pro's Loop Grid or Posts widget, or third-party query widgets. Static widgets stay for fixed UI sections like pricing tiers, feature pillars, and hero blocks.
• Minor fixes

• New: ACF specialization. AI agents can manage field groups and read and write field values on any post, user, or term (requires ACF 6.5+). With ACF Pro, also post types, taxonomies, and options pages registered through ACF.
• New: JetEngine specialization. AI agents can manage JetEngine meta boxes, options pages, and Custom Content Types (both the type definitions and the records inside them), with a dedicated workflow skill that activates when agents work on JetEngine (requires JetEngine 3.8.6.2+).
• New: Meta Box specialization. AI agents can manage field groups, custom post types and taxonomies, settings pages, and relationships, and read and write field values on any post, user, term, comment, or settings target. Includes a dedicated workflow skill (requires Meta Box 5.11.2+).
• New: Pods specialization. AI agents can model and populate Pods-defined Custom Post Types, Taxonomies, Advanced Content Types, Settings Pages, fields, groups, and items (requires Pods 3.2.1.1+).
• New: ACPT (Advanced Custom Post Types) specialization. AI agents can manage ACPT custom post types, taxonomies, meta groups, and option pages, and read and write field values on posts, terms, users, and option pages. Includes a dedicated workflow skill (requires ACPT 2.0.52+).
• New: ASE (Admin and Site Enhancements) Pro specialization. AI agents can manage custom field groups, custom post types, and custom taxonomies, and read and write field values on posts, terms, and options pages. Includes a dedicated workflow skill (requires ASE Pro 8.7+).
• New: AI agents now reason about post types, fields, taxonomies, options pages, and relationships using a shared vocabulary, so the way they talk and work stays consistent no matter which field plugin is in use.
• New: AI agents now have a guided workflow to follow when asked to move content from one field plugin to another.
• New: AI agents are now reliable at filling in Bricks dynamic data and Elementor dynamic tags from your field plugins, so widgets show the actual field value instead of literal text or an empty result.
• Minor fixes

• New: "Novamira feedback" skill. When you ask the agent to share feedback on a Novamira tool (something that didn't behave as expected, an unclear result, a friction point), it composes a sanitized English report with no personal data, content, keys, or URLs, that you can review and send to Novamira support.
• Tweak: Bricks pages built by AI agents now reuse your site's existing styles instead of typing colors, sizes, and spacing into every element. Before adding anything the agent checks what's already there (Bricks variables, global classes, palette colors, theme styles), sets up only what's missing once, and uses those by name in the page. Change a color or a spacing value later and every page that uses it updates automatically.
• Tweak: AI agents now produce cleaner widget content in Elementor. Headings, buttons, and other text widgets get plain text instead of accidentally embedded HTML; rich-text widgets get only inline formatting (bold, italic, links); layout (alignment, width, typography, spacing) flows through each widget's own controls. The HTML widget remains the place for free-form HTML.
• Fix: Bricks header/footer templates built through Novamira Pro abilities now save their elements in the right area, so the Bricks editor shows them instead of opening empty.
• Fix: Building responsive Elementor pages through AI agents now works end-to-end. Asking the agent for tablet or mobile font sizes, padding, alignment, etc. used to silently produce only the desktop value, because the per-breakpoint values were rejected before reaching Elementor. They now persist and render in the right media queries.
• Fix: Elementor pages built by AI agents now produce readable class names on sections that have a natural name (hero, footer, pricing card), so the rendered HTML and CSS are inspectable in DevTools and stylable from custom CSS.
• Fix: The local-style chip in the Elementor editor for elements built by AI agents now shows "local" (matching Elementor's native convention), instead of a cryptic auto-generated id.
• Fix: When Elementor's Atomic Widgets experiment is turned off, the setup check now reflects that correctly and the agent falls back to the legacy widgets, instead of being told the atomic path is available and failing halfway through.
• Minor fixes

• Fix: WordPress plugins page showing an update even if no update was present
• Fix: Elementor content reads now count all elements in the page tree, including children nested inside containers.
• Tweak: Clarify Elementor schema guidance to avoid broad style control dumps when narrower reads are enough.
• Minor fixes

• 🎉 First release!

Tweak

• Hostinger Agency hosting websites now appear in Sites next to regular Hostinger hosting, detected automatically with the same API token. Hostinger does not let HQ install plugins on Agency sites, so install and activate Novamira in WordPress, turn on AI Abilities, then use Connect. Accounts without Agency hosting keep listing their sites as before. Thanks to AGENTUR.STUDIO for contributing the tweak.

Fixed

• A site can be added manually by typing just its domain, such as example.com. HQ connects over https://, where the form previously refused the address with "Please enter a URL" until a scheme was typed.
• One-click setup of Claude Code and Codex works again when the novamira-hq terminal command is not enabled, as on a fresh Windows install. Before, they were registered with --v8-flags=--mcp instead of --mcp and could not connect to HQ. Setting the client up again from HQ now replaces such a broken entry instead of reporting that one already exists.

Added

• SandyWP can now be connected with an API key. HQ lists your sandboxes with their status and expiry, can create new ones from the command line, and can set up Novamira on a ready sandbox by uploading and activating the official plugin, never overwriting a Novamira folder that is already there. HQ cannot turn on AI Abilities on SandyWP, so enable them manually in the Novamira settings in WordPress before connecting.

Tweak

• Sites running Novamira 1.12.10 and newer, which name the full-access OAuth scope full_access instead of mcp, can be set up and connected again. Novamira setup accepts them, and the bundled Novamira CLI is updated to 1.3.6 so login and existing connections keep working.

Fixed

• Rocket.net sites that have a staging site now show both in Sites: the production site is listed as live and its staging site appears beside it. Before, HQ listed a production site as staging and left its real staging site out.

Added

• Read Mode can now be turned on for a connected site from its menu in Sites, and from the Novamira Pro page after installing Pro. HQ first checks the site, then turns Read Mode on through Novamira Pro. It needs an up-to-date Novamira Pro with an active license. HQ does not turn Read Mode off: a WordPress administrator does that on the Read Mode page in the Novamira menu or with wp novamira read-mode disable.

Changed

• The Windows installer and Novamira HQ for Windows are now signed by our company, Ovation S.r.l., so Windows and antivirus software can verify where they come from.

Added

• WHM servers can now be connected with a reseller's API token as well as root's: enter the reseller's user name as the WHM user. HQ then lists WordPress, creates and lists backups only for the accounts that reseller owns, and sets up Novamira with the temporary installer after your approval, since WHM's WP Toolkit does not accept reseller tokens. The reseller needs the list-accts privilege, and create-user-session for the installer; when one is missing, HQ names it.

Changed

• Windows releases now ship only the installer, novamira-hq-setup-windows-x86_64.exe. The portable novamira-hq-desktop-windows-x86_64.exe is no longer published; download the installer from https://novamira.ai/hq if your version does not offer the update.

Changed

• The bundled Novamira CLI is updated to 1.3.4. On Windows, a site profile that stores its credentials in a file can log in again after its stored credential is removed, including after a failed token refresh, instead of stopping with an internal error.

Added

• Configure your AI now includes Antigravity. Antigravity cannot add a local server by itself, so HQ gives you the configuration to paste into ~/.gemini/config/mcp_config.json. Antigravity, the Antigravity IDE and the agy CLI all read that file.
• When Novamira HQ runs from a different place than before (moved, reinstalled, or installed after using the portable Windows app), Configure your AI lists the AI clients that still start the old location and offers the fix for each one. On macOS it also warns when Novamira HQ runs outside Applications.
• Windows now has an installer. It installs Novamira HQ for your user account in a fixed folder, adds it to the Start menu and to Installed apps, and updates replace the app in the same place, so AI clients you configured keep working. Uninstalling keeps your settings and credentials.
• cPanel hosting accounts can now be connected with the HTTPS cPanel address (panel URL), the cPanel username and an API token. HQ lists WordPress at the root of each domain, creates and lists whole-account backups (they count against the account's disk quota), and sets up Novamira: through WP Toolkit when the account has it, otherwise, after your approval, through a temporary installer that removes itself after one run; when Novamira is already installed, HQ uploads only that installer, no ZIP. Restoring backups, clearing caches and changing PHP are not available through cPanel's user API.
• WHM servers can now be connected with the HTTPS WHM address and a root API token. HQ lists WordPress at the root of every cPanel account's domains, creates and lists account backups, and installs Novamira through WHM's WP Toolkit or, with your approval, a temporary installer.

Fixed

• On Windows, Novamira HQ no longer stops at startup with "The application acknowledgement record is unreadable or unsafe" when the Windows user name (or the folder that holds HQ's data) contains letters outside ASCII, such as Ö, Ş or é. HQ passed those paths to its permission check in a form Windows PowerShell misread.
• On Windows, opening Novamira HQ from the Start menu no longer leaves a console or Windows Terminal window open beside the app.
• On macOS, Claude Code started from a terminal no longer stops with "suspended (tty input)" when it starts HQ's connector, and moving the mouse no longer prints stray characters at the prompt. HQ's lookup of the programs installed on the Mac took over the terminal and did not give it back.

Changed

• The bundled Novamira CLI is updated to 1.3.3. When site-cli auth login opens the browser it now also prints the authorization URL, so it can be opened in the browser where you are signed in to WordPress, and a login that times out explains how to retry.

Fixed

• In Sites, each hosting environment now shows as connected only when its own address has a WordPress connection. Before, a Plesk subdomain could borrow its parent domain's connection, and a Kinsta or WP Engine environment could borrow another environment's, so Install Novamira Pro and Disconnect acted on the wrong site. An environment connected under an address other than its own now shows as not connected until it is connected with its own address.
• On Linux, HQ now detects an installed secret-tool, so hosting credentials and the Pro licence key save to the Secret Service instead of HQ reporting that the OS credential service is unavailable.
• Cloudways accounts can now be connected. HQ sent the Access Token in a header Cloudways no longer accepts, so every attempt failed with HTTP 400 "Check the access token parameter" and the token never showed as used.
• Backup lists in Hosting tools and the restore backup menu now show when each backup was created as a readable date in your computer's time zone, with the zone named next to it, instead of a raw provider timestamp. If the time zone cannot be determined, dates are shown in UTC.
• Hosting tools reports now show file sizes in readable units, such as 683 KB, instead of raw byte counts, and long values such as backup file names wrap inside their column instead of overlapping the next one.

Added

• xCloud hosting accounts can now be connected with an API token. HQ lists WordPress sites and their staging sites, creates backups, purges the page cache, updates plugins and themes, and shows access logs and site events. Without a team, HQ uses the first team the token can access. The xCloud API cannot install plugins, create or push staging sites, or restore backups, so those actions stay unavailable for xCloud.

Fixed

• Connecting a site that is already connected, with or without a different name, now reuses the existing connection instead of adding the site twice.
• Local development sites on *.localhost domains can now be connected over HTTP, matching the bundled Novamira CLI. Sites on .local domains connect over HTTPS, and HQ now explains how to enable it when plain HTTP is entered.
• In the desktop app, site connections now trust certificates in the system trust store, such as the one Local installs for HTTPS .local sites.
• When a site cannot be reached or is not ready during connection, HQ now asks whether Novamira is installed and active. The message points to Setup Novamira only where the dashboard offers it for that site.
• File uploads through the HQ MCP connector now receive the temporary upload token needed to transfer the file, where it was previously hidden.

Added

• Plesk hosting accounts now list domains even without WP Toolkit. With WP Toolkit active, HQ can discover WordPress installations, set up Novamira Free, create and restore backups, and copy files or databases between selected installations, including across domains.

Tweak

• Connecting a site that is already ready for Novamira now opens authorization sooner.

Fixed

• Hosting account names now accept accented characters, and validation errors let you correct the details and retry.
• Windows desktop startup now works from shortcuts without administrator access or downloading native libraries at launch.
• Windows credential storage and site connection checks now work reliably, including when authorization verification takes longer to complete.
• macOS command registration now uses the signed standalone launcher, including after moving the app.
• Novamira setup now accepts WordPress development builds such as 7.2-alpha-63789 when their numeric version meets the required minimum.
• After connecting a hosting account, HQ now confirms verified access and links to Sites without showing an actions table that was not verified for that account.
• Windows onboarding can save its acknowledgement without running Novamira HQ as an administrator. Private storage retains the current user's ownership while its access rules are secured; write failures now show a useful message.

Added

• Initial @novamira/hq package: hosting provisioning CLI and local dashboard.
• The hosting command tree and the config hosting-profile commands: 70 subcommands over eight providers, all rendering the v1 envelope.
• Focused contract tests freeze the v1 command surface.
• hosting novamira setup: installs and activates the Novamira plugin over provider WP-CLI, enables the two novamira_ai_abilities_* options, verifies the site against HQ's own copy of the site CLI's v1 compatibility matrix, and prints the novamira auth login <url> handoff. HQ writes no site credential, stores no site profile, and creates no WordPress user, so the Go program's --username, --app-name, --site-profile and --replace-profile flags and its rest_url / username / credential / site_profile / config_path output fields are gone permanently.
• The compatibility preflight: one public, unauthenticated GET {siteUrl}/.well-known/oauth-protected-resource per setup run, with no Authorization header, same-origin manual redirects, a 256 KiB ceiling and a bounded retry band. A failed check fails the invocation and names the check; --no-compat-check skips it and says so in the output.
• The server_unsupported error code at exit 4, for a site that cannot run the plugin — its PHP version, its WordPress version, the installed plugin's version, its REST contract, its feature flags, or its published compatibility document.
• NOVAMIRA_HQ_ALLOW_INSECURE_HTTP=1 accepts a plain-HTTP site URL that is not loopback, and a plain-HTTP loopback package registry; HQ never reads the site CLI's NOVAMIRA_ALLOW_INSECURE_HTTP.
• The local dashboard (novamira-hq dashboard): loopback-only binding, a per-process mutation token carried in a header and never in a URL, a DNS-rebinding guard, and seven pages driven by Datastar over SSE.
• novamira-hq skills list | get [name] | path [name], over the two packaged bundles core and hosting. No HQ command writes a skill to disk: the Go program's skills install and setup, which hand-wrote an agent stub and symlinked ~/.claude/skills/novamira at it, are deleted rather than ported.
• novamira-hq doctor [--offline] [--fix]: nine ordered checks with a pass/warn/fail severity and output-safe evidence. A produced report is a successful invocation whatever its status, --offline performs no network operation of any kind, and --fix may only repair private-path permissions and create the state directory.
• novamira-hq update [--check]: npm-only self-update. It reads the latest dist-tag of @novamira/hq over HTTPS — anonymously, carrying no cookie, token, profile, credential, provider or telemetry data — and installs with npm install --global --ignore-scripts or the Bun global equivalent. The Go program's GitHub release download, checksums.txt verification, archive extraction and in-place executable replacement are deleted, not ported, along with the upgrade alias.
• A background release notice, at most one registry request per 24 hours, cached in state/update-check.json under HQ's own namespace. It is suppressed — request and state write included — by --quiet, --json, NOVAMIRA_HQ_UPDATE_CHECK=0, dashboard, doctor --offline, and any invocation whose stderr is not a terminal.
• install.sh and install.ps1, published as GitHub release assets. They install the package with --ignore-scripts, smoke-test it with novamira-hq doctor --offline, and register the bundled agent skill through an exactly pinned skills@1.5.18. They then install @novamira/cli globally as a last step, so connected-state detection and the dashboard's Connect action work on a fresh machine. It is a separate global package and never a dependency of @novamira/hq: NOVAMIRA_HQ_SKIP_SITE_CLI skips the step, a failure is reported without failing the install, and neither script ever runs the novamira executable.
• The installers add /Applications/Novamira HQ.app on macOS when that folder is writable, otherwise falling back to ~/Applications; a freedesktop menu entry under ${XDG_DATA_HOME:-~/.local/share}/applications on Linux; and a **Novamira HQ** shortcut in the current user's Start Menu on Windows. Opening one runs novamira-hq dashboard --open using the exact HQ entry point and Node.js executable resolved at install time.
• bun run package:acceptance: packs the tarball, installs it into a throwaway prefix and exercises the installed executable offline. It runs on Linux, macOS and Windows in CI, and again in the release job against the published version.

Fixed

• Login and site commands now avoid failures caused by WordPress displaying error notices in their responses.

Fixed

• Windows profiles using file-based credentials can now log in again after their stored credential is removed, including after a failed token refresh. Missing credentials no longer cause an internal error.

Changed

• The installers can now set up the Novamira skill for Grok Build, MiniMax Code, Posit Assistant, Kimchi, fx, and Sarvam Code. They now require Node.js 22.20 or newer.

Fixed

• auth login now prints the authorization URL and a waiting notice even when it opens the browser, so the URL can be opened in the browser where you are signed in to WordPress when the system browser is a different one. A login that times out now explains how to retry.
• Bundled agent guidance now tells agents to read login output while it waits and relay the authorization URL, instead of blocking silently.

Fixed

• HTTP connections to local development sites using *.localhost domains were incorrectly rejected.
• Site profile names now accept accented letters for login, selection, and management.
• Windows: auth login now opens the system browser when started from a bundled desktop app, instead of leaving the authorization waiting without a browser.
• Sites running WordPress development builds such as 7.2-alpha-63789 can now connect when their numeric version meets the required minimum.

• Add managed command-prefix rendering for bundled core guidance, full references and JSON output. Embedded distributions can use novamira-hq site-cli while preserving site-owned guidance and Ability identifiers.
• Replace standalone update guidance with the distributor's update hint in managed mode.

Added

• Public @novamira/cli/entry callable entry point with a managed-distribution option that suppresses update checks and delegates updates to the distributor.
• Offline compiled Deno acceptance for the entry point and bundled guide data.
• Deno diagnostics report the actual runtime instead of its Node compatibility version.

Fixed

• auth login recovers a site whose OAuth client registration is gone, which happens when the plugin is reinstalled, the site is restored from a backup, or the registration is old enough to have been pruned. The login now confirms the site still holds the stored client before opening the browser, and registers a new one when it does not, instead of sending the browser to a page that answers Unknown client_id. while the CLI waits out its timeout.
• Windows: Credential Manager operations now preserve PowerShell's if/elseif/else chain, fixing OAuth login failures after approval and failed credential reads and deletes. Windows CI now exercises a real credential write, read, replacement, and delete round trip.

Added

• sites rename <name> <new-name> renames a site profile, moving its stored OAuth credentials with it and invalidating the old profile's cached Ability metadata. It never changes the site URL, origin, or grant, and it does not revoke remote access.
• The installers run unattended: set NOVAMIRA_AGENT to choose the agent that receives the Novamira skill, or NOVAMIRA_SKIP_SKILL=1 to install only the CLI.

Fixed

• Linux: Secret Service credential storage is now detected when the installed secret-tool does not support the non-portable --version option.
• Windows: OAuth credentials with realistic access and refresh token lengths now fit within Credential Manager's credential-blob limit.

Added

• auth login --device authorizes with a device code instead of a local browser, for SSH sessions, containers, and any host whose browser cannot reach a loopback listener on the CLI. The CLI prints a verification URL on the site and a short user code, then polls until the code is approved; it opens no port and launches no browser. Sites that do not advertise the grant report server_unsupported, and the browser flow still works there.

Changed

• The core guide now keeps agents proactive: setup, discovery, and description run without narration, and the user is involved only for mutation approval, browser sign-in, a genuine ambiguity, or a failure they must act on.

Fixed

• Ability failures now show the actionable error message returned by WordPress instead of replacing it with a generic REST or schema-validation message.
• File-editing refusals such as identical strings, missing matches, and multiple matches now report a non-retryable validation error instead of an internal error.
• discover no longer stalls on sites with many Abilities; the whole discovery is cached in one batch.
• Windows: doctor inspects and repairs permissions in one helper process instead of one per target.
• Windows: hardening no longer fails when Set-Acl reports a missing SeSecurityPrivilege but the permissions are already correct.
• Windows: interrupted commands no longer leave powershell.exe running.
• Windows: paths that are not plain ASCII, such as C:\Users\José, are hardened and verified correctly.
• The Ability cache stays within its size budget during a large discovery and reclaims abandoned temporary files.
• doctor no longer fails when another novamira process removes a lock file mid-check.
• A discovery that fails part way keeps the records it already refreshed.

Changed

• Login now always grants full access, without access modes.
• The minimum compatible Novamira server version is now 1.11.1.

Fixed

• Windows: auth login failed with an internal error after a successful browser sign-in and stored no profile. ([#1])
• Windows: doctor always reported storage.permissions as failing, and doctor --fix could not repair it.
• Windows: credential storage and browser launch failed when the CLI was run from a PowerShell 7 session.
• NOVAMIRA_ALLOW_INSECURE_HTTP is now honored on every request path.
• Reentrant profile locks fail immediately instead of stalling for the ten-second lock timeout.