code-coordinator 0.5.185__tar.gz → 0.5.187__tar.gz

{code_coordinator-0.5.185 → code_coordinator-0.5.187}/PKG-INFO

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

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: code-coordinator
-Version: 0.5.185
+Version: 0.5.187
 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.185 → code_coordinator-0.5.187}/code_coordinator.egg-info/scm_version.json

@@ -1,7 +1,7 @@
 {
-  "tag": "0.5.185",
+  "tag": "0.5.187",
   "distance": 0,
-  "node": "g2d150e839b7920ff70d6be0f4983503f6a092831",
+  "node": "gc74dfc5a8d399b33526076eaec24aed5d5ad1ce3",
   "dirty": false,
   "branch": "HEAD",
   "node_date": "2026-08-20"

{code_coordinator-0.5.185 → code_coordinator-0.5.187}/coord/commands/merge.py

@@ -456,7 +456,9 @@ def _dispatch_conflict_fixes(events, config, *, dry_run: bool) -> None:
             # failed for this entry in this session, don't loop — mark
             # HUMAN_REQUIRED so the user takes over.  A successful
             # prior fix does not trigger this guard (#784).
-            if has_prior_conflict_fix(fix_board, ev.entry.assignment_id):
+            if has_prior_conflict_fix(
+                fix_board, ev.entry.assignment_id, current_error=ev.entry.error,
+            ):
                 ev.entry.state = HUMAN_REQUIRED
                 click.echo(
                     f"  {ev.entry.repo_name} #{ev.entry.issue_number}: "

{code_coordinator-0.5.185 → code_coordinator-0.5.187}/coord/config.py

@@ -1617,11 +1617,15 @@ class HealthConfig:
     # None → ~/coord-web-dist — the symlink `deploy/coord-web-dist-build.timer`
     # atomically repoints at each new release (#1543).
     webapp_dist_path: str | None = None
-    # Directory holding the coord/dashboard/webapp/ sources the bundle was
-    # built from.  None → `<checkout>/coord/dashboard/webapp/src` for the
-    # first configured local checkout that has one.  Same `src/`-not-root
-    # reasoning as `tui_source_dir`: rooting at the webapp package root would
-    # sweep `node_modules`/`dist` were they not already skipped by name.
+    # Directory holding the `coord-web` sources the bundle was built from
+    # (#2470; before epic #2002 split the webapp out into its own repo, this
+    # was `coord/dashboard/webapp/` inside THIS repo).  None → `<checkout>/src`
+    # for this machine's `coord-web` checkout, discovered the same way
+    # `coord_web_checkout` is (see
+    # `coord.health.checks.coord_web_ci_pin.resolve_coord_web_checkout`).
+    # Same `src/`-not-root reasoning as `tui_source_dir`: rooting at the
+    # webapp package root would sweep `node_modules`/`dist` were they not
+    # already skipped by name.
     webapp_source_dir: str | None = None
     # Absolute path to the heartbeat coord-web-dist-build.sh writes on EVERY
     # invocation, whether or not there was anything to build (#2122). None →

{code_coordinator-0.5.185 → code_coordinator-0.5.187}/coord/conflict_fix.py

@@ -367,7 +367,32 @@ def _has_active_conflict_fix(board: Board, merge_entry_id: str | None) -> bool:
     )
 
 
-def has_prior_conflict_fix(board: Board, merge_entry_id: str | None) -> bool:
+def _dispatched_error(assignment: Assignment) -> str | None:
+    """The merge-failure text *assignment*'s briefing was built from.
+
+    ``build_conflict_fix_briefing``/``build_semantic_conflict_briefing``
+    both embed the triggering ``QueuedMerge.error`` verbatim (as a
+    ``"Reason: …"``/``"Last merge error: …"`` line) — that's the only durable
+    record of what the merge looked like *at dispatch time*, since
+    ``on_conflict_fix_done`` clears ``entry.error`` back to ``None`` on
+    success before the merge is retried. Returns ``None`` when the briefing
+    doesn't carry either marker (e.g. a hand-built test ``Assignment``).
+    """
+    briefing = assignment.briefing or ""
+    for line in briefing.splitlines():
+        if line.startswith("Reason: "):
+            return line[len("Reason: "):]
+        if line.startswith("Last merge error: "):
+            return line[len("Last merge error: "):]
+    return None
+
+
+def has_prior_conflict_fix(
+    board: Board,
+    merge_entry_id: str | None,
+    *,
+    current_error: str | None = None,
+) -> bool:
     """True when a second conflict-fix dispatch for *merge_entry_id* is blocked.
 
     Blocks when a conflict-fix is **active** (running/pending — don't spawn a
@@ -379,6 +404,18 @@ def has_prior_conflict_fix(board: Board, merge_entry_id: str | None) -> bool:
     followed by a new conflict if other PRs merged in the meantime; that is a
     fresh situation and warrants a fresh fix attempt.  Only actual failures
     consume the one-per-entry cap.
+
+    #2475: that "successful" carve-out assumed a ``done`` conflict-fix always
+    resolved *something*. It doesn't when the merge was never blocked by a
+    content conflict in the first place (e.g. a permanently-unmergeable
+    branch-protection state) — the worker finds nothing to rebase, exits
+    ``done``, and the merge queue retries into the *identical* failure
+    forever (#2009's 38-turn thrash). When *current_error* is given and a
+    prior ``done`` conflict-fix's dispatch-time error
+    (:func:`_dispatched_error`) matches it exactly, that's the same blocker
+    recurring unchanged — not a fresh conflict — so it now consumes the cap
+    too. Callers that don't pass *current_error* keep the pre-#2475 behaviour
+    (``done`` never blocks) since they have no error text to compare.
     """
     if merge_entry_id is None:
         return False
@@ -393,9 +430,16 @@ def has_prior_conflict_fix(board: Board, merge_entry_id: str | None) -> bool:
         # Genuine failure — retry cap consumed, surface to human.
         if a.status in ("failed", "advisory"):
             return True
-        # "done" = successful rebase → cap not consumed; a re-conflict is new.
-        # "cancelled" falls through here too — a cancelled attempt did no work,
-        # so it is treated the same as "done": re-dispatch is allowed.
+        if a.status == "done":
+            if current_error is not None and _dispatched_error(a) == current_error:
+                # Same failure text recurring after a "successful" fix means
+                # nothing was actually fixed — treat like a genuine failure.
+                return True
+            # Otherwise: successful rebase, different (or unknown) situation
+            # now → cap not consumed; a re-conflict is new.
+        # "cancelled" falls through here too — a cancelled attempt did no
+        # work, so it is treated the same as an unrelated "done": re-dispatch
+        # is allowed.
     return False
 
 
@@ -463,7 +507,10 @@ def dispatch_conflict_fix(
     the caller marks the entry ``HUMAN_REQUIRED``.  A ``done`` (successful)
     conflict-fix does *not* block a new dispatch — a successful rebase can be
     followed by a fresh conflict if other PRs merged in the meantime, and that
-    warrants a new attempt rather than an immediate human escalation (#784).
+    warrants a new attempt rather than an immediate human escalation (#784) —
+    UNLESS (#2475) *entry.error* is identical to the error the prior ``done``
+    attempt was dispatched for, which means the merge failed the same way
+    again with nothing actually fixed; see :func:`has_prior_conflict_fix`.
 
     ``semantic=True`` (#1291) dispatches the escalated second attempt: a
     different, less prescriptive briefing (see
@@ -481,7 +528,9 @@ def dispatch_conflict_fix(
             return None
         if _has_active_conflict_fix(board, entry.assignment_id):
             return None
-    elif has_prior_conflict_fix(board, entry.assignment_id):
+    elif has_prior_conflict_fix(
+        board, entry.assignment_id, current_error=entry.error,
+    ):
         return None
 
     repo = config.repo(entry.repo_name)

{code_coordinator-0.5.185 → code_coordinator-0.5.187}/coord/deploy/coord-web-dist-build.service

@@ -4,13 +4,14 @@
 #
 # A systemd *user* unit, Type=oneshot, mirroring coord-drive-queue.service's
 # tick pattern (timer-fired, its own flock so a slow run can't stack).  Runs
-# deploy/coord-web-dist-build.sh, which:
+# deploy/coord-web-dist-build.sh, which (#2470: tracks the dedicated
+# `coord-web` repo, not `coord/dashboard/webapp/` inside THIS repo — see
+# docs/ADR_COORD_WEB_DIST.md; #2009: that used to be ~/src/code-coordinator,
+# back when the webapp was a subdirectory of this repo):
 #   - fetches origin/main into ~/src/coord-web (read-only — only
 #     `git fetch` + `rev-parse`, never touches that checkout's working tree
-#     or whatever branch an operator has it parked on). #2009: that used
-#     to be ~/src/code-coordinator, back when the webapp was a
-#     subdirectory of this repo,
-#   - builds that repo's ROOT at that SHA inside a DEDICATED worktree
+#     or whatever branch an operator has it parked on),
+#   - builds coord-web's repo root from that SHA inside a DEDICATED worktree
 #     (~/.coord-web-checkout, never shared with an operator or `coord drive`),
 #   - atomically repoints ~/coord-web-dist at the new build.
 #

{code_coordinator-0.5.185 → code_coordinator-0.5.187}/coord/deploy/coord-web-dist-build.timer

@@ -48,6 +48,18 @@
 # overlap the flock, in which case the next fire simply retries 10 minutes
 # later.
 #
+# #2470: this unit now tracks the dedicated `coord-web` repo's `main`
+# (deploy/coord-web-dist-build.sh's BASE_CHECKOUT/WEBAPP_CHECKOUT), not
+# `coord/dashboard/webapp/` inside THIS repo (docs/ADR_COORD_WEB_DIST.md).
+# The cadence measurement above predates that split and was taken against
+# this repo's merge history; it stays the right order-of-magnitude
+# justification for 10 minutes because `coord-web`, being a repo dedicated
+# entirely to the webapp, has EVERY merge to its `main` in-scope for a build
+# — there is no "does this commit touch webapp/ at all" filtering to do
+# anymore (the script never filtered by path either; it always rebuilt on
+# any `origin/main` SHA change, webapp-only or not — this just makes that
+# now-trivially-true for the repo it targets).
+#
 # Install: see deploy/coord-web-dist-build.sh's header, or
 # docs/PHONE_WEBAPP.md / docs/AGENT_OPERATIONS.md.
 

{code_coordinator-0.5.185 → code_coordinator-0.5.187}/coord/health/checks/deploy_lane_facts.py

@@ -38,10 +38,14 @@ wheel's version the way ``agent_venv``/``spawned_coord`` are —
 ``~/.coord-venv`` release cadence, so "is it on the released version?" is
 not a well-formed question for it. What *is* well-formed, and what this
 checks — mirroring ``tui_binary`` exactly — is whether the live bundle is
-older than the webapp source tree it claims to have been built from. Since
-#2009 (epic #2002) that source tree is a ``coord-web`` checkout rather than
-this repo's ``coord/dashboard/webapp/``; see
-:func:`resolve_webapp_source_dir` for how both layouts are located.
+older than the source tree it claims to have been built from: the
+`coord-web` repo's own checkout (#2470; retargeted from this repo's now-gone
+``coord/dashboard/webapp/`` once the webapp moved out under epic #2002 —
+see :func:`resolve_webapp_source_dir`, which shares its checkout-discovery
+convention with ``coord.health.checks.coord_web_ci_pin`` so the two checks
+can never disagree about which local checkout *is* `coord-web`, with a
+fallback to the pre-#2009 in-repo layout for a checkout still parked on a
+pre-split commit).
 """
 
 from __future__ import annotations
@@ -50,6 +54,7 @@ import subprocess
 
 from coord.dist_name import CANDIDATE_NAMES
 from coord.health.checks.agent_install import pip_show
+from coord.health.checks.coord_web_ci_pin import resolve_coord_web_checkout
 from coord.health.models import CheckResult, HealthContext, Severity
 from coord.health.registry import check
 from coord.health.units import expand, shorten_path
@@ -142,31 +147,30 @@ def resolve_webapp_build_heartbeat_path(ctx: HealthContext):
 def resolve_webapp_source_dir(ctx: HealthContext):
     """The webapp source tree in the first local checkout that has one.
 
-    Same convention as :func:`resolve_tui_source_dir`. Two layouts are
-    recognised, in this order:
-
-    1. ``<checkout>/src`` — a ``coord-web`` checkout, whose repo ROOT is the
-       webapp root (#2009, epic #2002). Gated on a sibling ``package.json``
-       so an unrelated repo that merely happens to have a top-level ``src/``
-       (any Rust or src-layout Python project in ``ctx.checkouts``) cannot be
-       mistaken for the webapp — grading the live bundle against the WRONG
-       tree would manufacture staleness rather than report it, which is the
-       exact failure ``resolve_tui_source_dir`` refuses to risk by not
-       guessing relative to the binary path.
-    2. ``<checkout>/coord/dashboard/webapp/src`` — the pre-#2009 in-repo
-       layout. Kept because a machine can legitimately still have an older
-       ``claude-coordinator`` checkout parked on a pre-split commit, and this
-       lane reporting UNKNOWN there would be a regression in signal for no
-       gain. It can only ever match a tree that genuinely is webapp source.
+    Prefers a `coord-web` checkout (#2470), discovered via
+    :func:`coord.health.checks.coord_web_ci_pin.resolve_coord_web_checkout`
+    — the same "checkout named ``coord-web``, else one carrying
+    ``playwright.acceptance.config.ts`` at its root" discovery that check
+    already uses — so `webapp_bundle` and `coord_web_ci_pin` can never
+    disagree about which local checkout is `coord-web`. That checkout's
+    ``src/`` is the webapp root (#2009, epic #2002).
+
+    Falls back to ``<checkout>/coord/dashboard/webapp/src`` — the pre-#2009
+    in-repo layout. Kept because a machine can legitimately still have an
+    older ``claude-coordinator`` checkout parked on a pre-split commit, and
+    this lane reporting UNKNOWN there would be a regression in signal for no
+    gain. Configured ``health.webapp_source_dir`` still wins outright, same
+    convention as every other path in this module.
     """
     configured = getattr(ctx.thresholds, "webapp_source_dir", None)
     if configured:
         return expand(configured, ctx.home)
+    checkout = resolve_coord_web_checkout(ctx)
+    if checkout is not None:
+        candidate = checkout / "src"
+        if candidate.is_dir():
+            return candidate
     for checkout in ctx.checkouts:
-        if (checkout.path / "package.json").is_file():
-            candidate = checkout.path / "src"
-            if candidate.is_dir():
-                return candidate
         candidate = checkout.path / "coord" / "dashboard" / "webapp" / "src"
         if candidate.is_dir():
             return candidate

{code_coordinator-0.5.185 → code_coordinator-0.5.187}/coord/health/checks/fleet_deploy_lanes.py

@@ -351,8 +351,8 @@ def probe_tui_binary(ctx: HealthContext) -> CheckResult:
     order=13,
     description=(
         "The dist/ bundle `coord web --dist` serves is not older than the "
-        "coord/dashboard/webapp/ source tree it was supposedly built from, "
-        "on every machine that has one (#1834 lane 5)."
+        "`coord-web` source tree it was supposedly built from, "
+        "on every machine that has one (#1834 lane 5, #2470)."
     ),
 )
 def probe_webapp_bundle(ctx: HealthContext) -> CheckResult:

{code_coordinator-0.5.185 → code_coordinator-0.5.187}/coord/merge_queue.py

@@ -93,6 +93,18 @@ _HUMAN_SIGNALS = (
     "permission",
     "protected branch",
     "branch protection",
+    # #2475: GitHub's wording when a required status check can never report
+    # — e.g. its source CI job was deleted from the workflow while the
+    # check was still required in branch protection. This is a *permanent*
+    # block; no rebase or content change fixes it. The full message is
+    # something like "Pull request X is not mergeable: the base branch
+    # policy prohibits the merge.", which also contains "not mergeable" —
+    # a _REBASEABLE_SIGNALS entry — so without this specific phrase here,
+    # classify_conflict fell through past _HUMAN_SIGNALS (no match) to
+    # _REBASEABLE_SIGNALS's generic "not mergeable" match and misclassified
+    # the failure as "rebaseable", dispatching a conflict-fix worker that
+    # could never succeed (#2009's 38-turn thrash).
+    "policy prohibits the merge",
 )
 
 

{code_coordinator-0.5.185 → code_coordinator-0.5.187}/coord/notify.py

@@ -884,7 +884,11 @@ def detect_stalled_pipeline(
             elif (
                 matching_entry.state == CONFLICT
                 and classify_conflict(matching_entry.error) == "rebaseable"
-                and not has_prior_conflict_fix(board, matching_entry.assignment_id)
+                and not has_prior_conflict_fix(
+                    board,
+                    matching_entry.assignment_id,
+                    current_error=matching_entry.error,
+                )
             ):
                 # #1478: a rebaseable CONFLICT with no active/failed
                 # conflict-fix attempt — the #1474 classify-and-dispatch step
@@ -1412,7 +1416,9 @@ def dispatch_stalled_pipeline_action(
             return StalledDispatchAction(
                 kind="no_action", detail="merge queue entry no longer found",
             )
-        if has_prior_conflict_fix(board, entry.assignment_id):
+        if has_prior_conflict_fix(
+            board, entry.assignment_id, current_error=entry.error,
+        ):
             return StalledDispatchAction(
                 kind="skipped_human_required",
                 detail="conflict-fix already active or its retry cap was already hit",

{code_coordinator-0.5.185 → code_coordinator-0.5.187}/coord/release_verify.py

@@ -395,7 +395,7 @@ def findings_for_host(host: str, health: dict | None) -> list[Finding]:
                 )
             )
 
-    # ── webapp bundle vs coord/dashboard/webapp/ source (#1834 lane 5) ───
+    # ── webapp bundle vs coord-web's own source tree (#1834 lane 5, #2470) ─
     # Deliberately not a Lane/version comparison — see release_verify.py's
     # module docstring and coord.health.checks.fleet_deploy_lanes: the
     # bundle is versioned by origin/main's SHA on a continuous publish

{code_coordinator-0.5.185 → code_coordinator-0.5.187}/deploy/coord-web-dist-build.service

@@ -4,13 +4,14 @@
 #
 # A systemd *user* unit, Type=oneshot, mirroring coord-drive-queue.service's
 # tick pattern (timer-fired, its own flock so a slow run can't stack).  Runs
-# deploy/coord-web-dist-build.sh, which:
+# deploy/coord-web-dist-build.sh, which (#2470: tracks the dedicated
+# `coord-web` repo, not `coord/dashboard/webapp/` inside THIS repo — see
+# docs/ADR_COORD_WEB_DIST.md; #2009: that used to be ~/src/code-coordinator,
+# back when the webapp was a subdirectory of this repo):
 #   - fetches origin/main into ~/src/coord-web (read-only — only
 #     `git fetch` + `rev-parse`, never touches that checkout's working tree
-#     or whatever branch an operator has it parked on). #2009: that used
-#     to be ~/src/code-coordinator, back when the webapp was a
-#     subdirectory of this repo,
-#   - builds that repo's ROOT at that SHA inside a DEDICATED worktree
+#     or whatever branch an operator has it parked on),
+#   - builds coord-web's repo root from that SHA inside a DEDICATED worktree
 #     (~/.coord-web-checkout, never shared with an operator or `coord drive`),
 #   - atomically repoints ~/coord-web-dist at the new build.
 #

{code_coordinator-0.5.185 → code_coordinator-0.5.187}/deploy/coord-web-dist-build.sh

@@ -1,19 +1,26 @@
 #!/usr/bin/env bash
 #
-# coord-web-dist-build.sh — build the `coord-web` webapp from its merged
-# `main` into a directory `coord web --dist` serves, WITHOUT touching
-# ~/.coord-venv (#1543).
+# coord-web-dist-build.sh — build the React webapp from the `coord-web`
+# repo's merged `main` into a directory `coord web --dist` serves, WITHOUT
+# touching ~/.coord-venv (#1543; retargeted at `coord-web` by #2470 once the
+# webapp moved out of THIS repo into its own, epic #2002 — see
+# docs/ADR_COORD_WEB_DIST.md for the decision. Before #2470 this built
+# `coord/dashboard/webapp` out of a `claude-coordinator` checkout; the
+# mechanism below is otherwise unchanged, only which repo it points at).
 #
 # Why this exists: coord-web, coord-agent and coord-serve all `ExecStart`
 # from the SAME ~/.coord-venv, so "ship a webapp change" used to mean
 # `pip install --upgrade code-coordinator` on that venv — which also
 # upgrades the board daemon and the agent runtime on that host, and
 # `coord agent update` is already known to kill running headless workers
-# (see the #1543 issue body). This script decouples the two: it keeps an
-# independent worktree of the webapp's repo, builds it from merged main into
-# a fresh release directory named after the SHA, and atomically repoints a
-# symlink at it. `coord web --dist ~/coord-web-dist` (see
-# deploy/coord-web.service) always points at that symlink.
+# (see the #1543 issue body). This script decouples the two: it keeps a
+# DEDICATED clone of the `coord-web` repo (never an operator's own
+# `~/src/coord-web` dev checkout's working tree — same "never the checkout
+# someone else is using" rule this script has always applied to the repo it
+# builds from), builds it from merged main into a fresh, timestamped release
+# directory, and atomically repoints a symlink at it. `coord web --dist
+# ~/coord-web-dist` (see deploy/coord-web.service) always points at that
+# symlink.
 #
 # #2009 (epic #2002) — WHICH repo this builds changed, nothing else did.
 # Until the split, `$BASE_CHECKOUT` was a checkout of *claude-coordinator*
@@ -28,11 +35,12 @@
 # file (#2122) all carry over untouched, because none of them ever depended
 # on which repo the source came from.
 #
-# ONE thing does still come from claude-coordinator: the health check boots a
-# real `coord web --fixture` and needs that repo's board fixture JSON, which
-# `coord-web` has no copy of. `$COORD_CHECKOUT` (default
-# `$SRC_ROOT/code-coordinator`) is where it is read from — set
-# `$HEALTH_CHECK_FIXTURE` directly on a host that keeps no such checkout.
+# The health check boots a real `coord web --fixture` and needs a board
+# fixture JSON for it — `coord-web` vendored its own copy of the one
+# `e2e/fixtureServer.ts` already uses (post-#2005 split, commit 7e0bf5b), so
+# this reads `$WEBAPP_CHECKOUT/e2e/fixtures/board-pipeline-basic.json` and
+# has no dependency on a claude-coordinator checkout being present. Set
+# `$HEALTH_CHECK_FIXTURE` directly to override.
 #
 # NO RESTART of coord-web is required after the first build. Starlette's
 # StaticFiles/FileResponse re-resolve the directory on every request (see
@@ -45,14 +53,21 @@
 # once, THEN start/enable coord-web.
 #
 # Safe to run unattended on a timer (see coord-web-dist-build.timer): it
-# never touches ~/.coord-venv, ~/src/coord-web's own checkout (it
-# uses a DEDICATED `git worktree`, so it can't collide with whatever branch
-# an operator has that checkout parked on — same reasoning as `coord drive`'s
-# worktree isolation), or any running coord-agent/coord-serve/coord-web
-# process. A `flock` guards against overlapping runs; a same-SHA re-run is a
-# fast no-op.
+# never touches ~/.coord-venv or $BASE_CHECKOUT's working tree (only
+# `git fetch`/`rev-parse` run there — the actual build happens in a
+# SEPARATE, DEDICATED `git worktree`, $WEBAPP_CHECKOUT, so it can't collide
+# with whatever branch an operator has $BASE_CHECKOUT parked on — same
+# reasoning as `coord drive`'s worktree isolation), or any running
+# coord-agent/coord-serve/coord-web process. A `flock` guards against
+# overlapping runs; a same-SHA re-run is a fast no-op.
 #
-# Install:
+# Install: $BASE_CHECKOUT (default ~/src/coord-web) must be a real, already-
+# cloned `coord-web` checkout before the first run — this script only
+# fetches/rev-parses/worktrees off it, it never `git clone`s one into
+# existence. Use a checkout dedicated to this deploy lane if the operator
+# also keeps their own `coord-web` dev checkout elsewhere on this box.
+#
+#   git clone <coord-web-remote> ~/src/coord-web   # one-time, if not already there
 #   cp deploy/coord-web-dist-build.sh ~/.local/bin/   # or run in place
 #   chmod +x ~/.local/bin/coord-web-dist-build.sh
 #   ~/.local/bin/coord-web-dist-build.sh               # first build, before
@@ -116,6 +131,12 @@
 
 set -uo pipefail
 
+# #2470: tracks the `coord-web` repo's main, not this repo's — see the
+# header. $BASE_CHECKOUT is read-only from this script's point of view (only
+# `git fetch`/`rev-parse`/`worktree add` ever touch it, never `checkout`), so
+# an operator's own `coord-web` dev checkout at the default path is safe in
+# principle, but a checkout dedicated to this deploy lane is still the
+# documented install step — see the header's "Install" section.
 SRC_ROOT="${SRC_ROOT:-$HOME/src}"
 # #2009: the webapp's repo, not claude-coordinator's. See the header.
 REPO_NAME="${REPO_NAME:-coord-web}"
@@ -126,10 +147,6 @@ BRANCH="${BRANCH:-main}"
 # hard-coded `coord/dashboard/webapp`, and stays configurable so a future
 # monorepo layout needs an env var rather than an edit here.
 WEBAPP_SUBDIR="${WEBAPP_SUBDIR:-}"
-# claude-coordinator's checkout — needed ONLY for the health-check fixture
-# below, which lives in that repo's tests/fixtures/ and has no coord-web
-# equivalent. Not fetched, not built, not written to.
-COORD_CHECKOUT="${COORD_CHECKOUT:-$SRC_ROOT/code-coordinator}"
 
 # A worktree DEDICATED to this script — never the same directory an operator
 # or `coord drive` worktree might be using, and never checked out over a
@@ -168,9 +185,20 @@ HEALTH_CHECK_PORT="${HEALTH_CHECK_PORT:-18434}"
 HEALTH_CHECK_TIMEOUT_SECS="${HEALTH_CHECK_TIMEOUT_SECS:-20}"
 # The reference seeded board (#1538) — deterministic, no DB/fleet/network, so
 # the scratch instance below never touches ~/.coord/coord.db or races the
-# real coord-web/coord-serve/coord-agent processes. Defaults to the fixture
-# AT THE SHA BEING DEPLOYED (via $WEBAPP_CHECKOUT), so the fixture schema
-# always matches the server code that will parse it.
+# real coord-web/coord-serve/coord-agent processes. Defaults to the copy
+# checked into $WEBAPP_CHECKOUT (the `coord-web` SHA being deployed) at
+# `e2e/fixtures/board-pipeline-basic.json` — that is where the fixture
+# actually lives in the `coord-web` repo (`git ls-tree -r --name-only
+# origin/main` has no `tests/` directory at all post-split). NOTE:
+# `coord-web`'s own `playwright.acceptance.config.ts` still has a stale
+# `DEFAULT_FIXTURE` pointing at the old `tests/fixtures/...` path (a
+# leftover `REPO_ROOT` miscalculation from before the repo split — see
+# docs/ADR_COORD_WEB_DIST.md) so do NOT use that config as the source of
+# truth for this path; this comment documents the real, verified location
+# instead (#2470). This is never a claim that the fixture matches the
+# INSTALLED `coord`'s server code, which post-#2002-split is versioned
+# independently (see docs/ADR_COORD_WEB_DIST.md, "Staleness across the
+# split").
 HEALTH_CHECK_FIXTURE="${HEALTH_CHECK_FIXTURE:-}"
 
 say() { echo "[$(date -Is)] $*" >&2; }
@@ -220,9 +248,7 @@ health_check_release() {
     return 1
   fi
 
-  # #2009: read from claude-coordinator's checkout, not $WEBAPP_CHECKOUT —
-  # the fixture is a coord *board* fixture and never moved to coord-web.
-  fixture="${HEALTH_CHECK_FIXTURE:-$COORD_CHECKOUT/tests/fixtures/board-pipeline-basic.json}"
+  fixture="${HEALTH_CHECK_FIXTURE:-$WEBAPP_CHECKOUT/e2e/fixtures/board-pipeline-basic.json}"
   if [[ ! -f "$fixture" ]]; then
     say "ERROR: health-check fixture missing: $fixture — cannot health-check $release_dir"
     return 1

{code_coordinator-0.5.185 → code_coordinator-0.5.187}/deploy/coord-web-dist-build.timer

@@ -48,6 +48,18 @@
 # overlap the flock, in which case the next fire simply retries 10 minutes
 # later.
 #
+# #2470: this unit now tracks the dedicated `coord-web` repo's `main`
+# (deploy/coord-web-dist-build.sh's BASE_CHECKOUT/WEBAPP_CHECKOUT), not
+# `coord/dashboard/webapp/` inside THIS repo (docs/ADR_COORD_WEB_DIST.md).
+# The cadence measurement above predates that split and was taken against
+# this repo's merge history; it stays the right order-of-magnitude
+# justification for 10 minutes because `coord-web`, being a repo dedicated
+# entirely to the webapp, has EVERY merge to its `main` in-scope for a build
+# — there is no "does this commit touch webapp/ at all" filtering to do
+# anymore (the script never filtered by path either; it always rebuilt on
+# any `origin/main` SHA change, webapp-only or not — this just makes that
+# now-trivially-true for the repo it targets).
+#
 # Install: see deploy/coord-web-dist-build.sh's header, or
 # docs/PHONE_WEBAPP.md / docs/AGENT_OPERATIONS.md.
 

{code_coordinator-0.5.185 → code_coordinator-0.5.187}/docs/ADR_COORD_WEB_DIST.md

@@ -156,3 +156,14 @@ timer is still alive.
 - 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.
+- Known follow-up, not fixed here: `coord-web`'s own
+  `playwright.acceptance.config.ts` computes `DEFAULT_FIXTURE` via a
+  `REPO_ROOT = path.resolve(here, '../../..')` climb that predates the
+  split, when that config lived three levels down under
+  `coord/dashboard/webapp/`. Now that the config lives at the `coord-web`
+  repo root, that climb resolves outside the repo entirely, so the default
+  points at a path that doesn't exist — the same class of bug #2470 fixed
+  in `deploy/coord-web-dist-build.sh`'s health-check fixture default (now
+  `$WEBAPP_CHECKOUT/e2e/fixtures/board-pipeline-basic.json`). Will bite
+  `coord-web`'s own `npm run test:acceptance` whenever it runs with no
+  explicit fixture path arg; needs a fix in the `coord-web` repo, not here.

{code_coordinator-0.5.185 → code_coordinator-0.5.187}/docs/AGENT_OPERATIONS.md

@@ -1418,7 +1418,7 @@ Three things follow, and they are why this command is shaped the way it is:
 | unit files vs the packaged `coord/deploy/**` | each machine's `/health` | `unit_drift` / PATH shadow (#1831, #1927) |
 | `~/.coord-cli-venv` | each machine's `/health` | `cli_venv` (#1806) |
 | `coord-tui` binary vs `tui/` source | each machine's `/health` | `tui_binary` — until PKG-3/PKG-4 give it a real channel |
-| `coord web --dist` bundle vs `coord/dashboard/webapp/` source | each machine's `/health` | `webapp_bundle` / `fleet_webapp_bundle` — lane 5, staleness only (see below) |
+| `coord web --dist` bundle vs `coord-web`'s own source | each machine's `/health` | `webapp_bundle` / `fleet_webapp_bundle` — lane 5, staleness only (see below) |
 
 `.githooks/**` (lane 6 above) is deliberately **not** graded here: its failure
 mode is the inverse — it is live everywhere at the next `git fetch`, with no
@@ -1431,17 +1431,19 @@ row above — deliberately, not by oversight.** Every other lane compares
 against *the released version*: a pip version string that both an agent venv
 and a spawned `coord` can report. The webapp bundle has no such string to
 compare against. `deploy/coord-web-dist-build.timer` publishes it
-continuously off `origin/main`'s SHA, once a minute, **decoupled on purpose**
-from the `~/.coord-venv` release cadence every other lane rides (#1543) —
-that decoupling is the entire point of that pipeline, so folding it into the
-version-skew map above would manufacture permanent, meaningless "skew"
-between a semver string and a git SHA on every correctly-running fleet, not
-report a real defect. What `webapp_bundle` (machine-scope) /
-`fleet_webapp_bundle` (fleet-scope) check instead, on its own terms — the
-same shape `tui_binary`/`fleet_tui_binary` already use for the locally-built
-`coord-tui` binary — is whether the live bundle is *stale relative to the
-`coord/dashboard/webapp/` source tree it claims to have been built from*, and
-whether two machines both serving `coord web` agree on which build that is.
+continuously off the `coord-web` repo's `origin/main` SHA (#2470; before
+that, this repo's own `coord/dashboard/webapp/`, epic #2002), every 10
+minutes (#2122), **decoupled on purpose** from the `~/.coord-venv` release
+cadence every other lane rides (#1543) — that decoupling is the entire point
+of that pipeline, so folding it into the version-skew map above would
+manufacture permanent, meaningless "skew" between a semver string and a git
+SHA on every correctly-running fleet, not report a real defect. What
+`webapp_bundle` (machine-scope) / `fleet_webapp_bundle` (fleet-scope) check
+instead, on its own terms — the same shape `tui_binary`/`fleet_tui_binary`
+already use for the locally-built `coord-tui` binary — is whether the live
+bundle is *stale relative to the `coord-web` source tree it claims to have
+been built from*, and whether two machines both serving `coord web` agree on
+which build that is.
 A WARN there means "`coord-web-dist-build.timer` has stopped publishing",
 which is the failure mode this lane exists to catch; it says nothing about
 whether that publish is caught up with the latest tagged release, because