@chankov/agent-fleet 0.0.6 → 0.0.7

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 (419) hide show
  1. package/.claude/commands/set-hermes-watchdog.md +6 -0
  2. package/.opencode/commands/af-set-hermes-watchdog.md +6 -0
  3. package/.pi/harnesses/agent-hub/README.md +75 -16
  4. package/.pi/harnesses/agent-hub/artifacts.js +56 -2
  5. package/.pi/harnesses/agent-hub/assertion-ledger.js +58 -0
  6. package/.pi/harnesses/agent-hub/context-window.js +106 -0
  7. package/.pi/harnesses/agent-hub/delegate.ts +58 -9
  8. package/.pi/harnesses/agent-hub/drift-watchdog.js +54 -8
  9. package/.pi/harnesses/agent-hub/helpers.ts +34 -0
  10. package/.pi/harnesses/agent-hub/index.ts +723 -159
  11. package/.pi/harnesses/agent-hub/monitor-invoke-journal.ts +131 -0
  12. package/.pi/harnesses/agent-hub/monitor-invoke.ts +92 -0
  13. package/.pi/harnesses/agent-hub/monitor-lifecycle.ts +2 -2
  14. package/.pi/harnesses/agent-hub/monitor-session-bridge.ts +257 -11
  15. package/.pi/harnesses/agent-hub/package.json +1 -1
  16. package/.pi/harnesses/agent-hub/provider-semaphore.js +138 -0
  17. package/.pi/harnesses/agent-hub/return-contract.js +78 -0
  18. package/.pi/harnesses/agent-hub/return-extract.js +75 -0
  19. package/.pi/harnesses/agent-hub/run-budget.js +29 -3
  20. package/.pi/harnesses/agent-hub/session-health.js +110 -0
  21. package/.pi/harnesses/agent-hub/spawn.ts +109 -1
  22. package/.pi/harnesses/agent-hub/spawned-peers.js +74 -0
  23. package/.pi/harnesses/coms/README.md +4 -3
  24. package/.pi/harnesses/coms/index.ts +80 -58
  25. package/.pi/harnesses/coms/package.json +1 -1
  26. package/.pi/harnesses/damage-control-continue/package.json +1 -1
  27. package/.pi/harnesses/lib/coms-registry-entry.ts +94 -0
  28. package/.pi/harnesses/lib/herdr-client.ts +7 -2
  29. package/.pi/harnesses/lib/herdr-presence.ts +141 -30
  30. package/.pi/harnesses/lib/hermes-monitor-events.ts +136 -0
  31. package/.pi/harnesses/lib/hermes-monitor-model.ts +9 -0
  32. package/.pi/harnesses/lib/hermes-monitor-registry.ts +1 -1
  33. package/.pi/harnesses/lib/hermes-monitor-socket.ts +47 -2
  34. package/.pi/prompts/af-set-hermes-watchdog.md +6 -0
  35. package/.versions/0.0.7/.claude/commands/build.md +44 -0
  36. package/.versions/0.0.7/.claude/commands/code-simplify.md +22 -0
  37. package/.versions/0.0.7/.claude/commands/design-agent.md +14 -0
  38. package/.versions/0.0.7/.claude/commands/doctor-agent-fleet.md +17 -0
  39. package/.versions/0.0.7/.claude/commands/orchestrate.md +112 -0
  40. package/.versions/0.0.7/.claude/commands/plan.md +16 -0
  41. package/.versions/0.0.7/.claude/commands/prime.md +22 -0
  42. package/.versions/0.0.7/.claude/commands/review.md +16 -0
  43. package/.versions/0.0.7/.claude/commands/set-hermes-telegram.md +15 -0
  44. package/.versions/0.0.7/.claude/commands/set-hermes-watchdog.md +6 -0
  45. package/.versions/0.0.7/.claude/commands/setup-agent-fleet.md +25 -0
  46. package/.versions/0.0.7/.claude/commands/ship.md +72 -0
  47. package/.versions/0.0.7/.claude/commands/spec.md +15 -0
  48. package/.versions/0.0.7/.claude/commands/test.md +19 -0
  49. package/.versions/0.0.7/.claude/commands/webperf.md +32 -0
  50. package/.versions/0.0.7/.claude/orchestrate-teams.yaml +24 -0
  51. package/.versions/0.0.7/.opencode/commands/af-build.md +17 -0
  52. package/.versions/0.0.7/.opencode/commands/af-code-simplify.md +16 -0
  53. package/.versions/0.0.7/.opencode/commands/af-compound.md +16 -0
  54. package/.versions/0.0.7/.opencode/commands/af-design-agent.md +15 -0
  55. package/.versions/0.0.7/.opencode/commands/af-doctor-agent-fleet.md +17 -0
  56. package/.versions/0.0.7/.opencode/commands/af-orchestrate.md +112 -0
  57. package/.versions/0.0.7/.opencode/commands/af-plan.md +16 -0
  58. package/.versions/0.0.7/.opencode/commands/af-prime.md +22 -0
  59. package/.versions/0.0.7/.opencode/commands/af-review.md +15 -0
  60. package/.versions/0.0.7/.opencode/commands/af-set-hermes-telegram.md +15 -0
  61. package/.versions/0.0.7/.opencode/commands/af-set-hermes-watchdog.md +6 -0
  62. package/.versions/0.0.7/.opencode/commands/af-setup-agent-fleet.md +15 -0
  63. package/.versions/0.0.7/.opencode/commands/af-ship.md +16 -0
  64. package/.versions/0.0.7/.opencode/commands/af-spec.md +16 -0
  65. package/.versions/0.0.7/.opencode/commands/af-test.md +21 -0
  66. package/.versions/0.0.7/.opencode/commands/af-webperf.md +32 -0
  67. package/.versions/0.0.7/.opencode/orchestrate-teams.yaml +24 -0
  68. package/.versions/0.0.7/.pi/agents/dispatch-policy.yaml +32 -0
  69. package/.versions/0.0.7/.pi/agents/model-profiles.yaml +20 -0
  70. package/.versions/0.0.7/.pi/agents/peers.yaml +146 -0
  71. package/.versions/0.0.7/.pi/agents/teams.yaml +39 -0
  72. package/.versions/0.0.7/.pi/damage-control-rules.yaml +297 -0
  73. package/.versions/0.0.7/.pi/extensions/agent-fleet-update-check/README.md +58 -0
  74. package/.versions/0.0.7/.pi/extensions/agent-fleet-update-check/index.ts +161 -0
  75. package/.versions/0.0.7/.pi/extensions/agent-fleet-update-check/package.json +6 -0
  76. package/.versions/0.0.7/.pi/extensions/btw/README.md +118 -0
  77. package/.versions/0.0.7/.pi/extensions/btw/index.ts +917 -0
  78. package/.versions/0.0.7/.pi/extensions/btw/package.json +6 -0
  79. package/.versions/0.0.7/.pi/extensions/btw/state.js +179 -0
  80. package/.versions/0.0.7/.pi/extensions/chrome-devtools-mcp/README.md +58 -0
  81. package/.versions/0.0.7/.pi/extensions/chrome-devtools-mcp/index.ts +93 -0
  82. package/.versions/0.0.7/.pi/extensions/chrome-devtools-mcp/package.json +6 -0
  83. package/.versions/0.0.7/.pi/extensions/compact-and-continue/README.md +42 -0
  84. package/.versions/0.0.7/.pi/extensions/compact-and-continue/index.ts +120 -0
  85. package/.versions/0.0.7/.pi/extensions/compact-and-continue/package.json +6 -0
  86. package/.versions/0.0.7/.pi/extensions/mcp-bridge/README.md +46 -0
  87. package/.versions/0.0.7/.pi/extensions/mcp-bridge/index.ts +206 -0
  88. package/.versions/0.0.7/.pi/extensions/mcp-bridge/package.json +6 -0
  89. package/.versions/0.0.7/.pi/extensions/package-lock.json +1143 -0
  90. package/.versions/0.0.7/.pi/extensions/package.json +9 -0
  91. package/.versions/0.0.7/.pi/extensions/pi-voice-stt/README.md +201 -0
  92. package/.versions/0.0.7/.pi/extensions/pi-voice-stt/config.ts +198 -0
  93. package/.versions/0.0.7/.pi/extensions/pi-voice-stt/examples/stt.json +35 -0
  94. package/.versions/0.0.7/.pi/extensions/pi-voice-stt/index.ts +248 -0
  95. package/.versions/0.0.7/.pi/extensions/pi-voice-stt/package.json +6 -0
  96. package/.versions/0.0.7/.pi/extensions/pi-voice-stt/providers.ts +214 -0
  97. package/.versions/0.0.7/.pi/extensions/pi-voice-stt/recorder.ts +158 -0
  98. package/.versions/0.0.7/.pi/harnesses/agent-hub/README.md +857 -0
  99. package/.versions/0.0.7/.pi/harnesses/agent-hub/access-approval.ts +135 -0
  100. package/.versions/0.0.7/.pi/harnesses/agent-hub/artifacts.js +146 -0
  101. package/.versions/0.0.7/.pi/harnesses/agent-hub/assertion-ledger.js +58 -0
  102. package/.versions/0.0.7/.pi/harnesses/agent-hub/backend-policy.js +153 -0
  103. package/.versions/0.0.7/.pi/harnesses/agent-hub/context-window.js +106 -0
  104. package/.versions/0.0.7/.pi/harnesses/agent-hub/delegate.ts +435 -0
  105. package/.versions/0.0.7/.pi/harnesses/agent-hub/drift-watchdog.js +211 -0
  106. package/.versions/0.0.7/.pi/harnesses/agent-hub/evidence-rules.js +96 -0
  107. package/.versions/0.0.7/.pi/harnesses/agent-hub/footer.ts +29 -0
  108. package/.versions/0.0.7/.pi/harnesses/agent-hub/helpers.ts +248 -0
  109. package/.versions/0.0.7/.pi/harnesses/agent-hub/index.ts +8609 -0
  110. package/.versions/0.0.7/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
  111. package/.versions/0.0.7/.pi/harnesses/agent-hub/monitor-invoke-journal.ts +131 -0
  112. package/.versions/0.0.7/.pi/harnesses/agent-hub/monitor-invoke.ts +92 -0
  113. package/.versions/0.0.7/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
  114. package/.versions/0.0.7/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
  115. package/.versions/0.0.7/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
  116. package/.versions/0.0.7/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
  117. package/.versions/0.0.7/.pi/harnesses/agent-hub/monitor-session-bridge.ts +257 -0
  118. package/.versions/0.0.7/.pi/harnesses/agent-hub/package.json +7 -0
  119. package/.versions/0.0.7/.pi/harnesses/agent-hub/provider-semaphore.js +138 -0
  120. package/.versions/0.0.7/.pi/harnesses/agent-hub/research-retention.js +34 -0
  121. package/.versions/0.0.7/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
  122. package/.versions/0.0.7/.pi/harnesses/agent-hub/return-contract.js +293 -0
  123. package/.versions/0.0.7/.pi/harnesses/agent-hub/return-extract.js +75 -0
  124. package/.versions/0.0.7/.pi/harnesses/agent-hub/run-budget.js +181 -0
  125. package/.versions/0.0.7/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
  126. package/.versions/0.0.7/.pi/harnesses/agent-hub/scope-gate.js +103 -0
  127. package/.versions/0.0.7/.pi/harnesses/agent-hub/session-health.js +110 -0
  128. package/.versions/0.0.7/.pi/harnesses/agent-hub/spawn.ts +354 -0
  129. package/.versions/0.0.7/.pi/harnesses/agent-hub/spawned-peers.js +74 -0
  130. package/.versions/0.0.7/.pi/harnesses/agent-hub/version.ts +18 -0
  131. package/.versions/0.0.7/.pi/harnesses/ask-user-remote/README.md +19 -0
  132. package/.versions/0.0.7/.pi/harnesses/ask-user-remote/index.ts +321 -0
  133. package/.versions/0.0.7/.pi/harnesses/ask-user-remote/race-core.js +106 -0
  134. package/.versions/0.0.7/.pi/harnesses/coms/README.md +93 -0
  135. package/.versions/0.0.7/.pi/harnesses/coms/index.ts +1767 -0
  136. package/.versions/0.0.7/.pi/harnesses/coms/package.json +7 -0
  137. package/.versions/0.0.7/.pi/harnesses/coms/version.ts +18 -0
  138. package/.versions/0.0.7/.pi/harnesses/damage-control-continue/README.md +117 -0
  139. package/.versions/0.0.7/.pi/harnesses/damage-control-continue/index.ts +536 -0
  140. package/.versions/0.0.7/.pi/harnesses/damage-control-continue/package.json +7 -0
  141. package/.versions/0.0.7/.pi/harnesses/damage-control-continue/version.ts +18 -0
  142. package/.versions/0.0.7/.pi/harnesses/lib/coms-registry-entry.ts +94 -0
  143. package/.versions/0.0.7/.pi/harnesses/lib/damage-control-shared.ts +197 -0
  144. package/.versions/0.0.7/.pi/harnesses/lib/herdr-client.ts +463 -0
  145. package/.versions/0.0.7/.pi/harnesses/lib/herdr-presence.ts +399 -0
  146. package/.versions/0.0.7/.pi/harnesses/lib/hermes-monitor-events.ts +136 -0
  147. package/.versions/0.0.7/.pi/harnesses/lib/hermes-monitor-herdr.ts +28 -0
  148. package/.versions/0.0.7/.pi/harnesses/lib/hermes-monitor-model.ts +18 -0
  149. package/.versions/0.0.7/.pi/harnesses/lib/hermes-monitor-registry.ts +6 -0
  150. package/.versions/0.0.7/.pi/harnesses/lib/hermes-monitor-socket.ts +163 -0
  151. package/.versions/0.0.7/.pi/harnesses/lib/hermes-monitor-store.ts +31 -0
  152. package/.versions/0.0.7/.pi/harnesses/package-lock.json +35 -0
  153. package/.versions/0.0.7/.pi/harnesses/package.json +9 -0
  154. package/.versions/0.0.7/.pi/prompts/af-build.md +24 -0
  155. package/.versions/0.0.7/.pi/prompts/af-code-simplify.md +22 -0
  156. package/.versions/0.0.7/.pi/prompts/af-doctor-agent-fleet.md +15 -0
  157. package/.versions/0.0.7/.pi/prompts/af-plan.md +16 -0
  158. package/.versions/0.0.7/.pi/prompts/af-review.md +16 -0
  159. package/.versions/0.0.7/.pi/prompts/af-set-hermes-telegram.md +15 -0
  160. package/.versions/0.0.7/.pi/prompts/af-set-hermes-watchdog.md +6 -0
  161. package/.versions/0.0.7/.pi/prompts/af-setup-agent-fleet.md +27 -0
  162. package/.versions/0.0.7/.pi/prompts/af-ship.md +17 -0
  163. package/.versions/0.0.7/.pi/prompts/af-spec.md +15 -0
  164. package/.versions/0.0.7/.pi/prompts/af-test.md +19 -0
  165. package/.versions/0.0.7/.pi/skills/bowser/SKILL.md +145 -0
  166. package/.versions/0.0.7/.version +1 -0
  167. package/.versions/0.0.7/agents/architect.md +23 -0
  168. package/.versions/0.0.7/agents/bowser.md +26 -0
  169. package/.versions/0.0.7/agents/builder.md +53 -0
  170. package/.versions/0.0.7/agents/code-reviewer.md +205 -0
  171. package/.versions/0.0.7/agents/deep-researcher.md +31 -0
  172. package/.versions/0.0.7/agents/documenter.md +18 -0
  173. package/.versions/0.0.7/agents/orchestrator.md +65 -0
  174. package/.versions/0.0.7/agents/plan-reviewer.md +60 -0
  175. package/.versions/0.0.7/agents/planner.md +69 -0
  176. package/.versions/0.0.7/agents/releaser.md +24 -0
  177. package/.versions/0.0.7/agents/researcher.md +28 -0
  178. package/.versions/0.0.7/agents/security-auditor.md +166 -0
  179. package/.versions/0.0.7/agents/test-engineer.md +151 -0
  180. package/.versions/0.0.7/agents/web-debugger.md +42 -0
  181. package/.versions/0.0.7/agents/web-performance-auditor.md +192 -0
  182. package/.versions/0.0.7/codex/CONDUCTOR.md +148 -0
  183. package/.versions/0.0.7/docs/ARCHITECTURE.md +262 -0
  184. package/.versions/0.0.7/docs/agent-fleet-setup.md +366 -0
  185. package/.versions/0.0.7/docs/claude-code-coms-bridge.md +109 -0
  186. package/.versions/0.0.7/docs/codex-remote-conductor.md +170 -0
  187. package/.versions/0.0.7/docs/coms-hermes-bridge.md +189 -0
  188. package/.versions/0.0.7/docs/getting-started.md +231 -0
  189. package/.versions/0.0.7/docs/npm-install.md +337 -0
  190. package/.versions/0.0.7/docs/opencode-setup.md +249 -0
  191. package/.versions/0.0.7/docs/pi-extensions.md +293 -0
  192. package/.versions/0.0.7/docs/pi-setup.md +476 -0
  193. package/.versions/0.0.7/docs/skill-anatomy.md +150 -0
  194. package/.versions/0.0.7/hermes/README.md +347 -0
  195. package/.versions/0.0.7/hermes/desktop-plugins/agent-fleet-herdr/plugin.js +1291 -0
  196. package/.versions/0.0.7/hermes/desktop-plugins/agent-fleet-herdr/presentation.js +672 -0
  197. package/.versions/0.0.7/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
  198. package/.versions/0.0.7/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
  199. package/.versions/0.0.7/hermes/gates/gate-o-capability.md +8 -0
  200. package/.versions/0.0.7/hermes/gates/gate-o-validator-fixtures.json +1 -0
  201. package/.versions/0.0.7/hermes/plugins/agent-fleet-herdr/dashboard/activity.py +770 -0
  202. package/.versions/0.0.7/hermes/plugins/agent-fleet-herdr/dashboard/coms_registry.py +134 -0
  203. package/.versions/0.0.7/hermes/plugins/agent-fleet-herdr/dashboard/coms_send.py +350 -0
  204. package/.versions/0.0.7/hermes/plugins/agent-fleet-herdr/dashboard/herdr_source.py +193 -0
  205. package/.versions/0.0.7/hermes/plugins/agent-fleet-herdr/dashboard/manifest.json +4 -0
  206. package/.versions/0.0.7/hermes/plugins/agent-fleet-herdr/dashboard/plugin_api.py +444 -0
  207. package/.versions/0.0.7/hermes/plugins/agent-fleet-herdr/dashboard/sessions.py +205 -0
  208. package/.versions/0.0.7/hermes/plugins/agent-fleet-herdr/dashboard/tasks.py +300 -0
  209. package/.versions/0.0.7/hermes/plugins/agent-fleet-herdr/dashboard/watch.py +819 -0
  210. package/.versions/0.0.7/hermes/plugins/agent-fleet-herdr/plugin.yaml +8 -0
  211. package/.versions/0.0.7/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +139 -0
  212. package/.versions/0.0.7/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
  213. package/.versions/0.0.7/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
  214. package/.versions/0.0.7/hermes/skills/hub-conductor/SKILL.md +84 -0
  215. package/.versions/0.0.7/hermes/skills/hub-liaison/SKILL.md +84 -0
  216. package/.versions/0.0.7/hermes/skills/hub-watchdog/SKILL.md +76 -0
  217. package/.versions/0.0.7/hermes/skills/hub-watchdog/manifest.json +1 -0
  218. package/.versions/0.0.7/hermes/skills/hub-watchdog/scripts/watchdog.py +249 -0
  219. package/.versions/0.0.7/hermes/skills/hub-watchdog/scripts/watchdog_actions.py +124 -0
  220. package/.versions/0.0.7/hermes/skills/hub-watchdog/scripts/watchdog_contract.py +76 -0
  221. package/.versions/0.0.7/hermes/skills/hub-watchdog/scripts/watchdog_delivery.py +10 -0
  222. package/.versions/0.0.7/hermes/skills/hub-watchdog/scripts/watchdog_engine.py +128 -0
  223. package/.versions/0.0.7/hermes/skills/hub-watchdog/scripts/watchdog_judgment.py +41 -0
  224. package/.versions/0.0.7/hermes/skills/hub-watchdog/scripts/watchdog_recovery.py +103 -0
  225. package/.versions/0.0.7/hermes/skills/hub-watchdog/scripts/watchdog_state.py +163 -0
  226. package/.versions/0.0.7/hermes/skills/hub-watchdog/scripts/watchdog_transport.py +138 -0
  227. package/.versions/0.0.7/hermes/watchdog-tests/__init__.py +0 -0
  228. package/.versions/0.0.7/hooks/SIMPLIFY-IGNORE.md +90 -0
  229. package/.versions/0.0.7/hooks/coms-stop-hook.mjs +84 -0
  230. package/.versions/0.0.7/hooks/hooks.json +14 -0
  231. package/.versions/0.0.7/hooks/session-start.sh +74 -0
  232. package/.versions/0.0.7/hooks/simplify-ignore.sh +302 -0
  233. package/.versions/0.0.7/justfile +245 -0
  234. package/.versions/0.0.7/references/accessibility-checklist.md +160 -0
  235. package/.versions/0.0.7/references/definition-of-done.md +67 -0
  236. package/.versions/0.0.7/references/fleet-coordination-patterns.md +151 -0
  237. package/.versions/0.0.7/references/observability-checklist.md +91 -0
  238. package/.versions/0.0.7/references/orchestration-patterns.md +370 -0
  239. package/.versions/0.0.7/references/performance-checklist.md +153 -0
  240. package/.versions/0.0.7/references/prompting-patterns.md +380 -0
  241. package/.versions/0.0.7/references/security-checklist.md +179 -0
  242. package/.versions/0.0.7/references/testing-patterns.md +236 -0
  243. package/.versions/0.0.7/scripts/codex-conductor.ts +41 -0
  244. package/.versions/0.0.7/scripts/codex-remote-control.ts +167 -0
  245. package/.versions/0.0.7/scripts/coms-claude-bridge.ts +401 -0
  246. package/.versions/0.0.7/scripts/coms-cli.ts +484 -0
  247. package/.versions/0.0.7/scripts/coms-hermes-bridge.ts +413 -0
  248. package/.versions/0.0.7/scripts/fleet.ts +149 -0
  249. package/.versions/0.0.7/scripts/hermes-monitor-capability-runner.ts +25 -0
  250. package/.versions/0.0.7/scripts/hermes-monitor-scenario.ts +474 -0
  251. package/.versions/0.0.7/scripts/hermes-watchdog-capability-probe.ts +45 -0
  252. package/.versions/0.0.7/scripts/install-hermes-plugin.sh +180 -0
  253. package/.versions/0.0.7/scripts/lib/claude-bridge-core.ts +165 -0
  254. package/.versions/0.0.7/scripts/lib/codex-conductor.ts +88 -0
  255. package/.versions/0.0.7/scripts/lib/codex-remote-control.ts +480 -0
  256. package/.versions/0.0.7/scripts/lib/coms-envelope.ts +582 -0
  257. package/.versions/0.0.7/scripts/lib/fake-herdr-server.ts +88 -0
  258. package/.versions/0.0.7/scripts/lib/fleet-command.ts +109 -0
  259. package/.versions/0.0.7/scripts/lib/herdr-layout.ts +263 -0
  260. package/.versions/0.0.7/scripts/lib/hermes-bridge-core.ts +241 -0
  261. package/.versions/0.0.7/scripts/lib/hermes-monitor-events.ts +1 -0
  262. package/.versions/0.0.7/scripts/lib/hermes-monitor-herdr.ts +2 -0
  263. package/.versions/0.0.7/scripts/lib/hermes-monitor-model.ts +3 -0
  264. package/.versions/0.0.7/scripts/lib/hermes-monitor-registry.ts +2 -0
  265. package/.versions/0.0.7/scripts/lib/hermes-monitor-socket.ts +2 -0
  266. package/.versions/0.0.7/scripts/lib/hermes-monitor-store.ts +2 -0
  267. package/.versions/0.0.7/scripts/lib/monitor-env.ts +120 -0
  268. package/.versions/0.0.7/scripts/lib/persona-banner.ts +62 -0
  269. package/.versions/0.0.7/scripts/lib/spawn-stagger.ts +101 -0
  270. package/.versions/0.0.7/scripts/lib/team-project.ts +191 -0
  271. package/.versions/0.0.7/scripts/lib/team-snapshot.ts +147 -0
  272. package/.versions/0.0.7/scripts/peer-banner.ts +40 -0
  273. package/.versions/0.0.7/scripts/team-snapshot.ts +237 -0
  274. package/.versions/0.0.7/scripts/team-up.ts +360 -0
  275. package/.versions/0.0.7/skills/_internal/grilling.md +11 -0
  276. package/.versions/0.0.7/skills/browser-testing-with-devtools/SKILL.md +352 -0
  277. package/.versions/0.0.7/skills/code-review-and-quality/SKILL.md +381 -0
  278. package/.versions/0.0.7/skills/compound-learning/SKILL.md +137 -0
  279. package/.versions/0.0.7/skills/context-engineering/SKILL.md +291 -0
  280. package/.versions/0.0.7/skills/deprecation-and-migration/SKILL.md +206 -0
  281. package/.versions/0.0.7/skills/designing-agents/SKILL.md +394 -0
  282. package/.versions/0.0.7/skills/designing-agents/pi-harness-authoring.md +222 -0
  283. package/.versions/0.0.7/skills/frontend-ui-engineering/SKILL.md +328 -0
  284. package/.versions/0.0.7/skills/git-workflow-and-versioning/SKILL.md +316 -0
  285. package/.versions/0.0.7/skills/guided-workspace-setup/SKILL.md +544 -0
  286. package/.versions/0.0.7/skills/guided-workspace-setup/companion-manifest.json +35 -0
  287. package/.versions/0.0.7/skills/idea-refine/SKILL.md +182 -0
  288. package/.versions/0.0.7/skills/idea-refine/examples.md +238 -0
  289. package/.versions/0.0.7/skills/idea-refine/frameworks.md +99 -0
  290. package/.versions/0.0.7/skills/idea-refine/refinement-criteria.md +113 -0
  291. package/.versions/0.0.7/skills/idea-refine/scripts/idea-refine.sh +15 -0
  292. package/.versions/0.0.7/skills/incremental-implementation/SKILL.md +287 -0
  293. package/.versions/0.0.7/skills/interview-me/SKILL.md +226 -0
  294. package/.versions/0.0.7/skills/orchestration-verification/SKILL.md +181 -0
  295. package/.versions/0.0.7/skills/peer-coms/SKILL.md +90 -0
  296. package/.versions/0.0.7/skills/performance-optimization/SKILL.md +350 -0
  297. package/.versions/0.0.7/skills/planning-and-task-breakdown/SKILL.md +236 -0
  298. package/.versions/0.0.7/skills/security-and-hardening/SKILL.md +461 -0
  299. package/.versions/0.0.7/skills/spec-driven-development/SKILL.md +245 -0
  300. package/.versions/0.0.7/skills/using-agent-skills/SKILL.md +199 -0
  301. package/.versions/0.0.7/systemd/user/agent-fleet-codex-remote-control.service.in +23 -0
  302. package/.versions/0.0.7/vendor/agent-skills-upstream/LICENSE +21 -0
  303. package/.versions/0.0.7/vendor/agent-skills-upstream/README.md +11 -0
  304. package/.versions/0.0.7/vendor/agent-skills-upstream/skills/api-and-interface-design/SKILL.md +294 -0
  305. package/.versions/0.0.7/vendor/agent-skills-upstream/skills/browser-testing-with-devtools/SKILL.md +317 -0
  306. package/.versions/0.0.7/vendor/agent-skills-upstream/skills/ci-cd-and-automation/SKILL.md +390 -0
  307. package/.versions/0.0.7/vendor/agent-skills-upstream/skills/code-review-and-quality/SKILL.md +396 -0
  308. package/.versions/0.0.7/vendor/agent-skills-upstream/skills/code-simplification/SKILL.md +331 -0
  309. package/.versions/0.0.7/vendor/agent-skills-upstream/skills/context-engineering/SKILL.md +289 -0
  310. package/.versions/0.0.7/vendor/agent-skills-upstream/skills/debugging-and-error-recovery/SKILL.md +300 -0
  311. package/.versions/0.0.7/vendor/agent-skills-upstream/skills/deprecation-and-migration/SKILL.md +247 -0
  312. package/.versions/0.0.7/vendor/agent-skills-upstream/skills/documentation-and-adrs/SKILL.md +278 -0
  313. package/.versions/0.0.7/vendor/agent-skills-upstream/skills/doubt-driven-development/SKILL.md +243 -0
  314. package/.versions/0.0.7/vendor/agent-skills-upstream/skills/frontend-ui-engineering/SKILL.md +328 -0
  315. package/.versions/0.0.7/vendor/agent-skills-upstream/skills/git-workflow-and-versioning/SKILL.md +355 -0
  316. package/.versions/0.0.7/vendor/agent-skills-upstream/skills/idea-refine/SKILL.md +178 -0
  317. package/.versions/0.0.7/vendor/agent-skills-upstream/skills/idea-refine/examples.md +238 -0
  318. package/.versions/0.0.7/vendor/agent-skills-upstream/skills/idea-refine/frameworks.md +99 -0
  319. package/.versions/0.0.7/vendor/agent-skills-upstream/skills/idea-refine/refinement-criteria.md +113 -0
  320. package/.versions/0.0.7/vendor/agent-skills-upstream/skills/idea-refine/scripts/idea-refine.sh +15 -0
  321. package/.versions/0.0.7/vendor/agent-skills-upstream/skills/incremental-implementation/SKILL.md +249 -0
  322. package/.versions/0.0.7/vendor/agent-skills-upstream/skills/interview-me/SKILL.md +225 -0
  323. package/.versions/0.0.7/vendor/agent-skills-upstream/skills/observability-and-instrumentation/SKILL.md +203 -0
  324. package/.versions/0.0.7/vendor/agent-skills-upstream/skills/performance-optimization/SKILL.md +350 -0
  325. package/.versions/0.0.7/vendor/agent-skills-upstream/skills/planning-and-task-breakdown/SKILL.md +234 -0
  326. package/.versions/0.0.7/vendor/agent-skills-upstream/skills/security-and-hardening/SKILL.md +467 -0
  327. package/.versions/0.0.7/vendor/agent-skills-upstream/skills/shipping-and-launch/SKILL.md +310 -0
  328. package/.versions/0.0.7/vendor/agent-skills-upstream/skills/source-driven-development/SKILL.md +194 -0
  329. package/.versions/0.0.7/vendor/agent-skills-upstream/skills/spec-driven-development/SKILL.md +206 -0
  330. package/.versions/0.0.7/vendor/agent-skills-upstream/skills/test-driven-development/SKILL.md +383 -0
  331. package/.versions/0.0.7/vendor/agent-skills-upstream/skills/using-agent-skills/SKILL.md +191 -0
  332. package/CHANGELOG.md +134 -0
  333. package/README.md +175 -18
  334. package/agents/code-reviewer.md +2 -2
  335. package/agents/orchestrator.md +11 -0
  336. package/agents/plan-reviewer.md +1 -1
  337. package/agents/planner.md +1 -1
  338. package/agents/security-auditor.md +1 -1
  339. package/bin/cli.js +40 -1
  340. package/bin/lib/hermes-profile-artifact.js +144 -0
  341. package/bin/lib/set-hermes-watchdog.js +173 -0
  342. package/bin/set-hermes-watchdog.js +26 -0
  343. package/docs/ARCHITECTURE.md +64 -12
  344. package/docs/agent-fleet-setup.md +2 -2
  345. package/docs/claude-code-coms-bridge.md +7 -1
  346. package/docs/coms-hermes-bridge.md +10 -0
  347. package/docs/getting-started.md +48 -0
  348. package/docs/hermes-watchdog-supervisor.md +140 -0
  349. package/hermes/README.md +135 -19
  350. package/hermes/desktop-plugins/agent-fleet-herdr/plugin.js +1291 -0
  351. package/hermes/desktop-plugins/agent-fleet-herdr/presentation.js +672 -0
  352. package/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
  353. package/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
  354. package/hermes/plugins/agent-fleet-herdr/dashboard/activity.py +770 -0
  355. package/hermes/plugins/agent-fleet-herdr/dashboard/coms_registry.py +134 -0
  356. package/hermes/plugins/agent-fleet-herdr/dashboard/coms_send.py +350 -0
  357. package/hermes/plugins/agent-fleet-herdr/dashboard/herdr_source.py +193 -0
  358. package/hermes/plugins/agent-fleet-herdr/dashboard/manifest.json +4 -0
  359. package/hermes/plugins/agent-fleet-herdr/dashboard/plugin_api.py +444 -0
  360. package/hermes/plugins/agent-fleet-herdr/dashboard/sessions.py +205 -0
  361. package/hermes/plugins/agent-fleet-herdr/dashboard/tasks.py +300 -0
  362. package/hermes/plugins/agent-fleet-herdr/dashboard/watch.py +819 -0
  363. package/hermes/plugins/agent-fleet-herdr/plugin.yaml +8 -0
  364. package/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +139 -0
  365. package/hermes/plugins/agent-fleet-monitor/dashboard/dist/index.js +10 -0
  366. package/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
  367. package/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
  368. package/hermes/skills/hub-watchdog/SKILL.md +76 -0
  369. package/hermes/skills/hub-watchdog/manifest.json +1 -0
  370. package/hermes/skills/hub-watchdog/scripts/watchdog.py +249 -0
  371. package/hermes/skills/hub-watchdog/scripts/watchdog_actions.py +124 -0
  372. package/hermes/skills/hub-watchdog/scripts/watchdog_contract.py +76 -0
  373. package/hermes/skills/hub-watchdog/scripts/watchdog_delivery.py +10 -0
  374. package/hermes/skills/hub-watchdog/scripts/watchdog_engine.py +128 -0
  375. package/hermes/skills/hub-watchdog/scripts/watchdog_judgment.py +41 -0
  376. package/hermes/skills/hub-watchdog/scripts/watchdog_recovery.py +103 -0
  377. package/hermes/skills/hub-watchdog/scripts/watchdog_state.py +163 -0
  378. package/hermes/skills/hub-watchdog/scripts/watchdog_transport.py +138 -0
  379. package/hooks/coms-stop-hook.mjs +12 -1
  380. package/package.json +11 -2
  381. package/scripts/coms-claude-bridge.ts +154 -39
  382. package/scripts/fleet.ts +9 -1
  383. package/scripts/hermes-watchdog-capability-probe.ts +45 -0
  384. package/scripts/lib/claude-bridge-core.ts +65 -0
  385. package/scripts/lib/coms-envelope.ts +44 -1
  386. package/scripts/lib/hermes-monitor-events.ts +1 -0
  387. package/scripts/lib/monitor-env.ts +120 -0
  388. package/scripts/team-snapshot.ts +1 -1
  389. package/scripts/team-up.ts +10 -1
  390. package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-cap.test.py +0 -15
  391. package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-discovery.test.py +0 -19
  392. package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-envelope.test.py +0 -13
  393. package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-forged-owner.test.py +0 -11
  394. package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-lease-list.test.py +0 -9
  395. package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-multihub.test.py +0 -17
  396. package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-output.test.py +0 -34
  397. package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter.test.py +0 -39
  398. package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/plugin-api-validation.test.py +0 -12
  399. package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/review-live-wiring.red.test.py +0 -22
  400. package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-cap.test.py +0 -15
  401. package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-discovery.test.py +0 -19
  402. package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-envelope.test.py +0 -13
  403. package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-forged-owner.test.py +0 -11
  404. package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-lease-list.test.py +0 -9
  405. package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-multihub.test.py +0 -17
  406. package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-output.test.py +0 -34
  407. package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter.test.py +0 -39
  408. package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/plugin-api-validation.test.py +0 -12
  409. package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/review-live-wiring.red.test.py +0 -22
  410. package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/adapter-cap.test.py +0 -15
  411. package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/adapter-discovery.test.py +0 -19
  412. package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/adapter-envelope.test.py +0 -13
  413. package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/adapter-forged-owner.test.py +0 -11
  414. package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/adapter-lease-list.test.py +0 -9
  415. package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/adapter-multihub.test.py +0 -17
  416. package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/adapter-output.test.py +0 -34
  417. package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/adapter.test.py +0 -39
  418. package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/plugin-api-validation.test.py +0 -12
  419. package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/review-live-wiring.red.test.py +0 -22
@@ -91,7 +91,13 @@ Older releases used the ambiguous name-only path `~/.pi/coms/cli/<name>/`. If th
91
91
  ## Behavior notes
92
92
 
93
93
  - **Serialization:** one prompt at a time per pane; queue depth shows in the peer's
94
- agent card and the herdr sidebar (`<name> q<depth>`).
94
+ agent card and the herdr sidebar (`q<depth>`).
95
+ - **Presence:** the bridge annotates its pane through the shared `HerdrPresence`
96
+ (same dialect negotiation as pi peers — `tokens` on herdr >= 0.7.4, one latched
97
+ fallback to `custom_status`), so the pane carries `coms`/`proj` and the fleet panel
98
+ can join it to the registry entry. It writes the annotation ONLY, never
99
+ `pane.report_agent`: the pane's `agent_status` is herdr's own Claude detection and
100
+ the bridge polls it back as its turn-completion signal.
95
101
  - **Blocked panes:** a Claude waiting on a permission prompt returns a readable error
96
102
  envelope ("blocked on a permission prompt — a human must approve it") instead of
97
103
  hanging until timeout.
@@ -1,5 +1,13 @@
1
1
  # coms Hermes bridge
2
2
 
3
+ > The optional `hub-watchdog` is not this bridge and is not a coms conductor. It has no
4
+ > Herdr, shell, direct-tool, peer-delegation, service, or gateway authority. `hermes send --to`
5
+ > is an explicit destination mechanism, never origin-route evidence. Gate O has no checked-in
6
+ > live proof, so the supported watchdog posture is journal-only/dormant: no delivery,
7
+ > steering, cancellation, or recovery. It must not send an out-of-turn update, wake a chat, or
8
+ > fall back to another route. See [the watchdog runbook](hermes-watchdog-supervisor.md).
9
+
10
+
3
11
  Protocol contract for the Hermes ⇄ pi `coms` bridge. The first implemented daemon is `scripts/coms-hermes-bridge.ts`, which registers a `user-remote` peer and turns coms prompt envelopes into Hermes/Telegram questions.
4
12
 
5
13
  ## Pieces
@@ -76,6 +84,8 @@ If options exist and the trimmed answer is a 1-based number for an option, the r
76
84
 
77
85
  For a pending qid, cancel clears the timeout, removes the pending question, records terminal state `cancelled`, appends a `cancelled` log event, and sends a Telegram note: `✖ [HUB-Q:<qid>] The question was cancelled — it was answered from the console.` Cancel for a non-pending or invalid qid is a no-op after the envelope ack. A later answer file for a closed qid is treated as `late_answer`: logged, removed, and answered in Telegram with a polite ignored note; no response envelope is sent.
78
86
 
87
+ **Cancellation is local wait abandonment.** Cancelling a coms-backed run ends only this side's wait. The remote peer is not signalled and may keep working, so a `cancelled` state here is a statement about the local wait, never about the remote task. It follows that watchdog auto-recovery is forbidden for coms runs: no automatic retry, re-dispatch, retarget, or recovery invoke may follow a coms cancellation, and a cancelled coms run is never a recovery target. An explicit `hermes send --to <destination>` remains a destination-only mechanism chosen by a human; it is not evidence of an origin route and must not be used to "reply" to a cancelled run.
88
+
79
89
  ### Timeouts
80
90
 
81
91
  The per-question remote timeout defaults to `PI_COMS_TIMEOUT_MS`, or `1800000` ms when unset/invalid; `--timeout <ms>` overrides it. On timeout, the bridge removes the pending question, records terminal state `timeout`, logs `timeout`, sends the Telegram note `⌛ [HUB-Q:<qid>] The question timed out after <ms>ms.`, and sends an error response envelope with error `no remote answer within <ms>ms` and `response: null`.
@@ -18,6 +18,46 @@ Each skill is a Markdown file (`SKILL.md`) that describes a specific engineering
18
18
 
19
19
  All three converge on the same `guided-workspace-setup` skill — they only differ in how the source files reach your workspace. None is being deprecated.
20
20
 
21
+ ## Optional: see the fleet in Hermes Desktop
22
+
23
+ Once you are running more than one or two agents, `agent-fleet-herdr` gives you
24
+ a live panel of every Agent Fleet session — grouped by project, sorted so the
25
+ agent blocked on a human is at the top, with a toast when one gets stuck or
26
+ dies mid-work.
27
+
28
+ **You need:** Hermes v0.19.0+ with the Desktop app (`hermes` on `PATH`), this
29
+ repo checked out, and a fleet that has run at least once so
30
+ `~/.pi/coms/projects/` exists. [herdr](https://herdr.dev) is optional; without
31
+ it every row reads `unknown` instead of a live state.
32
+
33
+ ```bash
34
+ # 1. link both halves into the profile and open the enable gate
35
+ scripts/install-hermes-plugin.sh agent-fleet-herdr # --profile dev / --copy / --dry-run
36
+
37
+ # 2. restart the HERMES DESKTOP APP
38
+ # (not `hermes gateway restart` — the pane talks to the gateway Desktop spawns for itself,
39
+ # and backend routes only mount when that app starts)
40
+
41
+ # 3. start a fleet and open the "Agent Fleet" tab
42
+ just fleet team default
43
+ ```
44
+
45
+ Nothing about how you launch a fleet changes: the panel reads what the fleet
46
+ already writes (the coms registry, herdr presence, and each agent's own
47
+ transcript). It is read-only apart from `Focus pane` and cancelling a hub's
48
+ subagent. Uninstall with `scripts/install-hermes-plugin.sh agent-fleet-herdr
49
+ --uninstall`.
50
+
51
+ ![The Agent Fleet panel in Hermes Desktop listing seven live sessions in one project](assets/hermes-desktop-agent-fleet-panel.png)
52
+
53
+ Full runbook — prerequisites, API, join rules, event kinds, the optional
54
+ Telegram fan-out, and the failure modes that all look like an empty panel:
55
+ **[hermes-desktop-plugins.md](hermes-desktop-plugins.md)**.
56
+
57
+ Separately, the [coms ⇄ Hermes bridge](coms-hermes-bridge.md) relays an agent's
58
+ `ask_user` question to Telegram and races your phone's answer against a local
59
+ one. The two are independent; you can run either without the other.
60
+
21
61
  ## Optional experimental Android conductor
22
62
 
23
63
  Linux/pi fleet users can pair Codex Remote Control with ChatGPT Android and delegate one approval-gated task at a time to peers already running in a coms project. It is optional, supports only Codex CLI `0.144.x`, requires Node `22.6+` and user systemd, and does not replace Hermes as the inbound `ask_user` route.
@@ -174,6 +214,14 @@ The `/spec` and `/plan` commands create working artifacts (`SPEC.md`, `tasks/pla
174
214
  - Update them when scope or decisions change.
175
215
  - If your repo doesn’t want these files long‑term, delete them before merge or add the folder to `.gitignore` — the workflow doesn’t require them to be permanent.
176
216
 
217
+ ## Contributor verification
218
+
219
+ The live Agent Fleet hub delegation smoke is intentionally outside the default unit suite. It uses the current checkout's `HEAD` and a deterministic local Pi fixture (no network/model call):
220
+
221
+ ```bash
222
+ node --test scripts/agent-fleet-head-count-smoke.test.mjs
223
+ ```
224
+
177
225
  ## Tips
178
226
 
179
227
  1. **Start with spec-driven-development** for any non-trivial work
@@ -0,0 +1,140 @@
1
+ # Hermes watchdog supervisor
2
+
3
+ `hub-watchdog` is an optional, foreground Python skill packaged with Agent Fleet. It is a consumer of the local Agent Hub monitor transport, not a Hermes service, Herdr controller, coms conductor, or second dispatcher.
4
+
5
+ ## Current boundary and Gate O
6
+
7
+ The repository has **no proven Hermes API for an invoking chat's identity, incremental updates, wake/reconnect, or session attachment**. `hermes send --to …` selects an explicit destination; it does not prove an origin route.
8
+
9
+ Gate O has no checked-in live proof. Therefore the supported operational posture is:
10
+
11
+ - `originDelivery=false`;
12
+ - local decision journaling only;
13
+ - no chat delivery, steering, cancellation, or recovery; and
14
+ - no claim that live origin delivery, A6, or live watchdog autonomy has passed.
15
+
16
+ The capability probe and local tests validate a proposed artifact shape and fail-closed behavior only. They do not establish a real Hermes capability. Do not supply a synthetic artifact, a fixture, or an explicit `--to` target as Gate O evidence.
17
+
18
+ ## Safe out-of-turn policy
19
+
20
+ Run a watch only as an explicit, foreground operator action. It must not create a background service, wake a conversation, reopen a session, select a "last chat," redirect to another route, or act while the Hub is offline. Until Gate O is independently proven, any material event or deviation is recorded locally and nothing is sent or changed. Stop the foreground process to stop observation.
21
+
22
+ The watcher has no shell, PID-search, `pkill`, Herdr, gateway, service, direct Pi-tool, or peer-delegation authority. It does not replace the Hub's task ownership. Coms cancellation remains a local wait cancellation; a remote peer can continue, so it is never an automatic recovery target.
23
+
24
+ ## Installed skill and source package
25
+
26
+ `hermes/skills/hub-watchdog/` is the packaged **source artifact**, and the npm tarball also carries the backend and Desktop monitor plugin source under `hermes/plugins/` and `hermes/desktop-plugins/`. Packaging makes that source available to the installer and to a consumer that chooses to use it; it neither installs anything into a Hermes profile nor enables, launches, or configures a watcher or plugin. Installation into a profile is always an explicit opt-in operator action. The repository does not provide a supported live Hermes origin adapter.
27
+
28
+ Python test modules, bytecode, caches, and the local scenario fixtures are excluded from the tarball; the shipped Python is runtime-only and needs no dependency beyond the standard library.
29
+
30
+ The installed skill manifest defaults and caps autonomy at `observe`. The Python entrypoint also lowers `steer` or `surgical` to `observe` when Gate O is not valid. These checks are defensive code paths, not evidence that those higher tiers are approved for use.
31
+
32
+ ## Profile lifecycle
33
+
34
+ Use the deterministic controller or the matching guided command:
35
+
36
+ ```bash
37
+ agent-fleet set-hermes-watchdog status --profile <profile>
38
+ agent-fleet set-hermes-watchdog install --profile <profile>
39
+ agent-fleet set-hermes-watchdog update --profile <profile>
40
+ agent-fleet set-hermes-watchdog uninstall --profile <profile>
41
+ ```
42
+
43
+ `status` is read-only: it reports the resolved profile, whether that profile's gateway is running, the skill state (`missing`/`current`/`drifted`), the receipt state (`managed`/`unmanaged`/`drifted`), whether a watcher lock is active, and `originDelivery: false`. It writes nothing. `--dry-run` reports the write an `install`/`update` would make without making it.
44
+
45
+ `install` and `update` behave the same way and are chosen by intent:
46
+
47
+ | Skill state | Receipt state | Result |
48
+ | --- | --- | --- |
49
+ | missing | — | Atomic install plus a mode-0600 receipt |
50
+ | current | managed | No change |
51
+ | current | unmanaged | **Adopted**: the tree is re-fingerprinted and only the receipt is written |
52
+ | current | drifted | Refused; `--force` backs the tree up and reinstalls it |
53
+ | drifted | any | Refused; `--force` backs the tree up and replaces it |
54
+
55
+ Adoption is deliberately narrow: an unmanaged tree is adopted only when a fresh, symlink-free fingerprint exactly equals the packaged source at the moment of the write. An extra file, a symlink, an unsupported entry, or any drift is refused and left untouched — adoption never rewrites the tree it adopts, and never creates a backup.
56
+
57
+ `uninstall` removes only a `current`/`managed` tree by default, moving it to `backups/agent-fleet/` and deleting its receipt; anything else requires `--force`. It preserves `watchdog.json` and every journal. An active watcher lock is reported and never killed — stop the foreground process yourself first.
58
+
59
+ An install writes the profile's default configuration only when it is absent; it never overwrites an operator's edits.
60
+
61
+ The controller resolves the selected Hermes profile but does not start, stop, restart, or kill a gateway or watcher; change Hermes tools or permissions; send a test message; or manage Herdr. Use an explicit profile when automatic profile selection is not available.
62
+
63
+ The initial configuration written only when absent is:
64
+
65
+ ```json
66
+ {
67
+ "schemaVersion": 1,
68
+ "autonomy": "observe",
69
+ "maximumAutonomy": "observe",
70
+ "surgicalAllowlist": [],
71
+ "originDelivery": "required",
72
+ "runtimeDir": null
73
+ }
74
+ ```
75
+
76
+ Keep `autonomy` and `maximumAutonomy` at `observe` while Gate O is unproven. `runtimeDir: null` is not permission to scan runtime directories; a real watch invocation needs explicit validated monitor inputs.
77
+
78
+ ## Running and stopping a watch
79
+
80
+ A watch is a foreground process you start and stop yourself:
81
+
82
+ ```bash
83
+ python3 <profile>/skills/hub-watchdog/scripts/watchdog.py watch --invocation-json '<json>'
84
+ ```
85
+
86
+ The invocation names the profile, the validated `profileKey`/`hubKey` namespace, the hub instance, the monitor runtime directory, and the private state and lock directories. It takes a single `watch.lock` per profile under the lock directory; a second watcher for the same profile fails closed with `watcher_locked` rather than sharing state.
87
+
88
+ Send `SIGINT` (Ctrl-C) to stop it. On exit the watcher releases `watch.lock`, closes its UDS clients and any long-poll waiter, and leaves the local journal in place. It never daemonizes, re-execs, or restarts itself, and there is no service unit to disable.
89
+
90
+ ## Local monitor boundary
91
+
92
+ The Hub's owner-only UDS remains the source of task state. Existing monitor operations include bounded snapshot, task output, and exact-generation cancellation; `events` and `invoke` are additive on top of that baseline. Do not interpret implementation names, cursors, discovery fields, fixtures, or unit tests as a cross-process identity proof or a live watcher guarantee. A consumer must treat malformed discovery, ownership change, unavailable transport, and reconciliation uncertainty as stop conditions for action.
93
+
94
+ ### `events` and `invoke` responses
95
+
96
+ `events` replays the Hub's bounded event journal from a caller-held cursor. A request names `afterSequence`, a `limit` of 1–100, and a `waitMs` long-poll window of 0–25000. Set a read timeout that covers the window you ask the Hub to hold, otherwise a quiet poll expires locally and looks like an outage:
97
+
98
+ ```json
99
+ {"ok": true, "events": {"firstAvailableSequence": 1, "latestSequence": 4, "items": [], "timedOut": true}}
100
+ ```
101
+
102
+ When the cursor is older than the retained window the Hub refuses it instead of silently skipping facts, and the consumer must reconcile from a fresh snapshot and resume from sequence 0:
103
+
104
+ ```json
105
+ {"ok": false, "error": "cursor_too_old", "snapshotRequired": true, "firstAvailableSequence": 9, "latestSequence": 12}
106
+ ```
107
+
108
+ `invoke` submits one typed request and returns an admission status, never a result of work:
109
+
110
+ ```json
111
+ {"ok": true, "result": {"status": "accepted"}}
112
+ ```
113
+
114
+ `status` is one of `accepted`, `duplicate`, `queue_full`, `stale_generation`, `owner_changed`, `already_terminal`, `idempotency_conflict`, `unsupported`, or `rejected`. `accepted` means the Hub queued a visible follow-up for its operator to act on; it does not mean anything ran. A duplicate `requestId` returns `duplicate` and adds no second follow-up; the same `requestId` with different parameters returns `idempotency_conflict`.
115
+
116
+ ### Owner and profile mismatch
117
+
118
+ Identity is bound on every request: the configured profile key, hub instance, and owner must all equal what live discovery reports. A mismatch — a rolled-over owner, a different profile, a stale token — is a refusal, not a fallback. The watcher must rediscover the namespace and never reuse a previous owner's token or socket, and it must never search another profile's runtime tree. An accepted request is never re-driven across a rollover or restart.
119
+
120
+ The watchdog's local journal is a decision trace, not authoritative Hub history. It must not be used to infer a task's identity, completion, route, or delivery outcome beyond what the Hub has explicitly returned.
121
+
122
+ ## Migration, rollback, and incident handling
123
+
124
+ The monitor additions are intended to remain additive: older snapshot/output/cancel consumers continue to be the compatibility baseline. A consumer written against snapshot/output/cancel keeps working unchanged and needs no migration — `events` and `invoke` are new request types on the same socket, and a Hub that does not implement them answers `unsupported` rather than failing the connection.
125
+
126
+ To move such a consumer onto `events`, take a bounded snapshot first, then poll `events` from sequence 0 and treat `cursor_too_old` as an instruction to re-snapshot and restart the cursor. Keep the snapshot path: it is the only recovery route after a retention gap, an ownership change, or a reconnect. Output cursors stay per-task and are not comparable to event sequences. There is no migration that converts historical output cursors into a proven global event identity, and no migration that creates a Hermes origin route.
127
+
128
+ To roll back watchdog use:
129
+
130
+ 1. set the profile configuration to `observe` (or leave the default unchanged);
131
+ 2. stop the foreground watcher with `SIGINT` and confirm `watch.lock` is gone; and
132
+ 3. optionally run `uninstall` only after reviewing its status/backup behavior.
133
+
134
+ Rolling back to `observe` leaves the local journal intact and stops nothing else: the Hub keeps running, no task is cancelled, and no queued follow-up is withdrawn. Rollback is always to observe-and-journal, never to a different delivery route.
135
+
136
+ Do not delete a journal, lock, runtime directory, or profile tree to force recovery. Preserve suspect files for inspection. On a transport error, Gate O failure, owner/profile mismatch, ambiguous generation, or journal problem, leave the watcher stopped or journal-only; do not retry through Herdr, a gateway restart, a shell command, or coms.
137
+
138
+ ## Checks and evidence
139
+
140
+ The focused checks currently cover the capability-artifact validator, installer lifecycle, packaging boundary, and a small foreground watcher fixture. They are useful regression checks, but they do not prove live Hermes delivery, origin identity, wake/reconnect, multi-chat isolation, steering, or surgical recovery. Those claims remain blocked pending a sanitized, human-reviewed disposable live artifact naming the actual Hermes API and observed behavior.
package/hermes/README.md CHANGED
@@ -1,6 +1,61 @@
1
1
  # Hermes artifacts
2
2
 
3
- This directory contains in-repository Hermes skills for the coms Hermes bridge plan. They are source artifacts only; this pass does not modify `~/.hermes`.
3
+ This directory holds the in-repository Hermes surfaces of Agent Fleet: the
4
+ **Desktop plugin** that shows the live fleet, and the **skills** behind the
5
+ coms ⇄ Hermes question bridge. They are source artifacts, installed into a
6
+ profile explicitly — nothing here is published to npm and nothing writes to
7
+ `~/.hermes` unless you run an installer.
8
+
9
+ Two distinct integrations, easy to conflate:
10
+
11
+ | | What it does | Direction | Entry point |
12
+ |---|---|---|---|
13
+ | **Desktop plugin** (`agent-fleet-herdr`) | Shows every live Agent Fleet session, its state, what it is doing, and which agent is blocked on you | Hermes reads the fleet | [docs/hermes-desktop-plugins.md](../docs/hermes-desktop-plugins.md) |
14
+ | **Question bridge** (`hub-liaison`) | Relays an agent's `ask_user` question to Telegram and races your answer against a local one | The fleet asks you | [docs/coms-hermes-bridge.md](../docs/coms-hermes-bridge.md) |
15
+
16
+ ## Desktop plugins
17
+
18
+ `desktop-plugins/<id>/` and `plugins/<id>/` are the two halves of a Hermes
19
+ plugin — the Electron pane and the FastAPI backend it calls. They are installed
20
+ into a profile with `scripts/install-hermes-plugin.sh`, never published to npm.
21
+ The contract, the install runbook, and the failure modes that look identical
22
+ from the outside are documented in
23
+ [docs/hermes-desktop-plugins.md](../docs/hermes-desktop-plugins.md).
24
+
25
+ - `agent-fleet-herdr` — read-only panel of live Agent Fleet sessions grouped by
26
+ project, flagging the ones waiting for a human.
27
+ - `agent-fleet-monitor` — the separate agent-hub task view (leases, generations,
28
+ output cursors) over the local monitor transport described below. Its own
29
+ Desktop panel is deliberately left uninstalled: the subagent tree is rendered
30
+ inside `agent-fleet-herdr`'s session modal instead, so a human never has to
31
+ know which pane to open.
32
+
33
+ ### Install the fleet panel
34
+
35
+ Needs Hermes v0.19.0+ with the Desktop app, this checkout, and a fleet that has
36
+ run at least once (so `~/.pi/coms/projects/` exists). herdr is optional —
37
+ without it rows read `unknown` instead of a live state.
38
+
39
+ ```bash
40
+ scripts/install-hermes-plugin.sh agent-fleet-herdr # --profile / --copy / --dry-run / --uninstall
41
+ # then restart the Hermes DESKTOP APP (its gateway is the one that mounts the routes),
42
+ # start a fleet, and open the "Agent Fleet" tab:
43
+ just fleet team default
44
+ ```
45
+
46
+ ![The Agent Fleet panel in Hermes Desktop, listing seven live sessions in one project beside the chat that started them](../docs/assets/hermes-desktop-agent-fleet-panel.png)
47
+
48
+ Selecting a row opens a modal with that agent's purpose, model, context, queue,
49
+ uptime and heartbeat, a live tail of what it is doing read from its own
50
+ transcript, the subagents it is running with their stdout and a Cancel each, and
51
+ `Focus pane` to bring its workspace to the front.
52
+
53
+ ![The session modal for an orchestrator, showing its live activity tail and the Focus pane action](../docs/assets/hermes-desktop-session-modal.png)
54
+
55
+ Prerequisites in full, the API, the join rules, the failure modes and the
56
+ deliberate limits: [docs/hermes-desktop-plugins.md](../docs/hermes-desktop-plugins.md).
57
+
58
+ `skills/hub-watchdog/` is an optional foreground, fail-closed monitor consumer. It is packaged source, not an installed or enabled profile skill. Its profile-aware lifecycle is documented in [the watchdog runbook](../docs/hermes-watchdog-supervisor.md): no installer starts/stops a gateway or changes tools, and Gate O has no checked-in live origin proof. The supported posture is journal-only/dormant; it must not deliver, steer, cancel, recover, wake a chat, or choose a fallback route.
4
59
 
5
60
  ## Skills
6
61
 
@@ -20,7 +75,7 @@ agent-fleet set-hermes-telegram install --profile default --force
20
75
  agent-fleet set-hermes-telegram install --profile default --force --restart
21
76
  ```
22
77
 
23
- Pi and OpenCode use `/af-set-hermes-telegram`; Claude Code uses `/set-hermes-telegram`. The installer resolves the real profile path via `hermes profile show`, refuses drift without `--force`, backs up forced replacements, copies atomically, and verifies skill/tool/gateway readiness. It never sends a test Telegram message and never starts a stopped gateway. See [the bridge runbook](../docs/coms-hermes-bridge.md#set-hermes-telegram-bridge-control).
78
+ Pi and OpenCode use `/af-set-hermes-telegram`; Claude Code uses `/set-hermes-telegram`. The installer resolves the real profile path via `hermes profile show`, refuses drift without `--force`, backs up forced replacements, copies atomically, and verifies skill/tool/gateway readiness. It never sends a test Telegram message and never starts a stopped gateway. See [the bridge runbook](../docs/coms-hermes-bridge.md#telegram-bridge-control-command).
24
79
 
25
80
  The current `hermes skills install` CLI documents registry identifiers and direct HTTP(S) `SKILL.md` URLs, not local directories, so `hermes skills install hermes/skills/hub-liaison` is not the supported local installation path.
26
81
 
@@ -37,10 +92,11 @@ separate from the Telegram/coms bridge:
37
92
  - The monitor transport exposes dispatcher and specialist state through owner-only discovery,
38
93
  a token file, and a Unix domain socket (UDS).
39
94
 
40
- The repository does **not** ship or install a Hermes backend or Desktop plugin. A Hermes UI,
41
- operator tool, or other local client may consume the transport contract described below, but it
42
- owns its own presentation and lifecycle. The hub remains the source of truth for task state,
43
- output cursors, leases, and generation-safe cancellation.
95
+ A Hermes UI, operator tool, or other local client may consume the transport contract described
96
+ below, but it owns its own presentation and lifecycle. The hub remains the source of truth for
97
+ task state and cancellation. Source artifacts being present in this repository or its package do
98
+ not install, enable, or prove a live Hermes client. In particular, monitor cursor/discovery
99
+ fields and local tests are not proof of a Hermes origin identity or watcher delivery route.
44
100
 
45
101
  ### Integration in action
46
102
 
@@ -58,24 +114,33 @@ transport described below.
58
114
 
59
115
  ### Start a monitored hub
60
116
 
61
- Choose a stable Hermes profile ID and an absolute, owner-only runtime directory. A Herdr-backed
62
- hub is required because the stable hub identity includes `HERDR_WORKSPACE_ID` and
63
- `HERDR_PANE_ID`; the normal `hub-team` recipe supplies the Herdr environment.
117
+ Nothing to set up. A Herdr-backed hub is required because the stable hub identity includes
118
+ `HERDR_WORKSPACE_ID` and `HERDR_PANE_ID`, so use a team recipe:
64
119
 
65
120
  ```bash
66
- monitor_runtime="${XDG_RUNTIME_DIR:?XDG_RUNTIME_DIR must be set}/agent-fleet-monitor"
67
- install -d -m 700 "$monitor_runtime"
121
+ just fleet team default
122
+ ```
68
123
 
69
- export AGENT_FLEET_PROFILE_ID="dev"
70
- export AGENT_FLEET_MONITOR_RUNTIME_DIR="$monitor_runtime"
124
+ [scripts/lib/monitor-env.ts](../scripts/lib/monitor-env.ts) picks the profile ID (`dev`) and the
125
+ runtime directory (`$XDG_RUNTIME_DIR/agent-fleet-monitor`, created mode 0700) and the launchers
126
+ export both. Watch the tasks in the **agent-fleet-herdr** pane: select the hub's row, and its
127
+ subagents are a section of the modal with their live output and a Cancel each.
71
128
 
72
- just fleet team default
129
+ To point a hub at a different profile, or to turn the monitor off, set the variables yourself —
130
+ an existing value is never overwritten:
131
+
132
+ ```bash
133
+ AGENT_FLEET_PROFILE_ID=prod just fleet team default # a different Hermes profile
134
+ AGENT_FLEET_MONITOR=0 just fleet team default # unmonitored
73
135
  ```
74
136
 
75
- If either monitor variable is missing or invalid, or if the hub lacks stable Herdr identity, the
76
- monitor stays disabled while normal agent-hub orchestration continues. The profile ID must start
77
- with an alphanumeric character and may contain only alphanumerics, `.`, `_`, or `-`; `..` is
78
- rejected.
137
+ If either monitor variable is invalid, if the runtime directory cannot be made mode 0700, or if
138
+ the hub lacks stable Herdr identity, the monitor stays disabled while normal agent-hub
139
+ orchestration continues. The profile ID must start with an alphanumeric character and may contain
140
+ only alphanumerics, `.`, `_`, or `-`; `..` is rejected — the same class
141
+ `hermes/plugins/agent-fleet-monitor/dashboard/adapter.py` enforces when it reads the directory
142
+ back, because a value one end accepts and the other rejects is an empty listing with no error
143
+ anywhere.
79
144
 
80
145
  ### Discover the local endpoint
81
146
 
@@ -192,9 +257,60 @@ const cancelled = await monitorRequest(socketPath, {
192
257
 
193
258
  A native specialist cancellation targets only the hub-owned process generation and validates its
194
259
  process identity before signalling it. Cancelling a coms-backed run abandons the hub's local wait;
195
- the remote peer may continue. Neither operation creates, focuses, closes, or otherwise controls a
260
+ the remote peer may continue, so it is never an automatic recovery target and the watchdog must not
261
+ retry or re-dispatch it. Neither operation creates, focuses, closes, or otherwise controls a
196
262
  Herdr pane or workspace.
197
263
 
264
+ ### Additive `events` and `invoke` requests
265
+
266
+ Two request types extend the same socket. A hub that does not implement them answers `unsupported`,
267
+ so a snapshot/output/cancel consumer keeps working unchanged.
268
+
269
+ `events` replays a bounded journal from a cursor the consumer holds. Set a read timeout that covers
270
+ the `waitMs` window you ask the hub to hold, or every quiet poll expires locally and looks like an
271
+ outage:
272
+
273
+ ```js
274
+ const batch = await monitorRequest(socketPath, {
275
+ type: "events",
276
+ token,
277
+ afterSequence: 0,
278
+ limit: 50, // 1–100
279
+ waitMs: 2000 // 0–25000 long-poll window
280
+ });
281
+ // { ok: true, events: { firstAvailableSequence, latestSequence, items: [...], timedOut } }
282
+ ```
283
+
284
+ A cursor older than the retained window is refused rather than silently skipped. Reconcile from a
285
+ fresh snapshot and resume from sequence 0:
286
+
287
+ ```json
288
+ {"ok": false, "error": "cursor_too_old", "snapshotRequired": true, "firstAvailableSequence": 9, "latestSequence": 12}
289
+ ```
290
+
291
+ `invoke` submits one typed request and returns an admission status — never a result of work:
292
+
293
+ ```js
294
+ const admitted = await monitorRequest(socketPath, {
295
+ type: "invoke",
296
+ token,
297
+ requestId: "request-a",
298
+ taskId: "builder:1",
299
+ generation: 1,
300
+ action: "request_status",
301
+ parameters: { assertionIds: [], evidenceEventIds: ["hub:1"] },
302
+ basis: { deviation: "stalled_progress", judgment: "confirmed" }
303
+ });
304
+ // { ok: true, result: { status: "accepted" } }
305
+ ```
306
+
307
+ `status` is one of `accepted`, `duplicate`, `queue_full`, `stale_generation`, `owner_changed`,
308
+ `already_terminal`, `idempotency_conflict`, `unsupported`, or `rejected`. `accepted` means the hub
309
+ queued a visible follow-up for its operator; it does not mean anything ran. Reusing a `requestId`
310
+ returns `duplicate` and adds no second follow-up; reusing it with different parameters returns
311
+ `idempotency_conflict`. The action set is closed — there is no shell, tool, Herdr, or free-text
312
+ surface.
313
+
198
314
  ### Failure and reconnect behavior
199
315
 
200
316
  - `{"ok":false,"error":"unauthorized"}` means the token does not match current ownership.