@feigi/fleet-ctl 3.21.1 → 3.21.2

package/package.json

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

package/scripts/citation-sweep-prose.test.mjs

@@ -575,8 +575,12 @@ const FILES = [
   },
   {
     path: ["scripts", "review-core-snapshot-path.test.mjs"],
-    stale: [/select-dimensions\.test\.mjs:251-256/],
-    live: ["resolveDimensions"],
+    // #2546. The test once cited a `required:` comment inside
+    // `FINDINGS_SCHEMA` in review-core.mjs, which that file does not carry —
+    // the comment lived in the deleted review-pr.js. The stale form is that
+    // dangling citation; the live needle is the spec that now holds the quote.
+    stale: [/select-dimensions\.test\.mjs:251-256/, /`required:` comment inside `FINDINGS_SCHEMA` in review-core\.mjs/],
+    live: ["resolveDimensions", "2026-09-08-omp-eval-workflow-host.md"],
   },
   {
     path: ["scripts", "run-merge-bot-prose.test.mjs"],

package/scripts/review-core-snapshot-path.test.mjs

@@ -66,11 +66,17 @@ test("a fully verified snapshot is not missing", () => {
 //
 // A falsy `snap` is the agent contract failing — it died, or the harness
 // exhausted structured-output retries and `agent()` returned null — not a
-// claim about the tree on disk, which may be perfectly good. The citation is
-// the `required:` comment inside `FINDINGS_SCHEMA` in review-core.mjs, which
-// records that a schema REJECTION is retried and every observed one recovered:
-// exhaustion is the only one of the two that returns null, so naming rejection
-// as the cause would point an operator at a signature successful runs carry.
+// claim about the tree on disk, which may be perfectly good. The reason names
+// `died` and `exhausted` but never `rejected`: a schema REJECTION is handed
+// back to the model as a tool error and retried, and the rejections measured
+// under Claude Code all recovered on retry (docs/specs/2026-09-08-omp-eval-workflow-host.md,
+// Q2, quoting the "184 rejection events … every one recovered by retry"
+// comment that review-pr.js carried inside its FINDINGS_SCHEMA, in the
+// comment block above `required:`, until the omp-only cutover deleted that
+// file). A rejection is therefore a signature successful runs
+// carry, and naming it as the cause of a null would point an operator at the
+// wrong thing. review-eval.mjs's `ompAgent` comment records the omp side: a
+// rejected `.wait()` maps to null there.
 test("a falsy snapshot (agent died, or it exhausted its structured-output retries) names the agent contract, not a missing tree", () => {
   for (const dead of [null, undefined, false]) {
     const reason = snapshotMissing(dead);