code-coordinator 0.5.110__tar.gz → 0.5.112__tar.gz

{code_coordinator-0.5.110 → code_coordinator-0.5.112}/PKG-INFO

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

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: code-coordinator
-Version: 0.5.110
+Version: 0.5.112
 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.110 → code_coordinator-0.5.112}/code_coordinator.egg-info/SOURCES.txt

@@ -193,10 +193,10 @@ coord/dashboard/webapp/dist/index.html
 coord/dashboard/webapp/dist/manifest.webmanifest
 coord/dashboard/webapp/dist/sw.js
 coord/dashboard/webapp/dist/workbox-e4022e15.js
-coord/dashboard/webapp/dist/assets/Gallery-Cq84itDE.js
+coord/dashboard/webapp/dist/assets/Gallery-BoKs3mpY.js
 coord/dashboard/webapp/dist/assets/Terminal-9CEnUXvW.css
-coord/dashboard/webapp/dist/assets/Terminal-DOXLcMue.js
-coord/dashboard/webapp/dist/assets/index-DHn-RIJ8.js
+coord/dashboard/webapp/dist/assets/Terminal-CEsP08iX.js
+coord/dashboard/webapp/dist/assets/index-CDHPlB6k.js
 coord/dashboard/webapp/dist/assets/index-Dq4kwTdw.css
 coord/dashboard/webapp/dist/assets/workbox-window.prod.es5-BqEJf4Xk.js
 coord/dashboard/webapp/dist/icons/icon-192.png
@@ -786,6 +786,7 @@ tests/acceptance/ms-example/mocks/home-active.html
 tests/fixtures/board-pipeline-basic.json
 tests/fixtures/board-pipeline-terminal-gates.json
 tests/fixtures/opencode_run_failure_sample.jsonl
+tests/fixtures/opencode_run_length_sample.jsonl
 tests/fixtures/opencode_run_sample.jsonl
 tests/fixtures/playwright/all_pass.json
 tests/fixtures/playwright/global_setup_crash.json

{code_coordinator-0.5.110 → code_coordinator-0.5.112}/code_coordinator.egg-info/scm_file_list.json

@@ -433,6 +433,7 @@
     "tests/fixtures/board-pipeline-basic.json",
     "tests/fixtures/board-pipeline-terminal-gates.json",
     "tests/fixtures/opencode_run_failure_sample.jsonl",
+    "tests/fixtures/opencode_run_length_sample.jsonl",
     "tests/fixtures/opencode_run_sample.jsonl",
     "tests/fixtures/playwright/all_pass.json",
     "tests/fixtures/playwright/global_setup_crash.json",

{code_coordinator-0.5.110 → code_coordinator-0.5.112}/code_coordinator.egg-info/scm_version.json

@@ -1,7 +1,7 @@
 {
-  "tag": "0.5.110",
+  "tag": "0.5.112",
   "distance": 0,
-  "node": "g587648b558cece37b10d0ceb9906cec225d8ceab",
+  "node": "g6173265320032222560fcd77419a9f74fc98d14e",
   "dirty": false,
   "branch": "HEAD",
   "node_date": "2026-08-16"

{code_coordinator-0.5.110 → code_coordinator-0.5.112}/coord/__init__.py

@@ -124,13 +124,13 @@ def _resolve_version(names: tuple[str, ...] = CANDIDATE_NAMES) -> str:
     version literal; a release is just ``git tag vX.Y.Z && git push origin
     vX.Y.Z``.
 
-    #2103: resolves through :func:`coord.dist_name.resolve_installed` rather
-    than a single hardcoded distribution name — ``__version__`` is what
-    ``/health``'s ``"version"`` field reports, which is the *only* field
-    ``coord agent update``'s polling loop keys off of to decide a machine
-    "came back". A bare ``claude-coordinator``-only lookup would degrade to
-    ``"0+unknown"`` forever on any machine that has ``code-coordinator``
-    installed instead, faking a fleet-wide "did not come back".
+    #2103/#2106: resolves through :func:`coord.dist_name.resolve_installed`
+    rather than a hardcoded distribution name literal — ``__version__`` is
+    what ``/health``'s ``"version"`` field reports, which is the *only*
+    field ``coord agent update``'s polling loop keys off of to decide a
+    machine "came back". A hardcoded literal here would need editing at the
+    next rename and would degrade to ``"0+unknown"`` on every machine in
+    between, faking a fleet-wide "did not come back".
 
     #2010: for a wheel install that metadata is always correct — it's a
     frozen snapshot of a build that just happened. For an *editable*

{code_coordinator-0.5.110 → code_coordinator-0.5.112}/coord/agent_app.py

@@ -36,14 +36,13 @@ def _agent_pkg_spec() -> str:
     `[server]` extra — a bare upgrade would, on a fresh venv, leave the
     agent without starlette/uvicorn and dead on the next restart.
 
-    #2103: resolved tolerantly against whichever of `code-coordinator` /
-    `claude-coordinator` is currently installed, rather than the old
-    hardcoded `claude-coordinator[server]` — installing the wrong name once
-    the fleet is mid-rename either 404s against PyPI or, worse, silently
-    reinstalls the stale package. Deliberately NOT caught here: if neither
-    name resolves, the caller (`_do_update`'s existing try/except) turns
-    that into an explicit `last_update.json` failure naming both names
-    tried, instead of guessing.
+    #2103/#2106: resolved via `coord.dist_name` rather than a hardcoded
+    `claude-coordinator[server]` — installing the wrong name either 404s
+    against PyPI or, worse, silently reinstalls a stale package.
+    Deliberately NOT caught here: if the name doesn't resolve, the caller
+    (`_do_update`'s existing try/except) turns that into an explicit
+    `last_update.json` failure naming what was expected, instead of
+    guessing.
     """
     return _dist_pkg_spec(extra="server")
 
@@ -82,18 +81,18 @@ def _installed_version() -> str | None:
     process hasn't restarted since the last update" apart from "the update
     never happened".
 
-    #2103: tries `code-coordinator` then falls back to `claude-coordinator`
-    (see ``coord.dist_name``) rather than hardcoding one name — installing
-    under the name this process doesn't query used to make a fully-updated
-    agent report ``None`` here, the exact false negative behind the
-    fleet's most-recurring `✗ did not come back`.
+    #2103/#2106: resolves via ``coord.dist_name`` (see that module) rather
+    than hardcoding the distribution name — installing under a name this
+    process doesn't query used to make a fully-updated agent report
+    ``None`` here, the exact false negative behind the fleet's
+    most-recurring `✗ did not come back`.
 
     This is a *report* site, not an *act* site (contrast `_agent_pkg_spec`,
     which deliberately lets `DistributionNotFoundError` propagate): callers
     already fall back to the literal string `"unknown"` when this returns
-    `None`, so "neither name resolved" isn't silently swallowed end to end
-    — but it's still logged here, naming both names tried, rather than
-    disappearing into a bare `None` with no trace of why.
+    `None`, so a miss isn't silently swallowed end to end — but it's still
+    logged here, naming what was expected, rather than disappearing into a
+    bare `None` with no trace of why.
     """
     try:
         return resolve_installed().version
@@ -414,12 +413,11 @@ def _detect_install_mode() -> tuple[bool, str | None]:
     ``pip install -e .``).  *project_path* is the on-disk source directory for
     editable installs, or *None* for regular (site-packages) installs.
 
-    #2103: ``pip show`` needs an exact distribution name, so this resolves
-    which of `code-coordinator` / `claude-coordinator` is actually installed
-    (see ``coord.dist_name``) first rather than hardcoding one — asking
-    `pip show` for a name nothing is installed under always reports "not
-    editable", which would misreport a real editable install once the
-    fleet's mid-rename.
+    #2103/#2106: ``pip show`` needs an exact distribution name, so this
+    resolves which name is actually installed (see ``coord.dist_name``)
+    first rather than hardcoding one — asking `pip show` for a name
+    nothing is installed under always reports "not editable", which would
+    misreport a real editable install.
     """
     dist_name = resolve_installed_name()
     if dist_name is None:

{code_coordinator-0.5.110 → code_coordinator-0.5.112}/coord/agent_update.py

@@ -538,17 +538,15 @@ def _smoke_check(slot: Path, *, target_version: str | None) -> tuple[bool, str |
     mechanism :func:`_installed_version` uses) so a single subprocess call
     covers both "does it import" and "what version is this."
 
-    #2103: the version print resolves via ``coord.dist_name.resolve_installed``
-    (tries `code-coordinator` then falls back to `claude-coordinator`) rather
-    than a hardcoded ``m.version('claude-coordinator')`` — *slot* was just
-    installed from a pkg spec that itself resolved tolerantly (see
-    ``coord.agent_app._agent_pkg_spec``), so a hardcoded name here would
-    raise inside the new slot's own interpreter the moment that pkg spec
-    picked the other name, failing every smoke check fleet-wide the instant
-    the rename lands. Raising when *neither* name is installed is still the
-    right behavior here (not caught) — that means the fresh install is
-    genuinely broken, which is exactly what a failed smoke check should
-    report.
+    #2103/#2106: the version print resolves via
+    ``coord.dist_name.resolve_installed`` rather than a hardcoded
+    ``m.version('claude-coordinator')`` — *slot* was just installed from a
+    pkg spec that itself resolves via the same module (see
+    ``coord.agent_app._agent_pkg_spec``), so a name mismatch here would
+    raise inside the new slot's own interpreter for no reason. Raising when
+    the name isn't installed at all is still the right behavior here (not
+    caught) — that means the fresh install is genuinely broken, which is
+    exactly what a failed smoke check should report.
     """
     python = slot / "bin" / "python"
     coord_bin = slot / "bin" / "coord"

{code_coordinator-0.5.110 → code_coordinator-0.5.112}/coord/cli.py

@@ -255,21 +255,17 @@ def _warn_if_source_install_drift() -> None:
                 if staleness["days_behind"] is not None
                 else ""
             )
-            # #2103: suggest an upgrade of whichever distribution name is
-            # actually installed — `code-coordinator` since the #2104 rename,
-            # `claude-coordinator` on an agent that has not been updated past
-            # it yet. `_coord.__file__` is already confirmed above to be a
-            # real site-packages install, so one of the two names is
-            # guaranteed to resolve here; the literal fallback only guards a
-            # resolution race between that check and this one. It names the
-            # NEW distribution (#2104): the only way to reach it is "neither
-            # name resolved", and the one name guaranteed to still be
-            # publishable is the one every future release ships under —
-            # `claude-coordinator` is a tombstone that will never gain
-            # another version. `_dist_pkg_spec` is the module-level
-            # `coord.dist_name` import above (real module, independent of
-            # `_coord` here potentially being a test stand-in), so this
-            # doesn't depend on `coord.dist_name` already being cached.
+            # #2103/#2106: suggest an upgrade of the installed distribution
+            # name (`code-coordinator`), resolved via `coord.dist_name`
+            # rather than hardcoded. `_coord.__file__` is already confirmed
+            # above to be a real site-packages install, so resolution is
+            # guaranteed to succeed here; the literal fallback only guards a
+            # resolution race between that check and this one — the only
+            # way to reach it is "the distribution vanished between the two
+            # checks". `_dist_pkg_spec` is the module-level `coord.dist_name`
+            # import above (real module, independent of `_coord` here
+            # potentially being a test stand-in), so this doesn't depend on
+            # `coord.dist_name` already being cached.
             try:
                 install_target = _dist_pkg_spec(extra="server")
             except Exception:  # noqa: BLE001 — best-effort, never break the CLI