@apralabs/apra-fleet 0.3.5 → 0.4.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 (571) hide show
  1. package/README.md +245 -257
  2. package/dist/agents/backlog-groomer.md +287 -0
  3. package/dist/agents/deployer.md +52 -11
  4. package/dist/agents/doer.md +32 -7
  5. package/dist/agents/integ-test-runner.md +151 -61
  6. package/dist/agents/plan-reviewer.md +74 -17
  7. package/dist/agents/planner.md +94 -14
  8. package/dist/agents/regression-test-runner.md +216 -0
  9. package/dist/agents/reviewer.md +21 -6
  10. package/dist/agents/schemas/backlog-groomer-input.json +35 -0
  11. package/dist/agents/schemas/backlog-groomer-output.json +164 -0
  12. package/dist/agents/schemas/integ-test-runner-output.json +34 -0
  13. package/dist/agents/schemas/regression-test-runner-input.json +15 -0
  14. package/dist/agents/schemas/regression-test-runner-output.json +50 -0
  15. package/dist/agents/schemas/reviewer-output.json +4 -0
  16. package/dist/cli/agent-transform.d.ts +1 -0
  17. package/dist/cli/agent-transform.d.ts.map +1 -1
  18. package/dist/cli/agent-transform.js +77 -0
  19. package/dist/cli/agent-transform.js.map +1 -1
  20. package/dist/cli/auth.d.ts +3 -0
  21. package/dist/cli/auth.d.ts.map +1 -1
  22. package/dist/cli/auth.js +181 -5
  23. package/dist/cli/auth.js.map +1 -1
  24. package/dist/cli/config.d.ts +5 -1
  25. package/dist/cli/config.d.ts.map +1 -1
  26. package/dist/cli/config.js +7 -1
  27. package/dist/cli/config.js.map +1 -1
  28. package/dist/cli/dolt-install.d.ts +91 -0
  29. package/dist/cli/dolt-install.d.ts.map +1 -0
  30. package/dist/cli/dolt-install.js +334 -0
  31. package/dist/cli/dolt-install.js.map +1 -0
  32. package/dist/cli/install-guard.d.ts +29 -0
  33. package/dist/cli/install-guard.d.ts.map +1 -0
  34. package/dist/cli/install-guard.js +153 -0
  35. package/dist/cli/install-guard.js.map +1 -0
  36. package/dist/cli/install.d.ts +44 -3
  37. package/dist/cli/install.d.ts.map +1 -1
  38. package/dist/cli/install.js +604 -108
  39. package/dist/cli/install.js.map +1 -1
  40. package/dist/cli/join.d.ts +12 -0
  41. package/dist/cli/join.d.ts.map +1 -0
  42. package/dist/cli/join.js +87 -0
  43. package/dist/cli/join.js.map +1 -0
  44. package/dist/cli/register-member.d.ts +2 -0
  45. package/dist/cli/register-member.d.ts.map +1 -0
  46. package/dist/cli/register-member.js +193 -0
  47. package/dist/cli/register-member.js.map +1 -0
  48. package/dist/cli/restart.d.ts +2 -0
  49. package/dist/cli/restart.d.ts.map +1 -0
  50. package/dist/cli/restart.js +7 -0
  51. package/dist/cli/restart.js.map +1 -0
  52. package/dist/cli/secret.js +8 -2
  53. package/dist/cli/secret.js.map +1 -1
  54. package/dist/cli/spoke.d.ts +35 -0
  55. package/dist/cli/spoke.d.ts.map +1 -0
  56. package/dist/cli/spoke.js +212 -0
  57. package/dist/cli/spoke.js.map +1 -0
  58. package/dist/cli/start.d.ts +2 -0
  59. package/dist/cli/start.d.ts.map +1 -0
  60. package/dist/cli/start.js +92 -0
  61. package/dist/cli/start.js.map +1 -0
  62. package/dist/cli/status.d.ts +2 -0
  63. package/dist/cli/status.d.ts.map +1 -0
  64. package/dist/cli/status.js +83 -0
  65. package/dist/cli/status.js.map +1 -0
  66. package/dist/cli/stop.d.ts +2 -0
  67. package/dist/cli/stop.d.ts.map +1 -0
  68. package/dist/cli/stop.js +51 -0
  69. package/dist/cli/stop.js.map +1 -0
  70. package/dist/cli/uninstall.d.ts.map +1 -1
  71. package/dist/cli/uninstall.js +109 -9
  72. package/dist/cli/uninstall.js.map +1 -1
  73. package/dist/cli/update.d.ts.map +1 -1
  74. package/dist/cli/update.js +10 -1
  75. package/dist/cli/update.js.map +1 -1
  76. package/dist/cli/workflow-assets.d.ts +37 -0
  77. package/dist/cli/workflow-assets.d.ts.map +1 -0
  78. package/dist/cli/workflow-assets.js +144 -0
  79. package/dist/cli/workflow-assets.js.map +1 -0
  80. package/dist/cli/workflow.d.ts +75 -0
  81. package/dist/cli/workflow.d.ts.map +1 -0
  82. package/dist/cli/workflow.js +397 -0
  83. package/dist/cli/workflow.js.map +1 -0
  84. package/dist/hub-service/activity.d.ts +30 -0
  85. package/dist/hub-service/activity.d.ts.map +1 -0
  86. package/dist/hub-service/activity.js +20 -0
  87. package/dist/hub-service/activity.js.map +1 -0
  88. package/dist/hub-service/audit-log.d.ts +19 -0
  89. package/dist/hub-service/audit-log.d.ts.map +1 -0
  90. package/dist/hub-service/audit-log.js +13 -0
  91. package/dist/hub-service/audit-log.js.map +1 -0
  92. package/dist/hub-service/db/pool.d.ts +19 -0
  93. package/dist/hub-service/db/pool.d.ts.map +1 -0
  94. package/dist/hub-service/db/pool.js +53 -0
  95. package/dist/hub-service/db/pool.js.map +1 -0
  96. package/dist/hub-service/enrollment.d.ts +29 -0
  97. package/dist/hub-service/enrollment.d.ts.map +1 -0
  98. package/dist/hub-service/enrollment.js +48 -0
  99. package/dist/hub-service/enrollment.js.map +1 -0
  100. package/dist/hub-service/envelope-routes.d.ts +46 -0
  101. package/dist/hub-service/envelope-routes.d.ts.map +1 -0
  102. package/dist/hub-service/envelope-routes.js +94 -0
  103. package/dist/hub-service/envelope-routes.js.map +1 -0
  104. package/dist/hub-service/handlers/installers.d.ts +14 -0
  105. package/dist/hub-service/handlers/installers.d.ts.map +1 -0
  106. package/dist/hub-service/handlers/installers.js +8 -0
  107. package/dist/hub-service/handlers/installers.js.map +1 -0
  108. package/dist/hub-service/http-server.d.ts +31 -0
  109. package/dist/hub-service/http-server.d.ts.map +1 -0
  110. package/dist/hub-service/http-server.js +711 -0
  111. package/dist/hub-service/http-server.js.map +1 -0
  112. package/dist/hub-service/hub-jwt.d.ts +30 -0
  113. package/dist/hub-service/hub-jwt.d.ts.map +1 -0
  114. package/dist/hub-service/hub-jwt.js +105 -0
  115. package/dist/hub-service/hub-jwt.js.map +1 -0
  116. package/dist/hub-service/jwt-revocation.d.ts +20 -0
  117. package/dist/hub-service/jwt-revocation.d.ts.map +1 -0
  118. package/dist/hub-service/jwt-revocation.js +18 -0
  119. package/dist/hub-service/jwt-revocation.js.map +1 -0
  120. package/dist/hub-service/machines.d.ts +16 -0
  121. package/dist/hub-service/machines.d.ts.map +1 -0
  122. package/dist/hub-service/machines.js +14 -0
  123. package/dist/hub-service/machines.js.map +1 -0
  124. package/dist/hub-service/main.d.ts +3 -0
  125. package/dist/hub-service/main.d.ts.map +1 -0
  126. package/dist/hub-service/main.js +64 -0
  127. package/dist/hub-service/main.js.map +1 -0
  128. package/dist/hub-service/member-tokens.d.ts +11 -0
  129. package/dist/hub-service/member-tokens.d.ts.map +1 -0
  130. package/dist/hub-service/member-tokens.js +49 -0
  131. package/dist/hub-service/member-tokens.js.map +1 -0
  132. package/dist/hub-service/member-view.d.ts +20 -0
  133. package/dist/hub-service/member-view.d.ts.map +1 -0
  134. package/dist/hub-service/member-view.js +76 -0
  135. package/dist/hub-service/member-view.js.map +1 -0
  136. package/dist/hub-service/members.d.ts +44 -0
  137. package/dist/hub-service/members.d.ts.map +1 -0
  138. package/dist/hub-service/members.js +25 -0
  139. package/dist/hub-service/members.js.map +1 -0
  140. package/dist/hub-service/presence.d.ts +40 -0
  141. package/dist/hub-service/presence.d.ts.map +1 -0
  142. package/dist/hub-service/presence.js +44 -0
  143. package/dist/hub-service/presence.js.map +1 -0
  144. package/dist/hub-service/project-view.d.ts +12 -0
  145. package/dist/hub-service/project-view.d.ts.map +1 -0
  146. package/dist/hub-service/project-view.js +34 -0
  147. package/dist/hub-service/project-view.js.map +1 -0
  148. package/dist/hub-service/projects.d.ts +48 -0
  149. package/dist/hub-service/projects.d.ts.map +1 -0
  150. package/dist/hub-service/projects.js +80 -0
  151. package/dist/hub-service/projects.js.map +1 -0
  152. package/dist/hub-service/relay-queue.d.ts +115 -0
  153. package/dist/hub-service/relay-queue.d.ts.map +1 -0
  154. package/dist/hub-service/relay-queue.js +148 -0
  155. package/dist/hub-service/relay-queue.js.map +1 -0
  156. package/dist/hub-service/session-jwt.d.ts +10 -0
  157. package/dist/hub-service/session-jwt.d.ts.map +1 -0
  158. package/dist/hub-service/session-jwt.js +69 -0
  159. package/dist/hub-service/session-jwt.js.map +1 -0
  160. package/dist/hub-service/usage.d.ts +40 -0
  161. package/dist/hub-service/usage.d.ts.map +1 -0
  162. package/dist/hub-service/usage.js +25 -0
  163. package/dist/hub-service/usage.js.map +1 -0
  164. package/dist/hub-service/users.d.ts +56 -0
  165. package/dist/hub-service/users.d.ts.map +1 -0
  166. package/dist/hub-service/users.js +72 -0
  167. package/dist/hub-service/users.js.map +1 -0
  168. package/dist/hub-service/workspaces.d.ts +20 -0
  169. package/dist/hub-service/workspaces.d.ts.map +1 -0
  170. package/dist/hub-service/workspaces.js +10 -0
  171. package/dist/hub-service/workspaces.js.map +1 -0
  172. package/dist/index.js +179 -132
  173. package/dist/index.js.map +1 -1
  174. package/dist/os/linux.d.ts +13 -0
  175. package/dist/os/linux.d.ts.map +1 -1
  176. package/dist/os/linux.js +62 -3
  177. package/dist/os/linux.js.map +1 -1
  178. package/dist/os/os-commands.d.ts +10 -0
  179. package/dist/os/os-commands.d.ts.map +1 -1
  180. package/dist/os/windows.d.ts +1 -0
  181. package/dist/os/windows.d.ts.map +1 -1
  182. package/dist/os/windows.js +21 -1
  183. package/dist/os/windows.js.map +1 -1
  184. package/dist/paths.d.ts +23 -0
  185. package/dist/paths.d.ts.map +1 -1
  186. package/dist/paths.js +29 -0
  187. package/dist/paths.js.map +1 -1
  188. package/dist/providers/agy.d.ts +9 -2
  189. package/dist/providers/agy.d.ts.map +1 -1
  190. package/dist/providers/agy.js +127 -14
  191. package/dist/providers/agy.js.map +1 -1
  192. package/dist/providers/claude.d.ts +6 -2
  193. package/dist/providers/claude.d.ts.map +1 -1
  194. package/dist/providers/claude.js +248 -9
  195. package/dist/providers/claude.js.map +1 -1
  196. package/dist/providers/codex.d.ts +3 -2
  197. package/dist/providers/codex.d.ts.map +1 -1
  198. package/dist/providers/codex.js +7 -0
  199. package/dist/providers/codex.js.map +1 -1
  200. package/dist/providers/copilot.d.ts +3 -2
  201. package/dist/providers/copilot.d.ts.map +1 -1
  202. package/dist/providers/copilot.js +8 -1
  203. package/dist/providers/copilot.js.map +1 -1
  204. package/dist/providers/gemini.d.ts +3 -2
  205. package/dist/providers/gemini.d.ts.map +1 -1
  206. package/dist/providers/gemini.js +11 -1
  207. package/dist/providers/gemini.js.map +1 -1
  208. package/dist/providers/index.d.ts +1 -0
  209. package/dist/providers/index.d.ts.map +1 -1
  210. package/dist/providers/index.js +3 -0
  211. package/dist/providers/index.js.map +1 -1
  212. package/dist/providers/none.d.ts +51 -0
  213. package/dist/providers/none.d.ts.map +1 -0
  214. package/dist/providers/none.js +103 -0
  215. package/dist/providers/none.js.map +1 -0
  216. package/dist/providers/opencode.d.ts +4 -2
  217. package/dist/providers/opencode.d.ts.map +1 -1
  218. package/dist/providers/opencode.js +49 -0
  219. package/dist/providers/opencode.js.map +1 -1
  220. package/dist/providers/provider.d.ts +79 -1
  221. package/dist/providers/provider.d.ts.map +1 -1
  222. package/dist/providers/provider.js +10 -0
  223. package/dist/providers/provider.js.map +1 -1
  224. package/dist/services/agent-provisioner.d.ts +3 -3
  225. package/dist/services/agent-provisioner.d.ts.map +1 -1
  226. package/dist/services/agent-provisioner.js +12 -5
  227. package/dist/services/agent-provisioner.js.map +1 -1
  228. package/dist/services/auth-socket.d.ts.map +1 -1
  229. package/dist/services/auth-socket.js +2 -0
  230. package/dist/services/auth-socket.js.map +1 -1
  231. package/dist/services/budget-awareness.d.ts +130 -0
  232. package/dist/services/budget-awareness.d.ts.map +1 -0
  233. package/dist/services/budget-awareness.js +129 -0
  234. package/dist/services/budget-awareness.js.map +1 -0
  235. package/dist/services/cloud-sync.d.ts +35 -0
  236. package/dist/services/cloud-sync.d.ts.map +1 -0
  237. package/dist/services/cloud-sync.js +90 -0
  238. package/dist/services/cloud-sync.js.map +1 -0
  239. package/dist/services/context-admission.d.ts +82 -0
  240. package/dist/services/context-admission.d.ts.map +1 -0
  241. package/dist/services/context-admission.js +136 -0
  242. package/dist/services/context-admission.js.map +1 -0
  243. package/dist/services/event-bus.d.ts +27 -0
  244. package/dist/services/event-bus.d.ts.map +1 -0
  245. package/dist/services/event-bus.js +20 -0
  246. package/dist/services/event-bus.js.map +1 -0
  247. package/dist/services/file-chunker.d.ts +38 -0
  248. package/dist/services/file-chunker.d.ts.map +1 -0
  249. package/dist/services/file-chunker.js +63 -0
  250. package/dist/services/file-chunker.js.map +1 -0
  251. package/dist/services/file-transfer-relay.d.ts +55 -0
  252. package/dist/services/file-transfer-relay.d.ts.map +1 -0
  253. package/dist/services/file-transfer-relay.js +115 -0
  254. package/dist/services/file-transfer-relay.js.map +1 -0
  255. package/dist/services/github-app.d.ts.map +1 -1
  256. package/dist/services/github-app.js +1 -0
  257. package/dist/services/github-app.js.map +1 -1
  258. package/dist/services/http-transport.d.ts +25 -0
  259. package/dist/services/http-transport.d.ts.map +1 -0
  260. package/dist/services/http-transport.js +371 -0
  261. package/dist/services/http-transport.js.map +1 -0
  262. package/dist/services/hub-client.d.ts +69 -0
  263. package/dist/services/hub-client.d.ts.map +1 -0
  264. package/dist/services/hub-client.js +217 -0
  265. package/dist/services/hub-client.js.map +1 -0
  266. package/dist/services/jwt.d.ts +17 -0
  267. package/dist/services/jwt.d.ts.map +1 -0
  268. package/dist/services/jwt.js +70 -0
  269. package/dist/services/jwt.js.map +1 -0
  270. package/dist/services/known-sessions.d.ts +8 -0
  271. package/dist/services/known-sessions.d.ts.map +1 -0
  272. package/dist/services/known-sessions.js +40 -0
  273. package/dist/services/known-sessions.js.map +1 -0
  274. package/dist/services/model-pricing.d.ts +36 -0
  275. package/dist/services/model-pricing.d.ts.map +1 -0
  276. package/dist/services/model-pricing.js +108 -0
  277. package/dist/services/model-pricing.js.map +1 -0
  278. package/dist/services/orphan-recovery.d.ts +56 -0
  279. package/dist/services/orphan-recovery.d.ts.map +1 -0
  280. package/dist/services/orphan-recovery.js +111 -0
  281. package/dist/services/orphan-recovery.js.map +1 -0
  282. package/dist/services/pending-responses.d.ts +23 -0
  283. package/dist/services/pending-responses.d.ts.map +1 -0
  284. package/dist/services/pending-responses.js +52 -0
  285. package/dist/services/pending-responses.js.map +1 -0
  286. package/dist/services/registry.d.ts +4 -1
  287. package/dist/services/registry.d.ts.map +1 -1
  288. package/dist/services/registry.js +3 -0
  289. package/dist/services/registry.js.map +1 -1
  290. package/dist/services/relay-context.d.ts +23 -0
  291. package/dist/services/relay-context.d.ts.map +1 -0
  292. package/dist/services/relay-context.js +8 -0
  293. package/dist/services/relay-context.js.map +1 -0
  294. package/dist/services/relay-executor.d.ts +68 -0
  295. package/dist/services/relay-executor.d.ts.map +1 -0
  296. package/dist/services/relay-executor.js +70 -0
  297. package/dist/services/relay-executor.js.map +1 -0
  298. package/dist/services/relay-request.d.ts +65 -0
  299. package/dist/services/relay-request.d.ts.map +1 -0
  300. package/dist/services/relay-request.js +129 -0
  301. package/dist/services/relay-request.js.map +1 -0
  302. package/dist/services/relay-strategy.d.ts +19 -0
  303. package/dist/services/relay-strategy.d.ts.map +1 -0
  304. package/dist/services/relay-strategy.js +111 -0
  305. package/dist/services/relay-strategy.js.map +1 -0
  306. package/dist/services/service-manager/index.d.ts +5 -0
  307. package/dist/services/service-manager/index.d.ts.map +1 -0
  308. package/dist/services/service-manager/index.js +66 -0
  309. package/dist/services/service-manager/index.js.map +1 -0
  310. package/dist/services/service-manager/linux.d.ts +10 -0
  311. package/dist/services/service-manager/linux.d.ts.map +1 -0
  312. package/dist/services/service-manager/linux.js +97 -0
  313. package/dist/services/service-manager/linux.js.map +1 -0
  314. package/dist/services/service-manager/macos.d.ts +10 -0
  315. package/dist/services/service-manager/macos.d.ts.map +1 -0
  316. package/dist/services/service-manager/macos.js +94 -0
  317. package/dist/services/service-manager/macos.js.map +1 -0
  318. package/dist/services/service-manager/types.d.ts +18 -0
  319. package/dist/services/service-manager/types.d.ts.map +1 -0
  320. package/dist/services/service-manager/types.js +5 -0
  321. package/dist/services/service-manager/types.js.map +1 -0
  322. package/dist/services/service-manager/windows.d.ts +10 -0
  323. package/dist/services/service-manager/windows.d.ts.map +1 -0
  324. package/dist/services/service-manager/windows.js +73 -0
  325. package/dist/services/service-manager/windows.js.map +1 -0
  326. package/dist/services/session-registry.d.ts +70 -0
  327. package/dist/services/session-registry.d.ts.map +1 -0
  328. package/dist/services/session-registry.js +91 -0
  329. package/dist/services/session-registry.js.map +1 -0
  330. package/dist/services/singleton.d.ts +15 -0
  331. package/dist/services/singleton.d.ts.map +1 -0
  332. package/dist/services/singleton.js +98 -0
  333. package/dist/services/singleton.js.map +1 -0
  334. package/dist/services/sprint-coordination.d.ts +168 -0
  335. package/dist/services/sprint-coordination.d.ts.map +1 -0
  336. package/dist/services/sprint-coordination.js +564 -0
  337. package/dist/services/sprint-coordination.js.map +1 -0
  338. package/dist/services/ssh.d.ts.map +1 -1
  339. package/dist/services/ssh.js +70 -3
  340. package/dist/services/ssh.js.map +1 -1
  341. package/dist/services/stall/log-path-resolver.d.ts.map +1 -1
  342. package/dist/services/stall/log-path-resolver.js +8 -1
  343. package/dist/services/stall/log-path-resolver.js.map +1 -1
  344. package/dist/services/stall/stall-detector.d.ts.map +1 -1
  345. package/dist/services/stall/stall-detector.js +39 -7
  346. package/dist/services/stall/stall-detector.js.map +1 -1
  347. package/dist/services/stall/stall-poller.d.ts +16 -0
  348. package/dist/services/stall/stall-poller.d.ts.map +1 -1
  349. package/dist/services/stall/stall-poller.js +136 -18
  350. package/dist/services/stall/stall-poller.js.map +1 -1
  351. package/dist/services/strategy.d.ts.map +1 -1
  352. package/dist/services/strategy.js +55 -5
  353. package/dist/services/strategy.js.map +1 -1
  354. package/dist/services/substitution-engine.d.ts +20 -0
  355. package/dist/services/substitution-engine.d.ts.map +1 -0
  356. package/dist/services/substitution-engine.js +92 -0
  357. package/dist/services/substitution-engine.js.map +1 -0
  358. package/dist/services/task-cleanup.d.ts.map +1 -1
  359. package/dist/services/task-cleanup.js +1 -9
  360. package/dist/services/task-cleanup.js.map +1 -1
  361. package/dist/services/token-issuer.d.ts +47 -0
  362. package/dist/services/token-issuer.d.ts.map +1 -0
  363. package/dist/services/token-issuer.js +63 -0
  364. package/dist/services/token-issuer.js.map +1 -0
  365. package/dist/services/tool-registry.d.ts +3 -0
  366. package/dist/services/tool-registry.d.ts.map +1 -0
  367. package/dist/services/tool-registry.js +139 -0
  368. package/dist/services/tool-registry.js.map +1 -0
  369. package/dist/services/user-config.d.ts +14 -0
  370. package/dist/services/user-config.d.ts.map +1 -1
  371. package/dist/services/user-config.js +55 -0
  372. package/dist/services/user-config.js.map +1 -1
  373. package/dist/services/vcs/types.d.ts +44 -0
  374. package/dist/services/vcs/types.d.ts.map +1 -1
  375. package/dist/skills/fleet-sprint-cli/SKILL.md +103 -0
  376. package/dist/skills/pm/cost.md +3 -0
  377. package/dist/skills/pm/doer-reviewer-loop.md +3 -0
  378. package/dist/tools/check-status.d.ts.map +1 -1
  379. package/dist/tools/check-status.js +8 -2
  380. package/dist/tools/check-status.js.map +1 -1
  381. package/dist/tools/child-id-allocator.d.ts +45 -0
  382. package/dist/tools/child-id-allocator.d.ts.map +1 -0
  383. package/dist/tools/child-id-allocator.js +62 -0
  384. package/dist/tools/child-id-allocator.js.map +1 -0
  385. package/dist/tools/cloud-control.d.ts +2 -2
  386. package/dist/tools/compose-permissions.d.ts +12 -4
  387. package/dist/tools/compose-permissions.d.ts.map +1 -1
  388. package/dist/tools/compose-permissions.js +55 -4
  389. package/dist/tools/compose-permissions.js.map +1 -1
  390. package/dist/tools/dolt-push-mutex.d.ts +44 -0
  391. package/dist/tools/dolt-push-mutex.d.ts.map +1 -0
  392. package/dist/tools/dolt-push-mutex.js +83 -0
  393. package/dist/tools/dolt-push-mutex.js.map +1 -0
  394. package/dist/tools/execute-command.d.ts +11 -1
  395. package/dist/tools/execute-command.d.ts.map +1 -1
  396. package/dist/tools/execute-command.js +22 -5
  397. package/dist/tools/execute-command.js.map +1 -1
  398. package/dist/tools/execute-prompt.d.ts +72 -12
  399. package/dist/tools/execute-prompt.d.ts.map +1 -1
  400. package/dist/tools/execute-prompt.js +962 -71
  401. package/dist/tools/execute-prompt.js.map +1 -1
  402. package/dist/tools/get-member-model-pricing.d.ts +21 -0
  403. package/dist/tools/get-member-model-pricing.d.ts.map +1 -0
  404. package/dist/tools/get-member-model-pricing.js +29 -0
  405. package/dist/tools/get-member-model-pricing.js.map +1 -0
  406. package/dist/tools/list-members.d.ts.map +1 -1
  407. package/dist/tools/list-members.js +39 -7
  408. package/dist/tools/list-members.js.map +1 -1
  409. package/dist/tools/member-detail.d.ts +1 -1
  410. package/dist/tools/member-detail.d.ts.map +1 -1
  411. package/dist/tools/member-detail.js +8 -2
  412. package/dist/tools/member-detail.js.map +1 -1
  413. package/dist/tools/member-reservation.d.ts +29 -0
  414. package/dist/tools/member-reservation.d.ts.map +1 -0
  415. package/dist/tools/member-reservation.js +71 -0
  416. package/dist/tools/member-reservation.js.map +1 -0
  417. package/dist/tools/provision-vcs-auth.d.ts +7 -7
  418. package/dist/tools/provision-vcs-auth.js +1 -1
  419. package/dist/tools/provision-vcs-auth.js.map +1 -1
  420. package/dist/tools/register-member.d.ts +17 -5
  421. package/dist/tools/register-member.d.ts.map +1 -1
  422. package/dist/tools/register-member.js +144 -5
  423. package/dist/tools/register-member.js.map +1 -1
  424. package/dist/tools/remove-member.d.ts +1 -1
  425. package/dist/tools/report-status.d.ts +33 -0
  426. package/dist/tools/report-status.d.ts.map +1 -0
  427. package/dist/tools/report-status.js +44 -0
  428. package/dist/tools/report-status.js.map +1 -0
  429. package/dist/tools/respond-to-message.d.ts +21 -0
  430. package/dist/tools/respond-to-message.d.ts.map +1 -0
  431. package/dist/tools/respond-to-message.js +23 -0
  432. package/dist/tools/respond-to-message.js.map +1 -0
  433. package/dist/tools/send-files.d.ts +3 -0
  434. package/dist/tools/send-files.d.ts.map +1 -1
  435. package/dist/tools/send-files.js +88 -8
  436. package/dist/tools/send-files.js.map +1 -1
  437. package/dist/tools/send-message.d.ts +27 -0
  438. package/dist/tools/send-message.d.ts.map +1 -0
  439. package/dist/tools/send-message.js +46 -0
  440. package/dist/tools/send-message.js.map +1 -0
  441. package/dist/tools/shutdown-server.d.ts +2 -0
  442. package/dist/tools/shutdown-server.d.ts.map +1 -1
  443. package/dist/tools/shutdown-server.js +19 -0
  444. package/dist/tools/shutdown-server.js.map +1 -1
  445. package/dist/tools/update-member.d.ts +8 -8
  446. package/dist/tools/update-member.d.ts.map +1 -1
  447. package/dist/tools/update-member.js +11 -1
  448. package/dist/tools/update-member.js.map +1 -1
  449. package/dist/types.d.ts +15 -3
  450. package/dist/types.d.ts.map +1 -1
  451. package/dist/utils/agent-helpers.d.ts +2 -1
  452. package/dist/utils/agent-helpers.d.ts.map +1 -1
  453. package/dist/utils/agent-helpers.js +7 -2
  454. package/dist/utils/agent-helpers.js.map +1 -1
  455. package/dist/utils/pid-helpers.d.ts +15 -0
  456. package/dist/utils/pid-helpers.d.ts.map +1 -1
  457. package/dist/utils/pid-helpers.js +23 -0
  458. package/dist/utils/pid-helpers.js.map +1 -1
  459. package/dist/utils/process-utils.d.ts +3 -0
  460. package/dist/utils/process-utils.d.ts.map +1 -0
  461. package/dist/utils/process-utils.js +42 -0
  462. package/dist/utils/process-utils.js.map +1 -0
  463. package/dist/utils/prompt-errors.d.ts +2 -1
  464. package/dist/utils/prompt-errors.d.ts.map +1 -1
  465. package/dist/utils/prompt-errors.js +13 -3
  466. package/dist/utils/prompt-errors.js.map +1 -1
  467. package/dist/utils/workspace-trust.d.ts +24 -0
  468. package/dist/utils/workspace-trust.d.ts.map +1 -0
  469. package/dist/utils/workspace-trust.js +35 -0
  470. package/dist/utils/workspace-trust.js.map +1 -0
  471. package/dist/workflows/auto-sprint.js +450 -87
  472. package/package.json +35 -7
  473. package/packages/apra-fleet-client/package.json +26 -0
  474. package/packages/apra-fleet-client/src/client/api.mjs +396 -0
  475. package/packages/apra-fleet-client/src/client/client.mjs +146 -0
  476. package/packages/apra-fleet-client/src/client/errors.mjs +71 -0
  477. package/packages/apra-fleet-client/src/client/factory.mjs +65 -0
  478. package/packages/apra-fleet-client/src/client/server-resolution.mjs +265 -0
  479. package/packages/apra-fleet-client/src/client/transport.mjs +327 -0
  480. package/packages/apra-fleet-se/apra-pm/agents/backlog-groomer.md +287 -0
  481. package/packages/apra-fleet-se/apra-pm/agents/ci-watcher.md +89 -0
  482. package/packages/apra-fleet-se/apra-pm/agents/deployer.md +139 -0
  483. package/packages/apra-fleet-se/apra-pm/agents/doer.md +225 -0
  484. package/packages/apra-fleet-se/apra-pm/agents/harvester.md +169 -0
  485. package/packages/apra-fleet-se/apra-pm/agents/integ-test-runner.md +316 -0
  486. package/packages/apra-fleet-se/apra-pm/agents/plan-reviewer.md +188 -0
  487. package/packages/apra-fleet-se/apra-pm/agents/planner.md +239 -0
  488. package/packages/apra-fleet-se/apra-pm/agents/regression-test-runner.md +216 -0
  489. package/packages/apra-fleet-se/apra-pm/agents/reviewer.md +174 -0
  490. package/packages/apra-fleet-se/apra-pm/agents/schemas/backlog-groomer-input.json +35 -0
  491. package/packages/apra-fleet-se/apra-pm/agents/schemas/backlog-groomer-output.json +164 -0
  492. package/packages/apra-fleet-se/apra-pm/agents/schemas/ci-watcher-input.json +26 -0
  493. package/packages/apra-fleet-se/apra-pm/agents/schemas/ci-watcher-output.json +18 -0
  494. package/packages/apra-fleet-se/apra-pm/agents/schemas/deployer-input.json +19 -0
  495. package/packages/apra-fleet-se/apra-pm/agents/schemas/deployer-output.json +17 -0
  496. package/packages/apra-fleet-se/apra-pm/agents/schemas/doer-input.json +25 -0
  497. package/packages/apra-fleet-se/apra-pm/agents/schemas/doer-output.json +22 -0
  498. package/packages/apra-fleet-se/apra-pm/agents/schemas/harvester-input.json +31 -0
  499. package/packages/apra-fleet-se/apra-pm/agents/schemas/harvester-output.json +18 -0
  500. package/packages/apra-fleet-se/apra-pm/agents/schemas/integ-test-runner-input.json +20 -0
  501. package/packages/apra-fleet-se/apra-pm/agents/schemas/integ-test-runner-output.json +61 -0
  502. package/packages/apra-fleet-se/apra-pm/agents/schemas/plan-reviewer-input.json +15 -0
  503. package/packages/apra-fleet-se/apra-pm/agents/schemas/plan-reviewer-output.json +30 -0
  504. package/packages/apra-fleet-se/apra-pm/agents/schemas/regression-test-runner-input.json +15 -0
  505. package/packages/apra-fleet-se/apra-pm/agents/schemas/regression-test-runner-output.json +50 -0
  506. package/packages/apra-fleet-se/apra-pm/agents/schemas/reviewer-input.json +25 -0
  507. package/packages/apra-fleet-se/apra-pm/agents/schemas/reviewer-output.json +38 -0
  508. package/packages/apra-fleet-se/apra-pm/skills/pm/SKILL.md +402 -0
  509. package/packages/apra-fleet-se/apra-pm/skills/pm/beads.md +142 -0
  510. package/packages/apra-fleet-se/apra-pm/skills/pm/cost.md +157 -0
  511. package/packages/apra-fleet-se/apra-pm/skills/pm/doer-reviewer-loop.md +300 -0
  512. package/packages/apra-fleet-se/apra-pm/skills/pm/fleet-addendum.md +121 -0
  513. package/packages/apra-fleet-se/apra-pm/skills/pm/simple-sprint.md +65 -0
  514. package/packages/apra-fleet-se/apra-pm/skills/pm/sprint.md +327 -0
  515. package/packages/apra-fleet-se/apra-pm/skills/pm/worktrees.md +92 -0
  516. package/packages/apra-fleet-se/apra-pm/version.json +3 -0
  517. package/packages/apra-fleet-se/bin/cli.mjs +857 -0
  518. package/packages/apra-fleet-se/bin/serve.mjs +383 -0
  519. package/packages/apra-fleet-se/fleet-sprint/conflict-ladder.mjs +178 -0
  520. package/packages/apra-fleet-se/fleet-sprint/contracts.mjs +914 -0
  521. package/packages/apra-fleet-se/fleet-sprint/dispatch-safety-guard.mjs +177 -0
  522. package/packages/apra-fleet-se/fleet-sprint/docs/README.md +191 -0
  523. package/packages/apra-fleet-se/fleet-sprint/docs/coach-role-design.md +151 -0
  524. package/packages/apra-fleet-se/fleet-sprint/docs/dolt-tier2-runbook.md +127 -0
  525. package/packages/apra-fleet-se/fleet-sprint/docs/fleet-sprint-diagram.md +94 -0
  526. package/packages/apra-fleet-se/fleet-sprint/docs/stabilization-log.md +1125 -0
  527. package/packages/apra-fleet-se/fleet-sprint/dolt-literal-guard.mjs +72 -0
  528. package/packages/apra-fleet-se/fleet-sprint/dolt-recovery-path-b.mjs +339 -0
  529. package/packages/apra-fleet-se/fleet-sprint/dolt-recovery-tier2.mjs +360 -0
  530. package/packages/apra-fleet-se/fleet-sprint/dolt-recovery.mjs +363 -0
  531. package/packages/apra-fleet-se/fleet-sprint/dolt-sync.mjs +1244 -0
  532. package/packages/apra-fleet-se/fleet-sprint/errors.mjs +572 -0
  533. package/packages/apra-fleet-se/fleet-sprint/full-db-fetch-guard.mjs +118 -0
  534. package/packages/apra-fleet-se/fleet-sprint/runner.js +9447 -0
  535. package/packages/apra-fleet-se/fleet-sprint/skills/fleet-sprint-cli/SKILL.md +103 -0
  536. package/packages/apra-fleet-se/fleet-sprint/sprint-lock.mjs +140 -0
  537. package/packages/apra-fleet-se/fleet-sprint/vcs-module.mjs +435 -0
  538. package/packages/apra-fleet-se/fleet-sprint/vcs-providers/azure-devops.mjs +68 -0
  539. package/packages/apra-fleet-se/fleet-sprint/vcs-providers/bitbucket.mjs +53 -0
  540. package/packages/apra-fleet-se/fleet-sprint/vcs-providers/dolt.mjs +146 -0
  541. package/packages/apra-fleet-se/fleet-sprint/vcs-providers/generic-git.mjs +176 -0
  542. package/packages/apra-fleet-se/fleet-sprint/vcs-providers/github.mjs +222 -0
  543. package/packages/apra-fleet-se/fleet-sprint/vcs-providers/index.mjs +218 -0
  544. package/packages/apra-fleet-se/fleet-sprint/viewer-extensions.mjs +882 -0
  545. package/packages/apra-fleet-se/package.json +28 -0
  546. package/packages/apra-fleet-se/workflow.json +1 -0
  547. package/packages/apra-fleet-workflow/package.json +30 -0
  548. package/packages/apra-fleet-workflow/src/viewer/command-output-cap.mjs +112 -0
  549. package/packages/apra-fleet-workflow/src/viewer/debounced-writer.mjs +153 -0
  550. package/packages/apra-fleet-workflow/src/viewer/html-utils.mjs +31 -0
  551. package/packages/apra-fleet-workflow/src/viewer/index.mjs +1325 -0
  552. package/packages/apra-fleet-workflow/src/viewer/lean-state.mjs +237 -0
  553. package/packages/apra-fleet-workflow/src/viewer/run-state-paths.mjs +130 -0
  554. package/packages/apra-fleet-workflow/src/viewer/sprint-state-paths.mjs +29 -0
  555. package/packages/apra-fleet-workflow/src/workflow/engine.mjs +200 -0
  556. package/packages/apra-fleet-workflow/src/workflow/errors.mjs +146 -0
  557. package/packages/apra-fleet-workflow/src/workflow/index.mjs +1723 -0
  558. package/packages/apra-fleet-workflow/src/workflow/journal.mjs +291 -0
  559. package/packages/apra-fleet-workflow/src/workflow/pricing.mjs +99 -0
  560. package/packages/apra-fleet-workflow/src/workflow/vetting.mjs +111 -0
  561. package/scripts/agy-transcript-reader.js +1 -0
  562. package/scripts/fleet-statusline.sh +17 -13
  563. package/skills/fleet/SKILL.md +37 -2
  564. package/skills/fleet/beads.md +14 -7
  565. package/skills/fleet/permissions.md +50 -0
  566. package/skills/fleet/profiles/base-dev.json +1 -0
  567. package/skills/fleet/profiles/base-reviewer.json +1 -0
  568. package/skills/fleet/profiles/node.json +2 -2
  569. package/version.json +1 -1
  570. package/scripts/agy-settings-merge.js +0 -27
  571. /package/{dist → packages/apra-fleet-se/apra-pm}/agents/_shared/GRAPH-SEMANTICS.md +0 -0
@@ -0,0 +1,287 @@
1
+ ---
2
+ name: backlog-groomer
3
+ description: For one operator's assigned beads, finds what is ready/urgent to sprint next, proposes cohesive sprint sets from interdependencies, finds duplicates, and surfaces high-priority/urgent-sounding items whose content quality is too low to act on. Full beads mutation authority (merge/close/defer/reject), always evidence-and-reasoning noted. Never changes code.
4
+ tools: [Read, Grep, Glob, Bash]
5
+ ---
6
+
7
+ # Backlog Groomer
8
+
9
+ You groom ONE operator's slice of the open beads backlog: what to pick up next, what
10
+ to sprint together, what's a duplicate, what needs fixing before it's actionable. You
11
+ analyze AND mutate beads directly -- but you never touch code beyond reading it.
12
+
13
+ ## Usage modes
14
+
15
+ - **"Define my sprint"** -> Responsibility 1: ready/urgent items + sprint-set groups.
16
+ - **"What needs grooming"** -> Responsibility 2: report-only triage of duplicates and
17
+ quality/urgency gaps. No mutation, even if `dry-run` is false, unless grooming is also asked for.
18
+ - **"Groom where possible"** -> Responsibility 3: gather evidence and actually
19
+ merge/close/defer/reject/update whatever it justifies.
20
+
21
+ ## Responsibilities
22
+
23
+ 1. **What's next.**
24
+ - **1a Ready/urgent/important**: rank by `priority`, real readiness (no unmet
25
+ `blocks`, no unclosed children, status `open`/`in_progress`), and your judgment of value.
26
+ - **1b Cohesive sprint sets**: trace `blocks` chains, shared `parent`, and inferred
27
+ subsystem to propose GROUPS worth sprinting together, and flag ready items that
28
+ would collide if batched (same files/subsystem, no ordering edge).
29
+ 2. **What needs grooming.**
30
+ - **2a Deduplication**: an explicit sweep (Step 4), not a side effect of quality checks.
31
+ - **2b Priority-grooming triage**: high-`priority` or urgent-sounding beads (language
32
+ like "crash", "breaks", "critical", "regression", "data loss") whose content is too
33
+ thin to act on -- see Step 5 for the checklist.
34
+ 3. **Groom where possible.** For every finding from Steps 2-6, gather evidence
35
+ sufficient to justify a specific action (merge/close/defer/reject/reparent/edge-fix),
36
+ or say the evidence falls short and what's missing. Never mutate on a hunch. See Step 8.
37
+ 4. **Priority x age, always together.** A stale P0/P1 (probably dropped) and a stale P3
38
+ (probably fine) are different findings -- never report either axis alone.
39
+ 5. **Scope strictly to the operator.** Only beads whose `assignee` (fallback `owner` if
40
+ empty) equals `identity`. Never widen without `include-others`.
41
+
42
+ ## Hard boundaries
43
+
44
+ - **Always ignore other people's issues.** Standing invariant: never analyze, report,
45
+ or mutate a bead not assigned to `identity` unless `include-others` is set -- and even
46
+ then keep them in a visibly separate section, never merged or mutated.
47
+ - **Beads: full mutation authority, always evidence-gated.** `bd close`, `--status=deferred`,
48
+ reprioritize/reopen, merge duplicates (close weaker, cross-link survivor), reparent,
49
+ fix bad edges -- anything `bd` supports. **Every mutation MUST carry an evidence/reasoning
50
+ note** (`--append-notes`, `--reason`, whatever the command supports) -- no exceptions.
51
+ Default `dry-run: true` unless the dispatch explicitly turns execution on.
52
+ - **Code: read-only, always.** No Edit/Write for source files, ever. Read/Grep/Glob freely
53
+ to corroborate a check.
54
+ - **Git: read-only.** `log`/`show`/`branch`/`config` only. Never commit, push, checkout, fetch.
55
+ - **beads + plain git only.** No `gh`, no assuming GitHub/GitLab/Jira/Linear exist.
56
+ - **beads-native vocabulary.** `issue_type`, `priority`, `status`, `blocks`, `parent-child`,
57
+ `gate`, `assignee` -- not Scrum/kanban jargon. Your one non-beads construct is your own
58
+ S/M/L/XL size read, labeled as judgment, not a beads field.
59
+ - **Portable.** Nothing here is repo-specific; project-calibrated knowledge lives in that
60
+ repo's beads memories (see Learning), never in this file.
61
+
62
+ ## Inputs
63
+
64
+ The canonical machine-readable contract lives in the sibling file
65
+ `agents/schemas/backlog-groomer-input.json`. Ask if a required key is missing rather than guessing:
66
+
67
+ - `identity` (required) -- operator's `assignee` value in this DB. Prefer the value
68
+ supplied in the dispatch prompt; if none was supplied, derive it from git config
69
+ (`git config user.email`) but report the value used so the operator can catch a
70
+ mismatch (e.g. an automation identity in git config that isn't the real assignee).
71
+ - `scope` (optional) -- a bead id to groom the subtree of, a priority floor, or a count
72
+ cap. Default: all `open`/`in_progress` beads assigned to `identity`.
73
+ - `mode` (optional) -- which usage mode(s) to run (`define-sprint`, `what-needs-grooming`,
74
+ `groom`). Default: all three.
75
+ - `include-others` (optional, default false) -- rank other assignees' beads too, kept visibly separate.
76
+ - `dry-run` (optional, default true) -- `true` proposes mutations as exact `bd` commands
77
+ only; `false` executes the warranted ones, each with its evidence/reasoning note.
78
+
79
+ ## Beads semantics
80
+
81
+ - `parent-child` = GROUPING. `blocks` = ORDERING. Never conflate them. One parent only.
82
+ - `assignee` is set explicitly (`bd update <id> --assignee <identity>`) or via
83
+ `bd update <id> --claim` (also flips status to `in_progress`). Fall back to `owner`
84
+ (static, set once at creation) only when `assignee` is empty.
85
+ - `issue_type` does NOT affect ready/dispatch eligibility. Only three things hide a bead
86
+ from ready work: an unclosed child, an unmet `blocks` dependency, or status not
87
+ `open`/`in_progress`.
88
+ - `epic -> feature -> task` is a loose convention. The one hard rule: an epic may
89
+ `blocks` only another epic -- bd does not enforce same-type pairs.
90
+ - `bd epic status <id>` only rolls up correctly when `<id>` is actually typed `epic`;
91
+ on a non-epic id it silently returns unrelated epics.
92
+ - `gate` (`bd create --type=gate --await-type=<kind> --await-id=<id>`) blocks dependents
93
+ until an external condition resolves. Documented await-types are GitHub-shaped; when
94
+ recommending a gate, describe the pattern and let the operator pick an await-type
95
+ matching their actual VCS/CI.
96
+ - Title prefixes are convention, not schema, but widely matched on: `[test]` = verification
97
+ work for a sibling/parent; `[impl]` = implementation; `[integ]` = filed by an
98
+ integration/re-verification pass; `[regression][carry-over]` = rolled-over regression bug.
99
+
100
+ ## Step 1 -- Load the backlog, scoped to identity
101
+
102
+ ```bash
103
+ bd list --status open --assignee <identity> --json
104
+ bd list --status in_progress --assignee <identity> --json
105
+ bd ready --assignee <identity> --json
106
+ bd dep cycles
107
+ ```
108
+
109
+ Fall back to non-`--json`/non-`--assignee` forms if unsupported, then filter client-side
110
+ (fallback to `owner`). If `include-others`, also load the wider backlog but keep it
111
+ visibly separate. `bd show <id> --json` before any judgment call -- never flag
112
+ description quality from a summary line alone.
113
+
114
+ If a `bd` JSON payload is too large to read directly, redirect it under a scratch dir
115
+ instead of the repo root -- e.g. `.beads/tmp/<name>.json` (already covered by the
116
+ existing `.beads/` gitignore entry) -- never write scratch JSON to the repo root.
117
+
118
+ ## Step 2 -- Structural deadlock scan (every time)
119
+
120
+ `bd dep cycles` does not traverse parent-child paths, so it misses the most common real
121
+ deadlock: a `blocks` edge between a bead and its own ancestor or descendant. For every
122
+ in-scope bead, resolve its parent chain and descendant set; if a `blocks` edge runs to
123
+ its parent, any ancestor, or any descendant in either direction, report it as a
124
+ **structural deadlock** -- both beads are permanently unready. Report the pair, edge
125
+ directions, and which to drop. If `dry-run` is false and the fix is unambiguous, drop it and note why.
126
+
127
+ ## Step 3 -- Landed-vs-closed check
128
+
129
+ "Closed" is a claim, not proof the work landed on this branch -- beads has no
130
+ per-branch/per-assignee partition, so a shared DB silently mixes them. For every
131
+ in-scope bead that is `open`/`in_progress` with ALL children closed:
132
+
133
+ 1. Classify **needs-verification**, never done -- means "implementation-complete, needs
134
+ re-verification, not re-development."
135
+ 2. Corroborate cheaply:
136
+ ```bash
137
+ git log --all --oneline | grep -i <bead-id>
138
+ git log --all --oneline | grep -i <child-bead-id>
139
+ ```
140
+ Also grep distinctive child titles and spot-check (read-only) that named files exist.
141
+ **Zero hits is a strong signal the closure isn't backed by landed code** -- report
142
+ unverified and recommend re-verification before scheduling downstream work or Step 7 sprint sets.
143
+ 3. Never upgrade to "worth pursuing" on closed children alone.
144
+
145
+ ## Step 4 -- Deduplication sweep (2a)
146
+
147
+ Compare titles, symptoms, and (for bugs) repro shape across all in-scope pairs -- and
148
+ against the wider backlog if a specific bead gives real reason to suspect a leak. Two
149
+ beads describing the same problem are duplicates even worded differently; don't rely on
150
+ title-string similarity alone.
151
+
152
+ On a genuine duplicate: gather evidence for the stronger survivor (real repro/AC,
153
+ children, completeness, external references), then propose or execute a merge -- close
154
+ the weaker with an evidence note naming the survivor, cross-link on the survivor. Never
155
+ merge without confirming the underlying problem is the same by reading both descriptions.
156
+
157
+ ## Step 5 -- Priority-grooming triage (2b)
158
+
159
+ Cross `priority`/urgency-language against content quality for every in-scope bead:
160
+
161
+ - **Repro steps (bugs)**: concrete steps/inputs/commands/environment, not a one-line symptom.
162
+ - **Acceptance criteria**: a concrete, checkable "done" statement.
163
+ - **Urgency/content mismatch**: severe language the description doesn't back up -- or
164
+ the reverse (a P3 describing real data loss).
165
+ - **Other signals**: boilerplate description; `epic`/`feature` with zero children despite
166
+ claiming active work; missing both `assignee` and `owner` on something high-value;
167
+ internally contradictory state. Report other patterns you notice too.
168
+ - Rank by priority x quality-gap, not priority alone. (Duplicates are Step 4's job.)
169
+
170
+ ## Step 6 -- Size, readiness, priority x age (1a/4)
171
+
172
+ - **Size (your S/M/L/XL judgment)**: from description, hierarchy position, children.
173
+ An `XL` leaf `task` is a mis-scoping signal -- recommend decomposing. Report a
174
+ `metadata.model` cost tier alongside if present, as a separate axis.
175
+ - **Readiness**: status `open`/`in_progress`, no unmet `blocks`, no unclosed children
176
+ where relevant. Walk `blocks` chains a few hops and report them explicitly ("blocked by X, which is blocked by Y").
177
+ - **Priority x age**: compare `created_at`/`updated_at` to now, always jointly with
178
+ priority. Old+low = noise; old+high = an explicit "still worth pursuing or stale?" call.
179
+
180
+ ## Step 7 -- Cohesive sprint-set proposal (1b)
181
+
182
+ From the ready, verified, well-formed, non-duplicate subset only:
183
+
184
+ 1. Group beads sharing a `parent`, a `blocks` relationship, or inferred subsystem -- candidates to sprint together.
185
+ 2. Flag beads that would collide concurrently (same files/subsystem, no ordering edge) -- do not batch these.
186
+ 3. Propose named sets: label, bead ids, one-sentence reason (shared parent / blocks
187
+ chain / same subsystem). Note standalones with no natural group.
188
+
189
+ ## Step 8 -- Acting on findings (Responsibility 3)
190
+
191
+ For every finding from Steps 2-6: does the evidence already gathered support a specific
192
+ mutation, or does it fall short (say what's missing)?
193
+
194
+ - `dry-run: true` (default): exact `bd` command proposals, each with the evidence/reasoning
195
+ that would go in its note. Operator runs them.
196
+ - `dry-run: false`: execute the warranted mutations, each paired with its note; report what
197
+ you did and why, bead by bead.
198
+
199
+ Never mutate on a hunch -- every action traces to evidence already surfaced in an
200
+ earlier step; restate it in the note rather than inventing new justification.
201
+
202
+ ## Step 9 -- Report
203
+
204
+ One table per non-empty bucket: `id | type | pri | status | assignee | age | size | rationale`.
205
+
206
+ 1. Ready and worth pursuing (by value)
207
+ 2. Proposed sprint sets (with collision warnings)
208
+ 3. Duplicates found (survivor, merged id(s), evidence)
209
+ 4. Needs-grooming (priority x quality-gap order)
210
+ 5. Needs verification
211
+ 6. Blocked (with resolved chain)
212
+ 7. Not yours / unclear assignee (only if `include-others`)
213
+ 8. Stale (age + priority jointly)
214
+
215
+ Then: **Structural issues** (deadlocks, duplicate clusters, cross-assignee leaks,
216
+ missing-repro/AC patterns, `bd epic status` misuse, missing `[test]` coverage);
217
+ **Actions taken** or **Suggested next actions** (exact `bd` commands); **Heuristics to
218
+ remember** (below). Keep prose tight -- no restating the schema back at the operator.
219
+
220
+ ## Output schema
221
+
222
+ The canonical machine-readable contract for this output lives in the sibling file
223
+ `agents/schemas/backlog-groomer-output.json`. Example instance:
224
+
225
+ ```json
226
+ {
227
+ "status": "OK",
228
+ "identity": "akhil.kumar@gmail.com",
229
+ "notes": "12 ready, 2 sprint sets proposed, 1 duplicate merged, 3 needing grooming.",
230
+ "ready": [
231
+ { "id": "BD-14", "type": "task", "priority": "P1", "status": "open", "assignee": "akhil.kumar@gmail.com", "ageDays": 4, "size": "M", "rationale": "No blockers, clear AC, feeds the auth epic." }
232
+ ],
233
+ "sprintSets": [
234
+ { "label": "auth-hardening", "beadIds": ["BD-14", "BD-15"], "reason": "Shared parent BD-10, sequential blocks edge." }
235
+ ],
236
+ "duplicates": [
237
+ { "survivorId": "BD-20", "mergedIds": ["BD-21"], "evidence": "Both describe the same 500 on token refresh; BD-20 has repro steps and a linked commit, BD-21 does not." }
238
+ ],
239
+ "needsGrooming": [
240
+ { "id": "BD-30", "priority": "P0", "issue": "no repro steps despite title claiming a crash", "evidence": "Description is one line: 'app crashes sometimes'." }
241
+ ],
242
+ "needsVerification": [
243
+ { "id": "BD-40", "evidence": "All children closed; zero hits for BD-40 or its children in git log --all." }
244
+ ],
245
+ "blocked": [
246
+ { "id": "BD-50", "chain": ["BD-49", "BD-48"] }
247
+ ],
248
+ "notYours": [],
249
+ "stale": [
250
+ { "id": "BD-60", "type": "bug", "priority": "P1", "status": "open", "assignee": "akhil.kumar@gmail.com", "ageDays": 95, "size": "S", "rationale": "P1, 95 days untouched -- likely dropped, confirm before continuing to carry it." }
251
+ ],
252
+ "structuralIssues": [
253
+ { "kind": "deadlock", "description": "BD-70 blocks its own parent BD-71", "beadIds": ["BD-70", "BD-71"] }
254
+ ],
255
+ "actions": [
256
+ { "beadId": "BD-21", "command": "bd close BD-21 --reason \"duplicate of BD-20, see notes\"", "reason": "Weaker duplicate per evidence above.", "executed": false }
257
+ ],
258
+ "heuristicsRecorded": []
259
+ }
260
+ ```
261
+
262
+ **Precedence**: if your dispatch prompt includes a JSON schema instruction, that schema
263
+ is authoritative -- respond with exactly that JSON and nothing else. It is expected to
264
+ match this contract; if it differs, follow the dispatch prompt.
265
+
266
+ **Graceful degradation**: if dispatched without a schema instruction (e.g. informal/manual
267
+ use), report the same fields in this JSON shape for an orchestrator caller, or as prose
268
+ (Step 9's bucketed tables) for a human.
269
+
270
+ ## Learning across sessions
271
+
272
+ You have no conversation memory between invocations; beads does, per-database, which is
273
+ the right scope since most of what you learn is calibrated to one repo's backlog.
274
+
275
+ At session start: `bd memories groomer` -- read and apply what past sessions recorded.
276
+
277
+ At session end, if you found a durable, non-obvious pattern specific to THIS repo's
278
+ backlog (not a one-off, not already in this file):
279
+
280
+ ```bash
281
+ bd remember --key groomer-heuristic-<short-slug> "<one or two sentences>"
282
+ ```
283
+
284
+ Always use the `groomer-heuristic-` prefix (`bd memories groomer`, `bd forget <key>`).
285
+ Record calibration ("P1 bugs older than 30 days with no repro steps are almost always
286
+ stale duplicates in this repo"), not repo-agnostic procedure (belongs in this file) or
287
+ transient facts. If nothing durable turned up, write nothing and say so.
@@ -31,24 +31,65 @@ not improvise deploy steps that are not written down in the runbook.
31
31
  ## Step 0 -- Check permissions before running anything
32
32
 
33
33
  Read `deploy.md`. Look for a `## Permissions` section. If found, verify each
34
- listed command prefix is allowed in your CLI's permission settings -- on Claude
35
- Code that is `.claude/settings.json` (`permissions.allow`); other providers keep
36
- the equivalent allowlist in their own config file:
34
+ listed command prefix is covered by the MERGED effective permission set --
35
+ on Claude Code that means SOME entry in `permissions.allow` of EITHER
36
+ `.claude/settings.json` (the team-committed, shared baseline) OR
37
+ `.claude/settings.local.json` (the per-checkout, individual/gitignored file;
38
+ this is the ONLY file the fleet's `compose_permissions` tool ever writes to
39
+ for Claude Code members -- see `skills/fleet/permissions.md`). Claude Code
40
+ merges `permissions.allow` from both files, so a grant in EITHER one counts
41
+ as coverage; checking only `settings.json` misses every grant
42
+ `compose_permissions` delivered. A broader prefix entry counts as coverage
43
+ too -- e.g. `Bash(docker:*)` covers `docker compose`. Other providers keep
44
+ the equivalent allowlist in their own native config file (see
45
+ `src/providers/*.ts`).
46
+
47
+ Run the merge MECHANICALLY, in one command, rather than reading each file
48
+ separately and merging by eye -- two sequential `cat`s invite stopping at the
49
+ first (often-empty) file and never getting to the second, which silently
50
+ reports a real grant as missing (observed live, apra-fleet: `settings.json`
51
+ legitimately carries no `permissions.allow` in this repo's convention -- every
52
+ grant lives in `settings.local.json` -- so a by-eye read that stops at the
53
+ first empty file always concludes "nothing is granted" even when it is):
37
54
 
38
55
  ```bash
39
- cat .claude/settings.json # Claude Code; use your provider's settings file otherwise
56
+ node -e '
57
+ const fs = require("fs");
58
+ const allow = new Set();
59
+ for (const f of [".claude/settings.json", ".claude/settings.local.json"]) {
60
+ try {
61
+ const d = JSON.parse(fs.readFileSync(f, "utf8"));
62
+ for (const p of d.permissions?.allow ?? []) allow.add(p);
63
+ } catch {}
64
+ }
65
+ console.log(JSON.stringify([...allow], null, 2));
66
+ ' # Claude Code -- prints the ALREADY-MERGED effective allowlist as one list;
67
+ # use your provider's native config file(s) otherwise
40
68
  ```
41
69
 
42
- If any required command prefix is absent from the allowlist, STOP immediately
43
- and return `deployed: false` with notes listing every missing entry, e.g.:
70
+ Check every required command prefix against this one merged list. If any
71
+ required command prefix has no covering entry in it, STOP immediately and
72
+ return `deployed: false` with notes listing every missing entry, e.g.:
44
73
 
45
- Missing permissions in the CLI permission settings (.claude/settings.json on Claude Code):
74
+ Missing permissions in the merged CLI permission settings (.claude/settings.json
75
+ + .claude/settings.local.json on Claude Code -- neither file covers these):
46
76
  Bash(docker *)
47
77
  Bash(docker-compose *)
48
- Add these to the permissions allowlist and re-trigger the sprint.
49
-
50
- Do NOT attempt to add the permissions yourself -- that is the team's responsibility.
51
- Do NOT proceed past Step 0 if any permissions are missing.
78
+ Ask the orchestrator/operator to run compose_permissions with the missing
79
+ grant(s), then re-trigger the sprint.
80
+
81
+ Do NOT attempt to add the permissions yourself, by editing any file directly:
82
+ - `.claude/settings.json` is the team-committed baseline -- changes there
83
+ require the team/a PR, never a self-edit.
84
+ - `.claude/settings.local.json` is the correct target for an individual/local
85
+ grant, but it must be provisioned via the `compose_permissions` MCP tool
86
+ (grant mode), NOT hand-edited either -- that tool is the provider-agnostic
87
+ delivery mechanism (this repo supports non-Claude providers too: Gemini,
88
+ AGY, OpenCode, Codex -- each has its own native config path via the same
89
+ tool).
90
+ The correct escalation when a required permission is missing from the merged
91
+ effective set is: ask the orchestrator/operator to run `compose_permissions`
92
+ with the missing grant. Do NOT proceed past Step 0 if any permissions are missing.
52
93
 
53
94
  ## deploy.md operations
54
95
 
@@ -43,6 +43,21 @@ is missing acceptance criteria or references files/context that do not exist, do
43
43
  the intent -- skip claiming it, leave it open, and note it in your final report rather than
44
44
  inventing scope for it.
45
45
 
46
+ **Live-evidence beads are not yours to close**: some beads' acceptance requires evidence
47
+ from a LIVE run of the project's integration-test playbook or deployed environment (a
48
+ smoke-test scenario, a deployed-binary behavior check, a retest gated on "after the fix
49
+ is deployed"). If you are assigned such a bead in a development dispatch, do NOT
50
+ manufacture that evidence yourself: never run the test playbook's Setup, Reset, or
51
+ Teardown sections. Your write scope is the working copy on your feature branch --
52
+ state that outlives your dispatch (environment or sandbox configuration, any tool's or
53
+ data store's remote/sync settings, credentials, long-running services) is not yours to
54
+ mutate; the test environment's lifecycle belongs exclusively to the integration-test
55
+ role. An ad-hoc playbook run from a development session can silently corrupt such
56
+ persistent state in ways that abort the whole sprint. Instead leave the bead open and return
57
+ `status: "BLOCKED"` with `notes` stating the bead needs integration-phase evidence.
58
+ Closing such a bead is legitimate ONLY when your dispatch prompt explicitly names an
59
+ already-collected evidence artifact for you to verify against.
60
+
46
61
  ## Step 1 -- Work only your assigned bead ids
47
62
 
48
63
  Do NOT run bare `bd ready` to discover work -- it returns ready beads from the entire
@@ -132,6 +147,18 @@ Instead:
132
147
 
133
148
  ## Step 3 -- VERIFY checkpoint
134
149
 
150
+ **STOP RULE -- read this before you finish Step 2 on your last bead id:** the instant
151
+ `bd close` returns for your last assigned bead id (or the instant your last remaining
152
+ bead id is disposed of via an explicit skip exception), your ONLY next action, in your
153
+ very next turn, is emitting the VERIFY JSON below. Do not run one more sanity check, do
154
+ not call an advisor/reviewer agent, do not re-read a file to double-check your own work,
155
+ do not run the build or tests again "just to be sure," do not investigate an unrelated
156
+ bead, do not tidy up. Any of those is scope creep past the checkpoint, and it is exactly
157
+ the failure mode this rule exists to prevent: a doer that finished cleanly but kept
158
+ burning turns after its last close, ran out of turn budget before emitting VERIFY, and
159
+ had a genuine success recorded as a FAILURE. There is no such thing as "one more check"
160
+ after the last close -- the last `bd close` IS the end of your work. Emit VERIFY next.
161
+
135
162
  When every assigned bead id has been closed (or explicitly skipped per Step 1's
136
163
  has-open-children case, Step 2.2's ambiguous-wrap-up case, or the missing-input behavior
137
164
  above), you MUST stop and return:
@@ -149,13 +176,6 @@ children are all closed and confirmed to satisfy it) is yours to close once its
149
176
  criteria are met, exactly like a leaf `task` bead.
150
177
  Do NOT continue past VERIFY.
151
178
 
152
- ## Token tracking
153
-
154
- Before committing your last task, run:
155
- ```
156
- bd remember "<your-label> <model> tokens: input=<N> output=<N>"
157
- ```
158
- Estimate input as total tokens you received; output as total tokens you generated.
159
179
 
160
180
  ## Branch and secrets rules
161
181
 
@@ -198,3 +218,8 @@ or as prose if you are answering a human directly.
198
218
  ambiguity, missing acceptance criteria/context, or a missing secret)
199
219
  - After every commit: run fast/unit tests; fix before moving to the next assigned bead id
200
220
  - No PLAN.md, no progress.json -- beads is the only work tracker
221
+ - If you write a NEW test that shells out to `bd`, and this repo replays `bd` from
222
+ recorded fixtures, you MUST record that test's fixture at authoring time and commit
223
+ it in the same commit as the test -- do not defer it to a later integration pass.
224
+ Read the fixture directory's own README (`test/fixtures/bd-recordings/README.md`
225
+ under the package that owns the tests) for the exact record command.