October 2, 2026 CLI 0.1.25

# Failed deploys say who needs to act and how to fix it

- **deploy** A failed deploy now says who acts (your app, your account, or Ample), with a diagnosis, log evidence and a suggested fix, such as a missing environment variable.
- **deploy** When a failure is on Ample's side, the deploy waits while Ample fixes it and then continues. If it still fails, the error links to an incident.
- **cli** `ample auth claim --email` (MCP: ample_auth_claim) emails the person a link to claim the account. The sign-in page also offers to claim an unclaimed account.
- **pricing** Apps over their budget are now paused with their data kept, not deleted. They answer 503 budget_exceeded until the account is back under budget.
- **cli** `ample plan` detects standard-library Python apps and explains an empty plan. Rerunning `ample deploy` while a deploy is in progress waits for it instead of failing.
- **deploy** Files under node_modules, vendor, .venv, target and similar folders no longer decide an app's runtime.
- **deploy** An app's own start.sh is no longer overwritten. Every runtime with an install or build step gets an 8 GiB disk, and refused boots now report the reason.
- **pricing** The pricing page now lists the Free plan and a Custom plan for larger needs.
