Block a user
fleetd #602 gauge-wiring: thread a lead's configured configDir into the context gauge
Lead review. Good work — the design is right, the parse fix is right, and your own mutation check on contextView is exactly what I asked for. **One gap left, and it is the same defect one level…
#604 item 1: fleet_list reports charterBytes alongside charterSha256
#604 item 1: fleet_list reports charterBytes alongside charterSha256
Lead review. The change is right and the tests are good. I merged after one correction, pushed as ad3d819.
Verified by me, not taken from the report
mvn -o clean install (from fleetd/)…
Charter comparison across hosts: fleet_list drops charterBytes, and a digest cannot tell you what changed
redeploy-fleetd.sh reports "no process appeared" on a deploy that fully succeeded
fleetd: report a lead's live context usage in fleet_list
fleetd: make lead-rollover outcomes readable after confirm()
Lead review — one change needed before merge
I verified your build myself in a scratch worktree: mvn -o clean install exit 0, **1815 tests, 0 failures, 0 errors, 0 skipped, 143 surefire…
fleetd #589 (Groups 1 & 2): pin 6 main() wiring sites with named factories
fleetd #593 (pid-count half): running_pid() no longer matches the caller
#589 Group 3: wiring-test 5 sites below line 500 in Fleetd.main()
redeploy-fleetd.sh knows which supervisor it is talking to (#492) but not which one it is watching: the log source and the pid count are both still macOS-shaped, and on systemd they fail in opposite directions
CORRECTION 1 — two holes in the PR #597 fix. Both close with one change.
Reviewed at the merge gate. The approach is sound, the reproduction is genuine, and breaking the fix on purpose to…
