What problem does it solve? Expo OTA updates silently fail to reach users when the update's runtimeVersion fingerprint does not match the installed builds, and eas update gives no warning. This Skill enforces a publish-and-verify discipline so updates actually arrive on devices. ## Core Features & Use Cases - Fingerprint verification: Compares eas update:list against eas build:list after every publish to confirm the runtimeVersion values match exactly. - Fingerprint-breaking change list: Identifies which changes (native packages, SDK upgrades, app.json native config, stray ios/android directories) require a new binary instead of an OTA. - Channel-branch-profile mapping: Provides the standard eas.json triple (development/preview/production) and matching app.json configuration with the fingerprint runtimeVersion policy. - Use Case: A tester reports an update never arrived. Run the section 2 comparison, discover the fingerprint mismatch caused by a newly added native package, and cut a new binary instead of republishing OTA. ## Quick Start Ask the agent to publish the current change with eas update to the production branch and verify the runtimeVersion matches the latest build.