Provide reusable WordPress PHPUnit and bench recipe builders

[chubes4]

Problem

homeboy-extensions/wordpress manually assembles WP Codebox recipes for WordPress PHPUnit and bench runs in shell. It maps component mounts, dependency mounts, drop-ins, file mounts, WordPress versions, plugin entries, bench workloads, bootstrap files, blueprints, and shared-state mounts into wp-codebox/workspace-recipe/v1.

Some of that is Homeboy policy, but low-level WP Codebox recipe construction and mount normalization belong in WP Codebox. Keeping the recipe shape duplicated in shell makes Homeboy sensitive to WP Codebox contract drift.

Desired shape

Expose reusable recipe builder helpers or CLI commands for common WordPress plugin/theme workflows:

• PHPUnit recipe for a mounted WordPress plugin/theme component.
• Bench recipe for configured workloads, optional browser target metadata, dependency plugins, bootstrap files, and blueprint config.
• Component/dependency/drop-in/file-mount normalization with validation.

Homeboy should pass a component policy/settings payload and receive a validated WP Codebox recipe or run it through a stable WP Codebox command.

Acceptance criteria

• Add upstream recipe builder(s) or command(s) for WordPress PHPUnit and bench workflows.
• Builders support plugin/theme component paths, dependency plugin paths, db.php drop-ins, extra file mounts, WordPress version, multisite, wp-config defines, bench env, bootstrap files, workloads, and blueprint fragments.
• Builders validate path containment and unsafe mounts before returning/running a recipe.
• Builders return structured diagnostics for invalid settings.
• Homeboy can remove duplicated recipe construction from wordpress/scripts/test/test-runner-wp-codebox.sh and wordpress/scripts/bench/bench-runner-wp-codebox.sh while retaining Homeboy-specific sidecars and failure classification.
• Include smoke coverage for PHPUnit recipe generation and bench recipe generation with dependency mounts and a drop-in.

Related

• Audit source: Homeboy WordPress extension duplication audit.

AI assistance

• AI assistance: Yes
• Tool(s): OpenCode (openai/gpt-5.5)
• Used for: Drafted tracker from source audit; Chris remains responsible for prioritization and review.

[chubes4]

Opened partial upstream slice: #487

What it covers now:

• buildWordPressPhpunitRecipe() for the default WordPress PHPUnit recipe shape Homeboy currently assembles with jq.
• buildWordPressBenchRecipe() for the default WordPress bench recipe shape.
• normalizeRecipeMounts() so callers can share mount validation/defaulting instead of duplicating shell helpers.
• Smoke coverage validating generated recipes against the shared workspace recipe JSON schema.

Recommended remaining split:

1. Add a small CLI/subcommand or documented Node wrapper that reads a JSON options payload and emits one of these recipes. That lets Homeboy adopt the builders without becoming a TypeScript package consumer.
2. Update homeboy-extensions PHPUnit runner to replace the jq -n recipe assembly with the WP Codebox PHPUnit builder output.
3. Update homeboy-extensions bench runner to move scenario/manifest-specific shaping as needed, then emit the final recipe through the bench builder.
4. Add Homeboy regression tests around the exact emitted recipe payloads before deleting the old shell assembly helpers.