[ahegyes]

Every hook the framework fired for a plugin took its first level from the storage prefix, or from an id or option name the plugin passed, so a plugin's hooks changed whenever it renamed its stored keys, and the bootstrap updater's filter named the framework's vendor. A plugin also handed the framework its entry file, slug and prefix as loose strings, which a consumer could swap without a type error, and the names the framework stored were arguments that only convention kept under the prefix. Each plugin carried its own copy of the registrars for its wp-scripts build, and the reference fixtures declared their option names, migration steps, footprint, safeguards and boot callbacks as globals that any code could call.

Changes

• Core's PluginIdentity holds a plugin's entry file, slug and prefix, derives its hook root and refuses a prefix outside the storage pattern. Every framework class that needed one of those strings takes it instead: PluginBoot, AdminNotices, MigrationRunner, Assets, Scheduler, both loggers, CapabilityGrants, Lock, both caches, WooCommerceRequirement::check(), Uninstaller::run(), OptionsPage, ObjectForm and ProductDataTab. The composition root builds it once and defines it in the container.
• Every hook fires under the slug with underscores for its dashes; the three surfaces pass their id as the filters' last argument. AdminNotices registers its routes under {slug}/v1, and the updater filters {text_domain}/github_updater/config. The framework derives the names it stores from the prefix: the runner's {prefix}_revision, the grants' {prefix}_capabilities, a lock's {prefix}_{name} and a region under the prefix for each cache; every log channel is the slug.
• Core's Asset\Assets registers a plugin's built scripts and styles from the .asset.php wp-scripts writes, a style-{entry}.css chunk from its entry's, with translations under the slug and the RTL variant; a file wp-scripts did not build is versioned by its modification time as a best effort.
• consumer-a, consumer-b and the personas keep only contract in the global namespace: functions.php declares the @api accessor and registers its hooks as static closures, and option names, defaults and readers, migration steps and the footprint live in final classes. A component that builds a surface takes the identity by constructor. consumer-a's safeguard is a final Safeguards.php at the plugin root, parsed on PHP 7.4, and its entry wraps everything after it in one try. Conventions 2, 3, 5, 6 and 8 and the README excerpts follow.
• The WooCommerce floor is 11.3, and the Composer and npm locks are refreshed.
• The integration tests log the current user out after every row, which fixes an order-dependent failure.

Testing

composer quality-check (validation, PHPCS, PHPStan, Unit and Integration), the multisite and without-woocommerce groups, the Php74 suite, the end-to-end spec, ESLint, both audits, actionlint and zizmor, and the PHP 7.4 parse of consumer-a's by-path files and the bootstrap package, all passing locally.