Mobile Release

This is a Hermes-native mobile-release workflow skill.

Why This Exists

mobile-release exists because store releases had no owner: omh-release-cut decides a service release that can roll back, omh-deploy-and-monitor watches a deploy, and omh-production-audit audits readiness platform-neutrally, while signing, a privacy manifest, a TestFlight beta or a Play staged rollout had nothing that knew the store's gates.

First Steps

• Ask which platforms, which version and build number, and how signing is held today.
• Ask what halts the rollout, before planning any rollout step.

Do Not Use When

• The ask is a versioned release of a service or library -- what goes in, the tag, a canary, the rollback command; use omh-release-cut.
• A web or backend deploy is already out and the ask is watching its health; use omh-deploy-and-monitor.
• The ask is a readiness audit across observability, security, and operations before launch; use omh-production-audit.
• The app crashes or misbehaves and the ask is finding the cause in the code; use omh-app-debugging.