Carry the canonical comment sentences Component init() docblocks read "Hook registration.", get_instance() and the capability filters are summarised the way the majority phrases them, and the network activation loop carries the two canonical sentences about the lifted site cap and the restore inside the loop. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CVrFykSreGPwV1hTiRdQBY
Run the upgrade from init at priority 5, on every request The routine hung off admin_init after register(), which is the ordering that once armed the default_option trap this plugin's migration was bitten by. init fires on every request and is where the majority of the collection runs maybe_upgrade() now; the bootstrap registers it so the admin-only Settings component no longer has to, and the migration runs before register_setting() installs its default. The suite helper now clears the plugin's rows in set_up, because the hook fires once while the suite boots and the stamped version row would gate migrate() out of every test. The registered-default regression test keeps the filter live by hand so a later hook move cannot rearm the trap silently. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CVrFykSreGPwV1hTiRdQBY
Rename the canon methods to the collection's spellings markers() and register() are the names the majority of the nineteen settled on; this plugin carried get_versions() and register_settings() for the same two jobs. Callers and tests follow. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CVrFykSreGPwV1hTiRdQBY
List the settings constants in the order their siblings read GROUP now precedes PAGE in WP_PluginsUsed_Settings, the order every other settings class here lists them -- group, then page slug, then capability. The docblocks travel with their constants; nothing else moves. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CVrFykSreGPwV1hTiRdQBY
Flatten the uninstall guard to the one-liner the rest uses Every ABSPATH guard here is already the one-line defined() || exit form; uninstall.php still carried the if-block around exit(). The test pinning the guard now asserts the one-liner the way the other suites do, instead of a regex for the old block. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CVrFykSreGPwV1hTiRdQBY