Live sandboxes, forkable snapshots, loop-shape counters [rate class: sandbox_api_rps]

This workspace's sandbox plane at a glance: live sandboxes (each with the snapshot it forked from and its fork depth - or shared_base: true and no snapshot, meaning it came from a base Autoresearch keeps warm, which is ours and cannot be forked by id), forkable snapshots, and loop-shape counters - bakes, boots (create_sandbox), fork calls, sandboxes forked, execs, voids, oom_execs, deletes. Read it to audit a loop (N samples should read as ~1 bake, N forked, few exec calls, N deletes - if bakes or boots track your sample count, switch to fork_sandbox), to find leaked sandboxes still billing, and to see voids (infrastructure failures on our side, never billed). oom_execs counts execs that hit the guest's OOM killer - your memory budget, billed; if it tracks your sample count, bake the env with more ram_gib. The counters are live process counters since this api instance started - a shape audit, not a bill; metered usage lands in get_usage with M14.