game-qalisted

# Verify a game or asset integration Read [shared context](../../references/shared-context.md), project preferences and the task's actual changed files. Use the scope and selected review policy to choose checks. For read-only reviews, report missing preferences without making unrelated changes. ## Separate the evidence - Structural checks: files, imports, paths, resource metadata, sprite layout, rig/clip presence and asset hashes. - Functional checks: actual gameplay state, input, collisions, action/recovery behavior, progression and save/load. - Visual checks: real renderer output, continuous animation and comparison with the approved references at matched camera and size. - Performance checks: real-time profiling at the target workload, performed through game-optimization. A passing structural test cannot establish attractive anatomy or fluid animation. A fixed-fps movie cannot establish runtime frame rate. A short desktop profile cannot establish iPhone thermal or memory behavior. ## Test the meaningful paths Use isolated save slots or a temporary project copy. Import the final asset, not a fixture or earlier revision. Record the asset/source hashes that were actually tested. Read errors from the current run separately from historical editor logs. Exercise the complete scoped loop and its failure/recovery path. Check continuous traversal across boundaries, repeated actions, pause/resume, focus loss, and the configured input methods. Test actual global overlays and