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

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

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

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

@@ -796,6 +796,7 @@ tests/acceptance/ms-65/board_tabs_2282.rs
 tests/acceptance/ms-65/board_tabs_close_2283.rs
 tests/acceptance/ms-65/contract.md
 tests/acceptance/ms-65/manifest.yml
+tests/acceptance/ms-65/pipeline_tabs_2284.rs
 tests/acceptance/ms-65/mocks/board-baseline-no-tabs.screen
 tests/acceptance/ms-65/mocks/board-pinned-3-tabs.screen
 tests/acceptance/ms-65/mocks/board-preview-tab.screen

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

@@ -445,6 +445,7 @@
     "tests/acceptance/ms-65/mocks/board-tabs-help-overlay.screen",
     "tests/acceptance/ms-65/mocks/board-tabs-overflow.screen",
     "tests/acceptance/ms-65/mocks/pipeline-tabs-independent.screen",
+    "tests/acceptance/ms-65/pipeline_tabs_2284.rs",
     "tests/acceptance/ms-example/mocks/home-active.html",
     "tests/conftest.py",
     "tests/fixtures/board-pipeline-basic.json",

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

@@ -0,0 +1,8 @@
+{
+  "tag": "0.5.153",
+  "distance": 0,
+  "node": "g2968c6a10a7c3b15da201f4fd9049f641c23b3ee",
+  "dirty": false,
+  "branch": "HEAD",
+  "node_date": "2026-08-19"
+}

{code_coordinator-0.5.148 → code_coordinator-0.5.153}/coord/commands/drive_queue.py

@@ -71,6 +71,7 @@ from coord.drive_queue import (
     find_cycle,
     fired_holds,
     is_permanent_block_reason,
+    is_unsatisfiable_prereq_reason,
     parse_after_spec,
     parse_key,
     pending_probe_targets,
@@ -562,13 +563,31 @@ _BLOCKED_REMEDY = (
     "actually fixed, not merely because a pre-req merged"
 )
 
-# #2230: `blocked`'s MERGE GATE (as opposed to its `after=` graph, which
-# `_BLOCKED_REMEDY` above still correctly calls never-re-checked) is no
-# longer unconditionally terminal — see `coord.drive_queue.
-# is_permanent_block_reason`/`_reconcile_blocked`. Shown only for `blocked`
-# (never `failed`, which #2230 does not touch at all) so an operator reading
-# `list` right after this ships doesn't have to go read the issue to learn
-# their remove+add might be about to race an automatic resume.
+# #2362: a `blocked` row (never `failed` — the tick's `after=` resume sweep,
+# `coord.drive_queue._reconcile_blocked_after`, is scoped to `blocked` only)
+# whose OWN `last_reason` IS `_resolve_prereqs`'s "queued but blocked/failed
+# — it will never satisfy" verdict is auto re-checked every tick, and
+# resumes to `waiting` on its own the moment every named pre-req lands.
+# `_BLOCKED_REMEDY` above is flatly wrong for exactly this row shape (it is
+# in fact re-checked, on its own, without an operator) — this note replaces
+# it there instead of merely appending, mirroring #2230's own concern: an
+# operator told "never re-checked" for a row about to self-resume would
+# either do a needless remove+add or race the automatic one.
+_BLOCKED_AFTER_NOTE = (
+    "remedy: {state}'s `after=` graph above IS re-checked automatically "
+    "every tick (#2362) — once every named pre-req lands (`facts.landed`), "
+    "this row resumes to `waiting` on its own, attempt budget reset; no "
+    "operator remove+add needed. See `resumes=` above if it has already "
+    "self-resumed and re-blocked for an unrelated reason."
+)
+
+# #2230: `blocked`'s MERGE GATE (as opposed to its `after=` graph, handled by
+# `_BLOCKED_AFTER_NOTE`/`_BLOCKED_REMEDY` above) is no longer unconditionally
+# terminal — see `coord.drive_queue.is_permanent_block_reason`/
+# `_reconcile_blocked`. Shown only for `blocked` (never `failed`, which
+# #2230 does not touch at all) so an operator reading `list` right after this
+# ships doesn't have to go read the issue to learn their remove+add might be
+# about to race an automatic resume.
 _BLOCKED_GATE_NOTE = (
     "note: a re-evaluable blocked cause (i.e. not a #1844/#2019 permanent "
     "refusal) IS re-checked against the merge gate automatically (#2230) — "
@@ -693,12 +712,37 @@ def drive_queue_list(repo: str | None, output_json: bool, config_path: Path) ->
             # #2183 point 4: `blocked`/`failed` is terminal — say so where the
             # operator is already reading the row, not just in an unrelated
             # operator's hand-written `--hold-after` note.
-            click.echo(f"      {_BLOCKED_REMEDY.format(state=entry.state)}")
+            #
+            # #2404: EXCEPT when this row's own `last_reason` is exactly the
+            # unsatisfiable-`after=`-pre-req verdict on a `blocked` (not
+            # `failed`) entry — that shape auto-resumes on its own every tick
+            # (#2362), so the generic "never re-checked on its own" remedy
+            # would be actively wrong for it; swap in the note that says so.
+            if entry.state == STATE_BLOCKED and is_unsatisfiable_prereq_reason(
+                entry.last_reason
+            ):
+                click.echo(f"      {_BLOCKED_AFTER_NOTE.format(state=entry.state)}")
+            else:
+                click.echo(f"      {_BLOCKED_REMEDY.format(state=entry.state)}")
         # #2230: independent of the `after=` diagnosis above (most `blocked`
         # rows have no `after=` at all — they blocked on attempts, not a
         # pre-req), so gated on the row's OWN state and cause, not `diagnosed`.
-        if entry.state == STATE_BLOCKED and not is_permanent_block_reason(
-            entry.last_reason
+        #
+        # #2404 review: EXCLUDE the unsatisfiable-`after=`-pre-req shape
+        # `_BLOCKED_AFTER_NOTE` above already covers. #2230's sweep
+        # (`_blocked_gate_reading`) returns `None` — "no evidence" — for an
+        # entry that never reached the merge queue at all, which is exactly
+        # what a purely `after=`-caused block is; showing this note there
+        # would stack two auto-recheck notes citing two different issue
+        # numbers under one row, one of which has nothing to say about that
+        # row's actual cause. `is_permanent_block_reason` rows already skip
+        # this note on their own; this adds the sibling exclusion so the two
+        # notes stay mutually exclusive, matching what each mechanism can
+        # actually promise for a given row.
+        if (
+            entry.state == STATE_BLOCKED
+            and not is_permanent_block_reason(entry.last_reason)
+            and not is_unsatisfiable_prereq_reason(entry.last_reason)
         ):
             click.echo(f"      {_BLOCKED_GATE_NOTE}")
         for line in _hold_lines(entry):

{code_coordinator-0.5.148 → code_coordinator-0.5.153}/coord/drive_queue.py

@@ -1600,6 +1600,19 @@ def _is_unsatisfiable_prereq_reason(text: str | None) -> bool:
     return bool(text) and _UNSATISFIABLE_PREREQ_MARKER in text
 
 
+def is_unsatisfiable_prereq_reason(text: str | None) -> bool:
+    """Public alias for :func:`_is_unsatisfiable_prereq_reason`.
+
+    `coord drive-queue list`'s rendering (#2404) needs to tell whether a
+    `blocked` row's frozen ``last_reason`` is the exact shape
+    :func:`_reconcile_blocked_after` (#2362) auto-resumes once every named
+    pre-req lands, so it can stop telling the operator the ``after=`` graph
+    "is never re-checked on its own" for a row where that has stopped being
+    true — see ``coord.commands.drive_queue._BLOCKED_AFTER_NOTE``.
+    """
+    return _is_unsatisfiable_prereq_reason(text)
+
+
 def _reconcile_blocked_after(
     entry: QueueEntry,
     board: BoardView,

{code_coordinator-0.5.148 → code_coordinator-0.5.153}/coord/merge_queue.py

@@ -3984,6 +3984,17 @@ class PlannedMerge:
     # when no PR is open yet, or `ci_store` has no checks for this PR.
     pr_number: int | None = None
     ci_summary: "CiCheckSummary | None" = None
+    # #2397: mirrors `config.merge.auto_drain` (default False) at plan-build
+    # time — read-only exposure, no gate-logic change. The TUI's per-issue
+    # Merge stage box needs this to tell "nothing retries until a human runs
+    # `coord merge`" (auto_drain off) apart from "an automatic retry tick is
+    # already handling this" (auto_drain on); today it has no way to know
+    # and the box renders identically either way (issue #2397's incident:
+    # `#2284`'s acceptance-authoring slice sat "pending — waiting 2:22" with
+    # no signal that `merge.auto_drain: false` meant nothing was coming on
+    # its own). Same value on every entry in one `plan()` call — it's a
+    # single process-wide config flag, not per-entry state.
+    auto_drain: bool = False
 
 
 def _load_milestones_for_queue(
@@ -4058,6 +4069,10 @@ def plan(
     """
     items = load_queue()
     milestones = _load_milestones_for_queue(items)
+    # #2397: read once, stamped on every entry below — see `PlannedMerge
+    # .auto_drain`'s doc comment for why the TUI needs this alongside
+    # `reason`.
+    auto_drain = bool(getattr(getattr(config, "merge", None), "auto_drain", False))
 
     # ── Group by (repo_github, target_branch) ──────────────────────────────
     group_order: list[tuple[str, str]] = []
@@ -4133,6 +4148,7 @@ def plan(
                 enqueued_at=entry.enqueued_at,
                 last_attempt=entry.last_attempt,
                 milestone=milestones.get((entry.repo_name, entry.issue_number)),
+                auto_drain=auto_drain,
             ))
 
     return result

{code_coordinator-0.5.148 → code_coordinator-0.5.153}/tests/acceptance/ms-65/manifest.yml

@@ -86,6 +86,35 @@ tests:
   # zero-tab state. THIS IS THE GREEN CONTROL — see `expected_red` below.
   board_tabs_close_2283::zero_tabs_render_no_close_or_overflow_glyphs: 2283
 
+  # ── #2284 (W-3) — Pipeline's own independent tab set (contract §3) ────────
+  # Slice: pipeline_tabs_2284.rs · mocks: pipeline-tabs-independent.screen
+  # (plus board-pinned-3-tabs.screen — §3b calls the two "the independence
+  # pair")
+  #
+  # §3a — zero Pipeline tabs render no strip on Pipeline. THIS IS THE GREEN
+  # CONTROL — see the `expected_red` block below.
+  pipeline_tabs_2284::pipeline_with_zero_doc_tabs_renders_no_tab_strip: 2284
+  # §3a — Pipeline has no toolbar, so its strip is the FIRST main-panel content
+  # row, immediately above the Overview/Issue/Log/Summary/Terminal sub-tab bar
+  # (with §3a's own stated contrast: on Board the toolbar precedes the strip)
+  pipeline_tabs_2284::pipeline_doc_tab_strip_is_the_first_main_panel_row_with_no_toolbar_above_it: 2284
+  # §3b bullet 1 — switching to Pipeline shows Pipeline's (empty) set, not the
+  # Board's three tabs, and does not lose them. THIS IS A GREEN RATCHET — see
+  # the `expected_red` block below.
+  pipeline_tabs_2284::switching_to_pipeline_hides_the_boards_tabs_without_losing_them: 2284
+  # §3b + #2284 AC 1 — two Pipeline tabs with three already open on the Board
+  # shows EXACTLY two on Pipeline, and no Board document leaks into the strip
+  pipeline_tabs_2284::pipeline_opens_its_own_two_tabs_while_the_board_keeps_three: 2284
+  # §3b bullet 2 + AC 2 — the milestone's headline round trip: Board →
+  # Pipeline → Board restores the same three tabs, same order, same active tab
+  pipeline_tabs_2284::board_pipeline_board_round_trip_restores_the_boards_tabs_order_and_active_tab: 2284
+  # §3b + AC 3 — each scope owns its own preview slot: a single click in
+  # Pipeline leaves the Board's `∘ ` preview tab exactly where it was
+  pipeline_tabs_2284::each_scope_owns_its_own_preview_slot: 2284
+  # §3b + AC 4 — reveal-on-activate is per scope: activating a Pipeline tab
+  # selects its row in the PIPELINE sidebar and leaves the Board's selection
+  pipeline_tabs_2284::activating_a_pipeline_tab_reveals_its_row_in_the_pipeline_sidebar_not_the_boards: 2284
+
 # ── expected_red (#2164) ───────────────────────────────────────────────────
 # Hand-derived from a REAL run of the sealed suite against origin/main at the
 # time of authoring (`cd tui && cargo test --test acceptance --features
@@ -140,6 +169,34 @@ expected_red:
     - board_tabs_close_2283::activating_a_scrolled_out_tab_scrolls_it_back_into_view_and_renders_the_right_affordance
     - board_tabs_close_2283::closing_the_last_tab_restores_the_zero_tab_baseline
 
+  # #2284 — OBSERVED, not intended. Taken from three consecutive real runs of
+  # the sealed suite (`cd tui && RUSTC_BOOTSTRAP=1 cargo test --test acceptance
+  # --features test-support -- -Z unstable-options --format json`, the driver
+  # command in coordinator.yml) at authoring time: of this slice's 7 ids, the
+  # same 5 FAILED and the same 2 passed on every run. The 2 that passed are
+  # deliberately ABSENT below:
+  #
+  #   * `pipeline_with_zero_doc_tabs_renders_no_tab_strip` — the CONTROL.
+  #     Green today (no panel paints a strip with nothing open) and must stay
+  #     green after #2284 lands: an implementation that reserves the Pipeline
+  #     strip row unconditionally, or that renders the Board's tabs on
+  #     Pipeline, breaks exactly this test. Listing it would make its
+  #     inevitable pass a HARD FAILURE.
+  #   * `switching_to_pipeline_hides_the_boards_tabs_without_losing_them` — a
+  #     RATCHET. Green today for the degenerate reason that the single global
+  #     set #2282 shipped renders only on the Board, so nothing leaks onto
+  #     Pipeline and nothing is lost coming back. Both halves become real
+  #     constraints the moment the set is keyed by scope: a per-scope map that
+  #     rebuilds (rather than preserves) the outgoing scope's entry fails the
+  #     return leg, and a strip that paints the focused scope's tabs on the
+  #     wrong panel fails the outbound one.
+  2284:
+    - pipeline_tabs_2284::pipeline_doc_tab_strip_is_the_first_main_panel_row_with_no_toolbar_above_it
+    - pipeline_tabs_2284::pipeline_opens_its_own_two_tabs_while_the_board_keeps_three
+    - pipeline_tabs_2284::board_pipeline_board_round_trip_restores_the_boards_tabs_order_and_active_tab
+    - pipeline_tabs_2284::each_scope_owns_its_own_preview_slot
+    - pipeline_tabs_2284::activating_a_pipeline_tab_reveals_its_row_in_the_pipeline_sidebar_not_the_boards
+
 # ═══════════════════════════════════════════════════════════════════════════
 # FOR THE COORDINATOR — three findings from authoring this slice. None of them
 # is a worker's to fix, and none was resolved by editing the contract (a
@@ -255,3 +312,73 @@ expected_red:
 # (quadraui#593) have also landed (`style_at`/`styled_row`), but §1's ruling
 # stands: the `∘ ` marker remains the pinned preview signal, and this slice
 # asserts no styles.
+
+# ═══════════════════════════════════════════════════════════════════════════
+# FOR THE COORDINATOR — findings from authoring the #2284 slice (contract §3).
+# Independent of the #2282 / #2283 notes above; again, none is a worker's to
+# fix by editing this suite, and none was resolved by editing the contract.
+# ═══════════════════════════════════════════════════════════════════════════
+#
+# 7. LIVE HARNESS BLOCKER (flaky, machine-dependent, and it will bite #2284's
+#    worker on the very first run): **entering the Pipeline panel destroys the
+#    seeded fixture in the sealed suite.** Switching panels runs
+#    `sync_active_view_from_shell` -> `maybe_kick_pipeline_loader` ->
+#    `refresh()` -> `start_data_load()` (`tui/src/app/data.rs:2620`). That
+#    function short-circuits to `BoardData::default()` — so
+#    `apply_pending_data`'s #620 degraded-tick guard keeps the seeded board —
+#    but the short-circuit is gated `#[cfg(test)]` ONLY. `tui/tests/acceptance.rs`
+#    is a separate integration-test crate, so the `coord_tui` it links is built
+#    WITHOUT `cfg(test)`; the loader therefore reads the real local
+#    `~/.coord/coord.db`, and the next dispatched event (`dispatch_handle`
+#    drains the receiver before handling anything) wholesale-replaces
+#    `self.data`. Measured on this machine: two clicks after landing on
+#    Pipeline, the Board sidebar renders the developer's real `api (1)` repo
+#    and the Pipeline tree is empty ("Loading tracked issues…").
+#
+#    It is a RACE, not a certainty — the load runs on a spawned thread, so
+#    whether the fixture survives depends on whether that thread finished
+#    before the next event. Across three authoring runs, 3 of the 5 red ids
+#    died at the harness precondition and 2 got far enough to fail on the real
+#    §3a clause; which is which varied run to run. Every affected assertion
+#    says `HARNESS PRECONDITION (NOT a #2284 defect …)` in its panic message so
+#    the two failure modes are distinguishable from a JSON report alone.
+#
+#    The fix is one line of app code, and this repo has already made it once
+#    for the same reason: `resolve_board_service()`
+#    (`tui/src/app/data.rs:1950`) is gated
+#    `#[cfg(any(test, feature = "test-support"))]` with a comment citing #1039
+#    and naming this exact external-crate `cfg(test)` trap.
+#    `start_data_load()`'s stub needs the same widening. It is NOT in #2284's
+#    "Files" list, so the coordinator should either land it as a prerequisite
+#    or explicitly authorise the worker to widen that cfg — without it the five
+#    red ids below cannot go green reliably no matter how correct the
+#    per-scope tab model is.
+#
+# 8. §3b's "same scroll position as before the switch" is not asserted. The
+#    round-trip test opens three tabs in an 82-column strip, where nothing is
+#    scrolled, and the contract pins no rendered signal for a *restored* strip
+#    scroll offset beyond §4's `‹`/`›` affordances — which are #2283's slice
+#    and whose own mock the #2283 author already flagged (finding 4) as
+#    contradicting §2b's label width. Inventing an observable for it would
+#    have meant inventing a width. Flagged as a `TODO(test-author)` in the
+#    slice.
+#
+# 9. §2f's scroll half is likewise not re-asserted for the Pipeline scope.
+#    #2284's own AC says "reveals its row in the Pipeline sidebar, not the
+#    Board's", and the contract pins the scroll requirement only for the Board
+#    (§2f, five issues on a short viewport). This slice asserts the per-scope
+#    SELECTION (`▸ #201` inside the Pipeline sidebar's columns 3–37, plus the
+#    Board's own `▸ #103` surviving a Pipeline-side activation) and leaves the
+#    scroll half to #2282's slice, which owns §2f. Also a `TODO(test-author)`.
+#
+# Also worth knowing, not a contract problem: the Pipeline sidebar nests
+# tracked issues under state -> repo -> milestone nodes whose innermost node is
+# COLLAPSED by default, and renders rows as `#201  Add retry backoffwork`
+# (two spaces, title truncated to the 35-column sidebar, stage badge butted
+# against it) — nothing like the mocks' `#201 Add retry backoff to fetch`. The
+# slice therefore targets Pipeline rows by their `#<N>` tag restricted to the
+# sidebar columns (§0), never by a full row string, and expands that group as a
+# labelled precondition. The fixture also gives #101–#103 an untracked label
+# and #201–#203 the tracked `coord` one: the Board sidebar lists all six (it
+# does not filter by label) while the Pipeline lists only the 200s, which is
+# what makes the mocks' 100s/200s ranges disjoint in a single seeded board.