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
- ..
- 0001_init.sql
- 0002_rfc3339_timestamps.sql
- 0003_protection.sql
- 0004_store_key.sql
- 0005_topics.sql
- 0006_stored_bytes.sql
- 0007_git_operations.sql
- 0008_repo_redirects.sql
- 0009_lifecycle.sql
- 0010_refs_version.sql
- 0011_artifacts_meters_forks_health.sql
- 0012_deleted_with_workspace.sql
- 0013_backups.sql
- 0014_namespace_moves.sql
- 0015_about.sql
- 0016_stats_version.sql
- 0017_push_commits.sql
- 0018_mirror.sql