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
- ..
- about.rs
- activity.rs
- addresses.rs
- alerts.rs
- archives.rs
- audit.rs
- billing.rs
- blobs.rs
- broker.rs
- caches.rs
- checks.rs
- commits.rs
- contents.rs
- coordination.rs
- deploy_keys.rs
- deployments.rs
- folios.rs
- follow.rs
- lib.rs
- limits.rs
- logs.rs
- mcp.rs
- notifications.rs
- oauth.rs
- oidc.rs
- openapi.rs
- operations.rs
- packages.rs
- people.rs
- pins.rs
- projects.rs
- protection.rs
- reference.json
- renamed.rs
- responses.rs
- rest.rs
- rules.rs
- run_artifacts.rs
- runners.rs
- security.rs
- telemetry.rs
- token_policy.rs
- toolkit.rs
- tools.rs
- why.rs