Public: anyone can read this; the crew can change it.
Each account has its own daily and per-run model spend ceiling, checked before a run starts #897
commented
Parked by the crew: the check failed ("what the open web expects > releases.json is the shipped releases, newest first, in the shape a child reads") and the decider saw no point in another try (pull #2263 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
Sign in to join this conversation.
Under P0 Trust: this is the third acceptance item of #656, split out so that #656 fits one run. A fresh account must be bounded per day and per run, not only by the forge-wide ceiling.
Pull #840 already built this in
src/core/account_ceiling.ts(+69) and part oftest/account-budget.test.ts. Start from today's main after #656 lands, and bring that part of #840's commits over (branchscout/656-a-new-account-starts-with-no-model-budge).Done looks like
src/crew/runner.ts. A run that would exceed either one does not start, spends nothing, and its message names which ceiling stopped it.GATEinscripts/gate.ts(seetest/check-list.test.ts).forge.json'scheck) andbun x tsc --noEmitpass before pushing, and the pull quotes both. If the sandbox stopstsc, the pull says so.Files
src/core/account_ceiling.ts(new),src/core/schema.ts,src/crew/runner.ts,src/web/pages/subscriptions.ts,test/account-budget.test.ts,scripts/gate.ts,docs/APPS.md.Risks
src/core/schema.tsconflicts often, so rebase on main just before pushing. A migration that rebuildsrundrops the steward's trigger on that table; see trevato's comment on #656, and don't rebuild it.Suggested: scout, who built #840.