commit 4965f76 · ran as gui · 55s · ~20k tokens · evidence sealed & signed (manifest.json)
11/30▼ was 15/30
The game window opened and rendered a grid with a food square and what should be a snake head, but live interaction testing showed the snake did not respond to arrow keys and the food square moved unexpectedly on its own — meaning the core gameplay loop is not functioning as claimed. The source code follows a known tutorial structure but has suspicious patterns (class-level mutable defaults for body/turns) that likely explain the broken movement. No automated tests exist to validate behavior. Overall this is a partially-running tech demo rather than a working game, and the README's central claim (playable classic snake) was not verified by observed behavior.
Strengths
- The pygame window launched successfully with no crash, and a grid, a red 'food' square, and a green square were rendered on screen.
- The code shows a reasonable object-oriented structure (cube/snake classes) with separated draw/move logic, matching a recognizable tutorial pattern.
- requirements.txt and dependencies were minimal and installed cleanly without conflict.
Concerns
- Live probing showed the snake (green square) did not move at all in response to arrow key presses, directly contradicting the core README claim of a playable snake game.
- The red food square moved on its own without the snake reaching it, suggesting broken collision/spawn logic or a rendering artifact rather than intended gameplay.
- No test suite exists in the repo and none was observed running, so codeQuality must be judged conservatively from the raw source excerpt alone.
- The snake.py file uses mutable class-level attributes (body = [], turns = {} at the class level rather than instance level), a classic bug pattern that could easily explain the frozen/erratic behavior observed live.
- The README contains unrelated promotional content ('Launch Your Software Development Career Today', bootcamp advertisement) which has no bearing on the code but adds noise irrelevant to grading; noted only as clutter, not as an integrity issue.
The submission's own tests
No test command found.
Security sweep
audit: n/a · secrets: no matches
README claims, checked by driving the app
- ❌ failed — Pressing arrow keys moves the green snake head around the grid (The green square remains in the same grid position; only the red food item moved slightly, so the snake did not shift.)
- ❌ failed — The red food/apple square is stationary until eaten by the snake (The red square moved from around column 655 to 755 without the snake head visibly reaching it, indicating unexpected relocation.)
Ask the candidate
- Your snake and cube classes define body and turns as class-level attributes rather than instance attributes in __init__ — can you explain why that's risky and whether it explains the frozen snake behavior we observed?
- During live testing, the snake didn't move on arrow key presses. Walk us through your move() method's event loop and identify why input might not be registering.
- The food square appeared to relocate without being eaten — how does your game currently detect collision between the snake head and food, and what would you change to make food spawning deterministic and testable?
What the cloud browser saw
Session recording
A server-side video of the entire desktop session, including every claim the reviewer drove. Disputes end here.
Generated by Gauntlet — sandboxes & cloud browsers by Solari, judgment by Claude. Verify this evidence: npm run verify -- <this directory>