@feigi/fleet-ctl 3.137.4 → 3.138.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (50) hide show
  1. package/agents/fleet-finisher.agent.md +8 -8
  2. package/agents/fleet-fix-applier.agent.md +1 -1
  3. package/agents/fleet-merge-bot.agent.md +1 -1
  4. package/agents/fleet-recipe-deriver.agent.md +5 -5
  5. package/agents/fleet-review-runner.agent.md +1 -1
  6. package/commands/review-and-fix.md +11 -11
  7. package/commands/run-merge-bot.md +9 -9
  8. package/package.json +1 -1
  9. package/scripts/claim-ticket.sh +1 -1
  10. package/scripts/controller-alarm.mjs +1 -1
  11. package/scripts/evict-mark.mjs +1 -1
  12. package/scripts/finisher-audit.mjs +1 -1
  13. package/scripts/finisher-label.mjs +1 -1
  14. package/scripts/finisher-tree.mjs +1 -1
  15. package/scripts/fleet-provenance +9 -52
  16. package/scripts/fleet-run +5 -10
  17. package/scripts/fleet-tick.mjs +3 -3
  18. package/scripts/instruments.sh +3 -4
  19. package/scripts/ledger.mjs +1 -1
  20. package/scripts/main-checkout.mjs +1 -1
  21. package/scripts/phase0-receipt.mjs +1 -1
  22. package/scripts/preflight.mjs +0 -1
  23. package/scripts/recipe-check.mjs +1 -1
  24. package/scripts/repo-root.mjs +1 -1
  25. package/scripts/report-schema.mjs +1 -1
  26. package/scripts/review-core.mjs +6 -6
  27. package/scripts/review-eval.mjs +1 -1
  28. package/scripts/ticketless.mjs +1 -1
  29. package/skills/next-ticket/SKILL.md +8 -8
  30. package/skills/run-team/SKILL.md +22 -34
  31. package/skills/run-team/briefs/finisher.md +2 -2
  32. package/skills/run-team/briefs/fix-applier.md +9 -9
  33. package/skills/run-team/briefs/implementer.md +3 -3
  34. package/skills/run-team/briefs/merge-bot.md +2 -2
  35. package/skills/run-team/references/ci-and-staleness.md +1 -1
  36. package/skills/run-team/references/ci-watcher.md +1 -1
  37. package/skills/run-team/references/close-out.md +5 -5
  38. package/skills/run-team/references/failure-handling.md +2 -2
  39. package/skills/run-team/references/finisher.md +2 -2
  40. package/skills/run-team/references/instruments.md +1 -1
  41. package/skills/run-team/references/isolation.md +3 -3
  42. package/skills/run-team/references/ledger.md +1 -1
  43. package/skills/run-team/references/member-lifecycle.md +1 -1
  44. package/skills/run-team/references/phase-0.md +20 -20
  45. package/skills/run-team/references/pull.md +18 -10
  46. package/skills/run-team/references/reaping.md +13 -1
  47. package/skills/run-team/references/reviewers.md +9 -1
  48. package/skills/run-team/references/tick-rows.md +2 -2
  49. package/skills/sizing-a-ticket/SKILL.md +1 -1
  50. package/scripts/fleet-bootstrap +0 -140
@@ -2,23 +2,19 @@
2
2
  // The Provenance check (CONTEXT.md § Install
3
3
  // "Provenance check"). Names the live Install root — the realpath of omp's
4
4
  // `node_modules/@feigi/fleet-ctl` package entry, the one path every install kind
5
- // places — its kind and recorded version, and hashes the placed
6
- // Resolver (`~/.fleet/bin/fleet-run`) against the Install root's own copy and
7
- // refuses on drift. Writes nothing, mutates no config — every path below is
8
- // read-only.
5
+ // places — its kind and recorded version, and a digest over its scripts/.
6
+ // Exits 0 when the package entry resolves and 2 when it does not. Writes
7
+ // nothing, mutates no config — every path below is read-only.
9
8
  //
10
9
  // The `enabledProviders: ["claude-plugins"]` assertion retired here: omp
11
10
  // 18.2.1 exempts omp-origin installs from
12
11
  // that provider gate, and the native package route never depended on it.
13
12
  // Asserting it refused correct setups.
14
13
  //
15
- // SEPARATE FILE, not `fleet-run --check`. `fleet-run` is deliberately a
16
- // single self-contained file because it alone gets copied to
17
- // `~/.fleet/bin/fleet-run` (see that file's own header) — folding a second,
18
- // unrelated responsibility into it would grow the one artefact outside the
19
- // plugin for a feature that never needs to travel there. This script stays
20
- // inside the install and is reached like every other one, through the
21
- // Resolver: `fleet-run fleet-provenance`.
14
+ // SEPARATE FILE, not `fleet-run --check`. `fleet-run` is the single door
15
+ // between prose and a script, and maps a script name to the Install root and
16
+ // nothing else; this check is one more script behind that door, reached like
17
+ // every other one, through the Resolver: `fleet-run fleet-provenance`.
22
18
  "use strict";
23
19
 
24
20
  const fs = require("node:fs");
@@ -30,9 +26,8 @@ const NAME = "fleet-provenance";
30
26
  const PLUGIN_KEY = "@feigi/fleet-ctl"; // the plugin's package name, and its node_modules package dir.
31
27
 
32
28
  // Same resolution point as scripts/fleet-run (its header names the shape of
33
- // each install kind). Duplicated rather than shared because a module the
34
- // Resolver requires would have to travel with its placed copy — see
35
- // fleet-run's own header.
29
+ // each install kind), resolved in this file's own lines: fleet-run requires
30
+ // nothing from the rest of the plugin, so there is no shared module to call.
36
31
  function resolveInstall(home) {
37
32
  const packagePath = path.join(home, ".omp", "plugins", "node_modules", PLUGIN_KEY);
38
33
  let stat;
@@ -132,17 +127,6 @@ function main() {
132
127
  process.exit(2);
133
128
  }
134
129
 
135
- const placedPath = path.join(home, ".fleet", "bin", "fleet-run");
136
- let placedBuf = null;
137
- let placedError = null;
138
- try {
139
- placedBuf = fs.readFileSync(placedPath);
140
- } catch (e) {
141
- placedError = `${e.code || e.message}`;
142
- }
143
-
144
- let failed = false;
145
-
146
130
  const kind = kindOf(reg);
147
131
  const version = readLockVersion(home);
148
132
  process.stdout.write(`${NAME}: Install root: ${reg.installPath}\n`);
@@ -156,31 +140,6 @@ function main() {
156
140
  process.stdout.write(`${NAME}: scripts/ digest: sha256 ${digest.digest} (${digest.fileCount} files)\n`);
157
141
  }
158
142
 
159
- const installedRunPath = path.join(reg.installPath, "scripts", "fleet-run");
160
- let installedRunBuf = null;
161
- let installedRunError = null;
162
- try {
163
- installedRunBuf = fs.readFileSync(installedRunPath);
164
- } catch (e) {
165
- installedRunError = `${e.code || e.message}`;
166
- }
167
-
168
- if (placedError) {
169
- process.stdout.write(`${NAME}: Resolver drift: REFUSED — placed copy ${placedPath} unreadable (${placedError})\n`);
170
- failed = true;
171
- } else if (installedRunError) {
172
- process.stdout.write(`${NAME}: Resolver drift: REFUSED — installed copy ${installedRunPath} unreadable (${installedRunError})\n`);
173
- failed = true;
174
- } else if (!placedBuf.equals(installedRunBuf)) {
175
- process.stdout.write(
176
- `${NAME}: Resolver drift: REFUSED — ${placedPath} (sha256 ${sha256(placedBuf)}) `
177
- + `!= ${installedRunPath} (sha256 ${sha256(installedRunBuf)})\n`,
178
- );
179
- failed = true;
180
- } else {
181
- process.stdout.write(`${NAME}: Resolver drift: none — ${placedPath} matches ${installedRunPath}\n`);
182
- }
183
-
184
143
  if (kind === "linked-checkout") {
185
144
  // Not a failure: a link is the dev loop. It is a NOTICE on
186
145
  // every other install's answer, because a linked root outranks an
@@ -191,8 +150,6 @@ function main() {
191
150
  + "every fleet-run answer above came from that checkout, not from an installed release.\n",
192
151
  );
193
152
  }
194
-
195
- process.exit(failed ? 1 : 0);
196
153
  }
197
154
 
198
155
  main();
package/scripts/fleet-run CHANGED
@@ -19,16 +19,11 @@
19
19
  // CI dependency — node is (the whole test suite is `node --test`). node's
20
20
  // `realpathSync` is exact and already required.
21
21
  //
22
- // SINGLE FILE, ON PURPOSE. `fleet-bootstrap` places a copy of exactly this
23
- // file at `~/.fleet/bin/fleet-run`, OUTSIDE the plugin (CONTEXT.md's
24
- // Resolver entry: "cannot resolve itself"). Once there it has no siblings —
25
- // `scripts/repo-root.mjs`, `scripts/arg.mjs` and every other shared helper
26
- // in this directory are unreachable from that path. So this file requires
27
- // nothing from the rest of the plugin (CommonJS, core `node:*` modules
28
- // only) even though `scripts/fleet-provenance` duplicates a couple of lines
29
- // of its resolution logic rather than sharing a module with it, for the same
30
- // reason: a module this file `require()`s would need to travel with it, and
31
- // nothing else does.
22
+ // SINGLE FILE. Prose runs this file where the package holds it,
23
+ // `scripts/fleet-run` under the package entry above. It requires nothing from
24
+ // the rest of the plugin (CommonJS, core `node:*` modules only), and
25
+ // `scripts/fleet-provenance` and `scripts/instruments.sh` resolve the Install
26
+ // root the same way in their own lines rather than calling it.
32
27
  "use strict";
33
28
 
34
29
  const fs = require("node:fs");
@@ -249,7 +249,7 @@ const mkRow = (role, actual, target, detail) => (action, { acts = false, extra =
249
249
  // `<file>` does — one batch file, one entry per held member, the shape under
250
250
  // **The batch file is a JSON array, one entry per dispatched member** in
251
251
  // run-team/references/tick-rows.md.
252
- const tierCheckStep = (members, session) => "run ~/.fleet/bin/fleet-run tier-check.mjs --batch <file> with "
252
+ const tierCheckStep = (members, session) => "run ~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run tier-check.mjs --batch <file> with "
253
253
  + JSON.stringify(members.map((member) => (session ? { member } : { member, session: "<session>" })));
254
254
 
255
255
  // A mismatch clears when the next attempt on the ticket is dispatched at its
@@ -442,9 +442,9 @@ function reviewers(s) {
442
442
  // turns a record-only line into a HOLD.
443
443
  const conflictRows = [];
444
444
  if (s.conflicts.length) {
445
- const record = s.conflicts.map((n) => `~/.fleet/bin/fleet-run ledger.mjs row <key> "<text> · conflict-hold:#${n} (conflict: mergeable=CONFLICTING)" on the row naming PR#${n}`);
445
+ const record = s.conflicts.map((n) => `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run ledger.mjs row <key> "<text> · conflict-hold:#${n} (conflict: mergeable=CONFLICTING)" on the row naming PR#${n}`);
446
446
  conflictRows.push(row(`CONFLICT ${prs(s.conflicts)}`,
447
- { acts: true, extra: `GitHub reads CONFLICTING; ~/.fleet/bin/fleet-run ledger.mjs read, then ${record.join("; ")}` }));
447
+ { acts: true, extra: `GitHub reads CONFLICTING; ~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run ledger.mjs read, then ${record.join("; ")}` }));
448
448
  }
449
449
  if (s.conflictEscalate.length) {
450
450
  conflictRows.push(row(`ESCALATE conflict ${prs(s.conflictEscalate)}`,
@@ -183,10 +183,9 @@ fi
183
183
  base="$root/.fleet/instruments.sha"
184
184
 
185
185
  # The Install root, resolved inline on every pin and every check: the same
186
- # path fleet-run, fleet-provenance and fleet-bootstrap resolve, the same way —
187
- # the package entry's own link-ness for the kind, its realpath for the tree.
188
- # Mirrored rather than called. The placed `~/.fleet/bin/fleet-run` can drift
189
- # from the package, and an environment override or a `node` call would be a
186
+ # path fleet-run and fleet-provenance resolve, the same way — the package
187
+ # entry's own link-ness for the kind, its realpath for the tree. Mirrored
188
+ # rather than called: an environment override or a `node` call would be a
190
189
  # second way to name a tree the fleet does not execute.
191
190
  #
192
191
  # HOME is checked by hand because `set -u` does not answer for it: measured,
@@ -2023,7 +2023,7 @@ async function rulingOf(pr) {
2023
2023
  if (ruling !== undefined) return { tickets, ruling, tsv, refusal: null };
2024
2024
  }
2025
2025
  return { tickets, ruling: null, refusal: `PR #${pr}, the implementer PR of ${tickets.length === 1 ? "ticket" : "tickets"} ${tickets.map((n) => `#${n}`).join(", ")}, has no ruling — `
2026
- + `${tsv} has no row for it; rule its review with \`~/.fleet/bin/fleet-run tier-outcomes.mjs append ${pr}\`, `
2026
+ + `${tsv} has no row for it; rule its review with \`~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run tier-outcomes.mjs append ${pr}\`, `
2027
2027
  + "then dispatch the finisher again" };
2028
2028
  }
2029
2029
 
@@ -126,7 +126,7 @@ import { makeDie, defineFlags } from "./arg.mjs";
126
126
  import { gitEnv, mainCheckoutDirFromGitCommonDir } from "./git-env.mjs";
127
127
 
128
128
  export const BASELINE_FILE = "main-checkout.sha";
129
- export const RECORD_COMMAND = "~/.fleet/bin/fleet-run main-checkout.mjs --record";
129
+ export const RECORD_COMMAND = "~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run main-checkout.mjs --record";
130
130
  const RUN_BOOKKEEPING = new Set(["docs/metrics/tier-outcomes.tsv", "docs/metrics/member-outcomes.tsv", "docs/metrics/ticket-features.tsv"]);
131
131
  // Any change to an entry's hash or to a line's format bumps VERSION: a
132
132
  // baseline an older plugin wrote then reads `outdated` (re-record) and one a
@@ -76,7 +76,7 @@ export function readRunReceipt(opts) {
76
76
  // With no recorded session the remedy is the eval-cell run: phase0.mjs falls
77
77
  // back to PI_ARTIFACTS_DIR, which the bash tool's environment carries none of.
78
78
  const phase0Command = (session) => session
79
- ? `~/.fleet/bin/fleet-run phase0.mjs --session ${session}`
79
+ ? `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run phase0.mjs --session ${session}`
80
80
  : "phase0.mjs from a Python eval cell in the main checkout, without --session (run-team SKILL.md phase 0 step 0)";
81
81
 
82
82
  /**
@@ -75,7 +75,6 @@ export const CHECKS = [
75
75
  { name: "allow-merge-commit", argv: ["gh", "api", "repos/{owner}/{repo}", "--jq", ".allow_merge_commit"], want: "true" },
76
76
  { name: "ruleset", argv: ["gh", "api", "repos/{owner}/{repo}/rulesets", "--jq", ".[].name"], want: NONEMPTY },
77
77
  { name: "ci-workflow", argv: ["sh", "-c", CI_NAMED], warn: true },
78
- { name: "resolver", argv: ["~/.fleet/bin/fleet-run", "--root"] },
79
78
  ];
80
79
 
81
80
  /** sha256 over every row's name, argv, want and warn, in table order. */
@@ -7,7 +7,7 @@
7
7
  //
8
8
  // Run from the member's worktree, after `git add` and before the commit and
9
9
  // push, and again after any content change or rebase. Reached through the
10
- // Resolver: `~/.fleet/bin/fleet-run recipe-check.mjs ...`.
10
+ // Resolver: `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run recipe-check.mjs ...`.
11
11
  //
12
12
  // `--member` is the `impl-<N>[-x]` or `fix-pr-<M>[-x]` name the member was
13
13
  // dispatched as. `--testCmd` is the Test entrypoint exactly as the member was
@@ -533,7 +533,7 @@ function hasNodeShebang(path, buf) {
533
533
  * Every tracked file this repository ships that the consumer's own `node`
534
534
  * executes, in the working tree at `root`, repo-relative: each `*.mjs`, and
535
535
  * any other file whose first line is a node shebang — the extensionless
536
- * entrypoints `fleet-run`, `fleet-bootstrap` and `fleet-provenance`.
536
+ * entrypoints `fleet-run` and `fleet-provenance`.
537
537
  * A shebang decides, never an extension alone: `plugin/workflows/*.js` is ESM
538
538
  * a harness runs and plain node never loads, and carries none. Test files —
539
539
  * `*.test.mjs`, the one naming this repository gives them — are not shipped,
@@ -5,7 +5,7 @@
5
5
  // report-schema.mjs print <family>
6
6
  // report-schema.mjs validate <family> <file>
7
7
  //
8
- // Reached through the Resolver: `~/.fleet/bin/fleet-run report-schema.mjs ...`.
8
+ // Reached through the Resolver: `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run report-schema.mjs ...`.
9
9
  // <family> is one of `impl`, `fix-pr`, `finisher`, `merge-bot`. The review
10
10
  // runner is not a family here: its report already has a shape of its own.
11
11
  //
@@ -419,7 +419,7 @@ export function resolveTestCmd(explicit, snap) {
419
419
  // command is one word to the wrapper — it hands the string to `sh -c` itself —
420
420
  // so it is single-quoted here, each embedded `'` closed, escaped and reopened.
421
421
  function slotted(cmd) {
422
- return `~/.fleet/bin/fleet-run suite-slot.mjs '${cmd.replaceAll("'", "'\\''")}'`;
422
+ return `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run suite-slot.mjs '${cmd.replaceAll("'", "'\\''")}'`;
423
423
  }
424
424
 
425
425
  // The status suite-slot.mjs exits with when its wait for a slot expired.
@@ -1072,7 +1072,7 @@ export async function runReview(host, args) {
1072
1072
  mkdir -p "${runRootParent}" || { echo SNAPSHOT_RUNROOT_FAILED; exit 1; }
1073
1073
  RUN=$(mktemp -d "${runRootPrefix}XXXXXXXX") || { echo SNAPSHOT_RUNROOT_FAILED; exit 1; }
1074
1074
  echo SNAPSHOT_RUN_ROOT="$RUN"
1075
- ~/.fleet/bin/fleet-run reclaim-scratch.mjs --pr ${pr} --root "${scratch}" --apply | grep -qF '"failed":[]' || echo SNAPSHOT_PRUNE_FAILED
1075
+ ~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run reclaim-scratch.mjs --pr ${pr} --root "${scratch}" --apply | grep -qF '"failed":[]' || echo SNAPSHOT_PRUNE_FAILED
1076
1076
  SHA=$(git -C ${worktree} rev-parse --short HEAD) || { echo SNAPSHOT_REVPARSE_FAILED; exit 1; }
1077
1077
  SNAP="$RUN/snapshot-$SHA"
1078
1078
  echo SNAPSHOT_DEST="$SNAP"
@@ -1082,7 +1082,7 @@ export async function runReview(host, args) {
1082
1082
  ( cd "$SNAP" && git init -q && git add -A -f && git -c user.name=fleet -c user.email=fleet@invalid commit -q --no-verify -m "review snapshot of $SHA" ) || echo SNAPSHOT_INIT_FAILED
1083
1083
  SNAPTREE=$(git -C "$SNAP" rev-parse 'HEAD^{tree}' 2>/dev/null); SRCTREE=$(git -C ${worktree} rev-parse 'HEAD^{tree}')
1084
1084
  { [ -d "$SNAP/.git" ] && [ -n "$SNAPTREE" ] && [ "$SNAPTREE" = "$SRCTREE" ]; } && echo SNAPSHOT_TREE_MATCH || echo SNAPSHOT_TREE_MISMATCH="snapshot $SNAPTREE vs commit $SRCTREE"
1085
- INSTALL=$(~/.fleet/bin/fleet-run derive-testcmd.sh ${worktree} install) && echo SNAPSHOT_INSTALL_STEP="$INSTALL" || { INSTALL=; echo SNAPSHOT_INSTALL_UNREAD; }
1085
+ INSTALL=$(~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run derive-testcmd.sh ${worktree} install) && echo SNAPSHOT_INSTALL_STEP="$INSTALL" || { INSTALL=; echo SNAPSHOT_INSTALL_UNREAD; }
1086
1086
  [ -z "$INSTALL" ] || { ( cd "$SNAP" && env -u CI sh -c "$INSTALL" ) >"$RUN/install.log" 2>&1; echo SNAPSHOT_INSTALL_EXIT=$?; }
1087
1087
  if [ -d "$SNAP/.git" ] && git -C "$SNAP" status --porcelain --untracked-files=all >"$RUN/status.txt"; then head -n 20 "$RUN/status.txt" | sed 's/^/SNAPSHOT_UNTRACKED=/'; echo SNAPSHOT_UNTRACKED_COUNT=$(wc -l <"$RUN/status.txt" | tr -d ' '); else echo SNAPSHOT_STATUS_FAILED; fi
1088
1088
 
@@ -1203,7 +1203,7 @@ caller decide.
1203
1203
 
1204
1204
  Then read this repository's Test entrypoint out of its Recipe cache:
1205
1205
 
1206
- ~/.fleet/bin/fleet-run derive-testcmd.sh ${worktree} test
1206
+ ~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run derive-testcmd.sh ${worktree} test
1207
1207
 
1208
1208
  Report \`testCmd\` = its stdout ONLY if it exited 0. If it exited non-zero,
1209
1209
  report \`testCmdError\` = its stderr and omit \`testCmd\`. Never derive or
@@ -1214,7 +1214,7 @@ that instead of deriving.
1214
1214
  Then read, out of the same cache, the merge-gating CI steps that neither the
1215
1215
  Test entrypoint nor the Check step runs:
1216
1216
 
1217
- ~/.fleet/bin/fleet-run derive-testcmd.sh ${worktree} uncovered
1217
+ ~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run derive-testcmd.sh ${worktree} uncovered
1218
1218
 
1219
1219
  Report \`uncovered\` = its stdout, one line of JSON copied verbatim, ONLY if it
1220
1220
  exited 0. If it exited non-zero, report \`uncoveredError\` = its stderr and omit
@@ -1226,7 +1226,7 @@ it again because it is a separate command; the capture block above already
1226
1226
  reported why when it could not:
1227
1227
 
1228
1228
  REPO=$(cd ${worktree} && gh repo view --json url -q .url 2>/dev/null)
1229
- if [ -n "$REPO" ]; then ~/.fleet/bin/fleet-run diff-stats.mjs --pr ${pr} --repo "$REPO"; else echo SNAPSHOT_REPO_UNRESOLVED; fi
1229
+ if [ -n "$REPO" ]; then ~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run diff-stats.mjs --pr ${pr} --repo "$REPO"; else echo SNAPSHOT_REPO_UNRESOLVED; fi
1230
1230
 
1231
1231
  If that printed SNAPSHOT_REPO_UNRESOLVED, omit \`diffStats\`.
1232
1232
 
@@ -2,7 +2,7 @@
2
2
  // review-core.mjs directly) through
3
3
  // the Resolver, from an `eval` cell:
4
4
  //
5
- // const path = (await Bun.$`~/.fleet/bin/fleet-run --path review-eval.mjs`.text()).trim();
5
+ // const path = (await Bun.$`~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run --path review-eval.mjs`.text()).trim();
6
6
  // const { runReviewOnOmp } = await import(path);
7
7
  // const result = await runReviewOnOmp({ pr, branch, worktree, testCmd, scratch });
8
8
  //
@@ -16,7 +16,7 @@
16
16
  // it; `--ledger` names the ledger file instead. A ledger that cannot be
17
17
  // resolved is exit 2: `ledger.mjs`'s own cwd-relative fallback is never taken,
18
18
  // since an empty cwd-local ledger would answer Ticketless. Reached through the
19
- // Resolver: `~/.fleet/bin/fleet-run ticketless.mjs ...`.
19
+ // Resolver: `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run ticketless.mjs ...`.
20
20
  //
21
21
  // Stdout is one JSON line:
22
22
  //
@@ -18,13 +18,13 @@ Suggest ready tickets, maintainer picks, mark in-progress, implement at depth ti
18
18
  Before the query, run the Label map derivation step:
19
19
 
20
20
  ```bash
21
- ~/.fleet/bin/fleet-run label-map.mjs ensure
21
+ ~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run label-map.mjs ensure
22
22
  ```
23
23
 
24
- Exit 0 → the map is in place; go on. Exit 3 → it printed the question payload, a JSON object with `certain`, `uncertain` and `tableFile`, the path of the repository's triage-label table: render it to the maintainer as one question listing each uncertain role, its suggestion, why it is uncertain (a role declared in the table but not in the tracker names the payload's `tableFile`) and the alternatives, ending with "reply `defaults` to accept every suggestion, or name `<role>=<label>` for any you want otherwise — a role with no suggestion must be named; labels that do not exist are created on your confirmation". **Wait for the answer**, then run `~/.fleet/bin/fleet-run label-map.mjs set --create` with it — `--accept-suggestions` for `defaults`, plus each `<role>=<label>` the maintainer named — and run `ensure` again, which now exits 0. Tell the maintainer how to make the answer permanent: add or edit the row for the role in the file the payload's `tableFile` names, the role in the first cell and the string in the second; never write that table yourself. Exit 1 or 2 → show what it printed and stop; neither is a question.
24
+ Exit 0 → the map is in place; go on. Exit 3 → it printed the question payload, a JSON object with `certain`, `uncertain` and `tableFile`, the path of the repository's triage-label table: render it to the maintainer as one question listing each uncertain role, its suggestion, why it is uncertain (a role declared in the table but not in the tracker names the payload's `tableFile`) and the alternatives, ending with "reply `defaults` to accept every suggestion, or name `<role>=<label>` for any you want otherwise — a role with no suggestion must be named; labels that do not exist are created on your confirmation". **Wait for the answer**, then run `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run label-map.mjs set --create` with it — `--accept-suggestions` for `defaults`, plus each `<role>=<label>` the maintainer named — and run `ensure` again, which now exits 0. Tell the maintainer how to make the answer permanent: add or edit the row for the role in the file the payload's `tableFile` names, the role in the first cell and the string in the second; never write that table yourself. Exit 1 or 2 → show what it printed and stop; neither is a question.
25
25
 
26
26
  ```bash
27
- ~/.fleet/bin/fleet-run candidates.mjs --require-label ready-for-agent --allow-fallback
27
+ ~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run candidates.mjs --require-label ready-for-agent --allow-fallback
28
28
  ```
29
29
 
30
30
  Script owns the query: label exclusions server-side, raw `body` never fetched for
@@ -55,7 +55,7 @@ Cut runs on step 1 data alone — number, title, labels, `d` — never the Agent
55
55
  ## 3. In-flight check (all three, per candidate) — then fetch
56
56
 
57
57
  ```bash
58
- ~/.fleet/bin/fleet-run inflight.sh <N> # 0 free, 1 taken, 2 unanswerable
58
+ ~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run inflight.sh <N> # 0 free, 1 taken, 2 unanswerable
59
59
  ```
60
60
 
61
61
  Runs all three — a PR about the ticket, a remote branch, a local worktree or branch. Exit 1 → taken. "Shipped" memory not proof; open PR means unmerged. Exit 2 is not free: the question went unanswered (`gh` failed, no such issue, not a repo), so treat it as taken until you know.
@@ -87,9 +87,9 @@ Ask which. **Wait for answer.** Maintainer says taken → drop, re-suggest.
87
87
  gh issue edit <N> --add-label "<in-progress string>"
88
88
  ```
89
89
 
90
- `<in-progress string>` is what `~/.fleet/bin/fleet-run label-map.mjs show in-progress` prints. The derivation step in step 1 already confirmed the label exists in the tracker, creating it on the maintainer's confirmation where it was missing.
90
+ `<in-progress string>` is what `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run label-map.mjs show in-progress` prints. The derivation step in step 1 already confirmed the label exists in the tracker, creating it on the maintainer's confirmation where it was missing.
91
91
 
92
- Infer branch/worktree convention from `git worktree list` / `git branch -r` — commonly `feat|fix|refactor/<N>-slug` and `.worktrees/<N>-slug`. Branch off fresh `origin/main`, run the Install step, run the Check step, run the Test entrypoint as the baseline — the repo's **Recipe**, read from its Recipe cache: `~/.fleet/bin/fleet-run derive-testcmd.sh . install`, `… . check` and `… . test --at origin/main` print them. **No usable cache (any of the three exits 1) → run the Recipe derivation step first:** dispatch a `task` member, agent `fleet-recipe-deriver`, its prompt naming the main checkout's absolute path as `<repo>` and `<scratch>/derive-recipe/` as its scratch directory, `<scratch>` the output of `~/.fleet/bin/fleet-run scratch-root.mjs`; it reads the repo, proves all three commands in a throwaway worktree and writes the cache only on proof. `RECIPE NOT PROVEN` → stop and give the maintainer its reason; never pick a command yourself. Exit 3 is no verdict on the cache — the reader could not run a tool it needs — so fix that environment fault and re-run instead of deriving.
92
+ Infer branch/worktree convention from `git worktree list` / `git branch -r` — commonly `feat|fix|refactor/<N>-slug` and `.worktrees/<N>-slug`. Branch off fresh `origin/main`, run the Install step, run the Check step, run the Test entrypoint as the baseline — the repo's **Recipe**, read from its Recipe cache: `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run derive-testcmd.sh . install`, `… . check` and `… . test --at origin/main` print them. **No usable cache (any of the three exits 1) → run the Recipe derivation step first:** dispatch a `task` member, agent `fleet-recipe-deriver`, its prompt naming the main checkout's absolute path as `<repo>` and `<scratch>/derive-recipe/` as its scratch directory, `<scratch>` the output of `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run scratch-root.mjs`; it reads the repo, proves all three commands in a throwaway worktree and writes the cache only on proof. `RECIPE NOT PROVEN` → stop and give the maintainer its reason; never pick a command yourself. Exit 3 is no verdict on the cache — the reader could not run a tool it needs — so fix that environment fault and re-run instead of deriving.
93
93
 
94
94
  **Run the Install step with `CI` removed**, from the new worktree's root: `env -u CI sh -c "<install>"`, `<install>` the output of `derive-testcmd.sh . install`. A setup script that skips under `CI` installs no git hooks there, and you would then commit with the repository's commit-time checks silently absent. Only the Install step loses `CI`; the Check step and the Test entrypoint baseline run in your shell's own environment.
95
95
 
@@ -105,7 +105,7 @@ Come back here. The sizing path hands off; this step always follows.
105
105
 
106
106
  ```bash
107
107
  git fetch origin && git rebase origin/main # rebase, never merge main in
108
- ~/.fleet/bin/fleet-run recipe-check.mjs --member <your name> --testCmd "<test command>" --reports <scratch>/reports # re-run after any content change or rebase
108
+ ~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run recipe-check.mjs --member <your name> --testCmd "<test command>" --reports <scratch>/reports # re-run after any content change or rebase
109
109
  git push --force-with-lease -u origin HEAD
110
110
  gh pr create --base main --body "…
111
111
 
@@ -168,7 +168,7 @@ and a member sent into one is on `## HEAD (no branch)`, where the push above exi
168
168
  the cause, so no `-u`/force combination reaches it: the unqualified `HEAD`
169
169
  destination is, and plain `git push origin HEAD` fails the same way while a bare
170
170
  `git push` exits 128 (`fatal: You are not currently on a branch`). Name the branch
171
- instead, through the helper — `~/.fleet/bin/fleet-run push-sync.mjs --branch <branch> --force-with-lease`.
171
+ instead, through the helper — `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run push-sync.mjs --branch <branch> --force-with-lease`.
172
172
  A refspec push alone moves origin's ref and leaves the claim worktree's
173
173
  `refs/heads/<branch>` at its old tip; the helper pushes `HEAD:refs/heads/<branch>`,
174
174
  then moves the worktree holding `<branch>` to the pushed SHA with `reset --keep`,
@@ -39,7 +39,7 @@ Nothing in this phase, or in any later one, asks the maintainer which tickets to
39
39
 
40
40
  0. **Once per run, before anything else.** Run phase 0 from a Python eval
41
41
  cell in this main checkout, without `--session`:
42
- `subprocess.run([os.path.expanduser("~/.fleet/bin/fleet-run"),
42
+ `subprocess.run([os.path.expanduser("~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run"),
43
43
  "phase0.mjs", …], stderr=subprocess.STDOUT)`. Add `--in-flight <n>` and
44
44
  `--objective <o>` as `$ARGUMENTS` gave them, `--spend-dir <dir>` for the
45
45
  spend panel, and `--workflow <name>` or `--declare-no-ci`
@@ -49,7 +49,7 @@ Nothing in this phase, or in any later one, asks the maintainer which tickets to
49
49
  `rotate` has run, a re-run skips every `ok` step but `alarm` and resumes
50
50
  where the last one stopped; before it, a re-run runs every step again.
51
51
 
52
- The `tier-roles` step runs `~/.fleet/bin/fleet-run tier-roles.mjs --check
52
+ The `tier-roles` step runs `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run tier-roles.mjs --check
53
53
  --in-flight <B>`, `<B>` being the `--in-flight` given, else the default.
54
54
  **Default: In-flight bound 5, fixed for the run.** See references/pull.md.
55
55
  A line it prints on a pass about omp's `task.maxConcurrency`
@@ -58,7 +58,7 @@ Nothing in this phase, or in any later one, asks the maintainer which tickets to
58
58
 
59
59
  - `NEED derive-recipe` — the Recipe cache holds nothing valid. Dispatch a
60
60
  `task` member named `derive-recipe`, agent `fleet-recipe-deriver`, its
61
- prompt the brief `~/.fleet/bin/fleet-run dispatch-prompt.mjs render
61
+ prompt the brief `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run dispatch-prompt.mjs render
62
62
  recipe-deriver --member derive-recipe --repo <repo> --scratch <scratch>`
63
63
  prints (`<repo>` this main checkout's absolute path, `<scratch>` what
64
64
  `scratch-root.mjs` prints), and wait for its report. `RECIPE PROVEN` →
@@ -80,7 +80,7 @@ Nothing in this phase, or in any later one, asks the maintainer which tickets to
80
80
 
81
81
  See references/phase-0.md.
82
82
 
83
- 1. **Build the Shortlist** — `~/.fleet/bin/fleet-run shortlist.mjs`, then read
83
+ 1. **Build the Shortlist** — `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run shortlist.mjs`, then read
84
84
  `.fleet/shortlist.json` — `{scanned, shortlist: [{n, t}], dropped: [{n, reason}]}`:
85
85
  the survivors of its cheap filters, every probe failing CLOSED
86
86
  (references/phase-0.md, **Build the Shortlist**). Exit 0 is the file
@@ -121,7 +121,7 @@ call, which makes the wake's writes and ends in one `fleet-tick.mjs`
121
121
  invocation; do what it prints, and never hand-edit the ledger.
122
122
  See references/ci-and-staleness.md.
123
123
 
124
- Run each as `~/.fleet/bin/fleet-run fleet-event.mjs <kind> <args>`, from the main checkout:
124
+ Run each as `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run fleet-event.mjs <kind> <args>`, from the main checkout:
125
125
 
126
126
  | Wake | Command |
127
127
  |---|---|
@@ -184,7 +184,7 @@ owes beyond its call:
184
184
  See references/reaping.md.
185
185
  - **The run ends, or the maintainer says drain** → **End of run**, in this
186
186
  order; the drain starts the end of the run, it does not end it:
187
- 1. `~/.fleet/bin/fleet-run fleet-event.mjs drain --reason "<reason>"` — runs
187
+ 1. `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run fleet-event.mjs drain --reason "<reason>"` — runs
188
188
  `closeout.mjs begin --reason "<reason>"` (references/reaping.md), then the
189
189
  tick, which holds the implementer row at `HOLD (draining)` from then on. A
190
190
  claim it refuses prints `NEED hand-release #<N> <blocker>`: that refusal is
@@ -195,7 +195,7 @@ owes beyond its call:
195
195
  2. Act on the review, fix-applier and merge rows until the tick prints
196
196
  `ACTION: run over → fleet-heartbeat.mjs --stop "<reason>"`, which it does
197
197
  once the run is draining with no open PR and no live implementer.
198
- 3. `~/.fleet/bin/fleet-run closeout.mjs finish --reason "<reason>"`, which
198
+ 3. `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run closeout.mjs finish --reason "<reason>"`, which
199
199
  records `fleet-heartbeat.mjs --stop` and then merges the Close-out PR. On `NEED merge-wait PR #<n>`,
200
200
  run `finish` again at once. A PR it names `left open` is the next run's: you never label or merge it.
201
201
  A `NEED tier-outcomes append <pr>` is a reviewed PR with no verdict row — for an implementer's, one that never
@@ -244,7 +244,7 @@ Names follow the unit of work: `impl-<issue#>`, `fix-pr-<pr#>`,
244
244
  **new** member, **new** name. See references/member-lifecycle.md.
245
245
 
246
246
  **The scratch root is computed, never invented and never recorded.** You run
247
- `~/.fleet/bin/fleet-run scratch-root.mjs`; a non-zero exit is an environment to
247
+ `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run scratch-root.mjs`; a non-zero exit is an environment to
248
248
  fix, not a cue to pick another root.
249
249
  `<scratch>` in this file is the path it prints, resolved before you send
250
250
  anything: every brief that carries one carries the absolute path. A member
@@ -283,7 +283,7 @@ digest asks of you:
283
283
 
284
284
  **Guard: accumulate per PR, never conclude inside one run.** **Append one row to
285
285
  `docs/metrics/tier-outcomes.tsv` when you rule each PR's review, before its finisher, with
286
- `~/.fleet/bin/fleet-run tier-outcomes.mjs append <pr>`, never by hand** (that file's header carries the column meanings).
286
+ `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run tier-outcomes.mjs append <pr>`, never by hand** (that file's header carries the column meanings).
287
287
  The script works both verdicts out from the Charges on the PR's first review. The script
288
288
  fills `tier` itself; never type one in. `ledger.mjs dispatch` refuses the finisher until the row exists. That append is the whole duty. See references/pull.md.
289
289
 
@@ -296,7 +296,7 @@ fills `tier` itself; never type one in. `ledger.mjs dispatch` refuses the finish
296
296
  **Mark the beat when there is nothing to do, and end your turn.** See references/ci-and-staleness.md.
297
297
 
298
298
  ```bash
299
- ~/.fleet/bin/fleet-run fleet-heartbeat.mjs \
299
+ ~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run fleet-heartbeat.mjs \
300
300
  [--base 300] [--ceiling 1200] [--multiplier 2]
301
301
  ```
302
302
 
@@ -319,7 +319,7 @@ proof the pipeline is idle. See references/ci-and-staleness.md.
319
319
  you owe the next run.** See references/ci-and-staleness.md.
320
320
 
321
321
  ```bash
322
- ~/.fleet/bin/fleet-run fleet-heartbeat.mjs --stop "budget exhausted"
322
+ ~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run fleet-heartbeat.mjs --stop "budget exhausted"
323
323
  ```
324
324
 
325
325
  It holds nothing and returns at once. Use it when the budget goes, or when
@@ -355,7 +355,7 @@ Act on each line the tick prints as its row reads here, then stop: the next wake
355
355
  **In one line, every wake is one `fleet-event.mjs` call, which ends in the tick.** One tick invocation, and you act on what it prints:
356
356
 
357
357
  ```
358
- ~/.fleet/bin/fleet-run fleet-tick.mjs --apply [--in-flight <n>]
358
+ ~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run fleet-tick.mjs --apply [--in-flight <n>]
359
359
  ```
360
360
 
361
361
  Read the depth off the tick and never derive it by hand: act on the row it prints, and when it prints `SUGGEST /triage, hold idle`, hold the implementer row idle and suggest `/triage` in the report. See references/tick-rows.md.
@@ -405,7 +405,7 @@ A Pull is done when `pull.mjs next` exits 0 with its `DISPATCH` line, which the
405
405
  Serial, main checkout, one Pull at a time. Never parallel, never inside a member —
406
406
  concurrent `worktree add` and label writes race.
407
407
 
408
- A Pull's entry is `~/.fleet/bin/fleet-run pull.mjs next --head <N>`, run from
408
+ A Pull's entry is `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run pull.mjs next --head <N>`, run from
409
409
  the main checkout (without `--head`, the next shortlist entry). It stops at
410
410
  each judgement with a `QUESTION <qid>:` block and exit 10; `pull.mjs answer <N>
411
411
  <qid> <token> [--path <p>] [--] [<text>…]` records the answer and resumes it.
@@ -516,7 +516,7 @@ A dispatch is done when its `task` call is made, in the background, with the `ag
516
516
 
517
517
  Pointers: the `/resume` rules are in `references/phase-0.md`; the tick HOLD tier rules are in `references/tick-rows.md`; shell traps are in `references/shell-traps.md`. Rationale for these rules: `references/member-lifecycle.md`.
518
518
 
519
- **The test command every gate runs.** Pass the same command to the review, to the fix-applier, and to the finisher — whose duty-2 mutation gate runs it too — so every gate runs one command: the fix-applier and the finisher get the wrapped string as `<testCmd>` — `~/.fleet/bin/fleet-run suite-slot.mjs '<command>'`, each `'` inside the command written `'\''` — and the review's args the bare command. Never substitute `<testCmd>` with nothing.
519
+ **The test command every gate runs.** Pass the same command to the review, to the fix-applier, and to the finisher — whose duty-2 mutation gate runs it too — so every gate runs one command: the fix-applier and the finisher get the wrapped string as `<testCmd>` — `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run suite-slot.mjs '<command>'`, each `'` inside the command written `'\''` — and the review's args the bare command. Never substitute `<testCmd>` with nothing.
520
520
 
521
521
  **Where `<branch>` comes from:** the PR's head branch — `gh pr view <N> --json headRefName -q .headRefName`, or the same branch you cut the worktree from. See references/reviewers.md.
522
522
 
@@ -646,7 +646,7 @@ transfer, since it verified a different tree. See references/finisher.md.
646
646
  **Own the CI waits.** Arm a second persistent Monitor over open PRs' latest
647
647
  runs from the block in references/ci-watcher.md, verbatim, keyed
648
648
  `<run-id>:<attempt>:<conclusion>` so each terminal state fires once: one
649
- `~/.fleet/bin/fleet-run ci-state.mjs --pr <N>` per open PR emits run id,
649
+ `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run ci-state.mjs --pr <N>` per open PR emits run id,
650
650
  attempt, conclusion, behind-count and per-job conclusions. Call it **without
651
651
  `--quiet`** — that flag drops `jobs`, `missing` and `dropped`.
652
652
 
@@ -695,7 +695,7 @@ you cannot confirm was received, re-check the artifacts it governed. See referen
695
695
 
696
696
  - **Re-check before you act on any instrument reading** — a SHA acceptance, a CI
697
697
  verdict, the reconcile, a reap, a label gate — from the main checkout phase 0 pinned from:
698
- `~/.fleet/bin/fleet-run instruments.sh`. **Exit 0 is the only code that
698
+ `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run instruments.sh`. **Exit 0 is the only code that
699
699
  lets a gate proceed. Exit 1 (the set changed) and exit 2 (the check could not
700
700
  answer) both refuse: report what it printed and do NOT re-read the
701
701
  instrument** — a guard that fails open on "could not look" protects nothing.
@@ -814,7 +814,7 @@ Match the failure to its row in the table below and run that response; where the
814
814
  | Member idle with work outstanding | Read the PR first, *then* ping. Idle ≠ done |
815
815
  | Member **killed** (spend limit, API error, crash) | Confirm it is dead first — a frozen transcript does not establish that; see below — then run the **Member confirmed dead or never dispatched** wake, then new member, new name, prompt carries inherited state |
816
816
  | Member **unaccounted** (a live token the tick flags `CHECK-LIVENESS`, or any live token nothing has reported on) | Registry census first: `read history://` once. A row other than `running` → `read agent://<member>` and the artifacts (PR head, worktree, labels), settle the real outcome with the existing vocabulary, and resume a `parked` member with `write agent://<member>` when its work is worth continuing. A `running` row → the mtime discriminator below, two polls: moved means BLOCKED and alive; frozen at both polls **and** no artifact movement → `write proc://<member>/kill`, the **Member confirmed dead or never dispatched** wake, fresh name. Three independent alive-signals — the first poll, the second poll, the artifacts — must all be silent before a kill; the tick settles and kills nothing |
817
- | A claim abandoned mid-run (a collision found after the claim) | `~/.fleet/bin/fleet-run release-ticket.sh <N> impl-<N> implementer --apply`, the pair the claim took, on the spot — and over every claimed ticket with no PR when the run ends or the maintainer drains. **That refusal is the finding, never an obstacle**: a claim carrying commits or a pushed branch is not auto-released, ever — run `worktree-audit.sh` (it audits every worktree; find this claim's row in the output) and decide by hand. Update the released tickets' ledger rows in the same step. See references/reaping.md |
817
+ | A claim abandoned mid-run (a collision found after the claim) | `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run release-ticket.sh <N> impl-<N> implementer --apply`, the pair the claim took, on the spot — and over every claimed ticket with no PR when the run ends or the maintainer drains. **That refusal is the finding, never an obstacle**: a claim carrying commits or a pushed branch is not auto-released, ever — run `worktree-audit.sh` (it audits every worktree; find this claim's row in the output) and decide by hand. Update the released tickets' ledger rows in the same step. See references/reaping.md |
818
818
  | A second review launch refused for an open one | Wait for that one's `reviewed=`, or, once the **Member killed** row has confirmed its runner dead, settle it `=failed` in the same `ledger.mjs review` call as the new launch. |
819
819
  | `ledger.mjs settle <member> --from-report` exits 3 | A check failed: the member's claim and the world disagree, and nothing is written. You rule. |
820
820
  | `ledger.mjs settle <member> --from-report` exits 2 | The report is absent or invalid, or a check could not look; nothing is written. A check that could not look is run again once `gh` and `git` answer. |
@@ -835,7 +835,7 @@ Reviewers that went idle on CI recover as a **finisher, not a re-review** once
835
835
  commits are pushed. See references/member-lifecycle.md.
836
836
 
837
837
  **Audit every worktree before dispatching replacements**, with
838
- `~/.fleet/bin/fleet-run worktree-audit.sh`. See references/failure-handling.md.
838
+ `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run worktree-audit.sh`. See references/failure-handling.md.
839
839
 
840
840
  When a report is missing, **ask by name — that is what the "unless the controller asks by name" clause in every brief is for — and do not attribute the gap to the member until it answers.** See references/member-lifecycle.md.
841
841
 
@@ -843,7 +843,7 @@ A review that throws, returns empty or notifies a status not `completed` is a
843
843
  failure event, not a clean review: retry it as the **Failure handling** row for
844
844
  it says. See references/failure-handling.md.
845
845
 
846
- **Verify every reported SHA** with `~/.fleet/bin/fleet-run verify-sha.sh
846
+ **Verify every reported SHA** with `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run verify-sha.sh
847
847
  <branch> <sha>` before enqueueing. Exit 1, not reachable → flag, do not
848
848
  enqueue, do not return the ticket to the shortlist until the maintainer rules.
849
849
  **Exit 2 is not a verdict**: read its stderr, fix what it names and re-run;
@@ -900,13 +900,8 @@ Stop when a thought of yours matches one of these, and act on the line it carrie
900
900
  - "This member finished, send it the next ticket" → resumes its transcript.
901
901
  - "The name is cosmetic" → the name is the ledger token and the hub address.
902
902
  - "ready-for-agent came back empty, widen to ready-for-human" → empty with no `specs-dropped=` means no work; empty with drops means specs awaiting to-tickets, and is still never a reason to widen.
903
- - "The reap at the end will pick up the claim I never dispatched" → it declines:
904
- not `[gone]`, no unique commits. Release it, or it reads as taken next run.
905
- - "Touches eight files, too big for the fleet" → size is not the axis. Decided is.
906
- - "Body is three lines, so it's simple" → short bodies hide open design choices.
907
- - "The brief is thorough, so it's decided" → thorough ≠ decided. Read it for the
908
- choice it leaves open.
909
- - "I'd have to pick an approach myself" → that IS undecided.
903
+ - A thought about whether a ticket is decided → its red flags are in references/pull.md.
904
+ - A thought about reaping or removing a worktree → its red flags are in references/reaping.md.
910
905
  - "It reported the SHA, so it's on the branch" → verify.
911
906
  - "Let the merge bot arm its own monitor" → it dies, the queue stops.
912
907
  - "The member died, message it the state" → dead agents do not read mail.
@@ -918,13 +913,6 @@ Stop when a thought of yours matches one of these, and act on the line it carrie
918
913
  - "A quick install to set up the worktree" → the claim already ran the Recipe's
919
914
  Install step; any other install can rewrite the lockfile for the whole repo.
920
915
  - "I'm on my own copy, so I'm isolated" → not from the docker stack.
921
- - "`commit-commands:clean_gone` printed nothing, the tree is clean" → its
922
- `[gone]` detection works fine; it just runs `-D`/`--force` with no merged
923
- check, so "printed nothing" only means nothing was gone yet, not that it's safe.
924
- - "`--force` the worktree removal, the PR merged anyway" → merged says nothing
925
- about uncommitted files, and the reviewer may still be in there.
926
- - "Reap once at the end of the run" → stale worktrees make phase 0 read merged
927
- tickets as taken, so the starvation compounds with every Pull.
928
916
 
929
917
  ## Report
930
918
 
@@ -940,7 +928,7 @@ Plus a queue-depth line: shortlist, supply, whether triage was suggested.
940
928
 
941
929
  **Do not read a cell early** (references/pull.md, **Do not read a cell
942
930
  early**). **Report the count the per-cell readout prints,
943
- never one from any other query:** `~/.fleet/bin/fleet-run cell-readout.mjs`
931
+ never one from any other query:** `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run cell-readout.mjs`
944
932
  prints `<cell> <comparisons> <run_dates> <resolved models>` for each cell past
945
933
  that floor and a cell below it only as a count on stderr; a `mixed (…)` models
946
934
  column means the cell's history spans more than one model behind its role. See references/pull.md.
@@ -20,9 +20,9 @@ scratch: <scratch>
20
20
 
21
21
  Your report is a file, `<scratch>/reports/<your name>.json`, `<your name>` the
22
22
  `finisher-pr-<M>[-x]` you were dispatched as, in the shape
23
- `~/.fleet/bin/fleet-run report-schema.mjs print finisher` prints. Write it
23
+ `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run report-schema.mjs print finisher` prints. Write it
24
24
  before your final message, and send nothing until
25
- `~/.fleet/bin/fleet-run report-schema.mjs validate finisher <scratch>/reports/<your name>.json`
25
+ `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run report-schema.mjs validate finisher <scratch>/reports/<your name>.json`
26
26
  answers `valid`. Your final message is then one line,
27
27
  `<your name>: <outcome> <scratch>/reports/<your name>.json`, `<outcome>` the
28
28
  report's `outcome`.