Anti-template review step

Imported from GitHub issue El-SaMa/tekori#13 by @El-SaMa.

---

Goal

After the build, a reviewer judges whether the page could be any business's site, and the build gets one chance to fix it.

Tasks

• Rubric in a new skill packages/agents/skills/review.md: 1) Would this first screen work for a competitor by swapping the logo? 2) Is the concept visible within the first screen and at 50 %? 3) Does every checklist item appear? 4) Is the main action reachable on the phone's first screen? 5) Is the still version readable? 6) One signature moment that only this brand would have? Score 0-10 with reasons.
• Reviewer step (role reviewer) after the builder in bold and experimental modes (optional in safe), using look contact sheets (#12).
• Below the threshold (start at 6/10): one redo round for the first screen and the weakest signature moment, within the job's step budget; never more than one.
• Store template_score and the reviewer's reasons (#15).
• Guard against gaming: the reviewer sees screenshots, not the builder's own summary.

Acceptance criteria

• Tests for the step wiring and threshold logic with a fake model.
• Cost cap respected (the redo cannot push a job over its budget).

Depends on

#1, #11, #12.

---

Plan key T13. Epic: El-SaMa/tekori#19.