The platform now hands out boards per request and resets a board on release
(11-07 measured: free again after 42 s, new password, new host key, our key
gone). Boards are no longer ours between uses, so:
- harness/board_lease.py: request by board id (looked up by SSH port), install
our public key with that lease's password (SSH_ASKPASS, never on a command
line), release. A board-<slot>.rdk.json marker records each borrow, so a
crashed holder's board is found and released; boards a person holds on the
same account are never touched. Token in .env.local (RDK_SANDBOX_TOKEN) stays
in controller processes; without it boards are used as statically configured.
- scheduler: borrow after taking the slot lock, give back right after use; an
unavailable board rests 30 s per waiter. The reset replaces the board
quarantine: receipts/idle-probe release and the orphan-marker loop in
reconcile_leases become one sweep that gives back a dead holder's board.
- Host keys are no longer pinned (every borrow changes them): board_perf,
the idle probe, Salty containers stop copying known_hosts.
- health_check: platform status replaces TCP and pinned-key ssh probes; warns
when a march has no borrowable board or a borrow is older than 2 hours.
The agent's board access is unchanged (bench dev --board, stage run
board/eval); it never sees the token, passwords or which board it gets.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>