code-coordinator 0.5.140__tar.gz → 0.5.141__tar.gz

{code_coordinator-0.5.140 → code_coordinator-0.5.141}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: code-coordinator
-Version: 0.5.140
+Version: 0.5.141
 Summary: Coordinate Claude Code workers across multiple machines and repos.
 Author-email: John Donaghy <johnfdonaghy@gmail.com>
 License-Expression: LicenseRef-FSL-1.1-MIT

{code_coordinator-0.5.140 → code_coordinator-0.5.141}/code_coordinator.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: code-coordinator
-Version: 0.5.140
+Version: 0.5.141
 Summary: Coordinate Claude Code workers across multiple machines and repos.
 Author-email: John Donaghy <johnfdonaghy@gmail.com>
 License-Expression: LicenseRef-FSL-1.1-MIT

{code_coordinator-0.5.140 → code_coordinator-0.5.141}/code_coordinator.egg-info/scm_version.json

@@ -1,7 +1,7 @@
 {
-  "tag": "0.5.140",
+  "tag": "0.5.141",
   "distance": 0,
-  "node": "g99644043cc6f5e860c84b649e4a026a2d231dadb",
+  "node": "gef1e71db0f0c6bc0d0346e3020abaeabac680993",
   "dirty": false,
   "branch": "HEAD",
   "node_date": "2026-08-18"

{code_coordinator-0.5.140 → code_coordinator-0.5.141}/coord/commands/drive_queue.py

@@ -2761,11 +2761,18 @@ def drive_queue_tick(
                 gates=" | ".join(plan.alert.details),
                 command=plan.alert.command,
             )
-        elif any(h.outcome == "released" for h in plan.holds):
-            # A probe just auto-released the gate.  Drop the "QUEUE HELD"
-            # record in the same tick, or `status` keeps shouting HELD while
-            # the queue is demonstrably running again — the contradiction that
-            # teaches an operator to stop reading alerts.
+        else:
+            # #2381: ANY resolved alert-raising condition — a released hold,
+            # a lapsed/cleared cordon, a fixed editable-drift checkout — must
+            # drop the stale escalation record in the SAME tick it resolves,
+            # or `status` (and the TUI/`decisions` report reading the same
+            # record) keeps shouting the old reason while the queue is
+            # demonstrably running again. This used to be gated on `any(h.
+            # outcome == "released" for h in plan.holds)` — the deploy-gate
+            # case only — so a cleared CORDON (no `plan.holds` entry at all)
+            # never cleared its own stale alert. `_clear_queue_alert()` is a
+            # no-op when there is nothing to dismiss, so calling it on every
+            # alert-free tick is safe and cheap.
             _clear_queue_alert()
 
         target = plan.launch

{code_coordinator-0.5.140 → code_coordinator-0.5.141}/tests/test_cli_drive_queue.py

@@ -2798,6 +2798,41 @@ def test_a_passing_probe_releases_and_launches_in_the_same_tick(
     assert state._get_drive_escalation_local(QUEUE_ALERT_REPO, QUEUE_ALERT_ISSUE) is None
 
 
+def test_a_cleared_cordon_drops_its_stale_queue_alert(cli, seed, launches, monkeypatch):
+    """#2381: a cordon alert must not outlive the cordon.
+
+    The clear-on-resolve path used to be gated on `any(h.outcome ==
+    "released" for h in plan.holds)` — the deploy-gate-hold case only — so a
+    cordon (which raises `plan.alert` but never touches `plan.holds`) left
+    its escalation record behind forever once it lifted: `status` (and
+    anything reading the same record — the `decisions` report, the TUI)
+    kept reporting "cordoned: draining" long after the fleet had rolled and
+    resumed real work.
+    """
+    from coord.commands import drive_queue as drive_queue_cmd
+
+    seed(issues={1650: "open"})
+    cli("add", REPO, "1650")
+
+    monkeypatch.setattr(drive_queue_cmd, "_local_host_id", lambda: "testhost")
+    monkeypatch.setattr(
+        drive_queue_cmd, "_fetch_cordons",
+        lambda: {"testhost": "cordoned: draining for v0.9.9"},
+    )
+    result = cli("tick")
+    assert result.exit_code == 0, result.output
+    assert launches == []
+    alert = state._get_drive_escalation_local(QUEUE_ALERT_REPO, QUEUE_ALERT_ISSUE)
+    assert alert is not None and "cordoned" in alert["reason"]
+
+    # The cordon lifts; nothing else about the queue changed.
+    monkeypatch.setattr(drive_queue_cmd, "_fetch_cordons", lambda: {})
+    result = cli("tick")
+    assert result.exit_code == 0, result.output
+    assert launches and "1650" in " ".join(launches[0])
+    assert state._get_drive_escalation_local(QUEUE_ALERT_REPO, QUEUE_ALERT_ISSUE) is None
+
+
 def test_a_hanging_probe_is_killed_and_treated_as_a_failure(cli, seed, launches):
     """The REAL `_run_resume_probe`, against a command that never returns.