Role: product and premise critic.

Objective: Challenge the idea of copying the Steinberger workflow into Harness Kit.

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:
- Treat the post as inspiration, not a specification.
- Focus on Harness Kit as a cross-repo workflow substrate.
- Do not edit files.
- Do not propose an always-on hosted automation unless you also name privacy/security costs.

Output shape, max 500 words:
- Underlying user outcome in one sentence.
- 6 materially different product forms, with how each fails.
- Recommended form and why.
- Non-goals that prevent scope creep.
- One acceptance oracle that proves the workflow is useful without requiring live VNC in CI.
