code-coordinator 0.5.262__tar.gz → 0.5.264__tar.gz

{code_coordinator-0.5.262 → code_coordinator-0.5.264}/PKG-INFO

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

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

@@ -265,6 +265,7 @@ coord/skills/fleet-restart-safety/SKILL.md
 coord/skills/merge-stuck-triage/SKILL.md
 coord/skills/pipeline-limbo-triage/SKILL.md
 coord/skills/portal-followup/SKILL.md
+coord/skills/release-now/SKILL.md
 coord/skills/review-verdict-recovery/SKILL.md
 coord/skills/tui-quadraui-workflow/SKILL.md
 coord/skills/update-issue/SKILL.md

{code_coordinator-0.5.262 → code_coordinator-0.5.264}/code_coordinator.egg-info/scm_file_list.json

@@ -241,6 +241,7 @@
     "coord/skills/merge-stuck-triage/SKILL.md",
     "coord/skills/pipeline-limbo-triage/SKILL.md",
     "coord/skills/portal-followup/SKILL.md",
+    "coord/skills/release-now/SKILL.md",
     "coord/skills/review-verdict-recovery/SKILL.md",
     "coord/skills/tui-quadraui-workflow/SKILL.md",
     "coord/skills/update-issue/SKILL.md",

{code_coordinator-0.5.262 → code_coordinator-0.5.264}/code_coordinator.egg-info/scm_version.json

@@ -1,7 +1,7 @@
 {
-  "tag": "0.5.262",
+  "tag": "0.5.264",
   "distance": 0,
-  "node": "g0ef4d9fe88b17a02b984541dc5f936ddefb6ec56",
+  "node": "g037604ea4782108f989df77750337682d26f2a36",
   "dirty": false,
   "branch": "HEAD",
   "node_date": "2026-08-28"

{code_coordinator-0.5.262 → code_coordinator-0.5.264}/coord/commands/release.py

@@ -3146,7 +3146,29 @@ def release_nightly_window(
     existing = read_roll_pending()
 
     if dry_run:
-        if existing is not None:
+        # #2866: a marker naming a STALE target (not equal to the freshly
+        # resolved `record.target_version` — PyPI's "latest" moved, or the
+        # daemon reached/passed it some other way since the marker was set)
+        # must never be echoed back as "would attempt ... --target <stale>".
+        # This is the exact 2026-08-28 incident: a `propagate`-set marker
+        # for v0.5.254 survived on disk after the daemon had already
+        # reached v0.5.258 by other means, and `nightly-window --dry-run`
+        # read it back and printed a proposal to roll BACKWARDS to
+        # v0.5.254 — cleared by hand with `coord drive-queue cancel-roll`
+        # at the time. In reality a NON-dry-run run never fires a stale
+        # target either (section 3 below replaces it with
+        # `record.target_version` instead, whenever it differs) — this
+        # branch only makes the --dry-run description match that real
+        # behaviour instead of quoting the stale value as if it would run.
+        if existing is not None and existing.target_version != record.target_version:
+            click.echo(
+                f"a roll is pending for a stale target ({existing.describe()}) — "
+                f"would replace it with v{record.target_version} ({daemon_name} "
+                f"currently reports v{record.daemon_version or '?'}) rather than "
+                "ever firing the stale value (#2866); its original set_at/"
+                "deferrals would be preserved (#2607)"
+            )
+        elif existing is not None:
             click.echo(
                 f"a roll is already pending ({existing.describe()}) — would "
                 f"attempt `coord release propagate --daemon-host {daemon_name} "

{code_coordinator-0.5.262 → code_coordinator-0.5.264}/coord/deploy/coord-release-propagate.service

@@ -64,17 +64,38 @@
 #
 # MIN-RELEASES-BEHIND GATE (#2583) — OFF BY DEFAULT, NOT SET HERE
 # -----------------------------------------------------------------
-# `coord release propagate` (and `coord release nightly-window`, below)
-# support holding a run below a configurable delta —
-# `propagation.min_releases_behind` in coordinator.yml, or `--min-behind` on
-# either command — instead of attempting a roll on ANY delta at all (today's
-# default, `min_releases_behind=1`, unchanged unless configured). This
-# `ExecStart=` deliberately does NOT pass `--min-behind`: the threshold is
-# meant to be set (or left alone) via coordinator.yml so both this timer and
-# `coord-release-window.service` read the SAME value, and — per
-# `docs/AGENT_OPERATIONS.md`'s "Auto-roll threshold gate" section — must NOT
-# be raised above 1 on a fleet that has not first taken one manual roll onto
-# a fixed propagation lane. Below the threshold, this unit's own run reports
+# `coord release propagate` (and `coord release nightly-window`, its sibling
+# in `coord-release-window.service`) support holding a run below a
+# configurable delta — `propagation.min_releases_behind` in coordinator.yml,
+# or `--min-behind` on either command — instead of attempting a roll on ANY
+# delta at all (the default, `min_releases_behind=1`, unchanged unless
+# configured). This `ExecStart=` deliberately does NOT pass `--min-behind`:
+# THIS timer reads `propagation.min_releases_behind` straight from
+# coordinator.yml, un-overridden, and that is intentional — see #2866's
+# split:
+#
+#   | Trigger                          | Threshold | Role                  |
+#   |-----------------------------------|-----------|----------------------|
+#   | coord-release-propagate.timer     | 5 (config)| opportunistic — must  |
+#   | (this unit, every 20 min)         |           | not cordon/drain the  |
+#   |                                    |           | fleet every ~45 min,  |
+#   |                                    |           | auto-release.yml's    |
+#   |                                    |           | measured cadence      |
+#   |                                    |           | (12 releases on       |
+#   |                                    |           | 2026-08-27)           |
+#   | coord-release-window.timer        | 1 (fixed  | the guarantee — one   |
+#   | (daily)                           | via       | painless roll a day,  |
+#   |                                    | --min-behind)| whatever accumulated|
+#
+# `coordinator.yml` is a SHARED value read by both commands — raising it
+# here to spare this 20-minute cadence from over-eager rolls would ALSO
+# raise `coord-release-window.service`'s threshold if that unit read the
+# same unqualified default, which is exactly why THAT unit pins
+# `--min-behind 1` explicitly on its own `ExecStart=` rather than relying on
+# this shared config value. Per `docs/AGENT_OPERATIONS.md`'s "Auto-roll
+# threshold gate" section, `propagation.min_releases_behind` must NOT be
+# raised above 1 on a fleet that has not first taken one manual roll onto a
+# fixed propagation lane. Below the threshold, this unit's own run reports
 # `holding: N behind, threshold M` and exits 0, exactly like an ordinary
 # deferral — no cordon, no host touched.
 

{code_coordinator-0.5.262 → code_coordinator-0.5.264}/coord/deploy/coord-release-window.service

@@ -126,20 +126,53 @@
 #
 # MIN-RELEASES-BEHIND GATE (#2583) — OFF BY DEFAULT, NOT SET HERE
 # -----------------------------------------------------------------
-# This unit is the PREFERRED vehicle for the #2583 threshold: it is the one
-# place `coord release nightly-window` itself decides whether the daemon
-# host needs a roll at all, so a `propagation.min_releases_behind` set in
-# coordinator.yml (or a `--min-behind` appended to `ExecStart=` below) holds
-# it there — no roll-pending marker set, no `coord release propagate`
-# subprocess spawned — until the daemon is genuinely that many releases
-# behind PyPI's latest. Left unset here on purpose: `min_releases_behind=1`
-# (any delta at all, today's behaviour) is the safe default until an
-# operator deliberately raises it — see `docs/AGENT_OPERATIONS.md`'s
-# "Auto-roll threshold gate" section for why the CURRENT fleet must take one
-# manual roll first, onto a fixed propagation lane, before this is ever
-# turned up. A held run reports `holding: N behind, threshold M` in its own
-# journal (`coord release window-history`) and exits 0, same as a normal
-# `roll-pending`/`up-to-date` outcome.
+# #2866: `--min-behind 1` is set EXPLICITLY on `ExecStart=` below — this is
+# the packaged default now, not "left unset" as an earlier revision of this
+# comment said. The two release timers want DIFFERENT thresholds, and
+# `propagation.min_releases_behind` in coordinator.yml is shared by both
+# `coord release propagate` (step 3a) and `coord release nightly-window`
+# (step 2b) — raising it to spare the 20-minute propagate cadence from
+# cordoning/draining the fleet on every delta would ALSO raise it here,
+# which defeats the entire point of this unit (a guaranteed daily roll,
+# whatever accumulated):
+#
+#   | Trigger                          | Threshold | Role                  |
+#   |-----------------------------------|-----------|----------------------|
+#   | coord-release-propagate.timer     | 5 (config)| opportunistic — must  |
+#   | (every 20 min)                    |           | not cordon/drain the  |
+#   |                                    |           | fleet every ~45 min,  |
+#   |                                    |           | auto-release.yml's    |
+#   |                                    |           | measured cadence      |
+#   |                                    |           | (12 releases on       |
+#   |                                    |           | 2026-08-27)           |
+#   | coord-release-window.timer        | 1 (here)  | the guarantee — one   |
+#   | (daily)                           |           | painless roll a day,  |
+#   |                                    |           | whatever accumulated  |
+#
+# Measured on dellserver at 1 release behind: without `--min-behind` this
+# unit inherited the shared config's `min_releases_behind=5` and reported
+# `holding: 1 behind, threshold 5` — the daily guarantee was silently
+# count-based instead of time-based. `--min-behind` on `ExecStart=` always
+# wins over `propagation.min_releases_behind` (see `coord release
+# nightly-window --help`), so this unit's threshold stays 1 regardless of
+# what the shared config sets for the propagate timer. See
+# `docs/AGENT_OPERATIONS.md`'s "Auto-roll threshold gate" section for why a
+# threshold above 1 requires one manual roll first onto a fixed propagation
+# lane — that requirement is about `propagation.min_releases_behind`
+# (the propagate timer's knob), not this unit's hardcoded 1. A held run
+# reports `holding: N behind, threshold M` in its own journal (`coord
+# release window-history`) and exits 0, same as a normal `roll-pending`/
+# `up-to-date` outcome.
+#
+# The dellserver drop-in this superseded
+# (`~/.config/systemd/user/coord-release-window.service.d/override.conf`,
+# added as the interim fix before this landed) can now be deleted — this
+# `ExecStart=` reproduces it exactly, so removing the drop-in changes
+# nothing. `coord agent update` rewrites this unit file on every roll but
+# never touches a drop-in, which is why that override survived every roll
+# since it was added but would NOT have survived a from-scratch rebuild of
+# this host — the whole reason this is now the packaged default instead of
+# operator-local state.
 
 [Unit]
 Description=Release window: set/fire the #2587 roll-pending marker on the daemon host
@@ -153,7 +186,11 @@ Type=oneshot
 # it shells out to when firing an already-pending marker. A fleet that is
 # still busy is reported and left for the drive-queue tick to keep
 # watching, never overridden.
-ExecStart=%h/.local/bin/coord release nightly-window --config %h/.coord/coordinator.yml
+# #2866: --min-behind 1 is the daily guarantee's own threshold, deliberately
+# independent of `propagation.min_releases_behind` (which the 20-minute
+# coord-release-propagate.service alone should govern) — see the
+# MIN-RELEASES-BEHIND GATE comment above for the full split.
+ExecStart=%h/.local/bin/coord release nightly-window --config %h/.coord/coordinator.yml --min-behind 1
 # Bounded by the SAME ceiling coord-release-propagate.service uses: the
 # "marker already pending -> attempt a fire" branch shells out to `coord
 # release propagate` with its own 1800s subprocess timeout

code_coordinator-0.5.264/coord/deploy/coord-release-window.timer

@@ -0,0 +1,55 @@
+# coord release nightly-window — fires coord-release-window.service
+# (Type=oneshot) once a night. See that unit's header for the full
+# rationale (#2112, rewritten #2587).
+#
+# 10:00 America/Chicago — #2866: this is what the fleet actually runs
+# (dellserver carried it as an untracked
+# `coord-release-window.timer.d/override.conf` drop-in from 2026-08-26
+# until this became the packaged default), replacing the earlier packaged
+# 03:00 UTC. Named with an explicit zone rather than a bare local wall-clock
+# time specifically so a DST transition cannot drift the fire time by an
+# hour twice a year — `systemd.time(7)`'s `OnCalendar=` resolves a
+# zone-qualified spec against that zone's own clock, DST included. Still
+# inside a low-drive-activity part of the day; the exact hour matters far
+# less than picking ONE the operator can reason about, since #2587 already
+# means a late/early firing costs nothing (see below). #2587: this firing
+# itself is now fast (resolve the target, set-or-fire the roll-pending
+# marker, return) — there is no multi-hour drain to leave room for any
+# more. The ACTUAL roll may still land well after this fires if the fleet
+# stays busy; that is fine and by design, since it fires the instant `coord
+# drive-queue tick` sees the fleet's own next inter-drive gap rather than
+# waiting for THIS timer's next fire, and never stops any timer to get
+# there.
+#
+# The dellserver drop-in this superseded can now be deleted — this
+# `OnCalendar=` reproduces it exactly (same zone-qualified spec), so
+# removing the drop-in changes nothing. A from-scratch rebuild of that host
+# would otherwise have silently reverted to 03:00 UTC with no warning,
+# which is the whole reason this moved from operator-local override to
+# packaged default.
+#
+# RandomizedDelaySec is small and exists only to avoid firing at the exact
+# same wall-clock instant `coord-drive-queue.timer`'s own OnCalendar-free
+# interval schedule might land on, not because two hosts might race this
+# unit — it belongs on the daemon host ONLY (same rule as
+# coord-release-propagate.timer; see that unit's header for why a second
+# copy elsewhere is the #1440 two-overseers failure in a new costume).
+#
+# Persistent=true (#2112 trap 4 / acceptance-adjacent): a host that was
+# asleep or rebooted through 03:00 still catches up on the next boot, rather
+# than silently skipping a whole night. `coord release nightly-window`
+# itself is idempotent — see its module docstring's `needs_roll`: a fleet
+# already current at whatever time this actually fires touches nothing at
+# all.
+
+[Unit]
+Description=Nightly release window on the daemon host (#2112, #2587)
+
+[Timer]
+OnCalendar=*-*-* 10:00:00 America/Chicago
+RandomizedDelaySec=5min
+AccuracySec=1min
+Persistent=true
+
+[Install]
+WantedBy=timers.target

{code_coordinator-0.5.262 → code_coordinator-0.5.264}/coord/housekeeping.py

@@ -21,6 +21,18 @@ Two guarantees make the sweep safe:
 The sweep runs automatically on a low-cadence daemon tick and on demand via
 ``coord housekeeping`` (which routes through the daemon — the canonical DB lives
 there).
+
+#1107 Part 3: the same sweep also archives ``merge_queue`` rows in the
+``MERGED`` terminal state once they're older than the retention window, into
+``merge_queue_archive`` — mirroring the move-not-delete pattern above.
+``merge_queue`` has no natural "close" event of its own (unlike assignments,
+which age out via ``TERMINAL_STATUSES``), so without this a MERGED row lives
+forever: 192 such rows had accumulated by 2026-07-12 and 61 more by
+2026-07-30, both requiring a manual one-off ``DELETE``/``coord merge --drop``
+declog. ``coord.merge_queue.merged_issue_keys()`` unions the live table with
+the archive so the "already merged, don't re-enqueue" dedup in
+``enqueue_approved_work``/``staging_items`` keeps working after a row ages
+out.
 """
 
 from __future__ import annotations
@@ -48,6 +60,9 @@ _ASSIGNMENTS = "assignments"
 _ASSIGNMENTS_ARCHIVE = "assignments_archive"
 _NOTIFICATIONS = "notifications"
 _NOTIFICATIONS_ARCHIVE = "notifications_archive"
+_MERGE_QUEUE = "merge_queue"
+_MERGE_QUEUE_ARCHIVE = "merge_queue_archive"
+_MERGE_QUEUE_MERGED_STATE = "merged"
 _BATCH = 400  # keep IN(...) clauses well under SQLite's 999-variable limit
 
 
@@ -124,20 +139,26 @@ def _move_rows(
 
 
 def sweep(*, dry_run: bool = False, now: float | None = None) -> dict:
-    """Archive stale terminal assignments + their notifications.
+    """Archive stale terminal assignments + their notifications + merged
+    merge_queue entries.
 
     Returns ``{"archived_assignments": N, "archived_notifications": M,
-    "dry_run": bool, "retention_days": D}``.  ``archived_*`` are the counts that
-    were (or, for ``dry_run``, would be) moved.  A no-op returns zeros.
+    "archived_merge_queue": K, "dry_run": bool, "retention_days": D}``.
+    ``archived_*`` are the counts that were (or, for ``dry_run``, would be)
+    moved.  A no-op returns zeros.
 
     Conservative by construction: nothing active, recent (within the archive
     window), queued-for-merge, latest-of-an-open-issue, or review-linked to any
-    such row is ever moved.
+    such row is ever moved. Merge queue entries are archived only once they
+    are in the terminal ``MERGED`` state (#1107 Part 3) — non-terminal /
+    conflicted entries are left for ``prune_stale_queue_entries`` or manual
+    ``coord merge --drop``.
     """
     cutoff = _archive_cutoff(now)
     result = {
         "archived_assignments": 0,
         "archived_notifications": 0,
+        "archived_merge_queue": 0,
         "dry_run": dry_run,
         "retention_days": _archive_retention_days(),
     }
@@ -151,13 +172,19 @@ def sweep(*, dry_run: bool = False, now: float | None = None) -> dict:
             conn, f"SELECT {_KEEP_INDEX_COLUMNS} FROM {_ASSIGNMENTS}"  # noqa: S608
         ).fetchall()
     ]
-    mq_ids = {
+    mq_rows = sql.execute(
+        conn,
+        "SELECT assignment_id, state, last_attempt, enqueued_at "  # noqa: S608
+        f"FROM {_MERGE_QUEUE}",
+    ).fetchall()
+    mq_ids = {r["assignment_id"] for r in mq_rows if r["assignment_id"]}
+    mq_merged_ids = [
         r["assignment_id"]
-        for r in sql.execute(
-            conn, f"SELECT assignment_id FROM merge_queue"  # noqa: S608
-        ).fetchall()
+        for r in mq_rows
         if r["assignment_id"]
-    }
+        and (r["state"] or "").lower() == _MERGE_QUEUE_MERGED_STATE
+        and (r["last_attempt"] or r["enqueued_at"] or 0) < cutoff
+    ]
     open_keys = {
         (r["repo_name"], r["number"])
         for r in sql.execute(
@@ -194,7 +221,8 @@ def sweep(*, dry_run: bool = False, now: float | None = None) -> dict:
 
     result["archived_assignments"] = len(candidates)
     result["archived_notifications"] = len(notif_ids)
-    if dry_run or (not candidates and not notif_ids):
+    result["archived_merge_queue"] = len(mq_merged_ids)
+    if dry_run or (not candidates and not notif_ids and not mq_merged_ids):
         return result
 
     with conn:
@@ -206,4 +234,8 @@ def sweep(*, dry_run: bool = False, now: float | None = None) -> dict:
             _move_rows(
                 conn, _ASSIGNMENTS, _ASSIGNMENTS_ARCHIVE, "assignment_id", candidates
             )
+        if mq_merged_ids:
+            _move_rows(
+                conn, _MERGE_QUEUE, _MERGE_QUEUE_ARCHIVE, "assignment_id", mq_merged_ids
+            )
     return result

{code_coordinator-0.5.262 → code_coordinator-0.5.264}/coord/merge_queue.py

@@ -12,6 +12,7 @@ from __future__ import annotations
 import inspect
 import json
 import logging
+import sqlite3
 import time
 from dataclasses import dataclass, field
 from datetime import datetime, timezone
@@ -3753,6 +3754,58 @@ def save_queue(items: list[QueuedMerge]) -> None:
     retry_on_locked(_write)
 
 
+# ── Merged-history lookups (#1107 Part 3) ───────────────────────────────────
+#
+# `housekeeping.sweep()` archives MERGED merge_queue rows older than the
+# archive retention window into `merge_queue_archive` (same move-not-delete
+# pattern as `assignments`/`notifications`) so the live table stays bounded
+# instead of growing forever. `enqueue_approved_work()` and `staging_items()`
+# both dedup on "(repo, issue) already merged" to avoid re-surfacing an issue
+# whose prior work attempt already shipped — once the winning entry ages out
+# of the live table, that check must still see it, so it consults the
+# archive too.
+
+def _archived_merged_issue_keys(conn: sqlite3.Connection) -> set[tuple[str, int]]:
+    """(repo_name, issue_number) pairs recorded MERGED in the archive.
+
+    `merge_queue_archive` only exists once a housekeeping sweep has archived
+    at least one row (or archiving is disabled entirely), so this is
+    defensive against the table being absent.
+    """
+    try:
+        rows = sql.execute(
+            conn,
+            "SELECT repo_name, issue_number FROM merge_queue_archive WHERE state = ?",
+            (MERGED,),
+        ).fetchall()
+    except sql.driver_errors():  # #2784: not just sqlite3.OperationalError
+        # "no such table" surfaces as a *different* driver-named exception
+        # per backend (sqlite3.OperationalError vs psycopg.errors.
+        # UndefinedTable), so this must go through the dialect seam or the
+        # not-yet-archived case becomes an uncaught crash on Postgres.
+        return set()
+    return {(r["repo_name"], r["issue_number"]) for r in rows}
+
+
+def merged_issue_keys() -> set[tuple[str, int]]:
+    """All ``(repo_name, issue_number)`` pairs ever recorded MERGED.
+
+    Unions the live ``merge_queue`` table with ``merge_queue_archive`` so
+    callers get a correct answer regardless of whether the winning entry has
+    since been archived by ``housekeeping.sweep()``.
+    """
+    conn = get_connection()
+    live = {
+        (r["repo_name"], r["issue_number"])
+        for r in sql.execute(
+            conn,
+            "SELECT repo_name, issue_number FROM merge_queue WHERE state = ?",
+            (MERGED,),
+        ).fetchall()
+    }
+    return live | _archived_merged_issue_keys(conn)
+
+
 # ── Enqueue ──────────────────────────────────────────────────────────────
 
 def enqueue(
@@ -5403,12 +5456,10 @@ def staging_items(board, config, gh_ops: "GhOps | None" = None) -> list[StagingI
     queued_branches: set[str] = {x.branch for x in existing_queue if x.branch}
 
     # Fast-lookup: (repo_name, issue_number) pairs already MERGED so we skip
-    # issues whose prior attempt was already shipped.
-    already_merged: set[tuple[str, int]] = {
-        (x.repo_name, x.issue_number)
-        for x in existing_queue
-        if x.state == MERGED
-    }
+    # issues whose prior attempt was already shipped. Consults the archive
+    # too (#1107 Part 3) since the winning entry may have aged out of the
+    # live table by the time a later duplicate work item shows up here.
+    already_merged = merged_issue_keys()
 
     result: list[StagingItem] = []
     completed = list(getattr(board, "completed", []) or [])

{code_coordinator-0.5.262 → code_coordinator-0.5.264}/coord/serve_app.py

@@ -677,7 +677,8 @@ def _audit_housekeeping_sweep(swept: dict) -> None:
         summary=(
             f"housekeeping: archived {swept.get('archived_assignments', 0)} "
             f"assignment(s), {swept.get('archived_notifications', 0)} "
-            "notification(s)"
+            f"notification(s), {swept.get('archived_merge_queue', 0)} "
+            "merge_queue entry(ies)"
         ),
         details=swept,
     )
@@ -8500,14 +8501,17 @@ def build_app(store: CoordStore, config: Config, *, token: str | None = None) ->
 
                         os.environ["COORD_HOUSEKEEPING_ON_DAEMON"] = "1"
                         swept = await run_in_threadpool(_hk.sweep)
-                        if swept.get("archived_assignments") or swept.get(
-                            "archived_notifications"
+                        if (
+                            swept.get("archived_assignments")
+                            or swept.get("archived_notifications")
+                            or swept.get("archived_merge_queue")
                         ):
                             log.info(
                                 "housekeeping: archived %d assignment(s), "
-                                "%d notification(s)",
+                                "%d notification(s), %d merge_queue entry(ies)",
                                 swept["archived_assignments"],
                                 swept["archived_notifications"],
+                                swept.get("archived_merge_queue", 0),
                             )
                             _audit_housekeeping_sweep(swept)
                     except Exception:  # noqa: BLE001

{code_coordinator-0.5.262 → code_coordinator-0.5.264}/coord/skills/coord-dispatch-verbs/SKILL.md

@@ -1,3 +1,9 @@
+---
+name: coord-dispatch-verbs
+description: "Use before running a `coord` CLI command to enqueue, dispatch, stage, or otherwise move a GitHub issue through the coordinator — disambiguates ~70 top-level commands with similarly-named pairs that silently do the wrong thing instead of erroring."
+trigger: About to run a `coord` command to move an issue forward, especially when unsure of the exact subcommand, or a command exited 0 but the expected effect didn't happen.
+---
+
 # coord-dispatch-verbs skill
 
 **Trigger:** About to run a `coord` command to enqueue, dispatch, stage, or

{code_coordinator-0.5.262 → code_coordinator-0.5.264}/coord/skills/drive-queue-preflight/SKILL.md

@@ -1,3 +1,9 @@
+---
+name: drive-queue-preflight
+description: "Use before queuing more than ~2 issues on one repo with `coord drive-queue add`, setting up an overnight/unattended run, or seeing a QUEUE: STALLED/BLOCKED status-bar alert — gives the real cost model and the read-the-alert table."
+trigger: "About to `coord drive-queue add` deep on one repo, or looking at a QUEUE: STALLED/BLOCKED alert."
+---
+
 # drive-queue-preflight skill
 
 **Trigger:** About to `coord drive-queue add` more than ~2 issues on one repo,

{code_coordinator-0.5.262 → code_coordinator-0.5.264}/coord/skills/fleet-restart-safety/SKILL.md

@@ -1,3 +1,9 @@
+---
+name: fleet-restart-safety
+description: "Use before restarting coord-agent/coord-serve or editing coordinator.yml on a live fleet — the two restarts kill different things (headless workers vs. interactive finalize) and neither warns you the way you'd expect."
+trigger: About to restart coord-agent (incl. `coord agent update`) or coord-serve, or edit coordinator.yml/coordinator.remote.yml on a live fleet.
+---
+
 # fleet-restart-safety skill
 
 **Trigger:** About to restart `coord-agent` (including `coord agent update`)

{code_coordinator-0.5.262 → code_coordinator-0.5.264}/coord/skills/merge-stuck-triage/SKILL.md

@@ -1,3 +1,9 @@
+---
+name: merge-stuck-triage
+description: "Use when a story won't merge — the TUI Go does nothing, `coord merge` skips it, or the queue box stays grey/pending — walks the merge gates in the order they actually block instead of guessing."
+trigger: A story won't merge, or an operator asks why something isn't merging.
+---
+
 # merge-stuck-triage skill
 
 **Trigger:** A story won't merge — the TUI "Go" does nothing, `coord merge` skips

{code_coordinator-0.5.262 → code_coordinator-0.5.264}/coord/skills/pipeline-limbo-triage/SKILL.md

@@ -1,3 +1,9 @@
+---
+name: pipeline-limbo-triage
+description: "Use when an issue sits in the Pipeline with no dispatch or visible activity — explains that Board vs Pipeline membership is label-driven, not assignment-driven, and gives the one-command fix."
+trigger: An issue shows up in the Pipeline but nobody dispatched it, or a Pipeline card looks stuck.
+---
+
 # pipeline-limbo-triage skill
 
 **Trigger:** An issue shows up in the Pipeline but nobody dispatched it, a

{code_coordinator-0.5.262 → code_coordinator-0.5.264}/coord/skills/portal-followup/SKILL.md

@@ -1,3 +1,9 @@
+---
+name: portal-followup
+description: "Use when investigating a customer-portal signoff/event that hasn't shown up, or troubleshooting `coord portal` state — gets a straight answer out of outbox/events/sync instead of confusing local-machine state with the bridge's own."
+trigger: Investigating a stuck customer-portal signoff/event, or any `coord portal` state troubleshooting.
+---
+
 # portal-followup skill
 
 **Trigger:** Investigating a customer-portal signoff/event that "hasn't shown up"