@chankov/agent-fleet 0.0.8 → 0.0.10

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 (682) 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/agents/model-profiles.yaml +9 -2
  6. package/.pi/agents/peers.yaml +12 -16
  7. package/.pi/agents/teams.yaml +4 -2
  8. package/.pi/extensions/agent-fleet-update-check/README.md +2 -3
  9. package/.pi/extensions/btw/README.md +2 -2
  10. package/.pi/extensions/chrome-devtools-mcp/README.md +3 -6
  11. package/.pi/extensions/compact-and-continue/README.md +3 -3
  12. package/.pi/extensions/mcp-bridge/README.md +1 -1
  13. package/.pi/harnesses/agent-hub/README.md +159 -15
  14. package/.pi/harnesses/agent-hub/docs-lane.js +122 -0
  15. package/.pi/harnesses/agent-hub/external-blocker.js +85 -0
  16. package/.pi/harnesses/agent-hub/footer.ts +4 -2
  17. package/.pi/harnesses/agent-hub/index.ts +552 -50
  18. package/.pi/harnesses/agent-hub/package.json +1 -1
  19. package/.pi/harnesses/agent-hub/review-findings.js +102 -0
  20. package/.pi/harnesses/agent-hub/run-budget.js +302 -4
  21. package/.pi/harnesses/agent-hub/run-namespace.js +87 -0
  22. package/.pi/harnesses/agent-hub/version.ts +25 -1
  23. package/.pi/harnesses/coms/README.md +8 -1
  24. package/.pi/harnesses/coms/package.json +1 -1
  25. package/.pi/harnesses/coms/version.ts +25 -1
  26. package/.pi/harnesses/damage-control-continue/README.md +8 -1
  27. package/.pi/harnesses/damage-control-continue/package.json +1 -1
  28. package/.pi/harnesses/damage-control-continue/version.ts +25 -1
  29. package/.pi/harnesses/lib/herdr-client.ts +10 -1
  30. package/.pi/harnesses/lib/spawned-peers.js +190 -0
  31. package/.pi/prompts/af-doctor-agent-fleet.md +13 -6
  32. package/.pi/prompts/af-setup-agent-fleet.md +7 -15
  33. package/.versions/0.0.10/.claude/commands/build.md +44 -0
  34. package/.versions/0.0.10/.claude/commands/code-simplify.md +22 -0
  35. package/.versions/0.0.10/.claude/commands/design-agent.md +14 -0
  36. package/.versions/0.0.10/.claude/commands/doctor-agent-fleet.md +22 -0
  37. package/.versions/0.0.10/.claude/commands/orchestrate.md +112 -0
  38. package/.versions/0.0.10/.claude/commands/plan.md +16 -0
  39. package/.versions/0.0.10/.claude/commands/prime.md +22 -0
  40. package/.versions/0.0.10/.claude/commands/review.md +16 -0
  41. package/.versions/0.0.10/.claude/commands/set-hermes-telegram.md +15 -0
  42. package/.versions/0.0.10/.claude/commands/set-hermes-watchdog.md +6 -0
  43. package/.versions/0.0.10/.claude/commands/setup-agent-fleet.md +17 -0
  44. package/.versions/0.0.10/.claude/commands/ship.md +72 -0
  45. package/.versions/0.0.10/.claude/commands/spec.md +15 -0
  46. package/.versions/0.0.10/.claude/commands/test.md +19 -0
  47. package/.versions/0.0.10/.claude/commands/webperf.md +32 -0
  48. package/.versions/0.0.10/.claude/orchestrate-teams.yaml +24 -0
  49. package/.versions/0.0.10/.opencode/commands/af-build.md +17 -0
  50. package/.versions/0.0.10/.opencode/commands/af-code-simplify.md +16 -0
  51. package/.versions/0.0.10/.opencode/commands/af-compound.md +16 -0
  52. package/.versions/0.0.10/.opencode/commands/af-design-agent.md +15 -0
  53. package/.versions/0.0.10/.opencode/commands/af-doctor-agent-fleet.md +22 -0
  54. package/.versions/0.0.10/.opencode/commands/af-orchestrate.md +112 -0
  55. package/.versions/0.0.10/.opencode/commands/af-plan.md +16 -0
  56. package/.versions/0.0.10/.opencode/commands/af-prime.md +22 -0
  57. package/.versions/0.0.10/.opencode/commands/af-review.md +15 -0
  58. package/.versions/0.0.10/.opencode/commands/af-set-hermes-telegram.md +15 -0
  59. package/.versions/0.0.10/.opencode/commands/af-set-hermes-watchdog.md +6 -0
  60. package/.versions/0.0.10/.opencode/commands/af-setup-agent-fleet.md +17 -0
  61. package/.versions/0.0.10/.opencode/commands/af-ship.md +16 -0
  62. package/.versions/0.0.10/.opencode/commands/af-spec.md +16 -0
  63. package/.versions/0.0.10/.opencode/commands/af-test.md +21 -0
  64. package/.versions/0.0.10/.opencode/commands/af-webperf.md +32 -0
  65. package/.versions/0.0.10/.opencode/orchestrate-teams.yaml +24 -0
  66. package/.versions/0.0.10/.pi/agents/dispatch-policy.yaml +32 -0
  67. package/.versions/0.0.10/.pi/agents/model-profiles.yaml +27 -0
  68. package/.versions/0.0.10/.pi/agents/peers.yaml +142 -0
  69. package/.versions/0.0.10/.pi/agents/teams.yaml +41 -0
  70. package/.versions/0.0.10/.pi/damage-control-rules.yaml +297 -0
  71. package/.versions/0.0.10/.pi/extensions/agent-fleet-update-check/README.md +57 -0
  72. package/.versions/0.0.10/.pi/extensions/agent-fleet-update-check/index.ts +161 -0
  73. package/.versions/0.0.10/.pi/extensions/agent-fleet-update-check/package.json +6 -0
  74. package/.versions/0.0.10/.pi/extensions/btw/README.md +118 -0
  75. package/.versions/0.0.10/.pi/extensions/btw/index.ts +917 -0
  76. package/.versions/0.0.10/.pi/extensions/btw/package.json +6 -0
  77. package/.versions/0.0.10/.pi/extensions/btw/state.js +179 -0
  78. package/.versions/0.0.10/.pi/extensions/chrome-devtools-mcp/README.md +55 -0
  79. package/.versions/0.0.10/.pi/extensions/chrome-devtools-mcp/index.ts +93 -0
  80. package/.versions/0.0.10/.pi/extensions/chrome-devtools-mcp/package.json +6 -0
  81. package/.versions/0.0.10/.pi/extensions/compact-and-continue/README.md +42 -0
  82. package/.versions/0.0.10/.pi/extensions/compact-and-continue/index.ts +120 -0
  83. package/.versions/0.0.10/.pi/extensions/compact-and-continue/package.json +6 -0
  84. package/.versions/0.0.10/.pi/extensions/mcp-bridge/README.md +46 -0
  85. package/.versions/0.0.10/.pi/extensions/mcp-bridge/index.ts +206 -0
  86. package/.versions/0.0.10/.pi/extensions/mcp-bridge/package.json +6 -0
  87. package/.versions/0.0.10/.pi/extensions/package-lock.json +1143 -0
  88. package/.versions/0.0.10/.pi/extensions/package.json +9 -0
  89. package/.versions/0.0.10/.pi/extensions/pi-voice-stt/README.md +201 -0
  90. package/.versions/0.0.10/.pi/extensions/pi-voice-stt/config.ts +198 -0
  91. package/.versions/0.0.10/.pi/extensions/pi-voice-stt/examples/stt.json +35 -0
  92. package/.versions/0.0.10/.pi/extensions/pi-voice-stt/index.ts +248 -0
  93. package/.versions/0.0.10/.pi/extensions/pi-voice-stt/package.json +6 -0
  94. package/.versions/0.0.10/.pi/extensions/pi-voice-stt/providers.ts +214 -0
  95. package/.versions/0.0.10/.pi/extensions/pi-voice-stt/recorder.ts +158 -0
  96. package/.versions/0.0.10/.pi/harnesses/agent-hub/README.md +1001 -0
  97. package/.versions/0.0.10/.pi/harnesses/agent-hub/access-approval.ts +135 -0
  98. package/.versions/0.0.10/.pi/harnesses/agent-hub/artifacts.js +146 -0
  99. package/.versions/0.0.10/.pi/harnesses/agent-hub/assertion-ledger.js +58 -0
  100. package/.versions/0.0.10/.pi/harnesses/agent-hub/backend-policy.js +153 -0
  101. package/.versions/0.0.10/.pi/harnesses/agent-hub/context-window.js +106 -0
  102. package/.versions/0.0.10/.pi/harnesses/agent-hub/delegate.ts +435 -0
  103. package/.versions/0.0.10/.pi/harnesses/agent-hub/docs-lane.js +122 -0
  104. package/.versions/0.0.10/.pi/harnesses/agent-hub/drift-watchdog.js +211 -0
  105. package/.versions/0.0.10/.pi/harnesses/agent-hub/evidence-rules.js +96 -0
  106. package/.versions/0.0.10/.pi/harnesses/agent-hub/external-blocker.js +85 -0
  107. package/.versions/0.0.10/.pi/harnesses/agent-hub/footer.ts +31 -0
  108. package/.versions/0.0.10/.pi/harnesses/agent-hub/helpers.ts +248 -0
  109. package/.versions/0.0.10/.pi/harnesses/agent-hub/index.ts +9111 -0
  110. package/.versions/0.0.10/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
  111. package/.versions/0.0.10/.pi/harnesses/agent-hub/monitor-invoke-journal.ts +131 -0
  112. package/.versions/0.0.10/.pi/harnesses/agent-hub/monitor-invoke.ts +92 -0
  113. package/.versions/0.0.10/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
  114. package/.versions/0.0.10/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
  115. package/.versions/0.0.10/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
  116. package/.versions/0.0.10/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
  117. package/.versions/0.0.10/.pi/harnesses/agent-hub/monitor-session-bridge.ts +257 -0
  118. package/.versions/0.0.10/.pi/harnesses/agent-hub/package.json +7 -0
  119. package/.versions/0.0.10/.pi/harnesses/agent-hub/provider-semaphore.js +138 -0
  120. package/.versions/0.0.10/.pi/harnesses/agent-hub/research-retention.js +34 -0
  121. package/.versions/0.0.10/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
  122. package/.versions/0.0.10/.pi/harnesses/agent-hub/return-contract.js +293 -0
  123. package/.versions/0.0.10/.pi/harnesses/agent-hub/return-extract.js +75 -0
  124. package/.versions/0.0.10/.pi/harnesses/agent-hub/review-findings.js +102 -0
  125. package/.versions/0.0.10/.pi/harnesses/agent-hub/run-budget.js +479 -0
  126. package/.versions/0.0.10/.pi/harnesses/agent-hub/run-namespace.js +87 -0
  127. package/.versions/0.0.10/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
  128. package/.versions/0.0.10/.pi/harnesses/agent-hub/scope-gate.js +103 -0
  129. package/.versions/0.0.10/.pi/harnesses/agent-hub/session-health.js +110 -0
  130. package/.versions/0.0.10/.pi/harnesses/agent-hub/spawn.ts +354 -0
  131. package/.versions/0.0.10/.pi/harnesses/agent-hub/version.ts +42 -0
  132. package/.versions/0.0.10/.pi/harnesses/ask-user-remote/README.md +19 -0
  133. package/.versions/0.0.10/.pi/harnesses/ask-user-remote/index.ts +321 -0
  134. package/.versions/0.0.10/.pi/harnesses/ask-user-remote/race-core.js +106 -0
  135. package/.versions/0.0.10/.pi/harnesses/coms/README.md +100 -0
  136. package/.versions/0.0.10/.pi/harnesses/coms/index.ts +1767 -0
  137. package/.versions/0.0.10/.pi/harnesses/coms/package.json +7 -0
  138. package/.versions/0.0.10/.pi/harnesses/coms/version.ts +42 -0
  139. package/.versions/0.0.10/.pi/harnesses/damage-control-continue/README.md +124 -0
  140. package/.versions/0.0.10/.pi/harnesses/damage-control-continue/index.ts +536 -0
  141. package/.versions/0.0.10/.pi/harnesses/damage-control-continue/package.json +7 -0
  142. package/.versions/0.0.10/.pi/harnesses/damage-control-continue/version.ts +42 -0
  143. package/.versions/0.0.10/.pi/harnesses/lib/coms-registry-entry.ts +94 -0
  144. package/.versions/0.0.10/.pi/harnesses/lib/damage-control-shared.ts +197 -0
  145. package/.versions/0.0.10/.pi/harnesses/lib/herdr-client.ts +472 -0
  146. package/.versions/0.0.10/.pi/harnesses/lib/herdr-presence.ts +399 -0
  147. package/.versions/0.0.10/.pi/harnesses/lib/hermes-monitor-events.ts +136 -0
  148. package/.versions/0.0.10/.pi/harnesses/lib/hermes-monitor-herdr.ts +28 -0
  149. package/.versions/0.0.10/.pi/harnesses/lib/hermes-monitor-model.ts +18 -0
  150. package/.versions/0.0.10/.pi/harnesses/lib/hermes-monitor-registry.ts +6 -0
  151. package/.versions/0.0.10/.pi/harnesses/lib/hermes-monitor-socket.ts +163 -0
  152. package/.versions/0.0.10/.pi/harnesses/lib/hermes-monitor-store.ts +31 -0
  153. package/.versions/0.0.10/.pi/harnesses/lib/spawned-peers.js +190 -0
  154. package/.versions/0.0.10/.pi/harnesses/package-lock.json +35 -0
  155. package/.versions/0.0.10/.pi/harnesses/package.json +9 -0
  156. package/.versions/0.0.10/.pi/prompts/af-build.md +24 -0
  157. package/.versions/0.0.10/.pi/prompts/af-code-simplify.md +22 -0
  158. package/.versions/0.0.10/.pi/prompts/af-doctor-agent-fleet.md +22 -0
  159. package/.versions/0.0.10/.pi/prompts/af-plan.md +16 -0
  160. package/.versions/0.0.10/.pi/prompts/af-review.md +16 -0
  161. package/.versions/0.0.10/.pi/prompts/af-set-hermes-telegram.md +15 -0
  162. package/.versions/0.0.10/.pi/prompts/af-set-hermes-watchdog.md +6 -0
  163. package/.versions/0.0.10/.pi/prompts/af-setup-agent-fleet.md +19 -0
  164. package/.versions/0.0.10/.pi/prompts/af-ship.md +17 -0
  165. package/.versions/0.0.10/.pi/prompts/af-spec.md +15 -0
  166. package/.versions/0.0.10/.pi/prompts/af-test.md +19 -0
  167. package/.versions/0.0.10/.pi/skills/bowser/SKILL.md +145 -0
  168. package/.versions/0.0.10/.version +1 -0
  169. package/.versions/0.0.10/agents/architect.md +24 -0
  170. package/.versions/0.0.10/agents/bowser.md +27 -0
  171. package/.versions/0.0.10/agents/builder.md +54 -0
  172. package/.versions/0.0.10/agents/code-reviewer.md +208 -0
  173. package/.versions/0.0.10/agents/deep-researcher.md +32 -0
  174. package/.versions/0.0.10/agents/documenter.md +18 -0
  175. package/.versions/0.0.10/agents/orchestrator.md +72 -0
  176. package/.versions/0.0.10/agents/plan-reviewer.md +83 -0
  177. package/.versions/0.0.10/agents/planner.md +70 -0
  178. package/.versions/0.0.10/agents/releaser.md +24 -0
  179. package/.versions/0.0.10/agents/researcher.md +28 -0
  180. package/.versions/0.0.10/agents/security-auditor.md +167 -0
  181. package/.versions/0.0.10/agents/test-engineer.md +153 -0
  182. package/.versions/0.0.10/agents/web-debugger.md +43 -0
  183. package/.versions/0.0.10/agents/web-performance-auditor.md +193 -0
  184. package/.versions/0.0.10/codex/CONDUCTOR.md +148 -0
  185. package/.versions/0.0.10/docs/ARCHITECTURE.md +303 -0
  186. package/.versions/0.0.10/docs/agent-fleet-setup.md +377 -0
  187. package/.versions/0.0.10/docs/claude-code-coms-bridge.md +109 -0
  188. package/.versions/0.0.10/docs/codex-remote-conductor.md +170 -0
  189. package/.versions/0.0.10/docs/coms-hermes-bridge.md +189 -0
  190. package/.versions/0.0.10/docs/getting-started.md +254 -0
  191. package/.versions/0.0.10/docs/npm-install.md +514 -0
  192. package/.versions/0.0.10/docs/opencode-setup.md +281 -0
  193. package/.versions/0.0.10/docs/pi-extensions.md +363 -0
  194. package/.versions/0.0.10/docs/pi-setup.md +571 -0
  195. package/.versions/0.0.10/docs/skill-anatomy.md +150 -0
  196. package/.versions/0.0.10/hermes/README.md +347 -0
  197. package/.versions/0.0.10/hermes/desktop-plugins/agent-fleet-herdr/plugin.js +1291 -0
  198. package/.versions/0.0.10/hermes/desktop-plugins/agent-fleet-herdr/presentation.js +672 -0
  199. package/.versions/0.0.10/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
  200. package/.versions/0.0.10/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
  201. package/.versions/0.0.10/hermes/gates/gate-o-capability.md +8 -0
  202. package/.versions/0.0.10/hermes/gates/gate-o-validator-fixtures.json +1 -0
  203. package/.versions/0.0.10/hermes/plugins/agent-fleet-herdr/dashboard/activity.py +770 -0
  204. package/.versions/0.0.10/hermes/plugins/agent-fleet-herdr/dashboard/coms_registry.py +134 -0
  205. package/.versions/0.0.10/hermes/plugins/agent-fleet-herdr/dashboard/coms_send.py +350 -0
  206. package/.versions/0.0.10/hermes/plugins/agent-fleet-herdr/dashboard/herdr_source.py +193 -0
  207. package/.versions/0.0.10/hermes/plugins/agent-fleet-herdr/dashboard/manifest.json +4 -0
  208. package/.versions/0.0.10/hermes/plugins/agent-fleet-herdr/dashboard/plugin_api.py +444 -0
  209. package/.versions/0.0.10/hermes/plugins/agent-fleet-herdr/dashboard/sessions.py +205 -0
  210. package/.versions/0.0.10/hermes/plugins/agent-fleet-herdr/dashboard/tasks.py +300 -0
  211. package/.versions/0.0.10/hermes/plugins/agent-fleet-herdr/dashboard/watch.py +819 -0
  212. package/.versions/0.0.10/hermes/plugins/agent-fleet-herdr/plugin.yaml +8 -0
  213. package/.versions/0.0.10/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +139 -0
  214. package/.versions/0.0.10/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
  215. package/.versions/0.0.10/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
  216. package/.versions/0.0.10/hermes/skills/hub-conductor/SKILL.md +84 -0
  217. package/.versions/0.0.10/hermes/skills/hub-liaison/SKILL.md +84 -0
  218. package/.versions/0.0.10/hermes/skills/hub-watchdog/SKILL.md +76 -0
  219. package/.versions/0.0.10/hermes/skills/hub-watchdog/manifest.json +1 -0
  220. package/.versions/0.0.10/hermes/skills/hub-watchdog/scripts/watchdog.py +249 -0
  221. package/.versions/0.0.10/hermes/skills/hub-watchdog/scripts/watchdog_actions.py +124 -0
  222. package/.versions/0.0.10/hermes/skills/hub-watchdog/scripts/watchdog_contract.py +76 -0
  223. package/.versions/0.0.10/hermes/skills/hub-watchdog/scripts/watchdog_delivery.py +10 -0
  224. package/.versions/0.0.10/hermes/skills/hub-watchdog/scripts/watchdog_engine.py +128 -0
  225. package/.versions/0.0.10/hermes/skills/hub-watchdog/scripts/watchdog_judgment.py +41 -0
  226. package/.versions/0.0.10/hermes/skills/hub-watchdog/scripts/watchdog_recovery.py +103 -0
  227. package/.versions/0.0.10/hermes/skills/hub-watchdog/scripts/watchdog_state.py +163 -0
  228. package/.versions/0.0.10/hermes/skills/hub-watchdog/scripts/watchdog_transport.py +138 -0
  229. package/.versions/0.0.10/hermes/watchdog-tests/__init__.py +0 -0
  230. package/.versions/0.0.10/hooks/SIMPLIFY-IGNORE.md +90 -0
  231. package/.versions/0.0.10/hooks/coms-stop-hook.mjs +84 -0
  232. package/.versions/0.0.10/hooks/hooks.json +14 -0
  233. package/.versions/0.0.10/hooks/session-start.sh +74 -0
  234. package/.versions/0.0.10/hooks/simplify-ignore.sh +302 -0
  235. package/.versions/0.0.10/install-manifest.json +3615 -0
  236. package/.versions/0.0.10/justfile +254 -0
  237. package/.versions/0.0.10/manifest-meta.json +472 -0
  238. package/.versions/0.0.10/references/accessibility-checklist.md +160 -0
  239. package/.versions/0.0.10/references/definition-of-done.md +67 -0
  240. package/.versions/0.0.10/references/fleet-coordination-patterns.md +151 -0
  241. package/.versions/0.0.10/references/observability-checklist.md +91 -0
  242. package/.versions/0.0.10/references/orchestration-patterns.md +370 -0
  243. package/.versions/0.0.10/references/performance-checklist.md +153 -0
  244. package/.versions/0.0.10/references/prompting-patterns.md +380 -0
  245. package/.versions/0.0.10/references/security-checklist.md +179 -0
  246. package/.versions/0.0.10/references/testing-patterns.md +236 -0
  247. package/.versions/0.0.10/scripts/codex-conductor.ts +41 -0
  248. package/.versions/0.0.10/scripts/codex-remote-control.ts +167 -0
  249. package/.versions/0.0.10/scripts/coms-claude-bridge.ts +401 -0
  250. package/.versions/0.0.10/scripts/coms-cli.ts +484 -0
  251. package/.versions/0.0.10/scripts/coms-hermes-bridge.ts +413 -0
  252. package/.versions/0.0.10/scripts/fleet.ts +168 -0
  253. package/.versions/0.0.10/scripts/hermes-monitor-capability-runner.ts +25 -0
  254. package/.versions/0.0.10/scripts/hermes-monitor-scenario.ts +474 -0
  255. package/.versions/0.0.10/scripts/hermes-watchdog-capability-probe.ts +45 -0
  256. package/.versions/0.0.10/scripts/install-hermes-plugin.sh +180 -0
  257. package/.versions/0.0.10/scripts/lib/claude-bridge-core.ts +165 -0
  258. package/.versions/0.0.10/scripts/lib/codex-conductor.ts +88 -0
  259. package/.versions/0.0.10/scripts/lib/codex-remote-control.ts +480 -0
  260. package/.versions/0.0.10/scripts/lib/coms-envelope.ts +582 -0
  261. package/.versions/0.0.10/scripts/lib/fake-herdr-server.ts +88 -0
  262. package/.versions/0.0.10/scripts/lib/fleet-command.ts +111 -0
  263. package/.versions/0.0.10/scripts/lib/herdr-layout.ts +281 -0
  264. package/.versions/0.0.10/scripts/lib/hermes-bridge-core.ts +241 -0
  265. package/.versions/0.0.10/scripts/lib/hermes-monitor-events.ts +1 -0
  266. package/.versions/0.0.10/scripts/lib/hermes-monitor-herdr.ts +2 -0
  267. package/.versions/0.0.10/scripts/lib/hermes-monitor-model.ts +3 -0
  268. package/.versions/0.0.10/scripts/lib/hermes-monitor-registry.ts +2 -0
  269. package/.versions/0.0.10/scripts/lib/hermes-monitor-socket.ts +2 -0
  270. package/.versions/0.0.10/scripts/lib/hermes-monitor-store.ts +2 -0
  271. package/.versions/0.0.10/scripts/lib/monitor-env.ts +120 -0
  272. package/.versions/0.0.10/scripts/lib/peer-launch.ts +314 -0
  273. package/.versions/0.0.10/scripts/lib/persona-banner.ts +62 -0
  274. package/.versions/0.0.10/scripts/lib/spawn-stagger.ts +101 -0
  275. package/.versions/0.0.10/scripts/lib/team-project.ts +193 -0
  276. package/.versions/0.0.10/scripts/lib/team-snapshot.ts +147 -0
  277. package/.versions/0.0.10/scripts/peer-banner.ts +40 -0
  278. package/.versions/0.0.10/scripts/peer-launch.ts +259 -0
  279. package/.versions/0.0.10/scripts/team-snapshot.ts +237 -0
  280. package/.versions/0.0.10/scripts/team-up.ts +360 -0
  281. package/.versions/0.0.10/skills/_internal/grilling.md +11 -0
  282. package/.versions/0.0.10/skills/browser-testing-with-devtools/SKILL.md +351 -0
  283. package/.versions/0.0.10/skills/code-review-and-quality/SKILL.md +381 -0
  284. package/.versions/0.0.10/skills/compound-learning/SKILL.md +137 -0
  285. package/.versions/0.0.10/skills/context-engineering/SKILL.md +291 -0
  286. package/.versions/0.0.10/skills/deprecation-and-migration/SKILL.md +206 -0
  287. package/.versions/0.0.10/skills/designing-agents/SKILL.md +394 -0
  288. package/.versions/0.0.10/skills/designing-agents/pi-harness-authoring.md +222 -0
  289. package/.versions/0.0.10/skills/frontend-ui-engineering/SKILL.md +328 -0
  290. package/.versions/0.0.10/skills/git-workflow-and-versioning/SKILL.md +316 -0
  291. package/.versions/0.0.10/skills/guided-workspace-setup/SKILL.md +226 -0
  292. package/.versions/0.0.10/skills/guided-workspace-setup/companion-manifest.json +38 -0
  293. package/.versions/0.0.10/skills/idea-refine/SKILL.md +182 -0
  294. package/.versions/0.0.10/skills/idea-refine/examples.md +238 -0
  295. package/.versions/0.0.10/skills/idea-refine/frameworks.md +99 -0
  296. package/.versions/0.0.10/skills/idea-refine/refinement-criteria.md +113 -0
  297. package/.versions/0.0.10/skills/idea-refine/scripts/idea-refine.sh +15 -0
  298. package/.versions/0.0.10/skills/incremental-implementation/SKILL.md +287 -0
  299. package/.versions/0.0.10/skills/interview-me/SKILL.md +226 -0
  300. package/.versions/0.0.10/skills/orchestration-verification/SKILL.md +181 -0
  301. package/.versions/0.0.10/skills/peer-coms/SKILL.md +90 -0
  302. package/.versions/0.0.10/skills/performance-optimization/SKILL.md +350 -0
  303. package/.versions/0.0.10/skills/planning-and-task-breakdown/SKILL.md +254 -0
  304. package/.versions/0.0.10/skills/security-and-hardening/SKILL.md +461 -0
  305. package/.versions/0.0.10/skills/spec-driven-development/SKILL.md +257 -0
  306. package/.versions/0.0.10/skills/using-agent-skills/SKILL.md +199 -0
  307. package/.versions/0.0.10/systemd/user/agent-fleet-codex-remote-control.service.in +23 -0
  308. package/.versions/0.0.10/vendor/agent-skills-upstream/LICENSE +21 -0
  309. package/.versions/0.0.10/vendor/agent-skills-upstream/README.md +11 -0
  310. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/api-and-interface-design/SKILL.md +294 -0
  311. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/browser-testing-with-devtools/SKILL.md +317 -0
  312. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/ci-cd-and-automation/SKILL.md +390 -0
  313. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/code-review-and-quality/SKILL.md +396 -0
  314. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/code-simplification/SKILL.md +331 -0
  315. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/context-engineering/SKILL.md +289 -0
  316. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/debugging-and-error-recovery/SKILL.md +300 -0
  317. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/deprecation-and-migration/SKILL.md +247 -0
  318. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/documentation-and-adrs/SKILL.md +278 -0
  319. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/doubt-driven-development/SKILL.md +243 -0
  320. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/frontend-ui-engineering/SKILL.md +328 -0
  321. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/git-workflow-and-versioning/SKILL.md +355 -0
  322. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/idea-refine/SKILL.md +178 -0
  323. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/idea-refine/examples.md +238 -0
  324. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/idea-refine/frameworks.md +99 -0
  325. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/idea-refine/refinement-criteria.md +113 -0
  326. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/idea-refine/scripts/idea-refine.sh +15 -0
  327. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/incremental-implementation/SKILL.md +249 -0
  328. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/interview-me/SKILL.md +225 -0
  329. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/observability-and-instrumentation/SKILL.md +203 -0
  330. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/performance-optimization/SKILL.md +350 -0
  331. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/planning-and-task-breakdown/SKILL.md +234 -0
  332. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/security-and-hardening/SKILL.md +467 -0
  333. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/shipping-and-launch/SKILL.md +310 -0
  334. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/source-driven-development/SKILL.md +194 -0
  335. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/spec-driven-development/SKILL.md +206 -0
  336. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/test-driven-development/SKILL.md +383 -0
  337. package/.versions/0.0.10/vendor/agent-skills-upstream/skills/using-agent-skills/SKILL.md +191 -0
  338. package/.versions/0.0.9/.claude/commands/build.md +44 -0
  339. package/.versions/0.0.9/.claude/commands/code-simplify.md +22 -0
  340. package/.versions/0.0.9/.claude/commands/design-agent.md +14 -0
  341. package/.versions/0.0.9/.claude/commands/doctor-agent-fleet.md +17 -0
  342. package/.versions/0.0.9/.claude/commands/orchestrate.md +112 -0
  343. package/.versions/0.0.9/.claude/commands/plan.md +16 -0
  344. package/.versions/0.0.9/.claude/commands/prime.md +22 -0
  345. package/.versions/0.0.9/.claude/commands/review.md +16 -0
  346. package/.versions/0.0.9/.claude/commands/set-hermes-telegram.md +15 -0
  347. package/.versions/0.0.9/.claude/commands/set-hermes-watchdog.md +6 -0
  348. package/.versions/0.0.9/.claude/commands/setup-agent-fleet.md +25 -0
  349. package/.versions/0.0.9/.claude/commands/ship.md +72 -0
  350. package/.versions/0.0.9/.claude/commands/spec.md +15 -0
  351. package/.versions/0.0.9/.claude/commands/test.md +19 -0
  352. package/.versions/0.0.9/.claude/commands/webperf.md +32 -0
  353. package/.versions/0.0.9/.claude/orchestrate-teams.yaml +24 -0
  354. package/.versions/0.0.9/.opencode/commands/af-build.md +17 -0
  355. package/.versions/0.0.9/.opencode/commands/af-code-simplify.md +16 -0
  356. package/.versions/0.0.9/.opencode/commands/af-compound.md +16 -0
  357. package/.versions/0.0.9/.opencode/commands/af-design-agent.md +15 -0
  358. package/.versions/0.0.9/.opencode/commands/af-doctor-agent-fleet.md +17 -0
  359. package/.versions/0.0.9/.opencode/commands/af-orchestrate.md +112 -0
  360. package/.versions/0.0.9/.opencode/commands/af-plan.md +16 -0
  361. package/.versions/0.0.9/.opencode/commands/af-prime.md +22 -0
  362. package/.versions/0.0.9/.opencode/commands/af-review.md +15 -0
  363. package/.versions/0.0.9/.opencode/commands/af-set-hermes-telegram.md +15 -0
  364. package/.versions/0.0.9/.opencode/commands/af-set-hermes-watchdog.md +6 -0
  365. package/.versions/0.0.9/.opencode/commands/af-setup-agent-fleet.md +15 -0
  366. package/.versions/0.0.9/.opencode/commands/af-ship.md +16 -0
  367. package/.versions/0.0.9/.opencode/commands/af-spec.md +16 -0
  368. package/.versions/0.0.9/.opencode/commands/af-test.md +21 -0
  369. package/.versions/0.0.9/.opencode/commands/af-webperf.md +32 -0
  370. package/.versions/0.0.9/.opencode/orchestrate-teams.yaml +24 -0
  371. package/.versions/0.0.9/.pi/agents/dispatch-policy.yaml +32 -0
  372. package/.versions/0.0.9/.pi/agents/model-profiles.yaml +27 -0
  373. package/.versions/0.0.9/.pi/agents/peers.yaml +142 -0
  374. package/.versions/0.0.9/.pi/agents/teams.yaml +41 -0
  375. package/.versions/0.0.9/.pi/damage-control-rules.yaml +297 -0
  376. package/.versions/0.0.9/.pi/extensions/agent-fleet-update-check/README.md +58 -0
  377. package/.versions/0.0.9/.pi/extensions/agent-fleet-update-check/index.ts +161 -0
  378. package/.versions/0.0.9/.pi/extensions/agent-fleet-update-check/package.json +6 -0
  379. package/.versions/0.0.9/.pi/extensions/btw/README.md +118 -0
  380. package/.versions/0.0.9/.pi/extensions/btw/index.ts +917 -0
  381. package/.versions/0.0.9/.pi/extensions/btw/package.json +6 -0
  382. package/.versions/0.0.9/.pi/extensions/btw/state.js +179 -0
  383. package/.versions/0.0.9/.pi/extensions/chrome-devtools-mcp/README.md +58 -0
  384. package/.versions/0.0.9/.pi/extensions/chrome-devtools-mcp/index.ts +93 -0
  385. package/.versions/0.0.9/.pi/extensions/chrome-devtools-mcp/package.json +6 -0
  386. package/.versions/0.0.9/.pi/extensions/compact-and-continue/README.md +42 -0
  387. package/.versions/0.0.9/.pi/extensions/compact-and-continue/index.ts +120 -0
  388. package/.versions/0.0.9/.pi/extensions/compact-and-continue/package.json +6 -0
  389. package/.versions/0.0.9/.pi/extensions/mcp-bridge/README.md +46 -0
  390. package/.versions/0.0.9/.pi/extensions/mcp-bridge/index.ts +206 -0
  391. package/.versions/0.0.9/.pi/extensions/mcp-bridge/package.json +6 -0
  392. package/.versions/0.0.9/.pi/extensions/package-lock.json +1143 -0
  393. package/.versions/0.0.9/.pi/extensions/package.json +9 -0
  394. package/.versions/0.0.9/.pi/extensions/pi-voice-stt/README.md +201 -0
  395. package/.versions/0.0.9/.pi/extensions/pi-voice-stt/config.ts +198 -0
  396. package/.versions/0.0.9/.pi/extensions/pi-voice-stt/examples/stt.json +35 -0
  397. package/.versions/0.0.9/.pi/extensions/pi-voice-stt/index.ts +248 -0
  398. package/.versions/0.0.9/.pi/extensions/pi-voice-stt/package.json +6 -0
  399. package/.versions/0.0.9/.pi/extensions/pi-voice-stt/providers.ts +214 -0
  400. package/.versions/0.0.9/.pi/extensions/pi-voice-stt/recorder.ts +158 -0
  401. package/.versions/0.0.9/.pi/harnesses/agent-hub/README.md +872 -0
  402. package/.versions/0.0.9/.pi/harnesses/agent-hub/access-approval.ts +135 -0
  403. package/.versions/0.0.9/.pi/harnesses/agent-hub/artifacts.js +146 -0
  404. package/.versions/0.0.9/.pi/harnesses/agent-hub/assertion-ledger.js +58 -0
  405. package/.versions/0.0.9/.pi/harnesses/agent-hub/backend-policy.js +153 -0
  406. package/.versions/0.0.9/.pi/harnesses/agent-hub/context-window.js +106 -0
  407. package/.versions/0.0.9/.pi/harnesses/agent-hub/delegate.ts +435 -0
  408. package/.versions/0.0.9/.pi/harnesses/agent-hub/drift-watchdog.js +211 -0
  409. package/.versions/0.0.9/.pi/harnesses/agent-hub/evidence-rules.js +96 -0
  410. package/.versions/0.0.9/.pi/harnesses/agent-hub/footer.ts +31 -0
  411. package/.versions/0.0.9/.pi/harnesses/agent-hub/helpers.ts +248 -0
  412. package/.versions/0.0.9/.pi/harnesses/agent-hub/index.ts +8702 -0
  413. package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
  414. package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-invoke-journal.ts +131 -0
  415. package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-invoke.ts +92 -0
  416. package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
  417. package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
  418. package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
  419. package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
  420. package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-session-bridge.ts +257 -0
  421. package/.versions/0.0.9/.pi/harnesses/agent-hub/package.json +7 -0
  422. package/.versions/0.0.9/.pi/harnesses/agent-hub/provider-semaphore.js +138 -0
  423. package/.versions/0.0.9/.pi/harnesses/agent-hub/research-retention.js +34 -0
  424. package/.versions/0.0.9/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
  425. package/.versions/0.0.9/.pi/harnesses/agent-hub/return-contract.js +293 -0
  426. package/.versions/0.0.9/.pi/harnesses/agent-hub/return-extract.js +75 -0
  427. package/.versions/0.0.9/.pi/harnesses/agent-hub/run-budget.js +181 -0
  428. package/.versions/0.0.9/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
  429. package/.versions/0.0.9/.pi/harnesses/agent-hub/scope-gate.js +103 -0
  430. package/.versions/0.0.9/.pi/harnesses/agent-hub/session-health.js +110 -0
  431. package/.versions/0.0.9/.pi/harnesses/agent-hub/spawn.ts +354 -0
  432. package/.versions/0.0.9/.pi/harnesses/agent-hub/version.ts +42 -0
  433. package/.versions/0.0.9/.pi/harnesses/ask-user-remote/README.md +19 -0
  434. package/.versions/0.0.9/.pi/harnesses/ask-user-remote/index.ts +321 -0
  435. package/.versions/0.0.9/.pi/harnesses/ask-user-remote/race-core.js +106 -0
  436. package/.versions/0.0.9/.pi/harnesses/coms/README.md +100 -0
  437. package/.versions/0.0.9/.pi/harnesses/coms/index.ts +1767 -0
  438. package/.versions/0.0.9/.pi/harnesses/coms/package.json +7 -0
  439. package/.versions/0.0.9/.pi/harnesses/coms/version.ts +42 -0
  440. package/.versions/0.0.9/.pi/harnesses/damage-control-continue/README.md +124 -0
  441. package/.versions/0.0.9/.pi/harnesses/damage-control-continue/index.ts +536 -0
  442. package/.versions/0.0.9/.pi/harnesses/damage-control-continue/package.json +7 -0
  443. package/.versions/0.0.9/.pi/harnesses/damage-control-continue/version.ts +42 -0
  444. package/.versions/0.0.9/.pi/harnesses/lib/coms-registry-entry.ts +94 -0
  445. package/.versions/0.0.9/.pi/harnesses/lib/damage-control-shared.ts +197 -0
  446. package/.versions/0.0.9/.pi/harnesses/lib/herdr-client.ts +472 -0
  447. package/.versions/0.0.9/.pi/harnesses/lib/herdr-presence.ts +399 -0
  448. package/.versions/0.0.9/.pi/harnesses/lib/hermes-monitor-events.ts +136 -0
  449. package/.versions/0.0.9/.pi/harnesses/lib/hermes-monitor-herdr.ts +28 -0
  450. package/.versions/0.0.9/.pi/harnesses/lib/hermes-monitor-model.ts +18 -0
  451. package/.versions/0.0.9/.pi/harnesses/lib/hermes-monitor-registry.ts +6 -0
  452. package/.versions/0.0.9/.pi/harnesses/lib/hermes-monitor-socket.ts +163 -0
  453. package/.versions/0.0.9/.pi/harnesses/lib/hermes-monitor-store.ts +31 -0
  454. package/.versions/0.0.9/.pi/harnesses/lib/spawned-peers.js +190 -0
  455. package/.versions/0.0.9/.pi/harnesses/package-lock.json +35 -0
  456. package/.versions/0.0.9/.pi/harnesses/package.json +9 -0
  457. package/.versions/0.0.9/.pi/prompts/af-build.md +24 -0
  458. package/.versions/0.0.9/.pi/prompts/af-code-simplify.md +22 -0
  459. package/.versions/0.0.9/.pi/prompts/af-doctor-agent-fleet.md +15 -0
  460. package/.versions/0.0.9/.pi/prompts/af-plan.md +16 -0
  461. package/.versions/0.0.9/.pi/prompts/af-review.md +16 -0
  462. package/.versions/0.0.9/.pi/prompts/af-set-hermes-telegram.md +15 -0
  463. package/.versions/0.0.9/.pi/prompts/af-set-hermes-watchdog.md +6 -0
  464. package/.versions/0.0.9/.pi/prompts/af-setup-agent-fleet.md +27 -0
  465. package/.versions/0.0.9/.pi/prompts/af-ship.md +17 -0
  466. package/.versions/0.0.9/.pi/prompts/af-spec.md +15 -0
  467. package/.versions/0.0.9/.pi/prompts/af-test.md +19 -0
  468. package/.versions/0.0.9/.pi/skills/bowser/SKILL.md +145 -0
  469. package/.versions/0.0.9/.version +1 -0
  470. package/.versions/0.0.9/agents/architect.md +24 -0
  471. package/.versions/0.0.9/agents/bowser.md +27 -0
  472. package/.versions/0.0.9/agents/builder.md +54 -0
  473. package/.versions/0.0.9/agents/code-reviewer.md +204 -0
  474. package/.versions/0.0.9/agents/deep-researcher.md +32 -0
  475. package/.versions/0.0.9/agents/documenter.md +18 -0
  476. package/.versions/0.0.9/agents/orchestrator.md +66 -0
  477. package/.versions/0.0.9/agents/plan-reviewer.md +62 -0
  478. package/.versions/0.0.9/agents/planner.md +70 -0
  479. package/.versions/0.0.9/agents/releaser.md +24 -0
  480. package/.versions/0.0.9/agents/researcher.md +28 -0
  481. package/.versions/0.0.9/agents/security-auditor.md +167 -0
  482. package/.versions/0.0.9/agents/test-engineer.md +153 -0
  483. package/.versions/0.0.9/agents/web-debugger.md +43 -0
  484. package/.versions/0.0.9/agents/web-performance-auditor.md +193 -0
  485. package/.versions/0.0.9/codex/CONDUCTOR.md +148 -0
  486. package/.versions/0.0.9/docs/ARCHITECTURE.md +262 -0
  487. package/.versions/0.0.9/docs/agent-fleet-setup.md +366 -0
  488. package/.versions/0.0.9/docs/claude-code-coms-bridge.md +109 -0
  489. package/.versions/0.0.9/docs/codex-remote-conductor.md +170 -0
  490. package/.versions/0.0.9/docs/coms-hermes-bridge.md +189 -0
  491. package/.versions/0.0.9/docs/getting-started.md +231 -0
  492. package/.versions/0.0.9/docs/npm-install.md +337 -0
  493. package/.versions/0.0.9/docs/opencode-setup.md +249 -0
  494. package/.versions/0.0.9/docs/pi-extensions.md +356 -0
  495. package/.versions/0.0.9/docs/pi-setup.md +476 -0
  496. package/.versions/0.0.9/docs/skill-anatomy.md +150 -0
  497. package/.versions/0.0.9/hermes/README.md +347 -0
  498. package/.versions/0.0.9/hermes/desktop-plugins/agent-fleet-herdr/plugin.js +1291 -0
  499. package/.versions/0.0.9/hermes/desktop-plugins/agent-fleet-herdr/presentation.js +672 -0
  500. package/.versions/0.0.9/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
  501. package/.versions/0.0.9/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
  502. package/.versions/0.0.9/hermes/gates/gate-o-capability.md +8 -0
  503. package/.versions/0.0.9/hermes/gates/gate-o-validator-fixtures.json +1 -0
  504. package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/activity.py +770 -0
  505. package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/coms_registry.py +134 -0
  506. package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/coms_send.py +350 -0
  507. package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/herdr_source.py +193 -0
  508. package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/manifest.json +4 -0
  509. package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/plugin_api.py +444 -0
  510. package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/sessions.py +205 -0
  511. package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/tasks.py +300 -0
  512. package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/watch.py +819 -0
  513. package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/plugin.yaml +8 -0
  514. package/.versions/0.0.9/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +139 -0
  515. package/.versions/0.0.9/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
  516. package/.versions/0.0.9/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
  517. package/.versions/0.0.9/hermes/skills/hub-conductor/SKILL.md +84 -0
  518. package/.versions/0.0.9/hermes/skills/hub-liaison/SKILL.md +84 -0
  519. package/.versions/0.0.9/hermes/skills/hub-watchdog/SKILL.md +76 -0
  520. package/.versions/0.0.9/hermes/skills/hub-watchdog/manifest.json +1 -0
  521. package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog.py +249 -0
  522. package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_actions.py +124 -0
  523. package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_contract.py +76 -0
  524. package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_delivery.py +10 -0
  525. package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_engine.py +128 -0
  526. package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_judgment.py +41 -0
  527. package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_recovery.py +103 -0
  528. package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_state.py +163 -0
  529. package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_transport.py +138 -0
  530. package/.versions/0.0.9/hermes/watchdog-tests/__init__.py +0 -0
  531. package/.versions/0.0.9/hooks/SIMPLIFY-IGNORE.md +90 -0
  532. package/.versions/0.0.9/hooks/coms-stop-hook.mjs +84 -0
  533. package/.versions/0.0.9/hooks/hooks.json +14 -0
  534. package/.versions/0.0.9/hooks/session-start.sh +74 -0
  535. package/.versions/0.0.9/hooks/simplify-ignore.sh +302 -0
  536. package/.versions/0.0.9/justfile +254 -0
  537. package/.versions/0.0.9/references/accessibility-checklist.md +160 -0
  538. package/.versions/0.0.9/references/definition-of-done.md +67 -0
  539. package/.versions/0.0.9/references/fleet-coordination-patterns.md +151 -0
  540. package/.versions/0.0.9/references/observability-checklist.md +91 -0
  541. package/.versions/0.0.9/references/orchestration-patterns.md +370 -0
  542. package/.versions/0.0.9/references/performance-checklist.md +153 -0
  543. package/.versions/0.0.9/references/prompting-patterns.md +380 -0
  544. package/.versions/0.0.9/references/security-checklist.md +179 -0
  545. package/.versions/0.0.9/references/testing-patterns.md +236 -0
  546. package/.versions/0.0.9/scripts/codex-conductor.ts +41 -0
  547. package/.versions/0.0.9/scripts/codex-remote-control.ts +167 -0
  548. package/.versions/0.0.9/scripts/coms-claude-bridge.ts +401 -0
  549. package/.versions/0.0.9/scripts/coms-cli.ts +484 -0
  550. package/.versions/0.0.9/scripts/coms-hermes-bridge.ts +413 -0
  551. package/.versions/0.0.9/scripts/fleet.ts +168 -0
  552. package/.versions/0.0.9/scripts/hermes-monitor-capability-runner.ts +25 -0
  553. package/.versions/0.0.9/scripts/hermes-monitor-scenario.ts +474 -0
  554. package/.versions/0.0.9/scripts/hermes-watchdog-capability-probe.ts +45 -0
  555. package/.versions/0.0.9/scripts/install-hermes-plugin.sh +180 -0
  556. package/.versions/0.0.9/scripts/lib/claude-bridge-core.ts +165 -0
  557. package/.versions/0.0.9/scripts/lib/codex-conductor.ts +88 -0
  558. package/.versions/0.0.9/scripts/lib/codex-remote-control.ts +480 -0
  559. package/.versions/0.0.9/scripts/lib/coms-envelope.ts +582 -0
  560. package/.versions/0.0.9/scripts/lib/fake-herdr-server.ts +88 -0
  561. package/.versions/0.0.9/scripts/lib/fleet-command.ts +111 -0
  562. package/.versions/0.0.9/scripts/lib/herdr-layout.ts +281 -0
  563. package/.versions/0.0.9/scripts/lib/hermes-bridge-core.ts +241 -0
  564. package/.versions/0.0.9/scripts/lib/hermes-monitor-events.ts +1 -0
  565. package/.versions/0.0.9/scripts/lib/hermes-monitor-herdr.ts +2 -0
  566. package/.versions/0.0.9/scripts/lib/hermes-monitor-model.ts +3 -0
  567. package/.versions/0.0.9/scripts/lib/hermes-monitor-registry.ts +2 -0
  568. package/.versions/0.0.9/scripts/lib/hermes-monitor-socket.ts +2 -0
  569. package/.versions/0.0.9/scripts/lib/hermes-monitor-store.ts +2 -0
  570. package/.versions/0.0.9/scripts/lib/monitor-env.ts +120 -0
  571. package/.versions/0.0.9/scripts/lib/peer-launch.ts +314 -0
  572. package/.versions/0.0.9/scripts/lib/persona-banner.ts +62 -0
  573. package/.versions/0.0.9/scripts/lib/spawn-stagger.ts +101 -0
  574. package/.versions/0.0.9/scripts/lib/team-project.ts +193 -0
  575. package/.versions/0.0.9/scripts/lib/team-snapshot.ts +147 -0
  576. package/.versions/0.0.9/scripts/peer-banner.ts +40 -0
  577. package/.versions/0.0.9/scripts/peer-launch.ts +259 -0
  578. package/.versions/0.0.9/scripts/team-snapshot.ts +237 -0
  579. package/.versions/0.0.9/scripts/team-up.ts +360 -0
  580. package/.versions/0.0.9/skills/_internal/grilling.md +11 -0
  581. package/.versions/0.0.9/skills/browser-testing-with-devtools/SKILL.md +352 -0
  582. package/.versions/0.0.9/skills/code-review-and-quality/SKILL.md +381 -0
  583. package/.versions/0.0.9/skills/compound-learning/SKILL.md +137 -0
  584. package/.versions/0.0.9/skills/context-engineering/SKILL.md +291 -0
  585. package/.versions/0.0.9/skills/deprecation-and-migration/SKILL.md +206 -0
  586. package/.versions/0.0.9/skills/designing-agents/SKILL.md +394 -0
  587. package/.versions/0.0.9/skills/designing-agents/pi-harness-authoring.md +222 -0
  588. package/.versions/0.0.9/skills/frontend-ui-engineering/SKILL.md +328 -0
  589. package/.versions/0.0.9/skills/git-workflow-and-versioning/SKILL.md +316 -0
  590. package/.versions/0.0.9/skills/guided-workspace-setup/SKILL.md +544 -0
  591. package/.versions/0.0.9/skills/guided-workspace-setup/companion-manifest.json +38 -0
  592. package/.versions/0.0.9/skills/idea-refine/SKILL.md +182 -0
  593. package/.versions/0.0.9/skills/idea-refine/examples.md +238 -0
  594. package/.versions/0.0.9/skills/idea-refine/frameworks.md +99 -0
  595. package/.versions/0.0.9/skills/idea-refine/refinement-criteria.md +113 -0
  596. package/.versions/0.0.9/skills/idea-refine/scripts/idea-refine.sh +15 -0
  597. package/.versions/0.0.9/skills/incremental-implementation/SKILL.md +287 -0
  598. package/.versions/0.0.9/skills/interview-me/SKILL.md +226 -0
  599. package/.versions/0.0.9/skills/orchestration-verification/SKILL.md +181 -0
  600. package/.versions/0.0.9/skills/peer-coms/SKILL.md +90 -0
  601. package/.versions/0.0.9/skills/performance-optimization/SKILL.md +350 -0
  602. package/.versions/0.0.9/skills/planning-and-task-breakdown/SKILL.md +236 -0
  603. package/.versions/0.0.9/skills/security-and-hardening/SKILL.md +461 -0
  604. package/.versions/0.0.9/skills/spec-driven-development/SKILL.md +245 -0
  605. package/.versions/0.0.9/skills/using-agent-skills/SKILL.md +199 -0
  606. package/.versions/0.0.9/systemd/user/agent-fleet-codex-remote-control.service.in +23 -0
  607. package/.versions/0.0.9/vendor/agent-skills-upstream/LICENSE +21 -0
  608. package/.versions/0.0.9/vendor/agent-skills-upstream/README.md +11 -0
  609. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/api-and-interface-design/SKILL.md +294 -0
  610. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/browser-testing-with-devtools/SKILL.md +317 -0
  611. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/ci-cd-and-automation/SKILL.md +390 -0
  612. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/code-review-and-quality/SKILL.md +396 -0
  613. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/code-simplification/SKILL.md +331 -0
  614. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/context-engineering/SKILL.md +289 -0
  615. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/debugging-and-error-recovery/SKILL.md +300 -0
  616. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/deprecation-and-migration/SKILL.md +247 -0
  617. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/documentation-and-adrs/SKILL.md +278 -0
  618. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/doubt-driven-development/SKILL.md +243 -0
  619. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/frontend-ui-engineering/SKILL.md +328 -0
  620. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/git-workflow-and-versioning/SKILL.md +355 -0
  621. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/idea-refine/SKILL.md +178 -0
  622. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/idea-refine/examples.md +238 -0
  623. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/idea-refine/frameworks.md +99 -0
  624. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/idea-refine/refinement-criteria.md +113 -0
  625. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/idea-refine/scripts/idea-refine.sh +15 -0
  626. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/incremental-implementation/SKILL.md +249 -0
  627. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/interview-me/SKILL.md +225 -0
  628. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/observability-and-instrumentation/SKILL.md +203 -0
  629. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/performance-optimization/SKILL.md +350 -0
  630. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/planning-and-task-breakdown/SKILL.md +234 -0
  631. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/security-and-hardening/SKILL.md +467 -0
  632. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/shipping-and-launch/SKILL.md +310 -0
  633. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/source-driven-development/SKILL.md +194 -0
  634. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/spec-driven-development/SKILL.md +206 -0
  635. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/test-driven-development/SKILL.md +383 -0
  636. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/using-agent-skills/SKILL.md +191 -0
  637. package/CHANGELOG.md +141 -0
  638. package/README.md +22 -5
  639. package/agents/architect.md +1 -0
  640. package/agents/bowser.md +1 -0
  641. package/agents/builder.md +1 -0
  642. package/agents/code-reviewer.md +8 -5
  643. package/agents/deep-researcher.md +2 -1
  644. package/agents/orchestrator.md +8 -1
  645. package/agents/plan-reviewer.md +25 -2
  646. package/agents/planner.md +3 -2
  647. package/agents/security-auditor.md +1 -0
  648. package/agents/test-engineer.md +3 -1
  649. package/agents/web-debugger.md +1 -0
  650. package/agents/web-performance-auditor.md +1 -0
  651. package/bin/build-manifest.js +68 -0
  652. package/bin/cli.js +679 -49
  653. package/bin/lib/apply.js +641 -0
  654. package/bin/lib/manifest.js +731 -0
  655. package/bin/lib/merge-forms.js +106 -0
  656. package/bin/lib/plan.js +569 -0
  657. package/bin/lib/state.js +213 -0
  658. package/bin/lib/verify.js +576 -0
  659. package/bin/snapshot-version.js +5 -0
  660. package/docs/ARCHITECTURE.md +53 -12
  661. package/docs/agent-fleet-setup.md +59 -48
  662. package/docs/getting-started.md +29 -6
  663. package/docs/npm-install.md +208 -31
  664. package/docs/opencode-setup.md +32 -0
  665. package/docs/pi-extensions.md +83 -13
  666. package/docs/pi-setup.md +164 -69
  667. package/install-manifest.json +3615 -0
  668. package/justfile +10 -1
  669. package/manifest-meta.json +472 -0
  670. package/package.json +8 -3
  671. package/scripts/fleet.ts +22 -3
  672. package/scripts/lib/fleet-command.ts +5 -3
  673. package/scripts/lib/herdr-layout.ts +18 -0
  674. package/scripts/lib/peer-launch.ts +314 -0
  675. package/scripts/lib/team-project.ts +3 -1
  676. package/scripts/peer-launch.ts +259 -0
  677. package/skills/browser-testing-with-devtools/SKILL.md +3 -4
  678. package/skills/guided-workspace-setup/SKILL.md +172 -490
  679. package/skills/guided-workspace-setup/companion-manifest.json +2 -0
  680. package/skills/planning-and-task-breakdown/SKILL.md +18 -0
  681. package/skills/spec-driven-development/SKILL.md +12 -0
  682. package/.pi/harnesses/agent-hub/spawned-peers.js +0 -74
@@ -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.
@@ -4,14 +4,21 @@
4
4
  #
5
5
  # Profiles only switch the personas they list; everyone else keeps their
6
6
  # current model. They never touch delegate-children (`subagents:`) models.
7
- max:
7
+ mix-max:
8
+ code-reviewer: github-copilot/claude-opus-5
9
+ builder: openai-codex/gpt-5.6-sol
10
+ planner: github-copilot/claude-fable-5
11
+ plan-reviewer: openai-codex/gpt-5.6-sol
12
+ security-auditor: xai/grok-4.5
13
+ test-engineer: xai/grok-4.5
14
+ sol:
8
15
  code-reviewer: openai-codex/gpt-5.6-sol
9
16
  builder: openai-codex/gpt-5.6-sol
10
17
  planner: openai-codex/gpt-5.6-sol
11
18
  plan-reviewer: openai-codex/gpt-5.6-sol
12
19
  security-auditor: openai-codex/gpt-5.6-sol
13
20
  test-engineer: openai-codex/gpt-5.6-sol
14
- budget:
21
+ terra:
15
22
  code-reviewer: openai-codex/gpt-5.6-terra
16
23
  builder: openai-codex/gpt-5.6-terra
17
24
  planner: openai-codex/gpt-5.6-terra
@@ -4,6 +4,12 @@
4
4
  # (requires a running herdr server — https://herdr.dev),
5
5
  # using the hidden `_peer` helper (guarded Fleet Core + coms + the persona).
6
6
  #
7
+ # A team is NOT required to launch a single peer: `just fleet peer <name>` puts
8
+ # one peer (pi or `--runner claude-code`) in its own pane — splitting the current
9
+ # pane inside Herdr, else creating a one-pane workspace, or `--here` for the
10
+ # calling terminal. A name declared below keeps its runner/model/extensions/
11
+ # env_file; an undeclared name works too.
12
+ #
7
13
  # Each peer entry:
8
14
  # name — coms identity (the addressable peer name); overrides persona frontmatter
9
15
  # persona — file under agents/ (without .md); its body is the role, its
@@ -37,10 +43,10 @@ full:
37
43
  extensions: chrome-devtools-mcp
38
44
  - name: documenter
39
45
  persona: documenter
40
- model: openai-codex/gpt-5.6-terra
46
+ model: openai-codex/gpt-5.6-terra
41
47
  - name: researcher
42
48
  persona: researcher
43
- model: openai-codex/gpt-5.6-luna
49
+ model: openai-codex/gpt-5.6-luna
44
50
 
45
51
  web:
46
52
  - name: web-debugger
@@ -58,22 +64,12 @@ docs:
58
64
 
59
65
  # Mirrored from .pi/agents/teams.yaml for `just fleet team <team>`.
60
66
  default:
61
- - name: planner
62
- persona: planner
63
- model: openai-codex/gpt-5.6-sol
64
- - name: plan-reviewer
65
- runner: claude-code
66
- - name: builder
67
- persona: builder
68
- model: openai-codex/gpt-5.6-terra
69
- - name: test-engineer
70
- persona: test-engineer
71
- model: openai-codex/gpt-5.6-terra
72
67
  - name: code-reviewer
73
68
  runner: claude-code
74
- - name: documenter
75
- persona: documenter
69
+ - name: web-debugger
70
+ persona: web-debugger
76
71
  model: openai-codex/gpt-5.6-terra
72
+ extensions: chrome-devtools-mcp
77
73
 
78
74
  debug:
79
75
  - name: test-engineer
@@ -143,4 +139,4 @@ plan:
143
139
  - name: planner
144
140
  runner: claude-code
145
141
  - name: code-reviewer
146
- runner: claude-code
142
+ runner: claude-code
@@ -2,13 +2,15 @@
2
2
  # researcher / deep-researcher are not listed — they are always available through spawn_research.
3
3
 
4
4
  default:
5
- - planner
6
- - plan-reviewer
7
5
  - builder
8
6
  - test-engineer
9
7
  - code-reviewer
10
8
  - documenter
11
9
 
10
+ plan:
11
+ - planner
12
+ - plan-reviewer
13
+
12
14
  debug:
13
15
  - test-engineer
14
16
  - builder
@@ -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`).
@@ -75,11 +75,11 @@ The agent cannot trigger it; only you can.
75
75
 
76
76
  ## Install
77
77
 
78
- Auto-discovered like the other always-on utilities — drop or symlink it under
78
+ Auto-discovered like the other always-on utilities once it is under
79
79
  `.pi/extensions/` (see [docs/pi-setup.md](../../../docs/pi-setup.md)):
80
80
 
81
81
  ```bash
82
- ln -s /path/to/agent-fleet/.pi/extensions/btw .pi/extensions/btw
82
+ npx @chankov/agent-fleet install --agent pi --items pi-extension:btw --yes
83
83
  ```
84
84
 
85
85
  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.
@@ -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
@@ -282,7 +284,7 @@ the input box) and back. The current mode and binding are shown in the footer
282
284
  ### Version footer
283
285
 
284
286
  `agent-hub` renders its local harness version first in its custom footer:
285
- `v<version> · <model><thinking> · <team>`. It replaces pi's default footer, so it does **not**
287
+ `agent fleet v<version> · <model><thinking> · <team>`. It replaces pi's default footer, so it does **not**
286
288
  consume or render the shared version status; it reads its own adjacent stamped manifest directly.
287
289
  The three persistent-UI harnesses (`agent-hub`, `coms`, and
288
290
  `damage-control-continue`) still register that one shared key, which gives default footers one
@@ -294,6 +296,13 @@ by `bin/sync-harness-versions.js`. Its local `version.ts` reader intentionally s
294
296
  harness for copied or symlinked installs, but those installs still need the pre-existing full
295
297
  `.pi/harnesses/` dependency installation.
296
298
 
299
+ The `agent fleet` half of the label is an OSC 8 terminal hyperlink to the project homepage —
300
+ clickable in terminals that support hyperlinks, ignored (rendered as plain text) elsewhere, and
301
+ free of footer columns because pi strips OSC sequences before measuring width. It opens the
302
+ repository in a browser, not a TUI panel: pi has no mouse tracking, so a click never reaches the
303
+ harness. `AGENT_FLEET_NO_LINKS=1` restores the plain label on multiplexers that mangle OSC 8
304
+ (GNU screen, tmux before 3.4).
305
+
297
306
  ### Voice dictation indicator
298
307
 
299
308
  The custom footer renders the optional [`pi-voice-stt`](../../extensions/pi-voice-stt/README.md)
@@ -433,8 +442,49 @@ max-research-per-turn: 4 # integer or off
433
442
  turn-wall-time-s: 3600 # integer or off
434
443
  agent-turn-timeout-s: 1800 # whole-run deadline per spawned run; integer or off
435
444
  session-recycle-runs: 5 # recycle a specialist session after N resumed runs; integer or off
445
+ run-history-keep: 10 # previous sessions' artifact archives to retain; integer or off
436
446
  ```
437
447
 
448
+ #### Task budget (the bound a turn window cannot provide)
449
+
450
+ A per-message allowance cannot bound a task. In the run this guardrail comes from, every
451
+ steering message opened a fresh window of 8 dispatches and 60 minutes, so no counter ever
452
+ bound: one workspace stayed open **47 hours**, while the same change made in a narrow
453
+ workspace took **13 minutes**.
454
+
455
+ So there is a second envelope, **`TASK_BUDGET_MULTIPLIER` (3) × the turn envelope**, whose
456
+ counters are **not** reset by a user message:
457
+
458
+ | | per turn (standard, `feature`) | per task |
459
+ |---|---|---|
460
+ | `dispatch_agent` | 6 | 18 |
461
+ | `spawn_research` | 4 | 12 |
462
+ | clock | 60 min wall | 180 min **active** |
463
+
464
+ Exhausting it is a **hard stop**: the refusal says so, and another user message does not
465
+ reopen it. Only `/af-new-task [label]` (or `set_task_tier` with `new_task: true`) opens a
466
+ new task window — clearing the counters, the tier, the review-round count, the duplicate
467
+ guard, and any external-blocker stop. The status chip shows both (`… · task 4/18`).
468
+
469
+ The reasoning: a task that has burned three full envelopes has not hit a budget problem, it
470
+ has outgrown its scope, and re-scoping is the human's call.
471
+
472
+ The task clock charges **active time only** — turns that actually ran, each minus the time
473
+ the dispatcher sat blocked on `ask_user`. Inter-turn idle costs nothing, because no turn is
474
+ open across it. Raw wall clock would bill a lunch break, an overnight pause, and every long
475
+ human answer against the task; at `fast` mode's 45-minute envelope a coffee break would
476
+ hard-stop a task with two dispatches spent. A false stop is worse than no stop — it teaches
477
+ people to reset the task window reflexively, and that reset is the one thing that has to
478
+ stay deliberate. Dispatch and research counts remain the honest hard stops.
479
+
480
+ The **auto-research pipe** (specialist emits `NEEDS_RESEARCH`, the hub fans out read-only
481
+ helpers in code) stays exempt from the TURN budget — it is hub mechanics, not a dispatcher
482
+ decision, and it must not steal the dispatcher's slots — but it **is** charged against the
483
+ task envelope. At 2 rounds × 4 questions per dispatch and 18 dispatches per task, leaving it
484
+ uncounted would have put 144 research runs inside the bound that is supposed to be the outer
485
+ one. When the task's research envelope is spent the pipe does not spawn and the specialist is
486
+ not resumed; the dispatch result says so.
487
+
438
488
  Two related always-on behaviors: specialist **context pressure is measured over
439
489
  input + cacheRead + cacheWrite** (resumed sessions re-send their whole accumulated context
440
490
  as cache reads — counting `input` alone hid that entirely), and a specialist session is
@@ -479,17 +529,103 @@ can no longer hold its parent for hours.
479
529
 
480
530
  ### Task triage (complexity tiers)
481
531
 
482
- The dispatcher classifies each user turn with the `set_task_tier` tool BEFORE its first
532
+ The dispatcher classifies the current TASK with the `set_task_tier` tool BEFORE its first
483
533
  dispatch — `trivial` / `small` / `feature` / `project` — and the hub lowers the enforced
484
534
  dispatch/research caps to **min(mode, tier)**: trivial = 1 dispatch / 1 research,
485
- small = 2 / 2, feature = 6 / 4, `project` defers to the mode. Skipping the call makes the
486
- first dispatch assume `feature` (except in strict mode, where tiers are opt-in). The tier
487
- resets every user turn and shows in the `hub-mode` status chip (`Mode: standard·small · …`).
488
- The system prompt ties the tier to the anti-over-engineering rules: a provided plan is a
489
- spec (no re-planning), assertions stay ≤3 for trivial/small asks, and "using every persona"
490
- is called out as a smell. Two hygiene guards are enforced in code, not prose: a
491
- **duplicate-dispatch guard** refuses re-dispatching the same agent with a near-identical
492
- task inside one turn, and every budget/duplicate refusal is counted in `/af-hub-report`.
535
+ small = 2 / 2, feature = 6 / 4, `project` defers to the mode. The tier shows in the
536
+ `hub-mode` status chip (`Mode: standard·small · …`), with a trailing `?` while it is only
537
+ assumed.
538
+
539
+ Skipping the call makes the hub assume **`small`**, not `feature`. Because the tier is
540
+ task-scoped, a skipped triage latches for the whole task — and skipped triage is precisely
541
+ the case where the dispatcher was not thinking about proportionality. Assuming `feature`
542
+ there would unlock planner/plan-reviewer/security-auditor, loosen the review caps, and hand
543
+ out the full feature envelope: the over-apparatus failure mode, granted by forgetting a tool
544
+ call. Assuming `small` costs one explicit escalation when the work really is bigger, which
545
+ is the cheap direction to be wrong in. An assumed tier is not a ratchet baseline either: the
546
+ dispatcher's own first `set_task_tier` is treated as an initial declaration, so it never
547
+ needs a `reason` it had no way to know it needed.
548
+
549
+ The tier is **task-scoped and ratcheted**. It survives the user's next message, and it
550
+ moves in one direction cheaply: **lowering it is always free, raising it requires a
551
+ `reason`** naming what the ask turned out to contain (refused in code otherwise). A
552
+ turn-scoped tier could not bind on a steered run — every correction reset it to null, the
553
+ next dispatch re-assumed `feature`, and the effective tier drifted to the ceiling, because
554
+ nobody ever re-declares `trivial` after a steering message.
555
+
556
+ Three guards are enforced in code, not prose:
557
+
558
+ - **Duplicate-dispatch guard** — refuses re-dispatching the same agent with a
559
+ near-identical task inside one turn.
560
+ - **Tier persona gate** — at `trivial`/`small`, `dispatch_agent`/`spawn_research` refuse
561
+ `planner`, `plan-reviewer`, `architect`, `security-auditor` and `deep-researcher`
562
+ (`run-budget.js`). Each opens a document/finding loop whose output then has to be
563
+ executed and re-reviewed; the escape hatch is raising the tier *with a reason*, not a
564
+ flag. The refusal costs no budget slot.
565
+ - **Review round cap** — review dispatches per TASK are capped by tier (trivial/small 1,
566
+ feature 2, project uncapped) and the (N+1)-th is refused without spending a budget slot.
567
+ This is where the review ratchet is actually cut: findings become requirements and the
568
+ enlarged requirement set justifies the next round, so the round is the thing to bound.
569
+ - **Review finding budget** — a review persona's dispatch carries a blocking-finding cap
570
+ tied to the tier (trivial 1, small 2, feature 5, project uncapped) plus the rule that a
571
+ blocking finding may only enforce an invariant the task/plan/rules already state. The hub
572
+ **counts** what came back (`review-findings.js`) and appends a visible notice when the
573
+ return exceeds the cap — it never reclassifies a finding. No rule the hub can evaluate
574
+ distinguishes "invents a manifest nobody asked for" from "this logs a connection string";
575
+ both are a heading and a bullet, and silently demoting the second by position would, on
576
+ the day it matters, move a real security finding into the section nobody acts on.
577
+
578
+ Every budget/gate refusal is counted in `/af-hub-report`.
579
+
580
+ ### Docs lane (`docs-lane.js`)
581
+
582
+ A dispatch whose declared `scope` is documentation only — `Docs/**`, `**/*.md`,
583
+ `artifacts/evidence/*.png`, `.changeset/**` — runs in the single-worker docs lane:
584
+
585
+ - dispatching a review persona (`code-reviewer`, `plan-reviewer`, `security-auditor`,
586
+ `test-engineer`) on it is **refused** and costs no budget slot;
587
+ - any other persona's result carries a note telling the dispatcher not to open a review
588
+ gate for it.
589
+
590
+ An absent or empty `scope` is never the lighter lane — unknown is not docs. The refusal is
591
+ overridable per dispatch with `review_reason: "<why>"` for the cases that do warrant a gate
592
+ (the doc publishes a credential, or states a contract other systems depend on).
593
+
594
+ ### External-blocker stop (`external-blocker.js`)
595
+
596
+ A specialist that cannot proceed without something outside the fleet's reach — an account,
597
+ a permission, a deployment credential, a telemetry destination, a console-only action —
598
+ emits `EXTERNAL_BLOCKED: <what is missing, who owns it, what it blocks>` (the protocol is
599
+ injected into every specialist prompt). The hub records it and **refuses the next
600
+ dispatch/research** with an owner-escalation packet: what is missing and who owns it, which
601
+ assertions are blocked, what is already proven and where, and the human's options (provide
602
+ access / waive as UNPROVEN / drop from scope).
603
+
604
+ The gate opens when the human has been addressed — an `ask_user` call, or the next user
605
+ message. Without `ask_user` installed it fires exactly once, so a session that cannot reach
606
+ the human can still finish and report instead of deadlocking.
607
+
608
+ This exists because the alternative is the most expensive failure mode observed: with no
609
+ correlation destination available, a run kept substituting internal work for the missing
610
+ external fact — scripts, manifests, fixtures, diagnostic packets — for hours, and the
611
+ assertion still ended UNPROVEN.
612
+
613
+ ### Immutable per-run artifact namespaces (`run-namespace.js`)
614
+
615
+ Session start used to `rm -rf` `.pi/agent-sessions/artifacts/`, and specialist returns were
616
+ named by a per-session counter (`returns/builder-run1.md`). Both halves of that failed at
617
+ once: the next session's `builder-run1.md` claimed the same path as the previous one's, and
618
+ the wipe deleted the originals first — a post-mortem had to record eleven implementation
619
+ returns and two review artifacts as NOT RECOVERABLE.
620
+
621
+ Now each session **archives** the previous session's artifacts into
622
+ `.pi/agent-sessions/runs/<runId>/artifacts/` — a namespace written once and never reused —
623
+ alongside a read-only `meta.json` (run id, archive time, project, workspace, per-kind
624
+ artifact counts) and an appended `runs/index.json`. `runId` is a sortable UTC timestamp plus
625
+ a random suffix, so two sessions starting in the same second still get distinct namespaces.
626
+ Retention is `run-history-keep` (default 10, `off` keeps everything); an empty artifact tree
627
+ is not archived. If archiving fails the artifacts are **left in place** rather than deleted:
628
+ a stale tree is recoverable, a deleted one is not.
493
629
 
494
630
  ### Drift watchdog (in-flight observation)
495
631
 
@@ -548,10 +684,18 @@ Inside a [herdr](https://herdr.dev) pane with a live server, the dispatcher's to
548
684
  surface additionally gets (absent otherwise, like coms):
549
685
 
550
686
  - `herdr_spawn_peer` — stand up a persona peer (joins the coms pool via `just _peer`) or a
551
- raw command pane in the current workspace. A persona peer **boots idle** and does nothing until
552
- a `coms_send` reaches it, so the call waits (bounded, ~45s) for it to register and returns
553
- `peer_ready` plus its coms name instead of a bare pane id. Peers spawned but never addressed are
554
- named at turn end and in `/af-hub-report` with a close suggestion — closing stays the human's call
687
+ raw command pane in the current workspace. The peer joins **this session's `--project` pool**, and
688
+ a name declared in `.pi/agents/peers.yaml` keeps its declared `runner:`/`extensions:`/`env_file:`,
689
+ so a spawn by name is the same agent a team launch would produce. A persona peer **boots idle**
690
+ and does nothing until a `coms_send` reaches it, so the call waits (bounded, ~45s) for it to
691
+ register and returns `peer_ready` plus its coms name instead of a bare pane id; on failure it
692
+ returns the pane's last output, which means the peer did not start rather than that it is slow.
693
+ Peers spawned but never addressed are named at turn end and in `/af-hub-report` with a close
694
+ suggestion — closing stays the human's call.
695
+ Mechanism: herdr's `pane.split` takes **no command** — it opens a shell — so the spawn splits,
696
+ waits for the pane's prompt, and types the argv (text and Enter sent separately, because bash
697
+ bracketed paste would swallow a newline). Only `layout.apply` pane nodes carry an argv, which is
698
+ why `just fleet team` was never affected by this
555
699
  - `herdr_read_pane` — bounded `pane.read` (≤200 lines), read-to-decide on workers/tools;
556
700
  messaging still goes through coms, and peer busy state comes from `coms_list`, not from
557
701
  reading the screen