Fly.io CLI

**Quick judgment**: This is a solid, production-oriented Fly.io helper that wraps `flyctl` with strong safety defaults. It’s best suited for teams already using Fly.io who want the assistant to inspect and debug apps, and only mutate state when explicitly instructed. **What it’s good for** - Day-to-day diagnostics: checking app status, logs, config, releases, and secrets list (names only) without risk of unintended changes. - Guided debugging of deploy/build/runtime issues, especially Docker + Rails builds and native gem/platform mismatches. - Support for common Fly Postgres workflows (list clusters, attach to apps, create DBs, connect) when you explicitly approve changes. - Helping design or refine GitHub Actions CI/CD for Fly deploys and PR preview environments. **Key risks / limitations** - Any actual deploys, SSH commands, secrets changes, scaling, machines/volumes ops, or Postgres mutations depend on your explicit approval; if you’re not clear in your request, the assistant will (correctly) stay read-only. - Underlying reliability and performance depend on your Fly.io account, app configuration, and the availability of `flyctl` and Fly APIs. - It does not replace Fly.io documentation or deep platform knowledge for complex infra design; it’s an operational companion around `flyctl`. **Recommended scenarios** - You run apps on Fly.io and want safe, assistant-driven inspections and debugging. - You’re troubleshooting failed Fly deploys, especially for Rails or Docker-based apps. - You’re setting up or maintaining GitHub Actions workflows for Fly deploys and PR previews and want help wiring `flyctl` into CI. - You want a guarded interface where destructive operations are only run when you clearly and explicitly ask for them.