@feigi/fleet-ctl 3.82.19 → 3.82.20
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/agents/fleet-merge-bot.agent.md +6 -6
- package/package.json +1 -1
- package/skills/run-team/SKILL.md +177 -579
- package/skills/run-team/references/ci-and-staleness.md +47 -0
- package/skills/run-team/references/ci-watcher.md +138 -3
- package/skills/run-team/references/close-out.md +28 -0
- package/skills/run-team/references/failure-handling.md +43 -0
- package/skills/run-team/references/finisher.md +185 -0
- package/skills/run-team/references/instruments.md +20 -0
- package/skills/run-team/references/isolation.md +10 -0
- package/skills/run-team/references/ledger.md +4 -0
- package/skills/run-team/references/member-lifecycle.md +18 -0
- package/skills/run-team/references/phase-0.md +50 -0
- package/skills/run-team/references/pull.md +36 -1
- package/skills/run-team/references/reviewers.md +81 -0
- package/skills/run-team/references/shell-traps.md +10 -9
- package/skills/run-team/references/tick-rows.md +35 -0
|
@@ -18,9 +18,9 @@ Your report is the one file you write outside it: `<scratch>/reports/merge-bot-<
|
|
|
18
18
|
the path your brief names, holding every PR you merged in `merged`. Your final
|
|
19
19
|
message is the one line your brief gives, `merge-bot-<n>: done <path>`.
|
|
20
20
|
|
|
21
|
-
The shell traps below are copied from the controller's skill
|
|
22
|
-
`
|
|
23
|
-
|
|
21
|
+
The shell traps below are copied from the controller's skill, `run-team`. In
|
|
22
|
+
them `references/ci-watcher.md` is that skill's file on the controller's CI
|
|
23
|
+
watcher, which you do not run; each trap applies to every shell
|
|
24
24
|
command and loop you run.
|
|
25
25
|
|
|
26
26
|
**zsh word-splits an unquoted command substitution's result; it does NOT split
|
|
@@ -54,7 +54,7 @@ EOF
|
|
|
54
54
|
```
|
|
55
55
|
|
|
56
56
|
The inline `$(printf '%s\n' "$prs")` form splits correctly too and is what the
|
|
57
|
-
watcher block
|
|
57
|
+
watcher block in `references/ci-watcher.md` uses, but it splits on *every* whitespace character, so it is safe only
|
|
58
58
|
for values that cannot contain one — PR numbers cannot, branch names and paths
|
|
59
59
|
can. Measured on a two-line list whose first value is `two words`: three
|
|
60
60
|
iterations through `$(printf …)`, two through `while IFS= read -r`. On an empty
|
|
@@ -70,8 +70,8 @@ word-split bug, so a correct heredoc fix missing this half looks exactly like no
|
|
|
70
70
|
fix at all, and reads as one.
|
|
71
71
|
|
|
72
72
|
**A probe that could not look emits an event; it never `continue`s.** Stated in
|
|
73
|
-
full at *A probe that cannot read is a transition event, not silence*
|
|
74
|
-
and it binds every watcher
|
|
73
|
+
full at *A probe that cannot read is a transition event, not silence* in `references/ci-watcher.md`,
|
|
74
|
+
and it binds every watcher rather than that one block: the third
|
|
75
75
|
value beside pass and fail is what turns a broken loop into a loud failure
|
|
76
76
|
instead of a quiet one. A guard that drops an unreadable probe — `[ -n "$json" ]
|
|
77
77
|
|| continue` — makes *could not look* indistinguishable from *nothing to report*.
|