perf: speed up iOS simulator text entry

[thymikee]

Summary

Use XCTest's faster simulator text-entry path for multi-character iOS simulator fills, with fallback to standard XCUIElement.typeText when the private selector is unavailable.

Refs #1108.

Validation

pnpm build:xcuitest passes from a clean worktree and builds both iOS simulator and macOS runner targets. Live Bluesky/sample-app timing evidence is still needed before this should be marked ready.

Touched-file count: 4. Scope is limited to Apple runner text entry.

[github-actions]

Size Report

Metric	Base	Current	Diff
JS raw	1.5 MB	1.5 MB	0 B
JS gzip	491.8 kB	491.8 kB	0 B
npm tarball	597.4 kB	598.0 kB	+673 B
npm unpacked	2.1 MB	2.1 MB	+2.8 kB

Startup median (7 runs, lower is better):

Scenario	Base	Current	Diff
CLI --version	30.3 ms	30.1 ms	-0.1 ms
CLI --help	54.9 ms	55.8 ms	+0.8 ms

Top changed chunks: no changes in the largest emitted chunks.

[thymikee]

Closing this draft after live Bluesky verification from the #1108 worker.

The implementation builds, but it does not solve the motivating performance issue:

• baseline fill @e23 alpenglowxyz in Bluesky search: ~6.57s
• private synthesized XCTest text event: correct text but slower at ~16.9-17.0s
• simulator/host pasteboard + Command-V: correct only through repair, still ~10.7-11.0s
• in-runner pasteboard + Command-V: unreliable verification
• direct setValue(..., forKey: "value"): fell back to normal typing at ~6.40s

Since the proposed private selector path is slower than baseline, this should not move forward as a PR. The worker removed the failed probe code and left the #1108 worktree clean.

[github-actions]

PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-07-05 10:59 UTC