@chankov/agent-fleet 2.0.8 → 2.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 (912) hide show
  1. package/.pi/extensions/pi-voice-stt/README.md +24 -5
  2. package/.pi/extensions/pi-voice-stt/examples/stt.json +4 -4
  3. package/.pi/harnesses/agent-hub/README.md +20 -6
  4. package/.pi/harnesses/agent-hub/footer.ts +1 -1
  5. package/.pi/harnesses/agent-hub/index.ts +47 -66
  6. package/.pi/harnesses/agent-hub/input/shortcuts.ts +2 -0
  7. package/.pi/harnesses/agent-hub/package.json +1 -1
  8. package/.pi/harnesses/agent-hub/return-contract.js +34 -0
  9. package/.pi/harnesses/agent-hub/tools/dispatch-execution.ts +80 -18
  10. package/.pi/harnesses/agent-hub/ui/fleet-actions.ts +76 -0
  11. package/.pi/harnesses/agent-hub/ui/fleet-dashboard.ts +16 -42
  12. package/.pi/harnesses/agent-hub/ui/fleet-editor.ts +44 -0
  13. package/.pi/harnesses/agent-hub/ui/fleet-source.ts +157 -0
  14. package/.pi/harnesses/agent-hub/ui/grid.ts +145 -33
  15. package/.pi/harnesses/agent-hub/ui/running-strip.ts +2 -139
  16. package/.pi/harnesses/coms/package.json +1 -1
  17. package/.pi/harnesses/damage-control-continue/package.json +1 -1
  18. package/.pi/harnesses/lib/changed-file-diagnostics.ts +642 -0
  19. package/.pi/harnesses/lib/fleet-dashboard-ops.ts +17 -0
  20. package/.pi/harnesses/lib/fleet-dashboard-view.ts +22 -36
  21. package/.pi/harnesses/lib/fleet-read-model.ts +109 -27
  22. package/.pi/harnesses/lib/fleet-strip-controller.ts +74 -0
  23. package/.pi/harnesses/lib/fleet-strip-view.ts +132 -0
  24. package/.versions/2.0.10/.pi/agent-fleet/hermes/README.md +347 -0
  25. package/.versions/2.0.10/.pi/agent-fleet/hermes/desktop-plugins/agent-fleet-herdr/plugin.js +1291 -0
  26. package/.versions/2.0.10/.pi/agent-fleet/hermes/desktop-plugins/agent-fleet-herdr/presentation.js +672 -0
  27. package/.versions/2.0.10/.pi/agent-fleet/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
  28. package/.versions/2.0.10/.pi/agent-fleet/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
  29. package/.versions/2.0.10/.pi/agent-fleet/hermes/gates/gate-o-capability.md +8 -0
  30. package/.versions/2.0.10/.pi/agent-fleet/hermes/gates/gate-o-validator-fixtures.json +1 -0
  31. package/.versions/2.0.10/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/activity.py +773 -0
  32. package/.versions/2.0.10/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/coms_registry.py +134 -0
  33. package/.versions/2.0.10/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/coms_send.py +350 -0
  34. package/.versions/2.0.10/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/herdr_source.py +193 -0
  35. package/.versions/2.0.10/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/manifest.json +4 -0
  36. package/.versions/2.0.10/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/plugin_api.py +444 -0
  37. package/.versions/2.0.10/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/sessions.py +205 -0
  38. package/.versions/2.0.10/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/tasks.py +300 -0
  39. package/.versions/2.0.10/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/watch.py +819 -0
  40. package/.versions/2.0.10/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/plugin.yaml +8 -0
  41. package/.versions/2.0.10/.pi/agent-fleet/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +139 -0
  42. package/.versions/2.0.10/.pi/agent-fleet/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
  43. package/.versions/2.0.10/.pi/agent-fleet/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
  44. package/.versions/2.0.10/.pi/agent-fleet/hermes/skills/hub-conductor/SKILL.md +84 -0
  45. package/.versions/2.0.10/.pi/agent-fleet/hermes/skills/hub-liaison/SKILL.md +84 -0
  46. package/.versions/2.0.10/.pi/agent-fleet/hermes/skills/hub-watchdog/SKILL.md +76 -0
  47. package/.versions/2.0.10/.pi/agent-fleet/hermes/skills/hub-watchdog/manifest.json +1 -0
  48. package/.versions/2.0.10/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog.py +249 -0
  49. package/.versions/2.0.10/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_actions.py +124 -0
  50. package/.versions/2.0.10/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_contract.py +76 -0
  51. package/.versions/2.0.10/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_delivery.py +10 -0
  52. package/.versions/2.0.10/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_engine.py +128 -0
  53. package/.versions/2.0.10/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_judgment.py +41 -0
  54. package/.versions/2.0.10/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_recovery.py +103 -0
  55. package/.versions/2.0.10/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_state.py +163 -0
  56. package/.versions/2.0.10/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_transport.py +138 -0
  57. package/.versions/2.0.10/.pi/agent-fleet/hermes/watchdog-tests/__init__.py +0 -0
  58. package/.versions/2.0.10/.pi/agent-fleet/hooks/coms-stop-hook.mjs +84 -0
  59. package/.versions/2.0.10/.pi/agent-fleet/scripts/claude-code-preflight.ts +70 -0
  60. package/.versions/2.0.10/.pi/agent-fleet/scripts/coms-claude-bridge.ts +411 -0
  61. package/.versions/2.0.10/.pi/agent-fleet/scripts/coms-cli.ts +425 -0
  62. package/.versions/2.0.10/.pi/agent-fleet/scripts/coms-hermes-bridge.ts +413 -0
  63. package/.versions/2.0.10/.pi/agent-fleet/scripts/fleet-codex-client.ts +69 -0
  64. package/.versions/2.0.10/.pi/agent-fleet/scripts/fleet-codex-read.py +148 -0
  65. package/.versions/2.0.10/.pi/agent-fleet/scripts/fleet.ts +216 -0
  66. package/.versions/2.0.10/.pi/agent-fleet/scripts/flow.ts +137 -0
  67. package/.versions/2.0.10/.pi/agent-fleet/scripts/hermes-monitor-capability-runner.ts +25 -0
  68. package/.versions/2.0.10/.pi/agent-fleet/scripts/hermes-monitor-scenario.ts +474 -0
  69. package/.versions/2.0.10/.pi/agent-fleet/scripts/hermes-watchdog-capability-probe.ts +45 -0
  70. package/.versions/2.0.10/.pi/agent-fleet/scripts/install-hermes-plugin.sh +180 -0
  71. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/claude-bridge-core.ts +210 -0
  72. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/coms-envelope.ts +582 -0
  73. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/fake-herdr-server.ts +88 -0
  74. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/fleet-codex-catalog.ts +63 -0
  75. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/fleet-codex-operations.ts +190 -0
  76. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/fleet-codex-session.ts +166 -0
  77. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/fleet-codex-transport.ts +124 -0
  78. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/fleet-command.ts +252 -0
  79. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/flow-command.ts +93 -0
  80. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/flow-maintenance.ts +230 -0
  81. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/herdr-layout.ts +281 -0
  82. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/hermes-bridge-core.ts +241 -0
  83. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/hermes-monitor-events.ts +1 -0
  84. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/hermes-monitor-herdr.ts +2 -0
  85. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/hermes-monitor-model.ts +3 -0
  86. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/hermes-monitor-registry.ts +2 -0
  87. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/hermes-monitor-socket.ts +2 -0
  88. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/hermes-monitor-store.ts +2 -0
  89. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/monitor-env.ts +146 -0
  90. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/peer-launch.ts +318 -0
  91. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/persona-banner.ts +62 -0
  92. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/persona-dirs.ts +25 -0
  93. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/runtime-dependencies.js +124 -0
  94. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/spawn-stagger.ts +101 -0
  95. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/team-project.ts +178 -0
  96. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/team-snapshot.ts +147 -0
  97. package/.versions/2.0.10/.pi/agent-fleet/scripts/package-lock.json +35 -0
  98. package/.versions/2.0.10/.pi/agent-fleet/scripts/package.json +9 -0
  99. package/.versions/2.0.10/.pi/agent-fleet/scripts/peer-banner.ts +41 -0
  100. package/.versions/2.0.10/.pi/agent-fleet/scripts/peer-launch.ts +283 -0
  101. package/.versions/2.0.10/.pi/agent-fleet/scripts/team-snapshot.ts +237 -0
  102. package/.versions/2.0.10/.pi/agent-fleet/scripts/team-up.ts +378 -0
  103. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/agent-phase.ts +133 -0
  104. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/changes.ts +61 -0
  105. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/debate.ts +149 -0
  106. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/env.ts +34 -0
  107. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/envelopes.ts +169 -0
  108. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/gates.ts +81 -0
  109. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/git.ts +96 -0
  110. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/merge.ts +95 -0
  111. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/model-profile.ts +22 -0
  112. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/model-visibility.ts +92 -0
  113. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/permissions.ts +130 -0
  114. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/personas.ts +57 -0
  115. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/poll.ts +86 -0
  116. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/quality.ts +64 -0
  117. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/run.ts +108 -0
  118. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/trace.ts +34 -0
  119. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/voices.ts +128 -0
  120. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/writer-lease.ts +112 -0
  121. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/tsconfig.json +22 -0
  122. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/wf-build-test.ts +61 -0
  123. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/wf-debate.ts +87 -0
  124. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/wf-document.ts +50 -0
  125. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/wf-poll.ts +95 -0
  126. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/wf-quality.ts +20 -0
  127. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/wf-scout.ts +38 -0
  128. package/.versions/2.0.10/.pi/agents/dispatch-policy.yaml +32 -0
  129. package/.versions/2.0.10/.pi/agents/model-profiles.yaml +83 -0
  130. package/.versions/2.0.10/.pi/agents/peers.yaml +147 -0
  131. package/.versions/2.0.10/.pi/agents/teams.yaml +41 -0
  132. package/.versions/2.0.10/.pi/agents/voices.yaml +13 -0
  133. package/.versions/2.0.10/.pi/damage-control-rules.yaml +297 -0
  134. package/.versions/2.0.10/.pi/extensions/btw/README.md +120 -0
  135. package/.versions/2.0.10/.pi/extensions/btw/index.ts +914 -0
  136. package/.versions/2.0.10/.pi/extensions/btw/package.json +6 -0
  137. package/.versions/2.0.10/.pi/extensions/btw/state.js +179 -0
  138. package/.versions/2.0.10/.pi/extensions/chrome-devtools-mcp/README.md +55 -0
  139. package/.versions/2.0.10/.pi/extensions/chrome-devtools-mcp/index.ts +93 -0
  140. package/.versions/2.0.10/.pi/extensions/chrome-devtools-mcp/package.json +6 -0
  141. package/.versions/2.0.10/.pi/extensions/compact-and-continue/README.md +42 -0
  142. package/.versions/2.0.10/.pi/extensions/compact-and-continue/index.ts +120 -0
  143. package/.versions/2.0.10/.pi/extensions/compact-and-continue/package.json +6 -0
  144. package/.versions/2.0.10/.pi/extensions/mcp-bridge/README.md +46 -0
  145. package/.versions/2.0.10/.pi/extensions/mcp-bridge/index.ts +206 -0
  146. package/.versions/2.0.10/.pi/extensions/mcp-bridge/package.json +6 -0
  147. package/.versions/2.0.10/.pi/extensions/package-lock.json +1175 -0
  148. package/.versions/2.0.10/.pi/extensions/package.json +9 -0
  149. package/.versions/2.0.10/.pi/extensions/pi-voice-stt/README.md +224 -0
  150. package/.versions/2.0.10/.pi/extensions/pi-voice-stt/config.ts +198 -0
  151. package/.versions/2.0.10/.pi/extensions/pi-voice-stt/examples/stt.json +35 -0
  152. package/.versions/2.0.10/.pi/extensions/pi-voice-stt/index.ts +248 -0
  153. package/.versions/2.0.10/.pi/extensions/pi-voice-stt/package.json +6 -0
  154. package/.versions/2.0.10/.pi/extensions/pi-voice-stt/providers.ts +214 -0
  155. package/.versions/2.0.10/.pi/extensions/pi-voice-stt/recorder.ts +158 -0
  156. package/.versions/2.0.10/.pi/harnesses/agent-hub/README.md +1217 -0
  157. package/.versions/2.0.10/.pi/harnesses/agent-hub/acceptance.ts +62 -0
  158. package/.versions/2.0.10/.pi/harnesses/agent-hub/access-approval.ts +135 -0
  159. package/.versions/2.0.10/.pi/harnesses/agent-hub/artifacts.js +146 -0
  160. package/.versions/2.0.10/.pi/harnesses/agent-hub/assertion-ledger.js +58 -0
  161. package/.versions/2.0.10/.pi/harnesses/agent-hub/backend-policy.js +174 -0
  162. package/.versions/2.0.10/.pi/harnesses/agent-hub/budget-continuation.ts +13 -0
  163. package/.versions/2.0.10/.pi/harnesses/agent-hub/budget-recovery.ts +97 -0
  164. package/.versions/2.0.10/.pi/harnesses/agent-hub/capability-confirmation.ts +47 -0
  165. package/.versions/2.0.10/.pi/harnesses/agent-hub/capability-packs.ts +180 -0
  166. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/agent-model-thinking.ts +10 -0
  167. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/agent-model.ts +10 -0
  168. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/agent-models-substitute.ts +10 -0
  169. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/agents-add.ts +9 -0
  170. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/agents-drop.ts +9 -0
  171. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/agents-history.ts +9 -0
  172. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/agents-kill.ts +10 -0
  173. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/agents-list.ts +9 -0
  174. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/agents-restart.ts +10 -0
  175. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/agents-save.ts +9 -0
  176. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/agents-team.ts +9 -0
  177. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/budget-continue.ts +10 -0
  178. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/compound.ts +9 -0
  179. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/coms.ts +9 -0
  180. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/context-command.ts +9 -0
  181. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/context.ts +43 -0
  182. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/debate.ts +9 -0
  183. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/dispatch-policy.ts +9 -0
  184. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/handoff.ts +10 -0
  185. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/hub-report.ts +9 -0
  186. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/models.ts +10 -0
  187. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/poll.ts +9 -0
  188. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/retry.ts +10 -0
  189. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/watchdog.ts +9 -0
  190. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/work-mode.ts +29 -0
  191. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/zoom.ts +10 -0
  192. package/.versions/2.0.10/.pi/harnesses/agent-hub/config/agents.ts +177 -0
  193. package/.versions/2.0.10/.pi/harnesses/agent-hub/config/model-profiles.ts +216 -0
  194. package/.versions/2.0.10/.pi/harnesses/agent-hub/config/overrides.ts +153 -0
  195. package/.versions/2.0.10/.pi/harnesses/agent-hub/context/agent-state.ts +30 -0
  196. package/.versions/2.0.10/.pi/harnesses/agent-hub/context/assertions-artifacts.ts +213 -0
  197. package/.versions/2.0.10/.pi/harnesses/agent-hub/context/budgets.ts +202 -0
  198. package/.versions/2.0.10/.pi/harnesses/agent-hub/context/hub-state.ts +40 -0
  199. package/.versions/2.0.10/.pi/harnesses/agent-hub/context-budget-snapshot.ts +105 -0
  200. package/.versions/2.0.10/.pi/harnesses/agent-hub/context-pressure.ts +191 -0
  201. package/.versions/2.0.10/.pi/harnesses/agent-hub/context-window.js +106 -0
  202. package/.versions/2.0.10/.pi/harnesses/agent-hub/debate-command.ts +176 -0
  203. package/.versions/2.0.10/.pi/harnesses/agent-hub/delegate.ts +446 -0
  204. package/.versions/2.0.10/.pi/harnesses/agent-hub/dispatch-coms.ts +237 -0
  205. package/.versions/2.0.10/.pi/harnesses/agent-hub/dispatch-core.ts +27 -0
  206. package/.versions/2.0.10/.pi/harnesses/agent-hub/dispatch-native-complete.ts +154 -0
  207. package/.versions/2.0.10/.pi/harnesses/agent-hub/dispatch-native-prepare.ts +156 -0
  208. package/.versions/2.0.10/.pi/harnesses/agent-hub/dispatch-native-spawn.ts +193 -0
  209. package/.versions/2.0.10/.pi/harnesses/agent-hub/dispatch-native-types.ts +230 -0
  210. package/.versions/2.0.10/.pi/harnesses/agent-hub/dispatch-native.ts +213 -0
  211. package/.versions/2.0.10/.pi/harnesses/agent-hub/dispatch-observability.ts +225 -0
  212. package/.versions/2.0.10/.pi/harnesses/agent-hub/docs-lane.js +122 -0
  213. package/.versions/2.0.10/.pi/harnesses/agent-hub/drift-watchdog.js +218 -0
  214. package/.versions/2.0.10/.pi/harnesses/agent-hub/evidence-rules.js +96 -0
  215. package/.versions/2.0.10/.pi/harnesses/agent-hub/execution-evidence.ts +80 -0
  216. package/.versions/2.0.10/.pi/harnesses/agent-hub/external-blocker.js +85 -0
  217. package/.versions/2.0.10/.pi/harnesses/agent-hub/fixtures/registration-surface.json +57 -0
  218. package/.versions/2.0.10/.pi/harnesses/agent-hub/footer.ts +30 -0
  219. package/.versions/2.0.10/.pi/harnesses/agent-hub/helpers.ts +266 -0
  220. package/.versions/2.0.10/.pi/harnesses/agent-hub/hub-state-audit.js +64 -0
  221. package/.versions/2.0.10/.pi/harnesses/agent-hub/index.ts +2132 -0
  222. package/.versions/2.0.10/.pi/harnesses/agent-hub/input/completions.ts +76 -0
  223. package/.versions/2.0.10/.pi/harnesses/agent-hub/input/shortcuts.ts +20 -0
  224. package/.versions/2.0.10/.pi/harnesses/agent-hub/lifecycle/context-pressure.ts +123 -0
  225. package/.versions/2.0.10/.pi/harnesses/agent-hub/lifecycle/monitor-session.ts +104 -0
  226. package/.versions/2.0.10/.pi/harnesses/agent-hub/lifecycle/session-orchestration.ts +143 -0
  227. package/.versions/2.0.10/.pi/harnesses/agent-hub/lifecycle/turn-handlers.ts +74 -0
  228. package/.versions/2.0.10/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
  229. package/.versions/2.0.10/.pi/harnesses/agent-hub/monitor-invoke-journal.ts +131 -0
  230. package/.versions/2.0.10/.pi/harnesses/agent-hub/monitor-invoke.ts +92 -0
  231. package/.versions/2.0.10/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
  232. package/.versions/2.0.10/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
  233. package/.versions/2.0.10/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
  234. package/.versions/2.0.10/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
  235. package/.versions/2.0.10/.pi/harnesses/agent-hub/monitor-session-bridge.ts +266 -0
  236. package/.versions/2.0.10/.pi/harnesses/agent-hub/no-progress.ts +76 -0
  237. package/.versions/2.0.10/.pi/harnesses/agent-hub/package.json +7 -0
  238. package/.versions/2.0.10/.pi/harnesses/agent-hub/peer-spawn-plan.ts +116 -0
  239. package/.versions/2.0.10/.pi/harnesses/agent-hub/policy/models.ts +153 -0
  240. package/.versions/2.0.10/.pi/harnesses/agent-hub/policy/profile-activation.ts +62 -0
  241. package/.versions/2.0.10/.pi/harnesses/agent-hub/policy/profile-runtime.ts +120 -0
  242. package/.versions/2.0.10/.pi/harnesses/agent-hub/policy/roster.ts +94 -0
  243. package/.versions/2.0.10/.pi/harnesses/agent-hub/policy/work-mode.ts +119 -0
  244. package/.versions/2.0.10/.pi/harnesses/agent-hub/poll-command.ts +176 -0
  245. package/.versions/2.0.10/.pi/harnesses/agent-hub/presentation.ts +48 -0
  246. package/.versions/2.0.10/.pi/harnesses/agent-hub/prompts/context.ts +47 -0
  247. package/.versions/2.0.10/.pi/harnesses/agent-hub/prompts/fragments.ts +115 -0
  248. package/.versions/2.0.10/.pi/harnesses/agent-hub/prompts/session-start.ts +90 -0
  249. package/.versions/2.0.10/.pi/harnesses/agent-hub/prompts/system-prompt.ts +112 -0
  250. package/.versions/2.0.10/.pi/harnesses/agent-hub/provider-semaphore.js +138 -0
  251. package/.versions/2.0.10/.pi/harnesses/agent-hub/research/controls.ts +74 -0
  252. package/.versions/2.0.10/.pi/harnesses/agent-hub/research/runtime.ts +192 -0
  253. package/.versions/2.0.10/.pi/harnesses/agent-hub/research/spawn-run.ts +156 -0
  254. package/.versions/2.0.10/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
  255. package/.versions/2.0.10/.pi/harnesses/agent-hub/return-contract.js +327 -0
  256. package/.versions/2.0.10/.pi/harnesses/agent-hub/return-extract.js +75 -0
  257. package/.versions/2.0.10/.pi/harnesses/agent-hub/review-findings.js +102 -0
  258. package/.versions/2.0.10/.pi/harnesses/agent-hub/run-budget.js +537 -0
  259. package/.versions/2.0.10/.pi/harnesses/agent-hub/run-namespace.js +87 -0
  260. package/.versions/2.0.10/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
  261. package/.versions/2.0.10/.pi/harnesses/agent-hub/scope-gate.js +123 -0
  262. package/.versions/2.0.10/.pi/harnesses/agent-hub/session-health.js +110 -0
  263. package/.versions/2.0.10/.pi/harnesses/agent-hub/session-start.ts +42 -0
  264. package/.versions/2.0.10/.pi/harnesses/agent-hub/spawn.ts +404 -0
  265. package/.versions/2.0.10/.pi/harnesses/agent-hub/timeline.ts +54 -0
  266. package/.versions/2.0.10/.pi/harnesses/agent-hub/tools/action-executors.ts +149 -0
  267. package/.versions/2.0.10/.pi/harnesses/agent-hub/tools/coms-tools.ts +139 -0
  268. package/.versions/2.0.10/.pi/harnesses/agent-hub/tools/context.ts +134 -0
  269. package/.versions/2.0.10/.pi/harnesses/agent-hub/tools/dispatch-agent.ts +82 -0
  270. package/.versions/2.0.10/.pi/harnesses/agent-hub/tools/dispatch-execution.ts +335 -0
  271. package/.versions/2.0.10/.pi/harnesses/agent-hub/tools/execution-orchestration.ts +22 -0
  272. package/.versions/2.0.10/.pi/harnesses/agent-hub/tools/fleet-tools.ts +200 -0
  273. package/.versions/2.0.10/.pi/harnesses/agent-hub/tools/herdr-executors.ts +86 -0
  274. package/.versions/2.0.10/.pi/harnesses/agent-hub/tools/set-task-tier.ts +29 -0
  275. package/.versions/2.0.10/.pi/harnesses/agent-hub/tools/spawn-research.ts +62 -0
  276. package/.versions/2.0.10/.pi/harnesses/agent-hub/tools/team-adjust.ts +29 -0
  277. package/.versions/2.0.10/.pi/harnesses/agent-hub/tools/verification-contract.ts +77 -0
  278. package/.versions/2.0.10/.pi/harnesses/agent-hub/types.ts +63 -0
  279. package/.versions/2.0.10/.pi/harnesses/agent-hub/ui/activity-dots.ts +16 -0
  280. package/.versions/2.0.10/.pi/harnesses/agent-hub/ui/context-budget.ts +86 -0
  281. package/.versions/2.0.10/.pi/harnesses/agent-hub/ui/detail-panel.ts +178 -0
  282. package/.versions/2.0.10/.pi/harnesses/agent-hub/ui/fleet-actions.ts +76 -0
  283. package/.versions/2.0.10/.pi/harnesses/agent-hub/ui/fleet-dashboard.ts +99 -0
  284. package/.versions/2.0.10/.pi/harnesses/agent-hub/ui/fleet-editor.ts +44 -0
  285. package/.versions/2.0.10/.pi/harnesses/agent-hub/ui/fleet-source.ts +157 -0
  286. package/.versions/2.0.10/.pi/harnesses/agent-hub/ui/grid.ts +154 -0
  287. package/.versions/2.0.10/.pi/harnesses/agent-hub/ui/history-store.ts +137 -0
  288. package/.versions/2.0.10/.pi/harnesses/agent-hub/ui/history.ts +234 -0
  289. package/.versions/2.0.10/.pi/harnesses/agent-hub/ui/pool.ts +103 -0
  290. package/.versions/2.0.10/.pi/harnesses/agent-hub/ui/running-strip.ts +2 -0
  291. package/.versions/2.0.10/.pi/harnesses/agent-hub/ui/zoom.ts +204 -0
  292. package/.versions/2.0.10/.pi/harnesses/agent-hub/version.ts +42 -0
  293. package/.versions/2.0.10/.pi/harnesses/agent-hub/work-mode-controls.ts +56 -0
  294. package/.versions/2.0.10/.pi/harnesses/agent-hub/work-mode.ts +167 -0
  295. package/.versions/2.0.10/.pi/harnesses/ask-user-remote/README.md +59 -0
  296. package/.versions/2.0.10/.pi/harnesses/ask-user-remote/index.ts +558 -0
  297. package/.versions/2.0.10/.pi/harnesses/ask-user-remote/questions.ts +161 -0
  298. package/.versions/2.0.10/.pi/harnesses/ask-user-remote/race-core.js +124 -0
  299. package/.versions/2.0.10/.pi/harnesses/ask-user-remote/runtime-ask.ts +43 -0
  300. package/.versions/2.0.10/.pi/harnesses/coms/README.md +100 -0
  301. package/.versions/2.0.10/.pi/harnesses/coms/index.ts +282 -0
  302. package/.versions/2.0.10/.pi/harnesses/coms/package.json +7 -0
  303. package/.versions/2.0.10/.pi/harnesses/coms/version.ts +42 -0
  304. package/.versions/2.0.10/.pi/harnesses/damage-control-continue/README.md +135 -0
  305. package/.versions/2.0.10/.pi/harnesses/damage-control-continue/index.ts +541 -0
  306. package/.versions/2.0.10/.pi/harnesses/damage-control-continue/package.json +7 -0
  307. package/.versions/2.0.10/.pi/harnesses/damage-control-continue/version.ts +42 -0
  308. package/.versions/2.0.10/.pi/harnesses/lib/changed-file-diagnostics.ts +642 -0
  309. package/.versions/2.0.10/.pi/harnesses/lib/coms-core-io.ts +385 -0
  310. package/.versions/2.0.10/.pi/harnesses/lib/coms-core.ts +577 -0
  311. package/.versions/2.0.10/.pi/harnesses/lib/coms-registry-entry.ts +94 -0
  312. package/.versions/2.0.10/.pi/harnesses/lib/context-budget-child-prompt.ts +180 -0
  313. package/.versions/2.0.10/.pi/harnesses/lib/context-budget-hub-prompt.ts +114 -0
  314. package/.versions/2.0.10/.pi/harnesses/lib/context-budget-view.ts +107 -0
  315. package/.versions/2.0.10/.pi/harnesses/lib/context-budget.ts +114 -0
  316. package/.versions/2.0.10/.pi/harnesses/lib/damage-control-shared.ts +197 -0
  317. package/.versions/2.0.10/.pi/harnesses/lib/fixtures/context-budget-profiles.json +11 -0
  318. package/.versions/2.0.10/.pi/harnesses/lib/fixtures/hub-prompt-operator.legacy.txt +73 -0
  319. package/.versions/2.0.10/.pi/harnesses/lib/fixtures/hub-prompt-orchestrator.legacy.txt +73 -0
  320. package/.versions/2.0.10/.pi/harnesses/lib/fleet-dashboard-ops.ts +178 -0
  321. package/.versions/2.0.10/.pi/harnesses/lib/fleet-dashboard-view.ts +134 -0
  322. package/.versions/2.0.10/.pi/harnesses/lib/fleet-detail-view.ts +247 -0
  323. package/.versions/2.0.10/.pi/harnesses/lib/fleet-overlay.ts +26 -0
  324. package/.versions/2.0.10/.pi/harnesses/lib/fleet-panel.ts +34 -0
  325. package/.versions/2.0.10/.pi/harnesses/lib/fleet-read-model.ts +213 -0
  326. package/.versions/2.0.10/.pi/harnesses/lib/fleet-selection.ts +24 -0
  327. package/.versions/2.0.10/.pi/harnesses/lib/fleet-strip-controller.ts +74 -0
  328. package/.versions/2.0.10/.pi/harnesses/lib/fleet-strip-view.ts +132 -0
  329. package/.versions/2.0.10/.pi/harnesses/lib/fleet-transcript-store.ts +244 -0
  330. package/.versions/2.0.10/.pi/harnesses/lib/herdr-client.ts +472 -0
  331. package/.versions/2.0.10/.pi/harnesses/lib/herdr-presence.ts +399 -0
  332. package/.versions/2.0.10/.pi/harnesses/lib/hermes-monitor-events.ts +136 -0
  333. package/.versions/2.0.10/.pi/harnesses/lib/hermes-monitor-herdr.ts +28 -0
  334. package/.versions/2.0.10/.pi/harnesses/lib/hermes-monitor-model.ts +18 -0
  335. package/.versions/2.0.10/.pi/harnesses/lib/hermes-monitor-registry.ts +6 -0
  336. package/.versions/2.0.10/.pi/harnesses/lib/hermes-monitor-socket.ts +163 -0
  337. package/.versions/2.0.10/.pi/harnesses/lib/hermes-monitor-store.ts +31 -0
  338. package/.versions/2.0.10/.pi/harnesses/lib/spawned-peers.js +190 -0
  339. package/.versions/2.0.10/.pi/harnesses/lib/update-check.ts +222 -0
  340. package/.versions/2.0.10/.pi/harnesses/package-lock.json +2039 -0
  341. package/.versions/2.0.10/.pi/harnesses/package.json +10 -0
  342. package/.versions/2.0.10/.pi/prompts/af-build.md +24 -0
  343. package/.versions/2.0.10/.pi/prompts/af-code-simplify.md +22 -0
  344. package/.versions/2.0.10/.pi/prompts/af-constraints.md +31 -0
  345. package/.versions/2.0.10/.pi/prompts/af-plan.md +17 -0
  346. package/.versions/2.0.10/.pi/prompts/af-review.md +16 -0
  347. package/.versions/2.0.10/.pi/prompts/af-set-hermes-telegram.md +15 -0
  348. package/.versions/2.0.10/.pi/prompts/af-set-hermes-watchdog.md +6 -0
  349. package/.versions/2.0.10/.pi/prompts/af-ship.md +17 -0
  350. package/.versions/2.0.10/.pi/prompts/af-spec.md +15 -0
  351. package/.versions/2.0.10/.pi/prompts/af-test.md +19 -0
  352. package/.versions/2.0.10/.pi/skills/bowser/SKILL.md +145 -0
  353. package/.versions/2.0.10/.version +1 -0
  354. package/.versions/2.0.10/agents/architect.md +25 -0
  355. package/.versions/2.0.10/agents/bowser.md +28 -0
  356. package/.versions/2.0.10/agents/builder.md +56 -0
  357. package/.versions/2.0.10/agents/code-reviewer.md +210 -0
  358. package/.versions/2.0.10/agents/deep-researcher.md +33 -0
  359. package/.versions/2.0.10/agents/documenter.md +23 -0
  360. package/.versions/2.0.10/agents/orchestrator.md +23 -0
  361. package/.versions/2.0.10/agents/plan-reviewer.md +84 -0
  362. package/.versions/2.0.10/agents/planner.md +106 -0
  363. package/.versions/2.0.10/agents/releaser.md +25 -0
  364. package/.versions/2.0.10/agents/researcher.md +31 -0
  365. package/.versions/2.0.10/agents/security-auditor.md +168 -0
  366. package/.versions/2.0.10/agents/test-engineer.md +154 -0
  367. package/.versions/2.0.10/agents/web-debugger.md +44 -0
  368. package/.versions/2.0.10/agents/web-performance-auditor.md +194 -0
  369. package/.versions/2.0.10/bin/catalog/harness-runtime-closure.json +32 -0
  370. package/.versions/2.0.10/codex/fleet-session-client/SKILL.md +34 -0
  371. package/.versions/2.0.10/codex/fleet-session-client.zip +0 -0
  372. package/.versions/2.0.10/docs/ARCHITECTURE.md +416 -0
  373. package/.versions/2.0.10/docs/agent-fleet-setup.md +586 -0
  374. package/.versions/2.0.10/docs/claude-code-coms-bridge.md +134 -0
  375. package/.versions/2.0.10/docs/codex-session-bridge.md +219 -0
  376. package/.versions/2.0.10/docs/coms-hermes-bridge.md +188 -0
  377. package/.versions/2.0.10/docs/getting-started.md +126 -0
  378. package/.versions/2.0.10/docs/npm-install.md +383 -0
  379. package/.versions/2.0.10/docs/pi-extensions.md +449 -0
  380. package/.versions/2.0.10/docs/pi-setup.md +92 -0
  381. package/.versions/2.0.10/docs/skill-anatomy.md +150 -0
  382. package/.versions/2.0.10/install-manifest.json +2991 -0
  383. package/.versions/2.0.10/justfile +247 -0
  384. package/.versions/2.0.10/manifest-meta.json +970 -0
  385. package/.versions/2.0.10/references/accessibility-checklist.md +160 -0
  386. package/.versions/2.0.10/references/communication-contract.md +26 -0
  387. package/.versions/2.0.10/references/definition-of-done.md +67 -0
  388. package/.versions/2.0.10/references/fleet-coordination-patterns.md +171 -0
  389. package/.versions/2.0.10/references/observability-checklist.md +92 -0
  390. package/.versions/2.0.10/references/orchestration-patterns.md +370 -0
  391. package/.versions/2.0.10/references/performance-checklist.md +236 -0
  392. package/.versions/2.0.10/references/prompting-patterns.md +380 -0
  393. package/.versions/2.0.10/references/security-checklist.md +245 -0
  394. package/.versions/2.0.10/references/testing-patterns.md +235 -0
  395. package/.versions/2.0.10/references/workflow-authoring.md +304 -0
  396. package/.versions/2.0.10/skills/_internal/grilling.md +59 -0
  397. package/.versions/2.0.10/skills/browser-testing-with-devtools/SKILL.md +351 -0
  398. package/.versions/2.0.10/skills/code-review-and-quality/SKILL.md +396 -0
  399. package/.versions/2.0.10/skills/compound-learning/SKILL.md +137 -0
  400. package/.versions/2.0.10/skills/constraint-driven-development/SKILL.md +338 -0
  401. package/.versions/2.0.10/skills/constraint-driven-development/references/floor-guard.md +99 -0
  402. package/.versions/2.0.10/skills/context-engineering/SKILL.md +341 -0
  403. package/.versions/2.0.10/skills/deprecation-and-migration/SKILL.md +247 -0
  404. package/.versions/2.0.10/skills/designing-agents/SKILL.md +394 -0
  405. package/.versions/2.0.10/skills/designing-agents/pi-harness-authoring.md +222 -0
  406. package/.versions/2.0.10/skills/drafting-workflows/SKILL.md +143 -0
  407. package/.versions/2.0.10/skills/drafting-workflows/scripts/make-workflow.ts +177 -0
  408. package/.versions/2.0.10/skills/frontend-ui-engineering/SKILL.md +328 -0
  409. package/.versions/2.0.10/skills/git-workflow-and-versioning/SKILL.md +316 -0
  410. package/.versions/2.0.10/skills/idea-refine/SKILL.md +182 -0
  411. package/.versions/2.0.10/skills/idea-refine/examples.md +238 -0
  412. package/.versions/2.0.10/skills/idea-refine/frameworks.md +99 -0
  413. package/.versions/2.0.10/skills/idea-refine/refinement-criteria.md +113 -0
  414. package/.versions/2.0.10/skills/idea-refine/scripts/idea-refine.sh +15 -0
  415. package/.versions/2.0.10/skills/incremental-implementation/SKILL.md +302 -0
  416. package/.versions/2.0.10/skills/interview-me/SKILL.md +226 -0
  417. package/.versions/2.0.10/skills/orchestration-verification/SKILL.md +182 -0
  418. package/.versions/2.0.10/skills/peer-coms/SKILL.md +90 -0
  419. package/.versions/2.0.10/skills/performance-optimization/SKILL.md +496 -0
  420. package/.versions/2.0.10/skills/planning-and-task-breakdown/SKILL.md +289 -0
  421. package/.versions/2.0.10/skills/security-and-hardening/SKILL.md +524 -0
  422. package/.versions/2.0.10/skills/spec-driven-development/SKILL.md +295 -0
  423. package/.versions/2.0.10/skills/using-agent-skills/SKILL.md +198 -0
  424. package/.versions/2.0.10/vendor/agent-skills-upstream/LICENSE +21 -0
  425. package/.versions/2.0.10/vendor/agent-skills-upstream/README.md +430 -0
  426. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/api-and-interface-design/SKILL.md +367 -0
  427. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/browser-testing-with-devtools/SKILL.md +317 -0
  428. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/ci-cd-and-automation/SKILL.md +390 -0
  429. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/code-review-and-quality/SKILL.md +396 -0
  430. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/code-simplification/SKILL.md +331 -0
  431. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/constraint-driven-development/SKILL.md +311 -0
  432. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/constraint-driven-development/references/floor-guard.md +99 -0
  433. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/context-engineering/SKILL.md +337 -0
  434. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/debugging-and-error-recovery/SKILL.md +300 -0
  435. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/deprecation-and-migration/SKILL.md +247 -0
  436. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/documentation-and-adrs/SKILL.md +288 -0
  437. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/doubt-driven-development/SKILL.md +243 -0
  438. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/frontend-ui-engineering/SKILL.md +328 -0
  439. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/git-workflow-and-versioning/SKILL.md +355 -0
  440. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/idea-refine/SKILL.md +178 -0
  441. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/idea-refine/examples.md +238 -0
  442. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/idea-refine/frameworks.md +99 -0
  443. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/idea-refine/refinement-criteria.md +113 -0
  444. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/idea-refine/scripts/idea-refine.sh +15 -0
  445. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/incremental-implementation/SKILL.md +249 -0
  446. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/interview-me/SKILL.md +225 -0
  447. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/observability-and-instrumentation/SKILL.md +238 -0
  448. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/performance-optimization/SKILL.md +496 -0
  449. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/planning-and-task-breakdown/SKILL.md +257 -0
  450. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/security-and-hardening/SKILL.md +524 -0
  451. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/shipping-and-launch/SKILL.md +330 -0
  452. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/source-driven-development/SKILL.md +216 -0
  453. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/spec-driven-development/SKILL.md +245 -0
  454. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/test-driven-development/SKILL.md +398 -0
  455. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/using-agent-skills/SKILL.md +192 -0
  456. package/.versions/2.0.9/.pi/agent-fleet/hermes/README.md +347 -0
  457. package/.versions/2.0.9/.pi/agent-fleet/hermes/desktop-plugins/agent-fleet-herdr/plugin.js +1291 -0
  458. package/.versions/2.0.9/.pi/agent-fleet/hermes/desktop-plugins/agent-fleet-herdr/presentation.js +672 -0
  459. package/.versions/2.0.9/.pi/agent-fleet/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
  460. package/.versions/2.0.9/.pi/agent-fleet/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
  461. package/.versions/2.0.9/.pi/agent-fleet/hermes/gates/gate-o-capability.md +8 -0
  462. package/.versions/2.0.9/.pi/agent-fleet/hermes/gates/gate-o-validator-fixtures.json +1 -0
  463. package/.versions/2.0.9/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/activity.py +773 -0
  464. package/.versions/2.0.9/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/coms_registry.py +134 -0
  465. package/.versions/2.0.9/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/coms_send.py +350 -0
  466. package/.versions/2.0.9/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/herdr_source.py +193 -0
  467. package/.versions/2.0.9/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/manifest.json +4 -0
  468. package/.versions/2.0.9/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/plugin_api.py +444 -0
  469. package/.versions/2.0.9/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/sessions.py +205 -0
  470. package/.versions/2.0.9/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/tasks.py +300 -0
  471. package/.versions/2.0.9/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/watch.py +819 -0
  472. package/.versions/2.0.9/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/plugin.yaml +8 -0
  473. package/.versions/2.0.9/.pi/agent-fleet/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +139 -0
  474. package/.versions/2.0.9/.pi/agent-fleet/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
  475. package/.versions/2.0.9/.pi/agent-fleet/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
  476. package/.versions/2.0.9/.pi/agent-fleet/hermes/skills/hub-conductor/SKILL.md +84 -0
  477. package/.versions/2.0.9/.pi/agent-fleet/hermes/skills/hub-liaison/SKILL.md +84 -0
  478. package/.versions/2.0.9/.pi/agent-fleet/hermes/skills/hub-watchdog/SKILL.md +76 -0
  479. package/.versions/2.0.9/.pi/agent-fleet/hermes/skills/hub-watchdog/manifest.json +1 -0
  480. package/.versions/2.0.9/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog.py +249 -0
  481. package/.versions/2.0.9/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_actions.py +124 -0
  482. package/.versions/2.0.9/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_contract.py +76 -0
  483. package/.versions/2.0.9/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_delivery.py +10 -0
  484. package/.versions/2.0.9/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_engine.py +128 -0
  485. package/.versions/2.0.9/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_judgment.py +41 -0
  486. package/.versions/2.0.9/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_recovery.py +103 -0
  487. package/.versions/2.0.9/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_state.py +163 -0
  488. package/.versions/2.0.9/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_transport.py +138 -0
  489. package/.versions/2.0.9/.pi/agent-fleet/hermes/watchdog-tests/__init__.py +0 -0
  490. package/.versions/2.0.9/.pi/agent-fleet/hooks/coms-stop-hook.mjs +84 -0
  491. package/.versions/2.0.9/.pi/agent-fleet/scripts/claude-code-preflight.ts +70 -0
  492. package/.versions/2.0.9/.pi/agent-fleet/scripts/coms-claude-bridge.ts +411 -0
  493. package/.versions/2.0.9/.pi/agent-fleet/scripts/coms-cli.ts +425 -0
  494. package/.versions/2.0.9/.pi/agent-fleet/scripts/coms-hermes-bridge.ts +413 -0
  495. package/.versions/2.0.9/.pi/agent-fleet/scripts/fleet-codex-client.ts +69 -0
  496. package/.versions/2.0.9/.pi/agent-fleet/scripts/fleet-codex-read.py +148 -0
  497. package/.versions/2.0.9/.pi/agent-fleet/scripts/fleet.ts +216 -0
  498. package/.versions/2.0.9/.pi/agent-fleet/scripts/flow.ts +137 -0
  499. package/.versions/2.0.9/.pi/agent-fleet/scripts/hermes-monitor-capability-runner.ts +25 -0
  500. package/.versions/2.0.9/.pi/agent-fleet/scripts/hermes-monitor-scenario.ts +474 -0
  501. package/.versions/2.0.9/.pi/agent-fleet/scripts/hermes-watchdog-capability-probe.ts +45 -0
  502. package/.versions/2.0.9/.pi/agent-fleet/scripts/install-hermes-plugin.sh +180 -0
  503. package/.versions/2.0.9/.pi/agent-fleet/scripts/lib/claude-bridge-core.ts +210 -0
  504. package/.versions/2.0.9/.pi/agent-fleet/scripts/lib/coms-envelope.ts +582 -0
  505. package/.versions/2.0.9/.pi/agent-fleet/scripts/lib/fake-herdr-server.ts +88 -0
  506. package/.versions/2.0.9/.pi/agent-fleet/scripts/lib/fleet-codex-catalog.ts +63 -0
  507. package/.versions/2.0.9/.pi/agent-fleet/scripts/lib/fleet-codex-operations.ts +190 -0
  508. package/.versions/2.0.9/.pi/agent-fleet/scripts/lib/fleet-codex-session.ts +166 -0
  509. package/.versions/2.0.9/.pi/agent-fleet/scripts/lib/fleet-codex-transport.ts +124 -0
  510. package/.versions/2.0.9/.pi/agent-fleet/scripts/lib/fleet-command.ts +252 -0
  511. package/.versions/2.0.9/.pi/agent-fleet/scripts/lib/flow-command.ts +93 -0
  512. package/.versions/2.0.9/.pi/agent-fleet/scripts/lib/flow-maintenance.ts +230 -0
  513. package/.versions/2.0.9/.pi/agent-fleet/scripts/lib/herdr-layout.ts +281 -0
  514. package/.versions/2.0.9/.pi/agent-fleet/scripts/lib/hermes-bridge-core.ts +241 -0
  515. package/.versions/2.0.9/.pi/agent-fleet/scripts/lib/hermes-monitor-events.ts +1 -0
  516. package/.versions/2.0.9/.pi/agent-fleet/scripts/lib/hermes-monitor-herdr.ts +2 -0
  517. package/.versions/2.0.9/.pi/agent-fleet/scripts/lib/hermes-monitor-model.ts +3 -0
  518. package/.versions/2.0.9/.pi/agent-fleet/scripts/lib/hermes-monitor-registry.ts +2 -0
  519. package/.versions/2.0.9/.pi/agent-fleet/scripts/lib/hermes-monitor-socket.ts +2 -0
  520. package/.versions/2.0.9/.pi/agent-fleet/scripts/lib/hermes-monitor-store.ts +2 -0
  521. package/.versions/2.0.9/.pi/agent-fleet/scripts/lib/monitor-env.ts +146 -0
  522. package/.versions/2.0.9/.pi/agent-fleet/scripts/lib/peer-launch.ts +318 -0
  523. package/.versions/2.0.9/.pi/agent-fleet/scripts/lib/persona-banner.ts +62 -0
  524. package/.versions/2.0.9/.pi/agent-fleet/scripts/lib/persona-dirs.ts +25 -0
  525. package/.versions/2.0.9/.pi/agent-fleet/scripts/lib/runtime-dependencies.js +124 -0
  526. package/.versions/2.0.9/.pi/agent-fleet/scripts/lib/spawn-stagger.ts +101 -0
  527. package/.versions/2.0.9/.pi/agent-fleet/scripts/lib/team-project.ts +178 -0
  528. package/.versions/2.0.9/.pi/agent-fleet/scripts/lib/team-snapshot.ts +147 -0
  529. package/.versions/2.0.9/.pi/agent-fleet/scripts/package-lock.json +35 -0
  530. package/.versions/2.0.9/.pi/agent-fleet/scripts/package.json +9 -0
  531. package/.versions/2.0.9/.pi/agent-fleet/scripts/peer-banner.ts +41 -0
  532. package/.versions/2.0.9/.pi/agent-fleet/scripts/peer-launch.ts +283 -0
  533. package/.versions/2.0.9/.pi/agent-fleet/scripts/team-snapshot.ts +237 -0
  534. package/.versions/2.0.9/.pi/agent-fleet/scripts/team-up.ts +378 -0
  535. package/.versions/2.0.9/.pi/agent-fleet/scripts/workflows/lib/agent-phase.ts +133 -0
  536. package/.versions/2.0.9/.pi/agent-fleet/scripts/workflows/lib/changes.ts +61 -0
  537. package/.versions/2.0.9/.pi/agent-fleet/scripts/workflows/lib/debate.ts +149 -0
  538. package/.versions/2.0.9/.pi/agent-fleet/scripts/workflows/lib/env.ts +34 -0
  539. package/.versions/2.0.9/.pi/agent-fleet/scripts/workflows/lib/envelopes.ts +169 -0
  540. package/.versions/2.0.9/.pi/agent-fleet/scripts/workflows/lib/gates.ts +81 -0
  541. package/.versions/2.0.9/.pi/agent-fleet/scripts/workflows/lib/git.ts +96 -0
  542. package/.versions/2.0.9/.pi/agent-fleet/scripts/workflows/lib/merge.ts +95 -0
  543. package/.versions/2.0.9/.pi/agent-fleet/scripts/workflows/lib/model-profile.ts +22 -0
  544. package/.versions/2.0.9/.pi/agent-fleet/scripts/workflows/lib/model-visibility.ts +92 -0
  545. package/.versions/2.0.9/.pi/agent-fleet/scripts/workflows/lib/permissions.ts +130 -0
  546. package/.versions/2.0.9/.pi/agent-fleet/scripts/workflows/lib/personas.ts +57 -0
  547. package/.versions/2.0.9/.pi/agent-fleet/scripts/workflows/lib/poll.ts +86 -0
  548. package/.versions/2.0.9/.pi/agent-fleet/scripts/workflows/lib/quality.ts +64 -0
  549. package/.versions/2.0.9/.pi/agent-fleet/scripts/workflows/lib/run.ts +108 -0
  550. package/.versions/2.0.9/.pi/agent-fleet/scripts/workflows/lib/trace.ts +34 -0
  551. package/.versions/2.0.9/.pi/agent-fleet/scripts/workflows/lib/voices.ts +128 -0
  552. package/.versions/2.0.9/.pi/agent-fleet/scripts/workflows/lib/writer-lease.ts +112 -0
  553. package/.versions/2.0.9/.pi/agent-fleet/scripts/workflows/tsconfig.json +22 -0
  554. package/.versions/2.0.9/.pi/agent-fleet/scripts/workflows/wf-build-test.ts +61 -0
  555. package/.versions/2.0.9/.pi/agent-fleet/scripts/workflows/wf-debate.ts +87 -0
  556. package/.versions/2.0.9/.pi/agent-fleet/scripts/workflows/wf-document.ts +50 -0
  557. package/.versions/2.0.9/.pi/agent-fleet/scripts/workflows/wf-poll.ts +95 -0
  558. package/.versions/2.0.9/.pi/agent-fleet/scripts/workflows/wf-quality.ts +20 -0
  559. package/.versions/2.0.9/.pi/agent-fleet/scripts/workflows/wf-scout.ts +38 -0
  560. package/.versions/2.0.9/.pi/agents/dispatch-policy.yaml +32 -0
  561. package/.versions/2.0.9/.pi/agents/model-profiles.yaml +83 -0
  562. package/.versions/2.0.9/.pi/agents/peers.yaml +147 -0
  563. package/.versions/2.0.9/.pi/agents/teams.yaml +41 -0
  564. package/.versions/2.0.9/.pi/agents/voices.yaml +13 -0
  565. package/.versions/2.0.9/.pi/damage-control-rules.yaml +297 -0
  566. package/.versions/2.0.9/.pi/extensions/btw/README.md +120 -0
  567. package/.versions/2.0.9/.pi/extensions/btw/index.ts +914 -0
  568. package/.versions/2.0.9/.pi/extensions/btw/package.json +6 -0
  569. package/.versions/2.0.9/.pi/extensions/btw/state.js +179 -0
  570. package/.versions/2.0.9/.pi/extensions/chrome-devtools-mcp/README.md +55 -0
  571. package/.versions/2.0.9/.pi/extensions/chrome-devtools-mcp/index.ts +93 -0
  572. package/.versions/2.0.9/.pi/extensions/chrome-devtools-mcp/package.json +6 -0
  573. package/.versions/2.0.9/.pi/extensions/compact-and-continue/README.md +42 -0
  574. package/.versions/2.0.9/.pi/extensions/compact-and-continue/index.ts +120 -0
  575. package/.versions/2.0.9/.pi/extensions/compact-and-continue/package.json +6 -0
  576. package/.versions/2.0.9/.pi/extensions/mcp-bridge/README.md +46 -0
  577. package/.versions/2.0.9/.pi/extensions/mcp-bridge/index.ts +206 -0
  578. package/.versions/2.0.9/.pi/extensions/mcp-bridge/package.json +6 -0
  579. package/.versions/2.0.9/.pi/extensions/package-lock.json +1175 -0
  580. package/.versions/2.0.9/.pi/extensions/package.json +9 -0
  581. package/.versions/2.0.9/.pi/extensions/pi-voice-stt/README.md +205 -0
  582. package/.versions/2.0.9/.pi/extensions/pi-voice-stt/config.ts +198 -0
  583. package/.versions/2.0.9/.pi/extensions/pi-voice-stt/examples/stt.json +35 -0
  584. package/.versions/2.0.9/.pi/extensions/pi-voice-stt/index.ts +248 -0
  585. package/.versions/2.0.9/.pi/extensions/pi-voice-stt/package.json +6 -0
  586. package/.versions/2.0.9/.pi/extensions/pi-voice-stt/providers.ts +214 -0
  587. package/.versions/2.0.9/.pi/extensions/pi-voice-stt/recorder.ts +158 -0
  588. package/.versions/2.0.9/.pi/harnesses/agent-hub/README.md +1217 -0
  589. package/.versions/2.0.9/.pi/harnesses/agent-hub/acceptance.ts +62 -0
  590. package/.versions/2.0.9/.pi/harnesses/agent-hub/access-approval.ts +135 -0
  591. package/.versions/2.0.9/.pi/harnesses/agent-hub/artifacts.js +146 -0
  592. package/.versions/2.0.9/.pi/harnesses/agent-hub/assertion-ledger.js +58 -0
  593. package/.versions/2.0.9/.pi/harnesses/agent-hub/backend-policy.js +174 -0
  594. package/.versions/2.0.9/.pi/harnesses/agent-hub/budget-continuation.ts +13 -0
  595. package/.versions/2.0.9/.pi/harnesses/agent-hub/budget-recovery.ts +97 -0
  596. package/.versions/2.0.9/.pi/harnesses/agent-hub/capability-confirmation.ts +47 -0
  597. package/.versions/2.0.9/.pi/harnesses/agent-hub/capability-packs.ts +180 -0
  598. package/.versions/2.0.9/.pi/harnesses/agent-hub/commands/agent-model-thinking.ts +10 -0
  599. package/.versions/2.0.9/.pi/harnesses/agent-hub/commands/agent-model.ts +10 -0
  600. package/.versions/2.0.9/.pi/harnesses/agent-hub/commands/agent-models-substitute.ts +10 -0
  601. package/.versions/2.0.9/.pi/harnesses/agent-hub/commands/agents-add.ts +9 -0
  602. package/.versions/2.0.9/.pi/harnesses/agent-hub/commands/agents-drop.ts +9 -0
  603. package/.versions/2.0.9/.pi/harnesses/agent-hub/commands/agents-history.ts +9 -0
  604. package/.versions/2.0.9/.pi/harnesses/agent-hub/commands/agents-kill.ts +10 -0
  605. package/.versions/2.0.9/.pi/harnesses/agent-hub/commands/agents-list.ts +9 -0
  606. package/.versions/2.0.9/.pi/harnesses/agent-hub/commands/agents-restart.ts +10 -0
  607. package/.versions/2.0.9/.pi/harnesses/agent-hub/commands/agents-save.ts +9 -0
  608. package/.versions/2.0.9/.pi/harnesses/agent-hub/commands/agents-team.ts +9 -0
  609. package/.versions/2.0.9/.pi/harnesses/agent-hub/commands/budget-continue.ts +10 -0
  610. package/.versions/2.0.9/.pi/harnesses/agent-hub/commands/compound.ts +9 -0
  611. package/.versions/2.0.9/.pi/harnesses/agent-hub/commands/coms.ts +9 -0
  612. package/.versions/2.0.9/.pi/harnesses/agent-hub/commands/context-command.ts +9 -0
  613. package/.versions/2.0.9/.pi/harnesses/agent-hub/commands/context.ts +43 -0
  614. package/.versions/2.0.9/.pi/harnesses/agent-hub/commands/debate.ts +9 -0
  615. package/.versions/2.0.9/.pi/harnesses/agent-hub/commands/dispatch-policy.ts +9 -0
  616. package/.versions/2.0.9/.pi/harnesses/agent-hub/commands/handoff.ts +10 -0
  617. package/.versions/2.0.9/.pi/harnesses/agent-hub/commands/hub-report.ts +9 -0
  618. package/.versions/2.0.9/.pi/harnesses/agent-hub/commands/models.ts +10 -0
  619. package/.versions/2.0.9/.pi/harnesses/agent-hub/commands/poll.ts +9 -0
  620. package/.versions/2.0.9/.pi/harnesses/agent-hub/commands/retry.ts +10 -0
  621. package/.versions/2.0.9/.pi/harnesses/agent-hub/commands/watchdog.ts +9 -0
  622. package/.versions/2.0.9/.pi/harnesses/agent-hub/commands/work-mode.ts +29 -0
  623. package/.versions/2.0.9/.pi/harnesses/agent-hub/commands/zoom.ts +10 -0
  624. package/.versions/2.0.9/.pi/harnesses/agent-hub/config/agents.ts +177 -0
  625. package/.versions/2.0.9/.pi/harnesses/agent-hub/config/model-profiles.ts +216 -0
  626. package/.versions/2.0.9/.pi/harnesses/agent-hub/config/overrides.ts +153 -0
  627. package/.versions/2.0.9/.pi/harnesses/agent-hub/context/agent-state.ts +30 -0
  628. package/.versions/2.0.9/.pi/harnesses/agent-hub/context/assertions-artifacts.ts +213 -0
  629. package/.versions/2.0.9/.pi/harnesses/agent-hub/context/budgets.ts +202 -0
  630. package/.versions/2.0.9/.pi/harnesses/agent-hub/context/hub-state.ts +40 -0
  631. package/.versions/2.0.9/.pi/harnesses/agent-hub/context-budget-snapshot.ts +105 -0
  632. package/.versions/2.0.9/.pi/harnesses/agent-hub/context-pressure.ts +191 -0
  633. package/.versions/2.0.9/.pi/harnesses/agent-hub/context-window.js +106 -0
  634. package/.versions/2.0.9/.pi/harnesses/agent-hub/debate-command.ts +176 -0
  635. package/.versions/2.0.9/.pi/harnesses/agent-hub/delegate.ts +446 -0
  636. package/.versions/2.0.9/.pi/harnesses/agent-hub/dispatch-coms.ts +237 -0
  637. package/.versions/2.0.9/.pi/harnesses/agent-hub/dispatch-core.ts +27 -0
  638. package/.versions/2.0.9/.pi/harnesses/agent-hub/dispatch-native-complete.ts +154 -0
  639. package/.versions/2.0.9/.pi/harnesses/agent-hub/dispatch-native-prepare.ts +156 -0
  640. package/.versions/2.0.9/.pi/harnesses/agent-hub/dispatch-native-spawn.ts +193 -0
  641. package/.versions/2.0.9/.pi/harnesses/agent-hub/dispatch-native-types.ts +230 -0
  642. package/.versions/2.0.9/.pi/harnesses/agent-hub/dispatch-native.ts +213 -0
  643. package/.versions/2.0.9/.pi/harnesses/agent-hub/dispatch-observability.ts +225 -0
  644. package/.versions/2.0.9/.pi/harnesses/agent-hub/docs-lane.js +122 -0
  645. package/.versions/2.0.9/.pi/harnesses/agent-hub/drift-watchdog.js +218 -0
  646. package/.versions/2.0.9/.pi/harnesses/agent-hub/evidence-rules.js +96 -0
  647. package/.versions/2.0.9/.pi/harnesses/agent-hub/execution-evidence.ts +80 -0
  648. package/.versions/2.0.9/.pi/harnesses/agent-hub/external-blocker.js +85 -0
  649. package/.versions/2.0.9/.pi/harnesses/agent-hub/fixtures/registration-surface.json +57 -0
  650. package/.versions/2.0.9/.pi/harnesses/agent-hub/footer.ts +30 -0
  651. package/.versions/2.0.9/.pi/harnesses/agent-hub/helpers.ts +266 -0
  652. package/.versions/2.0.9/.pi/harnesses/agent-hub/hub-state-audit.js +64 -0
  653. package/.versions/2.0.9/.pi/harnesses/agent-hub/index.ts +2132 -0
  654. package/.versions/2.0.9/.pi/harnesses/agent-hub/input/completions.ts +76 -0
  655. package/.versions/2.0.9/.pi/harnesses/agent-hub/input/shortcuts.ts +20 -0
  656. package/.versions/2.0.9/.pi/harnesses/agent-hub/lifecycle/context-pressure.ts +123 -0
  657. package/.versions/2.0.9/.pi/harnesses/agent-hub/lifecycle/monitor-session.ts +104 -0
  658. package/.versions/2.0.9/.pi/harnesses/agent-hub/lifecycle/session-orchestration.ts +143 -0
  659. package/.versions/2.0.9/.pi/harnesses/agent-hub/lifecycle/turn-handlers.ts +74 -0
  660. package/.versions/2.0.9/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
  661. package/.versions/2.0.9/.pi/harnesses/agent-hub/monitor-invoke-journal.ts +131 -0
  662. package/.versions/2.0.9/.pi/harnesses/agent-hub/monitor-invoke.ts +92 -0
  663. package/.versions/2.0.9/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
  664. package/.versions/2.0.9/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
  665. package/.versions/2.0.9/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
  666. package/.versions/2.0.9/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
  667. package/.versions/2.0.9/.pi/harnesses/agent-hub/monitor-session-bridge.ts +266 -0
  668. package/.versions/2.0.9/.pi/harnesses/agent-hub/no-progress.ts +76 -0
  669. package/.versions/2.0.9/.pi/harnesses/agent-hub/package.json +7 -0
  670. package/.versions/2.0.9/.pi/harnesses/agent-hub/peer-spawn-plan.ts +116 -0
  671. package/.versions/2.0.9/.pi/harnesses/agent-hub/policy/models.ts +153 -0
  672. package/.versions/2.0.9/.pi/harnesses/agent-hub/policy/profile-activation.ts +62 -0
  673. package/.versions/2.0.9/.pi/harnesses/agent-hub/policy/profile-runtime.ts +120 -0
  674. package/.versions/2.0.9/.pi/harnesses/agent-hub/policy/roster.ts +94 -0
  675. package/.versions/2.0.9/.pi/harnesses/agent-hub/policy/work-mode.ts +119 -0
  676. package/.versions/2.0.9/.pi/harnesses/agent-hub/poll-command.ts +176 -0
  677. package/.versions/2.0.9/.pi/harnesses/agent-hub/presentation.ts +48 -0
  678. package/.versions/2.0.9/.pi/harnesses/agent-hub/prompts/context.ts +47 -0
  679. package/.versions/2.0.9/.pi/harnesses/agent-hub/prompts/fragments.ts +115 -0
  680. package/.versions/2.0.9/.pi/harnesses/agent-hub/prompts/session-start.ts +90 -0
  681. package/.versions/2.0.9/.pi/harnesses/agent-hub/prompts/system-prompt.ts +112 -0
  682. package/.versions/2.0.9/.pi/harnesses/agent-hub/provider-semaphore.js +138 -0
  683. package/.versions/2.0.9/.pi/harnesses/agent-hub/research/controls.ts +74 -0
  684. package/.versions/2.0.9/.pi/harnesses/agent-hub/research/runtime.ts +192 -0
  685. package/.versions/2.0.9/.pi/harnesses/agent-hub/research/spawn-run.ts +156 -0
  686. package/.versions/2.0.9/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
  687. package/.versions/2.0.9/.pi/harnesses/agent-hub/return-contract.js +293 -0
  688. package/.versions/2.0.9/.pi/harnesses/agent-hub/return-extract.js +75 -0
  689. package/.versions/2.0.9/.pi/harnesses/agent-hub/review-findings.js +102 -0
  690. package/.versions/2.0.9/.pi/harnesses/agent-hub/run-budget.js +537 -0
  691. package/.versions/2.0.9/.pi/harnesses/agent-hub/run-namespace.js +87 -0
  692. package/.versions/2.0.9/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
  693. package/.versions/2.0.9/.pi/harnesses/agent-hub/scope-gate.js +123 -0
  694. package/.versions/2.0.9/.pi/harnesses/agent-hub/session-health.js +110 -0
  695. package/.versions/2.0.9/.pi/harnesses/agent-hub/session-start.ts +42 -0
  696. package/.versions/2.0.9/.pi/harnesses/agent-hub/spawn.ts +404 -0
  697. package/.versions/2.0.9/.pi/harnesses/agent-hub/timeline.ts +54 -0
  698. package/.versions/2.0.9/.pi/harnesses/agent-hub/tools/action-executors.ts +149 -0
  699. package/.versions/2.0.9/.pi/harnesses/agent-hub/tools/coms-tools.ts +139 -0
  700. package/.versions/2.0.9/.pi/harnesses/agent-hub/tools/context.ts +134 -0
  701. package/.versions/2.0.9/.pi/harnesses/agent-hub/tools/dispatch-agent.ts +82 -0
  702. package/.versions/2.0.9/.pi/harnesses/agent-hub/tools/dispatch-execution.ts +273 -0
  703. package/.versions/2.0.9/.pi/harnesses/agent-hub/tools/execution-orchestration.ts +22 -0
  704. package/.versions/2.0.9/.pi/harnesses/agent-hub/tools/fleet-tools.ts +200 -0
  705. package/.versions/2.0.9/.pi/harnesses/agent-hub/tools/herdr-executors.ts +86 -0
  706. package/.versions/2.0.9/.pi/harnesses/agent-hub/tools/set-task-tier.ts +29 -0
  707. package/.versions/2.0.9/.pi/harnesses/agent-hub/tools/spawn-research.ts +62 -0
  708. package/.versions/2.0.9/.pi/harnesses/agent-hub/tools/team-adjust.ts +29 -0
  709. package/.versions/2.0.9/.pi/harnesses/agent-hub/tools/verification-contract.ts +77 -0
  710. package/.versions/2.0.9/.pi/harnesses/agent-hub/types.ts +63 -0
  711. package/.versions/2.0.9/.pi/harnesses/agent-hub/ui/activity-dots.ts +16 -0
  712. package/.versions/2.0.9/.pi/harnesses/agent-hub/ui/context-budget.ts +86 -0
  713. package/.versions/2.0.9/.pi/harnesses/agent-hub/ui/detail-panel.ts +178 -0
  714. package/.versions/2.0.9/.pi/harnesses/agent-hub/ui/fleet-actions.ts +76 -0
  715. package/.versions/2.0.9/.pi/harnesses/agent-hub/ui/fleet-dashboard.ts +99 -0
  716. package/.versions/2.0.9/.pi/harnesses/agent-hub/ui/fleet-editor.ts +44 -0
  717. package/.versions/2.0.9/.pi/harnesses/agent-hub/ui/fleet-source.ts +157 -0
  718. package/.versions/2.0.9/.pi/harnesses/agent-hub/ui/grid.ts +154 -0
  719. package/.versions/2.0.9/.pi/harnesses/agent-hub/ui/history-store.ts +137 -0
  720. package/.versions/2.0.9/.pi/harnesses/agent-hub/ui/history.ts +234 -0
  721. package/.versions/2.0.9/.pi/harnesses/agent-hub/ui/pool.ts +103 -0
  722. package/.versions/2.0.9/.pi/harnesses/agent-hub/ui/running-strip.ts +2 -0
  723. package/.versions/2.0.9/.pi/harnesses/agent-hub/ui/zoom.ts +204 -0
  724. package/.versions/2.0.9/.pi/harnesses/agent-hub/version.ts +42 -0
  725. package/.versions/2.0.9/.pi/harnesses/agent-hub/work-mode-controls.ts +56 -0
  726. package/.versions/2.0.9/.pi/harnesses/agent-hub/work-mode.ts +167 -0
  727. package/.versions/2.0.9/.pi/harnesses/ask-user-remote/README.md +59 -0
  728. package/.versions/2.0.9/.pi/harnesses/ask-user-remote/index.ts +558 -0
  729. package/.versions/2.0.9/.pi/harnesses/ask-user-remote/questions.ts +161 -0
  730. package/.versions/2.0.9/.pi/harnesses/ask-user-remote/race-core.js +124 -0
  731. package/.versions/2.0.9/.pi/harnesses/ask-user-remote/runtime-ask.ts +43 -0
  732. package/.versions/2.0.9/.pi/harnesses/coms/README.md +100 -0
  733. package/.versions/2.0.9/.pi/harnesses/coms/index.ts +282 -0
  734. package/.versions/2.0.9/.pi/harnesses/coms/package.json +7 -0
  735. package/.versions/2.0.9/.pi/harnesses/coms/version.ts +42 -0
  736. package/.versions/2.0.9/.pi/harnesses/damage-control-continue/README.md +135 -0
  737. package/.versions/2.0.9/.pi/harnesses/damage-control-continue/index.ts +541 -0
  738. package/.versions/2.0.9/.pi/harnesses/damage-control-continue/package.json +7 -0
  739. package/.versions/2.0.9/.pi/harnesses/damage-control-continue/version.ts +42 -0
  740. package/.versions/2.0.9/.pi/harnesses/lib/coms-core-io.ts +385 -0
  741. package/.versions/2.0.9/.pi/harnesses/lib/coms-core.ts +577 -0
  742. package/.versions/2.0.9/.pi/harnesses/lib/coms-registry-entry.ts +94 -0
  743. package/.versions/2.0.9/.pi/harnesses/lib/context-budget-child-prompt.ts +180 -0
  744. package/.versions/2.0.9/.pi/harnesses/lib/context-budget-hub-prompt.ts +114 -0
  745. package/.versions/2.0.9/.pi/harnesses/lib/context-budget-view.ts +107 -0
  746. package/.versions/2.0.9/.pi/harnesses/lib/context-budget.ts +114 -0
  747. package/.versions/2.0.9/.pi/harnesses/lib/damage-control-shared.ts +197 -0
  748. package/.versions/2.0.9/.pi/harnesses/lib/fixtures/context-budget-profiles.json +11 -0
  749. package/.versions/2.0.9/.pi/harnesses/lib/fixtures/hub-prompt-operator.legacy.txt +73 -0
  750. package/.versions/2.0.9/.pi/harnesses/lib/fixtures/hub-prompt-orchestrator.legacy.txt +73 -0
  751. package/.versions/2.0.9/.pi/harnesses/lib/fleet-dashboard-ops.ts +178 -0
  752. package/.versions/2.0.9/.pi/harnesses/lib/fleet-dashboard-view.ts +134 -0
  753. package/.versions/2.0.9/.pi/harnesses/lib/fleet-detail-view.ts +247 -0
  754. package/.versions/2.0.9/.pi/harnesses/lib/fleet-overlay.ts +26 -0
  755. package/.versions/2.0.9/.pi/harnesses/lib/fleet-panel.ts +34 -0
  756. package/.versions/2.0.9/.pi/harnesses/lib/fleet-read-model.ts +213 -0
  757. package/.versions/2.0.9/.pi/harnesses/lib/fleet-selection.ts +24 -0
  758. package/.versions/2.0.9/.pi/harnesses/lib/fleet-strip-controller.ts +74 -0
  759. package/.versions/2.0.9/.pi/harnesses/lib/fleet-strip-view.ts +132 -0
  760. package/.versions/2.0.9/.pi/harnesses/lib/fleet-transcript-store.ts +244 -0
  761. package/.versions/2.0.9/.pi/harnesses/lib/herdr-client.ts +472 -0
  762. package/.versions/2.0.9/.pi/harnesses/lib/herdr-presence.ts +399 -0
  763. package/.versions/2.0.9/.pi/harnesses/lib/hermes-monitor-events.ts +136 -0
  764. package/.versions/2.0.9/.pi/harnesses/lib/hermes-monitor-herdr.ts +28 -0
  765. package/.versions/2.0.9/.pi/harnesses/lib/hermes-monitor-model.ts +18 -0
  766. package/.versions/2.0.9/.pi/harnesses/lib/hermes-monitor-registry.ts +6 -0
  767. package/.versions/2.0.9/.pi/harnesses/lib/hermes-monitor-socket.ts +163 -0
  768. package/.versions/2.0.9/.pi/harnesses/lib/hermes-monitor-store.ts +31 -0
  769. package/.versions/2.0.9/.pi/harnesses/lib/spawned-peers.js +190 -0
  770. package/.versions/2.0.9/.pi/harnesses/lib/update-check.ts +222 -0
  771. package/.versions/2.0.9/.pi/harnesses/package-lock.json +2039 -0
  772. package/.versions/2.0.9/.pi/harnesses/package.json +10 -0
  773. package/.versions/2.0.9/.pi/prompts/af-build.md +24 -0
  774. package/.versions/2.0.9/.pi/prompts/af-code-simplify.md +22 -0
  775. package/.versions/2.0.9/.pi/prompts/af-constraints.md +31 -0
  776. package/.versions/2.0.9/.pi/prompts/af-plan.md +17 -0
  777. package/.versions/2.0.9/.pi/prompts/af-review.md +16 -0
  778. package/.versions/2.0.9/.pi/prompts/af-set-hermes-telegram.md +15 -0
  779. package/.versions/2.0.9/.pi/prompts/af-set-hermes-watchdog.md +6 -0
  780. package/.versions/2.0.9/.pi/prompts/af-ship.md +17 -0
  781. package/.versions/2.0.9/.pi/prompts/af-spec.md +15 -0
  782. package/.versions/2.0.9/.pi/prompts/af-test.md +19 -0
  783. package/.versions/2.0.9/.pi/skills/bowser/SKILL.md +145 -0
  784. package/.versions/2.0.9/.version +1 -0
  785. package/.versions/2.0.9/agents/architect.md +25 -0
  786. package/.versions/2.0.9/agents/bowser.md +28 -0
  787. package/.versions/2.0.9/agents/builder.md +56 -0
  788. package/.versions/2.0.9/agents/code-reviewer.md +210 -0
  789. package/.versions/2.0.9/agents/deep-researcher.md +33 -0
  790. package/.versions/2.0.9/agents/documenter.md +23 -0
  791. package/.versions/2.0.9/agents/orchestrator.md +23 -0
  792. package/.versions/2.0.9/agents/plan-reviewer.md +84 -0
  793. package/.versions/2.0.9/agents/planner.md +106 -0
  794. package/.versions/2.0.9/agents/releaser.md +25 -0
  795. package/.versions/2.0.9/agents/researcher.md +31 -0
  796. package/.versions/2.0.9/agents/security-auditor.md +168 -0
  797. package/.versions/2.0.9/agents/test-engineer.md +154 -0
  798. package/.versions/2.0.9/agents/web-debugger.md +44 -0
  799. package/.versions/2.0.9/agents/web-performance-auditor.md +194 -0
  800. package/.versions/2.0.9/bin/catalog/harness-runtime-closure.json +32 -0
  801. package/.versions/2.0.9/codex/fleet-session-client/SKILL.md +34 -0
  802. package/.versions/2.0.9/codex/fleet-session-client.zip +0 -0
  803. package/.versions/2.0.9/docs/ARCHITECTURE.md +416 -0
  804. package/.versions/2.0.9/docs/agent-fleet-setup.md +568 -0
  805. package/.versions/2.0.9/docs/claude-code-coms-bridge.md +134 -0
  806. package/.versions/2.0.9/docs/codex-session-bridge.md +219 -0
  807. package/.versions/2.0.9/docs/coms-hermes-bridge.md +188 -0
  808. package/.versions/2.0.9/docs/getting-started.md +126 -0
  809. package/.versions/2.0.9/docs/npm-install.md +356 -0
  810. package/.versions/2.0.9/docs/pi-extensions.md +449 -0
  811. package/.versions/2.0.9/docs/pi-setup.md +76 -0
  812. package/.versions/2.0.9/docs/skill-anatomy.md +150 -0
  813. package/.versions/2.0.9/install-manifest.json +2991 -0
  814. package/.versions/2.0.9/justfile +247 -0
  815. package/.versions/2.0.9/manifest-meta.json +970 -0
  816. package/.versions/2.0.9/references/accessibility-checklist.md +160 -0
  817. package/.versions/2.0.9/references/communication-contract.md +26 -0
  818. package/.versions/2.0.9/references/definition-of-done.md +67 -0
  819. package/.versions/2.0.9/references/fleet-coordination-patterns.md +171 -0
  820. package/.versions/2.0.9/references/observability-checklist.md +92 -0
  821. package/.versions/2.0.9/references/orchestration-patterns.md +370 -0
  822. package/.versions/2.0.9/references/performance-checklist.md +236 -0
  823. package/.versions/2.0.9/references/prompting-patterns.md +380 -0
  824. package/.versions/2.0.9/references/security-checklist.md +245 -0
  825. package/.versions/2.0.9/references/testing-patterns.md +235 -0
  826. package/.versions/2.0.9/references/workflow-authoring.md +304 -0
  827. package/.versions/2.0.9/skills/_internal/grilling.md +59 -0
  828. package/.versions/2.0.9/skills/browser-testing-with-devtools/SKILL.md +351 -0
  829. package/.versions/2.0.9/skills/code-review-and-quality/SKILL.md +396 -0
  830. package/.versions/2.0.9/skills/compound-learning/SKILL.md +137 -0
  831. package/.versions/2.0.9/skills/constraint-driven-development/SKILL.md +338 -0
  832. package/.versions/2.0.9/skills/constraint-driven-development/references/floor-guard.md +99 -0
  833. package/.versions/2.0.9/skills/context-engineering/SKILL.md +341 -0
  834. package/.versions/2.0.9/skills/deprecation-and-migration/SKILL.md +247 -0
  835. package/.versions/2.0.9/skills/designing-agents/SKILL.md +394 -0
  836. package/.versions/2.0.9/skills/designing-agents/pi-harness-authoring.md +222 -0
  837. package/.versions/2.0.9/skills/drafting-workflows/SKILL.md +143 -0
  838. package/.versions/2.0.9/skills/drafting-workflows/scripts/make-workflow.ts +177 -0
  839. package/.versions/2.0.9/skills/frontend-ui-engineering/SKILL.md +328 -0
  840. package/.versions/2.0.9/skills/git-workflow-and-versioning/SKILL.md +316 -0
  841. package/.versions/2.0.9/skills/idea-refine/SKILL.md +182 -0
  842. package/.versions/2.0.9/skills/idea-refine/examples.md +238 -0
  843. package/.versions/2.0.9/skills/idea-refine/frameworks.md +99 -0
  844. package/.versions/2.0.9/skills/idea-refine/refinement-criteria.md +113 -0
  845. package/.versions/2.0.9/skills/idea-refine/scripts/idea-refine.sh +15 -0
  846. package/.versions/2.0.9/skills/incremental-implementation/SKILL.md +302 -0
  847. package/.versions/2.0.9/skills/interview-me/SKILL.md +226 -0
  848. package/.versions/2.0.9/skills/orchestration-verification/SKILL.md +181 -0
  849. package/.versions/2.0.9/skills/peer-coms/SKILL.md +90 -0
  850. package/.versions/2.0.9/skills/performance-optimization/SKILL.md +496 -0
  851. package/.versions/2.0.9/skills/planning-and-task-breakdown/SKILL.md +289 -0
  852. package/.versions/2.0.9/skills/security-and-hardening/SKILL.md +524 -0
  853. package/.versions/2.0.9/skills/spec-driven-development/SKILL.md +295 -0
  854. package/.versions/2.0.9/skills/using-agent-skills/SKILL.md +198 -0
  855. package/.versions/2.0.9/vendor/agent-skills-upstream/LICENSE +21 -0
  856. package/.versions/2.0.9/vendor/agent-skills-upstream/README.md +430 -0
  857. package/.versions/2.0.9/vendor/agent-skills-upstream/skills/api-and-interface-design/SKILL.md +367 -0
  858. package/.versions/2.0.9/vendor/agent-skills-upstream/skills/browser-testing-with-devtools/SKILL.md +317 -0
  859. package/.versions/2.0.9/vendor/agent-skills-upstream/skills/ci-cd-and-automation/SKILL.md +390 -0
  860. package/.versions/2.0.9/vendor/agent-skills-upstream/skills/code-review-and-quality/SKILL.md +396 -0
  861. package/.versions/2.0.9/vendor/agent-skills-upstream/skills/code-simplification/SKILL.md +331 -0
  862. package/.versions/2.0.9/vendor/agent-skills-upstream/skills/constraint-driven-development/SKILL.md +311 -0
  863. package/.versions/2.0.9/vendor/agent-skills-upstream/skills/constraint-driven-development/references/floor-guard.md +99 -0
  864. package/.versions/2.0.9/vendor/agent-skills-upstream/skills/context-engineering/SKILL.md +337 -0
  865. package/.versions/2.0.9/vendor/agent-skills-upstream/skills/debugging-and-error-recovery/SKILL.md +300 -0
  866. package/.versions/2.0.9/vendor/agent-skills-upstream/skills/deprecation-and-migration/SKILL.md +247 -0
  867. package/.versions/2.0.9/vendor/agent-skills-upstream/skills/documentation-and-adrs/SKILL.md +288 -0
  868. package/.versions/2.0.9/vendor/agent-skills-upstream/skills/doubt-driven-development/SKILL.md +243 -0
  869. package/.versions/2.0.9/vendor/agent-skills-upstream/skills/frontend-ui-engineering/SKILL.md +328 -0
  870. package/.versions/2.0.9/vendor/agent-skills-upstream/skills/git-workflow-and-versioning/SKILL.md +355 -0
  871. package/.versions/2.0.9/vendor/agent-skills-upstream/skills/idea-refine/SKILL.md +178 -0
  872. package/.versions/2.0.9/vendor/agent-skills-upstream/skills/idea-refine/examples.md +238 -0
  873. package/.versions/2.0.9/vendor/agent-skills-upstream/skills/idea-refine/frameworks.md +99 -0
  874. package/.versions/2.0.9/vendor/agent-skills-upstream/skills/idea-refine/refinement-criteria.md +113 -0
  875. package/.versions/2.0.9/vendor/agent-skills-upstream/skills/idea-refine/scripts/idea-refine.sh +15 -0
  876. package/.versions/2.0.9/vendor/agent-skills-upstream/skills/incremental-implementation/SKILL.md +249 -0
  877. package/.versions/2.0.9/vendor/agent-skills-upstream/skills/interview-me/SKILL.md +225 -0
  878. package/.versions/2.0.9/vendor/agent-skills-upstream/skills/observability-and-instrumentation/SKILL.md +238 -0
  879. package/.versions/2.0.9/vendor/agent-skills-upstream/skills/performance-optimization/SKILL.md +496 -0
  880. package/.versions/2.0.9/vendor/agent-skills-upstream/skills/planning-and-task-breakdown/SKILL.md +257 -0
  881. package/.versions/2.0.9/vendor/agent-skills-upstream/skills/security-and-hardening/SKILL.md +524 -0
  882. package/.versions/2.0.9/vendor/agent-skills-upstream/skills/shipping-and-launch/SKILL.md +330 -0
  883. package/.versions/2.0.9/vendor/agent-skills-upstream/skills/source-driven-development/SKILL.md +216 -0
  884. package/.versions/2.0.9/vendor/agent-skills-upstream/skills/spec-driven-development/SKILL.md +245 -0
  885. package/.versions/2.0.9/vendor/agent-skills-upstream/skills/test-driven-development/SKILL.md +398 -0
  886. package/.versions/2.0.9/vendor/agent-skills-upstream/skills/using-agent-skills/SKILL.md +192 -0
  887. package/CHANGELOG.md +35 -0
  888. package/agents/architect.md +1 -1
  889. package/agents/bowser.md +1 -1
  890. package/agents/builder.md +1 -1
  891. package/agents/code-reviewer.md +1 -1
  892. package/agents/deep-researcher.md +1 -1
  893. package/agents/documenter.md +1 -1
  894. package/agents/orchestrator.md +1 -1
  895. package/agents/plan-reviewer.md +1 -1
  896. package/agents/planner.md +1 -1
  897. package/agents/releaser.md +1 -1
  898. package/agents/researcher.md +1 -1
  899. package/agents/security-auditor.md +1 -1
  900. package/agents/test-engineer.md +1 -1
  901. package/agents/web-debugger.md +1 -1
  902. package/agents/web-performance-auditor.md +1 -1
  903. package/bin/cli.js +8 -5
  904. package/bin/lib/path-boundaries.js +5 -6
  905. package/bin/lib/stt-wizard.js +154 -23
  906. package/docs/agent-fleet-setup.md +26 -8
  907. package/docs/npm-install.md +29 -2
  908. package/docs/pi-extensions.md +3 -0
  909. package/docs/pi-setup.md +16 -0
  910. package/install-manifest.json +1 -1
  911. package/package.json +45 -13
  912. package/skills/orchestration-verification/SKILL.md +1 -0
@@ -0,0 +1,1217 @@
1
+ # agent-hub
2
+
3
+ The unified Agent Fleet runtime for pi, with [`coms`](../coms/README.md) **embedded**. Bare
4
+ `just fleet` loads Fleet Core and starts `agent-hub` in **operator** work mode with direct coding
5
+ and orchestration tools, but no standing native roster. The same live session can switch to
6
+ **orchestrator** work mode, which removes direct coding tools and drives native specialists under
7
+ the Verification Contract. Fleet Core loads first: [`damage-control-continue`](../damage-control-continue/README.md),
8
+ [`ask-user-remote`](../ask-user-remote/README.md), STT, Compact & Continue, BTW, and the update
9
+ checker. Both work modes can adjust the native roster, run research, collaborate with Pi/Claude
10
+ peers, and hand the session to a visible coms peer.
11
+
12
+ > Consolidates the retired `agent-team` dispatcher into this harness and embeds the ported `coms`
13
+ > P2P layer from [`pi-vs-claude-code`](https://github.com/disler/pi-vs-claude-code) by
14
+ > [disler](https://github.com/disler) (MIT). See the
15
+ > [extension catalog](../../../docs/pi-extensions.md) and the
16
+ > [design plan](../../../docs/plans/agent-hub/).
17
+
18
+ **Optional ChatGPT client:** `just fleet --agents <roster> --peers <preset> --project <name>` can supply the live Pi session that the experimental [ChatGPT Fleet session client](https://github.com/chankov/agent-fleet/blob/main/docs/codex-session-bridge.md) selects. Hermes remains the inbound `ask_user` route.
19
+
20
+ ## Work Mode, roster, and topology
21
+
22
+ These are independent runtime axes:
23
+
24
+ - **Work Mode** — `/af-work-mode operator|orchestrator` switches prompt and active tools without
25
+ restarting or losing session state; `/af-work-mode` without an argument and **Alt+M** open the
26
+ two-option picker. Operator keeps `read`, `bash`, `edit`, `write`, approved extension tools, and
27
+ orchestration. Orchestrator withholds direct coding tools but keeps dispatch, research, assertions,
28
+ roster controls, `ask_user`, ready coms, and ready Herdr tools. In orchestrator work mode, raw
29
+ Herdr panes are auxiliary-process orchestration—not a route around delegation for reading,
30
+ editing, testing, or implementing code.
31
+ - **Native roster** — local headless Pi specialists from `.pi/agents/teams.yaml`. Bare Fleet starts
32
+ empty; select one with `--agents frontend` or add one live with `/af-agents-add code-reviewer`.
33
+ - **Peer topology** — separate long-lived Pi or Claude Code processes from `peers.yaml`, connected
34
+ by coms and optionally placed in sibling Herdr panes. `--peers frontend` selects a standing
35
+ preset; `--herdr` creates a Hub-only workspace through the empty `base` preset.
36
+ Switching from Operator to Orchestrator with no active agents automatically loads the first valid
37
+ team in configuration order (`default` in the shipped configuration), skipping empty teams and teams
38
+ with missing personas. Existing agents are kept. If no valid team is available, the switch is refused
39
+ with a warning. The selected team is saved in the session just like a manual team selection.
40
+ Budgets, nested delegation, and Verification Contract rigor follow the **task tier**, not Work Mode.
41
+
42
+ All Hub slash commands, including `/af-handoff`, are registered in both work modes. A command whose
43
+ runtime capability is unavailable refuses with remediation rather than disappearing. `--no-coms`
44
+ disables only embedded coms; direct operator work and native dispatch remain available.
45
+
46
+ ### Automatic capability surfaces
47
+
48
+ Capability packs load **automatically** from the current request, work mode, task tier, pending work,
49
+ and runtime state; there is no activation command. `core` is always present. Orchestrator work mode
50
+ always includes `fleet`; explicit delegation/research, acceptance work, an existing coms peer, a
51
+ Herdr pane/watcher request, and explicit or imminent compaction respectively add `fleet`,
52
+ `verification`, `peer`, `workspace`, and `compaction`. A ready coms or Herdr runtime is only
53
+ **readiness**, not intent: its tools and policy remain model-inactive until requested.
54
+
55
+ Ambiguous delegation, peer, or workspace intent provisionally exposes the smallest relevant pack
56
+ and records its reason in the state capsule and `/af-context`. Before that pack's first side effect,
57
+ the Hub asks one focused `ask_user` confirmation. Confirming promotes it for the task; reject or
58
+ cancel removes it and leaves no message, child, or pane behind. Active task packs persist through
59
+ follow-up turns so a workflow does not lose tools. They shrink only through
60
+ `set_task_tier(new_task: true)` (apart from mandatory work mode and pending-operation leases), never
61
+ merely because the next message sounds different.
62
+
63
+ `/af-context` separates stable replacement-prompt cost from the volatile state capsule and active
64
+ schemas. Inactive and ready-but-inactive packs cost zero model-visible characters. Provider totals,
65
+ including cache read/write when Pi supplies them, remain authoritative; deterministic character
66
+ figures are regression diagnostics and never invent provider usage.
67
+
68
+ ### Context-pressure and resume recovery
69
+
70
+ Pre-turn surface cost and live conversation pressure are different budgets. `/af-context` separates
71
+ the stable replacement prompt, volatile state capsule, and active tool schemas; user and assistant
72
+ messages plus tool results then accumulate during a turn. A long tool loop can therefore reach the
73
+ model window even while every standing prompt ceiling remains green.
74
+
75
+ The Hub samples live provider usage and projects each finalized tool result before another model
76
+ request:
77
+
78
+ - Below **80%**, pressure is `normal`.
79
+ - At **80%**, pressure becomes `warning`; the compact recovery surface is exposed transiently and
80
+ ordinary work may continue.
81
+ - At **90%**, the Hub aborts the next same-turn provider request, waits until the tool result and
82
+ aborted turn are persisted, and starts one automatic Pi compaction. Only one recovery may run at
83
+ a time. Input received while startup or same-turn recovery is active is retained in memory,
84
+ including images, then replayed once after compaction succeeds.
85
+
86
+ The status line and `/af-context` show the pressure phase, measured usage, both thresholds, episode,
87
+ and last recovery outcome. Persisted pressure diagnostics contain numeric/enumerated metadata only;
88
+ they never include prompts, tool output, credentials, error bodies, or compaction summaries.
89
+
90
+ If automatic recovery reports `failed`, the queued input remains retained. Use Pi's built-in manual
91
+ fallback, or switch to a model with a larger context window:
92
+
93
+ ```text
94
+ /compact Preserve the current goal, decisions, assertions, pending operations, blockers, and next step.
95
+ ```
96
+
97
+ A resumed orchestrator session can also require roster recovery. The Hub persists only the selected
98
+ team name and resolves it again against the current `.pi/agents/teams.yaml` and persona files. If the
99
+ team is missing, renamed, empty, or stale, the Hub preserves orchestrator work mode, keeps direct coding
100
+ tools unavailable, and blocks model input rather than inventing a roster or silently downgrading.
101
+ Recover with one of these explicit choices:
102
+
103
+ ```text
104
+ /af-agents-team # select a currently valid team in the live session
105
+ /af-work-mode operator # explicitly leave delegate-only work mode and restore direct tools
106
+ just fleet --agents <name> # restart through the public Fleet CLI
107
+ just fleet --work-mode operator # restart explicitly as an operator
108
+ ```
109
+
110
+ For a direct Pi launch, the roster flag is `--agent-team <name>` and the work mode flag is
111
+ `--work-mode operator`; explicit startup flags take precedence over persisted selections. Fix stale
112
+ team/persona declarations before selecting them.
113
+
114
+ The Pi session JSONL under `~/.pi/agent/sessions/` is the authoritative append-only conversation and
115
+ recovery record. Context overflow or a stale roster does **not** by itself mean that file is corrupt.
116
+ Inspect it through `/session`, resume it through `/resume` or Pi's session flags, and recover through
117
+ compaction or the commands above. Never edit, truncate, reorder, or synthesize JSONL entries to
118
+ recover a session.
119
+
120
+ ## What it does
121
+
122
+ The whole dispatch loop, end to end:
123
+
124
+ ```mermaid
125
+ sequenceDiagram
126
+ autonumber
127
+ actor U as You
128
+ participant H as Hub (dispatcher)
129
+ participant S as Specialist (e.g. builder)
130
+ participant R as Research helper
131
+ participant D as Disk (.pi/agent-sessions/)
132
+
133
+ U->>H: task
134
+ H->>D: set_assertions — Verification Contract persisted
135
+ H->>S: dispatch_agent (task + advisory scope)
136
+ S-->>H: NEEDS_RESEARCH: how does X work?
137
+ H->>R: spawn_research (researcher / deep-researcher)
138
+ R->>D: write findings file
139
+ R-->>H: one-line notice + path
140
+ H->>S: resume with file paths — never raw findings
141
+ S-->>H: structured return + named evidence
142
+ H->>D: update_assertion
143
+ H-->>U: Assertions: 2✓ 1○ 1✗ · open: A4
144
+ ```
145
+
146
+ Every borrowed idea from another harness passes one test before it lands: *does this persistently enter the dispatcher context?* If yes, it goes to disk or a one-line status instead.
147
+
148
+ `agent-hub` is the supported home for the former standalone dispatcher features:
149
+
150
+ - **Dispatcher grid** — a live dashboard of the active, dynamically adjustable native roster from `.pi/agents/teams.yaml`.
151
+ - **Context budget** — `/af-context` opens a separate read-only full-screen diagnostic in either work mode. It shows provider totals and cache fields beside named, metadata-only estimates; `loaded-excluded` Pi inputs are discovered but contribute zero to the replacement Hub prompt. Each specialist, research helper, delegate, and peer remains a separate context plane with its own model window. Component token estimates are heuristic/provider-scaled, never exact claims; unavailable peer/provider detail is labelled explicitly and raw prompts, schemas, and conversation text are never retained or displayed.
152
+ - **Specialist delegation** — `dispatch_agent` sends writable tasks to configured specialists.
153
+ - **Research helpers** — the dispatcher invokes `spawn_research` automatically for read-only
154
+ investigation; specialists can trigger the separate automatic `NEEDS_RESEARCH:` pipe described
155
+ below. Managed research children use a replacement read-only prompt with `--no-skills` and
156
+ `--no-context-files`; managed specialists receive a selected context manifest (persona, applicable
157
+ policy paths, and named skill paths) rather than inherited global skill/context loading. Two
158
+ `kind: research` personas ship by default: `researcher` (`gpt-5.6-luna`, low thinking) for simple
159
+ reads and `deep-researcher` (`grok-4.6`, medium thinking) for hard, cross-cutting investigation.
160
+ The dispatcher routes by persona; each persona's model + thinking level is shown in its catalog.
161
+ Live helpers appear in the Fleet Dashboard (`Alt+A`) and bounded fleet widget while they are
162
+ running. On every terminal outcome (success, error, timeout, spawn/preflight failure, or operator
163
+ kill) the live `rN` handle is removed immediately.
164
+ Session, transcript, and `findings/*.md` files remain on disk for the requester, and
165
+ `/af-agents-history` keeps the audit/timing record. Finished helpers cannot be restarted; a new
166
+ request always creates a fresh helper. `rN` handles are never reused during a Hub session.
167
+ - **Human handoff path** — `ask_user` is exposed by the `ask-user-remote` wrapper (capturing stock
168
+ `pi-ask-user` and optionally racing a `user-remote` bridge), so specialists can bubble decisions
169
+ back through the dispatcher.
170
+ - **Auto-research pipe (`NEEDS_RESEARCH:`)** — a specialist that lacks information pauses by ending
171
+ its turn with `NEEDS_RESEARCH: <question>` lines (mirror of the `ASK_USER:` protocol). The hub
172
+ intercepts them **in code**: it fans out read-only research helpers (max 4 questions per pause,
173
+ 2 pauses per dispatch), writes each helper's findings to `.pi/agent-sessions/findings/*.md`, and
174
+ resumes the specialist's session with the file paths. The dispatcher LLM sees only a one-line
175
+ notice — raw findings never enter its context. Findings files are wiped at session start.
176
+ - **Verification Contract (assertion ledger)** — the dispatcher owns a ledger of checkable
177
+ acceptance assertions built from the request *before* any builder runs, so a clearly stated
178
+ requirement is never silently dropped. `set_assertions` records the numbered, tagged assertions
179
+ (`test` | `runtime-ui` | `code-grep` | `manual`, one pass condition each, plus a required
180
+ `source` naming where the requirement comes from) and rebuilds the whole
181
+ ledger on a "wrong again" regression reset; `update_assertion` marks each one proven (named
182
+ evidence required), unproven, or failed after a verification gate; `get_assertions` reads the
183
+ full ledger (ids, tags, pass conditions, evidence) back. The hub persists the ledger to
184
+ `.pi/agent-sessions/assertions.json` (wiped at session start like `findings/`) and renders a
185
+ one-line status (`Assertions: 2✓ 1○ 1✗ · open: A4`) so the contract survives compaction without
186
+ re-flooding the dispatcher LLM context — after a compaction the dispatcher calls `get_assertions`
187
+ to recover the full text the status line omits. The `orchestrator` persona drives it — a deep-researcher
188
+ parity inventory for "behave like" requests, runtime proof for UI/visibility assertions, the
189
+ regression reset on a re-ask — per
190
+ [`orchestration-verification`](../../../skills/orchestration-verification/SKILL.md). The hub also
191
+ machine-parses each assertion-carrying specialist's structured return, writes the full raw output
192
+ to `.pi/agent-sessions/sessions/<sessionId>/artifacts/returns/<agentKey>-<dispatchId>.md`, surfaces only a compact
193
+ `details.structuredReturn` digest plus `details.returnPath`, and marks contract notices such as
194
+ missing assertion ids or evidence-less `assertions_proven` entries (demoted to unproven in the
195
+ tool text). `details.fullOutput` remains for `/af-zoom`/compatibility, but dispatcher-visible text is
196
+ digest + path oriented. `update_assertion(status: "proven")` validates evidence by assertion tag:
197
+ test evidence needs a command/test and outcome, `code-grep` needs pattern plus result sample,
198
+ manual needs user/`ask_user` confirmation, and `runtime-ui` needs an existing artifact path under
199
+ `.pi/agent-sessions/artifacts/evidence/`. **Advisory by design** (PRD open question 2): status is
200
+ surfaced and "proven" requires named evidence, but a dispatch is never hard-refused on an unproven
201
+ assertion — code-enforcement is the Checkpoint A decision. Two contract rules ARE enforced at the
202
+ tool: a batch with any sourceless assertion is refused with the offending ids named (a specialist
203
+ told to prove `A9` must be able to read its origin instead of spending a dispatch and an ASK_USER
204
+ cycle asking where `A9` was defined), and a batch over **8** open assertions is accepted with a
205
+ warning suggesting the split — declare the batch the next dispatches actually prove, and
206
+ `set_assertions` the next one when it starts.
207
+ - **Artifact bus** — session handoffs live under `.pi/agent-sessions/artifacts/` with conventional
208
+ `returns/`, `failures/`, `plans/`, `reviews/`, `inventories/`, and `evidence/` subdirectories, all
209
+ **archived** into an immutable `runs/<runId>/` namespace at session start rather than wiped (see
210
+ [Immutable per-run artifact namespaces](#immutable-per-run-artifact-namespaces-run-namespacejs)),
211
+ so a later session can never overwrite an earlier one's returns. `failures/` is separate on purpose: a run
212
+ that errored or timed out produced no specialist result, so its output goes there and the dispatch
213
+ result names it a **delivery failure** carrying no assertion evidence. Filing a 142-byte coms error
214
+ stub as `returns/code-reviewer-run4.md` once cost a 103-second dispatch investigating a review that
215
+ had in fact succeeded — only its reply was lost. `dispatch_agent` and `spawn_research` accept optional
216
+ `artifacts: string[]` paths (repo-relative or session-artifact-relative); the hub validates that
217
+ they stay inside the repo/session roots and injects only the path plus first heading/one-line
218
+ preview, never file bodies. Document-producing specialists are instructed to write plans, reviews,
219
+ inventories, and reports to the real session path
220
+ `.pi/agent-sessions/artifacts/<kind>/<agentKey>-run<N>.md` when their tools allow it, then report/pass
221
+ the artifact-relative handoff path `artifacts/<kind>/<agentKey>-run<N>.md`, finish with that path plus
222
+ a ≤10-line digest, and still include structured returns when assertions are carried. Repo-root
223
+ `./artifacts/...` files are not session artifacts. Planner's existing PLAN_FILE behavior is preserved;
224
+ the artifact path is an additional handoff channel.
225
+ - **Dispatch scope advisory** — `dispatch_agent` accepts optional `scope: string[]` for writable
226
+ builder-style runs. The orchestrator should derive these globs from the plan task's file list,
227
+ and skip scope for exploratory/reconnaissance work where the right files are not known yet. The
228
+ hub snapshots git status before the writable dispatch, diffs after the whole tool call (including
229
+ auto-research resumes), and reports out-of-scope paths in `details.scopeViolations` plus a ⚠ text
230
+ notice. This is advisory only: the hub never blocks completion, reverts files, or escalates
231
+ automatically. Known limitation: concurrent writable dispatches can only be attributed
232
+ approximately, so overlapping runs are flagged in the notice.
233
+ - **Agent controls** — `/af-zoom` inspects a live agent timeline; `/af-agents-history` replays the run as a
234
+ timeline (orchestrator turns, dispatches, research helpers) with per-agent durations, parallel-run
235
+ markers, and a grand total; kill/restart controls manage running child agents; per-agent `model:`
236
+ fields select models from team config. `/af-agents-kill <name|rN|all>` SIGTERMs a specialist (keeping
237
+ its standing card) or kills a currently running research helper (`all` clears every live helper).
238
+ `/af-agents-restart <name>` re-runs a specialist's last task fresh; research helpers cannot be
239
+ restarted. `/af-zoom <name|rN>` opens a running helper through the Fleet data model. Research spawning
240
+ and follow-up reconnaissance are automated through `spawn_research` and `NEEDS_RESEARCH:`; there are
241
+ no dedicated research lifecycle slash commands.
242
+ Restartable team specialists at or above 70% context render
243
+ their context percentage with a warning marker/color in the Fleet Dashboard, and their next
244
+ `dispatch_agent` result adds a `/af-agents-restart <persona>` hint. Research helpers are not warned,
245
+ and the hub never restarts specialists automatically.
246
+ - **Model switching** — a persona's frontmatter `models:` list declares the models it may switch to
247
+ (the default `model:` is implicitly a candidate). `/af-agent-model <persona>` picks from that list;
248
+ the choice lasts for the session and takes effect on the persona's next dispatch
249
+ (`/af-agents-restart <persona>` applies it immediately). The dot form
250
+ `/af-agent-model <persona>.<role>` switches a delegate sub-role's model instead — its candidates are
251
+ the role's declared default plus the parent persona's own candidate list; the switch is applied
252
+ when the parent is next dispatched (it lands in the serialized delegate config, so nested
253
+ children inherit it). `/af-models [profile]` applies a named profile
254
+ from `.pi/agents/model-profiles.yaml` — a macro over the same declared candidates, validated at
255
+ session start (a profile with any entry outside a persona's candidates is dropped whole, with an
256
+ error). This is the legacy flat format. Version 2 profiles also set all child roles, thinking,
257
+ dispatcher, watchdog/extraction, poll/debate and routing from one selection; they declare their
258
+ own models without project candidate overrides. See [complete model profiles](../../../docs/agent-fleet-setup.md#complete-model-profiles). Those
259
+ declared-candidate commands stay within their lists; Fleet Detail and the session-wide
260
+ substitution target picker intentionally use Pi's currently available registry. When an effective project or session override
261
+ fails with a model/provider error or aborted request before work begins (including local-model
262
+ memory-limit failures), the hub retries once with the model originally declared in the persona
263
+ frontmatter. For **write-capable** runs this is pre-work only: no fallback occurs after text
264
+ output, a tool call, cancellation, timeout, drift stop, or a Pi process-spawn failure, avoiding
265
+ duplicate writes. **Read-only children and research helpers** (tools limited to
266
+ `read,grep,find,ls`) also retry once when the provider fails *mid-run* — re-running a reader
267
+ repeats nothing, and those are exactly the children that exist to protect their parent's context,
268
+ so losing one to a local-endpoint OOM halfway through discards work for no safety gain. A
269
+ terminated run (watchdog, deadline, cancellation) never retries either way: that is a verdict on
270
+ the work, not a provider outage. The failed attempt is removed from the child session before retry. Per project,
271
+ `model.<persona>:` / `models.<persona>:` keys under `## agent-hub` in
272
+ `.ai/agent-fleet-overrides.md` replace a persona's default model / candidate list.
273
+ Research personas (`researcher` / `deep-researcher`, `kind: research`) are switchable the same
274
+ way — `/af-agent-model <persona>` and `/af-agent-model-thinking <persona>` accept them alongside team
275
+ members. Since research helpers are spawned fresh through `spawn_research`, the switch lands on
276
+ their next spawn (there is no running instance to `/af-agents-restart`).
277
+ `/af-agent-models-substitute [<source> <target>]` saves a runtime source → target mapping for
278
+ the current session. With no arguments it opens the same two-step visual picker as `m` in Fleet
279
+ Dashboard: first choose a source from every model configured across persona defaults, candidates,
280
+ fallbacks, and delegate sub-roles; then choose a target from Pi's currently available models. The
281
+ two-argument form performs the same operation directly. The mapping is resolved when work is
282
+ spawned rather than eagerly copied into today's roster, so team members, research personas, and
283
+ delegate sub-roles activated or created later in the session inherit it automatically. Existing
284
+ runs are not interrupted, and all mappings reset at the next `session_start`.
285
+ - **Thinking levels** — each persona's frontmatter `thinking:` sets its pi `--thinking`
286
+ reasoning effort (`off` · `minimal` · `low` · `medium` · `high` · `xhigh`). `/af-agent-model-thinking
287
+ <persona>` switches it among those six levels for the session; like a model switch it takes effect
288
+ on the persona's next dispatch (`/af-agents-restart <persona>` applies it now), and selecting the
289
+ frontmatter default clears the override. The level shows as a short badge after the model
290
+ everywhere a model is rendered — `gpt-5.5 (xh)` in the dashboard (`min`/`low`/`med`/`hi`/`xh`; `off` shows no badge). Per project, a `thinking.<persona>:` key
291
+ under `## agent-hub` in `.ai/agent-fleet-overrides.md` replaces a persona's default level.
292
+ - **Mid-turn delegation (`delegate` tool)** — a persona that declares a `subagents:` map in its
293
+ frontmatter (`role: { model, tools? }` entries, or an indented `model:`/`tools:` block per role)
294
+ gets a real mid-turn `delegate(role, instruction, context?, allow_write?)` tool, injected as an
295
+ extra `-e delegate.ts` extension into its spawned process (the `delegate` tool name is appended to
296
+ its `--tools` allowlist — pi filters extension tools too). Only declared roles are spawnable, on
297
+ their declared models — model choice is configuration, never the child LLM's. Budgets are readable
298
+ refusals: at most 4 delegate children per dispatch, tree-wide, and a per-persona `delegate_depth:`
299
+ budget capped at 1 (the default). Children spawned with remaining depth 0 do not receive the
300
+ `delegate` extension/tool. Write safety: children run read-only (`read,grep,find,ls`) unless a
301
+ SINGLE live child gets `allow_write: true`, which inherits the parent's tools intersected with the
302
+ role's `tools:` cap; if a declared role cap leaves no available tools, delegation is refused.
303
+ Concurrent children are always forced read-only. Children stream timeline events through
304
+ `.pi/agent-sessions/delegations/<persona>/events.jsonl`; the hub tails it and renders nested rows
305
+ under the parent's card (child id, model, tokens, status),
306
+ each openable with `/af-zoom <child-id>`. Each child also writes its full final output to
307
+ `.pi/agent-sessions/delegations/<persona>/results/<childId>.md`; the parent receives only status,
308
+ a required final `DIGEST:` section (≤30 lines with path:line citations), and the result-file path.
309
+ If a child omits `DIGEST:`, the parent gets the first ~30 lines plus a no-DIGEST warning and the
310
+ result path. Spend rolls up: every child row and the parent's subtree
311
+ total show tokens, and a session-wide `Δ delegated` counter sits in the status line.
312
+ `/af-agents-kill` on the parent SIGTERMs its whole process group, so the delegation tree dies with
313
+ it. `context: fork` is accepted but treated as a summary brief in v1. Per project,
314
+ `subagents.<persona>.<role>:` and `delegate-depth.<persona>:` keys under `## agent-hub` in
315
+ `.ai/agent-fleet-overrides.md` replace individual sub-roles / the depth budget. An overridden
316
+ role retains its frontmatter model as a one-shot fallback under the same pre-work-only safety
317
+ rule; delegate cards and results show the model that ultimately ran. Six personas ship with
318
+ declared sub-roles, on a three-tier OpenAI model ladder — `gpt-5.3-codex-spark` for
319
+ recon/grep sweeps, `gpt-5.4` for analysis sweeps, the `gpt-5.5` (or opus) parent reserved for
320
+ synthesis and verdicts:
321
+ - `code-reviewer` — `preflight`+`docs` (spark), `quality`+`perf` (gpt-5.4); its first delegate
322
+ call is always `preflight`, which studies the project rules and the files under review and
323
+ returns a summary that drives the rest of the fan-out. Deep security review is not a
324
+ sub-role — it belongs to the separate `security-auditor` persona, which the reviewer
325
+ recommends dispatching when it spots deeper risk.
326
+ - `planner` — `scout`+`rules` (spark) fan out before the plan is drafted; `risk` (gpt-5.4)
327
+ optionally challenges the draft breakdown.
328
+ - `plan-reviewer` — `feasibility` (gpt-5.4) checks plan claims against the actual codebase;
329
+ `deps` (spark) verifies dependency ordering and file overlap. No preflight — the plan is
330
+ the map.
331
+ - `security-auditor` — solo `recon` (spark) maps the attack surface first, then
332
+ `input-sweep` (gpt-5.4) and `secrets-sweep` (spark) fan out; exploit reasoning stays with
333
+ the parent.
334
+ - `builder` — `recon` (spark) maps call sites before edits; `verifier` (spark, the one
335
+ `allow_write: true` child) runs the test suite after them. Implementation is never
336
+ delegated.
337
+ - `test-engineer` — `coverage-scout`+`conventions` (spark) inventory gaps and test patterns;
338
+ test writing is never delegated.
339
+ - **Default damage-control guardrails** — `just fleet` and `just fleet --no-coms` load the
340
+ `damage-control-continue` harness before `agent-hub`, so dispatcher tool calls are checked against
341
+ `.pi/damage-control-rules.yaml` and a blocked call feeds back instead of aborting the turn. A
342
+ guardrail is also re-loaded into every native specialist, research helper, and nested delegate
343
+ (see [Safety scope](#safety-scope)). Missing safety plumbing refuses child dispatch.
344
+ - **Embedded coms** — the dispatcher is a discoverable peer on the local machine. Multiple
345
+ `agent-hub` (or plain `coms`) sessions on the same box find each other through per-project registry
346
+ files and exchange messages over a unix socket (named pipe on Windows).
347
+
348
+ `/af-zoom <name|rN|child-id>` opens the selected agent's full-screen stream detail. For fleet rows,
349
+ it uses the [Fleet Dashboard detail controls](#fleet-dashboard-and-detail); a directly addressed
350
+ fallback stream keeps the legacy zoom controls. Both overlays size to the terminal.
351
+
352
+ ### `/af-agents-history`
353
+
354
+ `/af-agents-history` (or **`h`** while the Fleet Dashboard is open) opens a read-only overlay (same chrome as `/af-zoom`) that replays the session as an
355
+ execution **tree**:
356
+
357
+ - **Orchestrator turns** — each dispatcher turn that actually dispatched something is a depth-0 row
358
+ labelled `(dispatcher)`. Chat-only turns add no rows.
359
+ - **Dispatched specialists and research helpers** nest one level beneath the turn that launched them;
360
+ **delegate sub-sub-agents** nest one level deeper still under the specialist that spawned them — in
361
+ start order at every level.
362
+ - **Parallel runs** — siblings whose run times overlap are marked with a `│→` connector, so a
363
+ concurrent fan-out reads as a visually grouped block.
364
+ - **Real-work durations** — each row shows that node's *own* work: its span **minus the time it spent
365
+ awaiting children**. A dispatcher blocked on six concurrent agents is credited only for the time it
366
+ actually worked between/around the awaits, never for the await itself — so the same wall-clock isn't
367
+ counted twice up the tree. The same subtraction applies to a specialist awaiting its own delegate
368
+ children. Format: plain seconds under a minute (`42sec`), `m:ss` above it (`10:20min` for 620s).
369
+ Running rows tick live (the overlay re-renders once a second) and a new dispatch appears the instant
370
+ it starts.
371
+ - **Footer** shows `Σ real work <total> · <n> runs (agents <a> + dispatchers <d>)` — the real work of
372
+ *everyone*: the dispatched specialists' and research helpers' full runtime (`agents`) plus each
373
+ dispatcher turn's own work (`dispatchers` — its span minus the time it awaited agents **and** the
374
+ human via `ask_user`). Wall-clock is deliberately **not** shown: it would fold in the idle gaps
375
+ while you're away between turns, and `ask_user` waits are subtracted for the same reason.
376
+
377
+ Navigate with `↑/↓`, press `G` to jump back to the live tail, and `Q`/`Esc` to close. The log resets
378
+ on each session start.
379
+
380
+ The default agent view includes a collapsed fleet summary below the editor. When the installed public
381
+ SDK editor contract can be positively verified, an empty focused editor can activate its bounded
382
+ inspection window with the registered `Alt+I` shortcut; the same chord collapses it, and `j`/`k`
383
+ select. Enter opens detail, while `x`/`r` use the same two-press confirmation and ownership checks as
384
+ the dashboard. Plain and Alt arrow keys remain editor input unchanged and exactly once. Existing
385
+ `Alt+M` and `Alt+A` shortcuts continue to open the work-mode picker and Fleet Dashboard exactly once
386
+ from either widget state. Autocomplete, paste, key release,
387
+ non-empty/unfocused editors, modal UI, RPC/print/headless modes, and unsupported custom editors do not
388
+ activate it; unsupported environments retain a noninteractive summary without a key hint. The window
389
+ uses at most `floor(terminal.rows / 3)` rows including chrome, retains completed/error runs for exactly
390
+ 10 seconds (or while the same selected run is pinned), and separates active peers from task counts.
391
+ Both fleet surfaces scrub terminal controls and size Unicode by display cells. A confirmed coms kill
392
+ aborts only the local request—the confirmation explicitly notes that the peer pane keeps running.
393
+ The coms pool panel remains at the **bottom of the Fleet Dashboard**.
394
+
395
+ ### Work Mode picker
396
+
397
+ Press **`Alt+M`** or run **`/af-work-mode`** to open the work mode picker:
398
+ **operator** (direct tools) or **orchestrator** (delegate-only). Arrow keys move, Enter applies,
399
+ and Esc cancels with no change. Switching to Orchestrator with no agents auto-loads the first valid
400
+ configured team. On macOS, the outer
401
+ terminal must send Option as Meta or Alt+M will not reach the Hub.
402
+
403
+ ### Fleet Dashboard and detail
404
+
405
+ Press **`Alt+A`** or run **`/af-agents-list`** to open the full-screen **Fleet Dashboard**. It is a
406
+ live overlay backed by the same fleet source as the compact widget and lists specialists, true nested
407
+ delegates, running research helpers, and coms peers. Dashboard filtering remains independent from the
408
+ widget, and `/af-zoom` continues to use an unfiltered key lookup.
409
+ The bordered **coms** panel is pinned to the bottom of this overlay. The dashboard shows status,
410
+ hierarchy, model, context/tokens, elapsed time, tool count, and recent work; its summary counts
411
+ running/done/failed rows, overlap-aware wall time, and visible token totals. Finished/idle/stale
412
+ rows are hidden by default.
413
+
414
+ - **`↑`/`↓`** or **`j`/`k`** selects a row; **`PgUp`/`PgDn`** pages; **Enter** opens its full-screen
415
+ detail view. **`h`** opens the same history overlay as `/af-agents-history` (Esc/`q` returns to the dashboard).
416
+ - **`f`** starts a name/model/recent-work filter; type the query and press **Enter** to apply it, or
417
+ **Esc** to clear it. **`a`** toggles finished rows.
418
+ - **`x`** requests a kill and **`r`** requests a restart; press the same key again within two seconds
419
+ to confirm. Kill acts on a local running specialist, a coms-backed specialist, or a research helper.
420
+ Confirmed restart terminates a running specialist when necessary, clears its session, and re-dispatches
421
+ its previous task fresh; it is refused for peer/delegate/research rows and rows with no previous task.
422
+ If a research detail view is already open when that helper finishes, it stays as a read-only terminal
423
+ snapshot until Esc; returning to the dashboard shows no completed research row.
424
+ - **`q`** or **Esc** closes the dashboard.
425
+
426
+ The detail view streams the selected local agent's assistant text, provider-emitted thinking, tool
427
+ arguments, and tool results (including success/error and duration). Normal events request an immediate
428
+ render; a 2-second ticker recovers missed file notifications and advances elapsed time. Use **`v`** to
429
+ switch between scan-friendly **Compact** rows and wrapped **Verbose** output. The choice is preserved
430
+ while drilling into other rows in the same open dashboard.
431
+
432
+ Use **`↑`/`↓`**, **`PgUp`/`PgDn`**, and **Home**/**End** to navigate. Manual movement pauses tail-follow;
433
+ **End** restores it. **Enter** expands a selected tool row in Compact mode and **Ctrl+C** copies the
434
+ selected entry. **`m`** replaces the log area with a full-screen picker containing every model currently
435
+ reported by Pi's available-model registry. Use **`↑`/`↓`**, **`PgUp`/`PgDn`**, or **Home**/**End**, then
436
+ **Enter** to apply; **Esc** cancels back to the logs.
437
+
438
+ Each local run also writes an append-only transcript under `.pi/agent-sessions/transcripts/`. The
439
+ directory/file permissions are owner-only (0700/0600 where the platform supports them), large events
440
+ are chunked, and the live in-memory window is bounded. Common authorization headers, API keys, access
441
+ tokens, passwords, provider tokens, and private-key blocks become `[REDACTED]` **before both persistence
442
+ and display**. This is pattern-based protection, so operators should still avoid deliberately printing
443
+ unknown secret formats.
444
+
445
+ “Thinking” means only text explicitly emitted by the provider/runtime; hidden model reasoning is not
446
+ available, and personas with thinking disabled have no thinking rows. Model switching works for local
447
+ specialists, a currently running research helper, and nested delegate roles. It applies on the next dispatch or
448
+ continuation and never interrupts a running child. A coms-backed specialist stores the choice for native
449
+ fallback runs; external coms peers control their own model, have no picker, and have no local transcript.
450
+ **Esc**/**`q`** returns to the dashboard. **`/af-zoom <name|rN>`** opens this same detail view directly.
451
+
452
+ ### Version footer
453
+
454
+ `agent-hub` renders its local harness version first in its custom footer:
455
+ `agent fleet v<version> · <model><thinking> · <team>`. It replaces pi's default footer, so it does **not**
456
+ consume or render the shared version status; it reads its own adjacent stamped manifest directly.
457
+ The three persistent-UI harnesses (`agent-hub`, `coms`, and
458
+ `damage-control-continue`) still register that one shared key, which gives default footers one
459
+ version in stacked non-hub sessions. In the supported guardrail-plus-hub stack, the hub's custom
460
+ footer supplies the single visible version. Damage-Control can update its own safety status after
461
+ a violation without overwriting the shared version entry. The canonical source is the
462
+ repository-root `package.json`; the adjacent harness manifest is a synchronized stamp maintained
463
+ by `bin/sync-harness-versions.js`. Its local `version.ts` reader intentionally stays with the
464
+ harness for copied or symlinked installs, but those installs still need the pre-existing full
465
+ `.pi/harnesses/` dependency installation.
466
+
467
+ The `agent fleet` half of the label is an OSC 8 terminal hyperlink to the project homepage —
468
+ clickable in terminals that support hyperlinks, ignored (rendered as plain text) elsewhere, and
469
+ free of footer columns because pi strips OSC sequences before measuring width. It opens the
470
+ repository in a browser, not a TUI panel: pi has no mouse tracking, so a click never reaches the
471
+ harness. `AGENT_FLEET_NO_LINKS=1` restores the plain label on multiplexers that mangle OSC 8
472
+ (GNU screen, tmux before 3.4).
473
+
474
+ ### Voice dictation indicator
475
+
476
+ The custom footer renders the optional [`pi-voice-stt`](../../extensions/pi-voice-stt/README.md)
477
+ extension's recording indicator on a line **below the model line** — e.g.
478
+ `● REC 0:01 ⏎ send · esc cancel` while recording, or a `transcribing…` dot. Because agent-hub
479
+ replaces pi's built-in footer (where that indicator normally lives), it reads the extension's
480
+ `setStatus("voice-stt", …)` value via the footer data provider and surfaces it itself. The
481
+ indicator only appears once `pi-voice-stt` is installed and configured; otherwise the footer is
482
+ the single model line. Press **`Alt+S`** to start/stop dictation as in a normal pi session.
483
+
484
+ ## Configuration
485
+
486
+ At session start, `agent-hub` reads `.ai/agent-fleet-overrides.md` in the workspace. The
487
+ canonical section name is `## agent-hub` (the legacy `## agent-team` name is still accepted):
488
+
489
+ ```markdown
490
+ ## agent-hub
491
+ # Replace Bulgarian with any language name.
492
+ language: Bulgarian
493
+ ```
494
+
495
+ Omit the section to keep the default `English`. `language` applies to dispatcher replies,
496
+ `ask_user` questions and `context` fields, handoff summaries, and user-facing status text;
497
+ specialist task strings stay in English.
498
+
499
+ The same section can point the team at the project's own rule files and documentation
500
+ entry points:
501
+
502
+ ```markdown
503
+ ## agent-hub
504
+ rules: docs/rules, .ai/rules
505
+ docs: Docs/AGENTS.md, Docs/architecture/ARCHITECTURE_OVERVIEW.md
506
+ ```
507
+
508
+ `rules:` lists repo-relative folders of HOW rules — implementation patterns the work must
509
+ comply with. Resolution is **index-first**: a folder with a top-level `README.md`/`index.md`
510
+ is treated as curated — personas read the index first and follow its loading manifest
511
+ (session bundles, conditional-load lists) instead of bulk-reading the tree; a folder without
512
+ an index is searched **recursively** through all subfolders. When set, every dispatched
513
+ specialist's system prompt gains a "Project rules" block naming the folders and the
514
+ resolution order; the planner and code-reviewer personas additionally validate their subject
515
+ against the relevant rules and pass them on (cited in plan acceptance criteria / handed to
516
+ delegate sub-reviewers).
517
+
518
+ `docs:` lists repo-relative WHAT/WHY documentation entry points — canonical files (e.g. an
519
+ `AGENTS.md`, an architecture overview) or doc folders (personas start from the folder's
520
+ README/index). Docs orient rather than bind: every dispatched specialist **and every research
521
+ helper** gains a "Project docs" block telling it to read the entry points relevant to its
522
+ task and follow their links instead of bulk-reading doc trees. The code-reviewer flags
523
+ changes that alter documented behavior without a doc update; the documenter treats the entry
524
+ points and the trees they link as the documentation it maintains.
525
+
526
+ `research-keep:` is **removed**. An existing key warns at session start and has no effect; delete it.
527
+ Live research helpers disappear from the Fleet Dashboard when they finish. Session/transcript/findings
528
+ files and `/af-agents-history` records remain.
529
+
530
+ ### Bounded local-disk searches
531
+
532
+ Every `read`, `grep`, `find`, and `ls` call made by a native research helper or a nested
533
+ `delegate` child has a **parent-side** watchdog. The default is **120 seconds per tool call**;
534
+ it is a per-tool bound, not a whole-run deadline — the whole-run bound is the execution
535
+ mode's per-run deadline below. Configure it in the repository-standard overrides file:
536
+
537
+ ```markdown
538
+ ## agent-hub
539
+ recon-search-timeout-s: 120 # integer 1..3600
540
+ # recon-search-timeout-s: off # disable this per-tool watchdog
541
+ ```
542
+
543
+ Invalid values warn at session start and use 120. Calls are tracked independently by their
544
+ JSONL `toolCallId`; a repeated start/update cannot extend an existing deadline. A timeout returns
545
+ `tool_timeout` with the call metadata, ends the research/delegate lifecycle, sends SIGTERM to the
546
+ child's explicitly owned process group, then SIGKILL after a finite grace period. The parent also
547
+ has a final settlement timer, so it settles rather than waiting indefinitely for `close` or
548
+ inherited pipe drain. If child/process-group death cannot be confirmed after this bounded cleanup,
549
+ the timeout metadata reports `terminationConfirmed: false`: this prevents the parent hanging, but
550
+ may indicate an uninterruptible OS-level process that needs operator attention. This group
551
+ ownership covers descendants even when the pi leader exits first; nested delegates own their groups
552
+ and forward parent cancellation, avoiding detached-orphan processes. Caller
553
+ cancellation follows the same bounded cleanup path but is reported as `cancelled`, not
554
+ `tool_timeout`.
555
+
556
+ ### Task-tier budgets
557
+
558
+ The hub runs **per-user-turn budgets enforced in code**, not prose, keyed off the current
559
+ **task tier**. This is the guardrail against runaway orchestration (the observed failure
560
+ mode: 100+ dispatches and 100M+ tokens for one task, most of it re-billed stale specialist
561
+ context).
562
+
563
+ | Budget (per user turn) | trivial | small | feature | project |
564
+ |-----------------------------------|---------|-------|---------|---------|
565
+ | `dispatch_agent` calls | 1 | 2 | 8 | 12 |
566
+ | `spawn_research` calls | 1 | 2 | 4 | 6 |
567
+ | Turn wall clock | 15 min | 15 min| 60 min | 90 min |
568
+ | Per-run deadline (specialist/research/delegate) | 10 min | 10 min | 30 min | 30 min |
569
+ | Specialist session recycled after | 3 runs | 3 runs| 5 runs | 5 runs |
570
+ | Nested delegation | off | off | on | on |
571
+
572
+ When a budget is exhausted, the runtime pauses `dispatch_agent`/`spawn_research` and opens
573
+ one localized Yes/No confirmation through the existing `ask-user-remote` wrapper. If the wrapper
574
+ is unavailable, it uses a local dialog; without either channel it stops. **Yes** renews the budget
575
+ and continues the original operation without another model call. Concurrent refusals share one
576
+ question and one renewal. **No**, cancellation, or confirmation failure latches a task-scoped stop
577
+ and aborts the parent loop. Only the human's `/af-budget-continue` command reopens that question;
578
+ the command itself neither grants budget nor dispatches work. Prose and magic-marker tool calls
579
+ cannot authorize renewal. A normal new user message still opens a fresh turn window, but cannot
580
+ clear a declined confirmation. Time blocked in any `ask_user` question is
581
+ excluded from the turn wall clock, so a slow human answer cannot exhaust the next dispatch.
582
+ Raise the task with `set_task_tier` when the work outgrew the current envelope. Override keys
583
+ in `.ai/agent-fleet-overrides.md` are a **ceiling** (`min` with the tier); `off` stays at the
584
+ tier rather than lifting the cap. A leftover `mode:` key is ignored with a warning.
585
+
586
+ ```markdown
587
+ ## agent-hub
588
+ max-dispatches-per-turn: 8 # integer ceiling, or off (stays at the tier)
589
+ max-research-per-turn: 4 # integer ceiling, or off (stays at the tier)
590
+ turn-wall-time-s: 3600 # integer ceiling, or off (stays at the tier)
591
+ agent-turn-timeout-s: 1800 # whole-run deadline per spawned run; integer or off
592
+ session-recycle-runs: 5 # recycle a specialist session after N resumed runs; integer or off
593
+ run-history-keep: 10 # previous sessions' artifact archives to retain; integer or off
594
+ ```
595
+
596
+ #### Task budget (the bound a turn window cannot provide)
597
+
598
+ A per-message allowance cannot bound a task. In the run this guardrail comes from, every
599
+ steering message opened a fresh window of 8 dispatches and 60 minutes, so no counter ever
600
+ bound: one workspace stayed open **47 hours**, while the same change made in a narrow
601
+ workspace took **13 minutes**.
602
+
603
+ So there is a second envelope, **`TASK_BUDGET_MULTIPLIER` (3) × the turn envelope**, whose
604
+ counters are **not** reset by a user message:
605
+
606
+ | | per turn (`feature`) | per task |
607
+ |---|---|---|
608
+ | `dispatch_agent` | 8 | 24 |
609
+ | `spawn_research` | 4 | 12 |
610
+ | clock | 60 min wall | 180 min **active** |
611
+
612
+ Exhausting it is a **hard stop**: the refusal says so, and another user message does not
613
+ reopen it. The hub asks one localized Yes/No `ask_user` question. **Yes** opens one audited
614
+ continuation tranche and resumes directly; it resets the task dispatch/research counters,
615
+ active-time clock, review allowance, and the current turn budget while preserving the task
616
+ tier, assertion ledger, capability packs, label, blockers, and accumulated progress. **No**
617
+ (or cancellation) stops. Each accepted tranche appends `agent-hub-budget-continuation` with
618
+ bounded prior usage, allowlisted process/session/pane identity, and runtime task/tranche/request
619
+ correlation. A reset invalidates pending answers; late or repeated answers cannot renew another task.
620
+ `/af-poll` and `/af-debate` use the same runtime confirmation gate for task and turn budgets.
621
+
622
+ `set_task_tier` with `new_task: true` remains the lifecycle action for genuinely different work.
623
+ It clears task identity/state as well as counters and appends an `agent-hub-task-reset` audit
624
+ entry. Do not use it merely to continue the same task. The status chip still shows both turn and
625
+ task usage (`… · task 4/18`).
626
+
627
+ The reasoning: three full envelopes still require an explicit human decision, but that decision
628
+ is now a single confirmation rather than a fake new task followed by a second message.
629
+
630
+ Both turn and task clocks charge **active time only** — turns that actually ran, minus the
631
+ time the dispatcher sat blocked on `ask_user`. Inter-turn idle costs nothing, because no turn
632
+ is open across it. Raw wall clock would bill a lunch break, an overnight pause, and every long
633
+ human answer against the task; at `fast` mode's 45-minute envelope a coffee break would
634
+ hard-stop a task with two dispatches spent. A false stop is worse than no stop — it teaches
635
+ people to reset the task window reflexively, and that reset is the one thing that has to
636
+ stay deliberate. Dispatch and research counts remain the honest hard stops.
637
+
638
+ The **auto-research pipe** (specialist emits `NEEDS_RESEARCH`, the hub fans out read-only
639
+ helpers in code) stays exempt from the TURN budget — it is hub mechanics, not a dispatcher
640
+ decision, and it must not steal the dispatcher's slots — but it **is** charged against the
641
+ task envelope. At 2 rounds × 4 questions per dispatch and 18 dispatches per task, leaving it
642
+ uncounted would have put 144 research runs inside the bound that is supposed to be the outer
643
+ one. When the task's research envelope is spent the pipe does not spawn and the specialist is
644
+ not resumed; the dispatch result says so.
645
+
646
+ Two related always-on behaviors: specialist **context pressure is measured over
647
+ input + cacheRead + cacheWrite** (resumed sessions re-send their whole accumulated context
648
+ as cache reads — counting `input` alone hid that entirely), and a specialist session is
649
+ **recycled** (fresh session, no `-c` resume) once it has served `session-recycle-runs` runs
650
+ or its measured context passes 60%. The dispatch result notes the recycle so the dispatcher
651
+ knows the specialist starts without session memory — task text and `artifacts:` paths must
652
+ carry the state, which the deliverable-to-file protocol already ensures.
653
+
654
+ Context is measured against **that agent's own** model window, resolved from pi's model
655
+ registry (`ctx.modelRegistry.find`) with the source recorded on every resolution. Dividing a
656
+ 49k local model's usage by the dispatcher's window is what produced unactionable readings
657
+ like `⚠ Planner context at 315%`; a reading above 100% now emits a one-time diagnostic that
658
+ names the window and where the number came from, so a mis-resolved window is distinguishable
659
+ from a genuine overflow. Two recycle rules follow from it: a session at or past a **full**
660
+ window is recycled unconditionally (no threshold override keeps it alive), and a resumed
661
+ session whose *projected* prompt — prior tokens plus this task — would overflow is recycled
662
+ **before** the spawn instead of after the run.
663
+
664
+ #### Per-provider concurrency
665
+
666
+ A dispatch may fan out to four delegate children at once and several specialists can be
667
+ mid-run, with nothing bounding how many requests land on one provider. That is fine against
668
+ a hosted endpoint and not against a local one. Requests are capped per process — **2 in
669
+ flight for `custom/*` and `omlx/*` by default, unlimited elsewhere**:
670
+
671
+ ```bash
672
+ AGENT_HUB_PROVIDER_LIMITS="custom=4" # raise the local cap
673
+ AGENT_HUB_PROVIDER_LIMITS="custom=off" # disable it
674
+ AGENT_HUB_PROVIDER_LIMITS="custom=2,ollama=1"
675
+ ```
676
+
677
+ Queued runs still execute — they wait for a permit, and the wait is announced rather than
678
+ looking like a hang. The cap applies per **level** of the delegation tree (each pi process
679
+ runs its own semaphore over the children it spawns), and a nested spawn reuses its parent's
680
+ permit, so a child can never wait on its own ancestor. The drift judge and the return
681
+ extractor are deliberately ungated: both run while a specialist holds a permit, so queueing
682
+ them behind it would stall the watchdog meant to stop it.
683
+
684
+ The per-run deadline lands as `turn_timeout` (exit 124) with partial output preserved, for
685
+ dispatched specialists, research helpers, and nested delegate children alike — a hung child
686
+ can no longer hold its parent for hours.
687
+
688
+ ### Task triage (complexity tiers)
689
+
690
+ The dispatcher classifies the current TASK with the `set_task_tier` tool BEFORE its first
691
+ dispatch — `trivial` / `small` / `feature` / `project` — and that classification *is* the
692
+ budget envelope (see the table above). The tier shows in the `hub-tier` status chip
693
+ (`Tier: small · …`), with a trailing `?` while it is only assumed.
694
+
695
+ Skipping the call makes the hub assume **`small`**, not `feature`. Because the tier is
696
+ task-scoped, a skipped triage latches for the whole task — and skipped triage is precisely
697
+ the case where the dispatcher was not thinking about proportionality. Assuming `feature`
698
+ there would unlock planner/plan-reviewer/security-auditor, loosen the review caps, and hand
699
+ out the full feature envelope: the over-apparatus failure mode, granted by forgetting a tool
700
+ call. Assuming `small` costs one explicit escalation when the work really is bigger, which
701
+ is the cheap direction to be wrong in. An assumed tier is not a ratchet baseline either: the
702
+ dispatcher's own first `set_task_tier` is treated as an initial declaration, so it never
703
+ needs a `reason` it had no way to know it needed.
704
+
705
+ The tier is **task-scoped and ratcheted**. It survives the user's next message, and it
706
+ moves in one direction cheaply: **lowering it is always free, raising it requires a
707
+ `reason`** naming what the ask turned out to contain (refused in code otherwise). A
708
+ turn-scoped tier could not bind on a steered run — every correction reset it to null, the
709
+ next dispatch re-assumed `feature`, and the effective tier drifted to the ceiling, because
710
+ nobody ever re-declares `trivial` after a steering message.
711
+
712
+ Three guards are enforced in code, not prose:
713
+
714
+ - **Duplicate-dispatch guard** — refuses re-dispatching the same agent with a
715
+ near-identical task inside one turn.
716
+ - **Tier persona gate** — at `trivial`/`small`, `dispatch_agent`/`spawn_research` refuse
717
+ `planner`, `plan-reviewer`, `architect`, `security-auditor` and `deep-researcher`
718
+ (`run-budget.js`). Each opens a document/finding loop whose output then has to be
719
+ executed and re-reviewed; the escape hatch is raising the tier *with a reason*, not a
720
+ flag. The refusal costs no budget slot.
721
+ - **Review round cap** — review dispatches per TASK are capped by tier (trivial/small 1,
722
+ feature 2, project uncapped) and the (N+1)-th is refused without spending a budget slot.
723
+ This is where the review ratchet is actually cut: findings become requirements and the
724
+ enlarged requirement set justifies the next round, so the round is the thing to bound.
725
+ - **Review finding budget** — a review persona's dispatch carries a blocking-finding cap
726
+ tied to the tier (trivial 1, small 2, feature 5, project uncapped) plus the rule that a
727
+ blocking finding may only enforce an invariant the task/plan/rules already state. The hub
728
+ **counts** what came back (`review-findings.js`) and appends a visible notice when the
729
+ return exceeds the cap — it never reclassifies a finding. No rule the hub can evaluate
730
+ distinguishes "invents a manifest nobody asked for" from "this logs a connection string";
731
+ both are a heading and a bullet, and silently demoting the second by position would, on
732
+ the day it matters, move a real security finding into the section nobody acts on.
733
+
734
+ Every budget/gate refusal is counted in `/af-hub-report`.
735
+
736
+ ### Docs lane (`docs-lane.js`)
737
+
738
+ A dispatch whose declared `scope` is documentation only — `Docs/**`, `**/*.md`,
739
+ `artifacts/evidence/*.png`, `.changeset/**` — runs in the single-worker docs lane:
740
+
741
+ - dispatching a review persona (`code-reviewer`, `plan-reviewer`, `security-auditor`,
742
+ `test-engineer`) on it is **refused** and costs no budget slot;
743
+ - any other persona's result carries a note telling the dispatcher not to open a review
744
+ gate for it.
745
+
746
+ An absent or empty `scope` is never the lighter lane — unknown is not docs. The refusal is
747
+ overridable per dispatch with `review_reason: "<why>"` for the cases that do warrant a gate
748
+ (the doc publishes a credential, or states a contract other systems depend on).
749
+
750
+ ### External-blocker stop (`external-blocker.js`)
751
+
752
+ A specialist that cannot proceed without something outside the fleet's reach — an account,
753
+ a permission, a deployment credential, a telemetry destination, a console-only action —
754
+ emits `EXTERNAL_BLOCKED: <what is missing, who owns it, what it blocks>` (the protocol is
755
+ injected into every specialist prompt). The hub records it and **refuses the next
756
+ dispatch/research** with an owner-escalation packet: what is missing and who owns it, which
757
+ assertions are blocked, what is already proven and where, and the human's options (provide
758
+ access / waive as UNPROVEN / drop from scope).
759
+
760
+ The gate opens when the human has been addressed — an `ask_user` call, or the next user
761
+ message. Without `ask_user` installed it fires exactly once, so a session that cannot reach
762
+ the human can still finish and report instead of deadlocking.
763
+
764
+ This exists because the alternative is the most expensive failure mode observed: with no
765
+ correlation destination available, a run kept substituting internal work for the missing
766
+ external fact — scripts, manifests, fixtures, diagnostic packets — for hours, and the
767
+ assertion still ended UNPROVEN.
768
+
769
+ ### Immutable per-run artifact namespaces (`run-namespace.js`)
770
+
771
+ Session start used to `rm -rf` `.pi/agent-sessions/artifacts/`, and specialist returns were
772
+ named by a per-session counter (`returns/builder-run1.md`). Both halves of that failed at
773
+ once: the next session's `builder-run1.md` claimed the same path as the previous one's, and
774
+ the wipe deleted the originals first — a post-mortem had to record eleven implementation
775
+ returns and two review artifacts as NOT RECOVERABLE.
776
+
777
+ Now each session **archives** the previous session's artifacts into
778
+ `.pi/agent-sessions/runs/<runId>/artifacts/` — a namespace written once and never reused —
779
+ alongside a read-only `meta.json` (run id, archive time, project, workspace, per-kind
780
+ artifact counts) and an appended `runs/index.json`. `runId` is a sortable UTC timestamp plus
781
+ a random suffix, so two sessions starting in the same second still get distinct namespaces.
782
+ Retention is `run-history-keep` (default 10, `off` keeps everything); an empty artifact tree
783
+ is not archived. If archiving fails the artifacts are **left in place** rather than deleted:
784
+ a stale tree is recoverable, a deleted one is not.
785
+
786
+ ### Drift watchdog (in-flight observation)
787
+
788
+ An armed dispatch is observed **while it runs**, from the same JSON event stream that
789
+ drives the cards — not post-hoc:
790
+
791
+ - **Layer 1 — deterministic rules, zero tokens** (`drift-watchdog.js`): a write/edit
792
+ outside the dispatch's declared `scope` globs, the identical tool call repeated 4×,
793
+ 5 consecutive failed tool calls, or 200 total tool calls in one run.
794
+ - **Layer 2 — LLM judge, escalation only**: when a rule fires (single-flight, 90 s
795
+ cooldown), a one-shot cheap run (default model: the researcher persona's; override with
796
+ `watchdog-judge-model`) reads the original task + declared scope + recent tool trail and
797
+ answers `VERDICT: ON_TRACK|DRIFTING|STUCK`. Judge failures fail open.
798
+ - **Intervention**: DRIFTING/STUCK terminates the run as **`drift_stop`** (exit 125,
799
+ partial output preserved) and the dispatch result instructs: re-dispatch ONCE with a
800
+ corrected, narrowed task — never the same task unchanged.
801
+
802
+ Enablement is dynamic. In **operator** work mode, precedence is the `watchdog: true|false`
803
+ param on a single `dispatch_agent` call → a per-agent override (`/af-watchdog builder
804
+ on|off|clear`) → the hub-wide setting (`/af-watchdog on|off|auto`, default `auto`, project
805
+ default via the `watchdog:` overrides key): `on`/`auto` arm and `off` disarms. In
806
+ **orchestrator** work mode, hub `auto`/`on` auto-arms; dispatch `watchdog: false` cannot
807
+ disarm it. Opt out with hub `/af-watchdog off` (or override `watchdog: off`), or a per-agent
808
+ `off`. Read-only research helpers are not monitored — they already run under the per-tool
809
+ watchdog + turn deadline and cannot write.
810
+
811
+ ### Dynamic teams
812
+
813
+ Rosters start from `.pi/agents/teams.yaml` but are not frozen there:
814
+
815
+ - `/af-agents-add <persona>…` / `/af-agents-drop <persona>…` — restructure the ACTIVE team
816
+ live (drop refuses running or last members; session files are kept for re-adding).
817
+ - `/af-agents-save <name>` — persist the current roster as a named team back into
818
+ `teams.yaml` (targeted block upsert; comments and other teams untouched).
819
+ - `team_adjust` — the dispatcher itself may add/drop a persona **with a stated reason**;
820
+ disabled at trivial/small tiers, capped at 8 roster members, and every change is notified to the
821
+ human. The system prompt is rebuilt each turn, so changes take effect immediately.
822
+
823
+ ### `/af-hub-report`
824
+
825
+ Per-turn cost accounting: dispatches (agent, status, elapsed, billed/output tokens),
826
+ research runs, session recycles, drift stops, and budget/duplicate refusals — for the
827
+ current turn, the last completed turn, and session totals. Billed tokens count
828
+ input + cacheRead + cacheWrite, the same measure the recycler uses.
829
+
830
+ Paths that don't exist produce a session-start warning, never an error. The full key list for
831
+ `## agent-hub` (models, sub-roles, depth budgets, persona gate, research retention, watchdog,
832
+ mode/budget keys) is documented in `docs/agent-fleet-setup.md`.
833
+
834
+ ## The coms layer
835
+
836
+ > The runtime coordination protocols this layer implements (sentinels, push over
837
+ > polling, barriers, fan-out digests, racing) are catalogued in
838
+ > [references/fleet-coordination-patterns.md](../../../references/fleet-coordination-patterns.md).
839
+
840
+ ### Fleet tools (herdr)
841
+
842
+ Inside a [herdr](https://herdr.dev) pane with a live server, the dispatcher's tool
843
+ surface additionally gets (absent otherwise, like coms):
844
+
845
+ - `herdr_spawn_peer` — stand up a constrained Fleet peer through the shared peer-launch resolver.
846
+ The peer joins **this session's `--project` pool** (the model cannot override it), and a name
847
+ declared in `.pi/agents/peers.yaml` keeps its declared `runner:`/`extensions:`/`env_file:`,
848
+ including `runner: claude-code`; undeclared explicit shapes may select a Pi persona, identity-only
849
+ Fleet Core peer, or Claude Code. Manifest-declared env is the only env admitted. The peer gets a
850
+ sibling pane in the current workspace/tab, not a second process in the Hub pane. A spawn by name
851
+ therefore produces the same declared agent as a preset launch. A persona peer **boots idle**
852
+ and does nothing until a `coms_send` reaches it, so the call waits (bounded, ~45s) for it to
853
+ register and returns `peer_ready` plus its coms name instead of a bare pane id; on failure it
854
+ returns the pane's last output, which means the peer did not start rather than that it is slow.
855
+ Peers spawned but never addressed are named at turn end and in `/af-hub-report` with a close
856
+ suggestion — closing stays the human's call.
857
+ Mechanism: herdr's `pane.split` takes **no command** — it opens a shell — so the spawn splits,
858
+ waits for the pane's prompt, and types the argv (text and Enter sent separately, because bash
859
+ bracketed paste would swallow a newline). Only `layout.apply` pane nodes carry an argv, which is
860
+ why declarative preset layouts were never affected by this.
861
+ - `herdr_spawn_pane` — create an arbitrary command pane when a constrained/addressable Fleet peer
862
+ is not the desired shape; raw commands are intentionally excluded from `herdr_spawn_peer`.
863
+ Orchestrators may use this for auxiliary processes such as watchers or servers, never to bypass
864
+ delegate-only implementation policy.
865
+ - `herdr_read_pane` — bounded `pane.read` (≤200 lines), read-to-decide on workers/tools;
866
+ messaging still goes through coms, and peer busy state comes from `coms_list`, not from
867
+ reading the screen
868
+ - `herdr_close_pane` — kills a pane; **asks the human to confirm every call**; the
869
+ bash-level `herdr pane close`/`workspace close`/`server stop` verbs are hard-blocked
870
+ for spawned specialists by `.pi/damage-control-rules.yaml`
871
+ - `herdr_notify` — desktop notification to reach the human when they are away
872
+
873
+ This closes the fleet loop: spawn a worker, watch it, notify the human, tear it down —
874
+ without leaving the session. Claude Code panes join the same pool via the
875
+ [coms bridge](../../../docs/claude-code-coms-bridge.md).
876
+
877
+ ### Presence backend (herdr or files)
878
+
879
+ Presence is pluggable, exactly as in the standalone [coms harness](../coms/README.md#presence-backends-herdr-vs-files):
880
+ inside a [herdr](https://herdr.dev) pane with a live server, the ping cycle is replaced by
881
+ push events (`agent.list` + `events.subscribe`) and the hub reports itself into the herdr
882
+ sidebar (`custom_status` = `<name> <pct>% q<depth>`); everywhere else the original 10s
883
+ ping loop runs unchanged. The file registry is written in both backends, and the
884
+ pool-scope boundary is enforced identically.
885
+
886
+ ### Identity
887
+
888
+ Each session registers a coms identity at start-up, resolved in this precedence order:
889
+
890
+ 1. **CLI flags** — `--name`, `--purpose`, `--project`, `--color`, `--explicit`
891
+ 2. **Defaults** — auto-generated name `hub-<id>`, purpose `agent-hub dispatcher`, project
892
+ `default`, a deterministic color derived from the session id
893
+
894
+ Names are de-duplicated per project (`resolveUniqueName`), so two hubs that both want `architect`
895
+ become `architect` and `architect-2`. `--explicit` marks a **private** peer — kept out of every
896
+ pool by default, so it is neither listed nor reachable until a human opts in with `/af-coms --all`
897
+ (see [Pool scope is the reach boundary](#pool-scope-is-the-reach-boundary)). The registry lives
898
+ under `~/.pi/coms/projects/<project>/agents/<name>.json` and is created at runtime.
899
+
900
+ ### Commands & tools (local dispatcher plus coms)
901
+
902
+ - `/af-coms` — coms control surface (peer list / status)
903
+ - `/af-handoff <peer>` — hand the whole session off to a coms peer (see [Handoff](#handoff))
904
+ - `/af-poll [--panel NAME] [--persona NAME] <question>` — ask every voice in a named model panel (from `.pi/agents/voices.yaml`) the same question. `--panel` wins; else `poll-panel:` in `## agent-hub`; else a refusal listing available panels. Counts as **one** turn-budget dispatch. The main loop gets an immediate `POLL STARTED` receipt (no dispatcher turn), then one `POLL VOICE` line per finished voice, then the digest. Full opinions stay on disk under `.pi/agent-sessions/artifacts/polls/<runId>/`.
905
+ - `/af-debate [--panel NAME] [--persona NAME] [--rounds N] <question>` — same panel, 2–5 harness-mediated rounds (default 3). Each surviving voice sees the labeled positions of the others from the previous round. There is no judge and no hidden merge. Counts as **one** turn-budget dispatch. Per-round files land under `.pi/agent-sessions/artifacts/polls/<runId>/debate/round-<n>/`.
906
+ - `/af-compound [focus]` — end-of-session **compound-learning pass**: the dispatcher composes a
907
+ candidate-lessons brief from the session (corrections, recurring findings, root causes),
908
+ confirms it with the user, then dispatches the `documenter` to land the approved lessons as
909
+ minimal diffs on the project's `rules:`/`docs:` targets per `skills/compound-learning/SKILL.md`.
910
+ Requires the `documenter` persona in the active team; run it before `/af-handoff` or session end.
911
+ - `coms_list` — discover the peers in your pool: names, models, live context usage, purpose,
912
+ `pane_id`, and `status` (`idle` | `working` | `booting`). Check status before sending: `working`
913
+ means your send waits behind the peer's current turn, `booting` means it is not addressable yet.
914
+ This is the field whose absence drove 127 `herdr_read_pane` calls in one session. Scoped
915
+ to your project and excluding private peers; the LLM cannot widen it (see
916
+ [Pool scope is the reach boundary](#pool-scope-is-the-reach-boundary)).
917
+ - `coms_send` — send a prompt to a peer **in your pool**; returns a `msg_id`
918
+ - `coms_await` — **block** until that `msg_id`'s reply lands (default 30 min,
919
+ `PI_COMS_TIMEOUT_MS`)
920
+ - `coms_get` — **non-blocking** poll of a `msg_id` (status `pending|complete|error`)
921
+
922
+ `/af-coms` and `/af-handoff` tab-complete live peer names **in your pool**.
923
+
924
+ ### Pool scope is the reach boundary
925
+
926
+ The set of peers shown in the pool widget is the security boundary: **a peer is reachable only if it
927
+ is in your pool.** `coms_list`, `coms_send`, and `/af-handoff` all resolve targets through the same
928
+ `peersInScope()` helper, so the dispatcher can never message a peer it cannot see. Two knobs define
929
+ the pool, and **both are human-only** — the LLM cannot widen scope to reach more peers:
930
+
931
+ - **Project** — defaults to your own `identity.project`. A human can retarget with `/af-coms --project
932
+ <name>` (one project) or `/af-coms --all` (every project). `coms_list`'s own parameters cannot
933
+ override this; an LLM request for a wider project is clamped back to the current pool and flagged.
934
+ - **Explicit (private) peers** — excluded from every pool by default. `/af-coms --all` opts them in.
935
+
936
+ This closes a cross-project leak where a peer reachable through the mesh was *not* shown in the
937
+ default project-scoped pool — so it could be messaged without being "connected." Now the reachable
938
+ set is always a subset of what the widget shows. To reach a peer outside the pool, a human widens
939
+ scope first; the dispatcher is told to **ask** rather than attempt it, and not to pass cross-project
940
+ context to a peer the human has not approved.
941
+
942
+ ### Peer as subagent
943
+
944
+ The dispatcher uses a peer as a subagent by pairing the tools: `coms_send(target, prompt)` to
945
+ issue the task, then `coms_await(msg_id)` to block for the reply (or `coms_get` to poll). This sits
946
+ alongside `dispatch_agent` — local persona specialists are dispatched as subprocesses; remote peers
947
+ are reached over coms. The two paths stay explicit for the LLM, but
948
+ [coms-backed dispatch](#coms-backed-dispatch-dispatch-policyyaml) can route a `dispatch_agent` call
949
+ to a same-name peer under the hood. (The specialist-level `delegate` tool is a third,
950
+ nested path: a dispatched specialist spawning its own declared sub-agents — it does not auto-route
951
+ between local and remote either.) Multi-hop is inherited from coms: a peer handling a dispatched task can `coms_send`
952
+ onward, hops accumulating up to `MAX_HOPS` (5).
953
+
954
+ ### Coms-backed dispatch (dispatch-policy.yaml)
955
+
956
+ `just fleet --agents <roster> --peers <preset>` boots the Hub next to standing peers from
957
+ `.pi/agents/peers.yaml` — and some
958
+ of them (e.g. `code-reviewer`, `plan-reviewer` with `runner: claude-code`) intentionally share a name
959
+ with a team member. `.pi/agents/dispatch-policy.yaml` tells the dispatcher to serve such members
960
+ **through the peer** instead of spawning a native subagent:
961
+
962
+ ```yaml
963
+ default: native # coms = substitute ANY member with a live same-name pool peer
964
+ grace_s: 30 # poll window for coms-required members
965
+ substitutions:
966
+ code-reviewer:
967
+ prefer: coms
968
+ fallback: native # none = coms-required: refuse with guidance instead of spawning
969
+ # timeout_s: 3600 # per-member reply timeout (default PI_COMS_TIMEOUT_MS, 30 min)
970
+ ```
971
+
972
+ Semantics:
973
+
974
+ - **One API with an explicit override.** `dispatch_agent(..., backend: "auto"|"native"|"coms")`
975
+ defaults to `auto`, which follows this policy. `native` always starts the local Pi specialist even
976
+ when a same-name peer is live. `coms` requires that live same-name peer and never falls back to
977
+ native. The whole downstream pipeline — structured return contract,
978
+ `ASK_USER:` extraction, the NEEDS_RESEARCH auto-research pipe, assertions, history, the grid —
979
+ consumes a coms reply exactly like a subagent's final output (the dispatch protocols ride in the
980
+ message body, since a standing peer only receives a user prompt).
981
+ - **Decided per dispatch, against the live pool.** Hub and peers boot in parallel, so the first
982
+ dispatch may land before the peer registers: with `fallback: native` it runs natively (one notice
983
+ per member per team activation), and later dispatches pick up the peer once it is live. With
984
+ `fallback: none` the dispatch polls the pool for `grace_s` seconds, then refuses with remediation
985
+ steps. The name match is scoped to the coms pool — the same security boundary as `coms_send`.
986
+ - **Standing context is the point.** Re-dispatches (ASK_USER answers, research resumes) go back to
987
+ the same peer session, so a Claude Code reviewer keeps its review context across rounds.
988
+ - **Visibility.** The member's grid card shows a `⇄coms <peer-model>` badge, history entries are
989
+ annotated `(coms)`, and `/af-dispatch-policy` prints the resolved routing per member with live-peer
990
+ status.
991
+ - **Limitations.** `/af-agents-kill` on a coms-backed run only abandons the wait — the peer keeps
992
+ running in its own pane and cannot be killed from the hub (`/af-agents-restart` abandons, then
993
+ re-dispatches). `/af-zoom` shows only the final reply (there is no stream), tool counts stay 0, and
994
+ context% is a registry snapshot. `/af-agent-model` overrides apply only to native(-fallback) runs —
995
+ the peer's model is set in `peers.yaml`.
996
+
997
+ Missing file = everything native. HOW a peer runs (persona, model, `runner: claude-code`, env) stays
998
+ in `peers.yaml`; this file only decides WHEN the hub prefers a peer over a native spawn.
999
+
1000
+ ### Handoff
1001
+
1002
+ `/af-handoff <peer>` transfers the session to another **main** agent. Following the plan's
1003
+ **decision G1**, it does *not* try to extract a compaction summary; instead it asks the dispatcher
1004
+ LLM to compose a **self-contained brief** ("everything the target needs, assume no shared history"),
1005
+ then `coms_send`s that brief to the peer, `coms_await`s the reply, and relays it back — in the
1006
+ configured user-facing language. When the handoff `coms_send` fires, the hub appends machine-generated
1007
+ sections after the LLM brief: `## Verification ledger (verbatim, machine-appended)` with every current
1008
+ assertion in canonical ledger form, and `## Artifact index` with artifact paths plus first headings.
1009
+ The target peer must treat the machine-appended ledger as the contract, not the paraphrased brief.
1010
+ The target peer takes over; the source relays the result. There is no raw session copy (pi sessions
1011
+ aren't portable between live agents). The target must be a peer in your pool — `/af-handoff` resolves
1012
+ through the same [scope boundary](#pool-scope-is-the-reach-boundary) as `coms_send`, so you cannot
1013
+ hand a session to a peer you cannot see.
1014
+
1015
+ ### Pool widget
1016
+
1017
+ A live "pool" widget lists connected peers with name, model, and live context usage, refreshed by a
1018
+ ping cycle; a keepalive cycle re-writes this session's own registry entry (and self-heals it if an
1019
+ external prune removed it). Both timers are `unref`'d so they never hold the process open.
1020
+
1021
+ ### Purpose
1022
+
1023
+ The coms identity `purpose` is the `--purpose` CLI flag when set, otherwise the default
1024
+ `agent-hub dispatcher`. There is no runtime dispatcher-persona picker.
1025
+
1026
+ ### Graceful degradation
1027
+
1028
+ If the coms socket can't bind at start-up (`comsReady` stays `false`), the session degrades to a
1029
+ local dispatcher without coms: the `coms_*` tools are withheld from `setActiveTools`, the
1030
+ `/af-handoff` command refuses with a notice, and the "Peer agents (coms)" prompt section is omitted.
1031
+ Orchestration, research helpers, and the grid keep working.
1032
+
1033
+ ### Tool surface
1034
+
1035
+ `setActiveTools` always preserves the orchestration surface and adds runtime-ready capabilities.
1036
+ Operator work mode also preserves the baseline direct/extension tools; orchestrator work mode does not.
1037
+ Coms tools are active only when coms is ready, Herdr tools only in a live Herdr pane, and `ask_user`
1038
+ only when registered. Work mode switching recomputes this list live without touching session state.
1039
+
1040
+ `set_assertions` / `update_assertion` / `get_assertions` are the always-on Verification Contract ledger tools (see
1041
+ [What it does](#what-it-does)); like `dispatch_agent` / `spawn_research` they stay on the
1042
+ orchestration surface in both work modes.
1043
+
1044
+ ## Optional Hermes local monitor transport
1045
+
1046
+ The optional monitor is an Agent Fleet-owned transport boundary, not a Hermes runtime API or a
1047
+ bundled Hermes plugin. When enabled, `agent-hub` publishes dispatcher-turn and specialist-run
1048
+ state and owns generation-safe cancellation. A separate local Hermes UI or operator client may
1049
+ consume the owner-only discovery + Unix-socket contract documented in
1050
+ [`.pi/agent-fleet/hermes/README.md`](../../agent-fleet/hermes/README.md#local-agent-hub-monitor-integration).
1051
+
1052
+ Set these before the hub starts:
1053
+
1054
+ ```bash
1055
+ export AGENT_FLEET_PROFILE_ID="approved-profile-id"
1056
+ export AGENT_FLEET_MONITOR_RUNTIME_DIR="/absolute/owner-only/runtime-root"
1057
+ ```
1058
+
1059
+ Both are required for monitor startup; the runtime root must be absolute and owner-only, and the
1060
+ profile ID must be a safe identifier. The monitor also starts only for a Herdr-backed hub with
1061
+ `HERDR_WORKSPACE_ID` and `HERDR_PANE_ID`; retain those values and `HERDR_SOCKET_PATH` in the
1062
+ standard `just fleet --agents <roster> --peers <preset>` flow. Workspace labels are display metadata, not monitor identity.
1063
+
1064
+ The live contract exposes three authenticated newline-delimited JSON requests: `snapshot`, cursor-
1065
+ based `output`, and exact-generation `cancel`. The monitor is local-only and fails closed when its
1066
+ profile discovery, lease, token, or Unix socket is unavailable. A native cancel targets only the
1067
+ matching hub-owned process generation. A coms cancel abandons the local wait only; its peer can
1068
+ continue. Neither path controls or closes a Herdr workspace/pane.
1069
+
1070
+ Example startup:
1071
+
1072
+ ```bash
1073
+ monitor_runtime="${XDG_RUNTIME_DIR:?}/agent-fleet-monitor"
1074
+ install -d -m 700 "$monitor_runtime"
1075
+ AGENT_FLEET_PROFILE_ID=dev \
1076
+ AGENT_FLEET_MONITOR_RUNTIME_DIR="$monitor_runtime" \
1077
+ just fleet --agents default --peers default
1078
+ ```
1079
+
1080
+ No Desktop/backend plugin installation is required or provided. Consumers must re-discover after
1081
+ lease or socket loss and must never persist or log the token.
1082
+
1083
+ ## Requires
1084
+
1085
+ - `.pi/agents/teams.yaml` for fixed specialist teams, the referenced persona `.md` files, and
1086
+ (strongly recommended) [`pi-ask-user`](https://github.com/edlsh/pi-ask-user).
1087
+ - `.pi/damage-control-rules.yaml` for every guarded `just fleet` Pi mode.
1088
+ - Nothing extra in-repo for coms — the peer registry lives at `~/.pi/coms/` and is created at
1089
+ runtime.
1090
+
1091
+ ## Usage
1092
+
1093
+ ```bash
1094
+ # Unified Fleet interface (Fleet Core + Agent Hub are loaded together)
1095
+ just fleet
1096
+ just fleet --work-mode operator --agents frontend --project myrepo
1097
+ just fleet --agents frontend --peers frontend --project myrepo
1098
+
1099
+ # equivalent direct guarded launch
1100
+ pi -e .pi/harnesses/damage-control-continue/index.ts -e .pi/harnesses/ask-user-remote/index.ts -e .pi/harnesses/agent-hub/index.ts
1101
+ pi -e .pi/harnesses/damage-control-continue/index.ts -e .pi/harnesses/ask-user-remote/index.ts -e .pi/harnesses/agent-hub/index.ts --name releaser --explicit
1102
+
1103
+ # direct unguarded launch, only when you intentionally want to skip damage-control
1104
+ pi -e .pi/harnesses/agent-hub/index.ts
1105
+ ```
1106
+
1107
+ Identity flags: `--name`, `--purpose`, `--project`, `--color`, `--explicit`.
1108
+
1109
+ ### Safety scope
1110
+
1111
+ `just fleet` and `just fleet --no-coms` load Fleet Core before `agent-hub`, so guardrails and `ask_user` apply
1112
+ to hub/dispatcher tool calls in that parent pi process — and because it is the *continue* variant, a
1113
+ blocked dispatcher call feeds back and the turn keeps going rather than aborting. Specialist and
1114
+ research agents are spawned as separate pi subprocesses with `--no-extensions` — but `agent-hub`
1115
+ resolves `damage-control-continue` from this session's `-e` flags, else the repo-local harness, and
1116
+ re-loads it into every native specialist, research helper, and nested delegate via explicit `-e`.
1117
+ `--no-extensions` keeps discovery off, so children never auto-load `.pi/extensions/` utilities or
1118
+ recursively re-load `agent-hub`; the explicit guardrail still checks every child's tool calls against
1119
+ `.pi/damage-control-rules.yaml`. Protected-path blocks escalate to the hub for explicit approval;
1120
+ protected deletions offer only Deny or Allow once, while inherently dangerous command patterns are
1121
+ non-exemptible. Denial or timeout blocks the call without aborting the child's turn. If continue
1122
+ cannot be resolved, dispatch is refused—children are never spawned unguarded. Research helpers are
1123
+ additionally read-only by construction. Guided setup enforces `agent-hub` ⇒
1124
+ `damage-control-continue` + `ask-user-remote`.
1125
+
1126
+ ### Related recipes
1127
+
1128
+ ```bash
1129
+ # Operator/native work without coms
1130
+ just fleet --no-coms
1131
+
1132
+ # Hub-only Herdr workspace and a combined topology
1133
+ just fleet --herdr --project af
1134
+ just fleet --agents default --peers docs --project af
1135
+ just fleet --agents default --peers docs --project af --dry-run
1136
+
1137
+ # Compatibility aliases (accepted with migration warnings)
1138
+ just fleet hub --solo
1139
+ just fleet team docs
1140
+
1141
+ # Snapshot refs / close cleanly / restore conversations
1142
+ just fleet snapshot docs
1143
+ just fleet down docs
1144
+ just fleet resume docs
1145
+ ```
1146
+
1147
+ `peers.yaml` groups reusable peers into named teams; each entry is `name` / `persona`
1148
+ (+ optional `model`). The persona's frontmatter `description`/`color` become the peer's
1149
+ coms purpose/color.
1150
+
1151
+ ## How it differs from its sources
1152
+
1153
+ - **Embedded, not stacked (decision 1).** coms is folded into this one `index.ts`; the identity
1154
+ flags are registered once. Loading `coms` as a second `-e` would double-register
1155
+ `--name/--purpose/...` and abort start-up.
1156
+ - **Single `session_start`.** coms init is folded into the former dispatcher's `session_start` and
1157
+ guarded by `if (!comsReady)`, so `/new` reuses the same peer identity (no leaked socket).
1158
+ - **Dispatcher is also a peer.** `setActiveTools` lists `coms_*` alongside `dispatch_agent` +
1159
+ `spawn_research` (+ `ask_user`); the system prompt gains a "Peer agents (coms)" section when coms
1160
+ is ready. The persona's `description` drives the coms `purpose` (decision 6 / Phase 6 peer
1161
+ mapping) instead of a static `--purpose`.
1162
+ - **`/af-handoff` uses an LLM-composed brief**, not a compaction-summary extraction (decision G1).
1163
+ - **Clean shutdown** SIGTERMs any running specialist/research children, clears the coms pool
1164
+ widget, and removes the registry entry on `session_shutdown` / SIGINT / SIGTERM.
1165
+
1166
+ ### Execution evidence isolation
1167
+
1168
+ New sessions allocate `.pi/agent-sessions/sessions/<UUID>/`; startup does not migrate,
1169
+ clear or prune legacy shared files. Each native/coms dispatch and research helper has
1170
+ a UUID and a create-exclusive `dispatches/<UUID>/request.json` / `result.json` bundle.
1171
+ Requests retain task/scope and copies of supplied input artifacts; results preserve
1172
+ output/diagnostics and transcript/session paths (`details.evidencePath`). Native
1173
+ continuation copies the previous raw session into the new dispatch, never rewrites it;
1174
+ delegation events also live under the dispatch. Counters remain UI labels, not evidence IDs.
1175
+
1176
+ `run-history-keep` keeps its configured limit, applied to **closed, fully settled new
1177
+ sessions whose owning process is gone**. Live, unfinished, pending and malformed
1178
+ namespaces are protected. A crash without a close marker is retained for manual
1179
+ inspection, not silently classified as safely deletable. Follow absolute paths from
1180
+ tool results; `artifacts/...` is a session-relative handoff alias, not a read-tool path.
1181
+
1182
+ ### No-progress stops
1183
+
1184
+ The first unchanged retry after a failed dispatch/research operation is refused across
1185
+ turns. Identity uses actor, scope, supplied artifact contents and worktree content,
1186
+ not task wording; generated runtime files are not progress. Budget renewal preserves
1187
+ the guard. New input content/scope or a genuine new task can permit work. For research
1188
+ without scope/artifacts, the guard conservatively treats the repository as its scope.
1189
+
1190
+ A human may type `/af-retry <failed-dispatchId>` to authorize exactly one retry of
1191
+ that failure. The command is audited, does not dispatch or renew budget, and stale
1192
+ IDs/prose do not authorize. Same-input concurrent operations are also refused.
1193
+
1194
+ The first unchanged refusal leaves the parent turn running so corrected inputs can
1195
+ be supplied; a second unchanged refusal stops the turn. Successful-but-unverified
1196
+ execution is **not** a no-progress failure; actual execution failure or failed
1197
+ deliverable readback is. This distinction prevents acceptance policy from blocking
1198
+ normal successful follow-up work.
1199
+
1200
+ ### Explicit delivery contract
1201
+
1202
+ `dispatch_agent` accepts `deliverables: string[]` of exact expected output files.
1203
+ The worker receives their absolute paths. The hub reads every expected file back,
1204
+ records size/hash/preview and whether it changed, retains the inspected content, and
1205
+ saves `details.assessmentPath`. Missing files, directories and unsafe symlink paths
1206
+ do not pass readback. An existing unchanged file is not attributed to this run.
1207
+
1208
+ Exit 0 returns `executionStatus: completed`, **not** acceptance. Tool status is
1209
+ `completed_unverified` or `verification_failed`; `accepted: false` and the assertion
1210
+ ledger keep semantic verification in the operator's hands. Every delivered return is
1211
+ saved even without assertion IDs. Pending peer delivery remains pending.
1212
+
1213
+ Scope roots are checked before budget confirmation/counters. Missing roots are not
1214
+ zero-match success. Set `scope_mode: create` explicitly to permit a new root. A new
1215
+ exact file in an existing directory is permitted when declared in `deliverables`;
1216
+ otherwise a missing dotted name such as `RIN.Video` is still treated as a missing
1217
+ root, not guessed to be a file. Free-form prose and XML are never executed as tools.