code-coordinator 0.5.520__tar.gz → 0.5.521__tar.gz

{code_coordinator-0.5.520 → code_coordinator-0.5.521}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: code-coordinator
-Version: 0.5.520
+Version: 0.5.521
 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.520 → code_coordinator-0.5.521}/code_coordinator.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: code-coordinator
-Version: 0.5.520
+Version: 0.5.521
 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.521/code_coordinator.egg-info/scm_version.json

@@ -0,0 +1,8 @@
+{
+  "tag": "0.5.521",
+  "distance": 0,
+  "node": "g1d59afeac7d0d003c9bbecd7b2711c6ebe8adaf8",
+  "dirty": false,
+  "branch": "HEAD",
+  "node_date": "2026-09-27"
+}

{code_coordinator-0.5.520 → code_coordinator-0.5.521}/coord/dr_verify.py

@@ -714,13 +714,26 @@ def live_board_assignment_count(live_db_path: Path) -> int:
     count, which is always larger once a board has any history (#762's
     retention cap). There is no need to *boot* a second daemon to answer this:
     the live daemon (if one is even running) is not what is being tested here
-    — only "what would `/board` report for this file" is needed, and that is
-    exactly :meth:`coord.dao.SqliteStore.board_projection`, the same function
-    `coord/serve_app.py`'s `/board` route calls. Calling it directly, read-only,
-    against the live file is the "one question, one answer" version of asking
-    a second daemon to boot just to answer a question the daemon already
-    knows how to answer without booting.
+    — only "what would `/board` report for this file" is needed.
+
+    That answer is **not** simply :meth:`coord.dao.SqliteStore.board_projection`
+    — #762's retention window is only the first of two filters the route
+    applies. ``coord/serve_app.py``'s `/board` route also runs the projection
+    through :func:`coord.board_wire.bound_board_payload`, which caps terminal
+    assignments to :data:`coord.board_wire.MAX_TERMINAL_ASSIGNMENTS` (#1791) on
+    top of the retention window — a *second*, tighter cut a board with any
+    real history will always hit before the 14-day window ever does (#3451).
+    Skipping that second cut here made this function's own docstring claim —
+    "the same function `/board` route calls" — false: it counted a raw,
+    unbounded-by-cardinality projection while the restored side (a real
+    daemon's `/board`) counted the capped one, so parity failed on every real
+    fleet board regardless of whether the restore was actually fine.
+    :func:`coord.board_wire.bound_board_payload` mutates ``payload`` in place,
+    so applying it here before counting is the "one question, one answer"
+    version of asking a second daemon to boot just to answer a question the
+    daemon already knows how to answer without booting.
     """
+    from coord.board_wire import bound_board_payload  # noqa: PLC0415
     from coord.dao import SqliteStore  # noqa: PLC0415
 
     try:
@@ -730,6 +743,7 @@ def live_board_assignment_count(live_db_path: Path) -> int:
             f"parity check failed: could not read the live board's /board "
             f"count from {live_db_path}: {exc}"
         ) from None
+    bound_board_payload(payload)
     rows = payload.get("assignments")
     if not isinstance(rows, list):
         raise DRVerifyError(

{code_coordinator-0.5.520 → code_coordinator-0.5.521}/tests/test_dr_verify.py

@@ -576,6 +576,77 @@ def test_parity_failure_names_both_board_comparands_not_a_table_count(lane):
     assert "/board (live)" in message
 
 
+def _seed_recent_terminal_assignments(path: Path, *, count: int) -> None:
+    """*count* RECENT terminal rows — inside #762's retention window, but
+    when *count* exceeds `coord.board_wire.MAX_TERMINAL_ASSIGNMENTS`, past
+    #1791's tighter cardinality cap the `/board` route applies on top of
+    retention. This is the #3451 shape: a store where the 14-day window keeps
+    everything, yet `/board` still trims — the case
+    `live_board_assignment_count` silently skipped before this fix.
+    """
+    conn = sqlite3.connect(str(path))
+    conn.row_factory = sqlite3.Row
+    try:
+        _ensure_schema(conn)
+        now = time.time()
+        conn.executemany(
+            "INSERT INTO assignments (assignment_id, machine_name, repo_name, "
+            "repo_github, issue_number, issue_title, status, type, "
+            "dispatched_at, finished_at) VALUES (?,?,?,?,?,?,?,?,?,?)",
+            [
+                (
+                    f"recent-term-{i}",
+                    "precision",
+                    "claude-coordinator",
+                    "JDonaghy/claude-coordinator",
+                    500_000 + i,
+                    f"recent issue {i}",
+                    "done",
+                    "work",
+                    now - i,
+                    now - i,
+                )
+                for i in range(count)
+            ],
+        )
+        conn.commit()
+    finally:
+        conn.close()
+
+
+def test_live_board_assignment_count_matches_the_real_board_route_past_the_cap(
+    tmp_path, valid_config_path, coord_db,
+):
+    """#3451: the live side must count exactly what a real `/board` route
+    would serve for the same file — including #1791's `MAX_TERMINAL_ASSIGNMENTS`
+    cardinality cap, not just #762's retention window (#3135's fix stopped
+    short of it). Pins the two paths together with the real route, not a
+    reimplementation of it, so a future cap cannot drift between them again.
+    """
+    pytest.importorskip("uvicorn")
+    from starlette.testclient import TestClient  # noqa: PLC0415
+
+    from coord.board_wire import MAX_TERMINAL_ASSIGNMENTS  # noqa: PLC0415
+    from coord.config import load as load_config  # noqa: PLC0415
+    from coord.dao import SqliteStore  # noqa: PLC0415
+    from coord.serve_app import build_app  # noqa: PLC0415
+
+    db_path = tmp_path / "live-shaped.db"
+    _seed_recent_terminal_assignments(db_path, count=MAX_TERMINAL_ASSIGNMENTS + 150)
+
+    app = build_app(SqliteStore(db_path), load_config(valid_config_path))
+    with TestClient(app) as client:
+        resp = client.get("/board")
+    assert resp.status_code == 200
+    route_served = resp.json()["assignments"]
+
+    # Sanity: the seed really is past the cap — otherwise this test cannot
+    # tell the #3451 fix apart from the bug it regression-tests.
+    assert len(route_served) < MAX_TERMINAL_ASSIGNMENTS + 150
+
+    assert dr_verify.live_board_assignment_count(db_path) == len(route_served)
+
+
 # ==========================================================================
 # Acceptance: the scratch copy is removed on EVERY exit path
 # ==========================================================================

{code_coordinator-0.5.520 → code_coordinator-0.5.521}/tests/test_sqlite_connect_ratchet.py

@@ -220,7 +220,7 @@ SQLITE_CONNECT_ALLOWLIST: dict[str, Classification] = {
         "it.",
     ),
     "test_dr_verify.py": Classification(
-        4, (BUCKET_A,),
+        5, (BUCKET_A,),
         "#3119's DR-verify lane — the restore half of test_backup.py directly "
         "above, and filed A for the same reason. All four sites build or "
         "mutate a real on-disk SQLite *file* that is then snapshotted, "
@@ -239,6 +239,15 @@ SQLITE_CONNECT_ALLOWLIST: dict[str, Classification] = {
         "restore it. (The zero-assignments parity case reuses "
         "hollow_out_assignments() rather than opening its own connection, so "
         "#3135 added one site, not two.) "
+        "+1 for #3451's _seed_recent_terminal_assignments(), which bulk-"
+        "inserts RECENT terminal rows past #1791's MAX_TERMINAL_ASSIGNMENTS "
+        "cardinality cap into a real on-disk file so the live side can be "
+        "pinned against a genuine /board TestClient response — the case "
+        "live_board_assignment_count silently skipped before this fix, "
+        "because #3135's retention window alone was not enough to trigger "
+        "the cap. Same file, same reason: it has to be an on-disk file "
+        "because the very next thing the test does is open it through both "
+        "SqliteStore(by path) and dr_verify.live_board_assignment_count(). "
         "The autouse coord_db fixture cannot serve any of them — there "
         "is no file to restic — and scratch_database() is out for the usual "
         "backend-following reason: under COORD_TEST_BACKEND=postgres these "

code_coordinator-0.5.520/code_coordinator.egg-info/scm_version.json

@@ -1,8 +0,0 @@
-{
-  "tag": "0.5.520",
-  "distance": 0,
-  "node": "g2ea6b6f3078698338dac5da492049a1c5a760d8e",
-  "dirty": false,
-  "branch": "HEAD",
-  "node_date": "2026-09-26"
-}