Developers

Read this page as markdown — for coding agents, or for anyone who prefers the source.

QA checklist

Internal review pass, run after automated checks have passed. Every box is verified by hand; automation covers the mechanical rules, not these.

Reviewer records outcome as approved or rejected with reasons. Vague rejections are not acceptable — the developer must know exactly what to fix.


Setup

Functional

Devices

Real hardware, not emulation.

Sizing

The failure mode here is silent: the game looks fine until it is given less room than it assumed, and then loses whatever it draws near an edge.

Performance

Network isolation

Sandbox compliance

Audio

Accessibility

Content

Catalogue readiness


Outcome

Game:     <id> v<version>
    Reviewer: <name>
    Date:     <date>
    Result:   approved | rejected

    Blocking issues:
      1. ...

    Non-blocking notes:
      1. ...