Design review

A written critique of rendered UI. It does not fix the design or rewrite copy. Criteria are in references/review-criteria.md, and finding the design, evidence and probes in references/sources.md.

Start from whatever the ask gives

"Check this screen before I ship" is enough. Defaults:

• The design: a scope the caller names, else the branch's changed screens, else top routes (references/sources.md).
• The purpose: inferred and marked assumed at the top of the record.
• Viewports: the widths of supplied images, else the narrowest and widest the app supports, default 390 and 1280 px. "On mobile" or a named device class means the phone width only (references/sources.md).

When a coordinator calls it

Take the captures, criteria and purpose as given and run to the end, recording any gap the solo path would ask about. With captures only, the scan and probes read not run: captures only, which counts as a reason. Start the report with a status line, Status: complete (Blocking n, Should fix n, Note n), Status: complete (partial: <what was not reviewed>) or Status: stopped: <condition>, then Commit: none, then the answer and ship lines. Return the report, or the stop shape, as text and write no report file.

Steps