Correction to my mutation numbers above
I reported mutation 2 as "4 failures + 1 error". The error carries nothing and should not have been in the total. The fleet01 lead caught it from…
This ticket and #489 are the same defect family. Naming it, with the bar for calling it a pattern not yet met.
The fleet01 lead gave me a definition while reviewing #490, and was careful to…
Three corrections and one generalisation, all from the fleet01 lead's second read
1. The release-and-send trade: use this reason, not the one in the ticket
I justified sending `bootstrapTe…
Not merging yet. none means two different things, and only one of them is safe.
Good work overall — the overridable-probe seam, require_drivable_supervisor, and assert_single_daemon are…
fleet01's operator has answered: deferred, not scheduled. Do not hold this issue for that host.
Reported for the fleet01 lead, who still has no forge credential. Their words, condensed:…
The fleet01 test: reported here on that lead's behalf
The operator asked me to have fleet01 test the roll and to fix whatever came out. I asked the fleet01 lead over the coordination channel.…
Correction to this ticket's "Related" section. My #488 claim was wrong.
I wrote that fleet01's layout "would expose" #488 — fleet.leaders.<name>.cwd never being validated, so a relative…
This now has a reproduction. Found while mutation-testing #489 / PR #490 on 2026-09-12.
Mutate one character of the FIRST gate in LeadRollover.waitUntilAtTurnBoundary — drop DONE, so it…
Acceptance criterion 6 is now answered, negatively. Measured on the Mac, 2026-09-12, first real rollover of the shipped feature with a Claude Code lead.
The roll was confirmed at `07:03:30.903…