Merge note to myself — a way this fix could ship dead
Recording this before I forget it, because it is the #234 trap wearing different clothes.
Fleetd.java:393 is one statement:
Co…
Point 3 is done — merged to main in 0d7b4fb (PR #242).
overlayParity now reports the outcome per spawn at info, with the denominator as this ticket and #113 asked:
parity overlay:…
Correction to the record, and it is my error, not the worker's.
My brief told this worker that #134 lived in overlayParity. It does not. #134 is about isolateToolSurface (`GitWorktrees.java:43…
Correction — I closed this by mistake, and have reopened it
My previous comment was wrong. I conflated two different methods in GitWorktrees:
Fixed on main in 0d7b4fb (PR #242).
GitWorktrees.overlayParity now names every file it marks --skip-worktree and states the consequence in the message itself:
parity overlay marked…
Merged to main in 0d7b4fb.
Verified by the lead. Baseline 1168 tests, 0 failures, 0 compile errors, BUILD SUCCESS, and the merged tree is byte-identical to the tree I built (`git diff…
Three more instances from one session (2026-09-03), all found while verifying #201/#227 Units 1-4 and #234. Adding them because each is a different way a checker reports more coverage than it…
Lead decision on points 1 and 2, with the facts first
The ticket says the live exposure was never established and that the answer changes the priority. I checked both hosts.
Merged to main in e5eb353.
Verified by the lead: baseline 1129 tests, 0 failures; routing the unmapped path back through onBackendIncident gives 1 red with 0 compile errors, and it is…
Merged to main in 959c835.
Verified by the lead: baseline 1135 tests, 0 failures; mutating evidenceCount() back to reasons.size() gives 2 reds with 0 compile errors.
One lead…