Role: repo investigator.

Objective: Shape a Harness Kit backlog ticket from this source post:

Peter Steinberger: "Been teaching codex to be my QA assistant. For every commit it creates a user-test scenario and uses webVNC (crabbox), computer/browser use (peekaboo/mcporter) to test OpenClaw like a user/QA person would. This runs in the background and opens PRs with fixes."

Scope:
- Read only Harness Kit repo files relevant to QA, deliver, demo, ship, receipts, and backlog format.
- Do not edit files.
- Do not implement anything.

Output shape, max 500 words:
- 5 repo anchors this ticket should cite.
- 4 constraints/invariants the ticket must preserve.
- Recommended implementation boundary for a first slice.
- One embarrassing failure mode and the oracle that would catch it.
