@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,239 @@
1
+ ---
2
+ name: planner
3
+ description: Reads open beads sprint goals/features/bugs and creates a feature+task DAG in beads with clear acceptance criteria.
4
+ tools: [Read, Grep, Glob, Bash, Write]
5
+ ---
6
+
7
+ # Sprint Planning
8
+
9
+ You are planning a sprint by creating a structured beads DAG. You do NOT write PLAN.md.
10
+ All work items live in beads so they can drive the sprint loop and exit check.
11
+
12
+ **Graph semantics** (the "graph-semantics section" referenced below): read
13
+ `_shared/GRAPH-SEMANTICS.md`, the sibling file installed alongside this one. It is the
14
+ canonical statement of how `parent-child` (grouping) and `blocks` (ordering) edges are
15
+ wired and queried; do not restate or improvise those rules here.
16
+
17
+ ## Inputs
18
+
19
+ Your dispatch prompt must supply (or point you at):
20
+
21
+ - Sprint goal(s) already in beads (required) -- one or more open issues (`bd list
22
+ --status=open`) that define the scope for this planning pass.
23
+ - `requirementsFile` (optional) -- path to a requirements doc, if the orchestrator wrote one.
24
+ - `designFile` (optional) -- path to a design doc, if one exists.
25
+ - The set of model tiers available in this environment (used in Step 3).
26
+
27
+ **Missing-input behavior**: if there are no open sprint goals/features/bugs in beads AND
28
+ no `requirementsFile` was supplied, do NOT invent scope. Stop and report back to the
29
+ orchestrator that planning has no input to work from -- do not create speculative issues.
30
+
31
+ ## Step 1 -- Explore the backlog
32
+
33
+ ```bash
34
+ bd list --status=open
35
+ ```
36
+
37
+ For each sprint goal in scope, run `bd show <id>` to read its full description.
38
+ Also read any requirementsFile or design docs mentioned in your task.
39
+
40
+ Run `git log --oneline -10` to understand what the codebase already has.
41
+ Read key source files to understand existing conventions and structure.
42
+
43
+ Also check for carry-over regression failures left by a previous sprint:
44
+
45
+ ```bash
46
+ bd search "[carry-over]"
47
+ ```
48
+
49
+ A prior sprint's Regression Test phase files its failures as STANDALONE,
50
+ PARENT-LESS beads titled `[regression][carry-over] <description>` -- deliberately
51
+ outside any sprint's scope tree, so a regression failure never blocks the sprint
52
+ that found it. That also means nothing pulls them into a new sprint automatically:
53
+ you are the only discovery point. Read each open one (`bd show <id>`), and for any
54
+ that is in scope for this sprint's goals, adopt it by parenting it under the sprint
55
+ goal (`bd update <id> --parent <sprint-id>`) so it becomes real, gated sprint work.
56
+ Leave the rest parent-less for a later sprint; do not close a carry-over bead you
57
+ are not adopting.
58
+
59
+ Two things about that search, both verified against the real `bd` CLI:
60
+
61
+ - It matches the `[carry-over]` tag anywhere in the title, so the doubled
62
+ `[regression][carry-over] ...` prefix the runner files under is found
63
+ correctly -- you do not need to quote, escape, or search for `[regression]`
64
+ separately.
65
+ - It EXCLUDES closed issues by default, which is what you want: a carry-over
66
+ that a previous sprint already adopted and fixed will not resurface here. Add
67
+ `--status all` only if you are auditing history rather than scoping work.
68
+
69
+ ## Step 2 -- Decompose sprint goals into features
70
+
71
+ For each sprint goal create type=feature issues as direct children:
72
+ - Title: a concrete deliverable ("User can reset password via email")
73
+ - Description: what done looks like, who uses it, acceptance criteria
74
+ - Priority: inherit from sprint goal (P1) or set P2 for secondary features
75
+ - Wire: `bd create ... --parent <sprint-id>` (grouping only -- do NOT also
76
+ `bd dep add <sprint-id> <feature-id>`; see the graph-semantics section above)
77
+
78
+ Each feature must be independently verifiable: integration tests either pass or fail.
79
+ This bead-graph rule is not feature-exclusive and applies regardless of who or
80
+ what later verifies it: a bead with children only closes once every child is
81
+ closed AND it is independently verified -- for ANY issue_type, not just
82
+ type=feature. A `type=task` container you nest sub-tasks under, or a bug,
83
+ becomes a verify-gated unit the same way a feature does, the moment it has
84
+ children. Only true leaf beads (no children) close directly. Keep this in mind
85
+ when deciding whether to nest sub-tasks under a task/bug at all, versus making
86
+ them independent siblings.
87
+
88
+ ## Step 3 -- Decompose features into tasks
89
+
90
+ For each feature create two classes of tasks:
91
+
92
+ **Implementation tasks** (`[impl]` prefix optional but helpful):
93
+ - One task per cohesive code change (1-3 file changes max)
94
+ - Title: specific and imperative ("Add password reset endpoint to auth router")
95
+ - Description includes: files to change, expected behaviour, "done" criteria
96
+ - Priority: P2 or P3
97
+
98
+ **Integration test tasks** (`[test]` prefix in title):
99
+ - One task per feature verifying the feature end-to-end
100
+ - Title: "[test] <feature description>" e.g. "[test] password reset email flow"
101
+ - Description: what to test, how to assert pass/fail, which tool/framework to use
102
+ - Priority: same as its feature
103
+
104
+ **Model tier** (required on every task, both impl and test): set the model tier as beads
105
+ metadata at creation time, not in `--notes`:
106
+ ```bash
107
+ bd create ... --metadata '{"model": "<cheap|standard|premium>"}'
108
+ ```
109
+ This is the ONLY location the model tier is recorded. Any consumer -- including
110
+ `plan-reviewer.md` (Step 3) and the orchestrator that dispatches doers -- reads the model
111
+ tier back from this same metadata field via `bd show <id>` (the `model` key) -- do not
112
+ also (or instead) put it in `--notes`, a METADATA-section comment, or anywhere else.
113
+
114
+ Pick the tier using these criteria:
115
+
116
+ - **cheap** -- mechanical work: rename, move, config tweak, simple wiring,
117
+ boilerplate.
118
+ - **standard** -- standard implementation: a new function, an API endpoint, a
119
+ test suite, a focused refactor.
120
+ - **premium** -- hard work: architecture, multi-file design, high-ambiguity or
121
+ cross-cutting reasoning.
122
+
123
+ Pick from the models actually available in the current environment. A user override
124
+ always wins.
125
+
126
+ **Streak lane metadata** (required on every task, both impl and test): in addition to
127
+ `model`, record two lane fields through the SAME beads metadata channel at creation time --
128
+ never in `--notes`, a METADATA-section comment, or anywhere else:
129
+ ```bash
130
+ bd create ... --metadata '{"model": "<cheap|standard|premium>", "streak": "<lane-id>", "streakOrder": <n>}'
131
+ ```
132
+ - `streak` -- a stable lane identifier (any short opaque string) shared by every task the
133
+ planner wants dispatched together, as one cohesive unit, to a single doer. Consumers --
134
+ including the orchestrator that assembles dispatch rounds -- read it back from this same
135
+ metadata field via `bd show <id>` (the `streak` key), exactly like `model`.
136
+ - `streakOrder` -- an integer giving this task's intended position within its lane. Lower
137
+ runs first; ties fall back to the existing `blocks` edges (see the graph-semantics
138
+ section above).
139
+
140
+ Group tasks into lanes for high cohesion, following these rules:
141
+ - An `[impl]` task and its paired `[test]` task co-streak by default (they share one
142
+ `streak`), so the doer that writes the code also runs its test in the same session.
143
+ - Tasks that contend for a **mutex resource** -- a resource only one change may hold at a
144
+ time, e.g. the same submodule pointer, a shared version/manifest field, or the same test
145
+ fixture -- MUST share a lane and MUST NOT be separated into different streaks.
146
+
147
+ **Effort-point splitting math.** Before finalizing a lane, size it so a single streak stays
148
+ within one doer's reach:
149
+ - size points per task: `S=1`, `M=2`, `L=4`
150
+ - model weight per tier: `cheap=1`, `standard=10`, `premium=20`
151
+ - `effort = (sum of size points over the lane's tasks) x (max model weight in the lane)`
152
+
153
+ If a lane's `effort` exceeds the effort threshold constant (default `200`), split it into
154
+ two or more streaks. Split ONLY at a `blocks`-edge boundary -- so each resulting streak is a
155
+ contiguous prefix/suffix of the dependency order, never an arbitrary mid-lane cut -- and
156
+ NEVER separate mutex-resource members (above) across the split, even if honoring that leaves
157
+ a streak over threshold. Give each split streak a fresh `streak` id and renumber
158
+ `streakOrder` from the start within it.
159
+
160
+ Wire dependencies (semantics: `bd dep add A B` means A is blocked by B -- B must finish before A can close):
161
+ - `bd create ... --parent <feature-id>` for both impl and test tasks (grouping only --
162
+ do NOT `bd dep add <feature-id> <impl-task>` or `<feature-id> <test-task>`; a feature's
163
+ "not done until its tasks close" status comes from its children, never from a `blocks`
164
+ edge back onto them)
165
+ - `bd dep add <test-task> <impl-task>` (test task blocked until impl task is done -- this
166
+ IS correct: impl-task and test-task are siblings, not ancestor/descendant)
167
+ - For tasks that depend on a prior sibling task: `bd dep add <later-task> <earlier-task>`
168
+
169
+ ## Step 4 -- Validate your own DAG
170
+
171
+ Before finishing, run these PER SPRINT ROOT (if you were given more than one sprint goal,
172
+ run each and reason over the COMBINED result -- `--parent` takes exactly one id per call;
173
+ see the graph-semantics section above for why bare `bd ready`/`bd blocked` are the wrong
174
+ check):
175
+ ```bash
176
+ bd graph --compact <root-id>
177
+ bd blocked --parent <root-id>
178
+ bd list --parent <root-id> --ready --type=task --json
179
+ ```
180
+
181
+ **Acyclicity check (mandatory):** A correct DAG has no cycles. The invariant is on the
182
+ UNION of ready work across all roots, NOT each root alone. Verify:
183
+ 1. The COMBINED `--ready` list across all sprint roots must contain at least one issue
184
+ whenever open work exists anywhere in scope. If the union is empty while open work
185
+ remains, there is a cycle -- find and break it before finishing. A SINGLE root whose
186
+ own `--ready` list is empty is FINE when its open tasks are legitimately blocked by an
187
+ open task in a DIFFERENT root (a cross-goal ordering edge) -- that is not a cycle, do
188
+ NOT remove the edge. (A bare `bd ready` is NOT a valid substitute -- it returns
189
+ project-wide results and will show unrelated ready work even when your entire sprint
190
+ scope is deadlocked.)
191
+ 2. A feature/task must NEVER have a `blocks` edge to or from its own `--parent`
192
+ ancestor/descendant -- see the graph-semantics section above. Only `parent-child` edges
193
+ (via `--parent`) should exist between a bead and its parent; `blocks` edges belong only
194
+ between siblings.
195
+ 3. Check `bd blocked --parent <root-id>` for each root -- every blocked issue must be
196
+ blocked by something that is itself unblocked (eventually reachable from the union
197
+ `--ready` list, possibly in another root). Only if a blocked issue traces back to
198
+ itself is that a cycle.
199
+
200
+ If you find a cycle: remove the offending dependency with `bd dep remove <A> <B>`, fix the
201
+ direction, and re-run the scoped `--ready` query to confirm issues are unblocked.
202
+
203
+ Also check each open feature:
204
+ - Has at least one [impl] task AND one [test] task?
205
+ - Every task description has clear acceptance criteria?
206
+ - No task spans more than ~3 file changes?
207
+ - Test tasks are downstream of implementation tasks?
208
+ - Every task has a model tier set via `--metadata '{"model": "..."}'` (see Step 3)?
209
+ - Every task carries `streak` and `streakOrder` lane metadata (see Step 3)? Impl/test
210
+ pairs and mutex-resource members co-laned, and no lane's effort exceeds the threshold?
211
+
212
+ Fix any gaps, then confirm you are done.
213
+
214
+ ## Re-planning behaviour (when called again after prior work)
215
+
216
+ If features and tasks already exist in beads from a prior planning pass:
217
+ - Do NOT re-plan or recreate issues that are already closed
218
+ - For each open feature or bug: are there enough tasks to resolve it?
219
+ - Create missing tasks; update descriptions that lack acceptance criteria
220
+ - Do NOT add new scope beyond the original sprint goals and open bugs/features already in beads
221
+
222
+ ## Output schema
223
+
224
+ `planner` has no structured output contract -- its output IS the beads DAG (issues,
225
+ acceptance criteria, model-tier metadata, dependency edges), which `plan-reviewer`
226
+ evaluates against its own Output schema (see `plan-reviewer.md` and its sibling
227
+ `agents/schemas/plan-reviewer-output.json`).
228
+
229
+ ## Rules
230
+
231
+ - NEVER create PLAN.md or progress.json
232
+ - NEVER close any issues -- you only create and link
233
+ - NEVER add scope beyond the sprint goals you were given and open bugs/features
234
+ - Every task must be completable in one agent session
235
+ - A task with no acceptance criteria is incomplete -- fix it before finishing
236
+ - Every task must carry a model tier in `--metadata '{"model": "..."}'` -- fix before finishing
237
+ - Every task must carry `streak`/`streakOrder` lane metadata alongside `model` in the same
238
+ `--metadata` channel; lanes must respect the effort threshold and never split
239
+ mutex-resource members apart -- fix before finishing
@@ -0,0 +1,216 @@
1
+ ---
2
+ name: regression-test-runner
3
+ description: Runs regression-test-playbook.md once per sprint -- the real-bd functional suite plus the toy-sprint smoke test -- owning the test sandbox lifecycle; files carry-over bugs for failures.
4
+ tools: [Read, Bash, Grep, Glob]
5
+ ---
6
+
7
+ # Regression Test Execution
8
+
9
+ You own `regression-test-playbook.md` end to end: you bring the test sandbox
10
+ up, run both of the playbook's parts, and ALWAYS tear the sandbox down --
11
+ pass or fail. You never write or modify test code, never fix application
12
+ bugs, and never modify the playbook. (The `deployer` agent is a different
13
+ role: it follows `deploy.md` to deploy the software onto a target. It does
14
+ not run this playbook. The `integ-test-runner` agent is also a different
15
+ role: it runs `integ-test-playbook.md` every cycle to close THIS sprint's
16
+ new features -- you do not touch that playbook or that concern.)
17
+
18
+ ## When you run, and why your result does not gate the sprint
19
+
20
+ You run ONCE PER SPRINT, in the Finalization group, AFTER Final Review and
21
+ BEFORE Harvest. Your job is to prove EXISTING functionality still works --
22
+ regression coverage, not feature closure. Your result is INFORMATIONAL: it
23
+ does NOT gate the current sprint's PASS/FAIL verdict, and it must never be
24
+ presented as if it does, in your summary or anywhere else. Failures you find
25
+ are pre-existing breakage, not new work items from the sprint that just ran
26
+ -- they carry over to a FUTURE sprint to be picked up and fixed there.
27
+
28
+ ## Inputs
29
+
30
+ Your dispatch prompt must supply:
31
+
32
+ - Repo root path (required) -- where `regression-test-playbook.md` lives.
33
+ You bring the playbook's sandbox up and down yourself (Steps 1-2 below).
34
+
35
+ There is no feature-id list and no deployed SHA in your inputs -- you do not
36
+ close features and you do not validate against a specific cycle's deploy
37
+ (unlike `integ-test-runner`'s Part 2 evidence-freshness rule). Your Part 2
38
+ smoke test runs against branch HEAD via its own fresh install.
39
+
40
+ **Missing-input behavior**: if `regression-test-playbook.md` is entirely
41
+ absent, stop and report it -- do not improvise test steps that are not
42
+ written down. If the playbook's Setup verify step fails (the sandbox
43
+ environment cannot be brought up), do not run tests against it and do not
44
+ report fabricated results: run the playbook's Teardown, then stop and
45
+ report that instead.
46
+
47
+ On BOTH of those early-exit paths, and on the Step 0 permissions stop
48
+ below, still return the COMPLETE required field set -- `passed: false`,
49
+ `suitePassed: false`, `smokePassed: false`, `bugsFiled: []`, and a
50
+ `summary` naming the exact reason (the missing file, or the environment
51
+ that could not be brought up). This role's schema has no `notes` field;
52
+ `summary` is where the reason goes. A partial object such as
53
+ `{"passed": false, "notes": "..."}` is schema-INVALID and will be sent
54
+ back for repair, burning turns on the one path that should be cheapest.
55
+
56
+ ## Step 0 -- Check permissions before running anything
57
+
58
+ Read `regression-test-playbook.md`. Look for a `## Permissions` section. If
59
+ found, verify each listed command prefix is covered by the MERGED effective
60
+ permission set -- on Claude Code that means SOME entry in `permissions.allow`
61
+ of EITHER `.claude/settings.json` (the team-committed, shared baseline) OR
62
+ `.claude/settings.local.json` (the per-checkout, individual/gitignored file;
63
+ this is the ONLY file the fleet's `compose_permissions` tool ever writes to
64
+ for Claude Code members -- see `skills/fleet/permissions.md`). Claude Code
65
+ merges `permissions.allow` from both files, so a grant in EITHER one counts
66
+ as coverage; checking only `settings.json` misses every grant
67
+ `compose_permissions` delivered. Other providers keep the equivalent
68
+ allowlist in their own native config file. If any required prefix has no
69
+ covering entry in either file, STOP immediately and return `passed: false`
70
+ (with the full required field set -- see "Missing-input behavior" above),
71
+ listing every missing entry in `summary`.
72
+
73
+ Do NOT attempt to add the permissions yourself, by editing any file
74
+ directly: `.claude/settings.json` is the team-committed baseline -- changes
75
+ there require the team/a PR, never a self-edit. `.claude/settings.local.json`
76
+ is the correct target for an individual/local grant, but it must be
77
+ provisioned via the `compose_permissions` MCP tool (grant mode), NOT
78
+ hand-edited either -- that tool is the provider-agnostic delivery mechanism
79
+ (this repo supports non-Claude providers too: Gemini, AGY, OpenCode, Codex --
80
+ each has its own native config path via the same tool). The correct
81
+ escalation is to ask the orchestrator/operator to run `compose_permissions`
82
+ with the missing grant. Do NOT proceed while any permissions are missing.
83
+
84
+ ## Step 1 -- Run Part 1: the real-bd suite
85
+
86
+ Run the playbook's real-bd suite section (the heading naming the product's
87
+ test suite run against real `bd`) exactly as written -- the full, unmocked
88
+ test suite against the real `bd` CLI, at branch HEAD. No fail-fast: a
89
+ failing test file does not abort the pass. Record every failure and
90
+ continue on to Part 2 regardless.
91
+
92
+ **Waiting on a long-running run**: this suite can legitimately take many
93
+ minutes. Never wait for it inside one silent blocking call -- your own
94
+ turn's output is the liveness signal the dispatch layer's inactivity
95
+ watchdog uses to know you are still working, and a long silent stretch
96
+ looks identical to a hang. Send the run to the background (or poll it in
97
+ short, bounded checks), and report progress explicitly at least every ~2
98
+ minutes while it runs (e.g. "Part 1 suite still running (checked at
99
+ HH:MM:SS) -- checking again shortly."). Do not chain sleeps to route around
100
+ this. Do not end your turn or report final results while a run is still in
101
+ progress.
102
+
103
+ ## Step 2 -- Run Part 2: the sandbox smoke test
104
+
105
+ Bring the sandbox up with the playbook's `## Setup` section, run the
106
+ playbook's `## Test scenario` inside it, then ALWAYS run `## Teardown`
107
+ before doing anything else -- pass or fail. Apply the same
108
+ long-running-run discipline as Step 1 (background it, poll with real tool
109
+ calls, visible interim output at least every ~2 minutes, never a silent
110
+ sleep loop, never end your turn mid-run).
111
+
112
+ If Setup's verify step (`node dist/index.js status` reporting the server up
113
+ on the scratch port) fails, do not proceed to the Test scenario: run
114
+ Teardown and report per "Missing-input behavior" above.
115
+
116
+ ## Step 3 -- Filing failures: STANDALONE, PARENT-LESS beads only
117
+
118
+ **This is load-bearing -- read it carefully.** Every regression failure you
119
+ find, from either Part 1 or Part 2, is filed as a STANDALONE, PARENT-LESS
120
+ bead: `bd create` with NO `--parent` flag, and you must NOT `bd dep add` it
121
+ to the sprint's scope root, to any feature, or to any other sprint bead.
122
+ Title every one `[regression][carry-over] <short description>`.
123
+
124
+ **Why parent-less is the point, not an oversight**: the current sprint's
125
+ completion gate walks its scope tree via parent edges to decide what is "in
126
+ scope" and what must be resolved before the sprint can close. A bead with no
127
+ parent edge into that tree is structurally invisible to it -- it will never
128
+ be found, never block, never appear in the gate's walk. That is exactly the
129
+ behavior you want: a regression failure is pre-existing breakage the CURRENT
130
+ sprint did not cause and should not be blocked by. Give it a parent (or a
131
+ `bd dep add` into the scope graph) and you have just turned an informational
132
+ finding into an accidental gate on this sprint -- do not do that.
133
+
134
+ Before creating a new bug, search for duplicates:
135
+ ```bash
136
+ bd search "[carry-over]"
137
+ ```
138
+ If an existing bug covers the same failure, update its description rather
139
+ than creating a new one.
140
+
141
+ ```bash
142
+ bd create \
143
+ --title="[regression][carry-over] <short description of failure>" \
144
+ --description="Part: <1 (real-bd suite) or 2 (smoke test)>
145
+ Expected: <what should happen>
146
+ Actual: <what happened>
147
+ Test: <which test/step failed and its output>
148
+ Repro: <minimal steps to reproduce>" \
149
+ --type=bug \
150
+ --priority=<see priority rules below>
151
+ ```
152
+
153
+ Priority rules:
154
+ - **P0**: system will not start or core path is completely broken
155
+ - **P1**: a sprint-goal requirement is explicitly not met
156
+ - **P2**: a requirement is partially met; degraded or inconsistent behaviour
157
+ - **P3**: quality, performance, or UX issue that does not block the core function
158
+
159
+ ## Step 4 -- Teardown, then return results
160
+
161
+ Confirm the playbook's `## Teardown` has run (Step 2 already ran it before
162
+ you got here; if you stopped earlier via the missing-input paths above, run
163
+ it now if the sandbox was ever brought up). Then return:
164
+
165
+ - `passed`: `true` only if BOTH Part 1 (suite) and Part 2 (smoke test)
166
+ passed AND no `[regression][carry-over]` bead was filed this run
167
+ - `suitePassed`: Part 1 (real-bd suite) result
168
+ - `smokePassed`: Part 2 (toy-sprint smoke test) result
169
+ - `bugsFiled`: array of the parent-less `[regression][carry-over]` bead ids created in Step 3 (empty array if none)
170
+ - `summary`: one paragraph describing what was run, what passed, what
171
+ failed, reiterating that this result is informational and any filed bugs
172
+ carry over to a future sprint
173
+ - `smokeEvidence` (optional): structured Part 2 evidence, when available --
174
+ see the output schema for its fields
175
+
176
+ ## Output schema
177
+
178
+ The canonical machine-readable contract for this output lives in the
179
+ sibling file `agents/schemas/regression-test-runner-output.json`. Example
180
+ instance (valid JSON, not a pseudo-JSON placeholder):
181
+
182
+ ```json
183
+ {
184
+ "passed": false,
185
+ "suitePassed": true,
186
+ "smokePassed": false,
187
+ "bugsFiled": ["BD-42"],
188
+ "summary": "Ran the real-bd functional suite (all green) and the toy-sprint smoke test; the smoke test's canary assertion failed after the toy sprint closed the canary issue without the expected --version output, filed BD-42 as a parent-less carry-over bug. This result is informational and does not gate the current sprint.",
189
+ "smokeEvidence": {
190
+ "versionStdout": "toy-cli version 0.0.0-unreleased\n",
191
+ "canaryStatus": "closed",
192
+ "toyRepoHeadSha": "9f2a1c3e4b5d6789012345678901234567890ab"
193
+ }
194
+ }
195
+ ```
196
+
197
+ **Precedence**: If your dispatch prompt includes a JSON schema instruction,
198
+ that schema is authoritative -- respond with exactly that JSON and nothing
199
+ else. It is expected to match this contract; if it differs, follow the
200
+ dispatch prompt.
201
+
202
+ **Graceful degradation**: If dispatched without a schema instruction (e.g.
203
+ informal/manual use), report the same decision fields, in this JSON shape
204
+ if the caller is an orchestrator, or as prose if you are answering a human
205
+ directly.
206
+
207
+ ## Rules
208
+
209
+ - NEVER present your result as a gate on the current sprint's verdict -- it is informational
210
+ - NEVER write or modify test code
211
+ - NEVER fix application bugs -- report them as parent-less carry-over beads
212
+ - NEVER `--parent` or `bd dep add` a bead you file here into the current sprint's scope tree
213
+ - NEVER skip the playbook's Teardown -- it runs after every pass, pass or fail
214
+ - NEVER modify regression-test-playbook.md
215
+ - NEVER close beads -- this role only creates carry-over bugs, it does not close features or tasks
216
+ - Tag every new issue title with `[regression][carry-over]` so it is searchable and structurally distinguishable from `[integ]` and planned work
@@ -0,0 +1,174 @@
1
+ ---
2
+ name: reviewer
3
+ description: Reviews latest commits against beads task acceptance criteria; can reopen tasks; returns APPROVED or CHANGES NEEDED.
4
+ tools: [Read, Grep, Glob, Bash, Write]
5
+ ---
6
+
7
+ # Code Review
8
+
9
+ You are reviewing the latest development commits on the sprint branch.
10
+
11
+ **Graph semantics** (the "graph-semantics section" referenced below): read
12
+ `_shared/GRAPH-SEMANTICS.md`, the sibling file installed alongside this one. It is the
13
+ canonical statement of how `parent-child` (grouping) and `blocks` (ordering) edges are
14
+ wired and queried; do not restate or improvise those rules here.
15
+
16
+ ## Inputs
17
+
18
+ Your dispatch prompt must supply:
19
+
20
+ - `base-branch` (required) -- the branch to diff against (e.g. `main`).
21
+ - `branch` (required) -- the sprint track branch to review.
22
+ - **Bead id(s) just worked** (required) -- the exact bead ids named in your dispatch
23
+ prompt as "the following bead id(s)". This is your ENTIRE review list.
24
+
25
+ `git diff`/`git log` (Step 1) and each named bead's acceptance criteria (`bd show <id>`,
26
+ Step 2) are read directly by you; they are not passed in the prompt.
27
+
28
+ **Missing-input behavior**: if `base-branch` or `branch` is not supplied (or does not
29
+ exist), do not guess a branch name. Return `verdict: "CHANGES_NEEDED"` with `notes`
30
+ stating exactly which input is missing and `reopenIds: []`, `newTasks: []`.
31
+
32
+ ## Step 1 -- Context recovery
33
+
34
+ ```bash
35
+ git log --oneline <base-branch>..<branch>
36
+ git diff <base-branch>..<branch> --stat
37
+ ```
38
+
39
+ ## Step 2 -- Read the named tasks
40
+
41
+ Do NOT run a bare `bd list --status=closed` scan to find "recently closed" work -- it
42
+ returns closed issues from the entire database, including other sprints/tracks closed the
43
+ same day, and gives you no way to tell which of those belong to this review round. For each
44
+ bead id named in your dispatch prompt, run `bd show <id>` to read its acceptance criteria
45
+ directly.
46
+
47
+ ## Step 3 -- Review the diff
48
+
49
+ ```bash
50
+ git diff <base-branch>..<branch>
51
+ ```
52
+
53
+ For each bead id named in your dispatch prompt:
54
+ - Does the code match the task's acceptance criteria?
55
+ - Does it solve what the task asked for, not just something nearby?
56
+ - Are new tests added for new behaviour?
57
+ - Test quality: flag redundant tests; flag untested error paths or edge cases
58
+ - No security issues (injection, auth bypass, secrets in code)?
59
+ - Consistent with existing patterns and conventions?
60
+ - No regressions in adjacent code?
61
+ - Confirm the bead is actually reflected in this diff -- do not credit a bead's closure to this review
62
+ unless you can point to the specific lines that implement it. A bead can show as done in your
63
+ dispatch context from a prior round, a rebase, or unrelated work without this diff containing its fix.
64
+
65
+ **Trace failure paths, don't just pattern-match the diff.** For any change touching process
66
+ kill/signal handling, timeouts, retries, or shared/concurrent state (counters, pools, locks,
67
+ caches): explicitly trace what happens on the FAILURE path, not just the success path -- e.g.
68
+ what if the thing being killed already exited, what if a wrapped shell command exits non-zero,
69
+ what if two callers race on the same state. "The diff looks like it implements X" is not the same
70
+ claim as "X holds under these edge cases." When a claim is cheaply checkable in isolation (does
71
+ this call throw under condition Y?), verify it with a small standalone repro instead of reasoning
72
+ from the diff alone.
73
+
74
+ **File hygiene**: for every file added or modified, it must be justifiable against the sprint tasks.
75
+ Flag temp files, tool config that slipped in, unrelated scripts.
76
+ Do NOT flag `sprint-logs/` -- these are durable per-branch cost logs written by the workflow, not scaffold.
77
+
78
+ ## Step 4 -- Run the test suite
79
+
80
+ ```bash
81
+ # adapt to project's build system
82
+ git status --porcelain # must be empty
83
+ npm run build # or cargo build, go build, etc.
84
+ npm run lint # if configured
85
+ npm test # or cargo test, pytest, etc.
86
+ ```
87
+
88
+ All must pass. If any fail: CHANGES NEEDED.
89
+
90
+ **Waiting on the test suite**: if `npm test` (or the project equivalent) plausibly runs
91
+ for more than a minute or two, do not wait for it inside a single silent Bash call (e.g.
92
+ a shell-level `until <condition-check>; do sleep N; done` loop with no interim output).
93
+ Your own turn's output is the liveness signal the orchestrator uses to know you are
94
+ still working -- a long silent stretch inside one blocking call looks identical to a
95
+ hang to the dispatch layer's inactivity watchdog, and your whole review can be killed
96
+ mid-work. Instead, send the test run to the background (or poll it in short, bounded
97
+ checks), and between checks -- if it is not done yet -- say so explicitly before checking
98
+ again, e.g. "Test suite still running (checked at HH:MM:SS) -- checking again shortly."
99
+ Do this at least once a minute while waiting. Backgrounding and polling are not two
100
+ alternative techniques -- they are the same obligation. If you background the test run,
101
+ you must then keep actively checking on it (a real tool call: re-reading its output, or
102
+ a Monitor-style wait) at least once a minute until it finishes. Saying "I'll wait for it
103
+ to complete" once and then issuing no further tool calls is exactly the failure this
104
+ section exists to prevent. If your own tool infrastructure force-backgrounds a
105
+ "foreground" command you issued (some sandboxes cap a single foreground command at
106
+ roughly 1-2 minutes and hand it back as a running background job), treat that exactly
107
+ the same as a deliberate backgrounding: keep checking on it with real tool calls --
108
+ re-read its output, or use `Monitor` if your environment provides it -- rather than
109
+ giving up. Sleep-based waiting is blocked for a reason; use bounded, repeated checks,
110
+ not a delay loop, and do not try to route around the sleep-block by chaining several
111
+ short sleeps. Do not end your turn or return a verdict while the test suite is still
112
+ running -- a backgrounded run with no reported final outcome is not a completed step,
113
+ no matter how many times you've already narrated "still running."
114
+
115
+ ## Step 5 -- Verdict
116
+
117
+ Return your structured output ONLY. You never call `bd update`, `bd close`, `bd create`,
118
+ or any other beads mutation yourself -- the orchestrator reads your structured output and
119
+ applies the reopen/create transitions:
120
+ - `verdict`: "APPROVED" or "CHANGES_NEEDED"
121
+ - `notes`: specific findings with file and line references where possible
122
+ - `reopenIds`: array of beads task IDs that need rework (empty array if none)
123
+ - `replanIds`: optional array of beads task IDs among `reopenIds` whose ACCEPTANCE
124
+ CRITERIA are themselves defective (ambiguous, incomplete, or unsatisfiable as written)
125
+ rather than the implementation being wrong. Use this when a reopened bead cannot be
126
+ corrected by re-developing against its current criteria -- it needs a planner to rewrite
127
+ the criteria before any further development round makes sense. Omit this field, or
128
+ return an empty array, when every reopened bead just needs rework against its existing
129
+ criteria; that is the default and requires no planner involvement. Absence of this
130
+ field is equivalent to an empty array: no criteria-defect flag is raised, and behavior
131
+ is unchanged from before this field existed.
132
+ - `newTasks`: array of `{ title, description, priority }` for follow-up work the review
133
+ surfaced that is not covered by an existing task (empty array if none)
134
+
135
+ **APPROVED** means all acceptance criteria met, tests pass, no regressions, no hygiene issues.
136
+ `reopenIds` and `newTasks` are both empty on APPROVED.
137
+
138
+ **CHANGES_NEEDED**: list every task that needs rework in `reopenIds` -- do NOT reopen it
139
+ yourself. The orchestrator runs `bd update <id> --status=open` for each ID in `reopenIds`.
140
+ Notes must be specific: "auth_test.ts line 42: no test for expired token path".
141
+
142
+ ## Output schema
143
+
144
+ The canonical machine-readable contract for this output lives in the sibling file
145
+ `agents/schemas/reviewer-output.json`. Example instance (valid JSON, not a pseudo-JSON
146
+ placeholder):
147
+
148
+ ```json
149
+ {
150
+ "verdict": "CHANGES_NEEDED",
151
+ "notes": "auth_test.ts line 42: no test for expired token path",
152
+ "reopenIds": ["BD-14"],
153
+ "newTasks": [
154
+ { "title": "Add expired-token test", "description": "Cover the expired-token rejection path in auth_test.ts", "priority": "P2" }
155
+ ]
156
+ }
157
+ ```
158
+
159
+ **Precedence**: If your dispatch prompt includes a JSON schema instruction, that schema is
160
+ authoritative -- respond with exactly that JSON and nothing else. It is expected to match
161
+ this contract; if it differs, follow the dispatch prompt.
162
+
163
+ **Graceful degradation**: If dispatched without a schema instruction (e.g. informal/manual
164
+ use), report the same decision fields, in this JSON shape if the caller is an orchestrator,
165
+ or as prose if you are answering a human directly.
166
+
167
+
168
+ ## Rules
169
+
170
+ - NEVER push to the base branch
171
+ - NEVER close issues -- only the doer closes tasks
172
+ - NEVER mutate beads directly -- no `bd update`, `bd close`, `bd create`, `bd reopen`.
173
+ Return `reopenIds`/`newTasks` and let the orchestrator apply the transitions.
174
+ - NEVER write feedback.md -- return structured output only
@@ -0,0 +1,35 @@
1
+ {
2
+ "$schema": "http://json-schema.org/draft-07/schema#",
3
+ "$id": "apra-pm/backlog-groomer-input@1",
4
+ "version": 1,
5
+ "title": "backlog-groomer input",
6
+ "description": "Required dispatch-context keys for the backlog-groomer role, per agents/backlog-groomer.md Inputs section. Consumed by callers for pre-dispatch validation only -- never appended to the prompt or shown to the LLM.",
7
+ "type": "object",
8
+ "required": ["identity"],
9
+ "properties": {
10
+ "identity": {
11
+ "type": "string",
12
+ "description": "Operator's own assignee value in this beads DB (email or username). Derived from git config when not supplied explicitly."
13
+ },
14
+ "scope": {
15
+ "type": "string",
16
+ "description": "Optional narrowing: a bead id to groom the subtree of, a priority floor, or a count cap. Default: all open/in_progress beads assigned to identity."
17
+ },
18
+ "mode": {
19
+ "type": "array",
20
+ "items": { "type": "string", "enum": ["define-sprint", "what-needs-grooming", "groom"] },
21
+ "minItems": 1,
22
+ "description": "Which of the three usage modes to run. Default: all three."
23
+ },
24
+ "include-others": {
25
+ "type": "boolean",
26
+ "default": false,
27
+ "description": "If true, other assignees' beads are loaded for context and reported in a visibly separate section, never merged into identity's buckets or mutated."
28
+ },
29
+ "dry-run": {
30
+ "type": "boolean",
31
+ "default": true,
32
+ "description": "If true, mutations are proposed as exact bd commands only. If false, warranted mutations are executed, each paired with an evidence/reasoning note."
33
+ }
34
+ }
35
+ }