@feigi/fleet-ctl 3.137.5 → 3.138.1

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 (52) 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 +15 -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/release-ticket.sh +16 -0
  25. package/scripts/repo-root.mjs +1 -1
  26. package/scripts/report-schema.mjs +1 -1
  27. package/scripts/review-core.mjs +6 -6
  28. package/scripts/review-eval.mjs +1 -1
  29. package/scripts/ticketless.mjs +1 -1
  30. package/scripts/worktree.sh +46 -0
  31. package/skills/next-ticket/SKILL.md +8 -8
  32. package/skills/run-team/SKILL.md +22 -34
  33. package/skills/run-team/briefs/finisher.md +2 -2
  34. package/skills/run-team/briefs/fix-applier.md +9 -9
  35. package/skills/run-team/briefs/implementer.md +3 -3
  36. package/skills/run-team/briefs/merge-bot.md +2 -2
  37. package/skills/run-team/references/ci-and-staleness.md +1 -1
  38. package/skills/run-team/references/ci-watcher.md +1 -1
  39. package/skills/run-team/references/close-out.md +5 -5
  40. package/skills/run-team/references/failure-handling.md +2 -2
  41. package/skills/run-team/references/finisher.md +2 -2
  42. package/skills/run-team/references/instruments.md +1 -1
  43. package/skills/run-team/references/isolation.md +3 -3
  44. package/skills/run-team/references/ledger.md +1 -1
  45. package/skills/run-team/references/member-lifecycle.md +1 -1
  46. package/skills/run-team/references/phase-0.md +20 -20
  47. package/skills/run-team/references/pull.md +18 -10
  48. package/skills/run-team/references/reaping.md +15 -1
  49. package/skills/run-team/references/reviewers.md +9 -1
  50. package/skills/run-team/references/tick-rows.md +2 -2
  51. package/skills/sizing-a-ticket/SKILL.md +1 -1
  52. package/scripts/fleet-bootstrap +0 -140
@@ -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`.
@@ -38,7 +38,7 @@ job is red on its current head and you are here to fix it — do not review, do
38
38
  not dispatch specialists.
39
39
 
40
40
  ## kind: review, dispositions-retry
41
- Read `$(~/.fleet/bin/fleet-run --root)/commands/review-and-fix.md` and run **steps 2, 3
41
+ Read `~/.omp/plugins/node_modules/@feigi/fleet-ctl/commands/review-and-fix.md` and run **steps 2, 3
42
42
  and 5 only**: split apply-now/defer, commit, push, file every deferral as its
43
43
  own issue with the label the finding's state calls for. Skip step 1 — the
44
44
  review already ran — and steps 4 and 6: the controller owns the CI wait and
@@ -48,8 +48,8 @@ Label names in this file are roles; the Label map gives the string to type; a me
48
48
 
49
49
  **Before your first edit or refuter dispatch, read the Label map — the two
50
50
  roles you type or compare, once — and use those strings for the rest of your
51
- run.** `~/.fleet/bin/fleet-run label-map.mjs show needs-triage` and
52
- `~/.fleet/bin/fleet-run label-map.mjs show wontfix` each print the string the
51
+ run.** `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run label-map.mjs show needs-triage` and
52
+ `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run label-map.mjs show wontfix` each print the string the
53
53
  tracker uses; every `gh` command and label comparison those steps of
54
54
  `review-and-fix.md` type for those two roles takes it. You never run `ensure`
55
55
  and never ask anyone. **A non-zero exit from `show` ends you with no report** —
@@ -91,13 +91,13 @@ The ticket:
91
91
  <ticket>
92
92
  ## kind: conflict
93
93
  Bring `<branch>` current with `origin/main`, resolving every conflict by the
94
- **No-undo audit** in `$(~/.fleet/bin/fleet-run --root)/commands/run-merge-bot.md`.
94
+ **No-undo audit** in `~/.omp/plugins/node_modules/@feigi/fleet-ctl/commands/run-merge-bot.md`.
95
95
  Run `recipe-check.mjs` (below) from the worktree before you push, then push with
96
- `~/.fleet/bin/fleet-run push-sync.mjs --branch <branch>`. Report the new head, or that no conflict was
96
+ `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run push-sync.mjs --branch <branch>`. Report the new head, or that no conflict was
97
97
  left.
98
98
  ## kind: red-check
99
99
  Read the failing job's log and fix the cause. Run `recipe-check.mjs` (below)
100
- from the worktree before you push, then push with `~/.fleet/bin/fleet-run push-sync.mjs --branch <branch>`.
100
+ from the worktree before you push, then push with `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run push-sync.mjs --branch <branch>`.
101
101
  Report the new head and **stop**: do not watch, poll or wait for CI — the
102
102
  controller owns the next run on the pushed head. A red that is not yours to
103
103
  fix — a flake that passes on rerun, or staleness — gets nothing pushed: report
@@ -121,7 +121,7 @@ re-run. That command never deletes an ignored file. A path the re-run still
121
121
  refuses after that clean → push nothing and report that cause.
122
122
 
123
123
  **`recipe-check.mjs` is how you run `<checkCmd>` and `<testCmd>`:**
124
- `~/.fleet/bin/fleet-run recipe-check.mjs --member <your name> --testCmd "<testCmd>" --reports <scratch>/reports`,
124
+ `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run recipe-check.mjs --member <your name> --testCmd "<testCmd>" --reports <scratch>/reports`,
125
125
  from the worktree, after `git add` and before the commit — `<testCmd>` copied
126
126
  verbatim as the one quoted argument. It runs the Recipe's Check step,
127
127
  `<checkCmd>`, then `<testCmd>`, against the staged tree and records both beside
@@ -166,13 +166,13 @@ nothing past, `applied` and `deferred` empty, `dispositionsRecord` and
166
166
 
167
167
  Your report is a file, `<scratch>/reports/<your name>.json`, `<your name>` the
168
168
  `fix-pr-` name you were dispatched as, in the shape
169
- `~/.fleet/bin/fleet-run report-schema.mjs print fix-pr` prints. A field with
169
+ `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run report-schema.mjs print fix-pr` prints. A field with
170
170
  nothing real to point at is `null`: `dispositionsRecord` for a conflict hold or
171
171
  a red-check fix, which write no dispositions record, and `testRun` when no test
172
172
  run exists — a `no-op`, or a `failed` that never ran tests. A non-null value
173
173
  always reflects a real record or a real run. Write the report before your
174
174
  final message, and send nothing until
175
- `~/.fleet/bin/fleet-run report-schema.mjs validate fix-pr <scratch>/reports/<your name>.json`
175
+ `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run report-schema.mjs validate fix-pr <scratch>/reports/<your name>.json`
176
176
  answers `valid`. Your final message is then one line,
177
177
  `<your name>: <outcome> <scratch>/reports/<your name>.json`, `<outcome>` the
178
178
  report's `outcome`.
@@ -27,7 +27,7 @@ The ticket, pasted verbatim from the controller's own read — its title, the
27
27
  The controller's staleness probe: <staleness>
28
28
 
29
29
  Before you commit and push, run
30
- `~/.fleet/bin/fleet-run recipe-check.mjs --member <your name> --testCmd ./agent-test --reports <scratch>/reports`
30
+ `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run recipe-check.mjs --member <your name> --testCmd ./agent-test --reports <scratch>/reports`
31
31
  from the worktree, after `git add`: it runs the Recipe's Check step, then
32
32
  `./agent-test`, against the staged tree and records both beside your report.
33
33
  Run it again after any content change or rebase. After the commit, and before
@@ -69,9 +69,9 @@ maintainer.
69
69
 
70
70
  Your report is a file, `<scratch>/reports/<your name>.json`, `<your name>` the
71
71
  `impl-<N>[-x]` you were dispatched as, in the shape
72
- `~/.fleet/bin/fleet-run report-schema.mjs print impl` prints. Write it before
72
+ `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run report-schema.mjs print impl` prints. Write it before
73
73
  your final message, and send nothing until
74
- `~/.fleet/bin/fleet-run report-schema.mjs validate impl <scratch>/reports/<your name>.json`
74
+ `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run report-schema.mjs validate impl <scratch>/reports/<your name>.json`
75
75
  answers `valid`. Your final message is then one line,
76
76
  `<your name>: <outcome> <scratch>/reports/<your name>.json`, `<outcome>` the
77
77
  report's `outcome`.
@@ -8,9 +8,9 @@ You are merge-bot-<n>.
8
8
  scratch: <scratch>
9
9
 
10
10
  Your report is a file, `<scratch>/reports/merge-bot-<n>.json`, in the shape
11
- `~/.fleet/bin/fleet-run report-schema.mjs print merge-bot` prints. Write it
11
+ `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run report-schema.mjs print merge-bot` prints. Write it
12
12
  before your final message, and send nothing until
13
- `~/.fleet/bin/fleet-run report-schema.mjs validate merge-bot <scratch>/reports/merge-bot-<n>.json`
13
+ `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run report-schema.mjs validate merge-bot <scratch>/reports/merge-bot-<n>.json`
14
14
  answers `valid`. Your final message is then one line,
15
15
  `merge-bot-<n>: done <scratch>/reports/merge-bot-<n>.json`. A Label map
16
16
  refusal, which `run-merge-bot.md` describes, follows that line with what
@@ -137,7 +137,7 @@ detected by its mark going stale. A run that stops KNOWINGLY can do better
137
137
  than being detected, and nothing else can write the reason afterwards:
138
138
 
139
139
  ```bash
140
- ~/.fleet/bin/fleet-run fleet-heartbeat.mjs --stop "budget exhausted"
140
+ ~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run fleet-heartbeat.mjs --stop "budget exhausted"
141
141
  ```
142
142
 
143
143
  Skipping it is not fatal — the next reader still reports the stop, it just
@@ -78,7 +78,7 @@ while :; do # one tick
78
78
  hidden_out=
79
79
  fi
80
80
  for pr in $(printf '%s\n' "$prs"); do # inline $(...): `for pr in $prs` is ONE iteration under zsh
81
- st=$(~/.fleet/bin/fleet-run ci-state.mjs --pr "$pr" 2>/dev/null) || : # not-green exits non-zero; the payload is the verdict
81
+ st=$(~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run ci-state.mjs --pr "$pr" 2>/dev/null) || : # not-green exits non-zero; the payload is the verdict
82
82
  if ! printf '%s' "$st" | jq -e '.verdict and .verdict != "rate-limited"' >/dev/null 2>&1; then
83
83
  case " $blind " in *" $pr "*) ;; *) # latch keyed BY PR: this cause is per-PR
84
84
  echo "WATCHER DEGRADED: no usable ci-state reading for #$pr — silence is NOT green"
@@ -8,7 +8,7 @@
8
8
  replacement controller too — and keeps the review, fix-applier and merge rows
9
9
  firing until the open PRs merge. The drain starts the end of the run; it does
10
10
  not end it. **End of run**, in this order:
11
- 1. `~/.fleet/bin/fleet-run fleet-event.mjs drain --reason "<reason>"` — runs
11
+ 1. `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run fleet-event.mjs drain --reason "<reason>"` — runs
12
12
  `closeout.mjs begin --reason "<reason>"` (references/reaping.md), then the tick. A claim it refuses prints `NEED hand-release #<N> <blocker>`: that
13
13
  refusal is the finding, so run `worktree-audit.sh` and decide by hand.
14
14
  `begin` selects a claim with no PR and a live or `bailed` implementer token
@@ -17,7 +17,7 @@
17
17
  2. Act on the review, fix-applier and merge rows until the tick prints
18
18
  `ACTION: run over → fleet-heartbeat.mjs --stop "<reason>"`, which it does
19
19
  once the run is draining with no open PR and no live implementer.
20
- 3. `~/.fleet/bin/fleet-run closeout.mjs finish --reason "<reason>"` — scrapes
20
+ 3. `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run closeout.mjs finish --reason "<reason>"` — scrapes
21
21
  the run's member facts, checks the tier-outcomes rows, refreshes the
22
22
  metrics, commits the three metrics files and opens their PR, sets the
23
23
  phase-0 receipt aside as `.fleet/phase0.previous.json`, records
@@ -83,7 +83,7 @@ re-dispatched picks the new transcript up. **Never hand-edit
83
83
  role classifier changes, and a hand-entered value would not survive that. The
84
84
  verdict for a PR goes to `tier-outcomes.tsv` through `tier-outcomes.mjs
85
85
  append`, as above. Once both files hold this run's rows, and before either is
86
- committed, run `~/.fleet/bin/fleet-run tier-outcomes.mjs check --live`. Exit 1
86
+ committed, run `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run tier-outcomes.mjs check --live`. Exit 1
87
87
  names each row whose `tier` disagrees with the one implementer the member facts
88
88
  say ran for its ticket: correct that row's `tier` to the short name it prints,
89
89
  or blank it and say why in `note`. Exit 1 also names the PRs of the case where
@@ -103,7 +103,7 @@ issue number among the reasons — comes before that PR's WARNING and says why.
103
103
 
104
104
  **Drain the pending ticket-features rows and refresh the cost guard, after
105
105
  the member-outcomes scrape and every `tier-outcomes.mjs append`, before the
106
- metrics files are committed.** `~/.fleet/bin/fleet-run metrics-refresh.mjs`
106
+ metrics files are committed.** `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run metrics-refresh.mjs`
107
107
  moves `.fleet/ticket-features.pending.tsv` — the row the router script
108
108
  appended for each Pull at dispatch — into `docs/metrics/ticket-features.tsv`,
109
109
  deduped on `session`+`agent`, so this run's own rows are in the file that gets
@@ -153,4 +153,4 @@ The step can refuse in each of these ways:
153
153
 
154
154
  ## Undo a drain
155
155
 
156
- **Undrain only when the maintainer asks, and never a drain that budget or context exhaustion caused.** `~/.fleet/bin/fleet-run fleet-event.mjs undrain --reason "<reason>"` runs `closeout.mjs reopen --reason "<reason>"`, then the tick, as `drain` does. `reopen` refuses (exit 2) once any `finish` step in `.fleet/closeout.json` is `ok`, because the tick and what follows it have already acted; a `finish` whose `tick` failed blocks nothing. Otherwise it puts `begin`'s `drain` and `release` steps back to pending and clears `begun`, then runs `ledger.mjs undrain "<reason>"`, which clears the marker, so the next `begin` drains and releases again. With no marker set it refuses (exit 2). A ledger drained by a bare `ledger.mjs drain`, with no receipt, is only undrained. A claim `begin` released stays released: its ticket goes back to the queue and is dispatched under the next free name (`impl-<N>-b`), because `ledger.mjs dispatch` refuses a name already dispatched this session.
156
+ **Undrain only when the maintainer asks, and never a drain that budget or context exhaustion caused.** `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run fleet-event.mjs undrain --reason "<reason>"` runs `closeout.mjs reopen --reason "<reason>"`, then the tick, as `drain` does. `reopen` refuses (exit 2) once any `finish` step in `.fleet/closeout.json` is `ok`, because the tick and what follows it have already acted; a `finish` whose `tick` failed blocks nothing. Otherwise it puts `begin`'s `drain` and `release` steps back to pending and clears `begun`, then runs `ledger.mjs undrain "<reason>"`, which clears the marker, so the next `begin` drains and releases again. With no marker set it refuses (exit 2). A ledger drained by a bare `ledger.mjs drain`, with no receipt, is only undrained. A claim `begin` released stays released: its ticket goes back to the queue and is dispatched under the next free name (`impl-<N>-b`), because `ledger.mjs dispatch` refuses a name already dispatched this session.
@@ -37,7 +37,7 @@ reaches it anyway, and neither replaces the other.
37
37
  ## Audit every worktree before dispatching replacements
38
38
 
39
39
  Audit every worktree before dispatching replacements with
40
- `~/.fleet/bin/fleet-run worktree-audit.sh` — it reports each worktree's
40
+ `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run worktree-audit.sh` — it reports each worktree's
41
41
  ahead-count and uncommitted files, the committed-vs-uncommitted distinction that
42
42
  decides whether a replacement redoes or destroys work.
43
43
 
@@ -54,7 +54,7 @@ review-due. A
54
54
  runner member that is killed rather than failed follows **Failure
55
55
  handling** (fresh name, inherited state stated).
56
56
 
57
- **Verify every reported SHA.** `~/.fleet/bin/fleet-run verify-sha.sh
57
+ **Verify every reported SHA.** `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run verify-sha.sh
58
58
  <branch> <sha>` before enqueueing — a member can commit in a nested worktree,
59
59
  leaving the SHA on a stray branch while its report reads normally. Exit codes as
60
60
  `inflight.sh`: `# 0 reachable, 1 not reachable, 2 unanswerable`. Not reachable
@@ -240,7 +240,7 @@ head is not part of it, and duty 1 audits that head separately.
240
240
 
241
241
  ## A Ticketless PR has no mutation and no ruling
242
242
 
243
- **A Ticketless PR skips the acceptance mutation on `ticketless.mjs`'s exit 0 alone.** Run `~/.fleet/bin/fleet-run ticketless.mjs --pr <M>`. It reads whether the PR closes an issue in its own repository and whether a settled `impl-<N>=PR#<M>` token names it; with neither, no ticket supplies a mutation to re-run, so exit 0 skips it whatever the diff, and the rest of duty 2 runs. Exit 1 and exit 2 (could not look) run duty 2 as for a ticket PR. Where a kill's evidence line would go, the report says that no mutation ran because the PR is ticketless.
243
+ **A Ticketless PR skips the acceptance mutation on `ticketless.mjs`'s exit 0 alone.** Run `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run ticketless.mjs --pr <M>`. It reads whether the PR closes an issue in its own repository and whether a settled `impl-<N>=PR#<M>` token names it; with neither, no ticket supplies a mutation to re-run, so exit 0 skips it whatever the diff, and the rest of duty 2 runs. Exit 1 and exit 2 (could not look) run duty 2 as for a ticket PR. Where a kill's evidence line would go, the report says that no mutation ran because the PR is ticketless.
244
244
 
245
245
  **Duty 3 holds a Ticketless PR whose diff is not inert.** `finisher-label.mjs` adds `patch` to a Ticketless PR that carries no release label, then runs the Inert diff verdict in-process at your pin. A diff that is not inert, or a verdict that could not look, gets the `ready-to-merge-head:` record and no `ready-to-merge`, and the script exits 5: halt with cause `human`. No ticket gives that PR a ruling or a mutation, so the maintainer's `ready-to-merge` is the merge. The merge bot merges it off the record at the pinned head, and a head that moved after the record is merged by hand.
246
246
 
@@ -257,7 +257,7 @@ ordering is detectable afterwards from the diff — a restore lands on the
257
257
  uncommitted clause and destroys it silently, or the mutant is still in the
258
258
  tree when the fix-applier commits and a deliberately broken guard ships as
259
259
  the fix, in a commit nothing re-reviews. So take your own:
260
- `~/.fleet/bin/fleet-run finisher-tree.mjs --worktree <abs-path> --pin <your dispatch pin> --pr <N> --member <your member name> --scratch <scratch>`
260
+ `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run finisher-tree.mjs --worktree <abs-path> --pin <your dispatch pin> --pr <N> --member <your member name> --scratch <scratch>`
261
261
  adds `git worktree add --detach <scratch>/pr<N>/finish-<your member name> <your dispatch pin>`
262
262
  and runs the Install step in it, as a claim does: a detached worktree holds
263
263
  tracked files only, so without that step a suite whose dependencies are
@@ -78,7 +78,7 @@ is the repository that `repository.url` in the Install root's `package.json`
78
78
  names — the same host and `owner/repo` — file it the way `review-and-fix.md`
79
79
  step 5 files a deferral: `ledger.mjs check "<subject>"`, then
80
80
  `gh issue create --label "<needs-triage string>"`, `<needs-triage string>` being what
81
- `~/.fleet/bin/fleet-run label-map.mjs show needs-triage` prints, then `ledger.mjs filed <N> "<subject>"` with the same subject. A
81
+ `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run label-map.mjs show needs-triage` prints, then `ledger.mjs filed <N> "<subject>"` with the same subject. A
82
82
  tracker hit is handled the way step 5 handles one. The subject is `<path>: <the
83
83
  defect in one line>`; the body carries the evidence — the members, the text
84
84
  they followed, the transcript and ledger lines — the trigger it met, the
@@ -6,7 +6,7 @@ Why isolation envelope file not briefing, why private filesystem not private sta
6
6
 
7
7
  Env vars in prompt missed five times in one run — including briefed member, and specialist whose parent briefed but did not pass down. So the runner is a file in the worktree. A claim writes `agent-test` into the fresh worktree it creates: an exec of the Recipe's Test entrypoint that exports one port triple derived from `<N>`, kept out of `git status` through the repository's exclude file. A repository that tracks its own `agent-test` keeps it byte-identical — the claim exports nothing into it, so its isolation is whatever that repository built, and any convenience beyond exec'ing the Test entrypoint is that runner's own to document. Brief members with `./agent-test` and nothing else: anyone who finds worktree finds runner — including grandchildren you never dispatched. Its arguments land after the Test entrypoint, so what one may name — a test file, a test name — is that entrypoint's to say, and nothing in the runner refuses one that selects no test: a run of zero tests is a failed run, not a pass. That triple makes collisions impossible, not discouraged — difference between safeguard and rule.
8
8
 
9
- The runner a claim writes is written once and never rewritten — a claim refuses a worktree that already exists — so every copy under `.worktrees/` is frozen at whenever that worktree was claimed; reading or measuring one measures that build, not what the current emitter produces. Line 2 is what tells a reader which build they are holding: `# agent-test template: <cksum>`. Reproduce the number from the installed script (`cksum $(~/.fleet/bin/fleet-run --path claim-ticket.sh)`) or from any revision of it (`git show <rev>:plugin/scripts/claim-ticket.sh | cksum`) and compare the first field — `cksum` also prints a byte count, and the path when it is given a file. It checksums the whole emitting script, not the runner template inside it, so it over-reports: a mismatch means only that `claim-ticket.sh`'s bytes differ from the ones you checksummed — a reworded die message or an edited comment moves it while the runner it produces stays byte-identical — not "the template changed", and not "older" either, because `cksum` carries no order: over `claim-ticket.sh`'s own history both the checksum and the byte count fall as well as rise. It under-reports too, so a match is not the freshness proof it looks like. The stamp covers `claim-ticket.sh` and nothing else, while the command the runner `exec`s is the Recipe cache's Test entrypoint, which it does not cover: two claims under one stamp exec different commands once the Recipe is re-derived between them. So read a match as "this runner came from these bytes of `claim-ticket.sh`"; only a fresh claim writes the current runner. Nothing reads the stamp and nothing refuses on a mismatch; it makes staleness legible to a human, it gates nothing.
9
+ The runner a claim writes is written once and never rewritten — a claim refuses a worktree that already exists — so every copy under `.worktrees/` is frozen at whenever that worktree was claimed; reading or measuring one measures that build, not what the current emitter produces. Line 2 is what tells a reader which build they are holding: `# agent-test template: <cksum>`. Reproduce the number from the installed script (`cksum $(~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run --path claim-ticket.sh)`) or from any revision of it (`git show <rev>:plugin/scripts/claim-ticket.sh | cksum`) and compare the first field — `cksum` also prints a byte count, and the path when it is given a file. It checksums the whole emitting script, not the runner template inside it, so it over-reports: a mismatch means only that `claim-ticket.sh`'s bytes differ from the ones you checksummed — a reworded die message or an edited comment moves it while the runner it produces stays byte-identical — not "the template changed", and not "older" either, because `cksum` carries no order: over `claim-ticket.sh`'s own history both the checksum and the byte count fall as well as rise. It under-reports too, so a match is not the freshness proof it looks like. The stamp covers `claim-ticket.sh` and nothing else, while the command the runner `exec`s is the Recipe cache's Test entrypoint, which it does not cover: two claims under one stamp exec different commands once the Recipe is re-derived between them. So read a match as "this runner came from these bytes of `claim-ticket.sh`"; only a fresh claim writes the current runner. Nothing reads the stamp and nothing refuses on a mismatch; it makes staleness legible to a human, it gates nothing.
10
10
 
11
11
  ## A worktree no claim built: the runner, and the commit
12
12
 
@@ -18,7 +18,7 @@ unless the repository tracks its own, and a member told to run one
18
18
  stalls on a missing script (observed with a rebase-resolver in a
19
19
  prior-run worktree). There, tell the member the runner is absent and to
20
20
  run the Recipe's Test entrypoint directly
21
- (`~/.fleet/bin/fleet-run derive-testcmd.sh <main checkout> test --at origin/main` prints
21
+ (`~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run derive-testcmd.sh <main checkout> test --at origin/main` prints
22
22
  it).
23
23
 
24
24
  **A reused worktree may also be on the wrong COMMIT.** `git worktree add <path>
@@ -115,7 +115,7 @@ tree with neither a HEAD move nor a restore in 7 days of every path git ignores
115
115
  but its runner, and leaves the tree, its branch and its commits. The renderer
116
116
  refuses to brief an implementer
117
117
  or a fix-applier into one; before you run code in one by hand, restore it with
118
- `~/.fleet/bin/fleet-run evict.mjs --restore <tree> --apply`, which runs the
118
+ `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run evict.mjs --restore <tree> --apply`, which runs the
119
119
  Install step there as a claim does.
120
120
 
121
121
  ## Filesystem isolation is not stack isolation
@@ -60,7 +60,7 @@ that was never read and from one whose rows you have to read yourself.
60
60
 
61
61
  ## Why the ledger outlives your context
62
62
 
63
- One git-ignored `.fleet/ledger.md` per run is updated at every state change through the `~/.fleet/bin/fleet-run ledger.mjs` subcommands (`row`, `filed`, `ruled`, `check`, `read`, `dispatch`, `settle`, `review`, `drain`, `rotate`). Your context is the least durable thing in the run: it compacts, and a controller that loses the dispatch map or the filed list redoes finished work. Two duplicate tickets shipped in one run from exactly that.
63
+ One git-ignored `.fleet/ledger.md` per run is updated at every state change through the `~/.omp/plugins/node_modules/@feigi/fleet-ctl/scripts/fleet-run ledger.mjs` subcommands (`row`, `filed`, `ruled`, `check`, `read`, `dispatch`, `settle`, `review`, `drain`, `rotate`). Your context is the least durable thing in the run: it compacts, and a controller that loses the dispatch map or the filed list redoes finished work. Two duplicate tickets shipped in one run from exactly that.
64
64
 
65
65
  ## One line per ticket
66
66
 
@@ -187,7 +187,7 @@ A mismatch on a ticket whose issue is already CLOSED holds nothing: the tick pro
187
187
 
188
188
  ## The test command every gate runs
189
189
 
190
- **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 run what you hand them, so hand them the wrapped string as `<testCmd>` — `~/.fleet/bin/fleet-run suite-slot.mjs '<command>'`, each `'` inside the command written `'\''` — and it is still one command for every gate. The review wraps its own one run, so its args carry the bare command; a wrapped string handed to it anyway is harmless, the inner wrapper being the nested case. Omit it from the review args and the review (`review-core.mjs`, in a runner) reads the same cache itself, refusing outright when there is none; the fix-applier has no such fallback, so substituting `<testCmd>` with nothing leaves it no gate at all. See `references/isolation.md` (the stack-free test command).
190
+ **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 run what you hand them, so hand them 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 it is still one command for every gate. The review wraps its own one run, so its args carry the bare command; a wrapped string handed to it anyway is harmless, the inner wrapper being the nested case. Omit it from the review args and the review (`review-core.mjs`, in a runner) reads the same cache itself, refusing outright when there is none; the fix-applier has no such fallback, so substituting `<testCmd>` with nothing leaves it no gate at all. See `references/isolation.md` (the stack-free test command).
191
191
 
192
192
  ## Dispatching the members a wake names, in full
193
193