@chankov/agent-fleet 0.0.9 → 0.0.11

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 (661) hide show
  1. package/.claude/commands/doctor-agent-fleet.md +12 -7
  2. package/.claude/commands/setup-agent-fleet.md +7 -15
  3. package/.opencode/commands/af-doctor-agent-fleet.md +12 -7
  4. package/.opencode/commands/af-setup-agent-fleet.md +8 -6
  5. package/.pi/extensions/agent-fleet-update-check/README.md +2 -3
  6. package/.pi/extensions/btw/README.md +5 -4
  7. package/.pi/extensions/chrome-devtools-mcp/README.md +3 -6
  8. package/.pi/extensions/compact-and-continue/README.md +3 -3
  9. package/.pi/extensions/mcp-bridge/README.md +1 -1
  10. package/.pi/extensions/pi-voice-stt/README.md +3 -0
  11. package/.pi/harnesses/agent-hub/README.md +142 -10
  12. package/.pi/harnesses/agent-hub/docs-lane.js +122 -0
  13. package/.pi/harnesses/agent-hub/external-blocker.js +85 -0
  14. package/.pi/harnesses/agent-hub/index.ts +448 -39
  15. package/.pi/harnesses/agent-hub/package.json +1 -1
  16. package/.pi/harnesses/agent-hub/review-findings.js +102 -0
  17. package/.pi/harnesses/agent-hub/run-budget.js +302 -4
  18. package/.pi/harnesses/agent-hub/run-namespace.js +87 -0
  19. package/.pi/harnesses/coms/package.json +1 -1
  20. package/.pi/harnesses/damage-control-continue/package.json +1 -1
  21. package/.pi/prompts/af-doctor-agent-fleet.md +13 -6
  22. package/.pi/prompts/af-setup-agent-fleet.md +7 -15
  23. package/.versions/0.0.10/.claude/commands/build.md +44 -0
  24. package/.versions/0.0.10/.claude/commands/code-simplify.md +22 -0
  25. package/.versions/0.0.10/.claude/commands/design-agent.md +14 -0
  26. package/.versions/0.0.10/.claude/commands/doctor-agent-fleet.md +22 -0
  27. package/.versions/0.0.10/.claude/commands/orchestrate.md +112 -0
  28. package/.versions/0.0.10/.claude/commands/plan.md +16 -0
  29. package/.versions/0.0.10/.claude/commands/prime.md +22 -0
  30. package/.versions/0.0.10/.claude/commands/review.md +16 -0
  31. package/.versions/0.0.10/.claude/commands/set-hermes-telegram.md +15 -0
  32. package/.versions/0.0.10/.claude/commands/set-hermes-watchdog.md +6 -0
  33. package/.versions/0.0.10/.claude/commands/setup-agent-fleet.md +17 -0
  34. package/.versions/0.0.10/.claude/commands/ship.md +72 -0
  35. package/.versions/0.0.10/.claude/commands/spec.md +15 -0
  36. package/.versions/0.0.10/.claude/commands/test.md +19 -0
  37. package/.versions/0.0.10/.claude/commands/webperf.md +32 -0
  38. package/.versions/0.0.10/.claude/orchestrate-teams.yaml +24 -0
  39. package/.versions/0.0.10/.opencode/commands/af-build.md +17 -0
  40. package/.versions/0.0.10/.opencode/commands/af-code-simplify.md +16 -0
  41. package/.versions/0.0.10/.opencode/commands/af-compound.md +16 -0
  42. package/.versions/0.0.10/.opencode/commands/af-design-agent.md +15 -0
  43. package/.versions/0.0.10/.opencode/commands/af-doctor-agent-fleet.md +22 -0
  44. package/.versions/0.0.10/.opencode/commands/af-orchestrate.md +112 -0
  45. package/.versions/0.0.10/.opencode/commands/af-plan.md +16 -0
  46. package/.versions/0.0.10/.opencode/commands/af-prime.md +22 -0
  47. package/.versions/0.0.10/.opencode/commands/af-review.md +15 -0
  48. package/.versions/0.0.10/.opencode/commands/af-set-hermes-telegram.md +15 -0
  49. package/.versions/0.0.10/.opencode/commands/af-set-hermes-watchdog.md +6 -0
  50. package/.versions/0.0.10/.opencode/commands/af-setup-agent-fleet.md +17 -0
  51. package/.versions/0.0.10/.opencode/commands/af-ship.md +16 -0
  52. package/.versions/0.0.10/.opencode/commands/af-spec.md +16 -0
  53. package/.versions/0.0.10/.opencode/commands/af-test.md +21 -0
  54. package/.versions/0.0.10/.opencode/commands/af-webperf.md +32 -0
  55. package/.versions/0.0.10/.opencode/orchestrate-teams.yaml +24 -0
  56. package/.versions/0.0.10/.pi/agents/dispatch-policy.yaml +32 -0
  57. package/.versions/0.0.10/.pi/agents/model-profiles.yaml +27 -0
  58. package/.versions/0.0.10/.pi/agents/peers.yaml +142 -0
  59. package/.versions/0.0.10/.pi/agents/teams.yaml +41 -0
  60. package/.versions/0.0.10/.pi/damage-control-rules.yaml +297 -0
  61. package/.versions/0.0.10/.pi/extensions/agent-fleet-update-check/README.md +57 -0
  62. package/.versions/0.0.10/.pi/extensions/agent-fleet-update-check/index.ts +161 -0
  63. package/.versions/0.0.10/.pi/extensions/agent-fleet-update-check/package.json +6 -0
  64. package/.versions/0.0.10/.pi/extensions/btw/README.md +118 -0
  65. package/.versions/0.0.10/.pi/extensions/btw/index.ts +917 -0
  66. package/.versions/0.0.10/.pi/extensions/btw/package.json +6 -0
  67. package/.versions/0.0.10/.pi/extensions/btw/state.js +179 -0
  68. package/.versions/0.0.10/.pi/extensions/chrome-devtools-mcp/README.md +55 -0
  69. package/.versions/0.0.10/.pi/extensions/chrome-devtools-mcp/index.ts +93 -0
  70. package/.versions/0.0.10/.pi/extensions/chrome-devtools-mcp/package.json +6 -0
  71. package/.versions/0.0.10/.pi/extensions/compact-and-continue/README.md +42 -0
  72. package/.versions/0.0.10/.pi/extensions/compact-and-continue/index.ts +120 -0
  73. package/.versions/0.0.10/.pi/extensions/compact-and-continue/package.json +6 -0
  74. package/.versions/0.0.10/.pi/extensions/mcp-bridge/README.md +46 -0
  75. package/.versions/0.0.10/.pi/extensions/mcp-bridge/index.ts +206 -0
  76. package/.versions/0.0.10/.pi/extensions/mcp-bridge/package.json +6 -0
  77. package/.versions/0.0.10/.pi/extensions/package-lock.json +1143 -0
  78. package/.versions/0.0.10/.pi/extensions/package.json +9 -0
  79. package/.versions/0.0.10/.pi/extensions/pi-voice-stt/README.md +201 -0
  80. package/.versions/0.0.10/.pi/extensions/pi-voice-stt/config.ts +198 -0
  81. package/.versions/0.0.10/.pi/extensions/pi-voice-stt/examples/stt.json +35 -0
  82. package/.versions/0.0.10/.pi/extensions/pi-voice-stt/index.ts +248 -0
  83. package/.versions/0.0.10/.pi/extensions/pi-voice-stt/package.json +6 -0
  84. package/.versions/0.0.10/.pi/extensions/pi-voice-stt/providers.ts +214 -0
  85. package/.versions/0.0.10/.pi/extensions/pi-voice-stt/recorder.ts +158 -0
  86. package/.versions/0.0.10/.pi/harnesses/agent-hub/README.md +1001 -0
  87. package/.versions/0.0.10/.pi/harnesses/agent-hub/access-approval.ts +135 -0
  88. package/.versions/0.0.10/.pi/harnesses/agent-hub/artifacts.js +146 -0
  89. package/.versions/0.0.10/.pi/harnesses/agent-hub/assertion-ledger.js +58 -0
  90. package/.versions/0.0.10/.pi/harnesses/agent-hub/backend-policy.js +153 -0
  91. package/.versions/0.0.10/.pi/harnesses/agent-hub/context-window.js +106 -0
  92. package/.versions/0.0.10/.pi/harnesses/agent-hub/delegate.ts +435 -0
  93. package/.versions/0.0.10/.pi/harnesses/agent-hub/docs-lane.js +122 -0
  94. package/.versions/0.0.10/.pi/harnesses/agent-hub/drift-watchdog.js +211 -0
  95. package/.versions/0.0.10/.pi/harnesses/agent-hub/evidence-rules.js +96 -0
  96. package/.versions/0.0.10/.pi/harnesses/agent-hub/external-blocker.js +85 -0
  97. package/.versions/0.0.10/.pi/harnesses/agent-hub/footer.ts +31 -0
  98. package/.versions/0.0.10/.pi/harnesses/agent-hub/helpers.ts +248 -0
  99. package/.versions/0.0.10/.pi/harnesses/agent-hub/index.ts +9111 -0
  100. package/.versions/0.0.10/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
  101. package/.versions/0.0.10/.pi/harnesses/agent-hub/monitor-invoke-journal.ts +131 -0
  102. package/.versions/0.0.10/.pi/harnesses/agent-hub/monitor-invoke.ts +92 -0
  103. package/.versions/0.0.10/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
  104. package/.versions/0.0.10/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
  105. package/.versions/0.0.10/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
  106. package/.versions/0.0.10/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
  107. package/.versions/0.0.10/.pi/harnesses/agent-hub/monitor-session-bridge.ts +257 -0
  108. package/.versions/0.0.10/.pi/harnesses/agent-hub/package.json +7 -0
  109. package/.versions/0.0.10/.pi/harnesses/agent-hub/provider-semaphore.js +138 -0
  110. package/.versions/0.0.10/.pi/harnesses/agent-hub/research-retention.js +34 -0
  111. package/.versions/0.0.10/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
  112. package/.versions/0.0.10/.pi/harnesses/agent-hub/return-contract.js +293 -0
  113. package/.versions/0.0.10/.pi/harnesses/agent-hub/return-extract.js +75 -0
  114. package/.versions/0.0.10/.pi/harnesses/agent-hub/review-findings.js +102 -0
  115. package/.versions/0.0.10/.pi/harnesses/agent-hub/run-budget.js +479 -0
  116. package/.versions/0.0.10/.pi/harnesses/agent-hub/run-namespace.js +87 -0
  117. package/.versions/0.0.10/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
  118. package/.versions/0.0.10/.pi/harnesses/agent-hub/scope-gate.js +103 -0
  119. package/.versions/0.0.10/.pi/harnesses/agent-hub/session-health.js +110 -0
  120. package/.versions/0.0.10/.pi/harnesses/agent-hub/spawn.ts +354 -0
  121. package/.versions/0.0.10/.pi/harnesses/agent-hub/version.ts +42 -0
  122. package/.versions/0.0.10/.pi/harnesses/ask-user-remote/README.md +19 -0
  123. package/.versions/0.0.10/.pi/harnesses/ask-user-remote/index.ts +321 -0
  124. package/.versions/0.0.10/.pi/harnesses/ask-user-remote/race-core.js +106 -0
  125. package/.versions/0.0.10/.pi/harnesses/coms/README.md +100 -0
  126. package/.versions/0.0.10/.pi/harnesses/coms/index.ts +1767 -0
  127. package/.versions/0.0.10/.pi/harnesses/coms/package.json +7 -0
  128. package/.versions/0.0.10/.pi/harnesses/coms/version.ts +42 -0
  129. package/.versions/0.0.10/.pi/harnesses/damage-control-continue/README.md +124 -0
  130. package/.versions/0.0.10/.pi/harnesses/damage-control-continue/index.ts +536 -0
  131. package/.versions/0.0.10/.pi/harnesses/damage-control-continue/package.json +7 -0
  132. package/.versions/0.0.10/.pi/harnesses/damage-control-continue/version.ts +42 -0
  133. package/.versions/0.0.10/.pi/harnesses/lib/coms-registry-entry.ts +94 -0
  134. package/.versions/0.0.10/.pi/harnesses/lib/damage-control-shared.ts +197 -0
  135. package/.versions/0.0.10/.pi/harnesses/lib/herdr-client.ts +472 -0
  136. package/.versions/0.0.10/.pi/harnesses/lib/herdr-presence.ts +399 -0
  137. package/.versions/0.0.10/.pi/harnesses/lib/hermes-monitor-events.ts +136 -0
  138. package/.versions/0.0.10/.pi/harnesses/lib/hermes-monitor-herdr.ts +28 -0
  139. package/.versions/0.0.10/.pi/harnesses/lib/hermes-monitor-model.ts +18 -0
  140. package/.versions/0.0.10/.pi/harnesses/lib/hermes-monitor-registry.ts +6 -0
  141. package/.versions/0.0.10/.pi/harnesses/lib/hermes-monitor-socket.ts +163 -0
  142. package/.versions/0.0.10/.pi/harnesses/lib/hermes-monitor-store.ts +31 -0
  143. package/.versions/0.0.10/.pi/harnesses/lib/spawned-peers.js +190 -0
  144. package/.versions/0.0.10/.pi/harnesses/package-lock.json +35 -0
  145. package/.versions/0.0.10/.pi/harnesses/package.json +9 -0
  146. package/.versions/0.0.10/.pi/prompts/af-build.md +24 -0
  147. package/.versions/0.0.10/.pi/prompts/af-code-simplify.md +22 -0
  148. package/.versions/0.0.10/.pi/prompts/af-doctor-agent-fleet.md +22 -0
  149. package/.versions/0.0.10/.pi/prompts/af-plan.md +16 -0
  150. package/.versions/0.0.10/.pi/prompts/af-review.md +16 -0
  151. package/.versions/0.0.10/.pi/prompts/af-set-hermes-telegram.md +15 -0
  152. package/.versions/0.0.10/.pi/prompts/af-set-hermes-watchdog.md +6 -0
  153. package/.versions/0.0.10/.pi/prompts/af-setup-agent-fleet.md +19 -0
  154. package/.versions/0.0.10/.pi/prompts/af-ship.md +17 -0
  155. package/.versions/0.0.10/.pi/prompts/af-spec.md +15 -0
  156. package/.versions/0.0.10/.pi/prompts/af-test.md +19 -0
  157. package/.versions/0.0.10/.pi/skills/bowser/SKILL.md +145 -0
  158. package/.versions/0.0.10/.version +1 -0
  159. package/.versions/0.0.10/agents/architect.md +24 -0
  160. package/.versions/0.0.10/agents/bowser.md +27 -0
  161. package/.versions/0.0.10/agents/builder.md +54 -0
  162. package/.versions/0.0.10/agents/code-reviewer.md +208 -0
  163. package/.versions/0.0.10/agents/deep-researcher.md +32 -0
  164. package/.versions/0.0.10/agents/documenter.md +18 -0
  165. package/.versions/0.0.10/agents/orchestrator.md +72 -0
  166. package/.versions/0.0.10/agents/plan-reviewer.md +83 -0
  167. package/.versions/0.0.10/agents/planner.md +70 -0
  168. package/.versions/0.0.10/agents/releaser.md +24 -0
  169. package/.versions/0.0.10/agents/researcher.md +28 -0
  170. package/.versions/0.0.10/agents/security-auditor.md +167 -0
  171. package/.versions/0.0.10/agents/test-engineer.md +153 -0
  172. package/.versions/0.0.10/agents/web-debugger.md +43 -0
  173. package/.versions/0.0.10/agents/web-performance-auditor.md +193 -0
  174. package/.versions/0.0.10/codex/CONDUCTOR.md +148 -0
  175. package/.versions/0.0.10/docs/ARCHITECTURE.md +303 -0
  176. package/.versions/0.0.10/docs/agent-fleet-setup.md +377 -0
  177. package/.versions/0.0.10/docs/claude-code-coms-bridge.md +109 -0
  178. package/.versions/0.0.10/docs/codex-remote-conductor.md +170 -0
  179. package/.versions/0.0.10/docs/coms-hermes-bridge.md +189 -0
  180. package/.versions/0.0.10/docs/getting-started.md +254 -0
  181. package/.versions/0.0.10/docs/npm-install.md +514 -0
  182. package/.versions/0.0.10/docs/opencode-setup.md +281 -0
  183. package/.versions/0.0.10/docs/pi-extensions.md +363 -0
  184. package/.versions/0.0.10/docs/pi-setup.md +571 -0
  185. package/.versions/0.0.10/docs/skill-anatomy.md +150 -0
  186. package/.versions/0.0.10/hermes/README.md +347 -0
  187. package/.versions/0.0.10/hermes/desktop-plugins/agent-fleet-herdr/plugin.js +1291 -0
  188. package/.versions/0.0.10/hermes/desktop-plugins/agent-fleet-herdr/presentation.js +672 -0
  189. package/.versions/0.0.10/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
  190. package/.versions/0.0.10/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
  191. package/.versions/0.0.10/hermes/gates/gate-o-capability.md +8 -0
  192. package/.versions/0.0.10/hermes/gates/gate-o-validator-fixtures.json +1 -0
  193. package/.versions/0.0.10/hermes/plugins/agent-fleet-herdr/dashboard/activity.py +770 -0
  194. package/.versions/0.0.10/hermes/plugins/agent-fleet-herdr/dashboard/coms_registry.py +134 -0
  195. package/.versions/0.0.10/hermes/plugins/agent-fleet-herdr/dashboard/coms_send.py +350 -0
  196. package/.versions/0.0.10/hermes/plugins/agent-fleet-herdr/dashboard/herdr_source.py +193 -0
  197. package/.versions/0.0.10/hermes/plugins/agent-fleet-herdr/dashboard/manifest.json +4 -0
  198. package/.versions/0.0.10/hermes/plugins/agent-fleet-herdr/dashboard/plugin_api.py +444 -0
  199. package/.versions/0.0.10/hermes/plugins/agent-fleet-herdr/dashboard/sessions.py +205 -0
  200. package/.versions/0.0.10/hermes/plugins/agent-fleet-herdr/dashboard/tasks.py +300 -0
  201. package/.versions/0.0.10/hermes/plugins/agent-fleet-herdr/dashboard/watch.py +819 -0
  202. package/.versions/0.0.10/hermes/plugins/agent-fleet-herdr/plugin.yaml +8 -0
  203. package/.versions/0.0.10/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +139 -0
  204. package/.versions/0.0.10/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
  205. package/.versions/0.0.10/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
  206. package/.versions/0.0.10/hermes/skills/hub-conductor/SKILL.md +84 -0
  207. package/.versions/0.0.10/hermes/skills/hub-liaison/SKILL.md +84 -0
  208. package/.versions/0.0.10/hermes/skills/hub-watchdog/SKILL.md +76 -0
  209. package/.versions/0.0.10/hermes/skills/hub-watchdog/manifest.json +1 -0
  210. package/.versions/0.0.10/hermes/skills/hub-watchdog/scripts/watchdog.py +249 -0
  211. package/.versions/0.0.10/hermes/skills/hub-watchdog/scripts/watchdog_actions.py +124 -0
  212. package/.versions/0.0.10/hermes/skills/hub-watchdog/scripts/watchdog_contract.py +76 -0
  213. package/.versions/0.0.10/hermes/skills/hub-watchdog/scripts/watchdog_delivery.py +10 -0
  214. package/.versions/0.0.10/hermes/skills/hub-watchdog/scripts/watchdog_engine.py +128 -0
  215. package/.versions/0.0.10/hermes/skills/hub-watchdog/scripts/watchdog_judgment.py +41 -0
  216. package/.versions/0.0.10/hermes/skills/hub-watchdog/scripts/watchdog_recovery.py +103 -0
  217. package/.versions/0.0.10/hermes/skills/hub-watchdog/scripts/watchdog_state.py +163 -0
  218. package/.versions/0.0.10/hermes/skills/hub-watchdog/scripts/watchdog_transport.py +138 -0
  219. package/.versions/0.0.10/hermes/watchdog-tests/__init__.py +0 -0
  220. package/.versions/0.0.10/hooks/SIMPLIFY-IGNORE.md +90 -0
  221. package/.versions/0.0.10/hooks/coms-stop-hook.mjs +84 -0
  222. package/.versions/0.0.10/hooks/hooks.json +14 -0
  223. package/.versions/0.0.10/hooks/session-start.sh +74 -0
  224. package/.versions/0.0.10/hooks/simplify-ignore.sh +302 -0
  225. package/.versions/0.0.10/install-manifest.json +3615 -0
  226. package/.versions/0.0.10/justfile +254 -0
  227. package/.versions/0.0.10/manifest-meta.json +472 -0
  228. package/.versions/0.0.10/references/accessibility-checklist.md +160 -0
  229. package/.versions/0.0.10/references/definition-of-done.md +67 -0
  230. package/.versions/0.0.10/references/fleet-coordination-patterns.md +151 -0
  231. package/.versions/0.0.10/references/observability-checklist.md +91 -0
  232. package/.versions/0.0.10/references/orchestration-patterns.md +370 -0
  233. package/.versions/0.0.10/references/performance-checklist.md +153 -0
  234. package/.versions/0.0.10/references/prompting-patterns.md +380 -0
  235. package/.versions/0.0.10/references/security-checklist.md +179 -0
  236. package/.versions/0.0.10/references/testing-patterns.md +236 -0
  237. package/.versions/0.0.10/scripts/codex-conductor.ts +41 -0
  238. package/.versions/0.0.10/scripts/codex-remote-control.ts +167 -0
  239. package/.versions/0.0.10/scripts/coms-claude-bridge.ts +401 -0
  240. package/.versions/0.0.10/scripts/coms-cli.ts +484 -0
  241. package/.versions/0.0.10/scripts/coms-hermes-bridge.ts +413 -0
  242. package/.versions/0.0.10/scripts/fleet.ts +168 -0
  243. package/.versions/0.0.10/scripts/hermes-monitor-capability-runner.ts +25 -0
  244. package/.versions/0.0.10/scripts/hermes-monitor-scenario.ts +474 -0
  245. package/.versions/0.0.10/scripts/hermes-watchdog-capability-probe.ts +45 -0
  246. package/.versions/0.0.10/scripts/install-hermes-plugin.sh +180 -0
  247. package/.versions/0.0.10/scripts/lib/claude-bridge-core.ts +165 -0
  248. package/.versions/0.0.10/scripts/lib/codex-conductor.ts +88 -0
  249. package/.versions/0.0.10/scripts/lib/codex-remote-control.ts +480 -0
  250. package/.versions/0.0.10/scripts/lib/coms-envelope.ts +582 -0
  251. package/.versions/0.0.10/scripts/lib/fake-herdr-server.ts +88 -0
  252. package/.versions/0.0.10/scripts/lib/fleet-command.ts +111 -0
  253. package/.versions/0.0.10/scripts/lib/herdr-layout.ts +281 -0
  254. package/.versions/0.0.10/scripts/lib/hermes-bridge-core.ts +241 -0
  255. package/.versions/0.0.10/scripts/lib/hermes-monitor-events.ts +1 -0
  256. package/.versions/0.0.10/scripts/lib/hermes-monitor-herdr.ts +2 -0
  257. package/.versions/0.0.10/scripts/lib/hermes-monitor-model.ts +3 -0
  258. package/.versions/0.0.10/scripts/lib/hermes-monitor-registry.ts +2 -0
  259. package/.versions/0.0.10/scripts/lib/hermes-monitor-socket.ts +2 -0
  260. package/.versions/0.0.10/scripts/lib/hermes-monitor-store.ts +2 -0
  261. package/.versions/0.0.10/scripts/lib/monitor-env.ts +120 -0
  262. package/.versions/0.0.10/scripts/lib/peer-launch.ts +314 -0
  263. package/.versions/0.0.10/scripts/lib/persona-banner.ts +62 -0
  264. package/.versions/0.0.10/scripts/lib/spawn-stagger.ts +101 -0
  265. package/.versions/0.0.10/scripts/lib/team-project.ts +193 -0
  266. package/.versions/0.0.10/scripts/lib/team-snapshot.ts +147 -0
  267. package/.versions/0.0.10/scripts/peer-banner.ts +40 -0
  268. package/.versions/0.0.10/scripts/peer-launch.ts +259 -0
  269. package/.versions/0.0.10/scripts/team-snapshot.ts +237 -0
  270. package/.versions/0.0.10/scripts/team-up.ts +360 -0
  271. package/.versions/0.0.10/skills/_internal/grilling.md +11 -0
  272. package/.versions/0.0.10/skills/browser-testing-with-devtools/SKILL.md +351 -0
  273. package/.versions/0.0.10/skills/code-review-and-quality/SKILL.md +381 -0
  274. package/.versions/0.0.10/skills/compound-learning/SKILL.md +137 -0
  275. package/.versions/0.0.10/skills/context-engineering/SKILL.md +291 -0
  276. package/.versions/0.0.10/skills/deprecation-and-migration/SKILL.md +206 -0
  277. package/.versions/0.0.10/skills/designing-agents/SKILL.md +394 -0
  278. package/.versions/0.0.10/skills/designing-agents/pi-harness-authoring.md +222 -0
  279. package/.versions/0.0.10/skills/frontend-ui-engineering/SKILL.md +328 -0
  280. package/.versions/0.0.10/skills/git-workflow-and-versioning/SKILL.md +316 -0
  281. package/.versions/0.0.10/skills/guided-workspace-setup/SKILL.md +226 -0
  282. package/.versions/0.0.10/skills/guided-workspace-setup/companion-manifest.json +38 -0
  283. package/.versions/0.0.10/skills/idea-refine/SKILL.md +182 -0
  284. package/.versions/0.0.10/skills/idea-refine/examples.md +238 -0
  285. package/.versions/0.0.10/skills/idea-refine/frameworks.md +99 -0
  286. package/.versions/0.0.10/skills/idea-refine/refinement-criteria.md +113 -0
  287. package/.versions/0.0.10/skills/idea-refine/scripts/idea-refine.sh +15 -0
  288. package/.versions/0.0.10/skills/incremental-implementation/SKILL.md +287 -0
  289. package/.versions/0.0.10/skills/interview-me/SKILL.md +226 -0
  290. package/.versions/0.0.10/skills/orchestration-verification/SKILL.md +181 -0
  291. package/.versions/0.0.10/skills/peer-coms/SKILL.md +90 -0
  292. package/.versions/0.0.10/skills/performance-optimization/SKILL.md +350 -0
  293. package/.versions/0.0.10/skills/planning-and-task-breakdown/SKILL.md +254 -0
  294. package/.versions/0.0.10/skills/security-and-hardening/SKILL.md +461 -0
  295. package/.versions/0.0.10/skills/spec-driven-development/SKILL.md +257 -0
  296. package/.versions/0.0.10/skills/using-agent-skills/SKILL.md +199 -0
  297. package/.versions/0.0.10/systemd/user/agent-fleet-codex-remote-control.service.in +23 -0
  298. package/.versions/0.0.10/vendor/agent-skills-upstream/LICENSE +21 -0
  299. package/.versions/0.0.10/vendor/agent-skills-upstream/README.md +11 -0
  300. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/api-and-interface-design/SKILL.md +294 -0
  301. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/browser-testing-with-devtools/SKILL.md +317 -0
  302. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/ci-cd-and-automation/SKILL.md +390 -0
  303. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/code-review-and-quality/SKILL.md +396 -0
  304. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/code-simplification/SKILL.md +331 -0
  305. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/context-engineering/SKILL.md +289 -0
  306. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/debugging-and-error-recovery/SKILL.md +300 -0
  307. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/deprecation-and-migration/SKILL.md +247 -0
  308. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/documentation-and-adrs/SKILL.md +278 -0
  309. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/doubt-driven-development/SKILL.md +243 -0
  310. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/frontend-ui-engineering/SKILL.md +328 -0
  311. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/git-workflow-and-versioning/SKILL.md +355 -0
  312. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/idea-refine/SKILL.md +178 -0
  313. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/idea-refine/examples.md +238 -0
  314. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/idea-refine/frameworks.md +99 -0
  315. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/idea-refine/refinement-criteria.md +113 -0
  316. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/idea-refine/scripts/idea-refine.sh +15 -0
  317. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/incremental-implementation/SKILL.md +249 -0
  318. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/interview-me/SKILL.md +225 -0
  319. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/observability-and-instrumentation/SKILL.md +203 -0
  320. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/performance-optimization/SKILL.md +350 -0
  321. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/planning-and-task-breakdown/SKILL.md +234 -0
  322. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/security-and-hardening/SKILL.md +467 -0
  323. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/shipping-and-launch/SKILL.md +310 -0
  324. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/source-driven-development/SKILL.md +194 -0
  325. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/spec-driven-development/SKILL.md +206 -0
  326. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/test-driven-development/SKILL.md +383 -0
  327. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/using-agent-skills/SKILL.md +191 -0
  328. package/.versions/0.0.11/.claude/commands/build.md +44 -0
  329. package/.versions/0.0.11/.claude/commands/code-simplify.md +22 -0
  330. package/.versions/0.0.11/.claude/commands/design-agent.md +14 -0
  331. package/.versions/0.0.11/.claude/commands/doctor-agent-fleet.md +22 -0
  332. package/.versions/0.0.11/.claude/commands/orchestrate.md +112 -0
  333. package/.versions/0.0.11/.claude/commands/plan.md +16 -0
  334. package/.versions/0.0.11/.claude/commands/prime.md +22 -0
  335. package/.versions/0.0.11/.claude/commands/review.md +16 -0
  336. package/.versions/0.0.11/.claude/commands/set-hermes-telegram.md +15 -0
  337. package/.versions/0.0.11/.claude/commands/set-hermes-watchdog.md +6 -0
  338. package/.versions/0.0.11/.claude/commands/setup-agent-fleet.md +17 -0
  339. package/.versions/0.0.11/.claude/commands/ship.md +72 -0
  340. package/.versions/0.0.11/.claude/commands/spec.md +15 -0
  341. package/.versions/0.0.11/.claude/commands/test.md +19 -0
  342. package/.versions/0.0.11/.claude/commands/webperf.md +32 -0
  343. package/.versions/0.0.11/.claude/orchestrate-teams.yaml +24 -0
  344. package/.versions/0.0.11/.opencode/commands/af-build.md +17 -0
  345. package/.versions/0.0.11/.opencode/commands/af-code-simplify.md +16 -0
  346. package/.versions/0.0.11/.opencode/commands/af-compound.md +16 -0
  347. package/.versions/0.0.11/.opencode/commands/af-design-agent.md +15 -0
  348. package/.versions/0.0.11/.opencode/commands/af-doctor-agent-fleet.md +22 -0
  349. package/.versions/0.0.11/.opencode/commands/af-orchestrate.md +112 -0
  350. package/.versions/0.0.11/.opencode/commands/af-plan.md +16 -0
  351. package/.versions/0.0.11/.opencode/commands/af-prime.md +22 -0
  352. package/.versions/0.0.11/.opencode/commands/af-review.md +15 -0
  353. package/.versions/0.0.11/.opencode/commands/af-set-hermes-telegram.md +15 -0
  354. package/.versions/0.0.11/.opencode/commands/af-set-hermes-watchdog.md +6 -0
  355. package/.versions/0.0.11/.opencode/commands/af-setup-agent-fleet.md +17 -0
  356. package/.versions/0.0.11/.opencode/commands/af-ship.md +16 -0
  357. package/.versions/0.0.11/.opencode/commands/af-spec.md +16 -0
  358. package/.versions/0.0.11/.opencode/commands/af-test.md +21 -0
  359. package/.versions/0.0.11/.opencode/commands/af-webperf.md +32 -0
  360. package/.versions/0.0.11/.opencode/orchestrate-teams.yaml +24 -0
  361. package/.versions/0.0.11/.pi/agents/dispatch-policy.yaml +32 -0
  362. package/.versions/0.0.11/.pi/agents/model-profiles.yaml +27 -0
  363. package/.versions/0.0.11/.pi/agents/peers.yaml +142 -0
  364. package/.versions/0.0.11/.pi/agents/teams.yaml +41 -0
  365. package/.versions/0.0.11/.pi/damage-control-rules.yaml +297 -0
  366. package/.versions/0.0.11/.pi/extensions/agent-fleet-update-check/README.md +57 -0
  367. package/.versions/0.0.11/.pi/extensions/agent-fleet-update-check/index.ts +161 -0
  368. package/.versions/0.0.11/.pi/extensions/agent-fleet-update-check/package.json +6 -0
  369. package/.versions/0.0.11/.pi/extensions/btw/README.md +119 -0
  370. package/.versions/0.0.11/.pi/extensions/btw/index.ts +917 -0
  371. package/.versions/0.0.11/.pi/extensions/btw/package.json +6 -0
  372. package/.versions/0.0.11/.pi/extensions/btw/state.js +179 -0
  373. package/.versions/0.0.11/.pi/extensions/chrome-devtools-mcp/README.md +55 -0
  374. package/.versions/0.0.11/.pi/extensions/chrome-devtools-mcp/index.ts +93 -0
  375. package/.versions/0.0.11/.pi/extensions/chrome-devtools-mcp/package.json +6 -0
  376. package/.versions/0.0.11/.pi/extensions/compact-and-continue/README.md +42 -0
  377. package/.versions/0.0.11/.pi/extensions/compact-and-continue/index.ts +120 -0
  378. package/.versions/0.0.11/.pi/extensions/compact-and-continue/package.json +6 -0
  379. package/.versions/0.0.11/.pi/extensions/mcp-bridge/README.md +46 -0
  380. package/.versions/0.0.11/.pi/extensions/mcp-bridge/index.ts +206 -0
  381. package/.versions/0.0.11/.pi/extensions/mcp-bridge/package.json +6 -0
  382. package/.versions/0.0.11/.pi/extensions/package-lock.json +1143 -0
  383. package/.versions/0.0.11/.pi/extensions/package.json +9 -0
  384. package/.versions/0.0.11/.pi/extensions/pi-voice-stt/README.md +204 -0
  385. package/.versions/0.0.11/.pi/extensions/pi-voice-stt/config.ts +198 -0
  386. package/.versions/0.0.11/.pi/extensions/pi-voice-stt/examples/stt.json +35 -0
  387. package/.versions/0.0.11/.pi/extensions/pi-voice-stt/index.ts +248 -0
  388. package/.versions/0.0.11/.pi/extensions/pi-voice-stt/package.json +6 -0
  389. package/.versions/0.0.11/.pi/extensions/pi-voice-stt/providers.ts +214 -0
  390. package/.versions/0.0.11/.pi/extensions/pi-voice-stt/recorder.ts +158 -0
  391. package/.versions/0.0.11/.pi/harnesses/agent-hub/README.md +1004 -0
  392. package/.versions/0.0.11/.pi/harnesses/agent-hub/access-approval.ts +135 -0
  393. package/.versions/0.0.11/.pi/harnesses/agent-hub/artifacts.js +146 -0
  394. package/.versions/0.0.11/.pi/harnesses/agent-hub/assertion-ledger.js +58 -0
  395. package/.versions/0.0.11/.pi/harnesses/agent-hub/backend-policy.js +153 -0
  396. package/.versions/0.0.11/.pi/harnesses/agent-hub/context-window.js +106 -0
  397. package/.versions/0.0.11/.pi/harnesses/agent-hub/delegate.ts +435 -0
  398. package/.versions/0.0.11/.pi/harnesses/agent-hub/docs-lane.js +122 -0
  399. package/.versions/0.0.11/.pi/harnesses/agent-hub/drift-watchdog.js +211 -0
  400. package/.versions/0.0.11/.pi/harnesses/agent-hub/evidence-rules.js +96 -0
  401. package/.versions/0.0.11/.pi/harnesses/agent-hub/external-blocker.js +85 -0
  402. package/.versions/0.0.11/.pi/harnesses/agent-hub/footer.ts +31 -0
  403. package/.versions/0.0.11/.pi/harnesses/agent-hub/helpers.ts +248 -0
  404. package/.versions/0.0.11/.pi/harnesses/agent-hub/index.ts +9111 -0
  405. package/.versions/0.0.11/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
  406. package/.versions/0.0.11/.pi/harnesses/agent-hub/monitor-invoke-journal.ts +131 -0
  407. package/.versions/0.0.11/.pi/harnesses/agent-hub/monitor-invoke.ts +92 -0
  408. package/.versions/0.0.11/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
  409. package/.versions/0.0.11/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
  410. package/.versions/0.0.11/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
  411. package/.versions/0.0.11/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
  412. package/.versions/0.0.11/.pi/harnesses/agent-hub/monitor-session-bridge.ts +257 -0
  413. package/.versions/0.0.11/.pi/harnesses/agent-hub/package.json +7 -0
  414. package/.versions/0.0.11/.pi/harnesses/agent-hub/provider-semaphore.js +138 -0
  415. package/.versions/0.0.11/.pi/harnesses/agent-hub/research-retention.js +34 -0
  416. package/.versions/0.0.11/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
  417. package/.versions/0.0.11/.pi/harnesses/agent-hub/return-contract.js +293 -0
  418. package/.versions/0.0.11/.pi/harnesses/agent-hub/return-extract.js +75 -0
  419. package/.versions/0.0.11/.pi/harnesses/agent-hub/review-findings.js +102 -0
  420. package/.versions/0.0.11/.pi/harnesses/agent-hub/run-budget.js +479 -0
  421. package/.versions/0.0.11/.pi/harnesses/agent-hub/run-namespace.js +87 -0
  422. package/.versions/0.0.11/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
  423. package/.versions/0.0.11/.pi/harnesses/agent-hub/scope-gate.js +103 -0
  424. package/.versions/0.0.11/.pi/harnesses/agent-hub/session-health.js +110 -0
  425. package/.versions/0.0.11/.pi/harnesses/agent-hub/spawn.ts +354 -0
  426. package/.versions/0.0.11/.pi/harnesses/agent-hub/version.ts +42 -0
  427. package/.versions/0.0.11/.pi/harnesses/ask-user-remote/README.md +19 -0
  428. package/.versions/0.0.11/.pi/harnesses/ask-user-remote/index.ts +321 -0
  429. package/.versions/0.0.11/.pi/harnesses/ask-user-remote/race-core.js +106 -0
  430. package/.versions/0.0.11/.pi/harnesses/coms/README.md +100 -0
  431. package/.versions/0.0.11/.pi/harnesses/coms/index.ts +1767 -0
  432. package/.versions/0.0.11/.pi/harnesses/coms/package.json +7 -0
  433. package/.versions/0.0.11/.pi/harnesses/coms/version.ts +42 -0
  434. package/.versions/0.0.11/.pi/harnesses/damage-control-continue/README.md +124 -0
  435. package/.versions/0.0.11/.pi/harnesses/damage-control-continue/index.ts +536 -0
  436. package/.versions/0.0.11/.pi/harnesses/damage-control-continue/package.json +7 -0
  437. package/.versions/0.0.11/.pi/harnesses/damage-control-continue/version.ts +42 -0
  438. package/.versions/0.0.11/.pi/harnesses/lib/coms-registry-entry.ts +94 -0
  439. package/.versions/0.0.11/.pi/harnesses/lib/damage-control-shared.ts +197 -0
  440. package/.versions/0.0.11/.pi/harnesses/lib/herdr-client.ts +472 -0
  441. package/.versions/0.0.11/.pi/harnesses/lib/herdr-presence.ts +399 -0
  442. package/.versions/0.0.11/.pi/harnesses/lib/hermes-monitor-events.ts +136 -0
  443. package/.versions/0.0.11/.pi/harnesses/lib/hermes-monitor-herdr.ts +28 -0
  444. package/.versions/0.0.11/.pi/harnesses/lib/hermes-monitor-model.ts +18 -0
  445. package/.versions/0.0.11/.pi/harnesses/lib/hermes-monitor-registry.ts +6 -0
  446. package/.versions/0.0.11/.pi/harnesses/lib/hermes-monitor-socket.ts +163 -0
  447. package/.versions/0.0.11/.pi/harnesses/lib/hermes-monitor-store.ts +31 -0
  448. package/.versions/0.0.11/.pi/harnesses/lib/spawned-peers.js +190 -0
  449. package/.versions/0.0.11/.pi/harnesses/package-lock.json +35 -0
  450. package/.versions/0.0.11/.pi/harnesses/package.json +9 -0
  451. package/.versions/0.0.11/.pi/prompts/af-build.md +24 -0
  452. package/.versions/0.0.11/.pi/prompts/af-code-simplify.md +22 -0
  453. package/.versions/0.0.11/.pi/prompts/af-doctor-agent-fleet.md +22 -0
  454. package/.versions/0.0.11/.pi/prompts/af-plan.md +16 -0
  455. package/.versions/0.0.11/.pi/prompts/af-review.md +16 -0
  456. package/.versions/0.0.11/.pi/prompts/af-set-hermes-telegram.md +15 -0
  457. package/.versions/0.0.11/.pi/prompts/af-set-hermes-watchdog.md +6 -0
  458. package/.versions/0.0.11/.pi/prompts/af-setup-agent-fleet.md +19 -0
  459. package/.versions/0.0.11/.pi/prompts/af-ship.md +17 -0
  460. package/.versions/0.0.11/.pi/prompts/af-spec.md +15 -0
  461. package/.versions/0.0.11/.pi/prompts/af-test.md +19 -0
  462. package/.versions/0.0.11/.pi/skills/bowser/SKILL.md +145 -0
  463. package/.versions/0.0.11/.version +1 -0
  464. package/.versions/0.0.11/agents/architect.md +24 -0
  465. package/.versions/0.0.11/agents/bowser.md +27 -0
  466. package/.versions/0.0.11/agents/builder.md +54 -0
  467. package/.versions/0.0.11/agents/code-reviewer.md +208 -0
  468. package/.versions/0.0.11/agents/deep-researcher.md +32 -0
  469. package/.versions/0.0.11/agents/documenter.md +18 -0
  470. package/.versions/0.0.11/agents/orchestrator.md +72 -0
  471. package/.versions/0.0.11/agents/plan-reviewer.md +83 -0
  472. package/.versions/0.0.11/agents/planner.md +70 -0
  473. package/.versions/0.0.11/agents/releaser.md +24 -0
  474. package/.versions/0.0.11/agents/researcher.md +28 -0
  475. package/.versions/0.0.11/agents/security-auditor.md +167 -0
  476. package/.versions/0.0.11/agents/test-engineer.md +153 -0
  477. package/.versions/0.0.11/agents/web-debugger.md +43 -0
  478. package/.versions/0.0.11/agents/web-performance-auditor.md +193 -0
  479. package/.versions/0.0.11/codex/CONDUCTOR.md +148 -0
  480. package/.versions/0.0.11/docs/ARCHITECTURE.md +303 -0
  481. package/.versions/0.0.11/docs/agent-fleet-setup.md +377 -0
  482. package/.versions/0.0.11/docs/claude-code-coms-bridge.md +109 -0
  483. package/.versions/0.0.11/docs/codex-remote-conductor.md +170 -0
  484. package/.versions/0.0.11/docs/coms-hermes-bridge.md +189 -0
  485. package/.versions/0.0.11/docs/getting-started.md +254 -0
  486. package/.versions/0.0.11/docs/npm-install.md +514 -0
  487. package/.versions/0.0.11/docs/opencode-setup.md +281 -0
  488. package/.versions/0.0.11/docs/pi-extensions.md +368 -0
  489. package/.versions/0.0.11/docs/pi-setup.md +571 -0
  490. package/.versions/0.0.11/docs/skill-anatomy.md +150 -0
  491. package/.versions/0.0.11/hermes/README.md +347 -0
  492. package/.versions/0.0.11/hermes/desktop-plugins/agent-fleet-herdr/plugin.js +1291 -0
  493. package/.versions/0.0.11/hermes/desktop-plugins/agent-fleet-herdr/presentation.js +672 -0
  494. package/.versions/0.0.11/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
  495. package/.versions/0.0.11/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
  496. package/.versions/0.0.11/hermes/gates/gate-o-capability.md +8 -0
  497. package/.versions/0.0.11/hermes/gates/gate-o-validator-fixtures.json +1 -0
  498. package/.versions/0.0.11/hermes/plugins/agent-fleet-herdr/dashboard/activity.py +770 -0
  499. package/.versions/0.0.11/hermes/plugins/agent-fleet-herdr/dashboard/coms_registry.py +134 -0
  500. package/.versions/0.0.11/hermes/plugins/agent-fleet-herdr/dashboard/coms_send.py +350 -0
  501. package/.versions/0.0.11/hermes/plugins/agent-fleet-herdr/dashboard/herdr_source.py +193 -0
  502. package/.versions/0.0.11/hermes/plugins/agent-fleet-herdr/dashboard/manifest.json +4 -0
  503. package/.versions/0.0.11/hermes/plugins/agent-fleet-herdr/dashboard/plugin_api.py +444 -0
  504. package/.versions/0.0.11/hermes/plugins/agent-fleet-herdr/dashboard/sessions.py +205 -0
  505. package/.versions/0.0.11/hermes/plugins/agent-fleet-herdr/dashboard/tasks.py +300 -0
  506. package/.versions/0.0.11/hermes/plugins/agent-fleet-herdr/dashboard/watch.py +819 -0
  507. package/.versions/0.0.11/hermes/plugins/agent-fleet-herdr/plugin.yaml +8 -0
  508. package/.versions/0.0.11/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +139 -0
  509. package/.versions/0.0.11/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
  510. package/.versions/0.0.11/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
  511. package/.versions/0.0.11/hermes/skills/hub-conductor/SKILL.md +84 -0
  512. package/.versions/0.0.11/hermes/skills/hub-liaison/SKILL.md +84 -0
  513. package/.versions/0.0.11/hermes/skills/hub-watchdog/SKILL.md +76 -0
  514. package/.versions/0.0.11/hermes/skills/hub-watchdog/manifest.json +1 -0
  515. package/.versions/0.0.11/hermes/skills/hub-watchdog/scripts/watchdog.py +249 -0
  516. package/.versions/0.0.11/hermes/skills/hub-watchdog/scripts/watchdog_actions.py +124 -0
  517. package/.versions/0.0.11/hermes/skills/hub-watchdog/scripts/watchdog_contract.py +76 -0
  518. package/.versions/0.0.11/hermes/skills/hub-watchdog/scripts/watchdog_delivery.py +10 -0
  519. package/.versions/0.0.11/hermes/skills/hub-watchdog/scripts/watchdog_engine.py +128 -0
  520. package/.versions/0.0.11/hermes/skills/hub-watchdog/scripts/watchdog_judgment.py +41 -0
  521. package/.versions/0.0.11/hermes/skills/hub-watchdog/scripts/watchdog_recovery.py +103 -0
  522. package/.versions/0.0.11/hermes/skills/hub-watchdog/scripts/watchdog_state.py +163 -0
  523. package/.versions/0.0.11/hermes/skills/hub-watchdog/scripts/watchdog_transport.py +138 -0
  524. package/.versions/0.0.11/hermes/watchdog-tests/__init__.py +0 -0
  525. package/.versions/0.0.11/hooks/SIMPLIFY-IGNORE.md +90 -0
  526. package/.versions/0.0.11/hooks/coms-stop-hook.mjs +84 -0
  527. package/.versions/0.0.11/hooks/hooks.json +14 -0
  528. package/.versions/0.0.11/hooks/session-start.sh +74 -0
  529. package/.versions/0.0.11/hooks/simplify-ignore.sh +302 -0
  530. package/.versions/0.0.11/install-manifest.json +3615 -0
  531. package/.versions/0.0.11/justfile +254 -0
  532. package/.versions/0.0.11/manifest-meta.json +472 -0
  533. package/.versions/0.0.11/references/accessibility-checklist.md +160 -0
  534. package/.versions/0.0.11/references/definition-of-done.md +67 -0
  535. package/.versions/0.0.11/references/fleet-coordination-patterns.md +151 -0
  536. package/.versions/0.0.11/references/observability-checklist.md +91 -0
  537. package/.versions/0.0.11/references/orchestration-patterns.md +370 -0
  538. package/.versions/0.0.11/references/performance-checklist.md +153 -0
  539. package/.versions/0.0.11/references/prompting-patterns.md +380 -0
  540. package/.versions/0.0.11/references/security-checklist.md +179 -0
  541. package/.versions/0.0.11/references/testing-patterns.md +236 -0
  542. package/.versions/0.0.11/scripts/codex-conductor.ts +41 -0
  543. package/.versions/0.0.11/scripts/codex-remote-control.ts +167 -0
  544. package/.versions/0.0.11/scripts/coms-claude-bridge.ts +401 -0
  545. package/.versions/0.0.11/scripts/coms-cli.ts +484 -0
  546. package/.versions/0.0.11/scripts/coms-hermes-bridge.ts +413 -0
  547. package/.versions/0.0.11/scripts/fleet.ts +168 -0
  548. package/.versions/0.0.11/scripts/hermes-monitor-capability-runner.ts +25 -0
  549. package/.versions/0.0.11/scripts/hermes-monitor-scenario.ts +474 -0
  550. package/.versions/0.0.11/scripts/hermes-watchdog-capability-probe.ts +45 -0
  551. package/.versions/0.0.11/scripts/install-hermes-plugin.sh +180 -0
  552. package/.versions/0.0.11/scripts/lib/claude-bridge-core.ts +165 -0
  553. package/.versions/0.0.11/scripts/lib/codex-conductor.ts +88 -0
  554. package/.versions/0.0.11/scripts/lib/codex-remote-control.ts +480 -0
  555. package/.versions/0.0.11/scripts/lib/coms-envelope.ts +582 -0
  556. package/.versions/0.0.11/scripts/lib/fake-herdr-server.ts +88 -0
  557. package/.versions/0.0.11/scripts/lib/fleet-command.ts +111 -0
  558. package/.versions/0.0.11/scripts/lib/herdr-layout.ts +281 -0
  559. package/.versions/0.0.11/scripts/lib/hermes-bridge-core.ts +241 -0
  560. package/.versions/0.0.11/scripts/lib/hermes-monitor-events.ts +1 -0
  561. package/.versions/0.0.11/scripts/lib/hermes-monitor-herdr.ts +2 -0
  562. package/.versions/0.0.11/scripts/lib/hermes-monitor-model.ts +3 -0
  563. package/.versions/0.0.11/scripts/lib/hermes-monitor-registry.ts +2 -0
  564. package/.versions/0.0.11/scripts/lib/hermes-monitor-socket.ts +2 -0
  565. package/.versions/0.0.11/scripts/lib/hermes-monitor-store.ts +2 -0
  566. package/.versions/0.0.11/scripts/lib/monitor-env.ts +134 -0
  567. package/.versions/0.0.11/scripts/lib/peer-launch.ts +314 -0
  568. package/.versions/0.0.11/scripts/lib/persona-banner.ts +62 -0
  569. package/.versions/0.0.11/scripts/lib/spawn-stagger.ts +101 -0
  570. package/.versions/0.0.11/scripts/lib/team-project.ts +193 -0
  571. package/.versions/0.0.11/scripts/lib/team-snapshot.ts +147 -0
  572. package/.versions/0.0.11/scripts/peer-banner.ts +40 -0
  573. package/.versions/0.0.11/scripts/peer-launch.ts +259 -0
  574. package/.versions/0.0.11/scripts/team-snapshot.ts +237 -0
  575. package/.versions/0.0.11/scripts/team-up.ts +360 -0
  576. package/.versions/0.0.11/skills/_internal/grilling.md +11 -0
  577. package/.versions/0.0.11/skills/browser-testing-with-devtools/SKILL.md +351 -0
  578. package/.versions/0.0.11/skills/code-review-and-quality/SKILL.md +381 -0
  579. package/.versions/0.0.11/skills/compound-learning/SKILL.md +137 -0
  580. package/.versions/0.0.11/skills/context-engineering/SKILL.md +291 -0
  581. package/.versions/0.0.11/skills/deprecation-and-migration/SKILL.md +206 -0
  582. package/.versions/0.0.11/skills/designing-agents/SKILL.md +394 -0
  583. package/.versions/0.0.11/skills/designing-agents/pi-harness-authoring.md +222 -0
  584. package/.versions/0.0.11/skills/frontend-ui-engineering/SKILL.md +328 -0
  585. package/.versions/0.0.11/skills/git-workflow-and-versioning/SKILL.md +316 -0
  586. package/.versions/0.0.11/skills/guided-workspace-setup/SKILL.md +226 -0
  587. package/.versions/0.0.11/skills/guided-workspace-setup/companion-manifest.json +38 -0
  588. package/.versions/0.0.11/skills/idea-refine/SKILL.md +182 -0
  589. package/.versions/0.0.11/skills/idea-refine/examples.md +238 -0
  590. package/.versions/0.0.11/skills/idea-refine/frameworks.md +99 -0
  591. package/.versions/0.0.11/skills/idea-refine/refinement-criteria.md +113 -0
  592. package/.versions/0.0.11/skills/idea-refine/scripts/idea-refine.sh +15 -0
  593. package/.versions/0.0.11/skills/incremental-implementation/SKILL.md +287 -0
  594. package/.versions/0.0.11/skills/interview-me/SKILL.md +226 -0
  595. package/.versions/0.0.11/skills/orchestration-verification/SKILL.md +181 -0
  596. package/.versions/0.0.11/skills/peer-coms/SKILL.md +90 -0
  597. package/.versions/0.0.11/skills/performance-optimization/SKILL.md +350 -0
  598. package/.versions/0.0.11/skills/planning-and-task-breakdown/SKILL.md +254 -0
  599. package/.versions/0.0.11/skills/security-and-hardening/SKILL.md +461 -0
  600. package/.versions/0.0.11/skills/spec-driven-development/SKILL.md +257 -0
  601. package/.versions/0.0.11/skills/using-agent-skills/SKILL.md +199 -0
  602. package/.versions/0.0.11/systemd/user/agent-fleet-codex-remote-control.service.in +23 -0
  603. package/.versions/0.0.11/vendor/agent-skills-upstream/LICENSE +21 -0
  604. package/.versions/0.0.11/vendor/agent-skills-upstream/README.md +11 -0
  605. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/api-and-interface-design/SKILL.md +294 -0
  606. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/browser-testing-with-devtools/SKILL.md +317 -0
  607. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/ci-cd-and-automation/SKILL.md +390 -0
  608. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/code-review-and-quality/SKILL.md +396 -0
  609. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/code-simplification/SKILL.md +331 -0
  610. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/context-engineering/SKILL.md +289 -0
  611. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/debugging-and-error-recovery/SKILL.md +300 -0
  612. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/deprecation-and-migration/SKILL.md +247 -0
  613. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/documentation-and-adrs/SKILL.md +278 -0
  614. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/doubt-driven-development/SKILL.md +243 -0
  615. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/frontend-ui-engineering/SKILL.md +328 -0
  616. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/git-workflow-and-versioning/SKILL.md +355 -0
  617. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/idea-refine/SKILL.md +178 -0
  618. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/idea-refine/examples.md +238 -0
  619. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/idea-refine/frameworks.md +99 -0
  620. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/idea-refine/refinement-criteria.md +113 -0
  621. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/idea-refine/scripts/idea-refine.sh +15 -0
  622. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/incremental-implementation/SKILL.md +249 -0
  623. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/interview-me/SKILL.md +225 -0
  624. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/observability-and-instrumentation/SKILL.md +203 -0
  625. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/performance-optimization/SKILL.md +350 -0
  626. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/planning-and-task-breakdown/SKILL.md +234 -0
  627. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/security-and-hardening/SKILL.md +467 -0
  628. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/shipping-and-launch/SKILL.md +310 -0
  629. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/source-driven-development/SKILL.md +194 -0
  630. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/spec-driven-development/SKILL.md +206 -0
  631. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/test-driven-development/SKILL.md +383 -0
  632. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/using-agent-skills/SKILL.md +191 -0
  633. package/CHANGELOG.md +110 -0
  634. package/README.md +22 -5
  635. package/agents/code-reviewer.md +4 -0
  636. package/agents/orchestrator.md +7 -1
  637. package/agents/plan-reviewer.md +22 -1
  638. package/bin/build-manifest.js +68 -0
  639. package/bin/cli.js +679 -49
  640. package/bin/lib/apply.js +641 -0
  641. package/bin/lib/manifest.js +731 -0
  642. package/bin/lib/merge-forms.js +106 -0
  643. package/bin/lib/plan.js +569 -0
  644. package/bin/lib/state.js +213 -0
  645. package/bin/lib/verify.js +576 -0
  646. package/bin/snapshot-version.js +5 -0
  647. package/docs/ARCHITECTURE.md +52 -11
  648. package/docs/agent-fleet-setup.md +59 -48
  649. package/docs/getting-started.md +29 -6
  650. package/docs/npm-install.md +208 -31
  651. package/docs/opencode-setup.md +32 -0
  652. package/docs/pi-extensions.md +22 -10
  653. package/docs/pi-setup.md +164 -69
  654. package/install-manifest.json +3615 -0
  655. package/manifest-meta.json +472 -0
  656. package/package.json +8 -3
  657. package/scripts/lib/monitor-env.ts +15 -1
  658. package/skills/browser-testing-with-devtools/SKILL.md +3 -4
  659. package/skills/guided-workspace-setup/SKILL.md +172 -490
  660. package/skills/planning-and-task-breakdown/SKILL.md +18 -0
  661. package/skills/spec-driven-development/SKILL.md +12 -0
@@ -2,16 +2,21 @@
2
2
  description: Scan agent-fleet install targets for broken symlinks, stale persona references, and overrides-file problems, then offer repairs
3
3
  ---
4
4
 
5
- Invoke the Doctor scan from the `agent-fleet:guided-workspace-setup` skill — Step 5 (the preflight scan) — without running the rest of the install flow. Use this when the user wants the repair pass on its own; the full `/setup-agent-fleet` flow runs the same scan automatically as soon as it detects prior install state.
5
+ Run the repair pass on its own. `/setup-agent-fleet` offers the same thing as soon as it finds prior install state; this command is when the user wants only that.
6
6
 
7
- Walk every install-target directory the chosen coding agent uses (`agents/`, `.claude/agents/`, `.opencode/agent/` (+ legacy `.opencode/agents/`), `.pi/agents/`, `.claude/skills/`, `.opencode/skills/`, `.pi/skills/`, `.agents/skills`, `.claude/commands/`, `.opencode/commands/`, `.pi/prompts/`, `.claude/references/`, `.claude/hooks/`). For each broken symlink, resolve where it pointed, look for a canonical replacement in the source `agents/` and `skills/` trees, and offer to repair or delete (persona links under `.claude/agents/` and `.opencode/agent(s)/` are repaired by regenerating a transformed copy via `transform-persona`, not by re-symlinking the raw source). Common stale names from the pre-merge persona layout: `reviewer` → `code-reviewer`, `red-team` → `security-auditor`.
7
+ Run the CLI — do not walk directories or repair files yourself:
8
8
 
9
- Also flag and offer to rewrite any remaining YAML configs (`teams.yaml`, `peers.yaml`, etc.) that still reference removed persona names.
9
+ ```
10
+ node <source-root>/bin/cli.js doctor --workspace <workspace> [--agent <agent>] --json
11
+ ```
10
12
 
11
- Also flag malformed peer entries in `.pi/agents/peers.yaml`: field lines (`persona:`, `model:`, ...) that sit under a team heading before any `- name: ...` list item. The team-up launcher's minimal parser silently drops such lines, so the peer never spawns and nothing errors — the usual cause is a `- name:` line lost in an edit. These findings are advisory only: report them with the missing `- name: <peer>` suggestion, never rewrite the file.
13
+ Resolve `<source-root>` from `<workspace>/.ai/.agent-fleet-bootstrap.json`, or this command's realpath if it is a symlink, or by asking. Never scan the filesystem for agent-fleet clones.
12
14
 
13
- Also validate `.ai/agent-fleet-overrides.md` when it exists, against the schema in `docs/agent-fleet-setup.md`: unknown sections, unknown keys in known sections, invalid values for the mechanically parsed `agent-hub` keys, missing `rules:` folders and `docs:` entry points, and `## env` `required:` names that are neither set nor declared in the root `.env`. These findings are advisory only — report them with fix "edit by hand", never edit the overrides file.
15
+ The report has two halves, and they are repaired differently on purpose:
14
16
 
15
- Present the findings per the skill's Step 1 interaction contract: print a short text summary (counts per kind, advisory findings as report-only text), then ask one `AskUserQuestion` multi-select — *"Which fixes should I apply now?"* — each option titled `<path> — <issue>` with the proposed fix as its description, chunked at ≤ 4 options per question; an empty selection applies nothing.
17
+ - `repairs` — recorded items that are missing, dangling, or linked outside the source root. These are rebuilt through the same `apply()` path `install` writes with, so a repaired file is byte-identical to a freshly installed one.
18
+ - `findings` — what the install record cannot own: broken symlinks in a pre-engine workspace, stale persona names in `.pi/agents/*.yaml` (`reviewer` → `code-reviewer`, `red-team` → `security-auditor`), plus advisory ones. `overrides` and `yaml-shape` findings are **advisory**: report them with "edit by hand" and never fix them, because the fix is always a hand edit of the flagged file.
16
19
 
17
- Never overwrite a regular file — only act on symlinks whose target is missing. Report `repaired`, `deleted`, and `skipped` counts, and append a `## doctor-runs` line to `.ai/agent-fleet-setup.md` with the date, agent, phase (`standalone`), and counts.
20
+ Print the two lists as text, then ask one `AskUserQuestion` — *"Apply the suggested fixes?"* — and on yes re-run with `--fix`. An empty answer or a cancel applies nothing.
21
+
22
+ Exit codes: `0` nothing to repair, `2` repairable issues found (or advisories present, or a repair failed), `1` could not run. Report the counts the CLI returns; do not invent your own.
@@ -2,24 +2,16 @@
2
2
  description: Guided setup — install agent-fleet artifacts into a workspace for a chosen coding agent
3
3
  ---
4
4
 
5
- Invoke the agent-fleet:guided-workspace-setup skill.
5
+ Invoke the agent-fleet:guided-workspace-setup skill and follow it.
6
6
 
7
- Run the guided install for a target workspace. If the user passed a workspace path, use it; otherwise ask for it. Detect the running coding agent and confirm it with the user.
7
+ Run the guided install for a target workspace. If the user passed a workspace path, use it; otherwise ask. Confirm the coding agent (`claude-code` here unless the user says otherwise).
8
8
 
9
- Analyse the workspace. If prior install state is found (`.ai/agent-fleet-setup.md` or a populated agent directory), run the **Doctor preflight** first (Step 5) — scan for broken symlinks and stale persona references, present findings as a table, and apply the fixes the user picks before continuing.
9
+ The skill is a front-end over the `agent-fleet` CLI's installer engine: `verify --json` supplies the menu (groups, profiles, per-item state), and `install` / `upgrade` / `uninstall` / `doctor --fix` do every write. **Do not copy, symlink, or delete an install target yourself** — the CLI records ownership in `.ai/agent-fleet-state.json`, and anything written by hand is invisible to every later run. Artifacts install as copies; never ask copy-vs-symlink and never pass `--method`.
10
10
 
11
- The Skills group draws from **two roots**: fleet-native `skills/` and the vendored upstream import `vendor/agent-skills-upstream/skills/` (see `docs/UPSTREAM-SKILLS.md`). On a name collision the native copy wins — never offer the vendored duplicate as a separate row.
11
+ Two things are yours rather than the CLI's: drafting `.ai/agent-fleet-overrides.md` from a scan of the project, and the `pi-voice-stt` provider Q&A.
12
12
 
13
- Then present the install menu per the skill's Step 1 interaction contract — drive every decision through `AskUserQuestion`, never a printed table awaiting a free-text reply. Open with the **Express question** (fresh workspace: `Recommended ★` / `Everything` / `Custom — group by group` / `Nothing`; existing: `Keep as-is` / `Apply updates` / `Keep + add recommended ★` / `Custom`) — any answer but `Custom` skips all group screens. On `Custom`, run the **7 groups** (4 shared: Skills, Agent personas, Commands/prompts, References & Hooks; 3 pi-only — a claude-code workspace sees just the 4 shared groups): each opens as a single-select quick screen (`Recommended ★ (n)` / `Everything (m)` / `Customise` / `Skip group`, or the installed-state variants with `Remove some…`), and multi-select drill-ins appear only behind `Customise`, chunked by sub-category (lifecycle phase for Skills, `rw`/`ro` for personas, …) at ≤ 4 options per question. Option titles carry `name ★ [st]` (`ok`/`upd`/`mod`/`cflt`/`gone`/`new`/`—`/`brk`); descriptions carry the purpose plus the state in plain words (`mod` → warn that refreshing overwrites local edits). There is **no pre-checking** — installed state shows as counts on quick screens and words in descriptions; leaving an installed item unselected in a drill-in keeps it as-is. `recommended` adds `★` items on top of what is installed — it never removes; cancel = keep-as-is/skip. `cflt` rows are resolved only by showing the three-way diff and asking per row — never by Express or `Apply updates`. Never offer `setup`, `doctor`, or `guided-workspace-setup` — those are installer-only and live in the source agent-fleet repo.
13
+ Drive every decision through `AskUserQuestion` (max 4 options per call), never a printed table awaiting a free-text reply. Open with the Express question backed by the manifest's profiles; group screens run only on `Custom`; drill-ins appear only behind `Customise`. Option titles carry `<name> ★ [state]` and descriptions say what picking it does in plain words. Leaving an installed item unpicked keeps it — removal is its own explicit screen and runs `uninstall`. Cancel is a no-op everywhere except the final confirmation.
14
14
 
15
- Removal happens **only** on an explicit `Remove some…` multi-select (empty selection = remove nothing), and it is scoped: the screen lists only items whose name is in the agent-fleet inventory **and** that are recorded in `## install-status` (or are symlinks resolving into the source repo). User-authored skills, custom commands, third-party plugins, and unrelated settings/env keys are left untouched and logged as "Skipped — not owned by agent-fleet".
15
+ If `verify` reports findings or broken items, offer `doctor --fix` before the menu — a broken workspace makes the menu lie about what is installed.
16
16
 
17
- **No cross-tool substitution.** Each row is offered only when the source file the chosen agent needs already exists — for `pi`, that means `.pi/prompts/<name>.md`, `.pi/extensions/<name>/`, etc. Never fall back to `.claude/commands/` (or another agent's tree) to satisfy a pi prompt request; items missing their per-agent source are filtered out of the menu entirely.
18
-
19
- **Personas are generated for non-pi targets.** The personas group lists the full availability roster from `node <source-root>/bin/cli.js transform-persona --list --agent <agent>` (pi-only personas — `bowser`, `orchestrator` — appear only when the agent is `pi`). For `claude-code`/`opencode` the apply step installs personas via `transform-persona --agent <agent> --workspace <workspace> <name…>` — always a generated copy, even in symlink mode — and records the rows with `transformed: true`; status checks diff against the generated output, not the raw canonical source.
20
-
21
- **pi harness companions.** When the agent is `pi`, installing/refreshing/removing any harness also refreshes its companions — the `justfile` launch recipes, the `team-up`/`coms-net` scripts, the peer/team YAML, `.pi/damage-control-rules.yaml`, and `.pi/harnesses/package.json`. `agent-hub` requires only `damage-control-continue` and `ask-user-remote`; auto-include both. Refresh the `justfile` from the current source (rewriting only the `agent-fleet:harnesses` managed region so user recipes survive) so retired-harness recipes are pruned and new ones added. Treat the retired `damage-control` hard-stop directory as `gone`: remove it only when recorded and unchanged against the recorded snapshot, or when it is a symlink into the source root (including a broken retirement link). Preserve every user-modified or unowned copy.
22
-
23
- **No mid-apply overwrite prompts.** The `mod` description already warns that refreshing overwrites local edits. The user's selection is the consent; the Step 9 confirmation is the single gate. During apply, refresh selected items unconditionally — never pause to ask "should I overwrite this file?". Genuine errors (permission denied, missing source) still stop and report.
24
-
25
- Offer override sections for the workspace's `.ai/agent-fleet-overrides.md` based on the analysis (print each draft, then `Accept` / `Edit` / `Skip` per section), and record what was installed in `.ai/agent-fleet-setup.md`. Print the plan as compact action-grouped lines (Add / Refresh / Remove / Keep-count / Records / Method), then confirm with one question whose options are `Apply — and remove the installer commands` (default) / `Apply — keep the installer commands` / `Adjust picks` / `Cancel` — write nothing until an Apply is chosen. Then perform the setup, re-scan for any new breakage, and report what changed.
17
+ Print the plan as compact action-grouped lines before confirming, then confirm once with `Apply — and remove the installer commands` (default) / `Apply — keep the installer commands` / `Adjust picks` / `Cancel`. Exit `3` from the CLI means conflicts: show the `.new` files it wrote and let the user decide — never pick a side for them. Relay `operator` and `external` steps verbatim; the CLI performs neither, and neither do you.
@@ -2,16 +2,21 @@
2
2
  description: Scan agent-fleet install targets for broken symlinks, stale persona references, and overrides-file problems, then offer repairs
3
3
  ---
4
4
 
5
- Invoke the Doctor preflight from the `guided-workspace-setup` skill (Step 5) via the `skill` tool — without running the rest of the install flow.
5
+ Invoke the `guided-workspace-setup` skill via the `skill` tool and run its repair path only — not the rest of the install flow. `/af-setup-agent-fleet` offers the same thing as soon as it finds prior install state.
6
6
 
7
- Walk every install-target directory the chosen coding agent uses (`agents/`, `.claude/agents/`, `.opencode/agent/` (+ legacy `.opencode/agents/`), `.pi/agents/`, `.claude/skills/`, `.opencode/skills/`, `.pi/skills/`, `.agents/skills`, `.claude/commands/`, `.opencode/commands/`, `.pi/prompts/`, `.claude/references/`, `.claude/hooks/`). For each broken symlink, resolve where it pointed, look for a canonical replacement in the source `agents/` and `skills/` trees, and offer to repair or delete (persona links under `.claude/agents/` and `.opencode/agent(s)/` are repaired by regenerating a transformed copy via `transform-persona`, not by re-symlinking the raw source). Common stale names from the pre-merge persona layout: `reviewer` → `code-reviewer`, `red-team` → `security-auditor`.
7
+ Run the CLI — do not walk directories or repair files yourself:
8
8
 
9
- Also flag and offer to rewrite any remaining YAML configs (`teams.yaml`, `peers.yaml`, etc.) that still reference removed persona names.
9
+ ```
10
+ node <source-root>/bin/cli.js doctor --workspace <workspace> [--agent <agent>] --json
11
+ ```
10
12
 
11
- Also flag malformed peer entries in `.pi/agents/peers.yaml`: field lines (`persona:`, `model:`, ...) that sit under a team heading before any `- name: ...` list item. The team-up launcher's minimal parser silently drops such lines, so the peer never spawns and nothing errors — the usual cause is a `- name:` line lost in an edit. These findings are advisory only: report them with the missing `- name: <peer>` suggestion, never rewrite the file.
13
+ Resolve `<source-root>` from `<workspace>/.ai/.agent-fleet-bootstrap.json`, or this prompt's realpath if it is a symlink, or by asking. Never scan the filesystem for agent-fleet clones.
12
14
 
13
- Also validate `.ai/agent-fleet-overrides.md` when it exists, against the schema in `docs/agent-fleet-setup.md`: unknown sections, unknown keys in known sections, invalid values for the mechanically parsed `agent-hub` keys, missing `rules:` folders and `docs:` entry points, and `## env` `required:` names that are neither set nor declared in the root `.env`. These findings are advisory only — report them with fix "edit by hand", never edit the overrides file.
15
+ The report has two halves, and they are repaired differently on purpose:
14
16
 
15
- Present the findings per the skill's Step 1 interaction contract: print a short text summary (counts per kind, advisory findings as report-only text), then ask one native multi-select — *"Which fixes should I apply now?"* — each option titled `<path> — <issue>` with the proposed fix as its description; an empty selection applies nothing. Without a widget, print a `# | Path | Issue | Suggested fix` table instead and take the picks as text.
17
+ - `repairs` — recorded items that are missing, dangling, or linked outside the source root. These are rebuilt through the same `apply()` path `install` writes with, so a repaired file is byte-identical to a freshly installed one.
18
+ - `findings` — what the install record cannot own: broken symlinks in a pre-engine workspace, stale persona names in `.pi/agents/*.yaml` (`reviewer` → `code-reviewer`, `red-team` → `security-auditor`), plus advisory ones. `overrides` and `yaml-shape` findings are **advisory**: report them with "edit by hand" and never fix them, because the fix is always a hand edit of the flagged file.
16
19
 
17
- Never overwrite a regular file — only act on symlinks whose target is missing. Report `repaired`, `deleted`, and `skipped` counts, and append a `## doctor-runs` line to `.ai/agent-fleet-setup.md` with the date and counts.
20
+ Print the two lists as text, then ask one native single-select (or a plain text question without a widget) — *"Apply the suggested fixes?"* — and on yes re-run with `--fix`. An empty answer or a cancel applies nothing.
21
+
22
+ Exit codes: `0` nothing to repair, `2` repairable issues found (or advisories present, or a repair failed), `1` could not run. Report the counts the CLI returns; do not invent your own.
@@ -2,14 +2,16 @@
2
2
  description: Guided setup — install agent-fleet artifacts into a workspace for a chosen coding agent
3
3
  ---
4
4
 
5
- Invoke the `guided-workspace-setup` skill via the `skill` tool.
5
+ Invoke the `guided-workspace-setup` skill via the `skill` tool and follow it.
6
6
 
7
- Run the guided install for a target workspace. If the user passed a workspace path, use it; otherwise ask for it. Detect the running coding agent and confirm it with the user.
7
+ Run the guided install for a target workspace. If the user passed a workspace path, use it; otherwise ask. Confirm the coding agent (`opencode` here unless the user says otherwise).
8
8
 
9
- The Skills group draws from **two roots**: fleet-native `skills/` and the vendored upstream import `vendor/agent-skills-upstream/skills/` (see `docs/UPSTREAM-SKILLS.md`). On a name collision the native copy wins — never offer the vendored duplicate as a separate row.
9
+ The skill is a front-end over the `agent-fleet` CLI's installer engine: `verify --json` supplies the menu (groups, profiles, per-item state), and `install` / `upgrade` / `uninstall` / `doctor --fix` do every write. **Do not copy, symlink, or delete an install target yourself** — the CLI records ownership in `.ai/agent-fleet-state.json`, and anything written by hand is invisible to every later run. Personas land in `.opencode/agent/<name>.md` as generated files; the CLI handles that too. Artifacts install as copies; never ask copy-vs-symlink and never pass `--method`.
10
10
 
11
- Analyse the workspace, then present the install menu per the skill's Step 1 interaction contract: with a native select widget, open with the **Express question** (`Recommended ★` / `Everything` / `Custom — group by group`, or the installed-state variants), and on `Custom` run the **7 groups** (4 shared: Skills, Agent personas, Commands/prompts, References & Hooks; 3 pi-only — an opencode workspace sees just the 4 shared groups) as single-select quick screens with multi-select drill-ins only behind `Customise`, chunked by sub-category; installed state shows as counts and plain-words descriptions (no pre-checking), removal only via an explicit `Remove some…` selection, and cancel = keep-as-is. Without a widget, fall back to the skill's tabular format (pre-checked `[x]` tables with text replies). On `pi`, installing/refreshing/removing any harness also refreshes its companions — the `justfile` launch recipes (managed region only, so user recipes survive), the `team-up` script, the peer/team YAML, `.pi/damage-control-rules.yaml`, and `.pi/harnesses/package.json` — refreshed from the current source so retired-harness recipes are pruned and new ones added. `agent-hub` requires only `damage-control-continue` and `ask-user-remote`. Treat the retired `damage-control` hard-stop directory as `gone`: remove it only when recorded and unchanged against the recorded snapshot, or when it is a symlink into the source root (including a broken retirement link); preserve every user-modified or unowned copy.
11
+ Two things are yours rather than the CLI's: drafting `.ai/agent-fleet-overrides.md` from a scan of the project, and the `pi-voice-stt` provider Q&A (pi workspaces only).
12
12
 
13
- **Personas are generated for opencode.** The personas group lists the full availability roster from `node <source-root>/bin/cli.js transform-persona --list --agent opencode` (pi-only personas — `bowser`, `orchestrator` — are excluded). The apply step installs them into `.opencode/agent/<name>.md` via `transform-persona --agent opencode --workspace <workspace> <name…>` — always a generated copy, even in symlink mode — and records the rows with `transformed: true`; status checks diff against the generated output, not the raw canonical source.
13
+ With a native select widget, open with the Express question backed by the manifest's profiles, then run group screens only on `Custom`, with drill-ins behind `Customise`. Without one, print a compact table and take a text reply. Option titles carry `<name> ★ [state]`; descriptions say what picking it does in plain words. Leaving an installed item unpicked keeps it — removal is its own explicit screen and runs `uninstall`. Cancel is a no-op everywhere except the final confirmation.
14
14
 
15
- Offer override sections for the workspace's `.ai/agent-fleet-overrides.md` based on a brief analysis of the project, and record what was installed in `.ai/agent-fleet-setup.md`. Summarise the full plan and wait for explicit confirmation before writing anything, then perform the setup and report what changed.
15
+ If `verify` reports findings or broken items, offer `doctor --fix` before the menu — a broken workspace makes the menu lie about what is installed.
16
+
17
+ Print the plan as compact action-grouped lines and wait for explicit confirmation before anything is written. Exit `3` from the CLI means conflicts: show the `.new` files it wrote and let the user decide — never pick a side for them. Relay `operator` and `external` steps verbatim; the CLI performs neither, and neither do you.
@@ -33,11 +33,10 @@ Every error path silently aborts. Update checks must never disrupt a session.
33
33
 
34
34
  ## Install
35
35
 
36
- Installed via `/af-setup-agent-fleet` as part of Group 10 — pi extensions. Or symlink manually:
36
+ Offered by `/af-setup-agent-fleet` with the other pi extensions, and included in the `pi-fleet-core` profile. Directly:
37
37
 
38
38
  ```bash
39
- ln -s /path/to/@chankov/agent-fleet/.pi/extensions/agent-fleet-update-check \
40
- .pi/extensions/agent-fleet-update-check
39
+ npx @chankov/agent-fleet install --agent pi --items pi-extension:agent-fleet-update-check --yes
41
40
  ```
42
41
 
43
42
  No runtime deps beyond pi's own `@mariozechner/pi-coding-agent` types and Node built-ins (`fs`, `os`, `path`, `https`).
@@ -31,8 +31,9 @@ opens a modal over it:
31
31
  - **`/af-btw <task>`** — start a side task and open its modal.
32
32
  - **`/af-btw`** (no args) — reopen the modal on the last-viewed (or most recent) thread.
33
33
  - **`Alt+'`** — reopen the modal. (Chosen because it doesn't collide with a pi
34
- composer motion the way `Alt+B` does — that's the editor's cursor-word-left. Pick
35
- another binding in `index.ts` if your terminal swallows `Alt+'`.)
34
+ composer motion the way `Alt+B` does — that's the editor's cursor-word-left.) On
35
+ macOS, configure the terminal to send Option as Meta; in Zed set
36
+ `terminal.option_as_meta` to `true`.
36
37
 
37
38
  Once any `/af-btw` command or `Alt+'` has run in a session, the **agent-hub** harness
38
39
  footer surfaces an `Alt+' btw` hint next to its `Alt+A view:` hint (via a
@@ -75,11 +76,11 @@ The agent cannot trigger it; only you can.
75
76
 
76
77
  ## Install
77
78
 
78
- Auto-discovered like the other always-on utilities — drop or symlink it under
79
+ Auto-discovered like the other always-on utilities once it is under
79
80
  `.pi/extensions/` (see [docs/pi-setup.md](../../../docs/pi-setup.md)):
80
81
 
81
82
  ```bash
82
- ln -s /path/to/agent-fleet/.pi/extensions/btw .pi/extensions/btw
83
+ npx @chankov/agent-fleet install --agent pi --items pi-extension:btw --yes
83
84
  ```
84
85
 
85
86
  No extra dependencies — the extension uses only Node built-ins and the pi runtime
@@ -31,15 +31,12 @@ PI_CHROME_DEVTOOLS_MODE=headed pi # interactive (default)
31
31
 
32
32
  ## Install
33
33
 
34
- Symlink both extensions from this repo into your project's `.pi/extensions/`:
35
-
36
34
  ```bash
37
- mkdir -p .pi/extensions
38
- ln -s /path/to/agent-fleet/.pi/extensions/mcp-bridge .pi/extensions/mcp-bridge
39
- ln -s /path/to/agent-fleet/.pi/extensions/chrome-devtools-mcp .pi/extensions/chrome-devtools-mcp
35
+ npx @chankov/agent-fleet install --agent pi --allow-exec --yes \
36
+ --items pi-extension:mcp-bridge,pi-extension:chrome-devtools-mcp
40
37
  ```
41
38
 
42
- `mcp-bridge` is a sibling library; `chrome-devtools-mcp` imports it via the relative path. Runtime dependencies live in `.pi/extensions/package.json` for cloned/copy installs and are also root production dependencies of the published package so npm-package symlink installs resolve them from the real package path. Run `npm ci` in `.pi/extensions/` once after cloning `agent-fleet` (see [docs/pi-setup.md](../../../docs/pi-setup.md#optional-pi-extensions)); a normal `@chankov/agent-fleet` package install needs no nested install.
39
+ Select both: `mcp-bridge` is a sibling library that `chrome-devtools-mcp` imports via a relative path, so it must sit beside it under `.pi/extensions/`. Runtime dependencies live in `.pi/extensions/package.json`, which is copied in with the extensions; `--allow-exec` runs `npm ci --prefix .pi/extensions` as part of the install, and without it that step is printed and left for you (see [docs/pi-setup.md](../../../docs/pi-setup.md#optional-pi-extensions)). They are also root production dependencies of the published package, so a pi-package install resolves them from the package root.
43
40
 
44
41
  ## Verify
45
42
 
@@ -26,13 +26,13 @@ The canonical usage point in this repo is `/af-build`: at slice-approval time, t
26
26
 
27
27
  ## Install
28
28
 
29
- Symlink alongside the other extensions (see [docs/pi-setup.md](../../../docs/pi-setup.md#optional-pi-extensions)):
29
+ Installs alongside the other extensions (see [docs/pi-setup.md](../../../docs/pi-setup.md#optional-pi-extensions)):
30
30
 
31
31
  ```bash
32
- ln -s /path/to/agent-fleet/.pi/extensions/compact-and-continue .pi/extensions/compact-and-continue
32
+ npx @chankov/agent-fleet install --agent pi --items pi-extension:compact-and-continue --yes
33
33
  ```
34
34
 
35
- The only runtime dep (`typebox`) is already hoisted at `.pi/extensions/package.json` for the other extensions, so no extra `npm ci` is needed if you've already installed.
35
+ It also comes in with the `pi-fleet-core` profile. The only runtime dep (`typebox`) is declared in `.pi/extensions/package.json` alongside the other extensions, so no extra `npm ci` is needed if you have already installed those.
36
36
 
37
37
  ## Behavior notes
38
38
 
@@ -43,4 +43,4 @@ pi does not yet have first-class MCP support. This bridge is a **stopgap**: it l
43
43
 
44
44
  ## Dependencies
45
45
 
46
- Runtime dependencies (`@modelcontextprotocol/sdk`, `typebox`) are declared at `.pi/extensions/package.json` for cloned/copy installs and duplicated in the root package's production `dependencies` for published-package symlink installs. The duplication is intentional: Node resolves a symlinked extension from its real path inside `@chankov/agent-fleet`, while npm does not install dependencies from a nested `.pi/extensions/package.json`. Run `npm ci` in `.pi/extensions/` for a clone or copied install; a normal `@chankov/agent-fleet` package install supplies the same dependencies at package root. No per-wrapper install is required. `@mariozechner/pi-coding-agent` is supplied by the pi runtime that loads the extension.
46
+ Runtime dependencies (`@modelcontextprotocol/sdk`, `typebox`) are declared at `.pi/extensions/package.json` — copied into the workspace with the extensions — and duplicated in the root package's production `dependencies`. The duplication is intentional: npm does not install dependencies from a nested `.pi/extensions/package.json`, so a pi-package install needs them at package root. In a workspace install, `agent-fleet install --allow-exec` runs `npm ci --prefix .pi/extensions` for you; otherwise run it yourself. No per-wrapper install is required. `@mariozechner/pi-coding-agent` is supplied by the pi runtime that loads the extension.
@@ -178,6 +178,9 @@ can be raised.
178
178
 
179
179
  ## Troubleshooting
180
180
 
181
+ - **macOS: Option shortcuts type symbols instead of activating** — configure the terminal to send
182
+ Option as Meta. In Zed set `terminal.option_as_meta` to `true`; this is terminal-specific, not an
183
+ OS-wide shortcut change.
181
184
  - **`/af-stt doctor` says ffmpeg not found** — install ffmpeg or set `capture.ffmpegPath`.
182
185
  - **Linux: no audio** — ensure PulseAudio/PipeWire is running; try `capture.input` of a
183
186
  specific source name from `pactl list sources short`.
@@ -102,7 +102,9 @@ Every borrowed idea from another harness passes one test before it lands: *does
102
102
  `set_assertions` the next one when it starts.
103
103
  - **Artifact bus** — session handoffs live under `.pi/agent-sessions/artifacts/` with conventional
104
104
  `returns/`, `failures/`, `plans/`, `reviews/`, `inventories/`, and `evidence/` subdirectories, all
105
- wiped and recreated at session start like `findings/`. `failures/` is separate on purpose: a run
105
+ **archived** into an immutable `runs/<runId>/` namespace at session start rather than wiped (see
106
+ [Immutable per-run artifact namespaces](#immutable-per-run-artifact-namespaces-run-namespacejs)),
107
+ so a later session can never overwrite an earlier one's returns. `failures/` is separate on purpose: a run
106
108
  that errored or timed out produced no specialist result, so its output goes there and the dispatch
107
109
  result names it a **delivery failure** carrying no assertion evidence. Filing a 142-byte coms error
108
110
  stub as `returns/code-reviewer-run4.md` once cost a 103-second dispatch investigating a review that
@@ -324,6 +326,9 @@ are inert in dashboard mode (use `/af-zoom <name>` there).
324
326
  > Terminal note: `Alt+[` emits `ESC [` (a CSI prefix) and may be swallowed by some terminals'
325
327
  > escape parsers; `Alt+]` and `Alt+\` are the reliable pair. `Alt+↑/↓/←/→` are reserved by the pi
326
328
  > editor, which is why the switcher uses the bracket/backslash keys.
329
+ >
330
+ > On macOS, configure the outer terminal to send Option as Meta. For Zed, set
331
+ > `terminal.option_as_meta` to `true`; otherwise Option combinations produce composed characters.
327
332
 
328
333
  ## Configuration
329
334
 
@@ -440,8 +445,49 @@ max-research-per-turn: 4 # integer or off
440
445
  turn-wall-time-s: 3600 # integer or off
441
446
  agent-turn-timeout-s: 1800 # whole-run deadline per spawned run; integer or off
442
447
  session-recycle-runs: 5 # recycle a specialist session after N resumed runs; integer or off
448
+ run-history-keep: 10 # previous sessions' artifact archives to retain; integer or off
443
449
  ```
444
450
 
451
+ #### Task budget (the bound a turn window cannot provide)
452
+
453
+ A per-message allowance cannot bound a task. In the run this guardrail comes from, every
454
+ steering message opened a fresh window of 8 dispatches and 60 minutes, so no counter ever
455
+ bound: one workspace stayed open **47 hours**, while the same change made in a narrow
456
+ workspace took **13 minutes**.
457
+
458
+ So there is a second envelope, **`TASK_BUDGET_MULTIPLIER` (3) × the turn envelope**, whose
459
+ counters are **not** reset by a user message:
460
+
461
+ | | per turn (standard, `feature`) | per task |
462
+ |---|---|---|
463
+ | `dispatch_agent` | 6 | 18 |
464
+ | `spawn_research` | 4 | 12 |
465
+ | clock | 60 min wall | 180 min **active** |
466
+
467
+ Exhausting it is a **hard stop**: the refusal says so, and another user message does not
468
+ reopen it. Only `/af-new-task [label]` (or `set_task_tier` with `new_task: true`) opens a
469
+ new task window — clearing the counters, the tier, the review-round count, the duplicate
470
+ guard, and any external-blocker stop. The status chip shows both (`… · task 4/18`).
471
+
472
+ The reasoning: a task that has burned three full envelopes has not hit a budget problem, it
473
+ has outgrown its scope, and re-scoping is the human's call.
474
+
475
+ The task clock charges **active time only** — turns that actually ran, each minus the time
476
+ the dispatcher sat blocked on `ask_user`. Inter-turn idle costs nothing, because no turn is
477
+ open across it. Raw wall clock would bill a lunch break, an overnight pause, and every long
478
+ human answer against the task; at `fast` mode's 45-minute envelope a coffee break would
479
+ hard-stop a task with two dispatches spent. A false stop is worse than no stop — it teaches
480
+ people to reset the task window reflexively, and that reset is the one thing that has to
481
+ stay deliberate. Dispatch and research counts remain the honest hard stops.
482
+
483
+ The **auto-research pipe** (specialist emits `NEEDS_RESEARCH`, the hub fans out read-only
484
+ helpers in code) stays exempt from the TURN budget — it is hub mechanics, not a dispatcher
485
+ decision, and it must not steal the dispatcher's slots — but it **is** charged against the
486
+ task envelope. At 2 rounds × 4 questions per dispatch and 18 dispatches per task, leaving it
487
+ uncounted would have put 144 research runs inside the bound that is supposed to be the outer
488
+ one. When the task's research envelope is spent the pipe does not spawn and the specialist is
489
+ not resumed; the dispatch result says so.
490
+
445
491
  Two related always-on behaviors: specialist **context pressure is measured over
446
492
  input + cacheRead + cacheWrite** (resumed sessions re-send their whole accumulated context
447
493
  as cache reads — counting `input` alone hid that entirely), and a specialist session is
@@ -486,17 +532,103 @@ can no longer hold its parent for hours.
486
532
 
487
533
  ### Task triage (complexity tiers)
488
534
 
489
- The dispatcher classifies each user turn with the `set_task_tier` tool BEFORE its first
535
+ The dispatcher classifies the current TASK with the `set_task_tier` tool BEFORE its first
490
536
  dispatch — `trivial` / `small` / `feature` / `project` — and the hub lowers the enforced
491
537
  dispatch/research caps to **min(mode, tier)**: trivial = 1 dispatch / 1 research,
492
- small = 2 / 2, feature = 6 / 4, `project` defers to the mode. Skipping the call makes the
493
- first dispatch assume `feature` (except in strict mode, where tiers are opt-in). The tier
494
- resets every user turn and shows in the `hub-mode` status chip (`Mode: standard·small · …`).
495
- The system prompt ties the tier to the anti-over-engineering rules: a provided plan is a
496
- spec (no re-planning), assertions stay ≤3 for trivial/small asks, and "using every persona"
497
- is called out as a smell. Two hygiene guards are enforced in code, not prose: a
498
- **duplicate-dispatch guard** refuses re-dispatching the same agent with a near-identical
499
- task inside one turn, and every budget/duplicate refusal is counted in `/af-hub-report`.
538
+ small = 2 / 2, feature = 6 / 4, `project` defers to the mode. The tier shows in the
539
+ `hub-mode` status chip (`Mode: standard·small · …`), with a trailing `?` while it is only
540
+ assumed.
541
+
542
+ Skipping the call makes the hub assume **`small`**, not `feature`. Because the tier is
543
+ task-scoped, a skipped triage latches for the whole task — and skipped triage is precisely
544
+ the case where the dispatcher was not thinking about proportionality. Assuming `feature`
545
+ there would unlock planner/plan-reviewer/security-auditor, loosen the review caps, and hand
546
+ out the full feature envelope: the over-apparatus failure mode, granted by forgetting a tool
547
+ call. Assuming `small` costs one explicit escalation when the work really is bigger, which
548
+ is the cheap direction to be wrong in. An assumed tier is not a ratchet baseline either: the
549
+ dispatcher's own first `set_task_tier` is treated as an initial declaration, so it never
550
+ needs a `reason` it had no way to know it needed.
551
+
552
+ The tier is **task-scoped and ratcheted**. It survives the user's next message, and it
553
+ moves in one direction cheaply: **lowering it is always free, raising it requires a
554
+ `reason`** naming what the ask turned out to contain (refused in code otherwise). A
555
+ turn-scoped tier could not bind on a steered run — every correction reset it to null, the
556
+ next dispatch re-assumed `feature`, and the effective tier drifted to the ceiling, because
557
+ nobody ever re-declares `trivial` after a steering message.
558
+
559
+ Three guards are enforced in code, not prose:
560
+
561
+ - **Duplicate-dispatch guard** — refuses re-dispatching the same agent with a
562
+ near-identical task inside one turn.
563
+ - **Tier persona gate** — at `trivial`/`small`, `dispatch_agent`/`spawn_research` refuse
564
+ `planner`, `plan-reviewer`, `architect`, `security-auditor` and `deep-researcher`
565
+ (`run-budget.js`). Each opens a document/finding loop whose output then has to be
566
+ executed and re-reviewed; the escape hatch is raising the tier *with a reason*, not a
567
+ flag. The refusal costs no budget slot.
568
+ - **Review round cap** — review dispatches per TASK are capped by tier (trivial/small 1,
569
+ feature 2, project uncapped) and the (N+1)-th is refused without spending a budget slot.
570
+ This is where the review ratchet is actually cut: findings become requirements and the
571
+ enlarged requirement set justifies the next round, so the round is the thing to bound.
572
+ - **Review finding budget** — a review persona's dispatch carries a blocking-finding cap
573
+ tied to the tier (trivial 1, small 2, feature 5, project uncapped) plus the rule that a
574
+ blocking finding may only enforce an invariant the task/plan/rules already state. The hub
575
+ **counts** what came back (`review-findings.js`) and appends a visible notice when the
576
+ return exceeds the cap — it never reclassifies a finding. No rule the hub can evaluate
577
+ distinguishes "invents a manifest nobody asked for" from "this logs a connection string";
578
+ both are a heading and a bullet, and silently demoting the second by position would, on
579
+ the day it matters, move a real security finding into the section nobody acts on.
580
+
581
+ Every budget/gate refusal is counted in `/af-hub-report`.
582
+
583
+ ### Docs lane (`docs-lane.js`)
584
+
585
+ A dispatch whose declared `scope` is documentation only — `Docs/**`, `**/*.md`,
586
+ `artifacts/evidence/*.png`, `.changeset/**` — runs in the single-worker docs lane:
587
+
588
+ - dispatching a review persona (`code-reviewer`, `plan-reviewer`, `security-auditor`,
589
+ `test-engineer`) on it is **refused** and costs no budget slot;
590
+ - any other persona's result carries a note telling the dispatcher not to open a review
591
+ gate for it.
592
+
593
+ An absent or empty `scope` is never the lighter lane — unknown is not docs. The refusal is
594
+ overridable per dispatch with `review_reason: "<why>"` for the cases that do warrant a gate
595
+ (the doc publishes a credential, or states a contract other systems depend on).
596
+
597
+ ### External-blocker stop (`external-blocker.js`)
598
+
599
+ A specialist that cannot proceed without something outside the fleet's reach — an account,
600
+ a permission, a deployment credential, a telemetry destination, a console-only action —
601
+ emits `EXTERNAL_BLOCKED: <what is missing, who owns it, what it blocks>` (the protocol is
602
+ injected into every specialist prompt). The hub records it and **refuses the next
603
+ dispatch/research** with an owner-escalation packet: what is missing and who owns it, which
604
+ assertions are blocked, what is already proven and where, and the human's options (provide
605
+ access / waive as UNPROVEN / drop from scope).
606
+
607
+ The gate opens when the human has been addressed — an `ask_user` call, or the next user
608
+ message. Without `ask_user` installed it fires exactly once, so a session that cannot reach
609
+ the human can still finish and report instead of deadlocking.
610
+
611
+ This exists because the alternative is the most expensive failure mode observed: with no
612
+ correlation destination available, a run kept substituting internal work for the missing
613
+ external fact — scripts, manifests, fixtures, diagnostic packets — for hours, and the
614
+ assertion still ended UNPROVEN.
615
+
616
+ ### Immutable per-run artifact namespaces (`run-namespace.js`)
617
+
618
+ Session start used to `rm -rf` `.pi/agent-sessions/artifacts/`, and specialist returns were
619
+ named by a per-session counter (`returns/builder-run1.md`). Both halves of that failed at
620
+ once: the next session's `builder-run1.md` claimed the same path as the previous one's, and
621
+ the wipe deleted the originals first — a post-mortem had to record eleven implementation
622
+ returns and two review artifacts as NOT RECOVERABLE.
623
+
624
+ Now each session **archives** the previous session's artifacts into
625
+ `.pi/agent-sessions/runs/<runId>/artifacts/` — a namespace written once and never reused —
626
+ alongside a read-only `meta.json` (run id, archive time, project, workspace, per-kind
627
+ artifact counts) and an appended `runs/index.json`. `runId` is a sortable UTC timestamp plus
628
+ a random suffix, so two sessions starting in the same second still get distinct namespaces.
629
+ Retention is `run-history-keep` (default 10, `off` keeps everything); an empty artifact tree
630
+ is not archived. If archiving fails the artifacts are **left in place** rather than deleted:
631
+ a stale tree is recoverable, a deleted one is not.
500
632
 
501
633
  ### Drift watchdog (in-flight observation)
502
634
 
@@ -0,0 +1,122 @@
1
+ // Docs-only lane — the pure policy core behind "a documentation change is not a
2
+ // code change". A closeout that touched only markdown was routed through a full
3
+ // code-review gate, which produced a reviewer cycle, a stop, and an objection
4
+ // from the human; the review had no code to review. This module decides, from a
5
+ // dispatch's declared `scope` globs alone, whether the change is documentation.
6
+ //
7
+ // Everything here is data + pure functions so the policy is unit-testable away
8
+ // from the harness.
9
+
10
+ import { REVIEW_PERSONAS } from "./run-budget.js";
11
+
12
+ // Extensions that are documentation by nature.
13
+ const DOC_EXTENSIONS = new Set(["md", "mdx", "markdown", "rst", "adoc", "txt"]);
14
+
15
+ // Path prefixes whose entire subtree is documentation/evidence. Matched on the
16
+ // first segment, case-insensitively.
17
+ const DOC_DIRS = new Set(["docs", "doc", "artifacts", "adr", "adrs", "changelog", ".changeset"]);
18
+
19
+ // Extensionless files that are documentation when they sit at a scope root.
20
+ const DOC_BASENAMES = new Set(["readme", "license", "licence", "changelog", "contributing", "notice", "authors", "codeowners"]);
21
+
22
+ // Personas whose dispatch is a review GATE. test-engineer is included: asking
23
+ // for tests on a markdown change is the same category error as asking for a
24
+ // code review of it.
25
+ export const DOCS_BLOCKED_PERSONAS = [...REVIEW_PERSONAS, "test-engineer"];
26
+
27
+ /** Strip glob magic so a pattern can be judged by its literal shape. */
28
+ function literalize(glob) {
29
+ return String(glob || "")
30
+ .trim()
31
+ .replace(/\\/g, "/")
32
+ .replace(/^\.\//, "")
33
+ .replace(/^\/+/, "");
34
+ }
35
+
36
+ /**
37
+ * Is ONE glob confined to documentation?
38
+ * `Docs/**`, `**\/*.md`, `CHANGELOG.md`, `artifacts/evidence/*.png` → true.
39
+ * `**`, `src/**`, `**\/*.{md,ts}`, `RIN.Live/**\/*.md` → the last one is true
40
+ * (it can only ever match markdown), the first three are false.
41
+ */
42
+ export function isDocsGlob(glob) {
43
+ const pattern = literalize(glob);
44
+ if (!pattern) return false;
45
+
46
+ const segments = pattern.split("/").filter(Boolean);
47
+ if (segments.length === 0) return false;
48
+
49
+ // A leading documentation directory confines everything beneath it, whatever
50
+ // the tail looks like — `Docs/**`, `artifacts/evidence/*.png`.
51
+ const first = segments[0].toLowerCase();
52
+ if (DOC_DIRS.has(first) && !first.includes("*")) return true;
53
+
54
+ // Otherwise the FINAL segment has to confine the match to a doc file: any
55
+ // wildcard directory in between is fine, since the leaf still decides.
56
+ const leaf = segments[segments.length - 1];
57
+ if (!leaf || leaf === "**" || leaf === "*") return false;
58
+
59
+ // Brace alternation is only docs when EVERY alternative is.
60
+ const braces = leaf.match(/\{([^}]*)\}/);
61
+ if (braces) {
62
+ const alternatives = braces[1].split(",").map((a) => a.trim()).filter(Boolean);
63
+ if (alternatives.length === 0) return false;
64
+ return alternatives.every((alt) => isDocsGlob(leaf.replace(/\{[^}]*\}/, alt)));
65
+ }
66
+
67
+ const dot = leaf.lastIndexOf(".");
68
+ if (dot === -1) {
69
+ // No extension: only a known documentation basename counts, and only when
70
+ // it carries no wildcard (`README` yes, `REA*` no).
71
+ if (/[*?[\]]/.test(leaf)) return false;
72
+ return DOC_BASENAMES.has(leaf.toLowerCase());
73
+ }
74
+ const ext = leaf.slice(dot + 1).toLowerCase();
75
+ if (/[*?[\]]/.test(ext)) return false;
76
+ return DOC_EXTENSIONS.has(ext);
77
+ }
78
+
79
+ /**
80
+ * Is the whole declared scope documentation-only? An empty/absent scope is NOT
81
+ * docs-only — an undeclared scope means "unknown", and unknown is never the
82
+ * lighter lane.
83
+ */
84
+ export function isDocsOnlyScope(globs) {
85
+ const list = (globs || []).map(literalize).filter(Boolean);
86
+ if (list.length === 0) return false;
87
+ return list.every((glob) => isDocsGlob(glob));
88
+ }
89
+
90
+ /**
91
+ * Gate a review-persona dispatch whose scope is documentation only.
92
+ * Returns null when allowed, else { reason, message }. `reviewReason` is the
93
+ * dispatcher's explicit justification and always opens the gate — a docs change
94
+ * CAN warrant review (a published credential, a contractual API doc), it just
95
+ * must not be the default.
96
+ */
97
+ export function checkDocsLane(agent, scopeGlobs, reviewReason = "") {
98
+ const name = String(agent || "").trim().toLowerCase();
99
+ if (!DOCS_BLOCKED_PERSONAS.includes(name)) return null;
100
+ if (!isDocsOnlyScope(scopeGlobs)) return null;
101
+ if (String(reviewReason || "").trim()) return null;
102
+ return {
103
+ reason: "docs_only_lane",
104
+ message: `⚠ ${name} refused for a documentation-only scope — and this dispatch was NOT counted ` +
105
+ `against any budget.\nScope: ${(scopeGlobs || []).join(", ")}\n` +
106
+ `Documentation changes run in the single-worker docs lane: the writer verifies its own change ` +
107
+ `(links resolve, statements match the code it describes) and the work is done. A review gate here ` +
108
+ `produces a round trip with no code to review.\n` +
109
+ `If this docs change genuinely needs a gate — it publishes a credential or secret, it states a ` +
110
+ `contract other systems rely on, or the human asked for a review — re-dispatch with ` +
111
+ `\`review_reason: "<why>"\`. If the change also touches code, put those paths in \`scope\` too.`,
112
+ };
113
+ }
114
+
115
+ /** Note appended to a non-review dispatch that runs in the docs lane. */
116
+ export function docsLaneNotice(agent, scopeGlobs) {
117
+ if (!isDocsOnlyScope(scopeGlobs)) return null;
118
+ const name = String(agent || "").trim().toLowerCase();
119
+ if (DOCS_BLOCKED_PERSONAS.includes(name)) return null;
120
+ return `📝 Docs lane: this dispatch's scope is documentation only, so it needs no review gate. ` +
121
+ `Take ${name}'s own verification as sufficient and close the item — do not dispatch a reviewer for it.`;
122
+ }