perf(harmonyos): memoize gesture viewport dumps

[thymikee]

Summary

HarmonyOS coordinate gestures now reuse one device-scoped ArkUI viewport for up to two seconds instead of paying a full layout dump for every adjacent gesture. Foreground-changing actions invalidate the memo, and keyboard dismiss delegates Back through the same invalidating owner as normal navigation.

The previous diagnostics and Apple changes were removed from this PR and preserved as separate ownership slices. This PR changes 7 files and stays within the HarmonyOS interaction family.

Validation

A planted 20-second TTL made the new exact-expiry regression return the stale portrait viewport after two seconds. Before the production fix, the real interactor keyboard-dismiss route emitted Back but did not invalidate the memo. Both regressions are green on c604df249e.

The affected gate passed all runnable checks, including 247 test files / 1,550 tests, format, lint, typecheck, layering, Fallow, build, and provider integration. No HarmonyOS hardware is provisioned locally or in CI; residual live risk is limited to physical rotation or multi-window geometry changes within the two-second TTL.

[thymikee]

Reviewed current head 6fba42957: not ready. src/utils/diagnostics.ts adds a process-global, never-cleared ensuredDiagnosticDirs set. A long-lived daemon retains every distinct debug/trace directory forever; worse, if a previously seen directory is removed, later scopes skip mkdirSync, the append fails, and emitDiagnostic swallows it—silently losing diagnostics. Keep this state request/scope-local (or remove the cache) and add a two-scope delete/recreate regression. The branch is also DIRTY/conflicting against current main, and only CodeQL ran on this head, so rebase and rerun full CI. HarmonyOS hardware remains an explicit residual evidence gap.

[thymikee]

Rebased onto current main and reconciled with #2050's package-owned Apple runner. The diagnostics directory memo is now scope-owned, including a delete/recreate regression; the stale-bundle test now lives under packages/platform-apple. Full local affected gate passed on 9a58fc4.

[github-actions]

Size Report

Metric	Base	Current	Diff
JS raw	2.45 MB	2.45 MB	+533 B
JS gzip	821.1 kB	821.4 kB	+217 B
npm tarball	943.9 kB	944.2 kB	+267 B
npm unpacked	3.28 MB	3.28 MB	+533 B

npm unpacked components

Component	Base	Current	Diff
JS / dist source	2.61 MB	2.61 MB	+533 B
Apple runner source/project	570.8 kB	570.8 kB	0 B
macOS helper source	54.8 kB	54.8 kB	0 B
Android helper artifacts	0 B	0 B	0 B
Other package files	45.3 kB	45.3 kB	0 B

Startup median (7 runs, lower is better):

Scenario	Base	Current	Diff
CLI --version	34.8 ms	34.8 ms	+0.1 ms
CLI --help	93.5 ms	90.0 ms	-3.5 ms

Top changed chunks:

Chunk	Raw diff	Gzip diff
dist/src/runner-client.js	+25 B	-6 B

Top changed packed files

Packed file	Base	Current	Diff
dist/src/app-lifecycle2.js	2.8 kB	5.3 kB	+2.5 kB
dist/src/harmonyos.js	6.6 kB	4.4 kB	-2.2 kB
dist/src/sdk-android-adb.js	21.7 kB	22.0 kB	+263 B
dist/src/apps.js	22.8 kB	22.8 kB	-32 B
dist/src/runner-client.js	85.9 kB	85.9 kB	+25 B
dist/src/simulator.js	3.2 kB	3.2 kB	-7 B

[thymikee]

Two P2 readiness blockers remain:

1. Add planted-red TTL-expiry coverage for the Harmony viewport cache. The new tests prove reuse, explicit invalidation, and device scoping, but never cross the configured 2,000ms TTL. A wrong or non-expiring TTL would stay green. Use a fake clock/timer to cache a viewport, cross 2s without an invalidation hook, and prove the next lookup performs a fresh dump.

2. Split this four-family leftovers batch into independently reviewable ownership slices: diagnostics scope/redaction, package-Apple stale-bundle cleanup, iOS boot memo reuse, and Harmony viewport caching share no owning interface or validation/evidence path. The refactor(apple): colocate the XCUITest runner client into packages/platform-apple (#2040) #2050 rebase explains the Apple test location but not a runtime dependency. This conflicts with the repository rule to keep changes within one command family/module group unless the task explicitly crosses a boundary.

[P1] Invalidate the Harmony viewport memo when pressHarmonyKeyboardKey receives Back. The Harmony interactor implements keyboard dismiss through pressHarmonyKeyboardKey(device, 'Back'), but this path emits HDC Back without the invalidation performed by backHarmony. If Back navigates (or no keyboard consumes it), the next gesture can use stale geometry for 2s. Add a regression through the keyboard-dismiss/interactor route.

The individual implementations otherwise look sound. Exact-head CI is still incomplete, and Harmony hardware evidence remains unavailable.

[thymikee]

Re-review summary at c604df249ee51daca15b238aa11607c90e864cc3:

• Fixed the HarmonyOS keyboard-dismiss finding by routing Back through the existing invalidating owner.
• Added exact 2,000 ms TTL expiry proof; both regressions were observed red before their fixes.
• Rebased onto current main and reduced this PR to the HarmonyOS owner slice.
• Preserved the removed work as independent current-main PRs: diagnostics perf(diagnostics): reuse redaction and directory work per scope #2056, Apple stale-bundle cleanup perf(apple): uninstall stale runner bundles concurrently #2058, Apple boot-memo reuse perf(apple): reuse booted simulator memo during open #2060.
• pnpm check:affected --run passed all runnable checks (247 files / 1,550 tests).

No remaining code-review finding is known on this head. CI is still authoritative for the final merge verdict.