@feigi/fleet-ctl 3.76.6 → 3.76.8

package/agents/fleet-finisher.agent.md

@@ -53,7 +53,23 @@ tree — so an exit 2 naming a moved or unreadable audited tree is a halt
 like every other, not a spelling for you to correct.
 
 **Confirm every deferral — and every claimed APPLY — has a home that outlives
-the merge.** The test is a durable home, not a tracker number: a tracker
+the merge.** A deferral of a finding in the review's result is not yours to
+re-judge when the PR's latest review counted a survived or unverified finding:
+`ledger.mjs dispatch` then dispatched you only once the PR's ledger row held a
+`dispositions-ok` verdict from `dispositions-check.mjs` on that review
+(`dispositionsRefusal`), and that check had already read back where the
+fix-applier's disposition record says each deferral was filed. That verdict is
+the judgement of those homes: do not halt on a home the script accepted, and
+do not re-file one as an open issue. One such home is the PR's own
+`PR #<M> review: the suggestion band, checked` issue, which counts although it
+is closed and labelled `wontfix`. Where the latest review counted no survived
+and no unverified finding, dispatch required no verdict; that record is still
+a home there when it matches the script's own definition — `homeHolds` in
+`dispositions-check.mjs`: state `CLOSED`, labelled `wontfix`, titled exactly
+`recordTitle(<M>)` — and any other closed issue is not. Everything else — a
+claimed APPLY, a deferral the review's result does not carry, and a deferral
+no verdict judged — you judge by hand, by the test below. The test is a
+durable home, not a tracker number: a tracker
 issue and a committed in-tree comment both qualify, and for a finding whose
 remedy was measured worse than the defect the in-tree note is the better one.
 What fails is a promise living only in a PR body, or on the PR's *own* source

package/package.json

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

package/scripts/tier-check.mjs

@@ -22,8 +22,10 @@
 //      readers — a member with no assistant turn yet still resolves off its
 //      dispatch-time `session_init` record, never treated as absent). An
 //      entry that names neither a `session` nor a `transcript` takes the
-//      `session` the phase-0 receipt `.fleet/phase0.json` records, and is
-//      exit 2 naming the receipt when it records none. That session is taken
+//      `session` the phase-0 receipt `.fleet/phase0.json` records — the one
+//      in the workspace holding `--ledger`, or the cwd's when `--ledger` is
+//      omitted, resolved the same way the default ledger is — and is exit 2
+//      naming the receipt when it records none. That session is taken
 //      as the receipt stands: whether the receipt is this run's is judged by
 //      fleet-tick.mjs's phase-0 gate, not here, and a message about it names
 //      the receipt's session where it would name `--session`.
@@ -77,14 +79,16 @@
 // LIVE member may yet write one; a member settled `PR#M`, `bailed`, `blocked`
 // or `tier-mismatch` ran, so its transcript exists and the `session` is the
 // wrong directory; a `session` that is empty, missing or not a directory,
-// or omitted with none in the phase-0 receipt, is exit 2 whether the member
-// is live or settled; and a session
+// or omitted with none in the phase-0 receipt — a `--ledger` outside any
+// repository or in a directory that does not exist among them, since no
+// workspace holds it and so there is no receipt to read — is exit 2 whether
+// the member is live or settled; and a session
 // directory that cannot be searched (EACCES) is exit 2 naming the errno,
 // never read as holding no transcript.
 
 import { readFileSync, existsSync, statSync } from "node:fs";
 import { execFileSync } from "node:child_process";
-import { join, dirname, isAbsolute } from "node:path";
+import { join, dirname, isAbsolute, resolve } from "node:path";
 import { fileURLToPath } from "node:url";
 import { isCLI } from "./is-cli.mjs";
 import { makeDie, defineFlags } from "./arg.mjs";
@@ -328,6 +332,19 @@ function sessionLacksTranscript(repoRoot, sessionPath, member) {
 // tier can still be judged.
 const NO_TRANSCRIPT_OUTCOMES = new Set(["killed", "released"]);
 
+// Where the phase-0 receipt is read from: the workspace the ledger in use
+// belongs to, so a `--ledger` naming another workspace's judges that
+// workspace's transcripts, not the cwd's. `--ledger` takes any path, not
+// always one under a `.fleet/` — so the workspace is the one git names for
+// the ledger's directory, the same answer ledger.mjs's own default gives
+// from the cwd. A ledger under no repository, or in a directory that does not
+// exist, has no workspace and so no receipt: sessionFromReceipt refuses
+// naming why, and the whole batch is exit 2 with nothing written. Omitted,
+// the cwd's.
+function receiptOpts(ledgerFile) {
+  return ledgerFile ? { cwd: dirname(resolve(ledgerFile)) } : undefined;
+}
+
 function runLedger(ledgerFile, args, what) {
   try {
     return execFileSync(process.execPath, [LEDGER_SCRIPT, ...(ledgerFile ? ["--file", ledgerFile] : []), ...args], { encoding: "utf8" });
@@ -480,7 +497,7 @@ function main() {
         // session directory the phase-0 receipt records — read once per
         // batch — and refuses naming the receipt when it records none. A
         // given one always wins.
-        const session = raw.session ?? (raw.transcript ? undefined : (receiptSession ??= sessionFromReceipt()));
+        const session = raw.session ?? (raw.transcript ? undefined : (receiptSession ??= sessionFromReceipt(receiptOpts(ledgerFile))));
         // Said as the caller's flag only when the caller gave it.
         const where = raw.session ? `--session ${session}` : `the phase-0 receipt's session ${session}`;
         if (session) {

package/skills/run-team/SKILL.md

@@ -740,10 +740,11 @@ dispatched under.
 Pull, a batch of one, the member just dispatched: `{member}`.
 `member` is the AgentId the dispatch returns (`impl-<N>`). An entry that
 names neither `session` nor `transcript` takes the session directory phase
-0's receipt `.fleet/phase0.json` records, and is exit 2 naming the receipt
-when it records none; the check reads the member's own
-`<session>/<member>.jsonl` directly, so a member with no assistant turn yet
-still resolves off its dispatch-time record. A `session` the entry gives
+0's receipt `.fleet/phase0.json` of `--ledger`'s workspace (else the cwd's,
+resolved as the default ledger is) records, and is exit 2 naming the receipt
+when it records none; the check reads `<session>/<member>.jsonl`, so a
+member with no assistant turn yet still resolves off its dispatch-time
+record. A `session` the entry gives
 wins over the receipt's; a caller already holding the exact transcript path
 may give `transcript` instead. The agent type an implementer was dispatched
 as lives only in its transcript. `resolvedModel`

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

@@ -18,7 +18,23 @@ What does not empty it is noticing the question and dispatching anyway.
 ## Duty 2: every deferral, and every claimed APPLY, has a home that outlives the merge
 
 **Confirm every deferral — and every claimed APPLY — has a home that outlives
-   the merge.** The test is a durable home, not a tracker number: a tracker
+   the merge.** A deferral of a finding in the review's result is not yours to
+   re-judge when the PR's latest review counted a survived or unverified finding:
+   `ledger.mjs dispatch` then dispatched you only once the PR's ledger row held a
+   `dispositions-ok` verdict from `dispositions-check.mjs` on that review
+   (`dispositionsRefusal`), and that check had already read back where the
+   fix-applier's disposition record says each deferral was filed. That verdict is
+   the judgement of those homes: do not halt on a home the script accepted, and
+   do not re-file one as an open issue. One such home is the PR's own
+   `PR #<M> review: the suggestion band, checked` issue, which counts although it
+   is closed and labelled `wontfix`. Where the latest review counted no survived
+   and no unverified finding, dispatch required no verdict; that record is still
+   a home there when it matches the script's own definition — `homeHolds` in
+   `dispositions-check.mjs`: state `CLOSED`, labelled `wontfix`, titled exactly
+   `recordTitle(<M>)` — and any other closed issue is not. Everything else — a
+   claimed APPLY, a deferral the review's result does not carry, and a deferral
+   no verdict judged — you judge by hand, by the test below. The test is a
+   durable home, not a tracker number: a tracker
    issue and a committed in-tree comment both qualify, and for a finding whose
    remedy was measured worse than the defect the in-tree note is the better one.
    What fails is a promise living only in a PR body, or on the PR's *own* source