@chankov/agent-fleet 0.0.8 → 0.0.9

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 (340) hide show
  1. package/.pi/agents/model-profiles.yaml +9 -2
  2. package/.pi/agents/peers.yaml +12 -16
  3. package/.pi/agents/teams.yaml +4 -2
  4. package/.pi/harnesses/agent-hub/README.md +20 -5
  5. package/.pi/harnesses/agent-hub/footer.ts +4 -2
  6. package/.pi/harnesses/agent-hub/index.ts +104 -11
  7. package/.pi/harnesses/agent-hub/package.json +1 -1
  8. package/.pi/harnesses/agent-hub/version.ts +25 -1
  9. package/.pi/harnesses/coms/README.md +8 -1
  10. package/.pi/harnesses/coms/package.json +1 -1
  11. package/.pi/harnesses/coms/version.ts +25 -1
  12. package/.pi/harnesses/damage-control-continue/README.md +8 -1
  13. package/.pi/harnesses/damage-control-continue/package.json +1 -1
  14. package/.pi/harnesses/damage-control-continue/version.ts +25 -1
  15. package/.pi/harnesses/lib/herdr-client.ts +10 -1
  16. package/.pi/harnesses/lib/spawned-peers.js +190 -0
  17. package/.versions/0.0.9/.claude/commands/build.md +44 -0
  18. package/.versions/0.0.9/.claude/commands/code-simplify.md +22 -0
  19. package/.versions/0.0.9/.claude/commands/design-agent.md +14 -0
  20. package/.versions/0.0.9/.claude/commands/doctor-agent-fleet.md +17 -0
  21. package/.versions/0.0.9/.claude/commands/orchestrate.md +112 -0
  22. package/.versions/0.0.9/.claude/commands/plan.md +16 -0
  23. package/.versions/0.0.9/.claude/commands/prime.md +22 -0
  24. package/.versions/0.0.9/.claude/commands/review.md +16 -0
  25. package/.versions/0.0.9/.claude/commands/set-hermes-telegram.md +15 -0
  26. package/.versions/0.0.9/.claude/commands/set-hermes-watchdog.md +6 -0
  27. package/.versions/0.0.9/.claude/commands/setup-agent-fleet.md +25 -0
  28. package/.versions/0.0.9/.claude/commands/ship.md +72 -0
  29. package/.versions/0.0.9/.claude/commands/spec.md +15 -0
  30. package/.versions/0.0.9/.claude/commands/test.md +19 -0
  31. package/.versions/0.0.9/.claude/commands/webperf.md +32 -0
  32. package/.versions/0.0.9/.claude/orchestrate-teams.yaml +24 -0
  33. package/.versions/0.0.9/.opencode/commands/af-build.md +17 -0
  34. package/.versions/0.0.9/.opencode/commands/af-code-simplify.md +16 -0
  35. package/.versions/0.0.9/.opencode/commands/af-compound.md +16 -0
  36. package/.versions/0.0.9/.opencode/commands/af-design-agent.md +15 -0
  37. package/.versions/0.0.9/.opencode/commands/af-doctor-agent-fleet.md +17 -0
  38. package/.versions/0.0.9/.opencode/commands/af-orchestrate.md +112 -0
  39. package/.versions/0.0.9/.opencode/commands/af-plan.md +16 -0
  40. package/.versions/0.0.9/.opencode/commands/af-prime.md +22 -0
  41. package/.versions/0.0.9/.opencode/commands/af-review.md +15 -0
  42. package/.versions/0.0.9/.opencode/commands/af-set-hermes-telegram.md +15 -0
  43. package/.versions/0.0.9/.opencode/commands/af-set-hermes-watchdog.md +6 -0
  44. package/.versions/0.0.9/.opencode/commands/af-setup-agent-fleet.md +15 -0
  45. package/.versions/0.0.9/.opencode/commands/af-ship.md +16 -0
  46. package/.versions/0.0.9/.opencode/commands/af-spec.md +16 -0
  47. package/.versions/0.0.9/.opencode/commands/af-test.md +21 -0
  48. package/.versions/0.0.9/.opencode/commands/af-webperf.md +32 -0
  49. package/.versions/0.0.9/.opencode/orchestrate-teams.yaml +24 -0
  50. package/.versions/0.0.9/.pi/agents/dispatch-policy.yaml +32 -0
  51. package/.versions/0.0.9/.pi/agents/model-profiles.yaml +27 -0
  52. package/.versions/0.0.9/.pi/agents/peers.yaml +142 -0
  53. package/.versions/0.0.9/.pi/agents/teams.yaml +41 -0
  54. package/.versions/0.0.9/.pi/damage-control-rules.yaml +297 -0
  55. package/.versions/0.0.9/.pi/extensions/agent-fleet-update-check/README.md +58 -0
  56. package/.versions/0.0.9/.pi/extensions/agent-fleet-update-check/index.ts +161 -0
  57. package/.versions/0.0.9/.pi/extensions/agent-fleet-update-check/package.json +6 -0
  58. package/.versions/0.0.9/.pi/extensions/btw/README.md +118 -0
  59. package/.versions/0.0.9/.pi/extensions/btw/index.ts +917 -0
  60. package/.versions/0.0.9/.pi/extensions/btw/package.json +6 -0
  61. package/.versions/0.0.9/.pi/extensions/btw/state.js +179 -0
  62. package/.versions/0.0.9/.pi/extensions/chrome-devtools-mcp/README.md +58 -0
  63. package/.versions/0.0.9/.pi/extensions/chrome-devtools-mcp/index.ts +93 -0
  64. package/.versions/0.0.9/.pi/extensions/chrome-devtools-mcp/package.json +6 -0
  65. package/.versions/0.0.9/.pi/extensions/compact-and-continue/README.md +42 -0
  66. package/.versions/0.0.9/.pi/extensions/compact-and-continue/index.ts +120 -0
  67. package/.versions/0.0.9/.pi/extensions/compact-and-continue/package.json +6 -0
  68. package/.versions/0.0.9/.pi/extensions/mcp-bridge/README.md +46 -0
  69. package/.versions/0.0.9/.pi/extensions/mcp-bridge/index.ts +206 -0
  70. package/.versions/0.0.9/.pi/extensions/mcp-bridge/package.json +6 -0
  71. package/.versions/0.0.9/.pi/extensions/package-lock.json +1143 -0
  72. package/.versions/0.0.9/.pi/extensions/package.json +9 -0
  73. package/.versions/0.0.9/.pi/extensions/pi-voice-stt/README.md +201 -0
  74. package/.versions/0.0.9/.pi/extensions/pi-voice-stt/config.ts +198 -0
  75. package/.versions/0.0.9/.pi/extensions/pi-voice-stt/examples/stt.json +35 -0
  76. package/.versions/0.0.9/.pi/extensions/pi-voice-stt/index.ts +248 -0
  77. package/.versions/0.0.9/.pi/extensions/pi-voice-stt/package.json +6 -0
  78. package/.versions/0.0.9/.pi/extensions/pi-voice-stt/providers.ts +214 -0
  79. package/.versions/0.0.9/.pi/extensions/pi-voice-stt/recorder.ts +158 -0
  80. package/.versions/0.0.9/.pi/harnesses/agent-hub/README.md +872 -0
  81. package/.versions/0.0.9/.pi/harnesses/agent-hub/access-approval.ts +135 -0
  82. package/.versions/0.0.9/.pi/harnesses/agent-hub/artifacts.js +146 -0
  83. package/.versions/0.0.9/.pi/harnesses/agent-hub/assertion-ledger.js +58 -0
  84. package/.versions/0.0.9/.pi/harnesses/agent-hub/backend-policy.js +153 -0
  85. package/.versions/0.0.9/.pi/harnesses/agent-hub/context-window.js +106 -0
  86. package/.versions/0.0.9/.pi/harnesses/agent-hub/delegate.ts +435 -0
  87. package/.versions/0.0.9/.pi/harnesses/agent-hub/drift-watchdog.js +211 -0
  88. package/.versions/0.0.9/.pi/harnesses/agent-hub/evidence-rules.js +96 -0
  89. package/.versions/0.0.9/.pi/harnesses/agent-hub/footer.ts +31 -0
  90. package/.versions/0.0.9/.pi/harnesses/agent-hub/helpers.ts +248 -0
  91. package/.versions/0.0.9/.pi/harnesses/agent-hub/index.ts +8702 -0
  92. package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
  93. package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-invoke-journal.ts +131 -0
  94. package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-invoke.ts +92 -0
  95. package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
  96. package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
  97. package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
  98. package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
  99. package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-session-bridge.ts +257 -0
  100. package/.versions/0.0.9/.pi/harnesses/agent-hub/package.json +7 -0
  101. package/.versions/0.0.9/.pi/harnesses/agent-hub/provider-semaphore.js +138 -0
  102. package/.versions/0.0.9/.pi/harnesses/agent-hub/research-retention.js +34 -0
  103. package/.versions/0.0.9/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
  104. package/.versions/0.0.9/.pi/harnesses/agent-hub/return-contract.js +293 -0
  105. package/.versions/0.0.9/.pi/harnesses/agent-hub/return-extract.js +75 -0
  106. package/.versions/0.0.9/.pi/harnesses/agent-hub/run-budget.js +181 -0
  107. package/.versions/0.0.9/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
  108. package/.versions/0.0.9/.pi/harnesses/agent-hub/scope-gate.js +103 -0
  109. package/.versions/0.0.9/.pi/harnesses/agent-hub/session-health.js +110 -0
  110. package/.versions/0.0.9/.pi/harnesses/agent-hub/spawn.ts +354 -0
  111. package/.versions/0.0.9/.pi/harnesses/agent-hub/version.ts +42 -0
  112. package/.versions/0.0.9/.pi/harnesses/ask-user-remote/README.md +19 -0
  113. package/.versions/0.0.9/.pi/harnesses/ask-user-remote/index.ts +321 -0
  114. package/.versions/0.0.9/.pi/harnesses/ask-user-remote/race-core.js +106 -0
  115. package/.versions/0.0.9/.pi/harnesses/coms/README.md +100 -0
  116. package/.versions/0.0.9/.pi/harnesses/coms/index.ts +1767 -0
  117. package/.versions/0.0.9/.pi/harnesses/coms/package.json +7 -0
  118. package/.versions/0.0.9/.pi/harnesses/coms/version.ts +42 -0
  119. package/.versions/0.0.9/.pi/harnesses/damage-control-continue/README.md +124 -0
  120. package/.versions/0.0.9/.pi/harnesses/damage-control-continue/index.ts +536 -0
  121. package/.versions/0.0.9/.pi/harnesses/damage-control-continue/package.json +7 -0
  122. package/.versions/0.0.9/.pi/harnesses/damage-control-continue/version.ts +42 -0
  123. package/.versions/0.0.9/.pi/harnesses/lib/coms-registry-entry.ts +94 -0
  124. package/.versions/0.0.9/.pi/harnesses/lib/damage-control-shared.ts +197 -0
  125. package/.versions/0.0.9/.pi/harnesses/lib/herdr-client.ts +472 -0
  126. package/.versions/0.0.9/.pi/harnesses/lib/herdr-presence.ts +399 -0
  127. package/.versions/0.0.9/.pi/harnesses/lib/hermes-monitor-events.ts +136 -0
  128. package/.versions/0.0.9/.pi/harnesses/lib/hermes-monitor-herdr.ts +28 -0
  129. package/.versions/0.0.9/.pi/harnesses/lib/hermes-monitor-model.ts +18 -0
  130. package/.versions/0.0.9/.pi/harnesses/lib/hermes-monitor-registry.ts +6 -0
  131. package/.versions/0.0.9/.pi/harnesses/lib/hermes-monitor-socket.ts +163 -0
  132. package/.versions/0.0.9/.pi/harnesses/lib/hermes-monitor-store.ts +31 -0
  133. package/.versions/0.0.9/.pi/harnesses/lib/spawned-peers.js +190 -0
  134. package/.versions/0.0.9/.pi/harnesses/package-lock.json +35 -0
  135. package/.versions/0.0.9/.pi/harnesses/package.json +9 -0
  136. package/.versions/0.0.9/.pi/prompts/af-build.md +24 -0
  137. package/.versions/0.0.9/.pi/prompts/af-code-simplify.md +22 -0
  138. package/.versions/0.0.9/.pi/prompts/af-doctor-agent-fleet.md +15 -0
  139. package/.versions/0.0.9/.pi/prompts/af-plan.md +16 -0
  140. package/.versions/0.0.9/.pi/prompts/af-review.md +16 -0
  141. package/.versions/0.0.9/.pi/prompts/af-set-hermes-telegram.md +15 -0
  142. package/.versions/0.0.9/.pi/prompts/af-set-hermes-watchdog.md +6 -0
  143. package/.versions/0.0.9/.pi/prompts/af-setup-agent-fleet.md +27 -0
  144. package/.versions/0.0.9/.pi/prompts/af-ship.md +17 -0
  145. package/.versions/0.0.9/.pi/prompts/af-spec.md +15 -0
  146. package/.versions/0.0.9/.pi/prompts/af-test.md +19 -0
  147. package/.versions/0.0.9/.pi/skills/bowser/SKILL.md +145 -0
  148. package/.versions/0.0.9/.version +1 -0
  149. package/.versions/0.0.9/agents/architect.md +24 -0
  150. package/.versions/0.0.9/agents/bowser.md +27 -0
  151. package/.versions/0.0.9/agents/builder.md +54 -0
  152. package/.versions/0.0.9/agents/code-reviewer.md +204 -0
  153. package/.versions/0.0.9/agents/deep-researcher.md +32 -0
  154. package/.versions/0.0.9/agents/documenter.md +18 -0
  155. package/.versions/0.0.9/agents/orchestrator.md +66 -0
  156. package/.versions/0.0.9/agents/plan-reviewer.md +62 -0
  157. package/.versions/0.0.9/agents/planner.md +70 -0
  158. package/.versions/0.0.9/agents/releaser.md +24 -0
  159. package/.versions/0.0.9/agents/researcher.md +28 -0
  160. package/.versions/0.0.9/agents/security-auditor.md +167 -0
  161. package/.versions/0.0.9/agents/test-engineer.md +153 -0
  162. package/.versions/0.0.9/agents/web-debugger.md +43 -0
  163. package/.versions/0.0.9/agents/web-performance-auditor.md +193 -0
  164. package/.versions/0.0.9/codex/CONDUCTOR.md +148 -0
  165. package/.versions/0.0.9/docs/ARCHITECTURE.md +262 -0
  166. package/.versions/0.0.9/docs/agent-fleet-setup.md +366 -0
  167. package/.versions/0.0.9/docs/claude-code-coms-bridge.md +109 -0
  168. package/.versions/0.0.9/docs/codex-remote-conductor.md +170 -0
  169. package/.versions/0.0.9/docs/coms-hermes-bridge.md +189 -0
  170. package/.versions/0.0.9/docs/getting-started.md +231 -0
  171. package/.versions/0.0.9/docs/npm-install.md +337 -0
  172. package/.versions/0.0.9/docs/opencode-setup.md +249 -0
  173. package/.versions/0.0.9/docs/pi-extensions.md +356 -0
  174. package/.versions/0.0.9/docs/pi-setup.md +476 -0
  175. package/.versions/0.0.9/docs/skill-anatomy.md +150 -0
  176. package/.versions/0.0.9/hermes/README.md +347 -0
  177. package/.versions/0.0.9/hermes/desktop-plugins/agent-fleet-herdr/plugin.js +1291 -0
  178. package/.versions/0.0.9/hermes/desktop-plugins/agent-fleet-herdr/presentation.js +672 -0
  179. package/.versions/0.0.9/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
  180. package/.versions/0.0.9/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
  181. package/.versions/0.0.9/hermes/gates/gate-o-capability.md +8 -0
  182. package/.versions/0.0.9/hermes/gates/gate-o-validator-fixtures.json +1 -0
  183. package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/activity.py +770 -0
  184. package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/coms_registry.py +134 -0
  185. package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/coms_send.py +350 -0
  186. package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/herdr_source.py +193 -0
  187. package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/manifest.json +4 -0
  188. package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/plugin_api.py +444 -0
  189. package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/sessions.py +205 -0
  190. package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/tasks.py +300 -0
  191. package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/watch.py +819 -0
  192. package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/plugin.yaml +8 -0
  193. package/.versions/0.0.9/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +139 -0
  194. package/.versions/0.0.9/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
  195. package/.versions/0.0.9/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
  196. package/.versions/0.0.9/hermes/skills/hub-conductor/SKILL.md +84 -0
  197. package/.versions/0.0.9/hermes/skills/hub-liaison/SKILL.md +84 -0
  198. package/.versions/0.0.9/hermes/skills/hub-watchdog/SKILL.md +76 -0
  199. package/.versions/0.0.9/hermes/skills/hub-watchdog/manifest.json +1 -0
  200. package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog.py +249 -0
  201. package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_actions.py +124 -0
  202. package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_contract.py +76 -0
  203. package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_delivery.py +10 -0
  204. package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_engine.py +128 -0
  205. package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_judgment.py +41 -0
  206. package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_recovery.py +103 -0
  207. package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_state.py +163 -0
  208. package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_transport.py +138 -0
  209. package/.versions/0.0.9/hermes/watchdog-tests/__init__.py +0 -0
  210. package/.versions/0.0.9/hooks/SIMPLIFY-IGNORE.md +90 -0
  211. package/.versions/0.0.9/hooks/coms-stop-hook.mjs +84 -0
  212. package/.versions/0.0.9/hooks/hooks.json +14 -0
  213. package/.versions/0.0.9/hooks/session-start.sh +74 -0
  214. package/.versions/0.0.9/hooks/simplify-ignore.sh +302 -0
  215. package/.versions/0.0.9/justfile +254 -0
  216. package/.versions/0.0.9/references/accessibility-checklist.md +160 -0
  217. package/.versions/0.0.9/references/definition-of-done.md +67 -0
  218. package/.versions/0.0.9/references/fleet-coordination-patterns.md +151 -0
  219. package/.versions/0.0.9/references/observability-checklist.md +91 -0
  220. package/.versions/0.0.9/references/orchestration-patterns.md +370 -0
  221. package/.versions/0.0.9/references/performance-checklist.md +153 -0
  222. package/.versions/0.0.9/references/prompting-patterns.md +380 -0
  223. package/.versions/0.0.9/references/security-checklist.md +179 -0
  224. package/.versions/0.0.9/references/testing-patterns.md +236 -0
  225. package/.versions/0.0.9/scripts/codex-conductor.ts +41 -0
  226. package/.versions/0.0.9/scripts/codex-remote-control.ts +167 -0
  227. package/.versions/0.0.9/scripts/coms-claude-bridge.ts +401 -0
  228. package/.versions/0.0.9/scripts/coms-cli.ts +484 -0
  229. package/.versions/0.0.9/scripts/coms-hermes-bridge.ts +413 -0
  230. package/.versions/0.0.9/scripts/fleet.ts +168 -0
  231. package/.versions/0.0.9/scripts/hermes-monitor-capability-runner.ts +25 -0
  232. package/.versions/0.0.9/scripts/hermes-monitor-scenario.ts +474 -0
  233. package/.versions/0.0.9/scripts/hermes-watchdog-capability-probe.ts +45 -0
  234. package/.versions/0.0.9/scripts/install-hermes-plugin.sh +180 -0
  235. package/.versions/0.0.9/scripts/lib/claude-bridge-core.ts +165 -0
  236. package/.versions/0.0.9/scripts/lib/codex-conductor.ts +88 -0
  237. package/.versions/0.0.9/scripts/lib/codex-remote-control.ts +480 -0
  238. package/.versions/0.0.9/scripts/lib/coms-envelope.ts +582 -0
  239. package/.versions/0.0.9/scripts/lib/fake-herdr-server.ts +88 -0
  240. package/.versions/0.0.9/scripts/lib/fleet-command.ts +111 -0
  241. package/.versions/0.0.9/scripts/lib/herdr-layout.ts +281 -0
  242. package/.versions/0.0.9/scripts/lib/hermes-bridge-core.ts +241 -0
  243. package/.versions/0.0.9/scripts/lib/hermes-monitor-events.ts +1 -0
  244. package/.versions/0.0.9/scripts/lib/hermes-monitor-herdr.ts +2 -0
  245. package/.versions/0.0.9/scripts/lib/hermes-monitor-model.ts +3 -0
  246. package/.versions/0.0.9/scripts/lib/hermes-monitor-registry.ts +2 -0
  247. package/.versions/0.0.9/scripts/lib/hermes-monitor-socket.ts +2 -0
  248. package/.versions/0.0.9/scripts/lib/hermes-monitor-store.ts +2 -0
  249. package/.versions/0.0.9/scripts/lib/monitor-env.ts +120 -0
  250. package/.versions/0.0.9/scripts/lib/peer-launch.ts +314 -0
  251. package/.versions/0.0.9/scripts/lib/persona-banner.ts +62 -0
  252. package/.versions/0.0.9/scripts/lib/spawn-stagger.ts +101 -0
  253. package/.versions/0.0.9/scripts/lib/team-project.ts +193 -0
  254. package/.versions/0.0.9/scripts/lib/team-snapshot.ts +147 -0
  255. package/.versions/0.0.9/scripts/peer-banner.ts +40 -0
  256. package/.versions/0.0.9/scripts/peer-launch.ts +259 -0
  257. package/.versions/0.0.9/scripts/team-snapshot.ts +237 -0
  258. package/.versions/0.0.9/scripts/team-up.ts +360 -0
  259. package/.versions/0.0.9/skills/_internal/grilling.md +11 -0
  260. package/.versions/0.0.9/skills/browser-testing-with-devtools/SKILL.md +352 -0
  261. package/.versions/0.0.9/skills/code-review-and-quality/SKILL.md +381 -0
  262. package/.versions/0.0.9/skills/compound-learning/SKILL.md +137 -0
  263. package/.versions/0.0.9/skills/context-engineering/SKILL.md +291 -0
  264. package/.versions/0.0.9/skills/deprecation-and-migration/SKILL.md +206 -0
  265. package/.versions/0.0.9/skills/designing-agents/SKILL.md +394 -0
  266. package/.versions/0.0.9/skills/designing-agents/pi-harness-authoring.md +222 -0
  267. package/.versions/0.0.9/skills/frontend-ui-engineering/SKILL.md +328 -0
  268. package/.versions/0.0.9/skills/git-workflow-and-versioning/SKILL.md +316 -0
  269. package/.versions/0.0.9/skills/guided-workspace-setup/SKILL.md +544 -0
  270. package/.versions/0.0.9/skills/guided-workspace-setup/companion-manifest.json +38 -0
  271. package/.versions/0.0.9/skills/idea-refine/SKILL.md +182 -0
  272. package/.versions/0.0.9/skills/idea-refine/examples.md +238 -0
  273. package/.versions/0.0.9/skills/idea-refine/frameworks.md +99 -0
  274. package/.versions/0.0.9/skills/idea-refine/refinement-criteria.md +113 -0
  275. package/.versions/0.0.9/skills/idea-refine/scripts/idea-refine.sh +15 -0
  276. package/.versions/0.0.9/skills/incremental-implementation/SKILL.md +287 -0
  277. package/.versions/0.0.9/skills/interview-me/SKILL.md +226 -0
  278. package/.versions/0.0.9/skills/orchestration-verification/SKILL.md +181 -0
  279. package/.versions/0.0.9/skills/peer-coms/SKILL.md +90 -0
  280. package/.versions/0.0.9/skills/performance-optimization/SKILL.md +350 -0
  281. package/.versions/0.0.9/skills/planning-and-task-breakdown/SKILL.md +236 -0
  282. package/.versions/0.0.9/skills/security-and-hardening/SKILL.md +461 -0
  283. package/.versions/0.0.9/skills/spec-driven-development/SKILL.md +245 -0
  284. package/.versions/0.0.9/skills/using-agent-skills/SKILL.md +199 -0
  285. package/.versions/0.0.9/systemd/user/agent-fleet-codex-remote-control.service.in +23 -0
  286. package/.versions/0.0.9/vendor/agent-skills-upstream/LICENSE +21 -0
  287. package/.versions/0.0.9/vendor/agent-skills-upstream/README.md +11 -0
  288. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/api-and-interface-design/SKILL.md +294 -0
  289. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/browser-testing-with-devtools/SKILL.md +317 -0
  290. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/ci-cd-and-automation/SKILL.md +390 -0
  291. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/code-review-and-quality/SKILL.md +396 -0
  292. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/code-simplification/SKILL.md +331 -0
  293. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/context-engineering/SKILL.md +289 -0
  294. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/debugging-and-error-recovery/SKILL.md +300 -0
  295. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/deprecation-and-migration/SKILL.md +247 -0
  296. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/documentation-and-adrs/SKILL.md +278 -0
  297. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/doubt-driven-development/SKILL.md +243 -0
  298. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/frontend-ui-engineering/SKILL.md +328 -0
  299. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/git-workflow-and-versioning/SKILL.md +355 -0
  300. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/idea-refine/SKILL.md +178 -0
  301. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/idea-refine/examples.md +238 -0
  302. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/idea-refine/frameworks.md +99 -0
  303. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/idea-refine/refinement-criteria.md +113 -0
  304. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/idea-refine/scripts/idea-refine.sh +15 -0
  305. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/incremental-implementation/SKILL.md +249 -0
  306. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/interview-me/SKILL.md +225 -0
  307. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/observability-and-instrumentation/SKILL.md +203 -0
  308. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/performance-optimization/SKILL.md +350 -0
  309. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/planning-and-task-breakdown/SKILL.md +234 -0
  310. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/security-and-hardening/SKILL.md +467 -0
  311. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/shipping-and-launch/SKILL.md +310 -0
  312. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/source-driven-development/SKILL.md +194 -0
  313. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/spec-driven-development/SKILL.md +206 -0
  314. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/test-driven-development/SKILL.md +383 -0
  315. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/using-agent-skills/SKILL.md +191 -0
  316. package/CHANGELOG.md +38 -0
  317. package/agents/architect.md +1 -0
  318. package/agents/bowser.md +1 -0
  319. package/agents/builder.md +1 -0
  320. package/agents/code-reviewer.md +4 -5
  321. package/agents/deep-researcher.md +2 -1
  322. package/agents/orchestrator.md +1 -0
  323. package/agents/plan-reviewer.md +3 -1
  324. package/agents/planner.md +3 -2
  325. package/agents/security-auditor.md +1 -0
  326. package/agents/test-engineer.md +3 -1
  327. package/agents/web-debugger.md +1 -0
  328. package/agents/web-performance-auditor.md +1 -0
  329. package/docs/ARCHITECTURE.md +1 -1
  330. package/docs/pi-extensions.md +66 -3
  331. package/justfile +10 -1
  332. package/package.json +2 -2
  333. package/scripts/fleet.ts +22 -3
  334. package/scripts/lib/fleet-command.ts +5 -3
  335. package/scripts/lib/herdr-layout.ts +18 -0
  336. package/scripts/lib/peer-launch.ts +314 -0
  337. package/scripts/lib/team-project.ts +3 -1
  338. package/scripts/peer-launch.ts +259 -0
  339. package/skills/guided-workspace-setup/companion-manifest.json +2 -0
  340. package/.pi/harnesses/agent-hub/spawned-peers.js +0 -74
@@ -0,0 +1,356 @@
1
+ # pi Extensions
2
+
3
+ A catalog of the pi extensions in this repo — what each one does, how to run it, the
4
+ supporting data it needs, and how the ported set differs from upstream.
5
+
6
+ ---
7
+
8
+ ## Attribution
9
+
10
+ The session harnesses documented here — together with their supporting agent
11
+ definitions, design specs, and the `justfile` — are ported
12
+ from the **`pi-vs-claude-code`** project:
13
+
14
+ - **Author:** [disler](https://github.com/disler) (IndyDevDan)
15
+ - **Source:** <https://github.com/disler/pi-vs-claude-code>
16
+ - **License:** MIT — Copyright (c) 2026 IndyDevDan
17
+
18
+ Ported files retain their original authorship; this repo adapts them to its layout and
19
+ conventions. Runtime design specs for the imported harnesses live in `docs/pi-specs/`.
20
+
21
+ ---
22
+
23
+ ## What these extensions are
24
+
25
+ `.pi/extensions/` ships always-on **utility** extensions — `mcp-bridge`,
26
+ `chrome-devtools-mcp`, `compact-and-continue`, `agent-fleet-update-check`, `btw`, and
27
+ `pi-voice-stt`. pi
28
+ auto-discovers that directory, so they layer onto every session. `btw` adds a
29
+ `/af-btw <task>` prompt command (plus an `Alt+'` shortcut) that forks the current session
30
+ into an in-process sub-session and opens a live modal over it — full context, same
31
+ cwd, follow-up composer, with a compact result card landing in the main transcript at
32
+ idle. See [.pi/extensions/btw/README.md](../.pi/extensions/btw/README.md).
33
+
34
+ `pi-voice-stt` adds **Alt+S** push-to-talk dictation: it records the mic to a temp WAV via
35
+ `ffmpeg` and transcribes through one of three backends — a generic OpenAI-compatible endpoint,
36
+ Azure Speech (REST short-audio, with optional per-phrase language identification), or Azure
37
+ OpenAI Whisper (Azure AI Foundry). Alt+S toggles record→insert; Enter-while-recording
38
+ transcribes and sends; Esc cancels. It is **gated**: the hotkey binds only once a provider is
39
+ configured (project-local `.ai/stt.json`, the global `~/.pi/agent/stt.json`, or `PI_STT_CONFIG`),
40
+ so an unconfigured session is a no-op. `/af-stt doctor`
41
+ checks the setup. A simplified port of [`cgarrot/pi-voice-stt`](https://github.com/cgarrot/pi-voice-stt);
42
+ see [.pi/extensions/pi-voice-stt/README.md](../.pi/extensions/pi-voice-stt/README.md).
43
+
44
+ The documented harnesses below are different: each is a **session harness**. They
45
+ reshape the whole pi session — some set orchestration/UI surfaces and some gate every
46
+ tool call. The unified `just fleet` entry point composes them with a deterministic
47
+ Fleet Core: `damage-control-continue`, `ask-user-remote`, STT, Compact & Continue,
48
+ BTW, and the update checker. `just fleet hub` adds `agent-hub`; `just fleet peer`
49
+ adds standalone coms. Harnesses live in **`.pi/harnesses/`** — a directory pi does
50
+ *not* auto-discover — so a plain `pi` run still loads no safety/orchestration harness.
51
+
52
+ ### Selective loading — read this first
53
+
54
+ pi auto-discovers every extension directory under a project's `.pi/extensions/` and loads
55
+ all of them. If the harnesses lived there, a plain `pi` run would load them all at once
56
+ — UI surfaces would fight, orchestrators would collide, and harnesses that register the
57
+ same CLI flags would abort startup with duplicate registrations. So the harnesses live in
58
+ `.pi/harnesses/` instead, and you load the desired recipe explicitly:
59
+
60
+ - through the unified `justfile` interface — `just fleet`, `just fleet hub`, `just fleet peer <name>`, `just fleet team <preset>`, …
61
+ - or directly — `pi -e .pi/harnesses/<name>/index.ts` (advanced use; you must compose safety/utilities yourself)
62
+
63
+ When you consume this repo from another project, point `pi -e` at the harness file you
64
+ want, or symlink that one directory into *its* `.pi/harnesses/` — never drop the harnesses
65
+ into `.pi/extensions/`, and never load all of them at once. The supported multi-harness
66
+ exception is loading `damage-control-continue` and `ask-user-remote` before `agent-hub` for a guarded hub session (see
67
+ [pi-setup.md](pi-setup.md#optional-pi-extensions)).
68
+
69
+ ---
70
+
71
+ ## Setup
72
+
73
+ ```bash
74
+ just fleet install # one-time runtime deps only; starts no Pi/harness
75
+ just fleet # guarded Pi + STT and core utilities
76
+ just fleet hub # guarded multi-agent hub
77
+ just fleet team docs # hub + guarded Herdr peer team
78
+ just fleet peer code-reviewer --project af # ONE peer in its own Herdr pane, no team
79
+ just fleet help # unified command grammar
80
+ just --list # shows the single public `fleet` entry point
81
+ ```
82
+
83
+ `just install` runs `npm install` for both dependency roots: `.pi/extensions/` for the
84
+ utilities (`@modelcontextprotocol/sdk`, `typebox`) and `.pi/harnesses/` for the harnesses
85
+ (`@sinclair/typebox`, `yaml`). The extension dependencies are also root production dependencies
86
+ of the published `@chankov/agent-fleet` package. This is intentional: npm does not install a
87
+ nested `.pi/extensions/package.json`, and Node resolves symlinked extensions from their real path
88
+ inside the package. The `@mariozechner/pi-*` packages are provided by the pi runtime itself.
89
+
90
+ ---
91
+
92
+ ## Catalog
93
+
94
+ | Extension | Category | What it does | Run |
95
+ |-----------|----------|--------------|-----|
96
+ | [agent-hub](../.pi/harnesses/agent-hub/README.md) | Orchestration | Supported multi-agent hub: Fleet Core guardrails, dispatcher grid, specialist delegation, research helpers, persona gate, embedded coms, `/af-handoff`, peer-as-subagent, and footer `agent fleet v<version> · <model><thinking> · <team>` — plus, inside a [herdr](https://herdr.dev) pane, fleet tools (`herdr_spawn_peer` / `herdr_read_pane` / `herdr_close_pane` with human confirmation / `herdr_notify`) | `just fleet hub` |
97
+ | [ask-user-remote](../.pi/harnesses/ask-user-remote/README.md) | Orchestration | Captures stock `pi-ask-user` and registers the default `ask_user`; with `user-remote` live it races local UI against the Hermes bridge, otherwise it is stock local behavior | Fleet Core (`just fleet`) |
98
+ | [damage-control-continue](../.pi/harnesses/damage-control-continue/README.md) | Safety | Fleet Core safety harness; guards default Pi, Hub, native children, and Herdr Pi peers. Blocks feed back without aborting the turn; protected paths support explicit approval, while dangerous command patterns remain non-exemptible | `just fleet` |
99
+ | [coms](../.pi/harnesses/coms/README.md) | Messaging | Peer-to-peer messaging between agents on one machine, composed with Fleet Core safety and utilities | `just fleet peer <name>` |
100
+ | [Hermes local monitor transport](../hermes/README.md#local-agent-hub-monitor-integration) | Optional local companion | Owner-only discovery + Unix socket for agent-hub snapshots, cursor output, and exact-generation cancellation; consumed by a separate local Hermes client | Set the two monitor environment variables, then run `just fleet team <team>` |
101
+
102
+ Each extension directory has its own `README.md` with the full description, command/tool
103
+ surface, requirements, and per-extension upstream changes.
104
+
105
+ ### Migration: retired hard-stop harness
106
+
107
+ The former `.pi/harnesses/damage-control/` hard-stop harness and its standalone recipe
108
+ are retired. Refresh pi harnesses with guided setup: it removes only an unchanged,
109
+ setup-recorded copy (or an agent-fleet source symlink), preserves user-modified/unowned copies,
110
+ and refreshes the managed `justfile` region. Use `damage-control-continue` for standalone and
111
+ Agent Hub safety; missing child safety now fails closed instead of falling back or spawning
112
+ unguarded.
113
+
114
+ ### Harness version footer and provenance
115
+
116
+ The three persistent-UI harnesses — `agent-hub`, `coms`, and
117
+ `damage-control-continue` — each register `agent fleet v<version>` on one shared status key. In pi's
118
+ default status footer, that shared key gives a supported stack exactly one version instead of one
119
+ copy per harness. `agent-hub` replaces the default footer: it does **not** consume that status
120
+ key. Its custom footer reads its own adjacent stamped manifest and renders one local version
121
+ first — `agent fleet v<version> · <model><thinking> · <team>` — so an agent-hub stack also displays the
122
+ version exactly once.
123
+
124
+ The `agent fleet` half of that label is an [OSC 8](https://gist.github.com/egmontkob/eb114294efbcd5adb1944c9f3cb5feda)
125
+ terminal hyperlink to the project homepage, so a click in a terminal that supports hyperlinks
126
+ (Ghostty, iTerm2, WezTerm, Kitty, VS Code, GNOME Terminal, tmux 3.4+) opens the repository. It is a
127
+ terminal-level link, not a TUI control: pi has no mouse tracking, so a click cannot open an
128
+ in-process overlay — the URL goes to the OS opener. Terminals without OSC 8 support render the
129
+ label unchanged, and pi's `visibleWidth`/`truncateToWidth` strip OSC sequences, so the link costs no
130
+ footer columns. Set `AGENT_FLEET_NO_LINKS=1` to fall back to a plain label on multiplexers that
131
+ mangle unknown OSC sequences (GNU screen, tmux before 3.4).
132
+
133
+ The shared version status is independent of mutable owner status: for example, a
134
+ Damage-Control violation can replace its own safety message without overwriting the version
135
+ entry. The canonical value is the root `package.json` version. During a release,
136
+ `bin/sync-harness-versions.js` stamps that value into each adjacent persistent-harness
137
+ `package.json` after the root bump and before lockfile finalization and snapshotting. Each
138
+ harness keeps a local `version.ts` provenance reader so copied or symlinked harness directories
139
+ resolve their adjacent stamp rather than the launch directory. That local provenance does not
140
+ make a harness self-contained: copied target harnesses still require the existing full
141
+ `.pi/harnesses/` dependency installation described in [Setup](#setup).
142
+
143
+ ### `agent-hub` components
144
+
145
+ `agent-hub` is the consolidated orchestration harness. It replaces the retired standalone
146
+ `agent-team` recipe and absorbs the day-to-day pieces that previously required separate
147
+ harnesses:
148
+
149
+ - **Dispatcher grid** — fixed specialists from `.pi/agents/teams.yaml`, shown in a live dashboard
150
+ with compact/full view toggling.
151
+ - **Specialist delegation** — `dispatch_agent` for writable child-agent work and
152
+ `spawn_research` / `/af-research` for read-only investigation.
153
+ - **Verification Contract** — the dispatcher owns a ledger of checkable acceptance assertions
154
+ built before any builder runs, via the `set_assertions` / `update_assertion` tools. Each
155
+ assertion is tagged (`test` | `runtime-ui` | `code-grep` | `manual`) and advanced only on
156
+ *proven with evidence*; the ledger persists to `.pi/agent-sessions/assertions.json` (wiped at
157
+ session start like `findings/`) and shows a one-line status, keeping the contract out of the
158
+ dispatcher LLM context. It kills the parity failure (exemplar shipped, siblings missed) by
159
+ requiring a parity/touchpoint inventory for "behave like" requests and runtime proof for UI
160
+ assertions — see the [`orchestration-verification`](../skills/orchestration-verification/SKILL.md)
161
+ skill, which the `orchestrator` persona drives. Advisory in this phase (surfaced, not a hard
162
+ dispatch refusal).
163
+ - **Persona gate** — requires an orchestrator persona at startup unless disabled in the local
164
+ override file; the chosen persona also feeds the coms purpose when no explicit `--purpose` is set.
165
+ - **Operator controls** — `/af-zoom` timeline inspection plus child-agent kill/restart controls.
166
+ - **Damage-control + ask_user by default** — `just fleet hub` and `just fleet hub --solo` load the
167
+ `damage-control-continue` safety harness and `ask-user-remote` before `agent-hub`, so the
168
+ dispatcher's tool calls are checked against the rules file and the `askUserAvailable` probe sees
169
+ `ask_user`. A blocked call feeds back and the turn keeps going rather than aborting. `agent-hub` also
170
+ re-loads `damage-control-continue` into every native specialist, research helper, and nested
171
+ delegate (via an explicit `-e` that survives `--no-extensions`). Protected-path access can be
172
+ granted at runtime: `/af-allow <pattern> [turn|session]` in the hub pre-authorizes, a parent-session
173
+ block opens an approval dialog, and a headless child escalates to the hub. Protected deletion
174
+ offers only deny/once; other protected paths may be scoped to an agent or session. Denial and
175
+ timeout fail closed without aborting the child turn. Destructive bash patterns are never exemptible,
176
+ and a missing continue harness refuses child dispatch.
177
+ - **Embedded coms** — peer discovery, `coms_list` / `coms_send` / `coms_get` / `coms_await`,
178
+ `/af-handoff`, and peer-as-subagent flows.
179
+ - **Solo mode** — `just fleet hub --solo` keeps the dispatcher grid, delegation, research helpers, persona
180
+ gate, and controls, but starts without the embedded coms layer.
181
+ - **Optional Hermes local monitor transport** — uses `AGENT_FLEET_PROFILE_ID`, the absolute
182
+ `AGENT_FLEET_MONITOR_RUNTIME_DIR`, and the Herdr `HERDR_WORKSPACE_ID` and `HERDR_PANE_ID`
183
+ required to establish its stable hub identity. It is a source-owned, local-only transport—not a
184
+ Hermes SDK task/lifecycle RPC or a bundled plugin—and fails closed without validated owner-only
185
+ discovery, lease, token, and socket state. Follow the
186
+ [Hermes integration guide](../hermes/README.md#local-agent-hub-monitor-integration) for startup,
187
+ wire examples, cancellation semantics, and reconnect behavior.
188
+
189
+ ---
190
+
191
+ ## Two browser stacks — when to use which
192
+
193
+ This repo ships **two** ways to drive a browser from a pi agent. They are complementary, not redundant — the axis that separates them is the **tool model** (and where they can run), not just headless-vs-headful, since both can do either:
194
+
195
+ | | `bowser` / `playwright-cli` | `web-debugger` / `chrome-devtools-mcp` |
196
+ |---|---|---|
197
+ | Tool model | CLI over **Bash** (no tool schemas in context) | live `chrome_devtools__*` MCP tools |
198
+ | Strength | headless, parallel named sessions, background automation, scraping, token-efficient | interactive headful debugging, live DOM/console/network, performance traces |
199
+ | Where it runs | **dispatched subagent** (survives `--no-extensions`), peer, or main session | main session or **coms peer** (the extension must be loaded into the process) |
200
+ | Persona | `bowser` | `web-debugger` |
201
+ | Skill | `.pi/skills/bowser/` | `skills/browser-testing-with-devtools/` |
202
+
203
+ **Policy:**
204
+
205
+ - **Automated / CI / background / parallel runtime-UI evidence** → `bowser` (headless `playwright-cli`). This is what the `orchestrator` delegates as a subagent to close `runtime-ui` acceptance assertions.
206
+ - **Interactive debugging of a running dev app** → `web-debugger` (headful `chrome-devtools-mcp`), reached as a coms peer or run on the main session.
207
+ - **Manual visual inspection / login flows** → `web-debugger` headful, or attach to an existing Chrome.
208
+ - **Always require runtime evidence** — snapshot + console + network before/after a critical interaction; a screenshot only for visual/layout confirmation.
209
+
210
+ Why `web-debugger` is a coms peer and not a dispatchable subagent: its `chrome_devtools__*` tools come from the always-on `chrome-devtools-mcp` extension, and agent-hub spawns subagents with `--no-extensions`, so a dispatched child would not have those tools. A coms peer is its own pi process that loads the extension explicitly (via the `extensions:` field in `.pi/agents/peers.yaml`, routed through the `_peer-plus` recipe), and a long-lived peer maps naturally onto one persistent live browser. `bowser` has no such constraint because it only needs Bash + the `playwright-cli` binary on PATH.
211
+
212
+ ## One peer at a time — `just fleet peer`
213
+
214
+ `just fleet team <preset>` is the right tool for a *known* set of collaborators, but it
215
+ requires every peer to be declared in `.pi/agents/peers.yaml` and it builds a whole
216
+ workspace. When you want **one** more agent — often a Claude Code reviewer — next to
217
+ what you already have:
218
+
219
+ ```bash
220
+ just fleet peer code-reviewer --project af # peers.yaml decides the runner
221
+ just fleet peer scratch-reviewer --runner claude-code --model opus --project af
222
+ just fleet peer researcher --model openai-codex/gpt-5.6-luna --project af
223
+ just fleet peer web-debugger --browser --project af # persona peer + devtools MCP
224
+ just fleet peer nick --here --project af # this terminal, not a pane
225
+ just fleet peer anything --runner claude-code --dry-run # print the plan, touch nothing
226
+ ```
227
+
228
+ **The name decides the shape of the peer** — one verb, three launchers:
229
+
230
+ | The name… | Peer | Recipe |
231
+ |---|---|---|
232
+ | is declared in `peers.yaml` | whatever it declares (`runner`, `model`, `extensions`, `env_file`) | per declaration |
233
+ | matches `agents/<name>.md` | that guarded persona peer | `_peer` / `_peer-plus` |
234
+ | matches nothing | Fleet Core + coms under that identity, no persona | `_fleet-peer` |
235
+ | `--runner claude-code` | interactive Claude Code + its coms bridge in one pane | `_claude-peer` |
236
+
237
+ The third row is what this command meant before pane placement existed, and it is the
238
+ only shape that accepts raw pi arguments — everything after `--` goes to pi verbatim
239
+ (`just fleet peer nick --here -- --session /path/to/session.json`). Note that the
240
+ persona-by-name rule can change what an existing invocation means: `agents/architect.md`
241
+ exists, so `just fleet peer architect` is now the architect persona peer. `--no-persona`
242
+ forces the plain Fleet Core shape back.
243
+
244
+ - **Placement** — by default the peer gets its own pane: run inside a herdr pane and it
245
+ splits *that* pane (`--direction right|down`); run outside herdr and it creates a
246
+ single-pane workspace labelled `<worktree-tag>-peer-<name>`, refusing to clobber an
247
+ existing one. `--here` runs it in the calling terminal instead.
248
+ - **Field resolution** — explicit flag → the `peers.yaml` declaration for that *name*
249
+ (searched across every team) → a convention default. A name the fleet already defines
250
+ keeps its declared fields; a name it does not need no manifest entry at all.
251
+ - **Nothing is silently dropped** — a flag that cannot apply to the resolved shape is an
252
+ error, not a no-op: `--all-extensions` on a persona peer, `--persona` on a Claude Code
253
+ peer, a mistyped flag, or a pi flag that forgot its `--` separator.
254
+ - **`--project` matters** — same rule as teams: the flag form is `--project af`;
255
+ `project=af` is a `just` variable override and is silently ignored, leaving the peer
256
+ in the shared `default` pool.
257
+ - **Readiness** — a pane launch waits (bounded) for the peer to register in the coms pool
258
+ and exits non-zero with the pane's last output if it never does. A peer that missed
259
+ the window has failed to start, not started slowly.
260
+
261
+ Pure logic in `scripts/lib/peer-launch.ts` (under `node --test`); the herdr wiring is
262
+ `scripts/peer-launch.ts`. Inside a hub session the equivalent is the `herdr_spawn_peer`
263
+ tool, which shares the same command builder and readiness policy.
264
+
265
+ ## Environment variables
266
+
267
+ The `justfile` sets `dotenv-load`, so a `.env` file at the repo root is auto-loaded
268
+ (`.env` is gitignored). Only a few extensions need keys:
269
+
270
+ | Variable | Needed by | Purpose |
271
+ |----------|-----------|---------|
272
+ | `PI_CHROME_DEVTOOLS_MODE` | `chrome-devtools-mcp` | `headless` runs Chrome with no UI; anything else (default) is headed |
273
+ | `PI_CHROME_DEVTOOLS_BROWSER_URL` | `chrome-devtools-mcp` | Attach to a running Chrome (e.g. `http://127.0.0.1:9222`) instead of launching one |
274
+ | `PI_CHROME_DEVTOOLS_USER_DATA_DIR` | `chrome-devtools-mcp` | Persistent Chrome profile path (else the default ephemeral `--isolated` profile) |
275
+ | `OPENAI_API_KEY` | `pi-voice-stt` (openai backend) | API key for the OpenAI-compatible transcription endpoint (var name overridable via `provider.apiKeyEnv`) |
276
+ | `AZURE_SPEECH_KEY` | `pi-voice-stt` (azure backend) | Azure Speech resource key |
277
+ | `AZURE_SPEECH_ENDPOINT` | `pi-voice-stt` (azure backend) | Azure resource endpoint, used when `provider.endpoint` is unset |
278
+ | `PI_STT_CONFIG` / `PI_STT_KEYBIND` | `pi-voice-stt` | Override config (inline JSON or path) / the record hotkey (default `alt+s`) |
279
+ | `AGENT_FLEET_SPAWN_DELAY` | `_peer` / `_peer-plus` recipes | Seconds to sleep before launching pi in a fleet pane (set per pane by `just fleet team`/`just fleet resume`, see below) |
280
+
281
+ The `chrome-devtools-mcp` server starts once at extension load, so changing its vars needs a pi
282
+ restart / `/reload` to take effect.
283
+
284
+ ### Spawn pre-warm/stagger
285
+
286
+ pi loads its credential store (`~/.pi/agent/auth.json`) once at boot under a short-retry
287
+ file lock. When the stored OAuth token is stale, the first pi to boot refreshes it over
288
+ the network *while holding that lock*; sibling panes spawned in the same instant (as
289
+ `just fleet team` / `just fleet resume` do) lose the lock race and come up
290
+ with every provider showing **unconfigured**. To dodge this, the team scripts check
291
+ `auth.json` before spawning (only `type`/`expires` are read — values never leave the
292
+ process): if any OAuth credential is expired or about to expire, one pi pane (the hub
293
+ when present, else the first pi peer) starts immediately and refreshes the token, and
294
+ every other pi pane gets `AGENT_FLEET_SPAWN_DELAY` in its pane env — the `_peer` /
295
+ `_peer-plus` recipes sleep that many seconds before launching pi. Fresh tokens mean zero
296
+ delay everywhere; `claude-code` runner panes never wait. Pure logic in
297
+ `scripts/lib/spawn-stagger.ts` (under `node --test`).
298
+
299
+ ---
300
+
301
+ ## Supporting data
302
+
303
+ These ported files are runtime dependencies of the extensions above:
304
+
305
+ - **`agents/`** — canonical persona Markdown files for shared and pi-specific agents.
306
+ Read by `agent-hub`.
307
+ - **`.pi/agents/`** — pi YAML configs only (`teams.yaml`, `peers.yaml`).
308
+ The earlier `reviewer` and `red-team` personas were folded into `code-reviewer` and
309
+ `security-auditor`; the remaining team/peer configs already reference the canonical names.
310
+ A peer entry may carry an optional `extensions:` field (comma-separated names under
311
+ `.pi/extensions/`) — Fleet's team launcher then routes it through the `_peer-plus` recipe so those
312
+ extensions load into the peer process. The `web-debugger` peer uses this to get
313
+ `chrome-devtools-mcp`'s `chrome_devtools__*` tools (see the two-browser-stacks section above).
314
+ - **`.pi/damage-control-rules.yaml`** — the destructive-command / protected-path rule set
315
+ for `damage-control-continue`.
316
+ - **`.pi/skills/bowser/`** — a pi-runtime skill for headless Playwright browser
317
+ automation, used by the `bowser` agent persona. Kept separate from the core
318
+ engineering `skills/`. It drives the external **Playwright Agent CLI**
319
+ (`playwright-cli`), which is **not** bundled — install it once with
320
+ `npm install -g @playwright/cli@latest` (the guided setup checks for it when
321
+ `bowser` is selected). Docs: <https://playwright.dev/agent-cli/installation>.
322
+ - **`docs/pi-specs/`** — the original design specifications: `agent-forge` (now consolidated
323
+ into `agent-hub`), `agent-workflow` (retired `agent-chain`), and `damage-control`.
324
+
325
+ ---
326
+
327
+ ## Upstream changes
328
+
329
+ What changed relative to `disler/pi-vs-claude-code`:
330
+
331
+ - **Theme code removed.** Every ported harness imported `applyExtensionDefaults` from a
332
+ shared `themeMap.ts`. That import and its `session_start` call site were stripped from
333
+ the ported files; `themeMap.ts` and the 11 `.pi/themes/*.json` palettes are not ported.
334
+ Extensions render against pi's active theme.
335
+ - **Layout converted.** Flat `extensions/<name>.ts` files became
336
+ `.pi/harnesses/<name>/index.ts` directories, each with its own `package.json` and
337
+ `README.md`. They live under `.pi/harnesses/` — *not* `.pi/extensions/` — because pi
338
+ auto-discovers and loads everything in `.pi/extensions/`, while harnesses must be loaded
339
+ explicitly through recipes (with `damage-control-continue` + `ask-user-remote` before
340
+ `agent-hub` as the supported stack).
341
+ - **Tooling switched to npm.** `bun` / `bun.lock` are not used; the `justfile` recipes
342
+ point at the new paths and use npm.
343
+
344
+ ### Not ported
345
+
346
+ - The `pure-focus`, `theme-cycler`, and `cross-agent` extensions.
347
+ - `themeMap.ts` and all 11 `.pi/themes/*.json` theme palettes.
348
+ - The Claude Code `statusLine` config and `status_lines/status_line.py`, and the
349
+ `plan_w_team.md` command (it depended on team-agent files absent from the source).
350
+
351
+ ### A note on `.pi/settings.json`
352
+
353
+ Upstream shipped a `.pi/settings.json` that only set the (now-stripped) theme and
354
+ registered a prompt directory. This repo already keeps pi prompts in the standard
355
+ `.pi/prompts/` location, so no `.pi/settings.json` is shipped — it would carry nothing
356
+ useful.