dev-workflow — Acceptance-Gated Development Loop

dev-workflow drives a feature or bugfix end-to-end: read (or bootstrap) a
local ISSUE markdown with acceptance criteria, explore the codebase, converge
on a design, run an engineering review (architecture impact + failure modes +
test matrix), implement with TDD, review in a fixed order (spec → quality →
security), capture screenshot evidence via the official Playwright CLI, then
pass a 3-round acceptance gate before a conventional Git commit.

The core rule: the verifier is never the implementer. Every judgment call —
evidence audit, convention review — runs in a fresh subagent with no stake in
the code. That is how wrong-region screenshots and self-graded "done" claims
get caught.

Tool-agnostic: no issue tracker, no CI vendor lock-in. Framework-aware via
profiles (Laravel shipped; other stacks degrade gracefully to whatever
linters the project already configures).

Three checkpoints only (kickoff / plan / wrap-up), seven hard gates that never
degrade. Ships a BLOCKED report with root-cause analysis when it can't clear
in 3 rounds instead of faking a pass.