A quota for each bench
Each bench gets its own byte and inode caps on a dedicated XFS mount, so a bench that runs out of room is refused writes while the shared store stays writable.
Managed Linux hosts only. Quotas need a dedicated XFS mount, a root-owned policy and a privileged helper, set up by an operator. On macOS and on other hosts a quota is recorded, not enforced.
Shared mirrors and caches
Benches start from shared git mirrors, and each repository chooses shared or checkout-local caches, so a new bench starts warm instead of cloning and installing from scratch.
Limits: the shared package store is part of the managed XFS setup above and shares its limits. If refreshing the shared mirror fails, the lease is refused. Collecting old shared caches is not built yet.
Archive and reap only after review
Only a released, clean bench whose checkpoint the remote has confirmed can be archived, as a read-only tree. Deleting it waits out a grace period, seven days by default, and a person approves the exact list of files first.
Local and reviewed. Archive and reap are administrative commands on the machine itself. A repository can opt in to archiving after a merged checkpoint, but nothing is deleted without a reviewed plan. Automatic log retention is off until an operator turns it on, and retiring a bench's quota during reap applies only on managed Linux hosts.
Supervised runs, fenced
bench run puts a process tree in its own cgroup and stops all of it, detached children too, before the bench is checkpointed and released. A run that fails keeps its lease.
Linux only, and fencing, not isolation. It needs a delegated cgroup v2. It does not run the task as a separate user or isolate its mounts, so use it with trusted repositories only.