v1.22.0

The Onboarding wizard now turns on automatic updates for Digitizer Pro Tools itself, under the checkbox that was already there.

Why the plugin is included while the baseline's GitHub items are not. Core's auto-update lists are answered by the WordPress.org update API, which has never heard of elementor-mcp or mcp-adapter — an entry there is a claim nothing acts on, so those items stay out. This plugin carries its own update checker, which writes its releases into the same transient core reads, so WordPress installs them unattended exactly as it would a plugin from the directory.

It happens in a step of its own, before any item. Hanging it off an item's success meant that unticking every row, or having every selected install fail, left a ticked box promising an enrolment that never happened.

A run with nothing ticked is now a run. Both options below the list are independent of it, and the button previously did nothing at all — which took the theme cleanup down with it even when its own box was ticked.

A refused write is reported as one. update_site_option() answers false both for a failed write and for a value that is already set, so the two are told apart: an entry already on the list is answered before any write, and everything else reports the write's own result.

The same permissions still apply as to everything else the checkbox does: update_plugins, manage_network_options on multisite, and core's own answer on whether the site processes background updates at all.

Verified with 315 assertions across six stub harnesses, php -l and node --check clean, the four Plugin Check security sniffs at zero, and a Hebrew catalog of 607 strings with nothing orphaned or missing. Three review rounds, three findings, all real.