What problem does it solve? After publishing an EAS Update, teams lack a quick terminal-based way to verify rollout health—crash rates, install counts, unique users, and the split between embedded and OTA users—without opening the expo.dev dashboard. ## Core Features & Use Cases - Update health checks: Run eas update:insights <groupId> to get per-platform launches, failed installs, crash rate, unique users, and payload size with daily breakdowns. - Channel-level adoption: Run eas channel:insights to compare embedded-build users versus OTA users and rank the most popular updates per channel and runtime version. - CI gating and regression detection: All commands support --json --non-interactive for scripting, enabling automated rollout monitoring and crash-rate thresholds. - Use Case: After publishing a fix to the production branch, grab the latest group ID with eas update:list, then check whether the crash rate exceeds 1% in the last 24 hours before widening the rollout. ## Quick Start Ask the assistant to check whether the latest EAS Update published to the production channel is healthy, including its crash rate and user adoption.