Q01: Qualify full Android workloads and integrated degradation before release

[TheDarkSkyXD]

Parent

Part of #122. Split from #143 with the user's instruction to keep all work before release.

What to deliver

Qualify the complete Android workload on the required physical device roles after real media implementations exist. Demonstrate measured admission, ordered runtime degradation, hysteresis, recovery, and preservation of focused work and artifacts through the finished mobile UI. This is mandatory development qualification, not work deferred until release or after release.

Acceptance criteria

• Preserve every full-workload requirement formerly assigned to B06: Measure Capability Profile and apply Runtime Degradation #143. Distinguish installation eligibility, raw observations, measured capacity and actual qualification. Neither emulator decoder inventory nor synthetic-only load qualifies a physical device.
• Exercise live and recorded playback, retained Multistream slots and two through six active videos, captions, recording, downloads, export and complete Diagnostics. Verify real mitigation consumers, focused audio/work ownership and artifact preservation, not just projected stage labels.
• Review reproducible absolute performance limits, measurement durations and hysteresis thresholds before qualification claims. Preserve the existing two-video floor, 43.11 MiB caption model, four-hour recording, 10% regression bound and PRD section 14 limits. OPEN-PERF is not waived.
• Verify constrained memory/storage, thermal transitions, all degradation stages, timed recovery, stale/unavailable measurements, retries, background gaps, process death and restart through actual workloads. Retain slot configurations and recoverable artifacts.
• Complete and verify all affected Watch, Multistream, media-job and Diagnostics UI/UX, loading, busy, unsupported, constrained, failure/retry and recovery states. Compare the approved mockups and Desktop outcomes. Feature issues still own their UI before closure; this issue validates integration and resolves remaining qualification findings.
• Use literal root npm start option 3 and Mobile MCP with the matching development client for custom native behavior. Include required physical-device evidence, source and APK identities, matched mockup/app screenshots and observed actions.
• Index current change-gate, lowest-device, constrained-device, thermal-proof and degradation-order evidence. Bind Android Parity Records to the current Desktop Baseline and Android candidate. Pass normal gates without exceptions or quarantined required tests.
• Finish before Mobile: Complete mockup, UI/UX, action, and business-logic coverage #195's final completion and before R04: Promote one exact APK into an immutable Android Release Set #178, P01: Close every Android parity record #179, P02: Pass the complete Candidate Gate twice #180 or P03: Publish the first Public Android Release #181 can complete. No release, promotion, acceptance waiver or threshold approval is authorized by this ticket.

Blocked by

• B06: Measure Capability Profile and apply Runtime Degradation #143 capability-profile and degradation foundation.
• W01: Resolve and watch one live Stream #152 live playback, W02: Deliver player controls, movable mini-player, and Android PiP #153 player controls and W03: Watch Videos and Clips #154 recorded playback.
• W09: Deliver capability-aware Multistream #160 Multistream.
• M01: Deliver the recoverable Media Job engine #163 recoverable Media Jobs, M02: Download and explicitly export Videos and Clips #164 downloads/export, M03: Record and recover a live Stream #165 recording and M04: Caption the focused Stream locally #166 captions.
• M05: Deliver appearance and player Settings #167 player Settings, M08: Deliver update, support, and maintenance Settings #170 maintenance Settings and M09: Deliver Android Diagnostics and sanitized reports #171 complete Diagnostics.
• R03: Automate the four Android verification gates #177 verification-gate automation.

Sources

• Implementation specification, especially sections 7, 10, 11, 14 and 19.
• Feature UI/UX and requirements review.
• Original foundation and qualification issue.