code-coordinator 0.5.146__tar.gz → 0.5.148__tar.gz

{code_coordinator-0.5.146 → code_coordinator-0.5.148}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: code-coordinator
-Version: 0.5.146
+Version: 0.5.148
 Summary: Coordinate Claude Code workers across multiple machines and repos.
 Author-email: John Donaghy <johnfdonaghy@gmail.com>
 License-Expression: LicenseRef-FSL-1.1-MIT
@@ -506,6 +506,8 @@ after publication.
   overnight drives.
 - [`docs/PHONE_WEBAPP.md`](docs/PHONE_WEBAPP.md) — build and serve the phone control-center PWA
   over Tailscale.
+- [`docs/ADR_COORD_WEB_DIST.md`](docs/ADR_COORD_WEB_DIST.md) — how a built `coord-web` bundle
+  reaches the daemon host, and the alternatives rejected.
 - [`docs/AGENT_OPERATIONS.md`](docs/AGENT_OPERATIONS.md) — agent install, upgrade, and
   releasing to PyPI.
 - [`docs/OPERATING_GOTCHAS.md`](docs/OPERATING_GOTCHAS.md) — traps that cost a real dispatch or

{code_coordinator-0.5.146 → code_coordinator-0.5.148}/README.md

@@ -466,6 +466,8 @@ after publication.
   overnight drives.
 - [`docs/PHONE_WEBAPP.md`](docs/PHONE_WEBAPP.md) — build and serve the phone control-center PWA
   over Tailscale.
+- [`docs/ADR_COORD_WEB_DIST.md`](docs/ADR_COORD_WEB_DIST.md) — how a built `coord-web` bundle
+  reaches the daemon host, and the alternatives rejected.
 - [`docs/AGENT_OPERATIONS.md`](docs/AGENT_OPERATIONS.md) — agent install, upgrade, and
   releasing to PyPI.
 - [`docs/OPERATING_GOTCHAS.md`](docs/OPERATING_GOTCHAS.md) — traps that cost a real dispatch or

{code_coordinator-0.5.146 → code_coordinator-0.5.148}/code_coordinator.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: code-coordinator
-Version: 0.5.146
+Version: 0.5.148
 Summary: Coordinate Claude Code workers across multiple machines and repos.
 Author-email: John Donaghy <johnfdonaghy@gmail.com>
 License-Expression: LicenseRef-FSL-1.1-MIT
@@ -506,6 +506,8 @@ after publication.
   overnight drives.
 - [`docs/PHONE_WEBAPP.md`](docs/PHONE_WEBAPP.md) — build and serve the phone control-center PWA
   over Tailscale.
+- [`docs/ADR_COORD_WEB_DIST.md`](docs/ADR_COORD_WEB_DIST.md) — how a built `coord-web` bundle
+  reaches the daemon host, and the alternatives rejected.
 - [`docs/AGENT_OPERATIONS.md`](docs/AGENT_OPERATIONS.md) — agent install, upgrade, and
   releasing to PyPI.
 - [`docs/OPERATING_GOTCHAS.md`](docs/OPERATING_GOTCHAS.md) — traps that cost a real dispatch or

{code_coordinator-0.5.146 → code_coordinator-0.5.148}/code_coordinator.egg-info/SOURCES.txt

@@ -365,6 +365,7 @@ deploy/coord-web-dist-build.timer
 deploy/coord-web-rollback.sh
 deploy/coord-web.service
 deploy/node-shim.sh
+docs/ADR_COORD_WEB_DIST.md
 docs/AGENT_OPERATIONS.md
 docs/ARCHITECTURE.md
 docs/ARCH_SECURITY_GATES.md

{code_coordinator-0.5.146 → code_coordinator-0.5.148}/code_coordinator.egg-info/scm_file_list.json

@@ -343,6 +343,7 @@
     "deploy/coord-web-rollback.sh",
     "deploy/coord-web.service",
     "deploy/node-shim.sh",
+    "docs/ADR_COORD_WEB_DIST.md",
     "docs/AGENT_OPERATIONS.md",
     "docs/ARCHITECTURE.md",
     "docs/ARCH_SECURITY_GATES.md",

{code_coordinator-0.5.146 → code_coordinator-0.5.148}/code_coordinator.egg-info/scm_version.json

@@ -1,7 +1,7 @@
 {
-  "tag": "0.5.146",
+  "tag": "0.5.148",
   "distance": 0,
-  "node": "geabea71cd1e375065c4baa33f806f7f473662f82",
+  "node": "gc274183d70afe3f92607c261ef1ba839d2fb672a",
   "dirty": false,
   "branch": "HEAD",
   "node_date": "2026-08-18"

{code_coordinator-0.5.146 → code_coordinator-0.5.148}/coord/commands/drive.py

@@ -692,12 +692,22 @@ def escalate_run(repo: str, issue: int, dismiss: bool, config_path: Path) -> Non
         "option or a drive-queue-only card; see the command's docstring."
     ),
 )
+@click.option(
+    "--list", "list_only", is_flag=True, default=False,
+    help=(
+        "Print REPO ISSUE's numbered option list (same options "
+        "`coord report run decisions`/`coord escalate list` would show for "
+        "this row) and exit — runs nothing. #2375: the discovery path the "
+        "bare/indexed invocation deliberately doesn't provide."
+    ),
+)
 @_CONFIG_OPTION
 def decide(
     repo: str,
     issue: int,
     option_index: int | None,
     dismiss: bool,
+    list_only: bool,
     config_path: Path,
 ) -> None:
     """Run one option from REPO ISSUE's `decisions` report card.
@@ -724,8 +734,16 @@ def decide(
       reappearance-or-not on the next `coord report run decisions` is the
       confirmation signal, not a second "resolved" state that could go
       stale or lie.
+
+    #2375: `--list` prints this same card's numbered options and stops —
+    the discovery path for picking OPTION_INDEX without running anything.
+    It is a NEW flag, not a change to the bare/no-index contract above:
+    that contract (#2370's own shipped acceptance criterion — no
+    OPTION_INDEX behaves identically to `coord escalate run`) stays exactly
+    as it is, since the TUI's "Recommended" click and #2370's acceptance
+    test both depend on it firing immediately.
     """
-    from coord.reports import find_decision  # noqa: PLC0415
+    from coord.reports import find_decision, format_option_cell  # noqa: PLC0415
     from coord.state import dismiss_drive_escalation  # noqa: PLC0415
 
     card = find_decision(repo, issue)
@@ -736,6 +754,12 @@ def decide(
     if not options:
         raise click.ClickException(f"decision card for {repo} #{issue} has no options")
 
+    if list_only:
+        click.echo(f"{repo} #{issue}: {len(options)} option(s)")
+        for i, opt in enumerate(options):
+            click.echo(f"  {i}: {format_option_cell(opt)}")
+        return
+
     if option_index is None:
         index = next(
             (i for i, opt in enumerate(options) if opt.get("recommended")), 0

{code_coordinator-0.5.146 → code_coordinator-0.5.148}/coord/commands/lifecycle.py

@@ -404,7 +404,7 @@ def web(
     # #1237: function-local + guarded — see _start_agent_server for why.
     with server_extra_guard("web"):
         import uvicorn
-        from coord.dashboard.server import build_app
+        from coord.dashboard.server import build_app, dist_has_bundle
         from coord.dashboard.terminal import resolve_web_token
 
     fixture = None
@@ -438,7 +438,26 @@ def web(
     app = build_app(cfg, token=token, fixture=fixture, dist_path=dist_path)
     click.echo(f"coord web: dashboard at http://{bind_host}:{bind_port}")
     if dist_path is not None:
-        click.echo(f"  serving webapp bundle from {dist_path} (#1543)")
+        # #2003: this used to unconditionally claim "serving webapp bundle
+        # from {dist_path}" even when that path was missing or empty — the
+        # server itself silently falls back to the legacy single-file
+        # dashboard in that case (build_app / index()), so the operator saw
+        # a success message for what was actually a silent regression to the
+        # legacy UI. Share the exact predicate build_app's index() route uses
+        # (dist_has_bundle) so this message can never drift from what
+        # actually gets served (#2096: two surfaces answering the same
+        # question must call the same function).
+        if dist_has_bundle(dist_path):
+            click.echo(f"  serving webapp bundle from {dist_path} (#1543)")
+        else:
+            click.echo(
+                f"  warning: --dist {dist_path} has no index.html (missing "
+                "or empty directory) — falling back to the legacy "
+                "single-file dashboard, NOT the bundle you pointed at. "
+                "Check the path / the build hook that populates it "
+                "(#2003).",
+                err=True,
+            )
     if fixture is not None:
         click.echo(
             f"  fixture mode: seeded board from {fixture_path} — reads are "

{code_coordinator-0.5.146 → code_coordinator-0.5.148}/coord/dashboard/server.py

@@ -46,6 +46,22 @@ DASHBOARD_DIR = Path(__file__).parent
 # that existing behaviour (and the test suite) is completely unaffected.
 WEBAPP_DIST = DASHBOARD_DIR / "webapp" / "dist"
 
+
+def dist_has_bundle(dist_path: Path) -> bool:
+    """Does ``dist_path`` contain a servable built webapp bundle?
+
+    This is the single definition of "valid bundle" for the dashboard: the
+    ``index()`` route below uses it to decide whether to serve the built
+    React app or fall back to the legacy single-file dashboard, and
+    ``coord web``'s CLI (coord/commands/lifecycle.py) uses it to decide
+    whether to print a success or warning message. Both call sites MUST
+    share this function rather than re-deriving the check, so the CLI's
+    message can never drift from what the server actually serves (#2003,
+    epic #2096).
+    """
+    return (dist_path / "index.html").exists()
+
+
 # How often (seconds) the background poller queries agent servers.
 _POLL_INTERVAL = 30.0
 # How long (seconds) an assignment must be running with no agent record before
@@ -698,7 +714,7 @@ def build_app(
         # Serve the built React webapp when available; fall back to the legacy
         # single-file dashboard so existing behaviour is entirely unchanged.
         spa_index = webapp_dist / "index.html"
-        html = spa_index.read_text() if spa_index.exists() else (DASHBOARD_DIR / "index.html").read_text()
+        html = spa_index.read_text() if dist_has_bundle(webapp_dist) else (DASHBOARD_DIR / "index.html").read_text()
         return HTMLResponse(html)
 
     async def api_board(request: Request) -> JSONResponse:

code_coordinator-0.5.148/docs/ADR_COORD_WEB_DIST.md

@@ -0,0 +1,158 @@
+# ADR: How a built `coord-web` bundle reaches the daemon host
+
+**Status:** Accepted
+**Date:** 2026-08-18
+**Issue:** #2004 (UX-2, Phase 1 of milestone #62, epic #2002). Blocks UX-4
+("CI must know what it publishes") and UX-7.
+
+## Context
+
+`coord/dashboard/webapp/**` is moving out of this repo into its own
+`coord-web` repo. Today, before that split, the same question already has a
+shipped answer: **[`docs/PHONE_WEBAPP.md`](PHONE_WEBAPP.md), "Going live
+automatically (#1543)."** `deploy/coord-web-dist-build.timer` fires every 10
+minutes (retuned from 1 minute by #2122; see that unit's header), fetches
+`origin/main` read-only, builds it in a dedicated worktree
+(`~/.coord-web-checkout`), health-checks the result on a scratch port before
+ever publishing it (#1560), and atomically repoints `~/coord-web-dist` —
+which `coord web --dist` serves — at the new release. A one-command rollback
+(`coord-web-rollback.sh`) with a rollback-sentinel anti-flap guard exists for
+the class of bug the health check can't see. `coord release verify` already
+has a lane for it: `webapp_bundle` (#1834 lane 5), which grades the live
+bundle's staleness against the `coord/dashboard/webapp/` source tree it
+claims to be built from — deliberately *not* against `--expected`/PyPI,
+because the bundle is versioned by `origin/main`'s SHA on its own continuous
+publish timer, decoupled on purpose from the `~/.coord-venv` release
+cadence. `webapp_build_heartbeat` (#2122) catches the timer going silently
+dead, independent of whether there's unbuilt source to expose it.
+
+The question #2004 poses is really: **once the thing that timer builds lives
+in a different repo, does any of this change in kind, or only in which
+repo(s) it points at?**
+
+## Decision
+
+**Extend the existing mechanism to track `coord-web`'s `main`, instead of
+`coord/dashboard/webapp/` inside this repo.** This is Option 1 from the
+issue, and it is not a new lane so much as a redirection of a lane this
+fleet already built, hardened, and has a release-verify check for.
+
+Concretely, once the split lands:
+
+- `coord-web-dist-build.sh`'s `BASE_CHECKOUT`/`WEBAPP_CHECKOUT` point at a
+  dedicated clone of `coord-web` (never the operator's own checkout, same
+  rule #1543 already enforces) instead of a worktree of this repo.
+- The build step becomes `npm ci && npm run build` at `coord-web`'s repo
+  root instead of `coord/dashboard/webapp/`.
+- The health-check-before-cutover, atomic symlink publish, rollback script,
+  and rollback-sentinel guard carry over **unchanged** — none of that logic
+  is specific to which repo it's building.
+- `coord.health.checks.deploy_lane_facts.resolve_webapp_source_dir` (which
+  scans `ctx.checkouts` for a directory that looks like the webapp source)
+  gets pointed at a `coord-web` checkout's layout instead of
+  `<checkout>/coord/dashboard/webapp/src`. The `webapp_bundle` check's
+  *shape* — dist mtime vs. source mtime, WARN on staleness, never a version
+  comparison — does not change; only the path it looks under does.
+- The PyPI-wheel-bundled fallback path (`coord/dashboard/webapp/dist`
+  vendored into `claude-coordinator`'s own release, #758) stays, unchanged
+  in role: it is the answer for `pip install code-coordinator` on a machine
+  with no `--dist` configured (fresh installs, CI, one-off dev boxes), not
+  the primary path to a running daemon host. This is Option 4, kept
+  deliberately as the fallback it already is today rather than promoted to
+  primary — see "Rejected alternatives" below for why it can't be primary
+  post-split.
+
+## Rejected alternatives
+
+**Option 2 — GitHub release artifact (tarball per `coord-web` release).**
+Versioned and auditable, but it reintroduces exactly the coupling #1543 was
+built to remove: a webapp fix would sit merged-but-not-live until someone
+cuts a release, and nothing today gives that step the ~10-minute, unattended
+cadence the timer already provides. It would also need the health-check
+gate and rollback machinery rebuilt around a fetch/verify/unpack step
+instead of a `git fetch` + worktree build — real new surface for no
+capability the current mechanism lacks. Revisit if `coord-web` ever needs a
+public, pinned distribution channel independent of the daemon host (it
+doesn't today).
+
+**Option 3 — npm package.** Same coupling-to-publish-cadence problem as
+Option 2, plus it adds a registry-auth and install-on-host step to a
+deploy path that currently needs neither. No requirement in this issue
+calls for the bundle to be consumable outside this fleet's own daemon host,
+which is the only scenario where an npm package would earn its cost back.
+
+**Option 4 — vendored at `claude-coordinator` release time, promoted to
+primary.** Rejected as the *primary* path because it re-couples the two
+repos' release cadences — the coupling the split (epic #2002) exists to
+remove. A `coord/dashboard/webapp/**` merge would go live only on
+`claude-coordinator`'s next PyPI release, not within ~10 minutes of merging.
+Kept as the fallback, because that's a real, already-solved problem
+(bootstrapping a `--dist`-less host, or a fresh install) distinct from
+"how does a live daemon host stay current," and downgrading it doesn't cost
+anything the fleet needs today.
+
+**Why Option 1 is not "a fifth silent lane."** The issue's core objection —
+this fleet already has four deploy lanes that go stale with no signal
+(agent venv, `coord-serve`, local `cargo build`, `~/.coord-cli-venv`) — is
+real, but those four go stale because going live requires an *operator* to
+re-run an install step (`pip install --upgrade`, `cargo build`) and nothing
+polls to catch it if they don't. The webapp-dist lane is structurally
+different: it already has (a) an autonomous timer instead of an
+operator-triggered pull, (b) a pre-cutover health check that refuses to
+publish a broken build in the first place, (c) a heartbeat file
+`coord health`/`coord release verify` already read to distinguish "up to
+date" from "the trigger died silently," and (d) a release-verify lane
+(`webapp_bundle`) already wired into the fleet health surface. Extending it
+to a second repo carries all four properties across unchanged — it doesn't
+have to invent them the way a from-scratch Option 2/3 pipeline would.
+
+## Staleness across the split is a different question than staleness today
+
+Pre-split, `coord-web-dist-build.timer` and `~/.coord-venv` build off the
+*same* repo, so "is the live bundle SHA an ancestor of what the daemon was
+built from" is at least answerable in principle. Post-split, `coord-serve`
+(from `claude-coordinator`, versioned by PyPI release) and the webapp bundle
+(from `coord-web`, versioned by its own `main` SHA) are two independently
+released artifacts with **no shared version number** — and per the
+`webapp_bundle` design already in `release_verify.py`, that's intentional:
+grading the bundle against `--expected`/PyPI would "manufacture permanent,
+meaningless skew rather than report a real one." That reasoning holds even
+harder once the source repos are different.
+
+What that does *not* cover, and what genuinely is new here: a phone hitting
+`http://dellserver:7434` can land on a `coord-web` bundle that expects an
+API shape `coord-serve` hasn't shipped yet (or vice versa), because nothing
+before this ADR pins a compatibility floor between the two repos'
+independent cadences. This is a real risk the split introduces — it isn't
+solved by choosing Option 1 over 2/3/4, and it isn't this ADR's job to
+solve, but it should be named so UX-4/UX-7 pick it up rather than
+rediscover it: the daemon already reports its own version
+(`coord/dashboard/server.py`'s `version=__version__`); the cheapest fix is
+likely a minimum-compatible-API marker the webapp checks against that value
+at load and degrades visibly (banner, not a silent break) on mismatch,
+rather than trying to keep the two repos' releases in lockstep.
+
+Propagation lag itself (a phone briefly on a bundle one merge behind the
+daemon, or vice versa) is not new and not a defect — it's the same ~10-minute
+window the timer already runs at for the single-repo case (retuned from the
+original 1-minute cadence #1543 documents; see #2122 and
+`deploy/coord-web-dist-build.timer`'s header for why). It stays detectable
+the same way: the release directory is named after the
+`coord-web` SHA it was built from, and `webapp_build_heartbeat` proves the
+timer is still alive.
+
+## Consequences
+
+- `coord release verify`'s `webapp_bundle` lane keeps working post-split
+  with a path/repo-target change, not a redesign — satisfying this issue's
+  "whichever option wins should be assertable by it" requirement at close
+  to zero incremental cost.
+- The daemon host needs a second dedicated checkout (`coord-web`, alongside
+  whatever `claude-coordinator` checkout it already keeps for other lanes)
+  and a second instance of the build-timer/rollback pairing pointed at it.
+  That's real setup work, tracked under UX-4/UX-7, not a design question.
+- A `coord-web`↔`coord-serve` compatibility floor is an explicitly named
+  open follow-up, not solved here.
+- Options 2 and 3 remain available to revisit if `coord-web` ever needs a
+  distribution channel independent of this fleet's own daemon host — no
+  requirement in scope today calls for that.

{code_coordinator-0.5.146 → code_coordinator-0.5.148}/docs/PHONE_WEBAPP.md

@@ -126,6 +126,12 @@ cd coord/dashboard/webapp && npm run build
 
 ---
 
+> **Repo split (#2004):** `coord/dashboard/webapp/**` is moving to its own
+> `coord-web` repo (epic #2002). The mechanism below is the answer for how a
+> built bundle reaches this daemon host both before and after that move —
+> see [`docs/ADR_COORD_WEB_DIST.md`](ADR_COORD_WEB_DIST.md) for the decision
+> and the rejected alternatives.
+
 ## Going live automatically (#1543): merged main, not release cadence
 
 **On dellserver in production, a merged `coord/dashboard/webapp/**` change

{code_coordinator-0.5.146 → code_coordinator-0.5.148}/tests/test_cli_decide.py

@@ -206,6 +206,78 @@ def test_source2_card_explicit_index_runs_that_option_and_never_touches_escalati
     assert state._get_drive_escalation_local("api", 55) is None
 
 
+# ── --list: discovery path, executes nothing (#2375) ────────────────────────
+
+
+def test_list_prints_numbered_options_and_runs_nothing_for_escalation_card(
+    coord_db, valid_config_path: Path, monkeypatch
+):
+    state._record_drive_escalation_local(
+        "api", 7, stage="merge", reason="stuck", gate_readings="",
+        proposed_command="echo hi",
+    )
+    seen: dict = {}
+    monkeypatch.setattr("coord.commands.drive.subprocess.run", _fake_run(seen))
+
+    result = CliRunner().invoke(
+        main, ["decide", "api", "7", "--list", "--config", str(valid_config_path)]
+    )
+    assert result.exit_code == 0, result.output
+    assert "command" not in seen
+    assert "0:" in result.output and "Recommended: echo hi" in result.output
+    assert "1:" in result.output and "Inspect: coord escalate list --repo api" in result.output
+    # nothing dismissed either — --list never touches state
+    assert state._get_drive_escalation_local("api", 7) is not None
+
+
+def test_list_prints_numbered_options_for_source2_card(
+    coord_db, valid_config_path: Path, monkeypatch
+):
+    _seed_blocked_queue_row("api", 55, _TWO_OPTION_REASON)
+    seen: dict = {}
+    monkeypatch.setattr("coord.commands.drive.subprocess.run", _fake_run(seen))
+
+    result = CliRunner().invoke(
+        main, ["decide", "api", "55", "--list", "--config", str(valid_config_path)]
+    )
+    assert result.exit_code == 0, result.output
+    assert "command" not in seen
+    assert "coord log aid-1 --machine dellserver" in result.output
+    assert "echo remedy-command" in result.output
+
+
+def test_list_matches_the_decisions_report_options_exactly(
+    coord_db, valid_config_path: Path
+):
+    """#2375 acceptance: `--list`'s numbered options are the same ones
+    `coord report run decisions` (and thus `format_option_cell`) would show
+    for this same card, byte-for-byte."""
+    _seed_blocked_queue_row("api", 55, _TWO_OPTION_REASON)
+
+    result = CliRunner().invoke(
+        main, ["decide", "api", "55", "--list", "--config", str(valid_config_path)]
+    )
+    assert result.exit_code == 0, result.output
+
+    from coord.reports import format_option_cell
+
+    report = run_decisions(repo="api")
+    card = next(r for r in report.rows if r["issue"] == 55)
+    for i, opt in enumerate(card["options"]):
+        assert f"  {i}: {format_option_cell(opt)}" in result.output
+
+
+def test_list_with_no_decision_on_file_is_a_clean_error(
+    coord_db, valid_config_path: Path
+):
+    result = CliRunner().invoke(
+        main, ["decide", "api", "7", "--list", "--config", str(valid_config_path)]
+    )
+    assert result.exit_code != 0
+    assert "no decision on file" in result.output
+    assert "Traceback" not in result.output
+
+
 def test_executed_command_is_byte_identical_to_the_decisions_report_option(
     coord_db, valid_config_path: Path, monkeypatch
 ):