What problem does it solve? After publishing an over-the-air update with EAS Update, teams lack a terminal-based way to verify rollout health, forcing them to manually check expo.dev dashboards for crash rates, adoption counts, and embedded-vs-OTA user splits. ## Core Features & Use Cases - Update Group Insights: Retrieve per-platform launches, failed installs, crash rate percentages, unique users, and payload sizes for any published update group via eas update:insights. - Channel-Level Analytics: Compare embedded build users against OTA update users and rank the most popular updates per channel and runtime version with eas channel:insights. - CI Gating and Regression Detection: Parse JSON output with jq to detect crash-rate spikes in the last 24 hours or gate releases on aggregate update health. - Use Case: After publishing a fix to the production branch, grab the latest group ID with eas update:list, then check crashRatePercent per platform to confirm the rollout is healthy before widening distribution. ## Quick Start Ask the assistant to check whether the latest EAS Update published to the production channel is healthy, including its crash rate and adoption numbers.