@feigi/fleet-ctl 3.64.4 → 3.64.5

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.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@feigi/fleet-ctl",
3
- "version": "3.64.4",
3
+ "version": "3.64.5",
4
4
  "description": "Agent fleet: run-team controller, merge bot, PR reviewer, and the ticket pipeline they share",
5
5
  "license": "Apache-2.0",
6
6
  "repository": {
@@ -966,8 +966,10 @@ impl-<N>)` then stops the whole tick, not only that member's ticket. It
966
966
  clears once the member settles: one settled `killed` or `released` gets
967
967
  `tier-unverifiable=` from the same check, and one settled any other way ran,
968
968
  so pass the directory that dispatched it, as above. Until it settles,
969
- follow the carried token's reconciliation in phase 0: `proc://` reads
970
- `running` → wait; dead → the Member-killed row.
969
+ follow the carried token's reconciliation in references/phase-0.md, the
970
+ "Resume the claims a dead run left without a PR" section, under its
971
+ `prior: ancestor` branch: `proc://` reads `running` → wait; dead → the
972
+ Member-killed row.
971
973
 
972
974
  **Run the check right after the dispatch, and never reinstall the plugin or
973
975
  change `modelRoles` while any member is unchecked.** The check reads the
@@ -1621,7 +1623,9 @@ depth** guard table applied in code. Act on each line as it reads:
1621
1623
  since HEAD moved off that commit and nobody has looked at the move, and
1622
1624
  resolve any stray paths, which the line does not name; only then re-record.
1623
1625
  - `MAIN-CHECKOUT-NO-BASELINE …` with `HOLD (main checkout no baseline)` — no
1624
- baseline was recorded. Yours to fix: run Phase 0's `--record`. A baseline
1626
+ baseline was recorded. Yours to fix: run
1627
+ `~/.fleet/bin/fleet-run main-checkout.mjs --record`, which references/phase-0.md
1628
+ describes under "Record the main-checkout baseline". A baseline
1625
1629
  that vanished mid-run is not a fresh run — report it to the maintainer
1626
1630
  before recording over whatever the tree now holds.
1627
1631
  - `PHASE0-INCOMPLETE <step>[, <step>…] …`, printed first above the rows,
@@ -1773,7 +1777,8 @@ record:
1773
1777
 
1774
1778
  - `heartbeat STALLED, controller gone` — the run that stranded them is dead.
1775
1779
  Its claims without a PR come back through the next run's phase 0
1776
- stranded-claim step, and its open PRs through the fold-in.
1780
+ stranded-claim step (references/phase-0.md, "Resume the claims a dead run
1781
+ left without a PR"), and its open PRs through the fold-in.
1777
1782
  - `heartbeat not beating, controller alive (pid N)`, or `(this session's
1778
1783
  earlier run)` — a controller that stopped beating and kept going. Nothing
1779
1784
  died, so nothing is resumed; when that controller is you, the fix is to
@@ -3572,7 +3577,7 @@ live count from it, so nobody states one. Write neither by hand:
3572
3577
  the previous run was this session's own, when it first writes the rows and
3573
3578
  `## Dispatched` entries still live into a new ledger, and every other
3574
3579
  settled name, or name given an out-of-vocabulary outcome, into its
3575
- `## Retired` (phase 0 says which). Refused
3580
+ `## Retired` (references/phase-0.md, "Rotate the ledger", says which). Refused
3576
3581
  while the recorded controller is alive and not this run's ancestor, ledger
3577
3582
  or none — or, with no record and a ledger to move, while the heartbeat mark
3578
3583
  is still beating, or a tick or ledger write is inside its window with no
@@ -3580,8 +3585,8 @@ live count from it, so nobody states one. Write neither by hand:
3580
3585
  table cannot be read, or `.fleet/heartbeat.json` exists but cannot be used
3581
3586
  (unreadable, not JSON, not an object, or a `controller` it cannot judge);
3582
3587
  with no ledger and no such refusal it moves nothing and exits 0. Then it
3583
- records this run's controller in `.fleet/heartbeat.json`. Phase 0 states
3584
- the guard.
3588
+ records this run's controller in `.fleet/heartbeat.json`. The guard is
3589
+ stated in references/phase-0.md, "Rotate the ledger".
3585
3590
 
3586
3591
  `row` refuses a malformed member token anywhere in its text — one whose outcome
3587
3592
  is outside the vocabulary above, e.g. `merge-bot-1=dispatched` — at exit 2,