v2.8.3

Fixed

input_text now resolves the cases where the screen offered no real choice. Three shapes, all of which previously refused to type into a field the caller could not have meant anything else by:

• A sole mounted input with nothing focused now resolves. The refusal to guess exists to stop text landing in the wrong field, and a wrong field needs a second candidate to exist.
• Two matches that describe identically (a screen kept mounted under its own re-push, as React Navigation does) take the later, visible one instead of asking the caller to pick between two lines of the same text.
• A targeted miss re-resolves once after 500ms. The field is often a screen transition away from mounting, and the fiber tree still holds the screen being navigated away from.

Telemetry

• New bad_target error category: an agent naming a target the screen does not uniquely offer no longer shares a failure rate with real faults like a device disconnect.
• The platform stamp now follows the tool's own device argument (or an ios_/android_ tool name) instead of whichever app landed in the connection map first, so platform breakdowns are correct in multi-device sessions.