Frontend Review

Review the rendered product, not just the component source. Keep this lane independent from Standards and Spec review so visual and interaction failures cannot be masked by clean code or nominal requirement coverage.

Establish the review surface

Pin the fixed point and list changed frontend routes and components. Locate the governing docs/design/<feature>/DESIGN.md, if any, and read its evidence and acceptance criteria. A missing contract is not automatically a defect when the change did not require a visual decision; state which visual source of truth, if any, was available.

Detect and report capabilities before testing:

• Runnable local application
• Browser automation and screenshot capture
• Supported viewport or device emulation
• Automated accessibility scanner
• Keyboard and screen-reader inspection
• Visual-regression baseline

Never translate a missing capability into a pass. Mark the affected checks Unverified and explain the exact limitation.