[schlessera]

Refs #2

Depends on mwpd/basic-scaffold#177 landing: src/Infrastructure/, the architecture rules and their tests are that branch's asset capability at c72bf64, renamed to this plugin, so the infrastructure copy stays in sync with the scaffold. If the scaffold PR changes again before it merges, this PR follows.

What changed

The outdated post notice ships a default style. OutdatedPostNotice implements HasAssets and declares assets/css/notice.css at the front-end enqueue point when the queried post is outdated, so the stylesheet is in the head before the notice shows; a fresh post, an archive, a feed or an admin screen loads nothing. The look is the agreed one (soft amber box, dot marker, em sizing, forced-colors fallback), which the project website mirrors. Themes adjust it by overriding .mwpd-content-freshness-notice, or replace it by dequeuing the mwpd-content-freshness-notice handle. README, readme.txt, the docs and the changelog say so; the version is not bumped.

The first commit ports the scaffold's asset capability (HasAssets, Asset\*, InvalidAsset, the ServiceBasedPlugin orchestration, the PHPStan rule changes, the API snapshot and the infrastructure tests), without the scaffold's sample assets. The second adds the notice's style. The third resyncs the port with the reviewed scaffold branch (get_asset_location() and get_debug_mode() template methods instead of injector delegations, the re-entrancy guard, AssetHandle, normalized script registrations, the prefix rule's dynamic receivers) and overrides get_debug_mode() in the composition root so the asset boundary checks the same DebugMode the services are bound to.

Why this shape

The predicate runs in the head, so it asks MainLoop::queried_post() and the FreshnessPolicy rather than is_rendering_queried_post(), which needs the loop. The service does not catch its own failure in get_assets(): the plugin's enqueue listener is the boundary there, as the service's own filter callback is for the_content, so the behaviour is the same (loud with WP_DEBUG, no style without it) and the service does not decide twice. The composition root returns the bound DebugMode from get_debug_mode(), so rebinding it once, through the bindings filter or in the root, covers the notice and the plugin's asset loading alike; the integration tests rely on that to exercise both modes.

Proof

composer test              # OK (781 tests, 3994 assertions)
composer lint              # phpcs, PHPStan, Psalm: no errors; 139 rule tests OK
composer check:autoloader  # Bundled autoloader loaded all 108 source declarations.
composer api:snapshot      # regenerated; only additions

Run in a php:8.3-cli container. The end-to-end tests ran in CI on the previous head and passed; tests/e2e/run.sh now also expects the stylesheet link on the old post, and the existing "no notice" checks cover its absence elsewhere, since the handle contains the class name.

Checklist

• composer test and composer lint pass locally; npm run e2e is left to CI.
• Every acceptance criterion from the issue is met, or the gap is named below.
• src/Infrastructure/ changed: the API snapshot is regenerated, and the change is the scaffold's own (Add scripts and styles as a capability the plugin orchestrates basic-scaffold#177).
• Docs and inline comments reflect the change.

Anything left open

• Add scripts and styles as a capability the plugin orchestrates basic-scaffold#177 has not merged. Once it does, the infrastructure copy is compared against the merged state and the AGENTS.md note is updated to the merged commit.
• Styling the notice inside the block editor is out of scope, as on the issue.