Mobile Release Validation

---
name: mobile-release-validation
description: Build, sign, package, and validate mobile releases across device/OS matrix, permissions, upgrades, deep links, background behavior, crash reporting, and store constraints.
---
# Mobile Release Validation

Use when this procedure is the primary professional method needed for the assignment.

## Procedure
1. Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
2. Establish the evidence baseline using release config, signing via approved secret flow, device matrix, prior production version, store rules, and test plan. Do not fill material gaps with assumptions when they can change the result.
3. Create clean release build, verify entitlements/manifests, test fresh install and upgrade, exercise critical device states, inspect symbols/crash reporting, and record store metadata requirements.
4. Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
5. Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
6. Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.

## Quality gate
The signed artifact passes critical flows on representative real devices and upgrade state is explicitly proven.