pj 3df8a3b3ba fix(sidecar): find the erased field by class, past the keyboard's own focus ...

The check that decides whether the select-all worked looked for an
"editable" attribute maestro's tree does not carry, so it answered
"cannot tell" every time and every erase paid the per-character
fallback. Worse, an open keyboard puts a second focused node in the
tree, one of the IME's own keys, carrying no text: taking the first
focused node would read a field still holding 4096 characters as empty,
which is the one answer that stops the erase early.

Match the text field by class instead. Measured against the real
backend, 4096 characters now clear in 385ms on API 34, 409ms on API 35
and 870ms on API 36, verified empty, where the fallback took ~4s.

2026-08-15 22:19:49 +05:30

..

src

fix(sidecar): find the erased field by class, past the keyboard's own focus

2026-08-15 22:19:49 +05:30

build.gradle.kts

experiment instrumentation: step budgets, arm labels, campaign runner (#72)

2026-08-12 22:20:31 +05:30