You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit b9b410a
Browse filesBrowse the repository at this point in the historyBrowse files
feat(interaction): report readiness wait on a successful press, click, or longpress (#3081)
* feat(interaction): report the readiness wait on a successful press, click, or longpress
A step that waited for its target and then acted now returns data.readiness
with polls and waitedMs, present only when more than one capture was needed.
The runtime selector poll reports the wait on the resolved target, the shared
interaction response builder attaches it without touching the warning, and a
replay step's pre-dispatch gate hands its own wait to the dispatch through
internal.replayReadinessWait so one step reports one combined readiness.
Tests and the mutation that fails each:
- press-target-readiness.test.ts "third poll" (provider scenario, polls 3):
resolution.ts drops `readiness = ready.readiness`.
- press-target-readiness.test.ts "first capture hits" and
selector-readiness.test.ts "first capture ... no readiness": the
`observed.polls.length > 1` guard becomes `> 0`.
- selector-readiness.test.ts "polls until the target appears": same drop as
the third-poll scenario.
- interaction-touch-response.test.ts carried-wait cases: the builder stops
combining `params.carriedReadiness`; the first case also pins the prior
warning staying composed.
- session-replay-target-verification-runtime.test.ts gate cases: the adapter
stops passing gateWait to applyReplayReadinessWait; or the gate records a
wait at `polls > 0`.
* docs: document data.readiness on a press that had to wait
* refactor(replay): drop the carried gate wait; replay evidence stays the readiness diagnostic
* test(interaction): pin data.readiness on the client and MCP success paths
The wait is capped at 2 seconds and covers only a target that has not appeared. When the target is still missing after the wait, the error carries `error.details.readiness` with `waitedMs`, `polls`, and `end` (`expired` or `stalled`). A capture that shows an empty accessibility tree ends the wait at once with `capture_sparse` and `readiness.end: sparse`. A covered, off-screen, or ambiguous target fails at once, and a screen that stays unreadable for the whole wait fails with its own error; neither carries `readiness`. `readinessTimeoutMs` is not an MCP tool argument and has no CLI flag.
300
+
The wait is capped at 2 seconds and covers only a target that has not appeared. When the target is still missing after the wait, the error carries `error.details.readiness` with `waitedMs`, `polls`, and `end` (`expired` or `stalled`). A capture that shows an empty accessibility tree ends the wait at once with `capture_sparse` and `readiness.end: sparse`. When the command had to wait and then succeeded, the result carries `data.readiness` with `polls` and `waitedMs`. A command that found its target on the first look has no `readiness` field. A covered, off-screen, or ambiguous target fails at once, and a screen that stays unreadable for the whole wait fails with its own error; neither carries `readiness`. `readinessTimeoutMs` is not an MCP tool argument and has no CLI flag.
301
301
302
302
Vega OS client support is currently VVD-only and covers device discovery, app open/close, `back`, `home`, and `tvRemote`. Physical Fire TV, capture, selector, install, logging, and performance methods report unsupported for Vega targets.
0 commit comments