Development record

Two abcd implement load --wait waiters in one copy renew the same reservations at once, and the one that loses reports each loss as a fault. On 2026-10-27 at 01:51Z a preflight's waiter and a gated test run's waiter, both in one worktree, renewed the same five reservations together. One renewed all five. The other logged 'could not renew your reservation' for each, four of them as origin refusing a non-fast-forward reservation push, and the fifth as 'its latest commit is not one this copy pushed, so it is not renewed from here', though this copy had pushed that commit seconds before. Nothing lapsed, but the lines read as a reservation at risk and the last one names the wrong cause.