desktop_wait matches an element past the 200-element cap but returns no snapshot to act on it #232

Seen 2026-11-01 with Desktop Tools 0.18.0 on macOS 26.5, Chrome 156, driving the Google Cloud console and Google Calendar in the background from Claude Code.

Observed: on Cloud console forms (Create service account, Policy details), the fields fall outside an inspect's first 200 elements. desktop_wait with element_appears then matched (for example {role: AXTextField, title: "Service account name"}), but returned inspection.snapshot_id: null with "The element is not among this inspection's elements". So the agent had to guess which container to scope into, or fall back to pixel inspects and point clicks.

Related to #178, which is about the budget being spent on offscreen elements.

Expected: when desktop_wait matches an element, it returns a snapshot that contains it. For example, a scoped snapshot rooted at the match's nearest container.

Also seen: desktop_insert with route: type into that "Service account name" field returned INSERTION_UNVERIFIED, although the screenshot showed the text typed correctly. That's the same family as #203.