@feigi/fleet-ctl 3.117.0 → 3.117.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.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@feigi/fleet-ctl",
3
- "version": "3.117.0",
3
+ "version": "3.117.1",
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": {
@@ -5,6 +5,8 @@ argument-hint: "[in-flight] [cost|speed]"
5
5
  disable-model-invocation: true
6
6
  ---
7
7
 
8
+ Label names in this file are roles; the Label map gives the string to type; a member never derives the map.
9
+
8
10
  Run `next-ticket`, `review-and-fix`, `run-merge-bot` as one fleet. You are the
9
11
  **controller**, in the main thread, never a member.
10
12
 
@@ -12,13 +14,11 @@ Run `next-ticket`, `review-and-fix`, `run-merge-bot` as one fleet. You are the
12
14
  a positive integer, default 5, and the Objective, default `cost`.
13
15
  Merge bot is at most one, not configurable.
14
16
 
15
- The war story behind a rule ending `See references/<file>` lives in that file; load
16
- it only when a member needs the *why*. A rule without that line carries its
17
- reasoning inline — nothing is missing.
17
+ A rule ending `See references/<file>` keeps its war story there, read only for the *why*; a rule without that line carries its reasoning inline.
18
18
 
19
19
  ## Invariants
20
20
 
21
- These hold in every phase: check a wake against them before you act on it, and report any evidence that one is broken.
21
+ These hold in every phase: check each wake against them, and report evidence that one is broken.
22
22
 
23
23
  - In-flight tickets at most the bound (default 5), at most one merge bot; the bound counts tickets, not live agents.
24
24
  - A grandchild surfaces as its own task-notification; an unrecognized task-id is not a member reporting done.
@@ -28,7 +28,7 @@ These hold in every phase: check a wake against them before you act on it, and r
28
28
  - Every member acts through the maintainer's `gh` credentials, so no write is attributable: when a label moves unexpectedly, ask members directly, rule out automation with `grep -rn '<label>' .github/workflows/`, and do not re-add it.
29
29
  - Phase 1 is serial; everything else may run concurrently.
30
30
 
31
- The reasoning behind each line is in references/invariants.md.
31
+ Reasoning: references/invariants.md.
32
32
 
33
33
  ## Phase 0 — shortlist
34
34
 
@@ -33,4 +33,6 @@ A member runs its test suite in the foreground and blocks on it. Exit 75 from th
33
33
  Never run `pkill -f` on a pattern: members share one process table, so a pattern such as a test file's name matches every member's run, not only yours. Clearing your own leftover process needs its PID; report a stalled run to the controller instead.
34
34
  ## kind: repair
35
35
 
36
+ Label names in this file are roles; the Label map gives the string to type; a member never derives the map.
37
+
36
38
  An earlier finisher on this PR reported `labelled`, but its read-back did not carry `ready-to-merge`: you are the repair finisher. Duty 3's script decides whether the label is on, as your agent definition says.
@@ -1,5 +1,7 @@
1
1
  # CI reading and staleness
2
2
 
3
+ Label names in this file are roles; the Label map gives the string to type; a member never derives the map.
4
+
3
5
  Why green not verdict, why absence is its own verdict, why conclusion not
4
6
  stable, why behind-count only honest signal, why the tick runs on every wake
5
7
  and why the beat is shaped as it is. Assertions live in SKILL.md's wake table,
@@ -1,5 +1,7 @@
1
1
  # The finisher: why its gate and duties are shaped the way they are
2
2
 
3
+ Label names in this file are roles; the Label map gives the string to type; a member never derives the map.
4
+
3
5
  Evidence for the finisher rules the finisher's agent body, `agents/fleet-finisher.agent.md`, and SKILL.md's **The finisher gate** state, keyed by the rule each justifies.
4
6
 
5
7
  ## The fix-applier pushes and exits; the finisher is dispatched fresh
@@ -1,5 +1,7 @@
1
1
  # Invariants: the full statements
2
2
 
3
+ Label names in this file are roles; the Label map gives the string to type; a member never derives the map.
4
+
3
5
  The invariants SKILL.md states one line each, as they read before they were tightened.
4
6
 
5
7
  - In-flight tickets at most the bound (default 5), ≤ 1 merge bot. The bound
@@ -1,5 +1,7 @@
1
1
  # The run ledger: the evidence behind its rules
2
2
 
3
+ Label names in this file are roles; the Label map gives the string to type; a member never derives the map.
4
+
3
5
  Evidence for the rules SKILL.md's wake and dispatch sections state, keyed by the rule each justifies.
4
6
 
5
7
  ## Writer policy: every write is serialized by `<file>.lock`
@@ -1,5 +1,7 @@
1
1
  # Member lifecycle: naming, fresh context, recovery
2
2
 
3
+ Label names in this file are roles; the Label map gives the string to type; a member never derives the map.
4
+
3
5
  Why member name load-bearing, why every member single-use, how a member's job outcome (`completed`/`failed`/`cancelled`) and peer liveness (`running`/`idle`/`parked`) decide its recovery. Assertions these justify live in SKILL.md's wake table, Dispatching the members a wake names, Reading a review result, A member's claims, Failure handling sections; evidence here.
4
6
 
5
7
  ## Every member is named
@@ -1,5 +1,7 @@
1
1
  # Landing a change on main
2
2
 
3
+ Label names in this file are roles; the Label map gives the string to type; a member never derives the map.
4
+
3
5
  Evidence for the rules SKILL.md states in **A mid-run tooling fix** and in the `ready-to-merge` wake, keyed by the rule each justifies.
4
6
 
5
7
  ## When to fix the tooling mid-run, and its shape
@@ -1,5 +1,7 @@
1
1
  # Phase 0: what each step does and why
2
2
 
3
+ Label names in this file are roles; the Label map gives the string to type; a member never derives the map.
4
+
3
5
  `phase0.mjs` runs the start sequence and writes the receipt `.fleet/phase0.json`; SKILL.md's phase 0 step 0 says how to drive it and what to do about each `NEED` line. This file is what each step means, in the order the script runs them, for the controller to read when a step refuses or a line asks for more than SKILL.md says. One heading per step.
4
6
 
5
7
  **Run it from a Python eval cell, never the bash tool.** That kernel's
@@ -1,5 +1,7 @@
1
1
  # The Pull: what each step does and why
2
2
 
3
+ Label names in this file are roles; the Label map gives the string to type; a member never derives the map.
4
+
3
5
  `pull.mjs` runs the Pull; SKILL.md's phase 1 says how to drive it, how to read the tick's `PULL` row and how to answer the questions it asks. This file is what each step means, and the measured reasons behind them, for the controller to read when a step refuses or an answer needs more than SKILL.md says.
4
6
 
5
7
  ## The steps
@@ -174,8 +176,8 @@ terminating in exactly one dispatch or an empty shortlist:
174
176
  for. Give exactly one — the direction is not inferable from the string, and
175
177
  the wrong one answers the opposite verdict with full confidence.
176
178
 
177
- A needle that itself starts with `--` — `--label ready-for-agent`
178
- is one this backlog carries — needs the end-of-options separator: `--gone
179
+ A needle that itself starts with `--` — `--label ready-for-agent` is an
180
+ illustration of one, a role name and not a string to type — needs the end-of-options separator: `--gone
179
181
  -- '<string>'`/`--present -- '<string>'`. Given bare, with no `--`
180
182
  immediately before it, the value guard still refuses it — `staleness:
181
183
  --gone needs a value` — at exit 2, a could-not-check to admit and annotate,
@@ -317,10 +319,10 @@ fleet has already judged unimplementable straight to the next member.
317
319
  yours to judge: `pull.mjs` finds it at step 3 and posts its own comment naming
318
320
  the stranded comment's heading line and URL, which is not one of the
319
321
  `briefs/relabel.md` comments.
320
- `gh issue edit <N> --remove-label ready-for-agent --add-label <label>` (no
322
+ `gh issue edit <N> --remove-label "<ready-for-agent string>" --add-label "<label string>"` (no
321
323
  `in-progress` to drop — it was never claimed), preceded by exactly one comment,
322
324
  the one `~/.fleet/bin/fleet-run dispatch-prompt.mjs render relabel --kind <kind> …`
323
- prints. `--kind needs-triage` takes `--line`, the one-line missing decision;
325
+ prints. Each `<… string>` is what `~/.fleet/bin/fleet-run label-map.mjs show <role>` prints for that role — `<label string>` for the role the cause names — and you type that string, not the role name; where the rendered comment names `ready-for-agent`, file the string `~/.fleet/bin/fleet-run label-map.mjs show ready-for-agent` prints in its place. `--kind needs-triage` takes `--line`, the one-line missing decision;
324
326
  `--kind fork` takes `--options`, the options verbatim from the brief, and is
325
327
  the `ready-for-human` comment for a fork; `--kind hands` takes `--hands`,
326
328
  one of external access, manual testing or judgment during the work, and
@@ -1,5 +1,7 @@
1
1
  # Reaping merged branches and worktrees
2
2
 
3
+ Label names in this file are roles; the Label map gives the string to type; a member never derives the map.
4
+
3
5
  Why reap runs after each merge pass, why `commit-commands:clean_gone` disqualified, why hand-rolled reap shaped this way (implemented by `reap.sh`), and why a claim that never became a PR needs a different script (`release-ticket.sh`). Assertions these justify live in SKILL.md's **Merge-bot pass reports done** wake and its Failure handling row for a claim abandoned mid-run; evidence here.
4
6
 
5
7
  ## Reap after each merge pass, not once at the end
@@ -1,5 +1,7 @@
1
1
  # The tick's rows: what each asks of the controller
2
2
 
3
+ Label names in this file are roles; the Label map gives the string to type; a member never derives the map.
4
+
3
5
  The full text of each row `fleet-tick.mjs` prints and what it asks of the controller. SKILL.md's **The tick's rows** carries one line for each.
4
6
 
5
7
  - `PULL #<N> …` — one Pull per named ticket, in the order printed: phase 1's