R03: Automate the four Android verification gates

[TheDarkSkyXD]

Parent

Build StreamFusion Mobile for Android

What to deliver

Change, Main, Candidate, and Public Release automation with API 30 and current emulator journeys, physical roles, live canaries, accessibility, performance, security, and fail-closed evidence freshness.

Capability IDs

• None; this is enabling work.

Code ownership

• verification
• repository
• mobile

Acceptance criteria

• The behavior above works through the real Android application or the named verification/release path; code presence alone is insufficient.
• Each affected capability has an updated Android Parity Record bound to the current Desktop Baseline and Android candidate.
• The implementation respects the approved responsibility layers and adapter boundaries owned by this ticket.
• Required evidence is indexed: change-gate, main-gate, candidate-gate, public-release-gate, diagnostic-retry, quarantine-block.
• External, lifecycle, persistence, native, or release boundaries define and verify safe failure containment, retry, fallback, disablement, rollback, or forward-fix behavior as applicable.
• The normal Change Gate passes with no untracked architecture exception, quarantined required test, or Development Exception.

Blocked by

• B02: Deliver the adaptive five-destination Android shell
• F04: Create the evidence catalog and verifier foundation

Sources

• Approved implementation specification
• Approved implementation roadmap
• Machine-readable ticket graph

[TheDarkSkyXD]

Claimed by SF Mobile Shipper for overnight parallel ship (while #147 / bc-40364657 finishes visual gate). CloudAgent + /superdev-mode starting.