@feigi/fleet-ctl 3.61.0 → 3.62.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.
@@ -26,6 +26,11 @@ before your final message, and send nothing until
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`.
29
+
30
+ The controller does not acknowledge reports. Send once and exit; never re-send unless the controller asks by name.
31
+ Confirmation state includes warnings received and acted on, even when the outcome is no change: say so when you report.
32
+ A member runs its test suite in the foreground and blocks on it. Exit 75 from the suite is not a test result; run the command again.
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.
29
34
  ## kind: repair
30
35
 
31
36
  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 above.
@@ -85,6 +85,13 @@ before your final message, and send nothing until
85
85
  answers `valid`. Your final message is then one line,
86
86
  `<your name>: <outcome> <scratch>/reports/<your name>.json`, `<outcome>` the
87
87
  report's `outcome`.
88
+
89
+ Push, write your report, exit; never poll a CI run.
90
+
91
+ The controller does not acknowledge reports. Send once and exit; never re-send unless the controller asks by name.
92
+ Confirmation state includes warnings received and acted on, even when the outcome is no change: say so when you report.
93
+ A member runs its test suite in the foreground and blocks on it. Exit 75 from the suite is not a test result; run the command again.
94
+ 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.
88
95
  ## kind: dispositions-retry
89
96
 
90
97
  This is the one automatic retry of a dispositions mismatch. The mismatched
@@ -32,4 +32,6 @@ answers `valid`. Your final message is then one line,
32
32
  report's `outcome`.
33
33
 
34
34
  The controller does not acknowledge reports. Send once and exit; never re-send unless the controller asks by name.
35
+ Confirmation state includes warnings received and acted on, even when the outcome is no change: say so when you report.
35
36
  A member runs its test suite in the foreground and blocks on it. Exit 75 from the suite is not a test result; run the command again.
37
+ 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.
@@ -15,3 +15,4 @@ answers `valid`. Your final message is then one line,
15
15
  `merge-bot-<n>: done <scratch>/reports/merge-bot-<n>.json`.
16
16
 
17
17
  The controller does not acknowledge reports. Send once and exit; never re-send unless the controller asks by name.
18
+ Confirmation state includes warnings received and acted on, even when the outcome is no change: say so when you report.
@@ -0,0 +1,15 @@
1
+ ---
2
+ arg line one line
3
+ arg options options
4
+ arg hands hands
5
+ ---
6
+ ## kind: needs-triage
7
+ *Relabelled by the fleet controller.* Pulled for implementation and
8
+ returned: the brief does not decide what to build. Missing decision:
9
+ <one line>. Returning to /triage; `ready-for-agent` restored once decided.
10
+ ## kind: fork
11
+ *Relabelled by the fleet controller.* Pulled for implementation and
12
+ returned: the brief leaves a decision open. Open fork: <options>.
13
+ ## kind: hands
14
+ *Relabelled by the fleet controller.* Pulled for implementation and
15
+ returned: needs human hands — <hands>: <one line>.
@@ -21,3 +21,4 @@ never a directory whose last component is `pr` plus digits: the review creates
21
21
  that partition under the root itself.
22
22
 
23
23
  The controller does not acknowledge reports. Send once and exit; never re-send unless the controller asks by name.
24
+ Confirmation state includes warnings received and acted on, even when the outcome is no change: say so when you report.
@@ -184,9 +184,10 @@ the run. `dispatch` refuses a retired name and names the replacement — one
184
184
  retry letter past the highest the session has used on that number,
185
185
  `impl-42-b` for a ticket this session's earlier run worked as `impl-42` —
186
186
  `review` refuses a retired runner name and names the next free reviewer
187
- name, and `dispatch merge-bot` numbers past retired bots. The tick never
188
- reads `## Retired`: a ticket an earlier run worked is not claimed by it
189
- and can be shortlisted again.
187
+ name, and `dispatch merge-bot` numbers past retired bots. The tick reads
188
+ `## Retired` only to account for a transcript in the session directory: a
189
+ ticket an earlier run worked is not claimed by it and can be shortlisted
190
+ again.
190
191
  A line it cannot parse is skipped with a warning naming it, and the
191
192
  rotation still succeeds; a member name on a skipped line that carries an
192
193
  outcome is retired all the same, and a bare member token on a skipped row
@@ -278,16 +279,13 @@ unknown: fix that environment fault and check again; deriving would not
278
279
  help. This step is yours: one derivation
279
280
  per run start at most, never one per member, and a member never derives.
280
281
  Dispatch a `task` member named `derive-recipe`, agent
281
- `fleet-recipe-deriver`, and wait for its report — nothing in this run can
282
- claim before it lands:
283
-
284
- > Derive, prove and cache the Recipe of the repository at `<repo>`. Your
285
- > scratch directory is `<scratch>/derive-recipe/`; write nowhere else.
286
- > Follow your definition's procedure exactly, and end with its report line.
287
-
288
- `<repo>` is this main checkout's absolute path and `<scratch>` is the
289
- absolute path `scratch-root.mjs` prints (SKILL.md's **The scratch root is
290
- computed**), written into the prompt before you send it. The member reads the repository,
282
+ `fleet-recipe-deriver`, its prompt the brief `~/.fleet/bin/fleet-run
283
+ dispatch-prompt.mjs render recipe-deriver --member derive-recipe --repo <repo>
284
+ --scratch <scratch>` prints, and wait for its report — nothing in this run can
285
+ claim before it lands. `<repo>` is this main checkout's absolute path and
286
+ `<scratch>` is the absolute path `scratch-root.mjs` prints (SKILL.md's **The
287
+ scratch root is computed**); the renderer refuses a relative one. The member
288
+ reads the repository,
291
289
  proposes both commands and proves them with `recipe-prove.mjs` in a
292
290
  throwaway worktree of `origin/main`: the Install step must leave the tree
293
291
  clean, and the Test entrypoint must be shown to run real tests — the