TOC Genius: moving from tocgenius to toc-genius (0.4.5)

WordPress.org assigned the Free package slug toc-genius. Its main file remains
tocgenius.php, so the new plugin identity is toc-genius/tocgenius.php. Author URI
remains https://plugins.shop/. Pro stays tocgenius-pro/tocgenius-pro.php and now
requires this canonical Free 0.4.5 or later. This is not an automatic folder rename.

Preserved data and content
The tocgenius_settings and tocgenius_pro options, all related Pro drafts/history,
_tocgenius_profile article metadata, saved heading IDs, [tocgenius] shortcode,
tocgenius/table-of-contents block, hooks and REST metadata identifiers are retained.
No migration routine rewrites or deletes stored data. Translation files now use
the toc-genius domain. No external service or API is introduced.

Safe migration
1. Back up plugin files and the database; rehearse on staging. Pro configuration
   export is an additional copy, not a complete article/database backup.
2. In the OLD Free plugin, turn Delete plugin data on uninstall OFF. Save, reload,
   and verify it is off. On multisite verify this for every site, including sites
   where the plugin is not currently active: the old uninstaller visits all sites.
3. Deactivate Pro, then deactivate the old Free plugin. Do not delete/uninstall.
4. Upload the new toc-genius ZIP and activate TOC Genius. Update the existing Pro
   add-on to matching 1.1.2, then activate it. Free-only sites omit the Pro steps.
5. Verify saved settings, article labels/exclusions, a manual block/shortcode,
   and any Pro rules, designs, navigation, history and exports.
6. Remove only the inactive old wp-content/plugins/tocgenius folder over SFTP or
   your hosting file manager without invoking its uninstaller. Alternatively use
   WordPress Delete only after confirming cleanup remains OFF on every site.
   Keep the new wp-content/plugins/toc-genius folder and your backup.

Safeguards and limits
The new package refuses activation while the old package is active or loaded.
If both are already marked active, only the legacy Free runtime loads; an admin
notice explains how to finish migration. No activation state or cleanup preference
is silently changed. The active new package blocks reactivating the old package
through normal Plugins-screen single/bulk activation and activation error replays.
WordPress 6.9+ also supplies a pre-inclusion validation filter used for this block.
WordPress 6.5-6.8 direct programmatic/WP-CLI activation of the OLD package is not
protected: use the documented Plugins-screen workflow, not a bypass.

While the new package is loaded, it pauses old-package uninstall if any site's
cleanup is enabled. The immutable old uninstaller cannot be protected when the
new package is inactive, skipped, or not loaded in that site's request. Always
verify cleanup OFF before old-package removal; do not rely only on this safeguard.
Removing the new package preserves shared data for sites with the old package
still active. Normal final uninstall otherwise retains the existing opt-in rules.

Recovery
If installation fails, keep both packages inactive until selecting one Free
runtime. Restore the previous matched Free/Pro files from backup and activate only
that pair. Do not restore an old database over newer editorial/customer work.
Existing toc-genius users update by replacing Free first, then matching Pro;
there is no need to uninstall or repeat the folder migration.
