@feigi/fleet-ctl 0.0.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.
Files changed (245) hide show
  1. package/.claude-plugin/plugin.json +9 -0
  2. package/LICENSE +202 -0
  3. package/NOTICE +18 -0
  4. package/agents/fleet-finisher.agent.md +7 -0
  5. package/agents/fleet-implementer-alt.agent.md +210 -0
  6. package/agents/fleet-implementer.agent.md +210 -0
  7. package/agents/fleet-merge-bot.agent.md +7 -0
  8. package/agents/fleet-review-comments.agent.md +40 -0
  9. package/agents/fleet-review-correctness.agent.md +43 -0
  10. package/agents/fleet-review-runner.agent.md +73 -0
  11. package/agents/fleet-review-silent-failure.agent.md +49 -0
  12. package/agents/fleet-review-simplify.agent.md +46 -0
  13. package/agents/fleet-review-snapshot.agent.md +24 -0
  14. package/agents/fleet-review-tests.agent.md +46 -0
  15. package/agents/fleet-review-types.agent.md +41 -0
  16. package/agents/fleet-review-verifier.agent.md +29 -0
  17. package/commands/review-and-fix.md +98 -0
  18. package/commands/run-merge-bot.md +357 -0
  19. package/commands/run-team-help.md +17 -0
  20. package/package.json +23 -0
  21. package/scripts/agent-test-dir-prose.test.mjs +59 -0
  22. package/scripts/agent-test.test.mjs +1636 -0
  23. package/scripts/ambient-git-vars-mjs-prose.test.mjs +354 -0
  24. package/scripts/ambient-git-vars-prose.test.mjs +192 -0
  25. package/scripts/ancestry-check-position-prose.test.mjs +175 -0
  26. package/scripts/apply-ruleset.test.mjs +420 -0
  27. package/scripts/arg-header-probes-prose.test.mjs +393 -0
  28. package/scripts/arg.mjs +600 -0
  29. package/scripts/arg.test.mjs +1354 -0
  30. package/scripts/board-cli.test.mjs +694 -0
  31. package/scripts/board-identity.test.mjs +429 -0
  32. package/scripts/board-liveness-banner.test.mjs +119 -0
  33. package/scripts/board-prev-shape.test.mjs +229 -0
  34. package/scripts/board-tryparse-null.test.mjs +119 -0
  35. package/scripts/board.html +471 -0
  36. package/scripts/board.mjs +2037 -0
  37. package/scripts/board.test.mjs +3086 -0
  38. package/scripts/brief-after-cut-prose.test.mjs +53 -0
  39. package/scripts/candidates-exit3-prose.test.mjs +302 -0
  40. package/scripts/candidates.mjs +674 -0
  41. package/scripts/candidates.test.mjs +2101 -0
  42. package/scripts/caveat-unification-prose.test.mjs +98 -0
  43. package/scripts/ci-comment-rot-prose.test.mjs +2025 -0
  44. package/scripts/ci-completes-premise-prose.test.mjs +257 -0
  45. package/scripts/ci-state-prose.test.mjs +113 -0
  46. package/scripts/ci-state.mjs +761 -0
  47. package/scripts/ci-state.test.mjs +1640 -0
  48. package/scripts/ci-vacuous-green.test.mjs +368 -0
  49. package/scripts/citation-sweep-prose.test.mjs +1572 -0
  50. package/scripts/claim-lifecycle.test.mjs +185 -0
  51. package/scripts/claim-ticket.sh +417 -0
  52. package/scripts/claim-ticket.test.mjs +1121 -0
  53. package/scripts/closing-keyword-prose.test.mjs +193 -0
  54. package/scripts/cockpit-launch-idempotent-prose.test.mjs +165 -0
  55. package/scripts/cockpit-tick-nonblocking.test.mjs +210 -0
  56. package/scripts/compute-board.mjs +579 -0
  57. package/scripts/compute-board.test.mjs +1060 -0
  58. package/scripts/compute-spend.mjs +329 -0
  59. package/scripts/compute-spend.test.mjs +451 -0
  60. package/scripts/cross-repo-citation-prose.test.mjs +156 -0
  61. package/scripts/cwd-isolation-pins.mjs +83 -0
  62. package/scripts/dedupe-guard-prose.test.mjs +243 -0
  63. package/scripts/derive-testcmd.sh +239 -0
  64. package/scripts/derive-testcmd.test.mjs +380 -0
  65. package/scripts/diff-stats.mjs +231 -0
  66. package/scripts/diff-stats.test.mjs +408 -0
  67. package/scripts/dispatch-block-golden-prose.test.mjs +1024 -0
  68. package/scripts/dispatch-block-pins-prose.test.mjs +615 -0
  69. package/scripts/drop-merged-label.sh +173 -0
  70. package/scripts/drop-merged-label.test.mjs +480 -0
  71. package/scripts/expected-jobs-prose.test.mjs +80 -0
  72. package/scripts/filing-bar-seat-prose.test.mjs +242 -0
  73. package/scripts/filing-claim-bar-prose.test.mjs +166 -0
  74. package/scripts/finisher-dispatch-premise-prose.test.mjs +312 -0
  75. package/scripts/finisher-halt-prose.test.mjs +106 -0
  76. package/scripts/finisher-name-prose.test.mjs +134 -0
  77. package/scripts/finisher-own-tree-prose.test.mjs +285 -0
  78. package/scripts/finisher-pin-race-prose.test.mjs +339 -0
  79. package/scripts/fix-applier-correction-rules-prose.test.mjs +201 -0
  80. package/scripts/fix-applier-result-file-prose.test.mjs +100 -0
  81. package/scripts/fleet-bootstrap +155 -0
  82. package/scripts/fleet-heartbeat.mjs +272 -0
  83. package/scripts/fleet-heartbeat.test.mjs +450 -0
  84. package/scripts/fleet-provenance +207 -0
  85. package/scripts/fleet-provenance.test.mjs +64 -0
  86. package/scripts/fleet-run +148 -0
  87. package/scripts/fleet-run.test.mjs +90 -0
  88. package/scripts/fleet-state.mjs +400 -0
  89. package/scripts/fleet-state.test.mjs +373 -0
  90. package/scripts/fleet-tick-prose.test.mjs +299 -0
  91. package/scripts/fleet-tick.mjs +832 -0
  92. package/scripts/fleet-tick.test.mjs +1332 -0
  93. package/scripts/force-with-lease-reason-prose.test.mjs +184 -0
  94. package/scripts/frontmatter-allowlist.json +64 -0
  95. package/scripts/frontmatter-check.mjs +256 -0
  96. package/scripts/frontmatter-check.test.mjs +436 -0
  97. package/scripts/git-env.mjs +124 -0
  98. package/scripts/git-env.test.mjs +149 -0
  99. package/scripts/git-status-untracked-mode-sweep.test.mjs +216 -0
  100. package/scripts/gone-walk.test.mjs +213 -0
  101. package/scripts/gp-sep-invariant-prose.test.mjs +188 -0
  102. package/scripts/head-moved-after-label-prose.test.mjs +233 -0
  103. package/scripts/immutable-body-claim-prose.test.mjs +413 -0
  104. package/scripts/implementer-model-tier.test.mjs +643 -0
  105. package/scripts/inflight-citation-prose.test.mjs +144 -0
  106. package/scripts/inflight-exit2-prose.test.mjs +81 -0
  107. package/scripts/inflight-probe-guard-prose.test.mjs +109 -0
  108. package/scripts/inflight-scan-scope-prose.test.mjs +57 -0
  109. package/scripts/inflight.sh +1106 -0
  110. package/scripts/inflight.test.mjs +2984 -0
  111. package/scripts/injection-control-prose.test.mjs +404 -0
  112. package/scripts/install-root-audit.test.mjs +464 -0
  113. package/scripts/instrument-check-prose.test.mjs +235 -0
  114. package/scripts/instruments.sh +394 -0
  115. package/scripts/instruments.test.mjs +787 -0
  116. package/scripts/issue-tracker-prose.test.mjs +71 -0
  117. package/scripts/json.sh +248 -0
  118. package/scripts/json.test.mjs +364 -0
  119. package/scripts/ledger-dispatch.test.mjs +516 -0
  120. package/scripts/ledger-grammar.mjs +85 -0
  121. package/scripts/ledger-grammar.test.mjs +142 -0
  122. package/scripts/ledger-read-require-file.test.mjs +197 -0
  123. package/scripts/ledger.mjs +1753 -0
  124. package/scripts/ledger.test.mjs +3554 -0
  125. package/scripts/line-distance-prose.test.mjs +245 -0
  126. package/scripts/liveness-rationale-prose.test.mjs +83 -0
  127. package/scripts/locale-pin-prose.test.mjs +189 -0
  128. package/scripts/member-outcome-prose.test.mjs +167 -0
  129. package/scripts/member-outcomes-header.test.mjs +148 -0
  130. package/scripts/member-outcomes-prose.test.mjs +63 -0
  131. package/scripts/member-outcomes.mjs +231 -0
  132. package/scripts/member-outcomes.test.mjs +507 -0
  133. package/scripts/member-prompt-prose.test.mjs +161 -0
  134. package/scripts/member-record.mjs +605 -0
  135. package/scripts/member-record.test.mjs +516 -0
  136. package/scripts/member-write-guard.mjs +279 -0
  137. package/scripts/member-write-guard.test.mjs +211 -0
  138. package/scripts/merge-commit-probe-prose.test.mjs +122 -0
  139. package/scripts/merge-gate.mjs +262 -0
  140. package/scripts/merge-gate.test.mjs +613 -0
  141. package/scripts/muted-git-guard-sweep.test.mjs +493 -0
  142. package/scripts/net-ssh-precedence-prose.test.mjs +91 -0
  143. package/scripts/net-watchdog-prose.test.mjs +79 -0
  144. package/scripts/net.sh +409 -0
  145. package/scripts/net.test.mjs +211 -0
  146. package/scripts/no-ci-gate-prose.test.mjs +108 -0
  147. package/scripts/no-undo-audit.sh +1134 -0
  148. package/scripts/no-undo-audit.test.mjs +3965 -0
  149. package/scripts/no-wave.test.mjs +138 -0
  150. package/scripts/node-floor-sweep.test.mjs +611 -0
  151. package/scripts/pointer-target-prose.test.mjs +186 -0
  152. package/scripts/pr-overlap.mjs +417 -0
  153. package/scripts/pr-overlap.test.mjs +695 -0
  154. package/scripts/printf-die-sweep.test.mjs +384 -0
  155. package/scripts/prompt-renderer.mjs +39 -0
  156. package/scripts/prompt-renderer.test.mjs +68 -0
  157. package/scripts/prose-pin.mjs +808 -0
  158. package/scripts/prose-pin.test.mjs +1034 -0
  159. package/scripts/prove-merge.sh +228 -0
  160. package/scripts/prove-merge.test.mjs +995 -0
  161. package/scripts/pull-table-relabel-prose.test.mjs +60 -0
  162. package/scripts/quiet-payload-prose.test.mjs +222 -0
  163. package/scripts/reap.sh +1768 -0
  164. package/scripts/reap.test.mjs +4395 -0
  165. package/scripts/reaping-prose.test.mjs +159 -0
  166. package/scripts/refuter-scratch-prose.test.mjs +135 -0
  167. package/scripts/release-label-required-prose.test.mjs +71 -0
  168. package/scripts/release-label-split-prose.test.mjs +169 -0
  169. package/scripts/release-ticket.sh +1716 -0
  170. package/scripts/release-ticket.test.mjs +5106 -0
  171. package/scripts/renovate-release-contract.test.mjs +379 -0
  172. package/scripts/repo-root.mjs +544 -0
  173. package/scripts/repo-root.test.mjs +873 -0
  174. package/scripts/reporter-output-rule-prose.test.mjs +208 -0
  175. package/scripts/review-agent-report-only.test.mjs +49 -0
  176. package/scripts/review-core-cwd-isolation.test.mjs +374 -0
  177. package/scripts/review-core-reads.test.mjs +478 -0
  178. package/scripts/review-core-refuter-scratch.test.mjs +148 -0
  179. package/scripts/review-core-snapshot-path.test.mjs +777 -0
  180. package/scripts/review-core-specialist-scratch.test.mjs +189 -0
  181. package/scripts/review-core-testcmd.test.mjs +288 -0
  182. package/scripts/review-core-unrun.test.mjs +530 -0
  183. package/scripts/review-core-unverified-discriminant.test.mjs +208 -0
  184. package/scripts/review-core.mjs +1028 -0
  185. package/scripts/review-eval-resolver-path.test.mjs +55 -0
  186. package/scripts/review-eval.mjs +197 -0
  187. package/scripts/review-host-fixture.mjs +73 -0
  188. package/scripts/review-in-run-retry.test.mjs +187 -0
  189. package/scripts/review-no-vendor-dispatch.test.mjs +45 -0
  190. package/scripts/review-path-default.test.mjs +796 -0
  191. package/scripts/review-runner-spawns.test.mjs +93 -0
  192. package/scripts/review-runner.test.mjs +155 -0
  193. package/scripts/review-tier-audit.test.mjs +140 -0
  194. package/scripts/run-artifact-pr-prose.test.mjs +341 -0
  195. package/scripts/run-merge-bot-prose.test.mjs +1391 -0
  196. package/scripts/scratch-partition-invariant-prose.test.mjs +74 -0
  197. package/scripts/scripts-path-citation-sweep.test.mjs +73 -0
  198. package/scripts/section-between-guard-prose.test.mjs +378 -0
  199. package/scripts/select-dimensions.test.mjs +674 -0
  200. package/scripts/shared-refusal.test.mjs +388 -0
  201. package/scripts/shell-traps-prose.test.mjs +507 -0
  202. package/scripts/shortlist.mjs +355 -0
  203. package/scripts/shortlist.test.mjs +366 -0
  204. package/scripts/slow-transport.mjs +72 -0
  205. package/scripts/snapshot-repo.test.mjs +772 -0
  206. package/scripts/snapshot-runner-audience-prose.test.mjs +129 -0
  207. package/scripts/spend-view.test.mjs +312 -0
  208. package/scripts/staleness-qualifier-prose.test.mjs +251 -0
  209. package/scripts/staleness-verdict-prose.test.mjs +142 -0
  210. package/scripts/staleness.mjs +414 -0
  211. package/scripts/staleness.test.mjs +893 -0
  212. package/scripts/stalled-member-liveness-prose.test.mjs +219 -0
  213. package/scripts/stash-prohibition-prose.test.mjs +313 -0
  214. package/scripts/strip-comments.mjs +44 -0
  215. package/scripts/tier-check.mjs +468 -0
  216. package/scripts/tier-check.test.mjs +726 -0
  217. package/scripts/tier-guard-gate-prose.test.mjs +216 -0
  218. package/scripts/tier-outcomes-header.test.mjs +586 -0
  219. package/scripts/tier-outcomes.mjs +441 -0
  220. package/scripts/tier-outcomes.test.mjs +342 -0
  221. package/scripts/tier-roles.mjs +250 -0
  222. package/scripts/tier-roles.test.mjs +316 -0
  223. package/scripts/tracker-block-copy-prose.test.mjs +288 -0
  224. package/scripts/triage-labels-gloss-prose.test.mjs +97 -0
  225. package/scripts/unattended-git-sweep.test.mjs +142 -0
  226. package/scripts/verify-sha-exit2-prose.test.mjs +269 -0
  227. package/scripts/verify-sha.sh +117 -0
  228. package/scripts/verify-sha.test.mjs +693 -0
  229. package/scripts/watcher-degraded-block.test.mjs +372 -0
  230. package/scripts/watcher-key-prose.test.mjs +106 -0
  231. package/scripts/within-run-pair-prose.test.mjs +208 -0
  232. package/scripts/worktree-audit.sh +482 -0
  233. package/scripts/worktree-audit.test.mjs +1407 -0
  234. package/scripts/worktree-head-prose.test.mjs +276 -0
  235. package/scripts/worktree-listing-sweep.test.mjs +217 -0
  236. package/scripts/worktree-model-prose.test.mjs +216 -0
  237. package/scripts/worktree.sh +470 -0
  238. package/skills/next-ticket/SKILL.md +138 -0
  239. package/skills/run-team/SKILL.md +3603 -0
  240. package/skills/run-team/references/ci-and-staleness.md +75 -0
  241. package/skills/run-team/references/correction-tickets.md +37 -0
  242. package/skills/run-team/references/isolation.md +23 -0
  243. package/skills/run-team/references/member-lifecycle.md +73 -0
  244. package/skills/run-team/references/reaping.md +73 -0
  245. package/skills/sizing-a-ticket/SKILL.md +39 -0
@@ -0,0 +1,9 @@
1
+ {
2
+ "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
3
+ "name": "fleet-ctl",
4
+ "description": "Agent fleet: run-team controller, merge bot, PR reviewer, and the ticket pipeline they share",
5
+ "author": {
6
+ "name": "Christian Ziegler",
7
+ "email": "christian.ziegler@core-concepts.de"
8
+ }
9
+ }
package/LICENSE ADDED
@@ -0,0 +1,202 @@
1
+
2
+ Apache License
3
+ Version 2.0, January 2004
4
+ http://www.apache.org/licenses/
5
+
6
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
7
+
8
+ 1. Definitions.
9
+
10
+ "License" shall mean the terms and conditions for use, reproduction,
11
+ and distribution as defined by Sections 1 through 9 of this document.
12
+
13
+ "Licensor" shall mean the copyright owner or entity authorized by
14
+ the copyright owner that is granting the License.
15
+
16
+ "Legal Entity" shall mean the union of the acting entity and all
17
+ other entities that control, are controlled by, or are under common
18
+ control with that entity. For the purposes of this definition,
19
+ "control" means (i) the power, direct or indirect, to cause the
20
+ direction or management of such entity, whether by contract or
21
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
22
+ outstanding shares, or (iii) beneficial ownership of such entity.
23
+
24
+ "You" (or "Your") shall mean an individual or Legal Entity
25
+ exercising permissions granted by this License.
26
+
27
+ "Source" form shall mean the preferred form for making modifications,
28
+ including but not limited to software source code, documentation
29
+ source, and configuration files.
30
+
31
+ "Object" form shall mean any form resulting from mechanical
32
+ transformation or translation of a Source form, including but
33
+ not limited to compiled object code, generated documentation,
34
+ and conversions to other media types.
35
+
36
+ "Work" shall mean the work of authorship, whether in Source or
37
+ Object form, made available under the License, as indicated by a
38
+ copyright notice that is included in or attached to the work
39
+ (an example is provided in the Appendix below).
40
+
41
+ "Derivative Works" shall mean any work, whether in Source or Object
42
+ form, that is based on (or derived from) the Work and for which the
43
+ editorial revisions, annotations, elaborations, or other modifications
44
+ represent, as a whole, an original work of authorship. For the purposes
45
+ of this License, Derivative Works shall not include works that remain
46
+ separable from, or merely link (or bind by name) to the interfaces of,
47
+ the Work and Derivative Works thereof.
48
+
49
+ "Contribution" shall mean any work of authorship, including
50
+ the original version of the Work and any modifications or additions
51
+ to that Work or Derivative Works thereof, that is intentionally
52
+ submitted to Licensor for inclusion in the Work by the copyright owner
53
+ or by an individual or Legal Entity authorized to submit on behalf of
54
+ the copyright owner. For the purposes of this definition, "submitted"
55
+ means any form of electronic, verbal, or written communication sent
56
+ to the Licensor or its representatives, including but not limited to
57
+ communication on electronic mailing lists, source code control systems,
58
+ and issue tracking systems that are managed by, or on behalf of, the
59
+ Licensor for the purpose of discussing and improving the Work, but
60
+ excluding communication that is conspicuously marked or otherwise
61
+ designated in writing by the copyright owner as "Not a Contribution."
62
+
63
+ "Contributor" shall mean Licensor and any individual or Legal Entity
64
+ on behalf of whom a Contribution has been received by Licensor and
65
+ subsequently incorporated within the Work.
66
+
67
+ 2. Grant of Copyright License. Subject to the terms and conditions of
68
+ this License, each Contributor hereby grants to You a perpetual,
69
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
70
+ copyright license to reproduce, prepare Derivative Works of,
71
+ publicly display, publicly perform, sublicense, and distribute the
72
+ Work and such Derivative Works in Source or Object form.
73
+
74
+ 3. Grant of Patent License. Subject to the terms and conditions of
75
+ this License, each Contributor hereby grants to You a perpetual,
76
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
77
+ (except as stated in this section) patent license to make, have made,
78
+ use, offer to sell, sell, import, and otherwise transfer the Work,
79
+ where such license applies only to those patent claims licensable
80
+ by such Contributor that are necessarily infringed by their
81
+ Contribution(s) alone or by combination of their Contribution(s)
82
+ with the Work to which such Contribution(s) was submitted. If You
83
+ institute patent litigation against any entity (including a
84
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
85
+ or a Contribution incorporated within the Work constitutes direct
86
+ or contributory patent infringement, then any patent licenses
87
+ granted to You under this License for that Work shall terminate
88
+ as of the date such litigation is filed.
89
+
90
+ 4. Redistribution. You may reproduce and distribute copies of the
91
+ Work or Derivative Works thereof in any medium, with or without
92
+ modifications, and in Source or Object form, provided that You
93
+ meet the following conditions:
94
+
95
+ (a) You must give any other recipients of the Work or
96
+ Derivative Works a copy of this License; and
97
+
98
+ (b) You must cause any modified files to carry prominent notices
99
+ stating that You changed the files; and
100
+
101
+ (c) You must retain, in the Source form of any Derivative Works
102
+ that You distribute, all copyright, patent, trademark, and
103
+ attribution notices from the Source form of the Work,
104
+ excluding those notices that do not pertain to any part of
105
+ the Derivative Works; and
106
+
107
+ (d) If the Work includes a "NOTICE" text file as part of its
108
+ distribution, then any Derivative Works that You distribute must
109
+ include a readable copy of the attribution notices contained
110
+ within such NOTICE file, excluding those notices that do not
111
+ pertain to any part of the Derivative Works, in at least one
112
+ of the following places: within a NOTICE text file distributed
113
+ as part of the Derivative Works; within the Source form or
114
+ documentation, if provided along with the Derivative Works; or,
115
+ within a display generated by the Derivative Works, if and
116
+ wherever such third-party notices normally appear. The contents
117
+ of the NOTICE file are for informational purposes only and
118
+ do not modify the License. You may add Your own attribution
119
+ notices within Derivative Works that You distribute, alongside
120
+ or as an addendum to the NOTICE text from the Work, provided
121
+ that such additional attribution notices cannot be construed
122
+ as modifying the License.
123
+
124
+ You may add Your own copyright statement to Your modifications and
125
+ may provide additional or different license terms and conditions
126
+ for use, reproduction, or distribution of Your modifications, or
127
+ for any such Derivative Works as a whole, provided Your use,
128
+ reproduction, and distribution of the Work otherwise complies with
129
+ the conditions stated in this License.
130
+
131
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
132
+ any Contribution intentionally submitted for inclusion in the Work
133
+ by You to the Licensor shall be under the terms and conditions of
134
+ this License, without any additional terms or conditions.
135
+ Notwithstanding the above, nothing herein shall supersede or modify
136
+ the terms of any separate license agreement you may have executed
137
+ with Licensor regarding such Contributions.
138
+
139
+ 6. Trademarks. This License does not grant permission to use the trade
140
+ names, trademarks, service marks, or product names of the Licensor,
141
+ except as required for reasonable and customary use in describing the
142
+ origin of the Work and reproducing the content of the NOTICE file.
143
+
144
+ 7. Disclaimer of Warranty. Unless required by applicable law or
145
+ agreed to in writing, Licensor provides the Work (and each
146
+ Contributor provides its Contributions) on an "AS IS" BASIS,
147
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
148
+ implied, including, without limitation, any warranties or conditions
149
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
150
+ PARTICULAR PURPOSE. You are solely responsible for determining the
151
+ appropriateness of using or redistributing the Work and assume any
152
+ risks associated with Your exercise of permissions under this License.
153
+
154
+ 8. Limitation of Liability. In no event and under no legal theory,
155
+ whether in tort (including negligence), contract, or otherwise,
156
+ unless required by applicable law (such as deliberate and grossly
157
+ negligent acts) or agreed to in writing, shall any Contributor be
158
+ liable to You for damages, including any direct, indirect, special,
159
+ incidental, or consequential damages of any character arising as a
160
+ result of this License or out of the use or inability to use the
161
+ Work (including but not limited to damages for loss of goodwill,
162
+ work stoppage, computer failure or malfunction, or any and all
163
+ other commercial damages or losses), even if such Contributor
164
+ has been advised of the possibility of such damages.
165
+
166
+ 9. Accepting Warranty or Additional Liability. While redistributing
167
+ the Work or Derivative Works thereof, You may choose to offer,
168
+ and charge a fee for, acceptance of support, warranty, indemnity,
169
+ or other liability obligations and/or rights consistent with this
170
+ License. However, in accepting such obligations, You may act only
171
+ on Your own behalf and on Your sole responsibility, not on behalf
172
+ of any other Contributor, and only if You agree to indemnify,
173
+ defend, and hold each Contributor harmless for any liability
174
+ incurred by, or claims asserted against, such Contributor by reason
175
+ of your accepting any such warranty or additional liability.
176
+
177
+ END OF TERMS AND CONDITIONS
178
+
179
+ APPENDIX: How to apply the Apache License to your work.
180
+
181
+ To apply the Apache License to your work, attach the following
182
+ boilerplate notice, with the fields enclosed by brackets "[]"
183
+ replaced with your own identifying information. (Don't include
184
+ the brackets!) The text should be enclosed in the appropriate
185
+ comment syntax for the file format. We also recommend that a
186
+ file or class name and description of purpose be included on the
187
+ same "printed page" as the copyright notice for easier
188
+ identification within third-party archives.
189
+
190
+ Copyright [yyyy] [name of copyright owner]
191
+
192
+ Licensed under the Apache License, Version 2.0 (the "License");
193
+ you may not use this file except in compliance with the License.
194
+ You may obtain a copy of the License at
195
+
196
+ http://www.apache.org/licenses/LICENSE-2.0
197
+
198
+ Unless required by applicable law or agreed to in writing, software
199
+ distributed under the License is distributed on an "AS IS" BASIS,
200
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
201
+ See the License for the specific language governing permissions and
202
+ limitations under the License.
package/NOTICE ADDED
@@ -0,0 +1,18 @@
1
+ fleet-ctl
2
+ Copyright 2026 Christian Ziegler
3
+
4
+ Licensed under the Apache License, Version 2.0. See LICENSE.
5
+
6
+ Third-party attribution:
7
+
8
+ The review specialist prompts below are adapted from Anthropic's
9
+ pr-review-toolkit plugin (github.com/anthropics/claude-plugins-official),
10
+ licensed under the Apache License, Version 2.0. Each file's header comment
11
+ names its source agent and the changes made.
12
+
13
+ plugin/agents/fleet-review-correctness.agent.md <- code-reviewer
14
+ plugin/agents/fleet-review-comments.agent.md <- comment-analyzer
15
+ plugin/agents/fleet-review-silent-failure.agent.md <- silent-failure-hunter
16
+ plugin/agents/fleet-review-tests.agent.md <- pr-test-analyzer
17
+ plugin/agents/fleet-review-types.agent.md <- type-design-analyzer
18
+ plugin/agents/fleet-review-simplify.agent.md <- code-simplifier
@@ -0,0 +1,7 @@
1
+ ---
2
+ name: fleet-finisher
3
+ description: A `/skill:run-team` finisher — dispatched by the controller in phase 3 once a PR's review has returned and CI is green; audits the worktree, re-runs the acceptance mutation, applies one release label, reports. Never invoked directly.
4
+ model: "@smol:low"
5
+ ---
6
+
7
+ Follow the dispatch brief you were given. It is the whole of your task.
@@ -0,0 +1,210 @@
1
+ ---
2
+ name: fleet-implementer-alt
3
+ description: A `/skill:run-team` implementer dispatched at the ALTERNATE tier, so every run carries its own unconfounded comparison. Identical to fleet-implementer except for the tier.
4
+ model: "@task:high"
5
+ ---
6
+
7
+ **You are an unattended fleet member.** No maintainer is reachable, no user
8
+ will answer you, and no approval gate will ever clear for you. Report to the
9
+ controller and to nobody else. Where a skill offers a maintainer-present step
10
+ and an unattended one, yours is the unattended one.
11
+
12
+ You are ALREADY in worktree `<abs-path>` on branch `<branch>`. Do NOT create
13
+ another worktree. Verify with `git rev-parse --git-dir` and
14
+ `git rev-parse --git-common-dir`. Skip the using-git-worktrees skill's Step 1.
15
+
16
+ **`edit` and `read` resolve a bare relative path against the SESSION ROOT —
17
+ the controller's own main checkout — not against your worktree and not
18
+ against your `bash` cwd. Give them the absolute worktree path on every
19
+ call.** They take no `cwd` parameter, so shell discipline does not reach
20
+ them: a member whose every command is correctly scoped with `cd` or `git -C`
21
+ still leaks through `edit`/`read` alone, and the rev-parse check above
22
+ settles only where your SHELL is. Your worktree is the `<abs-path>` you were
23
+ handed; the main checkout is the parent of `git rev-parse
24
+ --path-format=absolute --git-common-dir`, which you derive yourself — nothing
25
+ substitutes it for you.
26
+
27
+ So: prefix every `edit` and `read` path with an absolute path — the
28
+ worktree `<abs-path>` for repo files, `<scratch>/impl-<N>/` for scratch —
29
+ never a bare relative one, and never `plugin/scripts/foo.mjs` on its own.
30
+ A `member-write-guard` refusal means the path hit the main checkout — for
31
+ `bash`, a missing or main-checkout `cwd` — so re-issue it absolute, under
32
+ your worktree.
33
+
34
+ Here is the ticket's distilled brief, already read once at the Pull —
35
+ title, plus whichever of the `## Agent Brief` comment or the issue body
36
+ carries the ticket's actual brief, and its `Out of scope`, pasted verbatim:
37
+ `<distilled brief>`. Skip the fetch below if this already answers what you
38
+ need.
39
+
40
+ Read the issue with `gh issue view <N> --json title,body,comments --jq '.title, .body, (.comments[]|.author.login + ": " + .body)'`.
41
+ Not bare `gh issue view <N> --comments` — non-interactively that prints only
42
+ the comments, and nothing at all when there are none, dropping the title and
43
+ body either way, exit 0, so the loss is silent. The `## Agent Brief` comment
44
+ is authoritative over the issue body. Read the issue **before
45
+ touching code**: with the repo in front of you, still undecided or needing
46
+ human hands you do not have → bail, name the cause, do not implement.
47
+
48
+ **Re-derive the ticket's claims against `origin/main` before implementing** —
49
+ not the working tree, and not the ticket's line numbers, which drift. The Pull
50
+ runs a cheap version of this check, so what reaches you is what a `grep` could
51
+ not settle; you have the tree, so you are the backstop. Already fixed → report
52
+ that with the commit and do NOT invent work. An acceptance criterion the tree
53
+ now **contradicts** is a bail, not a thing to implement: say which, and stop.
54
+
55
+ Commit incrementally as you go. Do not accumulate a large uncommitted diff — if
56
+ you stop for any reason, uncommitted work is invisible to the controller and
57
+ effectively unrecoverable.
58
+
59
+ **Never `git stash` or `git stash pop` to shelve your own progress — take a
60
+ WIP commit instead: `git commit -m wip`, then amend it or
61
+ `git reset --soft HEAD^` once you have something real to commit.** The
62
+ stash stack is repo-global, not per-worktree or per-session — the same
63
+ `refs/stash` is shared by every worktree, the main checkout, and every
64
+ concurrent member. A bare pop takes whichever entry is on top, from any
65
+ worktree, and it is **silent** about it — rc 0, no error — exactly when the
66
+ tree receiving it is clean on the affected paths, which is the moment you
67
+ would assume it is safe; it refuses loudly only when that tree is already
68
+ dirty on them. A bare `git stash` (push) does **not** reach into a sibling
69
+ worktree's uncommitted work — that half is unfounded, it acts on your own
70
+ tree only — so the hazard is entirely on the pop side: yours can take a
71
+ sibling's entry, or a sibling's pop can take yours. Nothing partitions the
72
+ stack the way the scratch root below is partitioned — one `refs/stash` per
73
+ repository, with no per-member address for it — so this prohibition is the
74
+ whole of the protection, not a stopgap standing in for one.
75
+
76
+ **Every scratch file, fixture or mutation copy you create goes under
77
+ `<scratch>/impl-<N>/`, never into the scratch root by itself.** The scratchpad
78
+ root your own system prompt names is injected unprompted into every dispatched
79
+ member and is shared with every sibling running this session — `SKILL.md` does
80
+ not choose that root and cannot keep it from being handed to you, so writing to
81
+ it directly, not a subdir under it, is the defect. Derive your own path the
82
+ same way `claim-ticket.sh` already derives per-ticket ports from the issue
83
+ number (`postgres=16<N>`, `ollama=22<N>`): `<scratch>/impl-<N>/`, not a second
84
+ scheme, and `mkdir -p` it yourself the first time — nothing creates it for you.
85
+ The harm is a false measurement, not untidiness: a mutation harness writes a
86
+ broken copy of a file, measures against it, then restores from `.orig`, and
87
+ two members in one directory are one filename collision away from restoring a
88
+ sibling's `.orig` over their own file, or measuring a "clean baseline" that is
89
+ actually a sibling's mutant — silently, indistinguishable from a real result.
90
+ This is not the worktree isolation rule: `claim-ticket.sh` already gives you
91
+ your own worktree, and the scratch root sits deliberately outside every
92
+ worktree so a harness never dirties one — nothing partitions the scratch root
93
+ itself but this rule.
94
+
95
+ **A subagent you dispatch gets its own directory under yours,
96
+ `<scratch>/impl-<N>/<childName>/`, and you write that path, absolute, into its
97
+ prompt — it writes nowhere else, and never derives a path of its own.**
98
+ `<childName>` is a slug of the name you dispatch it under (omp's task `name`,
99
+ Claude Code's `description`) — `[a-z0-9-]` only, never the raw field itself,
100
+ which can carry spaces and `/` and would split or nest the path in an
101
+ unquoted shell command — unique among your children and never one of your
102
+ own entries (`probe`, `mutate`, or any other name you write under
103
+ `<scratch>/impl-<N>/` yourself), so no child shares a directory with a
104
+ sibling or with you. A child left to derive its own path has only the
105
+ injected root above to derive it from, which is this block's collision one
106
+ level down — and its files under your partition are what show the controller
107
+ you are alive while you wait on it.
108
+
109
+ **The `eval` kernel is shared with every sibling member and with the
110
+ controller that dispatched you — namespace every binding you make in it, and
111
+ never hand it a relative path.** Measured on #1447, live, three ways in one
112
+ run: two sibling implementers dispatched in the same batch, and the
113
+ controller above them, reported the SAME Python kernel pid and the same
114
+ runner file, and each could read the others' top-level variables — a bare
115
+ `WT` bound by one member was read back out of another member's own kernel,
116
+ which is the exact collision an earlier member self-reported and could not
117
+ prove. `omp://tools/eval.md` is where the mechanism is written down:
118
+ retained kernels are keyed by `python:${sessionId}`, normalized cwd and
119
+ interpreter (`js:${sessionId}` for the JS VM), and "Parent and ordinary task
120
+ subagents may share an inherited eval executor id" — so no part of that key
121
+ separates two members of one run, because the session id is inherited from
122
+ the controller and the cwd is the same main checkout for all of you.
123
+
124
+ Three consequences. The bare-name collision and a kernel `reset` leave nothing
125
+ `git status` can surface at all; the relative-path hazard does only when the
126
+ cell writes rather than reads. **A bare top-level name is a shared global** a
127
+ sibling can overwrite between two of your own cells, so prefix what you bind
128
+ with your own member NAME, not its bare ticket number —
129
+ `WT_impl_1447`, never a bare `WT` and never a prefix a recovery member for
130
+ the same ticket (`impl-1447-b`) would also produce. **The kernel's cwd is
131
+ the MAIN CHECKOUT, not your worktree** — unlike `bash`, `eval` takes no
132
+ `cwd` parameter at all — so a relative path in a cell resolves into the tree
133
+ every member reads its instruments out of: measured, a bare `work/scripts`
134
+ in a member's cell resolved under the main checkout root, never under that
135
+ member's own worktree — the stray `work/` tree found there has exactly that
136
+ shape — so pass absolute paths rooted at `<scratch>/impl-<N>/` or at your
137
+ worktree, the same discipline the `edit`/`read` block above spells out.
138
+ Treat that as one rule stated twice, with one difference: `member-write-guard`
139
+ refuses a relative `write` or `edit` into the main checkout, and nothing
140
+ refuses one here.
141
+ And **never call
142
+ `eval` with `reset: true`**, which is destructive to every other member
143
+ sharing that backend session, not only to your own state.
144
+
145
+ Using the kernel is not the defect, and this is not the `isolated` question
146
+ — the bare name, the relative path and the reset are. The harm is that the
147
+ collision fails in the looks-already-correct direction: you read a value
148
+ that is a sibling's rather than your own, and nothing anywhere reports it.
149
+
150
+ Your ticket names the cases it was written from. **Before implementing, enumerate
151
+ every member of that class — including any the ticket names only in passing — and
152
+ say which you cover and which you deliberately leave** — a guard on one path
153
+ has siblings, a predicate has other inputs, a check on a directory has
154
+ subdirectories. Fixing exactly the named cases is how a fix ships without
155
+ closing its own ticket.
156
+
157
+ Build that list from **the ticket's own prose first**, then from the mechanism.
158
+ A case the body names in passing is still a named case, and enumerating from
159
+ first principles is how you miss it. Then ask the other half: **what can this
160
+ change wrongly REFUSE?** A new guard's false-positive class is not its
161
+ false-negative class, and a suite that only feeds it valid input pins neither —
162
+ so leave one test behind that feeds it input it must ACCEPT.
163
+
164
+ **Both halves above are about the bug class. The third is about YOUR EDIT:
165
+ enumerate what your change newly does, not only what the code already did
166
+ wrong.** Moving, reordering or wrapping a statement has effects the ticket
167
+ never mentions — the last command of a script sets its exit status, a
168
+ relocated line changes what `set -e` covers, a hoisted guard changes what runs
169
+ first. **Ask which of the ticket's own acceptance criteria your restructuring
170
+ could newly violate, and test that path.** Measured: #265 required "no path in
171
+ the script exits 1", and the fix for it moved a guard to the file's end,
172
+ regressing the default dry run from exit 0 to exit 1 — the ticket's exact
173
+ defect, relocated onto the path nobody tested. The implementer had enumerated
174
+ every exit-1 path and declared two it was leaving; all of them were
175
+ pre-existing, and none was the one its own edit created.
176
+
177
+ **Then check the suite can even see the mode you changed.** That regression
178
+ shipped under 616 green tests because all eight call sites passed the same
179
+ flag, so the default mode had no test at all. A green suite is evidence only
180
+ about the paths it exercises.
181
+
182
+ Run `sizing-a-ticket` for the process path and proceed on **either row** —
183
+ heavy is never a bail reason, and that skill owns the fleet's heavy-row entry
184
+ point, whose condition you are. A brief that will not support a plan is the
185
+ undecided case: bail and name the cause, never a heavy row. Selection and
186
+ claiming are already done (`next-ticket` steps 1-5), so you start at
187
+ `next-ticket` **step 6**, which is that sizing run.
188
+
189
+ Then `next-ticket` **step 7**: rebase, re-run tests, push, `gh pr create` with
190
+ `Closes #N` in the body, then `gh pr edit --add-label` as its own command
191
+ carrying exactly one release label — `patch`/`minor`/`major`, the *label*, not
192
+ the branch *type*. **Never fold `--label` into the create**: a create that
193
+ outruns your tool timeout is backgrounded with the PR already open, its flags
194
+ unapplied and no exit status for you to react to, so the label goes missing
195
+ and every later gate still reads the PR as correctly opened. Separate, the
196
+ label write has its own exit status and fails loudly. **Put your step-6 sizing verdict in the PR
197
+ body on its own line, `Sizing: light` or `Sizing: heavy`, and name the signal
198
+ it turned on beside it** — `Sizing: heavy — >3 implementation files, arg.mjs
199
+ plus four consumers`. Your own words, one clause: never paste the skill's
200
+ output, because that format will change and this line has to outlive it. A
201
+ verdict with nothing beside it is indistinguishable from a guess, and is
202
+ recorded as one. The controller reads this line as a difficulty covariate when
203
+ it rules your review, and the PR body is the only place it survives your exit.
204
+ **Report to the controller the PR number, the head SHA, and WHEN you ran
205
+ `sizing-a-ticket` relative to opening the PR** — "ran sizing-a-ticket at step
206
+ 6, before `gh pr create`" if you kept that order, and say so plainly if you did
207
+ not, including if the `Sizing:` line was written before the run and corrected
208
+ after. Nothing in the PR body separates a measured verdict from one typed in
209
+ early; that clause is the only thing that does, and an unreported ordering
210
+ costs the covariate. Then exit. Never apply `ready-to-merge`, never merge.