Dogfood reviewed apply-back through a parent control plane

[chubes4]

Goal

Prove the end-to-end reviewed apply-back flow from a real parent control plane without coupling wp-codebox core to Homeboy Extensions.

Boundary

wp-codebox owns:

• sandbox task execution
• artifact validation
• apply-approved-artifact
• audit records
• canonical artifact/review/apply payload contracts

Homeboy Extensions / DMC / site-specific agent kits consume those contracts externally.

Target Flow

1. Parent-site chat/control plane calls wp-codebox/run-agent-task.
2. User reviews files/review.json and approves explicit approved_files[].
3. Parent control plane calls wp-codebox/apply-approved-artifact or retrieves the verified artifact payload.
4. Homeboy/DMC-backed consumer applies the exact approved patch.diff to a safe worktree/branch.
5. Consumer commits, pushes, and opens a bot-authored PR.
6. Parent site stores/links audit result metadata: adapter id, PR URL, branch, commit, artifact id, digest, approver.

Acceptance

• wp-codebox does not call Homeboy directly.
• The Homeboy/DMC side consumes wp-codebox artifacts/contracts.
• A real fixture or dogfood site demonstrates owner approval to bot-authored PR.
• Reviewer-facing evidence links are not local-only paths.