Usage included every month, for every account, and jobs run on it

Every account now gets 100 GiB-hours of machine memory, 25 vCPU-hours of active CPU, 10 GB of saved copies (snapshots, images, backups) and 5 GB of volumes each calendar month, enough for 100 free hours of a 1 GB machine, with no card. It renews on the 1st (UTC), is used before credit and is never charged. New accounts get it in place of free hours; an account given free hours before 6 October keeps what is left of them, and has the included usage as well. GET /v1/usage lists each product's share under allowances, and trial gains offer and renewsAt. A scheduled job's runs spend it first, then credit, as a sandbox does; a run it cannot take, on an account without credit, waits with blockedReason credits. An account holds up to 1,000 jobs and 1,000 secrets for jobs, where it held 50 and 200. Credit, bought or given, now opens every paid feature but three: a kept top-up is needed only for ports beyond 80 and 443, public previews, and private networks and Tailscale. Without credit, an account runs at most 8 vCPU and 16 GiB at once across its sandboxes and image builds, beside 2 vCPU and 4 GiB each and eight at once; past it, a create, wake or build is refused with 409 no_credit_total_limit, whose message says what runs now. Seven codes are renamed, in the API, MCP, CLI and every SDK: trial_busy is now no_credit_running_limit, trial_capacity no_credit_capacity_full, invalid_trial no_credit_size_limit, trial_domain_limit no_credit_domain_limit, trial_build_limit no_credit_build_limit, trial_exhausted included_usage_used_up and trial_unavailable included_usage_unavailable; code that compares with an old name should compare with both until it updates. See included usage and what a job costs.