@feigi/fleet-ctl 3.82.4 → 3.82.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@feigi/fleet-ctl",
-  "version": "3.82.4",
+  "version": "3.82.5",
   "description": "Agent fleet: run-team controller, merge bot, PR reviewer, and the ticket pipeline they share",
   "license": "Apache-2.0",
   "repository": {

package/skills/run-team/SKILL.md

@@ -599,7 +599,7 @@ worktree re-created for an already-open PR is in references/isolation.md.
 | 1 `LEFT #N: taken …` | in-flight hit, an in-flight check that could not answer, or `claim-ticket.sh` exit 2 | next entry |
 | 1 `LEFT #N: relabelled elsewhere` | no longer labelled `ready-for-agent` | next entry |
 | 1 `LEFT #N: closed: fixed by …` | `close` answered `yes` | next entry |
-| 1 `LEFT #N: relabelled <label>: …` | `decided` answered with a cause | next entry |
+| 1 `LEFT #N: relabelled <label>: …` | `decided` answered with a cause, or a stranded ruling | next entry |
 | 1 `LEFT #N: excluded …` | `collision` answered `behind-pr:#M` or `behind-issue:#M`, or its ledger exclusion stands | next entry |
 | 1 `EMPTY` | the shortlist holds no entry to pull | run `shortlist.mjs` once and Pull again; still empty, hold the slot idle until the next refresh trigger |
 | 2 | could not look, named on stderr | as the entry paragraph says |
@@ -1771,7 +1771,7 @@ above and every row of the table below already applied; every wake
 ends in it. The deficit is then *computed, not remembered*, which is
 the whole point: a table you must remember to consult is one you will not
 consult under a merge-side event storm, and that is how implementers reached
-0/target with one approved ticket waiting and ~57 `ready-for-agent` in supply while nobody
+0/target with ~57 `ready-for-agent` in supply while nobody
 noticed (#3). What follows stays here as the explanation of what the script decides —
 never as a second, hand-run copy of it. The table's shortlist counts no head
 whose Pull ended this run. A refresh at unclaimed < B leaves `unclaimed=` at

package/skills/run-team/references/pull.md

@@ -242,6 +242,7 @@ does:
 |---|---|
 | in-flight hit, or an in-flight check that could not answer | drop, next entry |
 | no longer labelled `ready-for-agent` | drop, next entry |
+| a stranded ruling: a `## Ruling` or `## Triage` comment newer than the last `## Agent Brief`, or on a ticket with none | relabel `ready-for-human`, next entry |
 | `staleness.mjs` exit 1 — provably fixed | close citing the commit, next entry |
 | brief names no *what* | relabel `needs-triage`, next entry |
 | genuine fork — options named, none ruled | relabel `ready-for-human`, next entry |
@@ -266,8 +267,11 @@ that trusted a list built before the relabel landed would hand a ticket the
 fleet has already judged unimplementable straight to the next member.
 
 **Relabel by cause.** An unclaimed ticket is yours to reclassify at the Pull —
-three causes, two labels: `ready-for-human` for hands or a fork;
-`needs-triage` for a brief that names no *what*.
+`ready-for-human` for hands or a fork; `needs-triage` for a brief that names no
+*what*. A stranded ruling relabels to `ready-for-human` as well, but it is never
+yours to judge: `pull.mjs` finds it at step 3 and posts its own comment naming
+the stranded comment's heading line and URL, which is not one of the
+`briefs/relabel.md` comments.
 `gh issue edit <N> --remove-label ready-for-agent --add-label <label>` (no
 `in-progress` to drop — it was never claimed), preceded by exactly one comment,
 the one `~/.fleet/bin/fleet-run dispatch-prompt.mjs render relabel --kind <kind> …`
@@ -280,8 +284,9 @@ live in `briefs/relabel.md`; `pull.mjs` posts its own one-line copy of the same
 words when a Pull answer relabels, so a change to either is a change to both.
 
 Neither label invokes anything: `/triage` is maintainer-run, and both labels
-only stop the ticket costing a read per scan. These comments are the only
-writes the fleet makes to a ticket it did not claim.
+only stop the ticket costing a read per scan. These comments, the
+stranded-ruling comment and the comment closing a provably fixed ticket are the
+only writes the fleet makes to a ticket it did not claim.
 
 **Exclusion is a ticket row with a premise.** `ledger.mjs row <N> "excluded ·
 behind-pr:#M"` or `ledger.mjs row <N> "excluded · behind-issue:#M"` — `#M` is