pr-review-gatelisted

# Pre-PR Review Gate No PR is opened until FOUR review passes have run on the full branch diff and their findings are resolved. Run them unasked — a review the user has to request is a process failure, and by the time they ask, findings are usually too large to fix in the same PR. The passes are independent: run them in parallel as subagents. 1. **Design / SOLID review** — the Uncle Bob (Robert C. Martin) lens: type-level single responsibility, ownership, state lifetimes, dependency direction, the `design-principles.md` thresholds, and the full design review lens (load the `design-review-lens` skill for the complete checklist: SOLID, Clean Architecture boundaries, GRASP, Clean Code hygiene, coupling laws). Explicit verdict on whether any type accumulated responsibilities over the branch. 2. **Standard code review** — correctness, project conventions, error handling, test coverage (use the code-reviewer agent where available). 3. **Security review** — adversarial pass over the diff: secrets/credentials in code or history, injection, unsafe file/archive/network handling (zip-slip, path traversal), authn/authz gaps, supply chain (dependency pins, mutable refs), sensitive data in logs, and location/EXIF metadata in committed media. 4. **Concurrency review** — a dedicated pass, because concurrency bugs are the class most frequently introduced during development and least visible in a general review: shared mutable state across threads / isolation