[teamleaderleo]

Leo, 2026-10-26: "Just throw it away. Just delete more stuff, more often." That holds on every mini except one a person has reserved.

What changes

This lands in front of #1622 (12 h ages), #1625 (12 h mirrors) and #1624 (node-store cap). On a reserved host they act only under floor pressure.

• No reservation data lives in this repository. glaeda-disk reads the list only from the host: ~/.local/share/glaeda/fleet-reservations.json in the home of the user that owns /Users/Shared/cmux-build-fleet (schema glaeda-fleet-reservations/v1: {"expires","reservations":[{"id","owner","hosts":[...],"from","until"}],"aliases":{host:[...]}}; the writer stamps expires 13 h after each write and refreshes it every 6 h), written there by the fleet's own writer, plus the host-local /Users/Shared/cmux-build-fleet/reservation.json (glaeda-reservation/v1, the file the runner hook reads).
• host_reservation() matches this host by glaeda-update's configured host name or its machine name. Fails closed: a missing, unreadable, malformed or expired list (or one with no expires) (hosts not a list of names, a bad time on any entry, aliases not lists) reads as reserved, whatever the host-local file says. An entry lapses by itself after until.
• On a reserved fleet mini, every --apply of glaeda-disk (the --runner-caches profile included) runs no idle sweep. A pressure pass starts at the runner floor itself (not floor + low_margin) and frees only up to the floor plus target_margin_gib. Any other apply deletes nothing and says why.
• glaeda-fleet-cas-prune --apply on a reserved host above its floor defers before anything, store gc included. It loads glaeda-disk registered in sys.modules, so the dataclasses load and the check is real (a test loads the real script against a made-up list).

Before / after

Before: a merged glaeda change reaches every mini through OTA, and its idle sweeps age out state on a host someone has reserved. After: on a reserved host, glaeda acts only to keep the disk above the floor until the reservation lapses. Baseline free-disk minimums are in #1622.

Risk

Low. Reserved hosts delete less. A host with no list yet also deletes less (fail closed), but the floor still protects jobs. Unreserved hosts with a list behave exactly as before.

Tests: HostReservationTest (active entry or alias, lapse, missing and malformed lists fail closed, the fleet owner's home, floor-exact pressure, the main-flow gate with and without --runner-caches); the prune's real-loader check and its gate before store gc. Fixtures use made-up ids, hosts and owners.

Agent session: agent session

🤖 Generated with Claude Code

[teamleaderleo]

Owned by an agent session · session

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
35581672	Triggered	Generic Password	5922735	scripts/test-glaeda-disk.py	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}