JGengine verification

Verification follows risk: cheapest deterministic evidence first, visual/browser evidence only for claims pixels or interaction uniquely prove. The default rungs below work in any JGengine project (a created standalone game included); engine-repository commands live in their own section at the end.

Core ladder

1. Run the project's focused type/tests while iterating (bun run check-types, bun test src).
2. Assert pure rules and serialized transitions in tests.
3. Assert scene/environment data through summarizeEnvironment, voxel summaries, or authored-document queries.
4. Exercise gameplay progress when the loop can softlock.
5. Capture and inspect screenshots only for visual/layout/integration claims.
6. Record a short clip (drive --record, engine monorepo) when the claim is about behavior over time — collision, movement, camera feel, animation, a sequence of states — and a single frame cannot carry it.

A feature or change that alters runtime behavior is not done when its tests pass: try it. Drive the actual game (drive with keys/probes/record) and observe the new behavior happening before claiming completion — tests prove the rule, the drive proves the game.

Choose evidence

Classify each acceptance claim before scheduling proof. A plan that uses screenshots where deterministic evidence suffices is incomplete.