ENGINEERING NOTES / OCTOBER 2026
Math Quest Inspector
An inspection-first proof of concept for understanding a compiled HTML5 game and testing browser-scoped input.
01 / THE PROBLEM
Inspect the game before building an automation loop.
The inspector collects rendering, runtime, storage, network, and background-timing signals to discover a deterministic question/answer interface before resorting to OCR.
02 / THE SYSTEM
From input to a checked result.
InspectIdentify canvas, WebGL, runtime classes, and candidate question fields.
Compare modesMeasure visible and background timing behavior.
Verify inputUse browser-scoped pointer and keyboard events on a synthetic canvas.
Bound the experimentKeep shared scoring endpoints blocked by default.
Python · Playwright · Haxe/OpenFL inspection
03 / EVIDENCE & LIMITS
What has been demonstrated.
Records canvas/runtime signals and tests pointer and keyboard input on a synthetic canvas without controlling the desktop mouse.
The repository documents an inspection PoC. A live one-battle automation loop is a next milestone, not a completed feature. Tests use a synthetic canvas and do not validate gameplay success.