@feigi/fleet-ctl 3.71.4 → 3.71.6

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.71.4",
3
+ "version": "3.71.6",
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": {
@@ -264,9 +264,9 @@ if (!cmd) die("usage: ledger.mjs [--file <path>] [--require-file] row|token|file
264
264
  // `check`'s tail ALONE — narrower than the first pass, which called this
265
265
  // from `filed`, `row` and `ruled` too. The length rule is only sound where
266
266
  // the documented convention IS one quoted argument, and `check` is the only
267
- // subcommand where it is: both places that instruct a caller to run it spell
268
- // it `ledger.mjs check "<subject>"` (run-team/SKILL.md's finisher step,
269
- // review-and-fix.md's filing step), while run-team/SKILL.md's ledger section
267
+ // subcommand where it is: every caller that instructs running it spells it
268
+ // `ledger.mjs check "<subject>"` (the finisher's deferred-finding filing duty,
269
+ // review-and-fix's filing step), while run-team/SKILL.md's ledger section
270
270
  // spells the other three `filed <issue> <subject>`, `row <ticket> <text>` and
271
271
  // `ruled <pr> <decision>` — a bare multi-word tail, as did this file's own
272
272
  // usage strings for them. Applied there, the rule refused what the docs
@@ -304,7 +304,7 @@ if (!cmd) die("usage: ledger.mjs [--file <path>] [--require-file] row|token|file
304
304
  // answer it replaces was silent. One residual of that trade is not this
305
305
  // file's to close: SKILL.md's ledger section spells `check <subject>`
306
306
  // unquoted inside the same entry that spells `filed <issue> <subject>`, where
307
- // the two instructions that tell a caller to RUN it quote the subject.
307
+ // the instructions that tell a caller to RUN it quote the subject.
308
308
  //
309
309
  // Narrowed on `check` too, not closed: a lone stray with no subject beside it
310
310
  // is a one-element tail, so it is still taken as the subject and answered at
@@ -10,9 +10,9 @@ one it runs in. Phase 3's monitor paragraph points here instead of restating
10
10
  any of it. The merge bot's agent body is the one place this block is copied
11
11
  whole (see **Merge bot**); the other deliberate copy is named at the end.
12
12
 
13
- **zsh word-splits an unquoted command substitution's result; it does NOT split an unquoted parameter expansion.** See references/shell-traps.md.
13
+ **zsh word-splits an unquoted command substitution's result; it does NOT split an unquoted parameter expansion.**
14
14
 
15
- **Word the rule against the first row.** See references/shell-traps.md.
15
+ **Word the rule against the first row.**
16
16
 
17
17
  **Capture-then-loop needs `while IFS= read -r` fed by a heredoc**, which is
18
18
  line-exact under every shell:
@@ -26,9 +26,9 @@ $prs
26
26
  EOF
27
27
  ```
28
28
 
29
- The inline `$(printf '%s\n' "$prs")` form splits correctly too and is what Phase 3's block uses, but it splits on *every* whitespace character, so it is safe only for values that cannot contain one — PR numbers cannot, branch names and paths can. See references/shell-traps.md.
29
+ The inline `$(printf '%s\n' "$prs")` form splits correctly too and is what Phase 3's block uses, but it splits on *every* whitespace character, so it is safe only for values that cannot contain one — PR numbers cannot, branch names and paths can.
30
30
 
31
- **`</dev/null` every command inside a `while read` loop.** See references/shell-traps.md.
31
+ **`</dev/null` every command inside a `while read` loop.**
32
32
 
33
33
  **A probe that could not look emits an event; it never `continue`s.** Stated in
34
34
  full at *A probe that cannot read is a transition event, not silence* in Phase 3,
@@ -42,7 +42,7 @@ instead of a quiet one. A guard that drops an unreadable probe — `[ -n "$json"
42
42
  empty and `[ "" -eq 0 ]` passes. A bot's merge gate opened without ever reading
43
43
  an exit code.
44
44
 
45
- **`status` is a READ-ONLY variable in zsh**, an alias for `$?`. Name the variable anything else (`ci_status`). See references/shell-traps.md.
45
+ **`status` is a READ-ONLY variable in zsh**, an alias for `$?`. Name the variable anything else (`ci_status`).
46
46
 
47
47
  **The other deliberate copy is `env $cfg sh ./probe.sh`.** The first trap's
48
48
  mechanism bites argv as well as loops, and that instance stays written out in the