@apralabs/apra-fleet 0.4.0 → 0.4.2

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 (548) hide show
  1. package/README.md +159 -13
  2. package/dist/agents/backlog-groomer.md +31 -19
  3. package/dist/agents/ci-watcher.md +16 -1
  4. package/dist/agents/deployer.md +37 -47
  5. package/dist/agents/doer.md +147 -114
  6. package/dist/agents/harvester.md +41 -34
  7. package/dist/agents/integ-test-runner.md +98 -114
  8. package/dist/agents/kb-reconciler.md +205 -0
  9. package/dist/agents/plan-reviewer.md +45 -44
  10. package/dist/agents/planner.md +121 -50
  11. package/dist/agents/regression-test-runner.md +84 -81
  12. package/dist/agents/reviewer.md +118 -44
  13. package/dist/agents/schemas/doer-output.json +63 -3
  14. package/dist/agents/schemas/harvester-output.json +59 -2
  15. package/dist/agents/schemas/integ-test-runner-output.json +3 -3
  16. package/dist/agents/schemas/kb-reconciler-output.json +87 -0
  17. package/dist/agents/schemas/planner-output.json +65 -0
  18. package/dist/agents/schemas/regression-test-runner-output.json +4 -17
  19. package/dist/agents/schemas/reviewer-output.json +105 -8
  20. package/dist/cli/auth.d.ts.map +1 -1
  21. package/dist/cli/auth.js +1 -2
  22. package/dist/cli/auth.js.map +1 -1
  23. package/dist/cli/config.d.ts +3 -3
  24. package/dist/cli/config.d.ts.map +1 -1
  25. package/dist/cli/config.js +4 -13
  26. package/dist/cli/config.js.map +1 -1
  27. package/dist/cli/install.d.ts +1 -0
  28. package/dist/cli/install.d.ts.map +1 -1
  29. package/dist/cli/install.js +141 -44
  30. package/dist/cli/install.js.map +1 -1
  31. package/dist/cli/join.js +1 -1
  32. package/dist/cli/join.js.map +1 -1
  33. package/dist/cli/kb-commit.d.ts +12 -0
  34. package/dist/cli/kb-commit.d.ts.map +1 -0
  35. package/dist/cli/kb-commit.js +53 -0
  36. package/dist/cli/kb-commit.js.map +1 -0
  37. package/dist/cli/kb-directives.d.ts +17 -0
  38. package/dist/cli/kb-directives.d.ts.map +1 -0
  39. package/dist/cli/kb-directives.js +146 -0
  40. package/dist/cli/kb-directives.js.map +1 -0
  41. package/dist/cli/kb-import.d.ts +13 -0
  42. package/dist/cli/kb-import.d.ts.map +1 -0
  43. package/dist/cli/kb-import.js +56 -0
  44. package/dist/cli/kb-import.js.map +1 -0
  45. package/dist/cli/register-member.js +1 -1
  46. package/dist/cli/start.d.ts.map +1 -1
  47. package/dist/cli/start.js +7 -0
  48. package/dist/cli/start.js.map +1 -1
  49. package/dist/cli/uninstall.d.ts.map +1 -1
  50. package/dist/cli/uninstall.js +16 -3
  51. package/dist/cli/uninstall.js.map +1 -1
  52. package/dist/cli/watch.d.ts +76 -4
  53. package/dist/cli/watch.d.ts.map +1 -1
  54. package/dist/cli/watch.js +150 -17
  55. package/dist/cli/watch.js.map +1 -1
  56. package/dist/commands/kb-server.d.ts +8 -0
  57. package/dist/commands/kb-server.d.ts.map +1 -0
  58. package/dist/commands/kb-server.js +221 -0
  59. package/dist/commands/kb-server.js.map +1 -0
  60. package/dist/index.js +77 -2
  61. package/dist/index.js.map +1 -1
  62. package/dist/os/git-bash-candidates.d.ts +35 -0
  63. package/dist/os/git-bash-candidates.d.ts.map +1 -0
  64. package/dist/os/git-bash-candidates.js +46 -0
  65. package/dist/os/git-bash-candidates.js.map +1 -0
  66. package/dist/os/index.d.ts +13 -4
  67. package/dist/os/index.d.ts.map +1 -1
  68. package/dist/os/index.js +17 -2
  69. package/dist/os/index.js.map +1 -1
  70. package/dist/os/linux.d.ts +1 -0
  71. package/dist/os/linux.d.ts.map +1 -1
  72. package/dist/os/linux.js +19 -2
  73. package/dist/os/linux.js.map +1 -1
  74. package/dist/os/os-commands.d.ts +12 -0
  75. package/dist/os/os-commands.d.ts.map +1 -1
  76. package/dist/os/os-commands.js.map +1 -1
  77. package/dist/os/windows-gitbash.d.ts +93 -0
  78. package/dist/os/windows-gitbash.d.ts.map +1 -0
  79. package/dist/os/windows-gitbash.js +244 -0
  80. package/dist/os/windows-gitbash.js.map +1 -0
  81. package/dist/os/windows.d.ts +35 -0
  82. package/dist/os/windows.d.ts.map +1 -1
  83. package/dist/os/windows.js +93 -35
  84. package/dist/os/windows.js.map +1 -1
  85. package/dist/providers/agy.d.ts +15 -3
  86. package/dist/providers/agy.d.ts.map +1 -1
  87. package/dist/providers/agy.js +145 -11
  88. package/dist/providers/agy.js.map +1 -1
  89. package/dist/providers/claude.d.ts +14 -3
  90. package/dist/providers/claude.d.ts.map +1 -1
  91. package/dist/providers/claude.js +69 -22
  92. package/dist/providers/claude.js.map +1 -1
  93. package/dist/providers/codex.d.ts +14 -3
  94. package/dist/providers/codex.d.ts.map +1 -1
  95. package/dist/providers/codex.js +34 -8
  96. package/dist/providers/codex.js.map +1 -1
  97. package/dist/providers/copilot.d.ts +14 -3
  98. package/dist/providers/copilot.d.ts.map +1 -1
  99. package/dist/providers/copilot.js +33 -8
  100. package/dist/providers/copilot.js.map +1 -1
  101. package/dist/providers/email/headers.d.ts +15 -0
  102. package/dist/providers/email/headers.d.ts.map +1 -0
  103. package/dist/providers/email/headers.js +42 -0
  104. package/dist/providers/email/headers.js.map +1 -0
  105. package/dist/providers/email/index.d.ts +18 -0
  106. package/dist/providers/email/index.d.ts.map +1 -0
  107. package/dist/providers/email/index.js +60 -0
  108. package/dist/providers/email/index.js.map +1 -0
  109. package/dist/providers/email/provider.d.ts +49 -0
  110. package/dist/providers/email/provider.d.ts.map +1 -0
  111. package/dist/providers/email/provider.js +2 -0
  112. package/dist/providers/email/provider.js.map +1 -0
  113. package/dist/providers/email/sendgrid.d.ts +12 -0
  114. package/dist/providers/email/sendgrid.d.ts.map +1 -0
  115. package/dist/providers/email/sendgrid.js +67 -0
  116. package/dist/providers/email/sendgrid.js.map +1 -0
  117. package/dist/providers/email/smtp.d.ts +65 -0
  118. package/dist/providers/email/smtp.d.ts.map +1 -0
  119. package/dist/providers/email/smtp.js +373 -0
  120. package/dist/providers/email/smtp.js.map +1 -0
  121. package/dist/providers/index.d.ts +0 -1
  122. package/dist/providers/index.d.ts.map +1 -1
  123. package/dist/providers/index.js +0 -3
  124. package/dist/providers/index.js.map +1 -1
  125. package/dist/providers/none.d.ts +14 -3
  126. package/dist/providers/none.d.ts.map +1 -1
  127. package/dist/providers/none.js +26 -2
  128. package/dist/providers/none.js.map +1 -1
  129. package/dist/providers/opencode.d.ts +14 -3
  130. package/dist/providers/opencode.d.ts.map +1 -1
  131. package/dist/providers/opencode.js +60 -6
  132. package/dist/providers/opencode.js.map +1 -1
  133. package/dist/providers/provider.d.ts +91 -5
  134. package/dist/providers/provider.d.ts.map +1 -1
  135. package/dist/providers/provider.js +45 -1
  136. package/dist/providers/provider.js.map +1 -1
  137. package/dist/services/agent-provisioner.d.ts.map +1 -1
  138. package/dist/services/agent-provisioner.js +5 -8
  139. package/dist/services/agent-provisioner.js.map +1 -1
  140. package/dist/services/cloud/activity.js +2 -2
  141. package/dist/services/cloud/activity.js.map +1 -1
  142. package/dist/services/cloud/lifecycle.d.ts.map +1 -1
  143. package/dist/services/cloud/lifecycle.js +3 -0
  144. package/dist/services/cloud/lifecycle.js.map +1 -1
  145. package/dist/services/cloud/task-wrapper.d.ts +18 -0
  146. package/dist/services/cloud/task-wrapper.d.ts.map +1 -1
  147. package/dist/services/cloud/task-wrapper.js +157 -0
  148. package/dist/services/cloud/task-wrapper.js.map +1 -1
  149. package/dist/services/context-admission.d.ts.map +1 -1
  150. package/dist/services/context-admission.js +9 -7
  151. package/dist/services/context-admission.js.map +1 -1
  152. package/dist/services/credential-cleanup.d.ts.map +1 -1
  153. package/dist/services/credential-cleanup.js +22 -3
  154. package/dist/services/credential-cleanup.js.map +1 -1
  155. package/dist/services/github-app.d.ts.map +1 -1
  156. package/dist/services/github-app.js +11 -2
  157. package/dist/services/github-app.js.map +1 -1
  158. package/dist/services/knowledge/audn.d.ts +37 -0
  159. package/dist/services/knowledge/audn.d.ts.map +1 -0
  160. package/dist/services/knowledge/audn.js +219 -0
  161. package/dist/services/knowledge/audn.js.map +1 -0
  162. package/dist/services/knowledge/file-hash.d.ts +11 -0
  163. package/dist/services/knowledge/file-hash.d.ts.map +1 -0
  164. package/dist/services/knowledge/file-hash.js +123 -0
  165. package/dist/services/knowledge/file-hash.js.map +1 -0
  166. package/dist/services/knowledge/http-provider.d.ts +46 -0
  167. package/dist/services/knowledge/http-provider.d.ts.map +1 -0
  168. package/dist/services/knowledge/http-provider.js +254 -0
  169. package/dist/services/knowledge/http-provider.js.map +1 -0
  170. package/dist/services/knowledge/kb-providers.d.ts +15 -0
  171. package/dist/services/knowledge/kb-providers.d.ts.map +1 -0
  172. package/dist/services/knowledge/kb-providers.js +92 -0
  173. package/dist/services/knowledge/kb-providers.js.map +1 -0
  174. package/dist/services/knowledge/kb-scope-input.d.ts +5 -0
  175. package/dist/services/knowledge/kb-scope-input.d.ts.map +1 -0
  176. package/dist/services/knowledge/kb-scope-input.js +11 -0
  177. package/dist/services/knowledge/kb-scope-input.js.map +1 -0
  178. package/dist/services/knowledge/kb-service.d.ts +3 -0
  179. package/dist/services/knowledge/kb-service.d.ts.map +1 -0
  180. package/dist/services/knowledge/kb-service.js +2 -0
  181. package/dist/services/knowledge/kb-service.js.map +1 -0
  182. package/dist/services/knowledge/path-validation.d.ts +2 -0
  183. package/dist/services/knowledge/path-validation.d.ts.map +1 -0
  184. package/dist/services/knowledge/path-validation.js +13 -0
  185. package/dist/services/knowledge/path-validation.js.map +1 -0
  186. package/dist/services/knowledge/pre-init.d.ts +14 -0
  187. package/dist/services/knowledge/pre-init.d.ts.map +1 -0
  188. package/dist/services/knowledge/pre-init.js +147 -0
  189. package/dist/services/knowledge/pre-init.js.map +1 -0
  190. package/dist/services/knowledge/project-slug.d.ts +2 -0
  191. package/dist/services/knowledge/project-slug.d.ts.map +1 -0
  192. package/dist/services/knowledge/project-slug.js +49 -0
  193. package/dist/services/knowledge/project-slug.js.map +1 -0
  194. package/dist/services/knowledge/sqlite-provider.d.ts +147 -0
  195. package/dist/services/knowledge/sqlite-provider.d.ts.map +1 -0
  196. package/dist/services/knowledge/sqlite-provider.js +1646 -0
  197. package/dist/services/knowledge/sqlite-provider.js.map +1 -0
  198. package/dist/services/knowledge/types.d.ts +163 -0
  199. package/dist/services/knowledge/types.d.ts.map +1 -0
  200. package/dist/services/knowledge/types.js +9 -0
  201. package/dist/services/knowledge/types.js.map +1 -0
  202. package/dist/services/member-home.d.ts +89 -0
  203. package/dist/services/member-home.d.ts.map +1 -0
  204. package/dist/services/member-home.js +259 -0
  205. package/dist/services/member-home.js.map +1 -0
  206. package/dist/services/member-remote-url.d.ts +34 -0
  207. package/dist/services/member-remote-url.d.ts.map +1 -0
  208. package/dist/services/member-remote-url.js +39 -0
  209. package/dist/services/member-remote-url.js.map +1 -0
  210. package/dist/services/model-pricing.d.ts.map +1 -1
  211. package/dist/services/model-pricing.js +0 -5
  212. package/dist/services/model-pricing.js.map +1 -1
  213. package/dist/services/orphan-recovery.d.ts +9 -3
  214. package/dist/services/orphan-recovery.d.ts.map +1 -1
  215. package/dist/services/orphan-recovery.js +22 -8
  216. package/dist/services/orphan-recovery.js.map +1 -1
  217. package/dist/services/preflight-check.d.ts +56 -0
  218. package/dist/services/preflight-check.d.ts.map +1 -0
  219. package/dist/services/preflight-check.js +277 -0
  220. package/dist/services/preflight-check.js.map +1 -0
  221. package/dist/services/shell-probe.d.ts +131 -0
  222. package/dist/services/shell-probe.d.ts.map +1 -0
  223. package/dist/services/shell-probe.js +210 -0
  224. package/dist/services/shell-probe.js.map +1 -0
  225. package/dist/services/singleton.d.ts +2 -0
  226. package/dist/services/singleton.d.ts.map +1 -1
  227. package/dist/services/singleton.js +1 -1
  228. package/dist/services/singleton.js.map +1 -1
  229. package/dist/services/ssh.js +2 -2
  230. package/dist/services/ssh.js.map +1 -1
  231. package/dist/services/stall/find-log-file.d.ts.map +1 -1
  232. package/dist/services/stall/find-log-file.js +22 -16
  233. package/dist/services/stall/find-log-file.js.map +1 -1
  234. package/dist/services/stall/log-path-resolver.d.ts +11 -8
  235. package/dist/services/stall/log-path-resolver.d.ts.map +1 -1
  236. package/dist/services/stall/log-path-resolver.js +17 -40
  237. package/dist/services/stall/log-path-resolver.js.map +1 -1
  238. package/dist/services/stall/read-log-tail.d.ts.map +1 -1
  239. package/dist/services/stall/read-log-tail.js +6 -5
  240. package/dist/services/stall/read-log-tail.js.map +1 -1
  241. package/dist/services/stall/stall-detector.d.ts +32 -0
  242. package/dist/services/stall/stall-detector.d.ts.map +1 -1
  243. package/dist/services/stall/stall-detector.js +149 -6
  244. package/dist/services/stall/stall-detector.js.map +1 -1
  245. package/dist/services/stall/stall-poller.d.ts +34 -0
  246. package/dist/services/stall/stall-poller.d.ts.map +1 -1
  247. package/dist/services/stall/stall-poller.js +160 -35
  248. package/dist/services/stall/stall-poller.js.map +1 -1
  249. package/dist/services/strategy.d.ts +9 -0
  250. package/dist/services/strategy.d.ts.map +1 -1
  251. package/dist/services/strategy.js +41 -7
  252. package/dist/services/strategy.js.map +1 -1
  253. package/dist/services/tool-registry.d.ts.map +1 -1
  254. package/dist/services/tool-registry.js +87 -1
  255. package/dist/services/tool-registry.js.map +1 -1
  256. package/dist/services/user-config.js +1 -1
  257. package/dist/services/user-config.js.map +1 -1
  258. package/dist/services/vcs/azure-devops.d.ts +1 -1
  259. package/dist/services/vcs/azure-devops.d.ts.map +1 -1
  260. package/dist/services/vcs/azure-devops.js +105 -10
  261. package/dist/services/vcs/azure-devops.js.map +1 -1
  262. package/dist/services/vcs/bitbucket.d.ts.map +1 -1
  263. package/dist/services/vcs/bitbucket.js +16 -0
  264. package/dist/services/vcs/bitbucket.js.map +1 -1
  265. package/dist/services/vcs/github.d.ts.map +1 -1
  266. package/dist/services/vcs/github.js +56 -1
  267. package/dist/services/vcs/github.js.map +1 -1
  268. package/dist/services/vcs/types.d.ts +123 -2
  269. package/dist/services/vcs/types.d.ts.map +1 -1
  270. package/dist/services/version-check.d.ts +22 -0
  271. package/dist/services/version-check.d.ts.map +1 -0
  272. package/dist/services/version-check.js +103 -0
  273. package/dist/services/version-check.js.map +1 -0
  274. package/dist/skills/fleet-sprint-cli/SKILL.md +15 -3
  275. package/dist/skills/pm/SKILL.md +0 -1
  276. package/dist/skills/pm/beads.md +6 -0
  277. package/dist/skills/pm/cost.md +0 -1
  278. package/dist/skills/pm/fleet-addendum.md +6 -1
  279. package/dist/skills/pm/index.md +56 -0
  280. package/dist/skills/pm/kb-reconcile.md +132 -0
  281. package/dist/skills/pm/kb-review.md +109 -0
  282. package/dist/tools/check-status.d.ts +47 -0
  283. package/dist/tools/check-status.d.ts.map +1 -1
  284. package/dist/tools/check-status.js +245 -3
  285. package/dist/tools/check-status.js.map +1 -1
  286. package/dist/tools/child-id-allocator.d.ts +2 -2
  287. package/dist/tools/cloud-control.js +2 -2
  288. package/dist/tools/cloud-control.js.map +1 -1
  289. package/dist/tools/code-intelligence-codebase-memory.d.ts +11 -0
  290. package/dist/tools/code-intelligence-codebase-memory.d.ts.map +1 -0
  291. package/dist/tools/code-intelligence-codebase-memory.js +270 -0
  292. package/dist/tools/code-intelligence-codebase-memory.js.map +1 -0
  293. package/dist/tools/code-intelligence-freshness.d.ts +2 -0
  294. package/dist/tools/code-intelligence-freshness.d.ts.map +1 -0
  295. package/dist/tools/code-intelligence-freshness.js +26 -0
  296. package/dist/tools/code-intelligence-freshness.js.map +1 -0
  297. package/dist/tools/code-intelligence-gitnexus.d.ts +14 -0
  298. package/dist/tools/code-intelligence-gitnexus.d.ts.map +1 -0
  299. package/dist/tools/code-intelligence-gitnexus.js +475 -0
  300. package/dist/tools/code-intelligence-gitnexus.js.map +1 -0
  301. package/dist/tools/code-intelligence-kb-enrich.d.ts +2 -0
  302. package/dist/tools/code-intelligence-kb-enrich.d.ts.map +1 -0
  303. package/dist/tools/code-intelligence-kb-enrich.js +65 -0
  304. package/dist/tools/code-intelligence-kb-enrich.js.map +1 -0
  305. package/dist/tools/code-intelligence-reindex.d.ts +7 -0
  306. package/dist/tools/code-intelligence-reindex.d.ts.map +1 -0
  307. package/dist/tools/code-intelligence-reindex.js +106 -0
  308. package/dist/tools/code-intelligence-reindex.js.map +1 -0
  309. package/dist/tools/code-intelligence-telemetry.d.ts +5 -0
  310. package/dist/tools/code-intelligence-telemetry.d.ts.map +1 -0
  311. package/dist/tools/code-intelligence-telemetry.js +52 -0
  312. package/dist/tools/code-intelligence-telemetry.js.map +1 -0
  313. package/dist/tools/code-intelligence-tests.d.ts +2 -0
  314. package/dist/tools/code-intelligence-tests.d.ts.map +1 -0
  315. package/dist/tools/code-intelligence-tests.js +24 -0
  316. package/dist/tools/code-intelligence-tests.js.map +1 -0
  317. package/dist/tools/code-intelligence.d.ts +114 -0
  318. package/dist/tools/code-intelligence.d.ts.map +1 -0
  319. package/dist/tools/code-intelligence.js +124 -0
  320. package/dist/tools/code-intelligence.js.map +1 -0
  321. package/dist/tools/compose-permissions.d.ts +26 -0
  322. package/dist/tools/compose-permissions.d.ts.map +1 -1
  323. package/dist/tools/compose-permissions.js +257 -33
  324. package/dist/tools/compose-permissions.js.map +1 -1
  325. package/dist/tools/execute-command.d.ts +2 -0
  326. package/dist/tools/execute-command.d.ts.map +1 -1
  327. package/dist/tools/execute-command.js +114 -28
  328. package/dist/tools/execute-command.js.map +1 -1
  329. package/dist/tools/execute-prompt.d.ts +13 -1
  330. package/dist/tools/execute-prompt.d.ts.map +1 -1
  331. package/dist/tools/execute-prompt.js +310 -61
  332. package/dist/tools/execute-prompt.js.map +1 -1
  333. package/dist/tools/kb-capture.d.ts +53 -0
  334. package/dist/tools/kb-capture.d.ts.map +1 -0
  335. package/dist/tools/kb-capture.js +130 -0
  336. package/dist/tools/kb-capture.js.map +1 -0
  337. package/dist/tools/kb-context.d.ts +17 -0
  338. package/dist/tools/kb-context.d.ts.map +1 -0
  339. package/dist/tools/kb-context.js +29 -0
  340. package/dist/tools/kb-context.js.map +1 -0
  341. package/dist/tools/kb-export.d.ts +19 -0
  342. package/dist/tools/kb-export.d.ts.map +1 -0
  343. package/dist/tools/kb-export.js +344 -0
  344. package/dist/tools/kb-export.js.map +1 -0
  345. package/dist/tools/kb-feedback.d.ts +23 -0
  346. package/dist/tools/kb-feedback.d.ts.map +1 -0
  347. package/dist/tools/kb-feedback.js +43 -0
  348. package/dist/tools/kb-feedback.js.map +1 -0
  349. package/dist/tools/kb-freshness-sweep.d.ts +14 -0
  350. package/dist/tools/kb-freshness-sweep.d.ts.map +1 -0
  351. package/dist/tools/kb-freshness-sweep.js +29 -0
  352. package/dist/tools/kb-freshness-sweep.js.map +1 -0
  353. package/dist/tools/kb-harvest.d.ts +20 -0
  354. package/dist/tools/kb-harvest.d.ts.map +1 -0
  355. package/dist/tools/kb-harvest.js +143 -0
  356. package/dist/tools/kb-harvest.js.map +1 -0
  357. package/dist/tools/kb-import.d.ts +44 -0
  358. package/dist/tools/kb-import.d.ts.map +1 -0
  359. package/dist/tools/kb-import.js +239 -0
  360. package/dist/tools/kb-import.js.map +1 -0
  361. package/dist/tools/kb-invalidate.d.ts +19 -0
  362. package/dist/tools/kb-invalidate.d.ts.map +1 -0
  363. package/dist/tools/kb-invalidate.js +34 -0
  364. package/dist/tools/kb-invalidate.js.map +1 -0
  365. package/dist/tools/kb-list.d.ts +32 -0
  366. package/dist/tools/kb-list.d.ts.map +1 -0
  367. package/dist/tools/kb-list.js +43 -0
  368. package/dist/tools/kb-list.js.map +1 -0
  369. package/dist/tools/kb-promote.d.ts +20 -0
  370. package/dist/tools/kb-promote.d.ts.map +1 -0
  371. package/dist/tools/kb-promote.js +20 -0
  372. package/dist/tools/kb-promote.js.map +1 -0
  373. package/dist/tools/kb-query.d.ts +35 -0
  374. package/dist/tools/kb-query.d.ts.map +1 -0
  375. package/dist/tools/kb-query.js +111 -0
  376. package/dist/tools/kb-query.js.map +1 -0
  377. package/dist/tools/kb-reconcile-prefilter.d.ts +14 -0
  378. package/dist/tools/kb-reconcile-prefilter.d.ts.map +1 -0
  379. package/dist/tools/kb-reconcile-prefilter.js +26 -0
  380. package/dist/tools/kb-reconcile-prefilter.js.map +1 -0
  381. package/dist/tools/kb-resolve-contradiction.d.ts +23 -0
  382. package/dist/tools/kb-resolve-contradiction.d.ts.map +1 -0
  383. package/dist/tools/kb-resolve-contradiction.js +37 -0
  384. package/dist/tools/kb-resolve-contradiction.js.map +1 -0
  385. package/dist/tools/kb-session-prime.d.ts +26 -0
  386. package/dist/tools/kb-session-prime.d.ts.map +1 -0
  387. package/dist/tools/kb-session-prime.js +392 -0
  388. package/dist/tools/kb-session-prime.js.map +1 -0
  389. package/dist/tools/kb-setup.d.ts +20 -0
  390. package/dist/tools/kb-setup.d.ts.map +1 -0
  391. package/dist/tools/kb-setup.js +49 -0
  392. package/dist/tools/kb-setup.js.map +1 -0
  393. package/dist/tools/kb-stats.d.ts +20 -0
  394. package/dist/tools/kb-stats.d.ts.map +1 -0
  395. package/dist/tools/kb-stats.js +115 -0
  396. package/dist/tools/kb-stats.js.map +1 -0
  397. package/dist/tools/list-members.d.ts.map +1 -1
  398. package/dist/tools/list-members.js +6 -2
  399. package/dist/tools/list-members.js.map +1 -1
  400. package/dist/tools/member-detail.d.ts.map +1 -1
  401. package/dist/tools/member-detail.js +13 -3
  402. package/dist/tools/member-detail.js.map +1 -1
  403. package/dist/tools/member-reservation.d.ts.map +1 -1
  404. package/dist/tools/member-reservation.js +13 -1
  405. package/dist/tools/member-reservation.js.map +1 -1
  406. package/dist/tools/monitor-task.d.ts.map +1 -1
  407. package/dist/tools/monitor-task.js +38 -5
  408. package/dist/tools/monitor-task.js.map +1 -1
  409. package/dist/tools/provision-auth.d.ts.map +1 -1
  410. package/dist/tools/provision-auth.js +15 -8
  411. package/dist/tools/provision-auth.js.map +1 -1
  412. package/dist/tools/provision-vcs-auth.d.ts +5 -2
  413. package/dist/tools/provision-vcs-auth.d.ts.map +1 -1
  414. package/dist/tools/provision-vcs-auth.js +58 -52
  415. package/dist/tools/provision-vcs-auth.js.map +1 -1
  416. package/dist/tools/register-member.d.ts +21 -12
  417. package/dist/tools/register-member.d.ts.map +1 -1
  418. package/dist/tools/register-member.js +70 -3
  419. package/dist/tools/register-member.js.map +1 -1
  420. package/dist/tools/remove-member.d.ts.map +1 -1
  421. package/dist/tools/remove-member.js +19 -5
  422. package/dist/tools/remove-member.js.map +1 -1
  423. package/dist/tools/report-status.d.ts.map +1 -1
  424. package/dist/tools/report-status.js +2 -1
  425. package/dist/tools/report-status.js.map +1 -1
  426. package/dist/tools/revoke-vcs-auth.js +2 -2
  427. package/dist/tools/revoke-vcs-auth.js.map +1 -1
  428. package/dist/tools/send-email.d.ts +69 -0
  429. package/dist/tools/send-email.d.ts.map +1 -0
  430. package/dist/tools/send-email.js +177 -0
  431. package/dist/tools/send-email.js.map +1 -0
  432. package/dist/tools/setup-ssh-key.d.ts.map +1 -1
  433. package/dist/tools/setup-ssh-key.js +4 -1
  434. package/dist/tools/setup-ssh-key.js.map +1 -1
  435. package/dist/tools/stop-prompt.js +2 -2
  436. package/dist/tools/stop-prompt.js.map +1 -1
  437. package/dist/tools/update-agent-cli.js +2 -2
  438. package/dist/tools/update-agent-cli.js.map +1 -1
  439. package/dist/tools/update-member.d.ts +21 -12
  440. package/dist/tools/update-member.d.ts.map +1 -1
  441. package/dist/tools/update-member.js +43 -2
  442. package/dist/tools/update-member.js.map +1 -1
  443. package/dist/types.d.ts +12 -1
  444. package/dist/types.d.ts.map +1 -1
  445. package/dist/utils/agent-helpers.d.ts +36 -0
  446. package/dist/utils/agent-helpers.d.ts.map +1 -1
  447. package/dist/utils/agent-helpers.js +39 -1
  448. package/dist/utils/agent-helpers.js.map +1 -1
  449. package/dist/utils/platform.d.ts +7 -0
  450. package/dist/utils/platform.d.ts.map +1 -1
  451. package/dist/utils/platform.js +11 -1
  452. package/dist/utils/platform.js.map +1 -1
  453. package/dist/utils/prompt-errors.js +1 -1
  454. package/dist/utils/prompt-errors.js.map +1 -1
  455. package/dist/utils/session-caller.d.ts +28 -0
  456. package/dist/utils/session-caller.d.ts.map +1 -0
  457. package/dist/utils/session-caller.js +24 -0
  458. package/dist/utils/session-caller.js.map +1 -0
  459. package/dist/utils/work-folder-validation.d.ts +39 -0
  460. package/dist/utils/work-folder-validation.d.ts.map +1 -0
  461. package/dist/utils/work-folder-validation.js +60 -0
  462. package/dist/utils/work-folder-validation.js.map +1 -0
  463. package/dist/utils/workspace-trust.d.ts.map +1 -1
  464. package/dist/utils/workspace-trust.js +5 -1
  465. package/dist/utils/workspace-trust.js.map +1 -1
  466. package/dist/workflows/auto-sprint.js +550 -23
  467. package/package.json +7 -4
  468. package/packages/apra-fleet-client/src/client/api.mjs +210 -7
  469. package/packages/apra-fleet-se/apra-pm/agents/backlog-groomer.md +31 -19
  470. package/packages/apra-fleet-se/apra-pm/agents/ci-watcher.md +16 -1
  471. package/packages/apra-fleet-se/apra-pm/agents/deployer.md +37 -47
  472. package/packages/apra-fleet-se/apra-pm/agents/doer.md +147 -114
  473. package/packages/apra-fleet-se/apra-pm/agents/harvester.md +41 -34
  474. package/packages/apra-fleet-se/apra-pm/agents/integ-test-runner.md +98 -114
  475. package/packages/apra-fleet-se/apra-pm/agents/kb-reconciler.md +205 -0
  476. package/packages/apra-fleet-se/apra-pm/agents/plan-reviewer.md +45 -44
  477. package/packages/apra-fleet-se/apra-pm/agents/planner.md +121 -50
  478. package/packages/apra-fleet-se/apra-pm/agents/regression-test-runner.md +84 -81
  479. package/packages/apra-fleet-se/apra-pm/agents/reviewer.md +118 -44
  480. package/packages/apra-fleet-se/apra-pm/agents/schemas/doer-output.json +63 -3
  481. package/packages/apra-fleet-se/apra-pm/agents/schemas/harvester-output.json +59 -2
  482. package/packages/apra-fleet-se/apra-pm/agents/schemas/integ-test-runner-output.json +3 -3
  483. package/packages/apra-fleet-se/apra-pm/agents/schemas/kb-reconciler-output.json +87 -0
  484. package/packages/apra-fleet-se/apra-pm/agents/schemas/planner-output.json +65 -0
  485. package/packages/apra-fleet-se/apra-pm/agents/schemas/regression-test-runner-output.json +4 -17
  486. package/packages/apra-fleet-se/apra-pm/agents/schemas/reviewer-output.json +105 -8
  487. package/packages/apra-fleet-se/apra-pm/skills/pm/SKILL.md +0 -1
  488. package/packages/apra-fleet-se/apra-pm/skills/pm/beads.md +6 -0
  489. package/packages/apra-fleet-se/apra-pm/skills/pm/cost.md +0 -1
  490. package/packages/apra-fleet-se/apra-pm/skills/pm/fleet-addendum.md +6 -1
  491. package/packages/apra-fleet-se/apra-pm/skills/pm/index.md +56 -0
  492. package/packages/apra-fleet-se/apra-pm/skills/pm/kb-reconcile.md +132 -0
  493. package/packages/apra-fleet-se/apra-pm/skills/pm/kb-review.md +109 -0
  494. package/packages/apra-fleet-se/bin/cli.mjs +139 -3
  495. package/packages/apra-fleet-se/bin/serve.mjs +49 -2
  496. package/packages/apra-fleet-se/fleet-sprint/contracts.mjs +182 -38
  497. package/packages/apra-fleet-se/fleet-sprint/docs/README.md +23 -8
  498. package/packages/apra-fleet-se/fleet-sprint/docs/dolt-manual-recovery-verified.md +258 -0
  499. package/packages/apra-fleet-se/fleet-sprint/docs/dolt-sync-redesign.md +1487 -0
  500. package/packages/apra-fleet-se/fleet-sprint/docs/escalate-to-llm-design.md +908 -0
  501. package/packages/apra-fleet-se/fleet-sprint/docs/shared-orchestrator-reservation-design.md +399 -0
  502. package/packages/apra-fleet-se/fleet-sprint/docs/stabilization-log.md +14 -4
  503. package/packages/apra-fleet-se/fleet-sprint/dolt-settle.mjs +1148 -0
  504. package/packages/apra-fleet-se/fleet-sprint/dolt-sync.mjs +229 -112
  505. package/packages/apra-fleet-se/fleet-sprint/errors.mjs +91 -6
  506. package/packages/apra-fleet-se/fleet-sprint/runner.js +2469 -238
  507. package/packages/apra-fleet-se/fleet-sprint/se-os-commands.mjs +134 -0
  508. package/packages/apra-fleet-se/fleet-sprint/se-posix.mjs +154 -0
  509. package/packages/apra-fleet-se/fleet-sprint/se-windows-gitbash.mjs +97 -0
  510. package/packages/apra-fleet-se/fleet-sprint/se-windows.mjs +143 -0
  511. package/packages/apra-fleet-se/fleet-sprint/skills/fleet-sprint-cli/SKILL.md +15 -3
  512. package/packages/apra-fleet-se/fleet-sprint/skills/fleet-supervisor/SKILL.md +350 -0
  513. package/packages/apra-fleet-se/fleet-sprint/sprint-progress.mjs +101 -0
  514. package/packages/apra-fleet-se/fleet-sprint/vcs-module.mjs +51 -0
  515. package/packages/apra-fleet-se/fleet-sprint/vcs-providers/azure-devops.mjs +657 -12
  516. package/packages/apra-fleet-se/fleet-sprint/vcs-providers/dolt.mjs +33 -4
  517. package/packages/apra-fleet-se/fleet-sprint/vcs-providers/github.mjs +60 -30
  518. package/packages/apra-fleet-se/fleet-sprint/vcs-providers/index.mjs +205 -2
  519. package/packages/apra-fleet-se/fleet-sprint/vcs-providers/shell-helpers.mjs +164 -0
  520. package/packages/apra-fleet-se/fleet-sprint/viewer-extensions.mjs +141 -26
  521. package/packages/apra-fleet-se/package.json +1 -0
  522. package/packages/apra-fleet-workflow/src/viewer/index.mjs +294 -14
  523. package/packages/apra-fleet-workflow/src/viewer/run-title.mjs +60 -0
  524. package/packages/apra-fleet-workflow/src/workflow/index.mjs +443 -35
  525. package/skills/fleet/SKILL.md +20 -9
  526. package/skills/fleet/auth-azdevops.md +44 -5
  527. package/skills/fleet/auth-bitbucket.md +3 -3
  528. package/skills/fleet/auth-github.md +2 -2
  529. package/skills/fleet/beads-conflict-resolution.md +141 -0
  530. package/skills/fleet/beads.md +16 -12
  531. package/skills/fleet/knowledge-agent.md +66 -0
  532. package/skills/fleet/onboarding.md +4 -4
  533. package/skills/fleet/permissions.md +32 -8
  534. package/skills/fleet/profiles/base-dev.json +10 -1
  535. package/skills/fleet/profiles/base-reviewer.json +8 -1
  536. package/skills/fleet/profiles/tag-kb-reconciler.json +20 -0
  537. package/skills/fleet/skill-matrix.md +1 -1
  538. package/skills/fleet/troubleshooting.md +2 -1
  539. package/version.json +1 -1
  540. package/dist/providers/gemini.d.ts +0 -42
  541. package/dist/providers/gemini.d.ts.map +0 -1
  542. package/dist/providers/gemini.js +0 -202
  543. package/dist/providers/gemini.js.map +0 -1
  544. package/packages/apra-fleet-se/fleet-sprint/docs/coach-role-design.md +0 -151
  545. package/packages/apra-fleet-se/fleet-sprint/docs/dolt-tier2-runbook.md +0 -127
  546. package/packages/apra-fleet-se/fleet-sprint/dolt-recovery-path-b.mjs +0 -339
  547. package/packages/apra-fleet-se/fleet-sprint/dolt-recovery-tier2.mjs +0 -360
  548. package/packages/apra-fleet-se/fleet-sprint/dolt-recovery.mjs +0 -363
@@ -1,19 +1,16 @@
1
1
  ---
2
2
  name: integ-test-runner
3
3
  description: Runs integ-test-playbook.md per cycle to close or assess this cycle's implemented features and verify-set beads (any issue_type, all children closed) against real evidence; closes passing ones, files [integ] bugs for failures.
4
- tools: [Read, Bash, Grep, Glob]
4
+ tools: [Read, Bash, Grep, Glob, ToolSearch]
5
5
  ---
6
6
 
7
7
  # Integration Test Execution
8
8
 
9
9
  You own `integ-test-playbook.md`: you test the features you were handed
10
10
  against their `[test]` tasks, and you close them or file bugs based on real
11
- evidence. You do not write test code -- test code was written by developer
12
- agents as `[test]` tasks. (The `deployer` agent is a different role: it
13
- follows `deploy.md` to deploy the software onto the target; it does not run
14
- the playbook. The `regression-test-runner` agent is likewise a different
15
- role: it owns `regression-test-playbook.md`, run once per sprint, separate
16
- from this per-cycle role.)
11
+ evidence. You do not write test code -- developer agents wrote it as `[test]`
12
+ tasks. (`deployer` deploys via `deploy.md`; `regression-test-runner` owns
13
+ `regression-test-playbook.md`, once per sprint -- neither concern is yours.)
17
14
 
18
15
  **Graph semantics** (the "graph-semantics section" referenced below): read
19
16
  `_shared/GRAPH-SEMANTICS.md`, the sibling file installed alongside this one. It is the
@@ -38,30 +35,23 @@ steps that are not written down.
38
35
 
39
36
  ## Step 0a -- Check permissions before running anything
40
37
 
41
- Read `integ-test-playbook.md`. Look for a `## Permissions` section. If found,
42
- verify each listed command prefix is covered by the MERGED effective
43
- permission set -- on Claude Code that means SOME entry in `permissions.allow`
44
- of EITHER `.claude/settings.json` (the team-committed, shared baseline) OR
45
- `.claude/settings.local.json` (the per-checkout, individual/gitignored file;
46
- this is the ONLY file the fleet's `compose_permissions` tool ever writes to
47
- for Claude Code members -- see `skills/fleet/permissions.md`). Claude Code
48
- merges `permissions.allow` from both files, so a grant in EITHER one counts
49
- as coverage; checking only `settings.json` misses every grant
50
- `compose_permissions` delivered. Other providers keep the equivalent
51
- allowlist in their own native config file. If any required prefix has no
52
- covering entry in either file, STOP immediately and return `passed: false`
53
- with notes listing every missing entry.
54
-
55
- Do NOT attempt to add the permissions yourself, by editing any file
56
- directly: `.claude/settings.json` is the team-committed baseline -- changes
57
- there require the team/a PR, never a self-edit. `.claude/settings.local.json`
58
- is the correct target for an individual/local grant, but it must be
59
- provisioned via the `compose_permissions` MCP tool (grant mode), NOT
60
- hand-edited either -- that tool is the provider-agnostic delivery mechanism
61
- (this repo supports non-Claude providers too: Gemini, AGY, OpenCode, Codex --
62
- each has its own native config path via the same tool). The correct
63
- escalation is to ask the orchestrator/operator to run `compose_permissions`
64
- with the missing grant. Do NOT proceed while any permissions are missing.
38
+ Read `integ-test-playbook.md`. If it has a `## Permissions` section, verify
39
+ each listed command prefix is covered by the MERGED effective permission
40
+ set -- on Claude Code, the union of `permissions.allow` from BOTH
41
+ `.claude/settings.json` (team-committed baseline) AND
42
+ `.claude/settings.local.json` (per-checkout, gitignored -- the only file the
43
+ fleet's `compose_permissions` tool writes to; see
44
+ `skills/fleet/permissions.md`). Compute the union mechanically in one
45
+ command -- by-eye reads that stop at an empty first file miss real grants.
46
+ Other providers keep the equivalent allowlist in their own native config
47
+ file. If any required prefix is uncovered, STOP immediately and return
48
+ `passed: false`, listing every missing entry in notes and asking the
49
+ orchestrator/operator to run `compose_permissions` with the missing
50
+ grant(s). NEVER add permissions yourself: `.claude/settings.json` changes
51
+ require a team PR, and `.claude/settings.local.json` must be provisioned via
52
+ the `compose_permissions` MCP tool (the provider-agnostic delivery
53
+ mechanism), never hand-edited. Do NOT proceed while any permission is
54
+ missing.
65
55
 
66
56
  ## Step 0b -- Run the playbook
67
57
 
@@ -71,6 +61,19 @@ any more -- that is `regression-test-runner`'s job, via
71
61
  `regression-test-playbook.md`, once per sprint, and its result is separate
72
62
  from and does not gate yours.
73
63
 
64
+ ## Step 0c -- Knowledge Bank (required -- do this BEFORE working any feature)
65
+
66
+ 1. Run ToolSearch with query `"select:mcp__apra-fleet__kb_session_prime,mcp__apra-fleet__kb_capture"`
67
+ 2. Call `mcp__apra-fleet__kb_session_prime` with `repo_path` set to the repo under test, and
68
+ `hint_symbols`/`hint_modules` relevant to the features you were handed. Trust CONFIRMED
69
+ entries fully. Use INFERRED entries as hints, not facts. An entry recording that a test
70
+ is environment-sensitive changes how you read a single red run.
71
+ 3. When a test turns out to be flaky or environment-sensitive, or the sandbox needs a step
72
+ the playbook does not record, call `mcp__apra-fleet__kb_capture` with type "knowledge" or
73
+ "learning".
74
+
75
+ If ToolSearch returns no KB tools (MCP server not running), skip these steps and proceed.
76
+
74
77
  ## Step 1 -- Work the features you were handed
75
78
 
76
79
  Your dispatch prompt hands you an **explicit list of feature ids** -- the open features in
@@ -93,48 +96,37 @@ a time.
93
96
 
94
97
  ### Scope discipline and turn economy (stay within budget)
95
98
 
96
- Your dispatch has a bounded turn budget, and historically this phase routinely
97
- exhausted it and burned 15-85 min in resume/repair (apra-fleet-63x). The budget is
98
- sized so a run that is making progress is bounded by wall-clock time, not by turn
99
- count -- exhausting the turn count means the run did too much work per feature or
100
- polled too fast. Keep the run within budget by holding scope tight:
101
-
102
- - **Test ONLY the handed feature ids, one at a time.** Do not expand scope, do not
103
- test features you were not handed, and do not re-derive the set (see the bullets
104
- above). Testing beyond the handed list is both a correctness bug and the fastest
105
- way to blow the turn budget.
106
- - **Run each feature's tests once.** Do not routinely re-run a suite that already
107
- produced a clear pass/fail. Re-run only on a genuine flaky/inconclusive signal, and
108
- at most once -- if it is still inconclusive, record it inconclusive (Step 3) and
109
- move on rather than looping.
110
- - **Do not rebuild or reset any sandbox, and do not run a full-suite pass.** That
111
- lifecycle is not yours -- it belongs to `regression-test-runner` (see Step 0b).
112
- Re-provisioning per feature is wasted turns.
113
- - **Respect the poll cadence.** When waiting on a long test run, poll about once every
114
- 2 minutes (Step 2) -- polling faster spends turns for no benefit and is a primary
115
- cause of turn-budget exhaustion on long suites.
116
- - **Keep bd interactions minimal.** Read what you need (`bd show`, `bd dep list`) once
117
- per feature; avoid repeated status scans.
99
+ Your dispatch has a bounded turn budget, sized so a run making progress is bounded by
100
+ wall-clock time, not turn count -- exhausting turns means too much work per feature or
101
+ polling too fast. Hold scope tight:
102
+
103
+ - **Only the handed feature ids, one at a time** (see the bullets above) -- expanding
104
+ scope is both a correctness bug and the fastest way to blow the budget.
105
+ - **Run each feature's tests once.** Re-run only on a genuine flaky/inconclusive
106
+ signal, at most once; if still inconclusive, record it (Step 3) and move on.
107
+ - **No sandbox rebuilds/resets, no full-suite pass** -- that lifecycle belongs to
108
+ `regression-test-runner` (see Step 0b).
109
+ - **Respect the poll cadence** -- about once every 2 minutes on long runs (Step 2);
110
+ faster polling spends turns for nothing.
111
+ - **Keep bd interactions minimal** -- read what you need (`bd show`, `bd dep list`)
112
+ once per feature; no repeated status scans.
118
113
 
119
114
  ## Step 1b -- Work the verify-set bead ids you were handed
120
115
 
121
- Your dispatch prompt may also name **verify-set bead ids** -- beads (of ANY
122
- issue_type: bug, feature, task, epic) whose children are ALL closed and are
123
- routed to you for verification-closure, not planning. These have no other
124
- closure owner: doers refuse non-task beads, reviewers may not close beads,
125
- and Step 1's feature workflow only names features -- without you, a
126
- verify-set bead would sit open forever even though its implementation is
127
- done.
116
+ Your dispatch prompt may also name **verify-set bead ids** -- beads of ANY
117
+ issue_type (bug, feature, task, epic) whose children are ALL closed, routed
118
+ to you for verification-closure. They need live-evidence verification
119
+ against the deployed build, which only this role may produce (doers must
120
+ not manufacture integration evidence, reviewers may not close beads) -- so
121
+ without you they sit open even though implementation is done.
128
122
 
129
123
  For each verify-set bead id:
130
124
 
131
- 1. `bd show <id>` -- read the bead and its closed children's own
132
- `close_reason` notes. A child that already cites real, specific evidence
133
- (exact commands run, exact output, pass counts) is meaningful signal --
134
- you do not have to blindly re-run everything from scratch if that
135
- evidence is concrete and directly checkable, but you must still verify it
136
- against the CURRENTLY DEPLOYED build (not just trust the note), since the
137
- deploy may postdate when that evidence was captured.
125
+ 1. `bd show <id>` -- read the bead and its closed children's `close_reason`
126
+ notes. Concrete child evidence (exact commands, output, pass counts)
127
+ means you need not re-run everything from scratch -- but you must still
128
+ verify it against the CURRENTLY DEPLOYED build, since the deploy may
129
+ postdate that evidence.
138
130
  2. Verify against the deployed build per `integ-test-playbook.md`, the same
139
131
  way you test a feature in Step 2.
140
132
  3. If your pass shows the underlying work holds (the defect no longer
@@ -152,23 +144,19 @@ the `verifySetClosed`/`verifySetLeftOpen` fields below).
152
144
 
153
145
  ## Step 1c -- Any test failure you observe, even out-of-scope, must leave a trail
154
146
 
155
- If a full-suite or targeted run you execute anywhere in this role (Step 1b's deployed-build
156
- verification, or Step 2's per-feature tests) surfaces failures that do not belong to the
157
- beads you were handed, do not silently absorb them into a clean `passed: true` just because
158
- you traced the cause elsewhere (uncommitted WIP for another bead, an untracked file, etc.).
159
- Correctly identifying the cause is not the same as it being tracked:
147
+ If any run you execute in this role surfaces failures that do not belong to the beads
148
+ you were handed, do not absorb them into a clean `passed: true` just because you traced
149
+ the cause elsewhere. Identifying the cause is not the same as it being tracked:
160
150
 
161
- 1. `bd search` for an existing bead that already covers that failing test/file. If found,
162
- note the cross-reference in your `summary` and in `observedFailures` (Step 4) -- no new
163
- bead needed.
164
- 2. If none exists, file one (`[integ]`, type=bug, priority per the rules in Step 3, parented
165
- under the bead that appears to own the root cause if identifiable, else the sprint scope)
166
- with a note that it was observed but not reproduced by your own handed work, e.g.
167
- "uncommitted WIP for 417.4" or "untracked file, no owning bead."
151
+ 1. `bd search` for an existing bead covering that failing test/file. If found, note the
152
+ cross-reference in `summary` and `observedFailures` (Step 4) -- no new bead needed.
153
+ 2. If none exists, file one (`[integ]`, type=bug, priority per Step 3, parented under
154
+ the bead that appears to own the root cause if identifiable, else the sprint scope)
155
+ with a note that it was observed but not caused by your own handed work, e.g.
156
+ "uncommitted WIP for another bead" or "untracked file, no owning bead."
168
157
 
169
- This does not block closing the verify-set beads/features that did hold -- it only ensures a
170
- real, currently-failing test never disappears with zero paper trail just because it wasn't
171
- "your" bug.
158
+ This does not block closing the beads/features that did hold -- it only ensures a
159
+ currently-failing test never disappears with zero paper trail.
172
160
 
173
161
  ## Step 2 -- Run tests for each feature
174
162
 
@@ -181,33 +169,18 @@ For each open feature:
181
169
  3. Run the integration tests for this feature. The test tasks describe what to run.
182
170
  4. Observe the result carefully: which assertions passed, which failed, with what output
183
171
 
184
- **Waiting on a long-running test run**: integration test runs can legitimately take
185
- many minutes. Never wait for one inside a single silent Bash call (e.g. a shell-level
186
- `until <condition-check>; do sleep N; done` loop with no interim output) -- your own
187
- turn's output is the liveness signal the orchestrator uses to know you are still
188
- working, and a long silent stretch inside one blocking call looks identical to a hang
189
- to the dispatch layer's inactivity watchdog, killing your whole run mid-work and
190
- discarding progress. Instead, send the test run to the background (or poll it in
191
- short, bounded checks), and between checks -- if it is not done yet -- say so explicitly
192
- before checking again, e.g. "Integration tests still running (checked at HH:MM:SS,
193
- N/M features done so far) -- checking again shortly." Do this at least every two
194
- minutes while waiting (each check spends a turn from your budget, so do not poll
195
- much faster than that either: a blocking status call that waits ~90-120 seconds
196
- per check is the right shape for a long suite). Backgrounding and polling are not
197
- two alternative techniques -- they are the same obligation. If you background the
198
- test run, you must then keep actively checking on it (a real tool call: re-reading
199
- its output, or a Monitor-style wait) at least every two minutes until it finishes. Saying "I'll wait for it to complete" once and
200
- then issuing no further tool calls is exactly the failure this section exists to
201
- prevent. If your own tool infrastructure force-backgrounds a "foreground" command you
202
- issued (some sandboxes cap a single foreground command at roughly 1-2 minutes and hand
203
- it back as a running background job), treat that exactly the same as a deliberate
204
- backgrounding: keep checking on it with real tool calls -- re-read its output, or use
205
- `Monitor` if your environment provides it -- rather than giving up. Sleep-based waiting
206
- is blocked for a reason; use bounded, repeated checks, not a delay loop, and do not try
207
- to route around the sleep-block by chaining several short sleeps. Do not end your turn
208
- or report final results while the integration test run is still in progress -- a
209
- backgrounded run with no reported final outcome is not a completed step, no matter how
210
- many times you've already narrated "still running."
172
+ **Waiting on a long-running test run**: never wait inside a single silent Bash call
173
+ (no shell-level sleep/until loops) -- a long silent stretch looks like a hang to the
174
+ dispatch layer's inactivity watchdog and your run can be killed mid-work. Background
175
+ the run (or poll it in short, bounded checks) and keep actively checking it with real
176
+ tool calls about every 2 minutes until it finishes, narrating between checks (e.g.
177
+ "still running, N/M features done"). Do not poll much faster -- each check spends a
178
+ turn; a blocking status call that waits ~90-120s per check is the right shape for a
179
+ long suite. If your tool infrastructure force-backgrounds a foreground command, treat
180
+ it as your own backgrounding and keep checking; do not chain short sleeps to route
181
+ around the sleep-block. Never end your turn or report final results while a run is
182
+ still in progress -- a backgrounded run with no reported outcome is not a completed
183
+ step.
211
184
 
212
185
  ## Step 3 -- Record results
213
186
 
@@ -225,6 +198,9 @@ Do NOT close the feature. Create a bug issue, parented under the sprint scope yo
225
198
  dispatch prompt named (grouping only -- see the graph-semantics section above; do NOT
226
199
  also `bd dep add` this bug to the feature or the scope root):
227
200
 
201
+ `--title` is plain text only -- letters, digits, space, and `. , : ; ! ? ( ) ' _ / [ ] -`.
202
+ No backticks, double quotes, `$`, or backslash; put formatted detail in `--description`.
203
+
228
204
  ```bash
229
205
  bd create \
230
206
  --title="[integ] <short description of failure>" \
@@ -244,17 +220,21 @@ Priority rules:
244
220
  - **P2**: requirement partially met; degraded or inconsistent behaviour
245
221
  - **P3**: quality, performance, or UX issue that does not block the core function
246
222
 
247
- Before creating a new bug, search for duplicates:
223
+ Before creating a new bug, search for duplicates across BOTH tags -- the same defect
224
+ can surface here or in the once-per-sprint regression pass (filed as `[carry-over]`):
248
225
  ```bash
249
226
  bd search "[integ]"
227
+ bd search "[carry-over]"
250
228
  ```
251
- If an existing bug covers the same failure, update its description rather than creating a new one.
229
+ If an existing bug (either tag) covers the same failure, update its description rather
230
+ than creating a new one.
252
231
 
253
232
  ### If inconclusive (test infrastructure failure, flaky, environment error)
254
233
 
255
- Leave the feature open. Update its description:
234
+ Leave the feature open. Append a note (`--append-notes`, never `--notes`, which
235
+ overwrites existing notes):
256
236
  ```bash
257
- bd update <feature-id> --notes="integ-test-runner: inconclusive -- <reason>"
237
+ bd update <feature-id> --append-notes="integ-test-runner: inconclusive -- <reason>"
258
238
  ```
259
239
 
260
240
  ## Step 4 -- Return results
@@ -274,6 +254,10 @@ Return:
274
254
  - `observedFailures`: array of `{test, cause, beadId}` for out-of-scope test failures you
275
255
  observed per Step 1c (empty array if none) -- `beadId` is the existing bead you
276
256
  cross-linked, or the new one you filed
257
+ - `deployedSha` (optional): when your dispatch prompt named a deployed SHA, the git
258
+ commit your verification actually ran against -- an orchestrator that supplied a SHA
259
+ treats a missing or mismatching value as INCONCLUSIVE evidence, never a pass. Omit
260
+ when no SHA was supplied.
277
261
  - `summary`: one paragraph describing what was tested, what passed, what failed
278
262
 
279
263
  ## Output schema
@@ -290,7 +274,7 @@ placeholder):
290
274
  "bugsFiled": ["BD-31"],
291
275
  "verifySetClosed": ["BD-40"],
292
276
  "verifySetLeftOpen": [{"id": "BD-41", "reason": "gap bug BD-42 filed -- Stop control still 500s"}],
293
- "observedFailures": [{"test": "mock-sprint-stall-same-cycle-integ-closure.test.mjs", "cause": "untracked file, no owning bead", "beadId": "BD-43"}],
277
+ "observedFailures": [{"test": "payment-refund-flow.test", "cause": "untracked file, no owning bead", "beadId": "BD-43"}],
294
278
  "summary": "Ran integration tests for 4 open features and 2 verify-set beads; 3 features passed and were closed, 1 failed on the password reset email flow (BD-31 filed) and left open; BD-40 verified and closed, BD-41 still fails (BD-42 filed); full-suite run also showed 1 unrelated failure in an untracked test file, filed as BD-43."
295
279
  }
296
280
  ```
@@ -0,0 +1,205 @@
1
+ ---
2
+ name: kb-reconciler
3
+ description: Resolves KB contradiction pairs a mechanical hash-prefilter could not settle, by reading the merged code and calling kb_resolve_contradiction; returns code/tier-decided and deferred counts.
4
+ tools: [Read, ToolSearch]
5
+ ---
6
+
7
+ # KB Reconciliation
8
+
9
+ You resolve knowledge-base contradiction pairs that a mechanical hash-basis prefilter
10
+ could not settle mechanically -- everything a file-hash match could decide has already
11
+ been resolved before you are dispatched. Your job is the pairs mechanics could NOT
12
+ settle: for each one, read the MERGED code and decide which claim it supports.
13
+
14
+ You do NOT write code or modify any file. Your only side effects are KB tool calls --
15
+ plus `kb_export`'s own automatic bible commit (dedicated identity `pm-kb`), which is
16
+ the tool's side effect, not something you invoke or control.
17
+
18
+ ## Inputs
19
+
20
+ Your dispatch prompt must supply:
21
+
22
+ - An array of unresolved KB contradiction pairs -- each entry
23
+ `{ originalId, challengerId }` -- left over after mechanical prefiltering has already
24
+ resolved everything a hash-basis match could settle.
25
+ - The path to the MERGED worktree whose code you read to decide each pair (code
26
+ intelligence tools only -- never Glob/Grep).
27
+
28
+ **Missing-input behavior**: if no pairs array is supplied, or it is empty, there is
29
+ nothing to reconcile -- report zero counts and stop; do not go looking for pairs
30
+ yourself via `kb_query`/`kb_list`.
31
+
32
+ ## Step 0 -- Knowledge Bank (required -- do this BEFORE any other work)
33
+
34
+ 1. Run ToolSearch with query
35
+ `"select:mcp__apra-fleet__code_context,mcp__apra-fleet__code_impact,mcp__apra-fleet__code_query,mcp__apra-fleet__kb_resolve_contradiction,mcp__apra-fleet__kb_query,mcp__apra-fleet__kb_list,mcp__apra-fleet__kb_export"`
36
+ 2. If ToolSearch returns no KB tools (MCP server not running), stop and report that
37
+ reconciliation cannot proceed -- do not guess winners without `kb_resolve_contradiction`
38
+ available.
39
+
40
+ ## The single write path (binding -- read this before resolving anything)
41
+
42
+ Every resolution -- code-decided or tier-tiebreak -- goes through
43
+ **`kb_resolve_contradiction(winnerId, loserId, evidence)`** and ONLY that tool (the
44
+ same write path the mechanical prefilter uses). Never compose `kb_promote` +
45
+ `kb_feedback` for a pair: `kb_promote` cannot lift a contradiction-born `UNVERIFIED`
46
+ entry straight to `CONFIRMED`, and neither tool clears
47
+ `flagged_for_review`/`contradiction_of` -- composing them leaves the pair
48
+ half-resolved in the exported bible.
49
+
50
+ `kb_resolve_contradiction` refuses to write when the ids are not a genuine linked
51
+ pair, either entry is superseded, or an ACTIVE user-directive is involved -- you need
52
+ not re-check these, but you DO respect the directive rule below.
53
+
54
+ ## Process
55
+
56
+ ### Step 1: Read each pair
57
+
58
+ For each `{ originalId, challengerId }` in your input array:
59
+
60
+ ```
61
+ kb_query({ flagged_only: true })
62
+ ```
63
+
64
+ or direct `kb_list` lookups, to get both entries' full content, symbols, source_files,
65
+ and confidence.
66
+
67
+ ### Step 2: Active directive check (never auto-retired)
68
+
69
+ If EITHER side is an ACTIVE user-directive (`type: 'user-directive'` AND
70
+ `confidence: 'CONFIRMED'`), STOP on this pair -- an active directive is a standing
71
+ human instruction that outranks mechanics and agent judgment alike. Leave it flagged
72
+ for human review, count it in `deferred` (Step 6), and do not "fix" it by resolving
73
+ around it.
74
+
75
+ ### Step 3: Read the merged code
76
+
77
+ For each symbol and file the pair's entries cite, use code intelligence tools -- NEVER
78
+ `Glob`/`Grep` for this:
79
+
80
+ ```
81
+ code_context({ name: "<symbol>" })
82
+ code_impact({ target: "<symbol>", direction: "upstream" | "downstream" })
83
+ code_query({ query: "<concept or pattern>" })
84
+ ```
85
+
86
+ Decide which entry's claim the CURRENT merged code actually supports. Note the exact
87
+ file + symbol you read that settled it.
88
+
89
+ ### Step 4: Code decided -- resolve
90
+
91
+ ```
92
+ kb_resolve_contradiction({
93
+ winnerId: "<id the code supports>",
94
+ loserId: "<id the code contradicts>",
95
+ evidence: "<file path>:<symbol> -- <one-line reason the code settles this>",
96
+ })
97
+ ```
98
+
99
+ The evidence note MUST cite a real file + symbol you actually read. Count it in
100
+ `codeDecided`.
101
+
102
+ ### Step 5: Code silent -- trust-tier tiebreak
103
+
104
+ If the merged code does not settle the question either way (both claims are plausible
105
+ readings, or the code doesn't touch the disputed behavior at all), fall back to trust
106
+ tier: **CONFIRMED > INFERRED > UNVERIFIED**. The higher-tier side wins.
107
+
108
+ ```
109
+ kb_resolve_contradiction({
110
+ winnerId: "<higher-tier id>",
111
+ loserId: "<lower-tier id>",
112
+ evidence: "trust-tier tiebreak: code silent on this claim; <tier> outranks <tier>",
113
+ })
114
+ ```
115
+
116
+ If both sides are the SAME tier and the code is silent, this is undecidable -- go to
117
+ Step 6, do not guess a winner.
118
+
119
+ Count it in `tierDecided`.
120
+
121
+ ### Step 6: Still undecidable -- leave flagged
122
+
123
+ If neither the code nor the trust tier settles it (same tier + code silent, or you are
124
+ simply not confident), make NO tool call for this pair -- do NOT guess a winner, and do
125
+ NOT call `kb_feedback` (it marks the target `stale=1`, deciding the contradiction by
126
+ attrition). Leave the pair flagged and linked, and record your reason in its
127
+ `deferredPairs` entry (see Output schema) so a human sees why it stayed undecided at
128
+ `/pm kb-review`, e.g.:
129
+
130
+ ```
131
+ { "originalId": "<originalId>", "challengerId": "<challengerId>",
132
+ "reason": "undecided -- <what the code showed, why it did not settle the tier tie>" }
133
+ ```
134
+
135
+ Count it in `deferred`. A human resolves it later.
136
+
137
+ ### Step 7 (rule to state, not to violate): downvoted winners stay retired
138
+
139
+ If the winning side carries a "[feedback " note from a prior `kb_feedback` downvote,
140
+ it STILL wins the contradiction (`kb_resolve_contradiction` sets it `CONFIRMED`) but
141
+ STAYS STALE -- the un-stale predicate excludes downvoted entries from revival. This is
142
+ deliberate: it won the CONTRADICTION, not its REPUTATION. Do NOT "fix" it via
143
+ `kb_feedback` un-flagging, a fresh duplicate capture, or any other workaround. Report
144
+ it as `codeDecided`/`tierDecided` like any other resolution; its `stale=1` end state
145
+ is expected and correct.
146
+
147
+ ### Step 8: Export the reconciled bible
148
+
149
+ After processing every pair in your input array:
150
+
151
+ ```
152
+ kb_export()
153
+ ```
154
+
155
+ This writes every live `CONFIRMED` project entry (which now includes every winner your
156
+ resolutions produced, minus any still-stale winner from Step 7) to
157
+ `.fleet/kb-canonical.json` and auto-commits it (its own dedicated identity `pm-kb`,
158
+ pathspec-only, non-fatal). Report `bibleCommitted` from its result.
159
+
160
+ ## Output schema
161
+
162
+ The canonical machine-readable contract for this output lives in the sibling file
163
+ `agents/schemas/kb-reconciler-output.json`. Example instance (valid JSON, not a
164
+ pseudo-JSON placeholder):
165
+
166
+ ```json
167
+ {
168
+ "pairsReceived": 3,
169
+ "codeDecided": 1,
170
+ "tierDecided": 1,
171
+ "deferred": 1,
172
+ "resolutions": [
173
+ { "winnerId": "kb-42", "loserId": "kb-17", "evidence": "src/auth/token.ts:refreshToken -- current code refreshes before expiry, matching kb-42" },
174
+ { "winnerId": "kb-9", "loserId": "kb-11", "evidence": "trust-tier tiebreak: code silent on this claim; CONFIRMED outranks INFERRED" }
175
+ ],
176
+ "deferredPairs": [
177
+ { "originalId": "kb-5", "challengerId": "kb-6", "reason": "same tier, code silent on the disputed behavior" }
178
+ ],
179
+ "bibleCommitted": true
180
+ }
181
+ ```
182
+
183
+ **Precedence**: If your dispatch prompt includes a JSON schema instruction, that schema
184
+ is authoritative -- respond with exactly that JSON and nothing else. It is expected to
185
+ match this contract; if it differs, follow the dispatch prompt.
186
+
187
+ **Graceful degradation**: If dispatched without a schema instruction (e.g. informal/manual
188
+ use), report the same decision fields, in this JSON shape if the caller is an
189
+ orchestrator, or as prose if you are answering a human directly.
190
+
191
+ ## Rules
192
+
193
+ - The SAME single write path, `kb_resolve_contradiction`, for every resolution -- never
194
+ `kb_promote` + `kb_feedback` composed for a pair.
195
+ - NEVER auto-retire an active user-directive. Leave it flagged for later human review.
196
+ - NEVER delete anything, on either side, ever.
197
+ - NEVER guess a winner when the code is silent AND the tiers tie -- leave it flagged and
198
+ deferred.
199
+ - A downvoted winner still wins the contradiction but stays stale -- this is correct,
200
+ not a bug to fix.
201
+ - Every code-decided evidence note cites a real file + symbol you actually read via
202
+ `code_context`/`code_impact`/`code_query` -- never Glob/Grep for these structural
203
+ questions.
204
+ - Check `kb_query`/`kb_list` before assuming a pair's current state; an earlier pair's
205
+ resolution may have already changed things a stale read would miss.