[chubes4]

Summary

• run WordPress Core workloads against the selected Core checkout through wordpress_directory
• replace local REST, database, and browser execution wrappers with canonical WP Codebox commands
• remove standalone browser rigs, duplicate materialization/lint machinery, helper-dependent contract tests, and Woo source-mutating preparation scripts
• retain product-owned fixtures, scenarios, assertions, and profiles

Why

The WordPress plugin and Core rigs contained local PHP, JSON, JavaScript, and shell implementations for behavior now owned by WP Codebox. Several manifests marked existing primitives as blocked, and Core workloads did not execute against the declared Core source.

This removes those parallel implementations and makes the rig packages declarative consumers of Codebox.

Upstream dependencies:

• Consolidate WordPress runtime inputs Automattic/wp-codebox#1865
• Delegate WordPress execution to WP Codebox Extra-Chill/homeboy-extensions#2294

How to test

1. Run node scripts/test-contracts.mjs --scope=wordpress-rigs.
2. Run homeboy rig lint WordPress/wordpress-develop --all.
3. Run homeboy rig lint WordPress/gutenberg --all.
4. Run homeboy rig lint Automattic/jetpack --all.
5. Run homeboy rig lint woocommerce/woocommerce --all.
6. With installed Studio/shared helper paths available, run node scripts/test-contracts.mjs to verify the complete repository suite.

Compatibility

This intentionally removes standalone browser rig IDs, local generic workload files, legacy wordpress.inventory-rest-routes usage, nonexistent Core fuzz commands, and source-mutating Woo preparation scripts. Consumers must use the consolidated full-surface profiles and canonical Codebox commands. No legacy aliases are retained.

AI assistance

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