v3.13.1
Patch. Every run now ships with a spend ceiling. A stuck or runaway pipeline can no longer drain a subscription quota unattended.
Fixed
max_budget_usddefaults to 5 (KJC-TSK-0621, from a field report of a stuck run burning a user's whole quota): the per-iteration budget enforcement existed but the default wasnull— opt-in safety. Exceeding the cap stops the run with the spend, the limit, how to raise it and how to continue (kj resumeopens a fresh window). Explicitnullopts out; the legacysession.max_budget_usdlocation keeps working.