Skip to content

v0.4.50: M31 fleet per-host health gate (no flip)

Choose a tag to compare

@surlymochan surlymochan released this 17 Nov 15:45
495a824

M31 accepted: fleet per-host health gate + default flip re-evaluation (no flip)

What shipped (PR #255 + #257):

  • Executor-side health probe (openswarm health-probe --backend <b> [--json]) and per-host gate decisions (fleet_probe_host_health(), health_gate_decide() as the single verdict path for run/batch/fleet); gate blocks unhealthy hosts and lets healthy hosts dispatch, recorded in the ledger as fleet_health_gate rows with probe_host / probe_side: executor.
  • Real cross-host evidence (gocc): deepseek blocked (RC=2, unhealthy — no DeepSeek API key) and codex dispatched and really executed (remote run 20261117-213237-5602ef, 28.8s, result done, usage 25838/122/71); full evidence in docs/m31-slice2-real-evidence.md.
  • Flip evaluation: NOT flipped. With the default flipped to enabled: true, the full suite ran 1345 tests with 55 failures + 9 errors — dispatch-path tests implicitly depend on the default being off (this VM's codex is not logged in, so the gate blocks dispatch). policy.json stays enabled: false. Re-flip requires migrating those 64 tests to green under default-on plus a user decision on the impact (every dispatch on a host with no logged-in default backend would exit 2).

Verification: PR CI 10/10 green; main CI run 44107892084 success (attempt 3 — macOS py3.13 leg was twice cancelled by the runner while queued, 0 steps, then passed); independent full-suite re-run 1345 tests OK (skipped=6); remote run result.json re-read on gocc by the reviewing round.

Honest notes: the control-side ledger rows were lost when the VM swapped and wiped /tmp; the blocked-side row rests on the builder's verbatim pre-swap readback, the allowed-side run was re-verified live on gocc. No behavior change to dispatch/routing; CLI name, bin path, OPENSWARM_* env, subcommand signatures and SKILL contract untouched.