@chankov/agent-fleet 2.0.1 → 2.0.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (695) hide show
  1. package/.pi/agents/voices.yaml +13 -0
  2. package/.pi/harnesses/agent-hub/README.md +3 -1
  3. package/.pi/harnesses/agent-hub/commands/context.ts +2 -0
  4. package/.pi/harnesses/agent-hub/commands/debate.ts +9 -0
  5. package/.pi/harnesses/agent-hub/commands/poll.ts +9 -0
  6. package/.pi/harnesses/agent-hub/config/agents.ts +14 -5
  7. package/.pi/harnesses/agent-hub/config/overrides.ts +44 -4
  8. package/.pi/harnesses/agent-hub/debate-command.ts +176 -0
  9. package/.pi/harnesses/agent-hub/delegate.ts +2 -2
  10. package/.pi/harnesses/agent-hub/index.ts +197 -0
  11. package/.pi/harnesses/agent-hub/lifecycle/session-orchestration.ts +5 -1
  12. package/.pi/harnesses/agent-hub/package.json +1 -1
  13. package/.pi/harnesses/agent-hub/poll-command.ts +176 -0
  14. package/.pi/harnesses/agent-hub/prompts/session-start.ts +2 -0
  15. package/.pi/harnesses/agent-hub/types.ts +1 -0
  16. package/.pi/harnesses/ask-user-remote/README.md +1 -1
  17. package/.pi/harnesses/coms/README.md +1 -1
  18. package/.pi/harnesses/coms/package.json +1 -1
  19. package/.pi/harnesses/damage-control-continue/package.json +1 -1
  20. package/.versions/2.0.2/.pi/agents/dispatch-policy.yaml +32 -0
  21. package/.versions/2.0.2/.pi/agents/model-profiles.yaml +27 -0
  22. package/.versions/2.0.2/.pi/agents/peers.yaml +142 -0
  23. package/.versions/2.0.2/.pi/agents/teams.yaml +41 -0
  24. package/.versions/2.0.2/.pi/agents/voices.yaml +13 -0
  25. package/.versions/2.0.2/.pi/damage-control-rules.yaml +297 -0
  26. package/.versions/2.0.2/.pi/extensions/agent-fleet-update-check/README.md +57 -0
  27. package/.versions/2.0.2/.pi/extensions/agent-fleet-update-check/index.ts +161 -0
  28. package/.versions/2.0.2/.pi/extensions/agent-fleet-update-check/package.json +6 -0
  29. package/.versions/2.0.2/.pi/extensions/btw/README.md +120 -0
  30. package/.versions/2.0.2/.pi/extensions/btw/index.ts +914 -0
  31. package/.versions/2.0.2/.pi/extensions/btw/package.json +6 -0
  32. package/.versions/2.0.2/.pi/extensions/btw/state.js +179 -0
  33. package/.versions/2.0.2/.pi/extensions/chrome-devtools-mcp/README.md +55 -0
  34. package/.versions/2.0.2/.pi/extensions/chrome-devtools-mcp/index.ts +93 -0
  35. package/.versions/2.0.2/.pi/extensions/chrome-devtools-mcp/package.json +6 -0
  36. package/.versions/2.0.2/.pi/extensions/compact-and-continue/README.md +42 -0
  37. package/.versions/2.0.2/.pi/extensions/compact-and-continue/index.ts +120 -0
  38. package/.versions/2.0.2/.pi/extensions/compact-and-continue/package.json +6 -0
  39. package/.versions/2.0.2/.pi/extensions/mcp-bridge/README.md +46 -0
  40. package/.versions/2.0.2/.pi/extensions/mcp-bridge/index.ts +206 -0
  41. package/.versions/2.0.2/.pi/extensions/mcp-bridge/package.json +6 -0
  42. package/.versions/2.0.2/.pi/extensions/package-lock.json +1175 -0
  43. package/.versions/2.0.2/.pi/extensions/package.json +9 -0
  44. package/.versions/2.0.2/.pi/extensions/pi-voice-stt/README.md +205 -0
  45. package/.versions/2.0.2/.pi/extensions/pi-voice-stt/config.ts +198 -0
  46. package/.versions/2.0.2/.pi/extensions/pi-voice-stt/examples/stt.json +35 -0
  47. package/.versions/2.0.2/.pi/extensions/pi-voice-stt/index.ts +248 -0
  48. package/.versions/2.0.2/.pi/extensions/pi-voice-stt/package.json +6 -0
  49. package/.versions/2.0.2/.pi/extensions/pi-voice-stt/providers.ts +214 -0
  50. package/.versions/2.0.2/.pi/extensions/pi-voice-stt/recorder.ts +158 -0
  51. package/.versions/2.0.2/.pi/harnesses/agent-hub/README.md +1163 -0
  52. package/.versions/2.0.2/.pi/harnesses/agent-hub/access-approval.ts +135 -0
  53. package/.versions/2.0.2/.pi/harnesses/agent-hub/artifacts.js +146 -0
  54. package/.versions/2.0.2/.pi/harnesses/agent-hub/assertion-ledger.js +58 -0
  55. package/.versions/2.0.2/.pi/harnesses/agent-hub/backend-policy.js +174 -0
  56. package/.versions/2.0.2/.pi/harnesses/agent-hub/budget-continuation.ts +73 -0
  57. package/.versions/2.0.2/.pi/harnesses/agent-hub/capability-confirmation.ts +47 -0
  58. package/.versions/2.0.2/.pi/harnesses/agent-hub/capability-packs.ts +180 -0
  59. package/.versions/2.0.2/.pi/harnesses/agent-hub/commands/agent-model-thinking.ts +10 -0
  60. package/.versions/2.0.2/.pi/harnesses/agent-hub/commands/agent-model.ts +10 -0
  61. package/.versions/2.0.2/.pi/harnesses/agent-hub/commands/agent-models-substitute.ts +10 -0
  62. package/.versions/2.0.2/.pi/harnesses/agent-hub/commands/agents-add.ts +9 -0
  63. package/.versions/2.0.2/.pi/harnesses/agent-hub/commands/agents-drop.ts +9 -0
  64. package/.versions/2.0.2/.pi/harnesses/agent-hub/commands/agents-history.ts +9 -0
  65. package/.versions/2.0.2/.pi/harnesses/agent-hub/commands/agents-kill.ts +10 -0
  66. package/.versions/2.0.2/.pi/harnesses/agent-hub/commands/agents-list.ts +9 -0
  67. package/.versions/2.0.2/.pi/harnesses/agent-hub/commands/agents-restart.ts +10 -0
  68. package/.versions/2.0.2/.pi/harnesses/agent-hub/commands/agents-save.ts +9 -0
  69. package/.versions/2.0.2/.pi/harnesses/agent-hub/commands/agents-team.ts +9 -0
  70. package/.versions/2.0.2/.pi/harnesses/agent-hub/commands/compound.ts +9 -0
  71. package/.versions/2.0.2/.pi/harnesses/agent-hub/commands/coms.ts +9 -0
  72. package/.versions/2.0.2/.pi/harnesses/agent-hub/commands/context-command.ts +9 -0
  73. package/.versions/2.0.2/.pi/harnesses/agent-hub/commands/context.ts +41 -0
  74. package/.versions/2.0.2/.pi/harnesses/agent-hub/commands/debate.ts +9 -0
  75. package/.versions/2.0.2/.pi/harnesses/agent-hub/commands/dispatch-policy.ts +9 -0
  76. package/.versions/2.0.2/.pi/harnesses/agent-hub/commands/handoff.ts +10 -0
  77. package/.versions/2.0.2/.pi/harnesses/agent-hub/commands/hub-report.ts +9 -0
  78. package/.versions/2.0.2/.pi/harnesses/agent-hub/commands/models.ts +10 -0
  79. package/.versions/2.0.2/.pi/harnesses/agent-hub/commands/poll.ts +9 -0
  80. package/.versions/2.0.2/.pi/harnesses/agent-hub/commands/watchdog.ts +9 -0
  81. package/.versions/2.0.2/.pi/harnesses/agent-hub/commands/work-mode.ts +29 -0
  82. package/.versions/2.0.2/.pi/harnesses/agent-hub/commands/zoom.ts +10 -0
  83. package/.versions/2.0.2/.pi/harnesses/agent-hub/config/agents.ts +180 -0
  84. package/.versions/2.0.2/.pi/harnesses/agent-hub/config/overrides.ts +158 -0
  85. package/.versions/2.0.2/.pi/harnesses/agent-hub/context/agent-state.ts +30 -0
  86. package/.versions/2.0.2/.pi/harnesses/agent-hub/context/assertions-artifacts.ts +211 -0
  87. package/.versions/2.0.2/.pi/harnesses/agent-hub/context/budgets.ts +208 -0
  88. package/.versions/2.0.2/.pi/harnesses/agent-hub/context/hub-state.ts +40 -0
  89. package/.versions/2.0.2/.pi/harnesses/agent-hub/context-budget-snapshot.ts +105 -0
  90. package/.versions/2.0.2/.pi/harnesses/agent-hub/context-pressure.ts +191 -0
  91. package/.versions/2.0.2/.pi/harnesses/agent-hub/context-window.js +106 -0
  92. package/.versions/2.0.2/.pi/harnesses/agent-hub/debate-command.ts +176 -0
  93. package/.versions/2.0.2/.pi/harnesses/agent-hub/delegate.ts +446 -0
  94. package/.versions/2.0.2/.pi/harnesses/agent-hub/dispatch-coms.ts +232 -0
  95. package/.versions/2.0.2/.pi/harnesses/agent-hub/dispatch-core.ts +27 -0
  96. package/.versions/2.0.2/.pi/harnesses/agent-hub/dispatch-native-complete.ts +135 -0
  97. package/.versions/2.0.2/.pi/harnesses/agent-hub/dispatch-native-prepare.ts +153 -0
  98. package/.versions/2.0.2/.pi/harnesses/agent-hub/dispatch-native-spawn.ts +191 -0
  99. package/.versions/2.0.2/.pi/harnesses/agent-hub/dispatch-native-types.ts +207 -0
  100. package/.versions/2.0.2/.pi/harnesses/agent-hub/dispatch-native.ts +184 -0
  101. package/.versions/2.0.2/.pi/harnesses/agent-hub/dispatch-observability.ts +220 -0
  102. package/.versions/2.0.2/.pi/harnesses/agent-hub/docs-lane.js +122 -0
  103. package/.versions/2.0.2/.pi/harnesses/agent-hub/drift-watchdog.js +218 -0
  104. package/.versions/2.0.2/.pi/harnesses/agent-hub/evidence-rules.js +96 -0
  105. package/.versions/2.0.2/.pi/harnesses/agent-hub/external-blocker.js +85 -0
  106. package/.versions/2.0.2/.pi/harnesses/agent-hub/fixtures/registration-surface.json +55 -0
  107. package/.versions/2.0.2/.pi/harnesses/agent-hub/footer.ts +30 -0
  108. package/.versions/2.0.2/.pi/harnesses/agent-hub/helpers.ts +266 -0
  109. package/.versions/2.0.2/.pi/harnesses/agent-hub/hub-state-audit.js +59 -0
  110. package/.versions/2.0.2/.pi/harnesses/agent-hub/index.ts +2047 -0
  111. package/.versions/2.0.2/.pi/harnesses/agent-hub/input/completions.ts +76 -0
  112. package/.versions/2.0.2/.pi/harnesses/agent-hub/input/shortcuts.ts +47 -0
  113. package/.versions/2.0.2/.pi/harnesses/agent-hub/lifecycle/context-pressure.ts +123 -0
  114. package/.versions/2.0.2/.pi/harnesses/agent-hub/lifecycle/monitor-session.ts +104 -0
  115. package/.versions/2.0.2/.pi/harnesses/agent-hub/lifecycle/session-orchestration.ts +143 -0
  116. package/.versions/2.0.2/.pi/harnesses/agent-hub/lifecycle/turn-handlers.ts +95 -0
  117. package/.versions/2.0.2/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
  118. package/.versions/2.0.2/.pi/harnesses/agent-hub/monitor-invoke-journal.ts +131 -0
  119. package/.versions/2.0.2/.pi/harnesses/agent-hub/monitor-invoke.ts +92 -0
  120. package/.versions/2.0.2/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
  121. package/.versions/2.0.2/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
  122. package/.versions/2.0.2/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
  123. package/.versions/2.0.2/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
  124. package/.versions/2.0.2/.pi/harnesses/agent-hub/monitor-session-bridge.ts +266 -0
  125. package/.versions/2.0.2/.pi/harnesses/agent-hub/package.json +7 -0
  126. package/.versions/2.0.2/.pi/harnesses/agent-hub/peer-spawn-plan.ts +116 -0
  127. package/.versions/2.0.2/.pi/harnesses/agent-hub/policy/models.ts +126 -0
  128. package/.versions/2.0.2/.pi/harnesses/agent-hub/policy/roster.ts +79 -0
  129. package/.versions/2.0.2/.pi/harnesses/agent-hub/policy/work-mode.ts +118 -0
  130. package/.versions/2.0.2/.pi/harnesses/agent-hub/poll-command.ts +176 -0
  131. package/.versions/2.0.2/.pi/harnesses/agent-hub/presentation.ts +48 -0
  132. package/.versions/2.0.2/.pi/harnesses/agent-hub/prompts/context.ts +46 -0
  133. package/.versions/2.0.2/.pi/harnesses/agent-hub/prompts/fragments.ts +115 -0
  134. package/.versions/2.0.2/.pi/harnesses/agent-hub/prompts/session-start.ts +90 -0
  135. package/.versions/2.0.2/.pi/harnesses/agent-hub/prompts/system-prompt.ts +110 -0
  136. package/.versions/2.0.2/.pi/harnesses/agent-hub/provider-semaphore.js +138 -0
  137. package/.versions/2.0.2/.pi/harnesses/agent-hub/research/controls.ts +75 -0
  138. package/.versions/2.0.2/.pi/harnesses/agent-hub/research/runtime.ts +184 -0
  139. package/.versions/2.0.2/.pi/harnesses/agent-hub/research/spawn-run.ts +146 -0
  140. package/.versions/2.0.2/.pi/harnesses/agent-hub/research-retention.js +34 -0
  141. package/.versions/2.0.2/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
  142. package/.versions/2.0.2/.pi/harnesses/agent-hub/return-contract.js +293 -0
  143. package/.versions/2.0.2/.pi/harnesses/agent-hub/return-extract.js +75 -0
  144. package/.versions/2.0.2/.pi/harnesses/agent-hub/review-findings.js +102 -0
  145. package/.versions/2.0.2/.pi/harnesses/agent-hub/run-budget.js +537 -0
  146. package/.versions/2.0.2/.pi/harnesses/agent-hub/run-namespace.js +87 -0
  147. package/.versions/2.0.2/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
  148. package/.versions/2.0.2/.pi/harnesses/agent-hub/scope-gate.js +103 -0
  149. package/.versions/2.0.2/.pi/harnesses/agent-hub/session-health.js +110 -0
  150. package/.versions/2.0.2/.pi/harnesses/agent-hub/session-start.ts +42 -0
  151. package/.versions/2.0.2/.pi/harnesses/agent-hub/spawn.ts +388 -0
  152. package/.versions/2.0.2/.pi/harnesses/agent-hub/timeline.ts +54 -0
  153. package/.versions/2.0.2/.pi/harnesses/agent-hub/tools/action-executors.ts +146 -0
  154. package/.versions/2.0.2/.pi/harnesses/agent-hub/tools/coms-tools.ts +139 -0
  155. package/.versions/2.0.2/.pi/harnesses/agent-hub/tools/context.ts +132 -0
  156. package/.versions/2.0.2/.pi/harnesses/agent-hub/tools/dispatch-agent.ts +79 -0
  157. package/.versions/2.0.2/.pi/harnesses/agent-hub/tools/dispatch-execution.ts +200 -0
  158. package/.versions/2.0.2/.pi/harnesses/agent-hub/tools/execution-orchestration.ts +22 -0
  159. package/.versions/2.0.2/.pi/harnesses/agent-hub/tools/fleet-tools.ts +202 -0
  160. package/.versions/2.0.2/.pi/harnesses/agent-hub/tools/herdr-executors.ts +82 -0
  161. package/.versions/2.0.2/.pi/harnesses/agent-hub/tools/set-task-tier.ts +29 -0
  162. package/.versions/2.0.2/.pi/harnesses/agent-hub/tools/spawn-research.ts +62 -0
  163. package/.versions/2.0.2/.pi/harnesses/agent-hub/tools/team-adjust.ts +29 -0
  164. package/.versions/2.0.2/.pi/harnesses/agent-hub/tools/verification-contract.ts +77 -0
  165. package/.versions/2.0.2/.pi/harnesses/agent-hub/types.ts +61 -0
  166. package/.versions/2.0.2/.pi/harnesses/agent-hub/ui/context-budget.ts +86 -0
  167. package/.versions/2.0.2/.pi/harnesses/agent-hub/ui/detail-panel.ts +175 -0
  168. package/.versions/2.0.2/.pi/harnesses/agent-hub/ui/fleet-dashboard.ts +130 -0
  169. package/.versions/2.0.2/.pi/harnesses/agent-hub/ui/grid.ts +306 -0
  170. package/.versions/2.0.2/.pi/harnesses/agent-hub/ui/history-store.ts +137 -0
  171. package/.versions/2.0.2/.pi/harnesses/agent-hub/ui/history.ts +234 -0
  172. package/.versions/2.0.2/.pi/harnesses/agent-hub/ui/pool.ts +103 -0
  173. package/.versions/2.0.2/.pi/harnesses/agent-hub/ui/zoom.ts +204 -0
  174. package/.versions/2.0.2/.pi/harnesses/agent-hub/version.ts +42 -0
  175. package/.versions/2.0.2/.pi/harnesses/agent-hub/work-mode-controls.ts +56 -0
  176. package/.versions/2.0.2/.pi/harnesses/agent-hub/work-mode.ts +167 -0
  177. package/.versions/2.0.2/.pi/harnesses/ask-user-remote/README.md +53 -0
  178. package/.versions/2.0.2/.pi/harnesses/ask-user-remote/index.ts +532 -0
  179. package/.versions/2.0.2/.pi/harnesses/ask-user-remote/race-core.js +106 -0
  180. package/.versions/2.0.2/.pi/harnesses/coms/README.md +100 -0
  181. package/.versions/2.0.2/.pi/harnesses/coms/index.ts +276 -0
  182. package/.versions/2.0.2/.pi/harnesses/coms/package.json +7 -0
  183. package/.versions/2.0.2/.pi/harnesses/coms/version.ts +42 -0
  184. package/.versions/2.0.2/.pi/harnesses/damage-control-continue/README.md +124 -0
  185. package/.versions/2.0.2/.pi/harnesses/damage-control-continue/index.ts +536 -0
  186. package/.versions/2.0.2/.pi/harnesses/damage-control-continue/package.json +7 -0
  187. package/.versions/2.0.2/.pi/harnesses/damage-control-continue/version.ts +42 -0
  188. package/.versions/2.0.2/.pi/harnesses/lib/coms-core-io.ts +385 -0
  189. package/.versions/2.0.2/.pi/harnesses/lib/coms-core.ts +577 -0
  190. package/.versions/2.0.2/.pi/harnesses/lib/coms-registry-entry.ts +94 -0
  191. package/.versions/2.0.2/.pi/harnesses/lib/context-budget-child-prompt.ts +179 -0
  192. package/.versions/2.0.2/.pi/harnesses/lib/context-budget-hub-prompt.ts +114 -0
  193. package/.versions/2.0.2/.pi/harnesses/lib/context-budget-view.ts +107 -0
  194. package/.versions/2.0.2/.pi/harnesses/lib/context-budget.ts +114 -0
  195. package/.versions/2.0.2/.pi/harnesses/lib/damage-control-shared.ts +197 -0
  196. package/.versions/2.0.2/.pi/harnesses/lib/fixtures/context-budget-profiles.json +11 -0
  197. package/.versions/2.0.2/.pi/harnesses/lib/fixtures/hub-prompt-operator.legacy.txt +73 -0
  198. package/.versions/2.0.2/.pi/harnesses/lib/fixtures/hub-prompt-orchestrator.legacy.txt +73 -0
  199. package/.versions/2.0.2/.pi/harnesses/lib/fleet-dashboard-ops.ts +155 -0
  200. package/.versions/2.0.2/.pi/harnesses/lib/fleet-dashboard-view.ts +142 -0
  201. package/.versions/2.0.2/.pi/harnesses/lib/fleet-detail-view.ts +247 -0
  202. package/.versions/2.0.2/.pi/harnesses/lib/fleet-overlay.ts +26 -0
  203. package/.versions/2.0.2/.pi/harnesses/lib/fleet-panel.ts +34 -0
  204. package/.versions/2.0.2/.pi/harnesses/lib/fleet-read-model.ts +131 -0
  205. package/.versions/2.0.2/.pi/harnesses/lib/fleet-selection.ts +24 -0
  206. package/.versions/2.0.2/.pi/harnesses/lib/fleet-transcript-store.ts +244 -0
  207. package/.versions/2.0.2/.pi/harnesses/lib/herdr-client.ts +472 -0
  208. package/.versions/2.0.2/.pi/harnesses/lib/herdr-presence.ts +399 -0
  209. package/.versions/2.0.2/.pi/harnesses/lib/hermes-monitor-events.ts +136 -0
  210. package/.versions/2.0.2/.pi/harnesses/lib/hermes-monitor-herdr.ts +28 -0
  211. package/.versions/2.0.2/.pi/harnesses/lib/hermes-monitor-model.ts +18 -0
  212. package/.versions/2.0.2/.pi/harnesses/lib/hermes-monitor-registry.ts +6 -0
  213. package/.versions/2.0.2/.pi/harnesses/lib/hermes-monitor-socket.ts +163 -0
  214. package/.versions/2.0.2/.pi/harnesses/lib/hermes-monitor-store.ts +31 -0
  215. package/.versions/2.0.2/.pi/harnesses/lib/spawned-peers.js +190 -0
  216. package/.versions/2.0.2/.pi/harnesses/package-lock.json +2039 -0
  217. package/.versions/2.0.2/.pi/harnesses/package.json +10 -0
  218. package/.versions/2.0.2/.pi/prompts/af-build.md +24 -0
  219. package/.versions/2.0.2/.pi/prompts/af-code-simplify.md +22 -0
  220. package/.versions/2.0.2/.pi/prompts/af-plan.md +17 -0
  221. package/.versions/2.0.2/.pi/prompts/af-review.md +16 -0
  222. package/.versions/2.0.2/.pi/prompts/af-set-hermes-telegram.md +15 -0
  223. package/.versions/2.0.2/.pi/prompts/af-set-hermes-watchdog.md +6 -0
  224. package/.versions/2.0.2/.pi/prompts/af-ship.md +17 -0
  225. package/.versions/2.0.2/.pi/prompts/af-spec.md +15 -0
  226. package/.versions/2.0.2/.pi/prompts/af-test.md +19 -0
  227. package/.versions/2.0.2/.pi/skills/bowser/SKILL.md +145 -0
  228. package/.versions/2.0.2/.version +1 -0
  229. package/.versions/2.0.2/agents/architect.md +25 -0
  230. package/.versions/2.0.2/agents/bowser.md +28 -0
  231. package/.versions/2.0.2/agents/builder.md +56 -0
  232. package/.versions/2.0.2/agents/code-reviewer.md +210 -0
  233. package/.versions/2.0.2/agents/deep-researcher.md +33 -0
  234. package/.versions/2.0.2/agents/documenter.md +22 -0
  235. package/.versions/2.0.2/agents/orchestrator.md +23 -0
  236. package/.versions/2.0.2/agents/plan-reviewer.md +84 -0
  237. package/.versions/2.0.2/agents/planner.md +105 -0
  238. package/.versions/2.0.2/agents/releaser.md +25 -0
  239. package/.versions/2.0.2/agents/researcher.md +31 -0
  240. package/.versions/2.0.2/agents/security-auditor.md +168 -0
  241. package/.versions/2.0.2/agents/test-engineer.md +154 -0
  242. package/.versions/2.0.2/agents/web-debugger.md +44 -0
  243. package/.versions/2.0.2/agents/web-performance-auditor.md +194 -0
  244. package/.versions/2.0.2/bin/catalog/harness-runtime-closure.json +34 -0
  245. package/.versions/2.0.2/codex/CONDUCTOR.md +148 -0
  246. package/.versions/2.0.2/docs/ARCHITECTURE.md +407 -0
  247. package/.versions/2.0.2/docs/agent-fleet-setup.md +473 -0
  248. package/.versions/2.0.2/docs/claude-code-coms-bridge.md +128 -0
  249. package/.versions/2.0.2/docs/codex-remote-conductor.md +170 -0
  250. package/.versions/2.0.2/docs/coms-hermes-bridge.md +189 -0
  251. package/.versions/2.0.2/docs/getting-started.md +119 -0
  252. package/.versions/2.0.2/docs/npm-install.md +292 -0
  253. package/.versions/2.0.2/docs/pi-extensions.md +444 -0
  254. package/.versions/2.0.2/docs/pi-setup.md +74 -0
  255. package/.versions/2.0.2/docs/skill-anatomy.md +150 -0
  256. package/.versions/2.0.2/hermes/README.md +347 -0
  257. package/.versions/2.0.2/hermes/desktop-plugins/agent-fleet-herdr/plugin.js +1291 -0
  258. package/.versions/2.0.2/hermes/desktop-plugins/agent-fleet-herdr/presentation.js +672 -0
  259. package/.versions/2.0.2/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
  260. package/.versions/2.0.2/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
  261. package/.versions/2.0.2/hermes/gates/gate-o-capability.md +8 -0
  262. package/.versions/2.0.2/hermes/gates/gate-o-validator-fixtures.json +1 -0
  263. package/.versions/2.0.2/hermes/plugins/agent-fleet-herdr/dashboard/activity.py +770 -0
  264. package/.versions/2.0.2/hermes/plugins/agent-fleet-herdr/dashboard/coms_registry.py +134 -0
  265. package/.versions/2.0.2/hermes/plugins/agent-fleet-herdr/dashboard/coms_send.py +350 -0
  266. package/.versions/2.0.2/hermes/plugins/agent-fleet-herdr/dashboard/herdr_source.py +193 -0
  267. package/.versions/2.0.2/hermes/plugins/agent-fleet-herdr/dashboard/manifest.json +4 -0
  268. package/.versions/2.0.2/hermes/plugins/agent-fleet-herdr/dashboard/plugin_api.py +444 -0
  269. package/.versions/2.0.2/hermes/plugins/agent-fleet-herdr/dashboard/sessions.py +205 -0
  270. package/.versions/2.0.2/hermes/plugins/agent-fleet-herdr/dashboard/tasks.py +300 -0
  271. package/.versions/2.0.2/hermes/plugins/agent-fleet-herdr/dashboard/watch.py +819 -0
  272. package/.versions/2.0.2/hermes/plugins/agent-fleet-herdr/plugin.yaml +8 -0
  273. package/.versions/2.0.2/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +139 -0
  274. package/.versions/2.0.2/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
  275. package/.versions/2.0.2/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
  276. package/.versions/2.0.2/hermes/skills/hub-conductor/SKILL.md +84 -0
  277. package/.versions/2.0.2/hermes/skills/hub-liaison/SKILL.md +84 -0
  278. package/.versions/2.0.2/hermes/skills/hub-watchdog/SKILL.md +76 -0
  279. package/.versions/2.0.2/hermes/skills/hub-watchdog/manifest.json +1 -0
  280. package/.versions/2.0.2/hermes/skills/hub-watchdog/scripts/watchdog.py +249 -0
  281. package/.versions/2.0.2/hermes/skills/hub-watchdog/scripts/watchdog_actions.py +124 -0
  282. package/.versions/2.0.2/hermes/skills/hub-watchdog/scripts/watchdog_contract.py +76 -0
  283. package/.versions/2.0.2/hermes/skills/hub-watchdog/scripts/watchdog_delivery.py +10 -0
  284. package/.versions/2.0.2/hermes/skills/hub-watchdog/scripts/watchdog_engine.py +128 -0
  285. package/.versions/2.0.2/hermes/skills/hub-watchdog/scripts/watchdog_judgment.py +41 -0
  286. package/.versions/2.0.2/hermes/skills/hub-watchdog/scripts/watchdog_recovery.py +103 -0
  287. package/.versions/2.0.2/hermes/skills/hub-watchdog/scripts/watchdog_state.py +163 -0
  288. package/.versions/2.0.2/hermes/skills/hub-watchdog/scripts/watchdog_transport.py +138 -0
  289. package/.versions/2.0.2/hermes/watchdog-tests/__init__.py +0 -0
  290. package/.versions/2.0.2/hooks/coms-stop-hook.mjs +84 -0
  291. package/.versions/2.0.2/install-manifest.json +2905 -0
  292. package/.versions/2.0.2/justfile +288 -0
  293. package/.versions/2.0.2/manifest-meta.json +945 -0
  294. package/.versions/2.0.2/references/accessibility-checklist.md +160 -0
  295. package/.versions/2.0.2/references/communication-contract.md +26 -0
  296. package/.versions/2.0.2/references/definition-of-done.md +67 -0
  297. package/.versions/2.0.2/references/fleet-coordination-patterns.md +171 -0
  298. package/.versions/2.0.2/references/observability-checklist.md +91 -0
  299. package/.versions/2.0.2/references/orchestration-patterns.md +370 -0
  300. package/.versions/2.0.2/references/performance-checklist.md +153 -0
  301. package/.versions/2.0.2/references/prompting-patterns.md +380 -0
  302. package/.versions/2.0.2/references/security-checklist.md +179 -0
  303. package/.versions/2.0.2/references/testing-patterns.md +236 -0
  304. package/.versions/2.0.2/references/workflow-authoring.md +304 -0
  305. package/.versions/2.0.2/scripts/codex-conductor.ts +41 -0
  306. package/.versions/2.0.2/scripts/codex-remote-control.ts +167 -0
  307. package/.versions/2.0.2/scripts/coms-claude-bridge.ts +411 -0
  308. package/.versions/2.0.2/scripts/coms-cli.ts +484 -0
  309. package/.versions/2.0.2/scripts/coms-hermes-bridge.ts +413 -0
  310. package/.versions/2.0.2/scripts/fleet.ts +199 -0
  311. package/.versions/2.0.2/scripts/flow.ts +137 -0
  312. package/.versions/2.0.2/scripts/hermes-monitor-capability-runner.ts +25 -0
  313. package/.versions/2.0.2/scripts/hermes-monitor-scenario.ts +474 -0
  314. package/.versions/2.0.2/scripts/hermes-watchdog-capability-probe.ts +45 -0
  315. package/.versions/2.0.2/scripts/install-hermes-plugin.sh +180 -0
  316. package/.versions/2.0.2/scripts/lib/claude-bridge-core.ts +210 -0
  317. package/.versions/2.0.2/scripts/lib/codex-conductor.ts +88 -0
  318. package/.versions/2.0.2/scripts/lib/codex-remote-control.ts +482 -0
  319. package/.versions/2.0.2/scripts/lib/coms-envelope.ts +582 -0
  320. package/.versions/2.0.2/scripts/lib/fake-herdr-server.ts +88 -0
  321. package/.versions/2.0.2/scripts/lib/fleet-command.ts +270 -0
  322. package/.versions/2.0.2/scripts/lib/flow-command.ts +93 -0
  323. package/.versions/2.0.2/scripts/lib/flow-maintenance.ts +230 -0
  324. package/.versions/2.0.2/scripts/lib/herdr-layout.ts +281 -0
  325. package/.versions/2.0.2/scripts/lib/hermes-bridge-core.ts +241 -0
  326. package/.versions/2.0.2/scripts/lib/hermes-monitor-events.ts +1 -0
  327. package/.versions/2.0.2/scripts/lib/hermes-monitor-herdr.ts +2 -0
  328. package/.versions/2.0.2/scripts/lib/hermes-monitor-model.ts +3 -0
  329. package/.versions/2.0.2/scripts/lib/hermes-monitor-registry.ts +2 -0
  330. package/.versions/2.0.2/scripts/lib/hermes-monitor-socket.ts +2 -0
  331. package/.versions/2.0.2/scripts/lib/hermes-monitor-store.ts +2 -0
  332. package/.versions/2.0.2/scripts/lib/monitor-env.ts +146 -0
  333. package/.versions/2.0.2/scripts/lib/peer-launch.ts +318 -0
  334. package/.versions/2.0.2/scripts/lib/persona-banner.ts +62 -0
  335. package/.versions/2.0.2/scripts/lib/spawn-stagger.ts +101 -0
  336. package/.versions/2.0.2/scripts/lib/team-project.ts +213 -0
  337. package/.versions/2.0.2/scripts/lib/team-snapshot.ts +147 -0
  338. package/.versions/2.0.2/scripts/peer-banner.ts +40 -0
  339. package/.versions/2.0.2/scripts/peer-launch.ts +259 -0
  340. package/.versions/2.0.2/scripts/team-snapshot.ts +237 -0
  341. package/.versions/2.0.2/scripts/team-up.ts +406 -0
  342. package/.versions/2.0.2/scripts/workflows/lib/agent-phase.ts +132 -0
  343. package/.versions/2.0.2/scripts/workflows/lib/changes.ts +61 -0
  344. package/.versions/2.0.2/scripts/workflows/lib/debate.ts +149 -0
  345. package/.versions/2.0.2/scripts/workflows/lib/env.ts +34 -0
  346. package/.versions/2.0.2/scripts/workflows/lib/envelopes.ts +169 -0
  347. package/.versions/2.0.2/scripts/workflows/lib/gates.ts +81 -0
  348. package/.versions/2.0.2/scripts/workflows/lib/git.ts +96 -0
  349. package/.versions/2.0.2/scripts/workflows/lib/merge.ts +95 -0
  350. package/.versions/2.0.2/scripts/workflows/lib/model-visibility.ts +92 -0
  351. package/.versions/2.0.2/scripts/workflows/lib/permissions.ts +130 -0
  352. package/.versions/2.0.2/scripts/workflows/lib/personas.ts +54 -0
  353. package/.versions/2.0.2/scripts/workflows/lib/poll.ts +86 -0
  354. package/.versions/2.0.2/scripts/workflows/lib/quality.ts +64 -0
  355. package/.versions/2.0.2/scripts/workflows/lib/run.ts +108 -0
  356. package/.versions/2.0.2/scripts/workflows/lib/trace.ts +34 -0
  357. package/.versions/2.0.2/scripts/workflows/lib/voices.ts +125 -0
  358. package/.versions/2.0.2/scripts/workflows/lib/writer-lease.ts +112 -0
  359. package/.versions/2.0.2/scripts/workflows/tsconfig.json +22 -0
  360. package/.versions/2.0.2/scripts/workflows/wf-build-test.ts +61 -0
  361. package/.versions/2.0.2/scripts/workflows/wf-debate.ts +87 -0
  362. package/.versions/2.0.2/scripts/workflows/wf-document.ts +50 -0
  363. package/.versions/2.0.2/scripts/workflows/wf-poll.ts +95 -0
  364. package/.versions/2.0.2/scripts/workflows/wf-quality.ts +20 -0
  365. package/.versions/2.0.2/scripts/workflows/wf-scout.ts +38 -0
  366. package/.versions/2.0.2/skills/_internal/grilling.md +59 -0
  367. package/.versions/2.0.2/skills/browser-testing-with-devtools/SKILL.md +351 -0
  368. package/.versions/2.0.2/skills/code-review-and-quality/SKILL.md +381 -0
  369. package/.versions/2.0.2/skills/compound-learning/SKILL.md +137 -0
  370. package/.versions/2.0.2/skills/context-engineering/SKILL.md +291 -0
  371. package/.versions/2.0.2/skills/deprecation-and-migration/SKILL.md +206 -0
  372. package/.versions/2.0.2/skills/designing-agents/SKILL.md +394 -0
  373. package/.versions/2.0.2/skills/designing-agents/pi-harness-authoring.md +222 -0
  374. package/.versions/2.0.2/skills/drafting-workflows/SKILL.md +143 -0
  375. package/.versions/2.0.2/skills/drafting-workflows/scripts/make-workflow.ts +177 -0
  376. package/.versions/2.0.2/skills/frontend-ui-engineering/SKILL.md +328 -0
  377. package/.versions/2.0.2/skills/git-workflow-and-versioning/SKILL.md +316 -0
  378. package/.versions/2.0.2/skills/idea-refine/SKILL.md +182 -0
  379. package/.versions/2.0.2/skills/idea-refine/examples.md +238 -0
  380. package/.versions/2.0.2/skills/idea-refine/frameworks.md +99 -0
  381. package/.versions/2.0.2/skills/idea-refine/refinement-criteria.md +113 -0
  382. package/.versions/2.0.2/skills/idea-refine/scripts/idea-refine.sh +15 -0
  383. package/.versions/2.0.2/skills/incremental-implementation/SKILL.md +298 -0
  384. package/.versions/2.0.2/skills/interview-me/SKILL.md +226 -0
  385. package/.versions/2.0.2/skills/orchestration-verification/SKILL.md +181 -0
  386. package/.versions/2.0.2/skills/peer-coms/SKILL.md +90 -0
  387. package/.versions/2.0.2/skills/performance-optimization/SKILL.md +350 -0
  388. package/.versions/2.0.2/skills/planning-and-task-breakdown/SKILL.md +265 -0
  389. package/.versions/2.0.2/skills/security-and-hardening/SKILL.md +461 -0
  390. package/.versions/2.0.2/skills/spec-driven-development/SKILL.md +256 -0
  391. package/.versions/2.0.2/skills/using-agent-skills/SKILL.md +197 -0
  392. package/.versions/2.0.2/systemd/user/agent-fleet-codex-remote-control.service.in +23 -0
  393. package/.versions/2.0.2/vendor/agent-skills-upstream/LICENSE +21 -0
  394. package/.versions/2.0.2/vendor/agent-skills-upstream/README.md +11 -0
  395. package/.versions/2.0.2/vendor/agent-skills-upstream/skills/api-and-interface-design/SKILL.md +294 -0
  396. package/.versions/2.0.2/vendor/agent-skills-upstream/skills/browser-testing-with-devtools/SKILL.md +317 -0
  397. package/.versions/2.0.2/vendor/agent-skills-upstream/skills/ci-cd-and-automation/SKILL.md +390 -0
  398. package/.versions/2.0.2/vendor/agent-skills-upstream/skills/code-review-and-quality/SKILL.md +396 -0
  399. package/.versions/2.0.2/vendor/agent-skills-upstream/skills/code-simplification/SKILL.md +331 -0
  400. package/.versions/2.0.2/vendor/agent-skills-upstream/skills/context-engineering/SKILL.md +289 -0
  401. package/.versions/2.0.2/vendor/agent-skills-upstream/skills/debugging-and-error-recovery/SKILL.md +300 -0
  402. package/.versions/2.0.2/vendor/agent-skills-upstream/skills/deprecation-and-migration/SKILL.md +247 -0
  403. package/.versions/2.0.2/vendor/agent-skills-upstream/skills/documentation-and-adrs/SKILL.md +278 -0
  404. package/.versions/2.0.2/vendor/agent-skills-upstream/skills/doubt-driven-development/SKILL.md +243 -0
  405. package/.versions/2.0.2/vendor/agent-skills-upstream/skills/frontend-ui-engineering/SKILL.md +328 -0
  406. package/.versions/2.0.2/vendor/agent-skills-upstream/skills/git-workflow-and-versioning/SKILL.md +355 -0
  407. package/.versions/2.0.2/vendor/agent-skills-upstream/skills/idea-refine/SKILL.md +178 -0
  408. package/.versions/2.0.2/vendor/agent-skills-upstream/skills/idea-refine/examples.md +238 -0
  409. package/.versions/2.0.2/vendor/agent-skills-upstream/skills/idea-refine/frameworks.md +99 -0
  410. package/.versions/2.0.2/vendor/agent-skills-upstream/skills/idea-refine/refinement-criteria.md +113 -0
  411. package/.versions/2.0.2/vendor/agent-skills-upstream/skills/idea-refine/scripts/idea-refine.sh +15 -0
  412. package/.versions/2.0.2/vendor/agent-skills-upstream/skills/incremental-implementation/SKILL.md +249 -0
  413. package/.versions/2.0.2/vendor/agent-skills-upstream/skills/interview-me/SKILL.md +225 -0
  414. package/.versions/2.0.2/vendor/agent-skills-upstream/skills/observability-and-instrumentation/SKILL.md +203 -0
  415. package/.versions/2.0.2/vendor/agent-skills-upstream/skills/performance-optimization/SKILL.md +350 -0
  416. package/.versions/2.0.2/vendor/agent-skills-upstream/skills/planning-and-task-breakdown/SKILL.md +234 -0
  417. package/.versions/2.0.2/vendor/agent-skills-upstream/skills/security-and-hardening/SKILL.md +467 -0
  418. package/.versions/2.0.2/vendor/agent-skills-upstream/skills/shipping-and-launch/SKILL.md +310 -0
  419. package/.versions/2.0.2/vendor/agent-skills-upstream/skills/source-driven-development/SKILL.md +194 -0
  420. package/.versions/2.0.2/vendor/agent-skills-upstream/skills/spec-driven-development/SKILL.md +206 -0
  421. package/.versions/2.0.2/vendor/agent-skills-upstream/skills/test-driven-development/SKILL.md +383 -0
  422. package/.versions/2.0.2/vendor/agent-skills-upstream/skills/using-agent-skills/SKILL.md +191 -0
  423. package/CHANGELOG.md +7 -0
  424. package/agents/planner.md +40 -8
  425. package/bin/catalog/harness-runtime-closure.json +0 -4
  426. package/bin/lib/apply.js +65 -2
  427. package/bin/lib/doctor.js +143 -1
  428. package/bin/lib/plan.js +2 -0
  429. package/bin/lib/transaction.js +14 -1
  430. package/bin/lib/validate-overrides.js +20 -0
  431. package/bin/lib/verify.js +22 -1
  432. package/codex/CONDUCTOR.md +1 -1
  433. package/docs/agent-fleet-setup.md +8 -3
  434. package/docs/codex-remote-conductor.md +3 -3
  435. package/docs/pi-extensions.md +5 -0
  436. package/docs/workflows.md +7 -0
  437. package/install-manifest.json +84 -9
  438. package/justfile +2 -0
  439. package/manifest-meta.json +37 -5
  440. package/node_modules/yaml/LICENSE +13 -0
  441. package/node_modules/yaml/README.md +172 -0
  442. package/node_modules/yaml/bin.mjs +11 -0
  443. package/node_modules/yaml/browser/dist/compose/compose-collection.js +88 -0
  444. package/node_modules/yaml/browser/dist/compose/compose-doc.js +43 -0
  445. package/node_modules/yaml/browser/dist/compose/compose-node.js +109 -0
  446. package/node_modules/yaml/browser/dist/compose/compose-scalar.js +86 -0
  447. package/node_modules/yaml/browser/dist/compose/composer.js +219 -0
  448. package/node_modules/yaml/browser/dist/compose/resolve-block-map.js +115 -0
  449. package/node_modules/yaml/browser/dist/compose/resolve-block-scalar.js +198 -0
  450. package/node_modules/yaml/browser/dist/compose/resolve-block-seq.js +49 -0
  451. package/node_modules/yaml/browser/dist/compose/resolve-end.js +37 -0
  452. package/node_modules/yaml/browser/dist/compose/resolve-flow-collection.js +207 -0
  453. package/node_modules/yaml/browser/dist/compose/resolve-flow-scalar.js +225 -0
  454. package/node_modules/yaml/browser/dist/compose/resolve-props.js +146 -0
  455. package/node_modules/yaml/browser/dist/compose/util-contains-newline.js +34 -0
  456. package/node_modules/yaml/browser/dist/compose/util-empty-scalar-position.js +26 -0
  457. package/node_modules/yaml/browser/dist/compose/util-flow-indent-check.js +15 -0
  458. package/node_modules/yaml/browser/dist/compose/util-map-includes.js +13 -0
  459. package/node_modules/yaml/browser/dist/doc/Document.js +335 -0
  460. package/node_modules/yaml/browser/dist/doc/anchors.js +71 -0
  461. package/node_modules/yaml/browser/dist/doc/applyReviver.js +55 -0
  462. package/node_modules/yaml/browser/dist/doc/createNode.js +88 -0
  463. package/node_modules/yaml/browser/dist/doc/directives.js +176 -0
  464. package/node_modules/yaml/browser/dist/errors.js +57 -0
  465. package/node_modules/yaml/browser/dist/index.js +17 -0
  466. package/node_modules/yaml/browser/dist/log.js +11 -0
  467. package/node_modules/yaml/browser/dist/nodes/Alias.js +116 -0
  468. package/node_modules/yaml/browser/dist/nodes/Collection.js +147 -0
  469. package/node_modules/yaml/browser/dist/nodes/Node.js +38 -0
  470. package/node_modules/yaml/browser/dist/nodes/Pair.js +36 -0
  471. package/node_modules/yaml/browser/dist/nodes/Scalar.js +24 -0
  472. package/node_modules/yaml/browser/dist/nodes/YAMLMap.js +144 -0
  473. package/node_modules/yaml/browser/dist/nodes/YAMLSeq.js +113 -0
  474. package/node_modules/yaml/browser/dist/nodes/addPairToJSMap.js +63 -0
  475. package/node_modules/yaml/browser/dist/nodes/identity.js +36 -0
  476. package/node_modules/yaml/browser/dist/nodes/toJS.js +37 -0
  477. package/node_modules/yaml/browser/dist/parse/cst-scalar.js +214 -0
  478. package/node_modules/yaml/browser/dist/parse/cst-stringify.js +61 -0
  479. package/node_modules/yaml/browser/dist/parse/cst-visit.js +97 -0
  480. package/node_modules/yaml/browser/dist/parse/cst.js +98 -0
  481. package/node_modules/yaml/browser/dist/parse/lexer.js +721 -0
  482. package/node_modules/yaml/browser/dist/parse/line-counter.js +39 -0
  483. package/node_modules/yaml/browser/dist/parse/parser.js +975 -0
  484. package/node_modules/yaml/browser/dist/public-api.js +102 -0
  485. package/node_modules/yaml/browser/dist/schema/Schema.js +37 -0
  486. package/node_modules/yaml/browser/dist/schema/common/map.js +17 -0
  487. package/node_modules/yaml/browser/dist/schema/common/null.js +15 -0
  488. package/node_modules/yaml/browser/dist/schema/common/seq.js +17 -0
  489. package/node_modules/yaml/browser/dist/schema/common/string.js +14 -0
  490. package/node_modules/yaml/browser/dist/schema/core/bool.js +19 -0
  491. package/node_modules/yaml/browser/dist/schema/core/float.js +43 -0
  492. package/node_modules/yaml/browser/dist/schema/core/int.js +38 -0
  493. package/node_modules/yaml/browser/dist/schema/core/schema.js +23 -0
  494. package/node_modules/yaml/browser/dist/schema/json/schema.js +62 -0
  495. package/node_modules/yaml/browser/dist/schema/tags.js +96 -0
  496. package/node_modules/yaml/browser/dist/schema/yaml-1.1/binary.js +58 -0
  497. package/node_modules/yaml/browser/dist/schema/yaml-1.1/bool.js +26 -0
  498. package/node_modules/yaml/browser/dist/schema/yaml-1.1/float.js +46 -0
  499. package/node_modules/yaml/browser/dist/schema/yaml-1.1/int.js +71 -0
  500. package/node_modules/yaml/browser/dist/schema/yaml-1.1/merge.js +67 -0
  501. package/node_modules/yaml/browser/dist/schema/yaml-1.1/omap.js +74 -0
  502. package/node_modules/yaml/browser/dist/schema/yaml-1.1/pairs.js +78 -0
  503. package/node_modules/yaml/browser/dist/schema/yaml-1.1/schema.js +39 -0
  504. package/node_modules/yaml/browser/dist/schema/yaml-1.1/set.js +93 -0
  505. package/node_modules/yaml/browser/dist/schema/yaml-1.1/timestamp.js +101 -0
  506. package/node_modules/yaml/browser/dist/stringify/foldFlowLines.js +146 -0
  507. package/node_modules/yaml/browser/dist/stringify/stringify.js +129 -0
  508. package/node_modules/yaml/browser/dist/stringify/stringifyCollection.js +153 -0
  509. package/node_modules/yaml/browser/dist/stringify/stringifyComment.js +20 -0
  510. package/node_modules/yaml/browser/dist/stringify/stringifyDocument.js +85 -0
  511. package/node_modules/yaml/browser/dist/stringify/stringifyNumber.js +25 -0
  512. package/node_modules/yaml/browser/dist/stringify/stringifyPair.js +150 -0
  513. package/node_modules/yaml/browser/dist/stringify/stringifyString.js +336 -0
  514. package/node_modules/yaml/browser/dist/util.js +11 -0
  515. package/node_modules/yaml/browser/dist/visit.js +233 -0
  516. package/node_modules/yaml/browser/index.js +5 -0
  517. package/node_modules/yaml/browser/package.json +3 -0
  518. package/node_modules/yaml/dist/cli.d.ts +8 -0
  519. package/node_modules/yaml/dist/cli.mjs +201 -0
  520. package/node_modules/yaml/dist/compose/compose-collection.d.ts +11 -0
  521. package/node_modules/yaml/dist/compose/compose-collection.js +90 -0
  522. package/node_modules/yaml/dist/compose/compose-doc.d.ts +7 -0
  523. package/node_modules/yaml/dist/compose/compose-doc.js +45 -0
  524. package/node_modules/yaml/dist/compose/compose-node.d.ts +29 -0
  525. package/node_modules/yaml/dist/compose/compose-node.js +112 -0
  526. package/node_modules/yaml/dist/compose/compose-scalar.d.ts +5 -0
  527. package/node_modules/yaml/dist/compose/compose-scalar.js +88 -0
  528. package/node_modules/yaml/dist/compose/composer.d.ts +63 -0
  529. package/node_modules/yaml/dist/compose/composer.js +224 -0
  530. package/node_modules/yaml/dist/compose/resolve-block-map.d.ts +6 -0
  531. package/node_modules/yaml/dist/compose/resolve-block-map.js +117 -0
  532. package/node_modules/yaml/dist/compose/resolve-block-scalar.d.ts +11 -0
  533. package/node_modules/yaml/dist/compose/resolve-block-scalar.js +200 -0
  534. package/node_modules/yaml/dist/compose/resolve-block-seq.d.ts +6 -0
  535. package/node_modules/yaml/dist/compose/resolve-block-seq.js +51 -0
  536. package/node_modules/yaml/dist/compose/resolve-end.d.ts +6 -0
  537. package/node_modules/yaml/dist/compose/resolve-end.js +39 -0
  538. package/node_modules/yaml/dist/compose/resolve-flow-collection.d.ts +7 -0
  539. package/node_modules/yaml/dist/compose/resolve-flow-collection.js +209 -0
  540. package/node_modules/yaml/dist/compose/resolve-flow-scalar.d.ts +10 -0
  541. package/node_modules/yaml/dist/compose/resolve-flow-scalar.js +227 -0
  542. package/node_modules/yaml/dist/compose/resolve-props.d.ts +23 -0
  543. package/node_modules/yaml/dist/compose/resolve-props.js +148 -0
  544. package/node_modules/yaml/dist/compose/util-contains-newline.d.ts +2 -0
  545. package/node_modules/yaml/dist/compose/util-contains-newline.js +36 -0
  546. package/node_modules/yaml/dist/compose/util-empty-scalar-position.d.ts +2 -0
  547. package/node_modules/yaml/dist/compose/util-empty-scalar-position.js +28 -0
  548. package/node_modules/yaml/dist/compose/util-flow-indent-check.d.ts +3 -0
  549. package/node_modules/yaml/dist/compose/util-flow-indent-check.js +17 -0
  550. package/node_modules/yaml/dist/compose/util-map-includes.d.ts +4 -0
  551. package/node_modules/yaml/dist/compose/util-map-includes.js +15 -0
  552. package/node_modules/yaml/dist/doc/Document.d.ts +141 -0
  553. package/node_modules/yaml/dist/doc/Document.js +337 -0
  554. package/node_modules/yaml/dist/doc/anchors.d.ts +24 -0
  555. package/node_modules/yaml/dist/doc/anchors.js +76 -0
  556. package/node_modules/yaml/dist/doc/applyReviver.d.ts +9 -0
  557. package/node_modules/yaml/dist/doc/applyReviver.js +57 -0
  558. package/node_modules/yaml/dist/doc/createNode.d.ts +17 -0
  559. package/node_modules/yaml/dist/doc/createNode.js +90 -0
  560. package/node_modules/yaml/dist/doc/directives.d.ts +49 -0
  561. package/node_modules/yaml/dist/doc/directives.js +178 -0
  562. package/node_modules/yaml/dist/errors.d.ts +21 -0
  563. package/node_modules/yaml/dist/errors.js +62 -0
  564. package/node_modules/yaml/dist/index.d.ts +25 -0
  565. package/node_modules/yaml/dist/index.js +50 -0
  566. package/node_modules/yaml/dist/log.d.ts +3 -0
  567. package/node_modules/yaml/dist/log.js +19 -0
  568. package/node_modules/yaml/dist/nodes/Alias.d.ts +29 -0
  569. package/node_modules/yaml/dist/nodes/Alias.js +118 -0
  570. package/node_modules/yaml/dist/nodes/Collection.d.ts +73 -0
  571. package/node_modules/yaml/dist/nodes/Collection.js +151 -0
  572. package/node_modules/yaml/dist/nodes/Node.d.ts +53 -0
  573. package/node_modules/yaml/dist/nodes/Node.js +40 -0
  574. package/node_modules/yaml/dist/nodes/Pair.d.ts +22 -0
  575. package/node_modules/yaml/dist/nodes/Pair.js +39 -0
  576. package/node_modules/yaml/dist/nodes/Scalar.d.ts +47 -0
  577. package/node_modules/yaml/dist/nodes/Scalar.js +27 -0
  578. package/node_modules/yaml/dist/nodes/YAMLMap.d.ts +53 -0
  579. package/node_modules/yaml/dist/nodes/YAMLMap.js +147 -0
  580. package/node_modules/yaml/dist/nodes/YAMLSeq.d.ts +60 -0
  581. package/node_modules/yaml/dist/nodes/YAMLSeq.js +115 -0
  582. package/node_modules/yaml/dist/nodes/addPairToJSMap.d.ts +4 -0
  583. package/node_modules/yaml/dist/nodes/addPairToJSMap.js +65 -0
  584. package/node_modules/yaml/dist/nodes/identity.d.ts +23 -0
  585. package/node_modules/yaml/dist/nodes/identity.js +53 -0
  586. package/node_modules/yaml/dist/nodes/toJS.d.ts +29 -0
  587. package/node_modules/yaml/dist/nodes/toJS.js +39 -0
  588. package/node_modules/yaml/dist/options.d.ts +350 -0
  589. package/node_modules/yaml/dist/parse/cst-scalar.d.ts +64 -0
  590. package/node_modules/yaml/dist/parse/cst-scalar.js +218 -0
  591. package/node_modules/yaml/dist/parse/cst-stringify.d.ts +8 -0
  592. package/node_modules/yaml/dist/parse/cst-stringify.js +63 -0
  593. package/node_modules/yaml/dist/parse/cst-visit.d.ts +39 -0
  594. package/node_modules/yaml/dist/parse/cst-visit.js +99 -0
  595. package/node_modules/yaml/dist/parse/cst.d.ts +109 -0
  596. package/node_modules/yaml/dist/parse/cst.js +112 -0
  597. package/node_modules/yaml/dist/parse/lexer.d.ts +87 -0
  598. package/node_modules/yaml/dist/parse/lexer.js +723 -0
  599. package/node_modules/yaml/dist/parse/line-counter.d.ts +22 -0
  600. package/node_modules/yaml/dist/parse/line-counter.js +41 -0
  601. package/node_modules/yaml/dist/parse/parser.d.ts +84 -0
  602. package/node_modules/yaml/dist/parse/parser.js +980 -0
  603. package/node_modules/yaml/dist/public-api.d.ts +44 -0
  604. package/node_modules/yaml/dist/public-api.js +107 -0
  605. package/node_modules/yaml/dist/schema/Schema.d.ts +17 -0
  606. package/node_modules/yaml/dist/schema/Schema.js +39 -0
  607. package/node_modules/yaml/dist/schema/common/map.d.ts +2 -0
  608. package/node_modules/yaml/dist/schema/common/map.js +19 -0
  609. package/node_modules/yaml/dist/schema/common/null.d.ts +4 -0
  610. package/node_modules/yaml/dist/schema/common/null.js +17 -0
  611. package/node_modules/yaml/dist/schema/common/seq.d.ts +2 -0
  612. package/node_modules/yaml/dist/schema/common/seq.js +19 -0
  613. package/node_modules/yaml/dist/schema/common/string.d.ts +2 -0
  614. package/node_modules/yaml/dist/schema/common/string.js +16 -0
  615. package/node_modules/yaml/dist/schema/core/bool.d.ts +4 -0
  616. package/node_modules/yaml/dist/schema/core/bool.js +21 -0
  617. package/node_modules/yaml/dist/schema/core/float.d.ts +4 -0
  618. package/node_modules/yaml/dist/schema/core/float.js +47 -0
  619. package/node_modules/yaml/dist/schema/core/int.d.ts +4 -0
  620. package/node_modules/yaml/dist/schema/core/int.js +42 -0
  621. package/node_modules/yaml/dist/schema/core/schema.d.ts +1 -0
  622. package/node_modules/yaml/dist/schema/core/schema.js +25 -0
  623. package/node_modules/yaml/dist/schema/json/schema.d.ts +2 -0
  624. package/node_modules/yaml/dist/schema/json/schema.js +64 -0
  625. package/node_modules/yaml/dist/schema/json-schema.d.ts +69 -0
  626. package/node_modules/yaml/dist/schema/tags.d.ts +48 -0
  627. package/node_modules/yaml/dist/schema/tags.js +99 -0
  628. package/node_modules/yaml/dist/schema/types.d.ts +92 -0
  629. package/node_modules/yaml/dist/schema/yaml-1.1/binary.d.ts +2 -0
  630. package/node_modules/yaml/dist/schema/yaml-1.1/binary.js +70 -0
  631. package/node_modules/yaml/dist/schema/yaml-1.1/bool.d.ts +7 -0
  632. package/node_modules/yaml/dist/schema/yaml-1.1/bool.js +29 -0
  633. package/node_modules/yaml/dist/schema/yaml-1.1/float.d.ts +4 -0
  634. package/node_modules/yaml/dist/schema/yaml-1.1/float.js +50 -0
  635. package/node_modules/yaml/dist/schema/yaml-1.1/int.d.ts +5 -0
  636. package/node_modules/yaml/dist/schema/yaml-1.1/int.js +76 -0
  637. package/node_modules/yaml/dist/schema/yaml-1.1/merge.d.ts +9 -0
  638. package/node_modules/yaml/dist/schema/yaml-1.1/merge.js +71 -0
  639. package/node_modules/yaml/dist/schema/yaml-1.1/omap.d.ts +22 -0
  640. package/node_modules/yaml/dist/schema/yaml-1.1/omap.js +77 -0
  641. package/node_modules/yaml/dist/schema/yaml-1.1/pairs.d.ts +10 -0
  642. package/node_modules/yaml/dist/schema/yaml-1.1/pairs.js +82 -0
  643. package/node_modules/yaml/dist/schema/yaml-1.1/schema.d.ts +1 -0
  644. package/node_modules/yaml/dist/schema/yaml-1.1/schema.js +41 -0
  645. package/node_modules/yaml/dist/schema/yaml-1.1/set.d.ts +28 -0
  646. package/node_modules/yaml/dist/schema/yaml-1.1/set.js +96 -0
  647. package/node_modules/yaml/dist/schema/yaml-1.1/timestamp.d.ts +6 -0
  648. package/node_modules/yaml/dist/schema/yaml-1.1/timestamp.js +105 -0
  649. package/node_modules/yaml/dist/stringify/foldFlowLines.d.ts +34 -0
  650. package/node_modules/yaml/dist/stringify/foldFlowLines.js +151 -0
  651. package/node_modules/yaml/dist/stringify/stringify.d.ts +21 -0
  652. package/node_modules/yaml/dist/stringify/stringify.js +132 -0
  653. package/node_modules/yaml/dist/stringify/stringifyCollection.d.ts +17 -0
  654. package/node_modules/yaml/dist/stringify/stringifyCollection.js +155 -0
  655. package/node_modules/yaml/dist/stringify/stringifyComment.d.ts +10 -0
  656. package/node_modules/yaml/dist/stringify/stringifyComment.js +24 -0
  657. package/node_modules/yaml/dist/stringify/stringifyDocument.d.ts +4 -0
  658. package/node_modules/yaml/dist/stringify/stringifyDocument.js +87 -0
  659. package/node_modules/yaml/dist/stringify/stringifyNumber.d.ts +2 -0
  660. package/node_modules/yaml/dist/stringify/stringifyNumber.js +27 -0
  661. package/node_modules/yaml/dist/stringify/stringifyPair.d.ts +3 -0
  662. package/node_modules/yaml/dist/stringify/stringifyPair.js +152 -0
  663. package/node_modules/yaml/dist/stringify/stringifyString.d.ts +9 -0
  664. package/node_modules/yaml/dist/stringify/stringifyString.js +338 -0
  665. package/node_modules/yaml/dist/test-events.d.ts +4 -0
  666. package/node_modules/yaml/dist/test-events.js +134 -0
  667. package/node_modules/yaml/dist/util.d.ts +16 -0
  668. package/node_modules/yaml/dist/util.js +28 -0
  669. package/node_modules/yaml/dist/visit.d.ts +102 -0
  670. package/node_modules/yaml/dist/visit.js +236 -0
  671. package/node_modules/yaml/package.json +97 -0
  672. package/node_modules/yaml/util.js +2 -0
  673. package/package.json +4 -3
  674. package/references/communication-contract.md +26 -0
  675. package/references/fleet-coordination-patterns.md +20 -0
  676. package/references/orchestration-patterns.md +2 -2
  677. package/references/workflow-authoring.md +1 -1
  678. package/scripts/fleet.ts +2 -1
  679. package/scripts/flow.ts +23 -7
  680. package/scripts/lib/codex-remote-control.ts +3 -1
  681. package/scripts/lib/flow-command.ts +19 -3
  682. package/scripts/workflows/lib/agent-phase.ts +18 -4
  683. package/scripts/workflows/lib/debate.ts +149 -0
  684. package/scripts/workflows/lib/envelopes.ts +32 -4
  685. package/scripts/workflows/lib/merge.ts +95 -0
  686. package/scripts/workflows/lib/model-visibility.ts +92 -0
  687. package/scripts/workflows/lib/personas.ts +10 -0
  688. package/scripts/workflows/lib/poll.ts +86 -0
  689. package/scripts/workflows/lib/run.ts +2 -0
  690. package/scripts/workflows/lib/voices.ts +125 -0
  691. package/scripts/workflows/lib/writer-lease.ts +112 -0
  692. package/scripts/workflows/wf-debate.ts +87 -0
  693. package/scripts/workflows/wf-poll.ts +95 -0
  694. package/skills/drafting-workflows/SKILL.md +1 -1
  695. package/skills/planning-and-task-breakdown/SKILL.md +2 -0
@@ -0,0 +1,170 @@
1
+ # Codex Remote-Control Conductor
2
+
3
+ > **Experimental; verified with Codex CLI 0.144.6 on Linux.** The daemon is user-systemd-managed on the headless host, while manual pairing happens in the operator's interactive terminal. Revalidate the live gate after any Codex minor-version or mobile-client behavior change.
4
+
5
+ The conductor is an outbound-initiated, singleton Codex remote-control service with a visible Herdr **control** pane. The pane displays user-systemd requested state; it never starts, stops, or owns the daemon. Based on the verified design boundary, closing its workspace leaves the enabled service running. The package source contract is [`../codex/CONDUCTOR.md`](../codex/CONDUCTOR.md); workspace setup installs its managed copy at `.pi/agent-fleet/codex/CONDUCTOR.md`. Hermes/Telegram remains the inbound `ask_user` route.
6
+
7
+ ## Supported facts and limits
8
+
9
+ - The pilot was validated with `codex-cli 0.144.6`. Public policy supports **only `0.144.x`**. Resolve the local binary with `command -v codex`; normal lifecycle state changes run a capability preflight, and `0.145.x` or later fail closed until reviewed.
10
+ - The confirmed remote-control subcommands are `start`, `stop`, and `pair`.
11
+ - The only approval modes are `untrusted`, `on-request`, and `never`. The only sandbox modes are `read-only`, `workspace-write`, and `danger-full-access`. **There is no `writes` mode.**
12
+ - The verified posture is `on-request` with `workspace-write`. The runtime-only container is `$HOME/.local/state/agent-fleet/codex-conductor`, outside every checkout; wrapper commands execute from its `workspace` child. Codex 0.144.x/Android may expose the container parent as writable, but repository source and the managed `.pi/agent-fleet/codex/CONDUCTOR.md` remain outside it. Setup places a managed `workspace/AGENTS.md` copy inside the container. The helper requests the configured `~/.pi/coms` directory as the only extra writable root. The mobile client's managed permission profile still requires a visible one-command escalation for `send`; this approval is mandatory. A remote thread that reports `approval_policy=never` must not delegate.
13
+ - Codex documents neither a foreground daemon lifecycle nor a websocket address/port. Do not configure, probe, document, or depend on a websocket port, PID, or health endpoint.
14
+ - `systemd` state is not daemon health: `active (exited)` means that the requested start command succeeded, not that a paired client is usable.
15
+ - Remote control is outbound-initiated and exclusive **as far as verified for this pilot**. It does not create inbound questions; use Hermes/Telegram for inbound `ask_user`.
16
+
17
+ Both Codex and Hermes are external conductors. Their contracts and human approvals are advisory safeguards outside Pi's damage-control harness; Pi's guardrails and an OS command allowlist do not technically constrain either process. See [Hermes and coms](coms-hermes-bridge.md).
18
+
19
+ ## Before touching the host
20
+
21
+ 1. Confirm the operator accepts the singleton/global-stop limitation: `stop` can affect the remote-control daemon rather than a process systemd can prove it owns.
22
+ 2. Use a Node runtime that supports `--experimental-strip-types` (Node `22.6+`) for these optional TypeScript recipes. Setup persists the exact `process.execPath` for systemd, and team-up passes the same absolute binary to the control pane.
23
+ 3. Close Codex Desktop, editor-owned Codex app servers, and interactive Codex sessions for this host before starting the headless service. The remote-control host is singleton; a desktop/app-server owner can make headless `start` fail with `connection is errored`. Do not mix Mode B with the community Linux desktop workaround.
24
+ 4. Set global `approval_policy = "on-request"` in `~/.codex/config.toml` after making a private backup. The Android client applies this global value to new threads and can override daemon-only config. This affects all local Codex sessions; the lifecycle preflight verifies the effective redacted `codex doctor --json` value and refuses `never`.
25
+ 5. Keep pairing codes, credentials, auth files, remote-control URLs, approval transcripts, and screenshots **out of Git, documentation, plans, test fixtures, and logs**. Pairing output stays in the operator's terminal.
26
+ 6. Run the non-mutating compatibility evidence. It confirms only advertised static capabilities and configured approval posture; it does not prove daemon ownership, pairing, session root, contract loading, approval delivery, or health.
27
+
28
+ ```bash
29
+ CODEX="$(command -v codex)"
30
+ "$CODEX" --version
31
+ "$CODEX" remote-control --help
32
+ "$CODEX" remote-control start --help
33
+ "$CODEX" remote-control stop --help
34
+ "$CODEX" remote-control pair --help
35
+ "$CODEX" doctor --json # redacted; preflight requires approval policy OnRequest
36
+ node --experimental-strip-types scripts/codex-remote-control.ts preflight --codex-bin "$CODEX"
37
+ ```
38
+
39
+ **Compatibility stop condition:** if the version is not `0.144.x`, a required subcommand is absent, or `on-request` plus `workspace-write` cannot be demonstrated for this remote-control path, stop. Do not use guessed flags, a port, or a fallback launcher.
40
+
41
+ The loading mechanism uses a managed runtime contract at `$HOME/.local/state/agent-fleet/codex-conductor/workspace/AGENTS.md`, copied from `.pi/agent-fleet/codex/CONDUCTOR.md` in an installed workspace (or from package-source `codex/CONDUCTOR.md` in an Agent Fleet development checkout). A fresh thread must prove that managed copy was loaded and that any mobile writable root remains inside the external user-state runtime container; cwd and environment markers alone remain insufficient.
42
+
43
+ ## Lifecycle
44
+
45
+ Run these recipes from the repository root. The helper rejects unsafe scope, invalid paths, unsupported Codex versions, and mismatched singleton configuration.
46
+
47
+ ```bash
48
+ just fleet conductor codex setup docs --project af
49
+ ```
50
+
51
+ The recipe resolves `codex`, the real repository root, and `$HOME/.pi/coms`, derives the isolated identity `codex-docs-conductor`, creates `$HOME/.local/state/agent-fleet/codex-conductor/workspace` outside the checkout and refreshes its owned contract copy with the absolute validated wrapper path. The lower-level `scripts/codex-remote-control.ts setup` command remains available for explicit integrations.
52
+
53
+ `setup` preflights, writes non-secret owned files, reloads user systemd, and enables the service. It does **not** pair or start it. The owned paths are:
54
+
55
+ - `~/.config/agent-fleet/codex-remote-control.json` (mode-restricted, non-secret configuration, including the external runtime directory)
56
+ - `~/.config/systemd/user/agent-fleet-codex-remote-control.service`
57
+ - `~/.local/state/agent-fleet/codex-conductor/workspace/AGENTS.md` (managed runtime copy)
58
+
59
+ The unit is `Type=oneshot` with `RemainAfterExit=yes`, has no `Restart=` policy, uses the dedicated scratch directory as daemon `WorkingDirectory` (the verified mobile client broadens its managed root only to the runtime-only parent container), and runs preflight immediately before `remote-control start`. Start passes the verified `approval_policy="on-request"`, `sandbox_mode="workspace-write"`, and one `sandbox_workspace_write.writable_roots` entry for the validated coms directory. `ExecStopPost` uses the capability-checked stop path even after a failed `ExecStart`. A mobile managed profile can remain narrower, so the exact wrapper `send` must request and receive phone approval before its first execution. The unit makes no foreground, PID, port, or readiness claim.
60
+
61
+ ### Pair — human interaction required
62
+
63
+ Pair the mobile client manually in an interactive operator TTY, after setup. Any displayed pairing code is short-lived secret material:
64
+
65
+ ```bash
66
+ just fleet conductor codex pair
67
+ ```
68
+
69
+ Do not pipe, tee, capture, transcribe, screenshot, or commit the output. Never put pairing material or Codex credentials in the unit or config.
70
+
71
+ ### Start, status, and conductor launch
72
+
73
+ ```bash
74
+ just fleet conductor codex start
75
+ just fleet conductor codex status
76
+ just fleet conductor codex docs --project af
77
+ ```
78
+
79
+ `status` reports only requested systemd state. Actual usability must be checked from the paired client, without inventing a network probe. The control pane similarly reports requested state only. Legacy `conductor-codex-pilot*` aliases remain available for the initial 0.144.x rollout.
80
+
81
+ ### Use with `just fleet team` and Android
82
+
83
+ The service does not start peers. Launch a hub/team in the exact project stored by setup:
84
+
85
+ ```bash
86
+ just fleet team docs --project af
87
+ ```
88
+
89
+ Do not also run `just fleet conductor codex docs --project af` for the same team unless a second peer set is intentional. The conductor mode is the alternative control-pane-plus-team layout when no Hub is needed.
90
+
91
+ In ChatGPT Android, open the paired Remote Control host and create a fresh thread using:
92
+
93
+ ```text
94
+ $HOME/.local/state/agent-fleet/codex-conductor/workspace
95
+ ```
96
+
97
+ Do not start a local `codex` process as a substitute for the Android flow. Ask the thread to load its `AGENTS.md`, run one fresh wrapper list, and request approval once if needed. The managed contract contains the validated absolute wrapper path; do not reconstruct it or invoke `coms-cli` directly. For a send, first confirm the listed peer and exact bounded task conversationally, then approve the one displayed wrapper command. A denial stops without retry or side effect.
98
+
99
+ Example read-only delegation:
100
+
101
+ ```text
102
+ List peers once. If researcher is visible, ask me to confirm:
103
+ "Inspect the current implementation and return findings with file:line evidence; do not edit files."
104
+ After confirmation, request approval for the exact wrapper send once.
105
+ ```
106
+
107
+ ### Stop, recovery, and reconfiguration
108
+
109
+ ```bash
110
+ just fleet conductor codex stop
111
+ just fleet conductor codex recover
112
+ ```
113
+
114
+ Use recovery when the unit says `active (exited)` but the paired client is unavailable, or when an `ExecStart` failure left the unit in `failed`. It is an explicit operator-confirmed systemd stop/reset/preflight/start path, not a health probe. Plain `start` still refuses `failed` and directs the operator to recovery or uninstall. Stop and emergency stop safely clear a confirmed `failed` state; other ambiguous states refuse rather than guessing.
115
+
116
+ To change the configured scope—or to upgrade an earlier in-checkout pilot runtime to the external user-state boundary—use `reconfigure` with the complete validated setup arguments, then explicitly stop/start as required. Do not edit the unit or config by hand:
117
+
118
+ ```bash
119
+ just fleet conductor codex reconfigure docs --project af
120
+ ```
121
+
122
+ ### Stale Codex send lock
123
+
124
+ A crash or `SIGKILL` can leave `~/.pi/coms/locks/codex-send.lock`. Automatic removal is intentionally forbidden because removing a live lock could permit concurrent sends. When the wrapper reports a held-or-stale lock:
125
+
126
+ 1. Do not retry or start another delegation.
127
+ 2. Inspect the non-secret JSON metadata (`started_at`, `project`, `name`, and advisory `pid`) without copying it into repository artifacts.
128
+ 3. Confirm in the mobile thread that no wrapper command is still running. A host-side `kill -0` check is insufficient because remote commands may use a different PID namespace.
129
+ 4. Wait beyond the configured send timeout. If ownership remains uncertain, stop the user service and confirm that no delegation is active.
130
+ 5. Only then remove that one exact lock file manually and restart/recover the service if it was stopped.
131
+
132
+ Never use a wildcard cleanup or remove project spools as part of lock recovery.
133
+
134
+ ### Version drift: emergency stop and uninstall
135
+
136
+ If normal preflight fails after Codex version/capability drift, normal start/stop/recovery remains blocked. The only exception is an explicit emergency stop, which first proves that the currently installed CLI still advertises the exact `remote-control stop` capability:
137
+
138
+ ```bash
139
+ node --experimental-strip-types scripts/codex-remote-control.ts emergency-stop \
140
+ --confirm emergency-stop-confirmed
141
+ ```
142
+
143
+ If that capability is absent, restore a supported `0.144.x` CLI before stopping or uninstalling. Never substitute a guessed stop command.
144
+
145
+ Uninstall is explicit, operates only on the owned unit/config, accepts and clears a confirmed `failed` state, resets the loaded unit before deleting it, disables the service, reloads user systemd, and leaves Codex authentication and pairing state untouched:
146
+
147
+ ```bash
148
+ just fleet conductor codex uninstall
149
+ # After version drift, use the lower-level helper only if the exact current
150
+ # stop capability is proved:
151
+ node --experimental-strip-types scripts/codex-remote-control.ts uninstall \
152
+ --confirm operator-confirmed --emergency-confirm emergency-stop-confirmed
153
+ ```
154
+
155
+ Repository rollback does not stop or uninstall an already installed user service. If ownership is ambiguous, stop and review; do not remove files or use a broad manual cleanup. The scratch directory is retained if it contains operator-visible files; inspect it before removing it manually. After stopping/uninstalling the conductor, the operator may restore the private pre-change `config.toml` backup if `on-request` is not wanted for other Codex sessions.
156
+
157
+ ## Verified live behavior
158
+
159
+ The Linux/Android live gate passed with CLI `0.144.6`: the managed unit completed start/stop/restart, manual pairing connected the phone, a fresh mobile thread loaded the original parent contract before workspace isolation, and the wrapper listed the `af` pool despite the remote PID namespace. The human confirmed one bounded delegation and separately approved the exact elevated wrapper command; `documenter` replied `Pilot acknowledged. No files changed.` A second approval was denied, producing no researcher message and no lock. The lock was absent after completion, and closing the control workspace did not stop the service.
160
+
161
+ Post-review live hardening passed on Android: because Codex 0.144.x can broaden the managed root to the runtime container parent regardless of daemon cwd, the entire container now lives under user state outside the checkout. A fresh Android thread used `$HOME/.local/state/agent-fleet/codex-conductor/workspace`, loaded its managed `AGENTS.md`, requested one approval for the rendered absolute list wrapper, listed `documenter` and `researcher`, and performed no edit or send.
162
+
163
+ Remote threads use only `scripts/codex-conductor.ts` from the dedicated scratch workspace. It reads owned scope, pins the real coms directory, and refuses repository/project/name/timeout overrides. **Human interaction remains required** twice for every send: first to confirm the freshly listed recipient/task conversationally, then to approve the exact wrapper command through Codex's `on-request` approval. The command must request escalation before its first execution because coms state and Unix sockets are outside the selected workspace.
164
+
165
+ ## Related documentation
166
+
167
+ - [Experimental implementation plan](../plans/codex-remote-conductor.md) — gates and acceptance criteria.
168
+ - [Canonical Codex conductor contract](../codex/CONDUCTOR.md) — bounded outbound delegation rules.
169
+ - [Hermes/coms bridge](coms-hermes-bridge.md) — inbound human questions and Hermes conductor boundary.
170
+ - [Architecture](ARCHITECTURE.md) — ownership of Pi, Herdr, coms, and external conductors.
@@ -0,0 +1,189 @@
1
+ # coms Hermes bridge
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
+
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.
12
+
13
+ ## Pieces
14
+
15
+ | Piece | Role |
16
+ | --- | --- |
17
+ | `scripts/coms-hermes-bridge.ts` | Daemon peer, default name `user-remote`, purpose `Remote human via Hermes/Telegram`. Accepts prompt, cancel, and ping envelopes. |
18
+ | `scripts/lib/hermes-bridge-core.ts` | Pure contract logic: qid validation, Telegram formatting, answer-file validation, answer mapping, timeout outcome, state transitions, and log records. |
19
+ | `scripts/lib/coms-envelope.ts` | Shared non-pi envelope wire shapes, including additive `cancel` envelopes. |
20
+ | `~/.pi/coms/hermes-bridge/questions/` | Private answer-file wire written by the Hermes gateway/liaison. |
21
+ | `~/.pi/coms/hermes-bridge/log.ndjson` | Bridge observability log. |
22
+
23
+ ## user-remote topology
24
+
25
+ 1. A pi peer sends a coms `prompt` envelope to `user-remote`.
26
+ 2. The bridge derives `qid` from `prompt.msg_id`, formats the question, and runs `hermes send --to <target> <message>` (`<target>` defaults to `telegram`). For a topic, copy the target accepted by `hermes send --list telegram`; depending on the Hermes output format, its `id` may already contain the `:<thread_id>` suffix, so do not append the thread twice.
27
+ 3. The human replies in Telegram; the Hermes gateway/liaison writes the answer file.
28
+ 4. The bridge polls the questions directory, validates the file, maps the answer, sends a coms `response` envelope, and removes the answer file.
29
+
30
+ ## Protocol contract v1
31
+
32
+ ### qid and correlation
33
+
34
+ `qid` is exactly the prompt envelope's `msg_id`. It must match the 26-character Crockford ULID regex `^[0-9A-HJKMNP-TV-Z]{26}$`. The same `qid` is the only correlation key across coms, Telegram, answer files, state, and logs.
35
+
36
+ ### Telegram question format
37
+
38
+ `formatTelegramQuestion` emits UTF-16 text capped at 4096 code units:
39
+
40
+ ```text
41
+ ❓ [HUB-Q:<qid>] <question>
42
+
43
+ 📁 Project: <coms-project>
44
+
45
+ Context: <context, truncated if needed>
46
+
47
+ Options:
48
+ 1. <title> — <description>
49
+ ...
50
+
51
+ ↩ Reply to this message, or type: HUB-Q:<qid>: <answer>
52
+ ```
53
+
54
+ `Project:` is always present and comes from the bridge's validated `--project` scope, making simultaneous questions from different pools distinguishable. `Context:` is omitted when absent. `Options:` is omitted when no options are supplied. Context receives the remaining budget after the header, project, options, and reply instruction.
55
+
56
+ ### Answer-file path, schema, and validation
57
+
58
+ The private wire path is:
59
+
60
+ ```text
61
+ ~/.pi/coms/hermes-bridge/questions/<qid>.answer.json
62
+ ```
63
+
64
+ Schema:
65
+
66
+ ```json
67
+ {
68
+ "qid": "<26-character Crockford ULID>",
69
+ "answer": "<text>",
70
+ "answered_by": "telegram:<user>",
71
+ "at": "<ISO timestamp>"
72
+ }
73
+ ```
74
+
75
+ Validation rejects and ignores files unless all conditions hold: filename ends in `.answer.json`; filename qid is valid; filename qid is currently pending; JSON parses; object fields match the schema; `at` parses as a timestamp; and body `qid` equals the filename qid. Rejection reasons are `invalid_path`, `invalid_qid`, `foreign_qid`, `invalid_json`, `invalid_schema`, and `qid_mismatch`; the daemon logs rejected files as `answer_rejected` and removes them. Exception: an `invalid_json` file is treated as a possible partial write and left in place for a short grace window (`max(2 × poll interval, 1s)` from first sighting); it is rejected and removed only if it still fails to parse after the grace expires.
76
+
77
+ ### Answer mapping
78
+
79
+ If options exist and the trimmed answer is a 1-based number for an option, the response is `{ "kind": "selection", "selections": ["<option title>"] }`. If options exist and the trimmed answer case-insensitively equals an option title, it maps to the same selection shape. All other answers map to `{ "kind": "freeform", "text": "<trimmed answer>" }`.
80
+
81
+ ### Cancel semantics
82
+
83
+ `cancel` is an additive coms envelope with shape `{ "type": "cancel", "msg_id", "from", "to", "created_at", "ref_msg_id" }`; `ref_msg_id` is the target `qid`. The bridge acks well-formed cancel envelopes before handling them.
84
+
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.
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
+
89
+ ### Timeouts
90
+
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`.
92
+
93
+ ### States
94
+
95
+ Question states are in-memory per qid: `pending`, `delivered`, `answered`, `cancelled`, and `timeout`. Implemented transitions are: `null + question_received → pending`; `pending + delivered → delivered`; `pending + delivery_error → null`; `pending|delivered + answered → answered` (the daemon currently answers from delivered or pending if the file arrives quickly); `pending|delivered + cancelled → cancelled`; `pending|delivered + timeout → timeout`; and terminal `answered|cancelled|timeout + late_answer` remains terminal.
96
+
97
+ ### ndjson logging
98
+
99
+ The bridge appends one JSON object per line to `~/.pi/coms/hermes-bridge/log.ndjson`. Core log records have shape `{ "at": "<ISO>", "qid": "<qid>", "event": "<event>", "detail"?: <value> }`. Contract events are `question_received`, `delivered`, `delivery_error`, `answered`, `cancelled`, `timeout`, and `late_answer`; the daemon also writes `answer_rejected` for invalid answer files. Ping agent cards report `queue_depth` as the current number of pending questions.
100
+
101
+ ## Hermes as conductor
102
+
103
+ Hermes can also act as the conductor without this daemon: use `coms-cli list` to discover peers and `coms-cli send --await --timeout <ms>` to delegate to hub-team pi peers, then synthesize the results for the human. This conductor topology uses the existing coms CLI as the bridge; no standing Hermes peer is required.
104
+
105
+ Launch a visible conductor workspace with:
106
+
107
+ ```bash
108
+ just fleet conductor hermes docs # live conductor + team workspace
109
+ just fleet conductor hermes docs --dry-run # preview; no Herdr calls
110
+ ```
111
+
112
+ The live recipe reuses `scripts/team-up.ts --conductor`: it creates a normal herdr workspace labeled `<worktree-tag>-conductor-<team>` (the tag is the last dot-segment of the checkout's basename, so the same team from a different worktree gets its own workspace), places a `conductor` pane running `hermes -p dev`, and tiles the chosen team beside it. Team peers keep their normal coms harness and herdr presence reporting, so they continue to show agent state in the sidebar; Hermes' own herdr-agent-state plugin is responsible for the conductor pane's state.
113
+
114
+ ### Telegram bridge control command
115
+
116
+ The outbound `hermes send` path needs a configured Telegram channel but no skill. Full reply round-trip additionally needs Agent Fleet's `hub-liaison` skill in the profile that owns the running Telegram gateway. Pi uses the namespaced command:
117
+
118
+ ```text
119
+ /af-set-hermes-telegram status --profile default
120
+ /af-set-hermes-telegram install --profile default
121
+ /af-set-hermes-telegram install --profile default --force --restart
122
+ /af-set-hermes-telegram on 7883056502:1735 --profile default
123
+ /af-set-hermes-telegram off 7883056502:1735
124
+ ```
125
+
126
+ Claude Code exposes the unprefixed `/set-hermes-telegram`; the arguments and backend are identical. The deterministic CLI can also be called directly with `agent-fleet set-hermes-telegram ...`.
127
+
128
+ #### `status` and profile resolution
129
+
130
+ `status` is read-only. It verifies the Hermes executable/profile, compares the complete installed `hub-liaison` tree to the version packaged with Agent Fleet, asks Hermes whether the skill is enabled, checks `terminal` and `file` toolsets for the `telegram` platform, and reports gateway state. `--profile <name>` is recommended. Without it the controller selects a profile only when `hermes gateway list` reports exactly one running gateway; zero or multiple running gateways fail closed and require an explicit profile.
131
+
132
+ #### `install`
133
+
134
+ `install` writes to `<Hermes-profile-path>/skills/hub-liaison`, where the profile path comes from `hermes profile show <name>` (important because the `default` profile is normally `~/.hermes`, while named profiles normally live below `~/.hermes/profiles/`). Installation behavior is:
135
+
136
+ - missing skill: copied atomically from the packaged Agent Fleet source;
137
+ - byte-identical tree: no-op;
138
+ - differing tree: refused unless `--force` is explicit;
139
+ - forced replacement: the previous tree is moved first to `<profile>/backups/agent-fleet/hub-liaison-<timestamp>`;
140
+ - symlinks or unsupported filesystem entries in either skill tree are refused;
141
+ - the installed tree is fingerprinted again, then `hermes --profile <name> skills list --enabled-only` and `tools list --platform telegram` are run for verification.
142
+
143
+ The command does not silently broaden Telegram tool permissions. If `terminal` or `file` is disabled, it prints the explicit remediation:
144
+
145
+ ```bash
146
+ hermes --profile <name> tools enable --platform telegram terminal file
147
+ ```
148
+
149
+ If the skill itself is disabled, use `hermes --profile <name> skills config`. A running gateway is restarted only with explicit `--restart`; otherwise the command prints the required restart command. A stopped gateway is never started as a side effect. No install/status/on/off action sends a test Telegram message.
150
+
151
+ #### `on` and `off`
152
+
153
+ `on` fails before touching Herdr unless the selected gateway is running, `hub-liaison` is current and enabled, and both required Telegram toolsets are enabled. It then closes any existing pane labeled `hermes-bridge` in the current workspace, creates a new right-hand pane in that **same Herdr workspace**, labels it `hermes-bridge`, and starts the daemon with `telegram:<id>` as its exact target. The selected profile is forwarded as `--hermes-profile`, so every question, timeout, cancel, and late-answer send executes as `hermes --profile <name> send ...` rather than silently falling back to Hermes' sticky default. `off` remains available even when Hermes readiness is broken, closes the bridge pane, creates nothing, and is idempotent.
154
+
155
+ The Telegram destination must contain digits only (`<chat_id>`) or two digit groups separated by one colon (`<chat_id>:<topic_id>`). Values such as `telegram:123`, `123:`, `123:456:789`, spaces, signs, and letters are rejected. The controller infers the coms project independently from the current hub process's explicit `--project`, then `PI_COMS_PROJECT`, then `default`.
156
+
157
+ The manual equivalent is:
158
+
159
+ ```bash
160
+ node --experimental-strip-types scripts/coms-hermes-bridge.ts \
161
+ --project af \
162
+ --hermes-profile default \
163
+ --timeout 1800000 \
164
+ --to 'telegram:<chat_id>:<thread_id>'
165
+ just fleet team docs --project af
166
+ ```
167
+
168
+ Repeated value flags such as two `--to` arguments are rejected at startup rather than silently selecting one destination. The `ask-user-remote` wrapper resolves the explicit Pi `--project` flag when the tool executes, so non-default hubs discover `user-remote` in their own pool.
169
+
170
+ Hard boundary: the Hermes conductor must not run `herdr` commands, drive panes, create/kill workspaces, or manage fleet lifecycle. Herdr driving stays with the human/orchestrator so the damage-control model remains intact; see `.pi/damage-control-rules.yaml` for the authoritative no-herdr boundary. Hermes may only operate inside the project coms pool through the documented coms CLI commands.
171
+
172
+ ## Hermes and the experimental Codex conductor
173
+
174
+ Hermes/Telegram remains the **inbound** human `ask_user` complement to the
175
+ experimental Codex remote-control conductor. Codex is outbound-initiated,
176
+ approval-gated, and serialized; it is not an inbound question channel. The Codex user service and control-pane lifecycle are
177
+ separate from Hermes. See the [experimental Codex operator runbook](codex-remote-conductor.md).
178
+
179
+ Both conductor contracts are advisory outside Pi damage-control: Pi wraps Pi
180
+ tool calls, not Hermes or Codex, and neither has an OS command allowlist.
181
+ Human confirmation, approvals, and sandboxing reduce risk but do not
182
+ technically enforce either external contract.
183
+
184
+ ## Deferred
185
+
186
+ - Standing conductor peer for pi → Hermes inbound messages.
187
+ - Telegram-driven conductor profile.
188
+ - Group/multi-recipient questions and non-text answers.
189
+ - Kanban-driven orchestration on top of the same conductor contract.
@@ -0,0 +1,119 @@
1
+ # Getting started
2
+
3
+ Agent Fleet installs deterministic pi workspace content. The public lifecycle is
4
+ **setup**, **doctor**, and **uninstall**; no coding agent or model is required.
5
+
6
+ ## Install a new repository
7
+
8
+ From the target repository, run the package command. `just fleet` does not exist
9
+ yet — the managed justfile region is one of the things setup writes — so a first
10
+ install always goes through `npx`:
11
+
12
+ ```bash
13
+ cd ~/projects/my-app
14
+ npx @chankov/agent-fleet@latest setup
15
+ ```
16
+
17
+ In a real TTY that opens the installer: choose **Default** or **Full** plus
18
+ optional comma-separated features, read the exact plan, and confirm once. For
19
+ automation, name the selection and consent:
20
+
21
+ ```bash
22
+ npx @chankov/agent-fleet@latest setup --preset default --features none --yes
23
+ ```
24
+
25
+ Choose **Default** for stable Fleet Core or **Full** for all stable,
26
+ platform-applicable catalogue roots. Default creates neither voice configuration
27
+ nor `.claude/`; Full may install the recorded Claude Code coms bridge. Features
28
+ are named additions after preset selection. In an Agent Fleet source checkout,
29
+ use `node bin/cli.js setup` instead.
30
+
31
+ Setup writes files but runs no commands, so finish the install with the two npm
32
+ steps it deliberately skipped — the workspace is not launchable until they run:
33
+
34
+ ```bash
35
+ just fleet deps # npm install in .pi/extensions and .pi/harnesses
36
+ just fleet doctor # exit 0 = nothing to repair
37
+ ```
38
+
39
+ (Or pass `--allow-exec` to setup and let it run them in the same pass.)
40
+
41
+ ## First session
42
+
43
+ ```bash
44
+ just fleet # Hub/operator; empty native roster
45
+ just fleet --agents default --project af # Hub/orchestrator + native roster
46
+ just fleet --agents default --peers docs --project af
47
+ # Hub + standing Herdr peers
48
+ ```
49
+
50
+ ## Run and maintain deterministic flows
51
+
52
+ When the workflow runtime is selected, `just flow` runs code-owned workflows outside the interactive hub:
53
+
54
+ ```bash
55
+ just flow scout "where is authentication configured?"
56
+ just flow quality
57
+ just flow build-test "add the validated endpoint"
58
+ ```
59
+
60
+ Each run creates a `flow/<name>-<runId>` branch. Use the numbered maintenance selector to remove an empty/integrated branch or squash-merge an accepted result back to the branch from which it started:
61
+
62
+ ```bash
63
+ just flow cleanup # list flow branches and prompt for a number
64
+ just flow cleanup 1 # safely remove selection 1 through Worktrunk
65
+ just flow merge # list flow branches and prompt for a number
66
+ just flow merge 2 # squash-merge selection 2 through Worktrunk
67
+ ```
68
+
69
+ Maintenance requires [Worktrunk](https://worktrunk.dev). It refuses dirty worktrees, rejected runs, and unknown merge targets. See [workflows.md](workflows.md#clean-up-and-merge-flow-branches) for `--discard`, `--target`, full branch selectors, non-interactive `--yes`, and safety details.
70
+
71
+ ## Update an existing install
72
+
73
+ A pi session tells you when a newer version is published. To act on it:
74
+
75
+ ```bash
76
+ just fleet setup --dry-run # preview: what changes, what gets overwritten
77
+ just fleet setup # apply; shows the plan and asks once
78
+ just fleet deps # if the plan skipped the npm steps
79
+ just fleet doctor
80
+ ```
81
+
82
+ Your preset and features are remembered in `.ai/agent-fleet.json`, so a plain
83
+ `setup` reconciles to the selection you already chose.
84
+
85
+ Two things to know before your first update:
86
+
87
+ - **`setup` reconciles toward the package.** A file you edited in place is
88
+ refreshed and your edit is overwritten — no prompt, no conflict. Customize
89
+ through `.ai/agent-fleet-overrides.md` instead, which the lifecycle never
90
+ touches.
91
+ - **A conflict stops the run.** If you *and* the new version changed the same
92
+ file, setup exits `3` having written nothing; re-run with `--on-conflict
93
+ theirs` or `--on-conflict ours`.
94
+
95
+ `pi update --extensions` updates pi's own extensions only — never this installer
96
+ or what it wrote. Full update reference, including what happens to every file
97
+ state: [npm-install.md](npm-install.md#updating-an-existing-install).
98
+
99
+ ## Uninstall
100
+
101
+ `just fleet uninstall --yes` is for the self-hosted workspace lifecycle; it
102
+ removes the launcher last. Reinstall after that with the package CLI, not `just`:
103
+
104
+ ```bash
105
+ npx @chankov/agent-fleet@latest setup --preset default --features none --yes
106
+ ```
107
+
108
+ ## Pi package-native skills and prompts
109
+
110
+ For pi package-native skills/prompts instead of copied ones:
111
+
112
+ ```bash
113
+ pi install -l npm:@chankov/agent-fleet
114
+ ```
115
+
116
+ Do not mix copied and package-native skills/prompts. `doctor` identifies that
117
+ ownership overlap. Read [pi-setup.md](pi-setup.md) for runtime composition,
118
+ [agent-fleet-setup.md](agent-fleet-setup.md) for project configuration, and
119
+ [MIGRATION-agent-fleet.md](MIGRATION-agent-fleet.md) for the major-release matrix.