syntaqxThe spend caps of g1t's former agents are gone end to end. Billing no longer serves set_caps (the owners' run and issue caps, which nothing called), reads the owners' caps from limits, or puts a run cap and an issue cap in a workspace's entitlements; ISSUE_CAP_MICROS and RUN_CAP_MICROS are no longer read, and a staff override no longer carries either, so sudo stops sending them. The runner no longer turns a run cap into a cost cap, and the GUARDRAILS it hands a sandbox says the run's time cap and default branch only, without the command rules, deny patterns and cost cap nothing reads. A run's guardrails no longer carry restrictNetwork and hosts, sent only for runners from before network rules were removed. Stored data still reads: the limits and billing_accounts columns stay, no migration is touched, and a run recorded with a budget still shows it. Checked: cargo test for g1t-billing (243) and g1t-contracts (307), cargo check of the workspace, the TypeScript typecheck, the runner's 88 tests, sudo's 153, the contracts' 48 and the deploy tool's 92.7c48be8History
- ..
- advisories.rs
- code_scanning.rs
- config.rs
- deps.rs
- history.rs
- lib.rs
- manifests.rs
- overview.rs
- patterns.rs
- planning.rs
- pull_text.rs
- ranges.rs
- registries.rs
- resolved.rs
- schedule.rs
- secret_alerts.rs
- security_updates.rs
- store.rs
- suite.rs
- suite_store.rs
- summaries.rs
- supply_chain.rs
- timezones.rs
- update_store.rs
- updates.rs
- version_updates.rs
- yaml.rs