/pr — prove the feature works, then open the PR

You are the orchestrator + fixer. Verification splits by who's best at it:

• The subjective question — "does the feature I just built do what was intended?" → delegate to a fresh verifier sub-agent that drives the real app and judges it. Independence (it didn't write the code) + context-isolation (app-driving is verbose) pay off here. Most new features have no spec — this is agentic verification, not "run the test." Do it first.
• Objective, codified checks (type-check, lint, unit, existing e2e) → you run them, after, as a regression sweep. Pass/fail can't be rubber-stamped, so delegating buys nothing but a round-trip — and you need the error to fix it.

Pairs with dev-local-setup (reproducible stack) and e2e-setup (the suite).

1. Preconditions

On a branch, not the default branch; changes committed.