code-coordinator 0.5.755__tar.gz → 0.5.756__tar.gz

{code_coordinator-0.5.755 → code_coordinator-0.5.756}/PKG-INFO

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

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

@@ -0,0 +1,8 @@
+{
+  "tag": "0.5.756",
+  "distance": 0,
+  "node": "g6554d6ff10c266cf881ccdd2d5940ba15260475a",
+  "dirty": false,
+  "branch": "HEAD",
+  "node_date": "2026-11-11"
+}

{code_coordinator-0.5.755 → code_coordinator-0.5.756}/coord/dispatch.py

@@ -592,6 +592,12 @@ that hosts it.
 # half (parse, file through the issue-tracker seam, link, block the queue row
 # `after=` it). The example deliberately uses `<placeholders>`: the parser
 # rejects them, so a log that echoes this briefing never files a fake gap.
+# #3977: the body MUST name a real inline-code symbol (not `<placeholder>`,
+# not a backtick-quoted sentence or shell command — `_named_symbols` only
+# recognises a single identifier path) — a marker with none can't be checked
+# against the upstream repo before filing (`_verify_gap`), so it goes out
+# unverified and unqueued, costing a human a confirmation round-trip that
+# naming the symbol up front would have skipped.
 UPSTREAM_GAP_BRIEFING_NOTE = """
 
 ## Cross-repo gaps — `BLOCKED_ON_UPSTREAM` (#3676)
@@ -608,11 +614,17 @@ the lines directly below it (a blank line ends the body):
 where this repo would call it>
 
 `<repo>` is the upstream repo's coordinator name or its `owner/name` GitHub \
-slug. The coordinator files the upstream issue for you, links it to this \
-one, and holds this issue's drive-queue row until it lands — you never need \
-the issue number. Still commit and push whatever is genuinely done; if the \
-gap leaves this issue unresolved, also declare `ISSUE_RESOLUTION: partial — \
-blocked on upstream (BLOCKED_ON_UPSTREAM above)`.
+slug. The body MUST name at least one inline-code symbol for the missing \
+API — a bare symbol (`` `Foo::bar` ``) is clearest, and a path-prefixed or \
+call-decorated span (`` `a/b.rs::Foo::bar(Baz)` ``) is also recognised — \
+the coordinator greps the upstream repo's own default branch for it before \
+filing, so a marker with no checkable symbol is filed unverified and held \
+unqueued until a human confirms it (#3977). The coordinator files the upstream \
+issue for you, links it to this one, and holds this issue's drive-queue \
+row until it lands — you never need the issue number. Still commit and \
+push whatever is genuinely done; if the gap leaves this issue unresolved, \
+also declare `ISSUE_RESOLUTION: partial — blocked on upstream \
+(BLOCKED_ON_UPSTREAM above)`.
 """
 
 # #3711: appended to every `type="work"` briefing, alongside

{code_coordinator-0.5.755 → code_coordinator-0.5.756}/coord/drive_queue.py

@@ -123,6 +123,7 @@ from coord.models import (
     is_needs_decomposition_reason,
     is_policy_refusal_reason,
     is_premise_refusal_reason,
+    is_upstream_gap_park_reason,
     parse_issue_resolution,
 )
 from coord.worker_events import classify_zero_commit_outcome
@@ -8760,6 +8761,21 @@ def plan_tick(
         # (`coord drive-queue remove`).
         if is_needs_decomposition_reason(entry.last_reason):
             continue
+        # #3977: an upstream-gap park (`coord.upstream_gaps._park_queue_row`)
+        # has the SAME "no external verdict to poll for" shape as the three
+        # checks just above — a release landing or a coordinator confirming
+        # a dedup/unverified gap leaves no trace this tick can read, so this
+        # never resumes itself either. Without this check the row would read
+        # exactly like a cleared CI gate (`facts.merge_ci_pending` is False —
+        # this row was never in the merge queue) and fall straight into the
+        # #1891 default below, flipping back to `waiting`, resetting
+        # `attempts`, and relaunching a worker straight into re-emitting the
+        # identical marker — the park/relaunch bounce #2234's comment above
+        # exists to prevent, replayed here for a park written outside this
+        # module. Stays parked until a human clears it by hand (`coord
+        # drive-queue remove`).
+        if is_upstream_gap_park_reason(entry.last_reason):
+            continue
         # #2977: a throttle-skip park (`github_ops.is_throttle_skip_reason`)
         # carries its OWN known wall-clock expiry (`until=<epoch>`, embedded
         # by `github_ops.format_throttle_skip_reason` at park time) — unlike

{code_coordinator-0.5.755 → code_coordinator-0.5.756}/coord/github_ops.py

@@ -3661,13 +3661,43 @@ def create_issue(
     labels: list[str] | None = None,
     milestone: str | None = None,
 ) -> dict:
+    """Create an issue via ``gh issue create``. Returns ``{"number", "url"}``.
+
+    ``gh`` hard-fails the create when a requested label does not exist in
+    *repo*, so a label-not-found failure auto-creates every requested label
+    and retries the create once — the same recovery
+    :func:`change_issue_labels` performs on its add path, and what lets a
+    caller pass a policy label (e.g.
+    `coord.board_doctor.STRANDED_PREREQ_OPT_OUT_LABEL`) without every
+    target repo having been provisioned with it first. Only label-not-found
+    errors trigger it: :func:`_is_label_not_found` screens out auth,
+    network and rate-limit failures, which propagate untouched so a create
+    is never retried against a forge that may have accepted the first one.
+    A retry that still reports label-not-found raises :class:`GhNotFound`.
+    """
     args = ["issue", "create", "--repo", repo, "--title", title, "--body", body]
     if labels:
         for label in labels:
             args.extend(["--label", label])
     if milestone:
         args.extend(["--milestone", milestone])
-    raw = _gh(*args, caller="github_ops.create_issue")
+    try:
+        raw = _gh(*args, caller="github_ops.create_issue")
+    except RuntimeError as exc:
+        if not (labels and _is_label_not_found(exc)):
+            raise
+        for label in labels:
+            try:
+                _gh("label", "create", label, "--repo", repo,
+                    caller="github_ops.create_issue")
+            except RuntimeError:
+                pass  # idempotent: label may already exist (concurrent create)
+        try:
+            raw = _gh(*args, caller="github_ops.create_issue")
+        except RuntimeError as retry_exc:
+            if _is_label_not_found(retry_exc):
+                raise GhNotFound(str(retry_exc)) from retry_exc
+            raise
     url = raw.strip()
     number = int(url.rstrip("/").rsplit("/", 1)[-1])
     return {"number": number, "url": url}

{code_coordinator-0.5.755 → code_coordinator-0.5.756}/coord/models.py

@@ -1142,6 +1142,39 @@ def is_needs_decomposition_reason(text: str | None) -> bool:
     return bool(text) and NEEDS_DECOMPOSITION_MARKER in text
 
 
+# #3977: the machine-readable tag `coord.upstream_gaps._park_queue_row`
+# embeds in a downstream drive-queue row's `last_reason` when it parks the
+# row directly — no upstream issue, no `after=` edge: a symbol confirmed on
+# the upstream default branch (unreleased, not missing) or a dedup match
+# that closed within the recent-close window. Same SIBLING shape as
+# `POLICY_REFUSAL_MARKER`/`PREMISE_REFUSAL_MARKER`/`NEEDS_DECOMPOSITION_
+# MARKER` above: nothing on the board signals a release landing or a
+# coordinator's confirmation, so there is no external verdict to poll for.
+#
+# Text-marker matching (not a dedicated exit code), same rationale as the
+# three markers above: `coord/drive_queue.py`'s parked pre-pass recognises
+# this straight out of the row's own `last_reason` and leaves the row
+# parked rather than falling through to the CI-park "resume" default, which
+# would otherwise flip it back to `waiting` on the very next tick and
+# relaunch a worker straight into re-emitting the identical marker.
+UPSTREAM_GAP_PARK_MARKER = "[parked-on-upstream-gap #3977]"
+
+
+def is_upstream_gap_park_reason(text: str | None) -> bool:
+    """Whether *text* is a #3977 upstream-gap park reason.
+
+    Like a policy/premise refusal or a needs-decomposition park, this has
+    no external verdict that can arrive and clear it on its own — a
+    release landing, or a coordinator confirming a dedup/unverified gap,
+    leaves no trace on the board that this module (or anything else) polls
+    for — so nothing auto-resumes an entry parked for this reason. An
+    operator clears it by hand once the release lands / the pin is bumped,
+    or once the gap is confirmed, the same way they clear a `blocked` entry
+    (`coord drive-queue remove` + `add` for a fresh row).
+    """
+    return bool(text) and UPSTREAM_GAP_PARK_MARKER in text
+
+
 # #2850: the machine-readable tag `coord.drive.decide` embeds in its
 # `_succeed()` message when the "terminal: merged" branch's own LIVE check
 # (`MergeVerifier.verify_merged`) confirms the issue has genuinely landed —