test: add Android full emulator coverage

[thymikee]

Summary

Adds Android-specific full/nightly fixture coverage for runtime permissions, IME recovery, app-observed push broadcasts, helper-backed gestures, long-list replay recovery, observability artifacts, and JUnit replay output.

Stacked on PR #1482 (test/android-emulator-catalog-smoke). This PR remains stacked and must be rebased onto PR2's accepted head before final validation. It must not merge until the coordinator marks it ready-for-human, exact-head checks pass, and adversarial review is clean.

Validation

• pnpm check
• pnpm check:affected against PR2 head 5512f89
• Android emulator coverage and fixture-artifact contract tests
• Retry-free Android smoke E2E on an attached emulator
• Native Expo module prebuild/autolinking and Release compilation reached native module compilation; the host-specific local AAPT long-path failure leaves Ubuntu exact-head CI as the full live oracle.

[thymikee]

PR #1484 is not ready at exact head 8538b7b.

• P1 — stacked-base blocker. The PR is based on test(android): add comprehensive emulator E2E coverage #1482 head d8de04d, while test(android): add comprehensive emulator E2E coverage #1482 has advanced; GitHub reports this branch conflicted. This head has no PR checks, so there is no exact-head CI or inspectable full-emulator evidence. Rebase onto test(android): add comprehensive emulator E2E coverage #1482’s accepted head, resolve the dependency first, and rerun the required checks plus the Android full-emulator lane.
• P2 — trace MCP schema drift. TraceCommandResult and record-trace.ts now require/return artifacts for trace: "stopped", but src/mcp/command-output-schemas.ts still advertises only trace and outPath. Schema-driven clients will not discover the downloadable trace-log artifact. Add the standard artifact array to the stopped-trace schema and a focused MCP output-schema assertion.

No ready-for-human label while the branch is conflicted, lacks exact-head evidence, and carries this contract drift.

[thymikee]

Exact-head review found two blockers:

1. Stack/base blocker: this draft is still stacked on a stale test(android): add comprehensive emulator E2E coverage #1482 base and is currently conflicting. It has no exact-head GitHub checks. Rebase onto test(android): add comprehensive emulator E2E coverage #1482’s accepted head, resolve conflicts, then rerun the required checks and full Android emulator evidence before requesting readiness.
2. MCP schema drift: trace stop now returns a required artifacts array with a downloadable trace-log, but the stopped trace branch in src/mcp/command-output-schemas.ts still declares only trace and outPath. Add the standard artifacts schema and a focused schema assertion so schema-driven clients can discover the new response field.

The manifest/evidence machinery is otherwise structurally meaningful, but the expanded live-scenario scope goes beyond #1426’s original guardrail and needs explicit coordination/approval after the stack is repaired.

[thymikee]

Exact head 8538b7b is not ready: it is conflicting against the rewritten #1482 stack, and two gaps remain. (1) trace stop now requires/emits artifacts, but the MCP output schema still advertises only trace and outPath; add required artifact schema coverage. (2) coverage-report.json contains runtime evidence/timing only, but #1426 requires manifest-derived live/contract/capability-denial/known-gap counts; add the rollup and a drift-proof test. Rebase first, then validate the resolved exact head with CI/live emulator evidence.