You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fb99b46: Fleet booking, step 2 of 2 (A11-244): the scheduled fleet work takes leases from the lease ledger too, so it never lands in the middle of a capture. The hourly drift check (fleet-drift.ts --record) takes a shared read lease on every box no maintain lease holds; it reads beside a capture, because it sends only GET /health and GET /progress, the reads that already run during every capture. A box under maintain is not asked that hour: it is recorded in skipped as unread with its holder, and its last differences are carried. The daily freeze (a11y-fleet-freeze-daily.service) now runs src/fleet-leases/freeze-daily.ts, which takes an exclusive maintain lease per box, runs freeze.yml --limit <the free boxes> as batches, waits for the rest, and stops after 6 hours, naming any box it never got in leased in runs/fleet-freeze-last-run.json (carried into the hourly record's freeze) and failing the unit. The idle power-off produces its lease-pending (per box: a live capture or maintain lease, or a queued job that named it) and batch-queued (a job waiting for "any N" or ready boxes) signals from the ledger, and takes a non-queueing maintain lease across each sleep.yml dispatch. Re-run pnpm run fleet:freeze-schedule after merge to install the freeze unit's new ExecStart.