[chubes4]

Part of #3649. This is the last step to a fully green smoke suite.

Once #3676–#3681 were merged together, 2 smokes failed on main (63bbf5a). Each one had passed on its own branch.

• flow-formatter-loaded-settings-display: test: add missing WordPress stubs to shared smoke-wp-stubs #3677 added a filter-registry apply_filters() to the shared smoke-wp-stubs.php. That stopped this smoke's own function_exists-guarded apply_filters() override from ever being defined. The smoke now registers its step types and handler settings with add_filter() against the shared registry.
• runtime-vocabulary: test: repair email, queue, retention and docs contract smokes #3680 and test: make host-dependent smokes hermetic and resolve toolchain from Homeboy #3681 added HOMEBOY_WORDPRESS_CORE_ROOT / HOMEBOY_EXTENSION_PATH toolchain lookups to email-multi-inbox-forward and cli-global-options. That is the same test-harness use for which phpunit-file-isolation is already allowlisted, so both files join that allowlist. This check was already failing on main before test: derive bootstrap/runtime contract smokes from current service composition #3679 repaired it, so neither branch's gate saw the new mentions.

Verification

On main with this patch and the CI environment (HOMEBOY_EXTENSION_PATH, HOMEBOY_WORDPRESS_CORE_ROOT): 0 of 371 smokes fail. Both audits pass. phpcs counts in both changed files equal main's.

---

AI disclosure: Claude found and fixed these interaction failures directly, outside Homeboy, while integrating the #3649 repair PRs at Chris's direction.

Update: CI-only fixes (commit 1a80fa8)

CI turned up two more failures that only reproduce on the GitHub runner:

• runtime-vocabulary was scanning untracked runner output (.homeboy-bin/homeboy, homeboy-test-*.json). It now skips untracked files outside vendor/. Tracked violations still fail; I checked with a probe file.
• composable-caller-containment: on the runner, the dead compose process is reparented to a subreaper that never reaps it, and posix_kill( $pid, 0 ) still succeeds on a zombie. The probe now reads /proc/<pid>/stat and treats Z/X as exited. I reproduced the failure locally under a non-reaping PR_SET_CHILD_SUBREAPER parent; with the fix it passes there, and it still fails when the monitor is disabled.

Shard 1 and shard 4 are green now. What's still failing predates this work and is tracked in #3683 (job-artifact-hashable on PHP 8.2, plus 1 unnamed PHPUnit test that was already failing on #3669/#3681).