Consolidate WordPress runtime inputs

[chubes4]

Summary

• add canonical wordpress_directory runtime input for mounted WordPress Core checkouts
• keep Core sources separate from plugin extra_plugins
• standardize REST inventory on wordpress.rest-route-inventory
• reject legacy camelCase extraPlugins recipe input

Why

Homeboy WordPress Core rigs were projecting wordpress-develop through the plugin mount path, so runtime discovery and fuzz workloads booted stock WordPress instead of the selected Core checkout. Downstream callers also carried two REST inventory command names and multiple plugin-input spellings.

This makes WP Codebox the single owner of the canonical Core/plugin runtime boundary.

How to test

1. Run npm install from a fresh checkout.
2. Run npm run build.
3. Run npm exec -- tsx tests/public-fuzz-workload-cli.test.ts.
4. Run npm exec -- tsx tests/wordpress-runtime-discovery-contracts.test.ts.
5. Run npm exec -- tsx tests/agent-task-contracts.test.ts.
6. Run npm exec -- tsx tests/playground-cli-runner-bootstrap-ini.test.ts.
7. Run php scripts/php-fuzz-suite-runner-smoke.php.

Compatibility

This intentionally removes legacy support for wordpress.inventory-rest-routes and camelCase extraPlugins. Callers must use wordpress.rest-route-inventory and extra_plugins. This is a deliberate breaking contract cleanup; downstream Homeboy Extensions and Homeboy Rigs PRs migrate together.

AI assistance

• AI assistance: Yes
• Tool(s): OpenAI gpt-5.6-sol via OpenCode
• Used for: Cross-repository contract analysis, implementation, tests, and PR preparation under Chris Huber's direction.