docs(interaction): state that click and press report dispatch, not landing

[thymikee]

Summary

States the click/press success contract: success means the tap was dispatched, not that it landed on the element. help click, help press, and the commands guide now say this and name --verify (changedFromBefore), --settle, and wait <selector> as the ways to confirm it landed. No runtime behavior changes.

Both tap-outcome waivers in interaction-guarantees.ts (TAP_OUTCOME_NOT_OBSERVED_GAP, DIRECT_IOS_OUTCOME_NOT_OBSERVED_GAP) now point their trackingIssue at #3335 instead of the closed #1081 umbrella.

I put the help text in the click/press descriptions rather than the workflow card, because that card is already at its 9,100-byte budget.

Refs #3335. That issue stays open to track the waived outcomeObservation cell. The stale tap point found in the same evidence is #3354.

3 files touched.

Validation

• pnpm check:affected --run passed on 90d8fb035 (2298 tests, plus command-doc coverage) and again on 4539b1d48 after review fixes to the wording.
• No device run, because nothing changed at runtime: the diff is help text, docs, and a tracking-issue URL.

🤖 Generated with Claude Code

[github-actions]

PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-10-10 06:01 UTC

[github-actions]

Size Report

Metric	Base	Current	Diff
Installed (including dependencies)	5.15 MB	5.15 MB	+230 B
Package (unpacked)	5.15 MB	5.15 MB	+230 B
Package (download)	1.55 MB	1.55 MB	+40 B

Startup median (7 runs, lower is better):

Scenario	Base	Current	Diff
CLI --version	20.9 ms	18.9 ms	-2.0 ms
CLI --help	58.5 ms	53.7 ms	-4.8 ms

[cubic-dev-ai]

All reported issues were addressed across 3 files

<sub>Reply with feedback, questions, or to request a fix.

View guided diff | Turn on auto-fix | Re-trigger cubic</sub>

[thymikee]

This PR is ready at 4539b1d. The change is small and the code looks right.

Not blocking: the new paragraph in website/docs/docs/commands.md (https://github.com/callstack/agent-device/blob/4539b1d/website/docs/docs/commands.md#L467) names --verify and --settle but not the per-command flag names on press, and it sits among the fill/type notes rather than next to the click/press examples, so you can move it or leave it.

The iOS smoke job failed with daemon_startup_failed after a 15s startup timeout. This diff only changes a tracking-issue URL constant, two help strings and one docs paragraph, so it does not touch daemon startup, and the failure looks unrelated. I judged that from the diff and the log excerpt and did not rerun the job. I also did not check that the macOS native backend acts through accessibility actions, or whether any test or snapshot pins the click/press description strings. There are no conflicts. Please rerun the Smoke Tests job before merge.