# Unity-native acceptance — currently OPEN Record the exact editor, Input System, platform, OS and Console output. These checks are instructions, not evidence that Forge has run the editor. 1. Import into an empty licensed 2D project; no red Console errors. Create the scene with the Forge menu; five walls, player, three coins and patrol exist. 2. Enter Play Mode. Arrows and WASD move at the same cardinal speed. Diagonals are not faster; release stops motion. Click Game view if it lacks focus. 3. Hold against every wall/divider; the player must not pass through. Test at multiple frame rates; physics uses fixed steps, not transform translation. 4. Collect a coin, leave/re-enter; score increments once. Collect (-5,3), then (5,3), then (5,-3) by travelling above the divider. Win freezes the round. 5. Restart. Walk into the red patrol between x=-1 and x=3 at y=-2. Lose freezes score/timer. Patrol cannot give a later loss after a win. Restart again. 6. Wait without collecting: timer reaches zero, loss occurs, no negative timer. 7. Press P: movement, patrol, idle animation, score and clock stay frozen. Press P again: resume. Losing focus pauses; returning requires P to resume. 8. Test held keys while changing focus; return without an unintended movement. Disable/re-enable the controller and check input/physics cleanup. 9. Use R and HUD Restart after play, pause, win and loss; coins, patrol, spawn, score and timer reset. Repeat ten times; no duplicate callbacks/extra sprites. 10. Resize Game view; the full room stays visible. Confirm actual included art is the five idle frames, not claimed walk/run animation. Capture permitted editor/game images only after checking what they actually show. 11. Build the desktop profile into a separate folder; run outside the editor. Repeat steps 2–10. Check the active profile scene list and installed module. 12. Independently run an AI build/debug/upgrade prompt against your permitted project; record actual output/files/test results. Clipboard is not AI proof. Web/mobile/touch/accessibility/GPU/performance and BINX.fun embedding need their own checks. None is inferred from the console-rule report or this checklist.