@chankov/agent-fleet 0.0.3 → 0.0.5

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 (608) hide show
  1. package/.claude/commands/set-hermes-telegram.md +15 -0
  2. package/.claude/commands/setup-agent-fleet.md +1 -1
  3. package/.opencode/commands/af-set-hermes-telegram.md +15 -0
  4. package/.opencode/commands/af-setup-agent-fleet.md +1 -1
  5. package/.pi/agents/dispatch-policy.yaml +1 -1
  6. package/.pi/agents/peers.yaml +4 -4
  7. package/.pi/extensions/chrome-devtools-mcp/README.md +1 -1
  8. package/.pi/extensions/mcp-bridge/README.md +1 -1
  9. package/.pi/harnesses/agent-hub/README.md +223 -40
  10. package/.pi/harnesses/agent-hub/access-approval.ts +135 -0
  11. package/.pi/harnesses/agent-hub/delegate.ts +32 -9
  12. package/.pi/harnesses/agent-hub/drift-watchdog.js +165 -0
  13. package/.pi/harnesses/agent-hub/footer.ts +29 -0
  14. package/.pi/harnesses/agent-hub/helpers.ts +49 -0
  15. package/.pi/harnesses/agent-hub/index.ts +1037 -246
  16. package/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
  17. package/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
  18. package/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
  19. package/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
  20. package/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
  21. package/.pi/harnesses/agent-hub/monitor-session-bridge.ts +11 -0
  22. package/.pi/harnesses/agent-hub/package.json +5 -4
  23. package/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
  24. package/.pi/harnesses/agent-hub/run-budget.js +155 -0
  25. package/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
  26. package/.pi/harnesses/agent-hub/spawn.ts +161 -94
  27. package/.pi/harnesses/agent-hub/version.ts +18 -0
  28. package/.pi/harnesses/ask-user-remote/README.md +1 -0
  29. package/.pi/harnesses/ask-user-remote/index.ts +36 -8
  30. package/.pi/harnesses/coms/README.md +15 -5
  31. package/.pi/harnesses/coms/index.ts +2 -0
  32. package/.pi/harnesses/coms/package.json +5 -4
  33. package/.pi/harnesses/coms/version.ts +18 -0
  34. package/.pi/harnesses/damage-control-continue/README.md +36 -35
  35. package/.pi/harnesses/damage-control-continue/index.ts +23 -9
  36. package/.pi/harnesses/damage-control-continue/package.json +5 -4
  37. package/.pi/harnesses/damage-control-continue/version.ts +18 -0
  38. package/.pi/harnesses/{damage-control/shared.ts → lib/damage-control-shared.ts} +20 -6
  39. package/.pi/harnesses/lib/hermes-monitor-herdr.ts +28 -0
  40. package/.pi/harnesses/lib/hermes-monitor-model.ts +9 -0
  41. package/.pi/harnesses/lib/hermes-monitor-registry.ts +6 -0
  42. package/.pi/harnesses/lib/hermes-monitor-socket.ts +118 -0
  43. package/.pi/harnesses/lib/hermes-monitor-store.ts +31 -0
  44. package/.pi/prompts/set-hermes-telegram.md +15 -0
  45. package/.pi/prompts/setup-agent-fleet.md +1 -1
  46. package/.versions/0.0.4/.claude/commands/build.md +44 -0
  47. package/.versions/0.0.4/.claude/commands/code-simplify.md +22 -0
  48. package/.versions/0.0.4/.claude/commands/design-agent.md +14 -0
  49. package/.versions/0.0.4/.claude/commands/doctor-agent-fleet.md +17 -0
  50. package/.versions/0.0.4/.claude/commands/orchestrate.md +112 -0
  51. package/.versions/0.0.4/.claude/commands/plan.md +16 -0
  52. package/.versions/0.0.4/.claude/commands/prime.md +22 -0
  53. package/.versions/0.0.4/.claude/commands/review.md +16 -0
  54. package/.versions/0.0.4/.claude/commands/setup-agent-fleet.md +25 -0
  55. package/.versions/0.0.4/.claude/commands/ship.md +72 -0
  56. package/.versions/0.0.4/.claude/commands/spec.md +15 -0
  57. package/.versions/0.0.4/.claude/commands/test.md +19 -0
  58. package/.versions/0.0.4/.claude/commands/webperf.md +32 -0
  59. package/.versions/0.0.4/.claude/orchestrate-teams.yaml +24 -0
  60. package/.versions/0.0.4/.opencode/commands/af-build.md +17 -0
  61. package/.versions/0.0.4/.opencode/commands/af-code-simplify.md +16 -0
  62. package/.versions/0.0.4/.opencode/commands/af-compound.md +16 -0
  63. package/.versions/0.0.4/.opencode/commands/af-design-agent.md +15 -0
  64. package/.versions/0.0.4/.opencode/commands/af-doctor-agent-fleet.md +17 -0
  65. package/.versions/0.0.4/.opencode/commands/af-orchestrate.md +112 -0
  66. package/.versions/0.0.4/.opencode/commands/af-plan.md +16 -0
  67. package/.versions/0.0.4/.opencode/commands/af-prime.md +22 -0
  68. package/.versions/0.0.4/.opencode/commands/af-review.md +15 -0
  69. package/.versions/0.0.4/.opencode/commands/af-setup-agent-fleet.md +15 -0
  70. package/.versions/0.0.4/.opencode/commands/af-ship.md +16 -0
  71. package/.versions/0.0.4/.opencode/commands/af-spec.md +16 -0
  72. package/.versions/0.0.4/.opencode/commands/af-test.md +21 -0
  73. package/.versions/0.0.4/.opencode/commands/af-webperf.md +32 -0
  74. package/.versions/0.0.4/.opencode/orchestrate-teams.yaml +24 -0
  75. package/.versions/0.0.4/.pi/agents/dispatch-policy.yaml +32 -0
  76. package/.versions/0.0.4/.pi/agents/model-profiles.yaml +20 -0
  77. package/.versions/0.0.4/.pi/agents/peers.yaml +146 -0
  78. package/.versions/0.0.4/.pi/agents/teams.yaml +39 -0
  79. package/.versions/0.0.4/.pi/damage-control-rules.yaml +297 -0
  80. package/.versions/0.0.4/.pi/extensions/agent-fleet-update-check/README.md +58 -0
  81. package/.versions/0.0.4/.pi/extensions/agent-fleet-update-check/index.ts +161 -0
  82. package/{.pi/harnesses/damage-control → .versions/0.0.4/.pi/extensions/agent-fleet-update-check}/package.json +1 -1
  83. package/.versions/0.0.4/.pi/extensions/btw/README.md +118 -0
  84. package/.versions/0.0.4/.pi/extensions/btw/index.ts +917 -0
  85. package/.versions/0.0.4/.pi/extensions/btw/package.json +6 -0
  86. package/.versions/0.0.4/.pi/extensions/btw/state.js +179 -0
  87. package/.versions/0.0.4/.pi/extensions/chrome-devtools-mcp/README.md +58 -0
  88. package/.versions/0.0.4/.pi/extensions/chrome-devtools-mcp/index.ts +92 -0
  89. package/.versions/0.0.4/.pi/extensions/chrome-devtools-mcp/package.json +6 -0
  90. package/.versions/0.0.4/.pi/extensions/compact-and-continue/README.md +42 -0
  91. package/.versions/0.0.4/.pi/extensions/compact-and-continue/index.ts +120 -0
  92. package/.versions/0.0.4/.pi/extensions/compact-and-continue/package.json +6 -0
  93. package/.versions/0.0.4/.pi/extensions/mcp-bridge/README.md +46 -0
  94. package/.versions/0.0.4/.pi/extensions/mcp-bridge/index.ts +206 -0
  95. package/.versions/0.0.4/.pi/extensions/mcp-bridge/package.json +6 -0
  96. package/.versions/0.0.4/.pi/extensions/package-lock.json +1143 -0
  97. package/.versions/0.0.4/.pi/extensions/package.json +9 -0
  98. package/.versions/0.0.4/.pi/extensions/pi-voice-stt/README.md +201 -0
  99. package/.versions/0.0.4/.pi/extensions/pi-voice-stt/config.ts +198 -0
  100. package/.versions/0.0.4/.pi/extensions/pi-voice-stt/examples/stt.json +35 -0
  101. package/.versions/0.0.4/.pi/extensions/pi-voice-stt/index.ts +248 -0
  102. package/.versions/0.0.4/.pi/extensions/pi-voice-stt/package.json +6 -0
  103. package/.versions/0.0.4/.pi/extensions/pi-voice-stt/providers.ts +214 -0
  104. package/.versions/0.0.4/.pi/extensions/pi-voice-stt/recorder.ts +158 -0
  105. package/.versions/0.0.4/.pi/harnesses/agent-hub/README.md +798 -0
  106. package/.versions/0.0.4/.pi/harnesses/agent-hub/access-approval.ts +135 -0
  107. package/.versions/0.0.4/.pi/harnesses/agent-hub/artifacts.js +92 -0
  108. package/.versions/0.0.4/.pi/harnesses/agent-hub/backend-policy.js +153 -0
  109. package/.versions/0.0.4/.pi/harnesses/agent-hub/delegate.ts +386 -0
  110. package/.versions/0.0.4/.pi/harnesses/agent-hub/drift-watchdog.js +165 -0
  111. package/.versions/0.0.4/.pi/harnesses/agent-hub/evidence-rules.js +96 -0
  112. package/.versions/0.0.4/.pi/harnesses/agent-hub/footer.ts +29 -0
  113. package/.versions/0.0.4/.pi/harnesses/agent-hub/helpers.ts +214 -0
  114. package/.versions/0.0.4/.pi/harnesses/agent-hub/index.ts +8045 -0
  115. package/.versions/0.0.4/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
  116. package/.versions/0.0.4/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
  117. package/.versions/0.0.4/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
  118. package/.versions/0.0.4/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
  119. package/.versions/0.0.4/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
  120. package/.versions/0.0.4/.pi/harnesses/agent-hub/monitor-session-bridge.ts +11 -0
  121. package/.versions/0.0.4/.pi/harnesses/agent-hub/package.json +7 -0
  122. package/.versions/0.0.4/.pi/harnesses/agent-hub/research-retention.js +34 -0
  123. package/.versions/0.0.4/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
  124. package/.versions/0.0.4/.pi/harnesses/agent-hub/return-contract.js +215 -0
  125. package/.versions/0.0.4/.pi/harnesses/agent-hub/run-budget.js +155 -0
  126. package/.versions/0.0.4/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
  127. package/.versions/0.0.4/.pi/harnesses/agent-hub/scope-gate.js +103 -0
  128. package/.versions/0.0.4/.pi/harnesses/agent-hub/spawn.ts +246 -0
  129. package/.versions/0.0.4/.pi/harnesses/agent-hub/version.ts +18 -0
  130. package/.versions/0.0.4/.pi/harnesses/ask-user-remote/README.md +18 -0
  131. package/.versions/0.0.4/.pi/harnesses/ask-user-remote/index.ts +293 -0
  132. package/.versions/0.0.4/.pi/harnesses/ask-user-remote/race-core.js +106 -0
  133. package/.versions/0.0.4/.pi/harnesses/coms/README.md +92 -0
  134. package/.versions/0.0.4/.pi/harnesses/coms/index.ts +1745 -0
  135. package/.versions/0.0.4/.pi/harnesses/coms/package.json +7 -0
  136. package/.versions/0.0.4/.pi/harnesses/coms/version.ts +18 -0
  137. package/.versions/0.0.4/.pi/harnesses/damage-control-continue/README.md +117 -0
  138. package/.versions/0.0.4/.pi/harnesses/damage-control-continue/index.ts +536 -0
  139. package/.versions/0.0.4/.pi/harnesses/damage-control-continue/package.json +7 -0
  140. package/.versions/0.0.4/.pi/harnesses/damage-control-continue/version.ts +18 -0
  141. package/.versions/0.0.4/.pi/harnesses/lib/damage-control-shared.ts +197 -0
  142. package/.versions/0.0.4/.pi/harnesses/lib/herdr-client.ts +458 -0
  143. package/.versions/0.0.4/.pi/harnesses/lib/herdr-presence.ts +288 -0
  144. package/.versions/0.0.4/.pi/harnesses/package-lock.json +35 -0
  145. package/.versions/0.0.4/.pi/harnesses/package.json +9 -0
  146. package/.versions/0.0.4/.pi/prompts/build.md +24 -0
  147. package/.versions/0.0.4/.pi/prompts/code-simplify.md +22 -0
  148. package/.versions/0.0.4/.pi/prompts/doctor-agent-fleet.md +15 -0
  149. package/.versions/0.0.4/.pi/prompts/plan.md +16 -0
  150. package/.versions/0.0.4/.pi/prompts/review.md +16 -0
  151. package/.versions/0.0.4/.pi/prompts/setup-agent-fleet.md +27 -0
  152. package/.versions/0.0.4/.pi/prompts/ship.md +17 -0
  153. package/.versions/0.0.4/.pi/prompts/spec.md +15 -0
  154. package/.versions/0.0.4/.pi/prompts/test.md +19 -0
  155. package/.versions/0.0.4/.pi/skills/bowser/SKILL.md +145 -0
  156. package/.versions/0.0.4/.version +1 -0
  157. package/.versions/0.0.4/agents/architect.md +23 -0
  158. package/.versions/0.0.4/agents/bowser.md +26 -0
  159. package/.versions/0.0.4/agents/builder.md +53 -0
  160. package/.versions/0.0.4/agents/code-reviewer.md +205 -0
  161. package/.versions/0.0.4/agents/deep-researcher.md +31 -0
  162. package/.versions/0.0.4/agents/documenter.md +18 -0
  163. package/.versions/0.0.4/agents/orchestrator.md +54 -0
  164. package/.versions/0.0.4/agents/plan-reviewer.md +60 -0
  165. package/.versions/0.0.4/agents/planner.md +69 -0
  166. package/.versions/0.0.4/agents/releaser.md +24 -0
  167. package/.versions/0.0.4/agents/researcher.md +28 -0
  168. package/.versions/0.0.4/agents/security-auditor.md +166 -0
  169. package/.versions/0.0.4/agents/test-engineer.md +151 -0
  170. package/.versions/0.0.4/agents/web-debugger.md +42 -0
  171. package/.versions/0.0.4/agents/web-performance-auditor.md +192 -0
  172. package/.versions/0.0.4/codex/CONDUCTOR.md +148 -0
  173. package/.versions/0.0.4/docs/ARCHITECTURE.md +210 -0
  174. package/.versions/0.0.4/docs/agent-fleet-setup.md +366 -0
  175. package/.versions/0.0.4/docs/claude-code-coms-bridge.md +103 -0
  176. package/.versions/0.0.4/docs/codex-remote-conductor.md +170 -0
  177. package/.versions/0.0.4/docs/coms-hermes-bridge.md +121 -0
  178. package/.versions/0.0.4/docs/getting-started.md +183 -0
  179. package/.versions/0.0.4/docs/npm-install.md +337 -0
  180. package/.versions/0.0.4/docs/opencode-setup.md +248 -0
  181. package/.versions/0.0.4/docs/pi-extensions.md +288 -0
  182. package/.versions/0.0.4/docs/pi-setup.md +463 -0
  183. package/.versions/0.0.4/docs/skill-anatomy.md +150 -0
  184. package/.versions/0.0.4/hermes/README.md +228 -0
  185. package/.versions/0.0.4/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
  186. package/.versions/0.0.4/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
  187. package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-cap.test.py +15 -0
  188. package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-discovery.test.py +19 -0
  189. package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-envelope.test.py +13 -0
  190. package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-forged-owner.test.py +11 -0
  191. package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-lease-list.test.py +9 -0
  192. package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-multihub.test.py +17 -0
  193. package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-output.test.py +34 -0
  194. package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +151 -0
  195. package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter.test.py +39 -0
  196. package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
  197. package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/plugin-api-validation.test.py +12 -0
  198. package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
  199. package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/review-live-wiring.red.test.py +22 -0
  200. package/.versions/0.0.4/hermes/skills/hub-conductor/SKILL.md +84 -0
  201. package/.versions/0.0.4/hermes/skills/hub-liaison/SKILL.md +84 -0
  202. package/.versions/0.0.4/hooks/SIMPLIFY-IGNORE.md +90 -0
  203. package/.versions/0.0.4/hooks/coms-stop-hook.mjs +73 -0
  204. package/.versions/0.0.4/hooks/hooks.json +14 -0
  205. package/.versions/0.0.4/hooks/session-start.sh +74 -0
  206. package/.versions/0.0.4/hooks/simplify-ignore.sh +302 -0
  207. package/.versions/0.0.4/justfile +256 -0
  208. package/.versions/0.0.4/references/accessibility-checklist.md +160 -0
  209. package/.versions/0.0.4/references/definition-of-done.md +67 -0
  210. package/.versions/0.0.4/references/fleet-coordination-patterns.md +151 -0
  211. package/.versions/0.0.4/references/observability-checklist.md +91 -0
  212. package/.versions/0.0.4/references/orchestration-patterns.md +370 -0
  213. package/.versions/0.0.4/references/performance-checklist.md +153 -0
  214. package/.versions/0.0.4/references/prompting-patterns.md +380 -0
  215. package/.versions/0.0.4/references/security-checklist.md +179 -0
  216. package/.versions/0.0.4/references/testing-patterns.md +236 -0
  217. package/.versions/0.0.4/scripts/codex-conductor.ts +41 -0
  218. package/.versions/0.0.4/scripts/codex-remote-control.ts +167 -0
  219. package/.versions/0.0.4/scripts/coms-claude-bridge.ts +286 -0
  220. package/.versions/0.0.4/scripts/coms-cli.ts +484 -0
  221. package/.versions/0.0.4/scripts/coms-hermes-bridge.ts +403 -0
  222. package/.versions/0.0.4/scripts/hermes-monitor-capability-runner.ts +25 -0
  223. package/.versions/0.0.4/scripts/hermes-monitor-scenario.ts +7 -0
  224. package/.versions/0.0.4/scripts/lib/claude-bridge-core.ts +100 -0
  225. package/.versions/0.0.4/scripts/lib/codex-conductor.ts +88 -0
  226. package/.versions/0.0.4/scripts/lib/codex-remote-control.ts +480 -0
  227. package/.versions/0.0.4/scripts/lib/coms-envelope.ts +539 -0
  228. package/.versions/0.0.4/scripts/lib/fake-herdr-server.ts +88 -0
  229. package/.versions/0.0.4/scripts/lib/herdr-layout.ts +263 -0
  230. package/.versions/0.0.4/scripts/lib/hermes-bridge-core.ts +238 -0
  231. package/.versions/0.0.4/scripts/lib/hermes-monitor-herdr.ts +28 -0
  232. package/.versions/0.0.4/scripts/lib/hermes-monitor-model.ts +9 -0
  233. package/.versions/0.0.4/scripts/lib/hermes-monitor-registry.ts +6 -0
  234. package/.versions/0.0.4/scripts/lib/hermes-monitor-socket.ts +118 -0
  235. package/.versions/0.0.4/scripts/lib/hermes-monitor-store.ts +31 -0
  236. package/.versions/0.0.4/scripts/lib/persona-banner.ts +62 -0
  237. package/.versions/0.0.4/scripts/lib/spawn-stagger.ts +101 -0
  238. package/.versions/0.0.4/scripts/lib/team-project.ts +184 -0
  239. package/.versions/0.0.4/scripts/lib/team-snapshot.ts +147 -0
  240. package/.versions/0.0.4/scripts/peer-banner.ts +40 -0
  241. package/.versions/0.0.4/scripts/team-snapshot.ts +238 -0
  242. package/.versions/0.0.4/scripts/team-up.ts +333 -0
  243. package/.versions/0.0.4/skills/_internal/grilling.md +11 -0
  244. package/.versions/0.0.4/skills/browser-testing-with-devtools/SKILL.md +352 -0
  245. package/.versions/0.0.4/skills/code-review-and-quality/SKILL.md +381 -0
  246. package/.versions/0.0.4/skills/compound-learning/SKILL.md +137 -0
  247. package/.versions/0.0.4/skills/context-engineering/SKILL.md +291 -0
  248. package/.versions/0.0.4/skills/deprecation-and-migration/SKILL.md +206 -0
  249. package/.versions/0.0.4/skills/designing-agents/SKILL.md +394 -0
  250. package/.versions/0.0.4/skills/designing-agents/pi-harness-authoring.md +222 -0
  251. package/.versions/0.0.4/skills/frontend-ui-engineering/SKILL.md +328 -0
  252. package/.versions/0.0.4/skills/git-workflow-and-versioning/SKILL.md +316 -0
  253. package/.versions/0.0.4/skills/guided-workspace-setup/SKILL.md +535 -0
  254. package/.versions/0.0.4/skills/guided-workspace-setup/companion-manifest.json +33 -0
  255. package/.versions/0.0.4/skills/idea-refine/SKILL.md +182 -0
  256. package/.versions/0.0.4/skills/idea-refine/examples.md +238 -0
  257. package/.versions/0.0.4/skills/idea-refine/frameworks.md +99 -0
  258. package/.versions/0.0.4/skills/idea-refine/refinement-criteria.md +113 -0
  259. package/.versions/0.0.4/skills/idea-refine/scripts/idea-refine.sh +15 -0
  260. package/.versions/0.0.4/skills/incremental-implementation/SKILL.md +287 -0
  261. package/.versions/0.0.4/skills/interview-me/SKILL.md +226 -0
  262. package/.versions/0.0.4/skills/orchestration-verification/SKILL.md +181 -0
  263. package/.versions/0.0.4/skills/peer-coms/SKILL.md +90 -0
  264. package/.versions/0.0.4/skills/performance-optimization/SKILL.md +350 -0
  265. package/.versions/0.0.4/skills/planning-and-task-breakdown/SKILL.md +236 -0
  266. package/.versions/0.0.4/skills/security-and-hardening/SKILL.md +461 -0
  267. package/.versions/0.0.4/skills/spec-driven-development/SKILL.md +245 -0
  268. package/.versions/0.0.4/skills/using-agent-skills/SKILL.md +199 -0
  269. package/.versions/0.0.4/systemd/user/agent-fleet-codex-remote-control.service.in +23 -0
  270. package/.versions/0.0.4/vendor/agent-skills-upstream/LICENSE +21 -0
  271. package/.versions/0.0.4/vendor/agent-skills-upstream/README.md +11 -0
  272. package/.versions/0.0.4/vendor/agent-skills-upstream/skills/api-and-interface-design/SKILL.md +294 -0
  273. package/.versions/0.0.4/vendor/agent-skills-upstream/skills/browser-testing-with-devtools/SKILL.md +317 -0
  274. package/.versions/0.0.4/vendor/agent-skills-upstream/skills/ci-cd-and-automation/SKILL.md +390 -0
  275. package/.versions/0.0.4/vendor/agent-skills-upstream/skills/code-review-and-quality/SKILL.md +396 -0
  276. package/.versions/0.0.4/vendor/agent-skills-upstream/skills/code-simplification/SKILL.md +331 -0
  277. package/.versions/0.0.4/vendor/agent-skills-upstream/skills/context-engineering/SKILL.md +289 -0
  278. package/.versions/0.0.4/vendor/agent-skills-upstream/skills/debugging-and-error-recovery/SKILL.md +300 -0
  279. package/.versions/0.0.4/vendor/agent-skills-upstream/skills/deprecation-and-migration/SKILL.md +247 -0
  280. package/.versions/0.0.4/vendor/agent-skills-upstream/skills/documentation-and-adrs/SKILL.md +278 -0
  281. package/.versions/0.0.4/vendor/agent-skills-upstream/skills/doubt-driven-development/SKILL.md +243 -0
  282. package/.versions/0.0.4/vendor/agent-skills-upstream/skills/frontend-ui-engineering/SKILL.md +328 -0
  283. package/.versions/0.0.4/vendor/agent-skills-upstream/skills/git-workflow-and-versioning/SKILL.md +355 -0
  284. package/.versions/0.0.4/vendor/agent-skills-upstream/skills/idea-refine/SKILL.md +178 -0
  285. package/.versions/0.0.4/vendor/agent-skills-upstream/skills/idea-refine/examples.md +238 -0
  286. package/.versions/0.0.4/vendor/agent-skills-upstream/skills/idea-refine/frameworks.md +99 -0
  287. package/.versions/0.0.4/vendor/agent-skills-upstream/skills/idea-refine/refinement-criteria.md +113 -0
  288. package/.versions/0.0.4/vendor/agent-skills-upstream/skills/idea-refine/scripts/idea-refine.sh +15 -0
  289. package/.versions/0.0.4/vendor/agent-skills-upstream/skills/incremental-implementation/SKILL.md +249 -0
  290. package/.versions/0.0.4/vendor/agent-skills-upstream/skills/interview-me/SKILL.md +225 -0
  291. package/.versions/0.0.4/vendor/agent-skills-upstream/skills/observability-and-instrumentation/SKILL.md +203 -0
  292. package/.versions/0.0.4/vendor/agent-skills-upstream/skills/performance-optimization/SKILL.md +350 -0
  293. package/.versions/0.0.4/vendor/agent-skills-upstream/skills/planning-and-task-breakdown/SKILL.md +234 -0
  294. package/.versions/0.0.4/vendor/agent-skills-upstream/skills/security-and-hardening/SKILL.md +467 -0
  295. package/.versions/0.0.4/vendor/agent-skills-upstream/skills/shipping-and-launch/SKILL.md +310 -0
  296. package/.versions/0.0.4/vendor/agent-skills-upstream/skills/source-driven-development/SKILL.md +194 -0
  297. package/.versions/0.0.4/vendor/agent-skills-upstream/skills/spec-driven-development/SKILL.md +206 -0
  298. package/.versions/0.0.4/vendor/agent-skills-upstream/skills/test-driven-development/SKILL.md +383 -0
  299. package/.versions/0.0.4/vendor/agent-skills-upstream/skills/using-agent-skills/SKILL.md +191 -0
  300. package/.versions/0.0.5/.claude/commands/build.md +44 -0
  301. package/.versions/0.0.5/.claude/commands/code-simplify.md +22 -0
  302. package/.versions/0.0.5/.claude/commands/design-agent.md +14 -0
  303. package/.versions/0.0.5/.claude/commands/doctor-agent-fleet.md +17 -0
  304. package/.versions/0.0.5/.claude/commands/orchestrate.md +112 -0
  305. package/.versions/0.0.5/.claude/commands/plan.md +16 -0
  306. package/.versions/0.0.5/.claude/commands/prime.md +22 -0
  307. package/.versions/0.0.5/.claude/commands/review.md +16 -0
  308. package/.versions/0.0.5/.claude/commands/set-hermes-telegram.md +15 -0
  309. package/.versions/0.0.5/.claude/commands/setup-agent-fleet.md +25 -0
  310. package/.versions/0.0.5/.claude/commands/ship.md +72 -0
  311. package/.versions/0.0.5/.claude/commands/spec.md +15 -0
  312. package/.versions/0.0.5/.claude/commands/test.md +19 -0
  313. package/.versions/0.0.5/.claude/commands/webperf.md +32 -0
  314. package/.versions/0.0.5/.claude/orchestrate-teams.yaml +24 -0
  315. package/.versions/0.0.5/.opencode/commands/af-build.md +17 -0
  316. package/.versions/0.0.5/.opencode/commands/af-code-simplify.md +16 -0
  317. package/.versions/0.0.5/.opencode/commands/af-compound.md +16 -0
  318. package/.versions/0.0.5/.opencode/commands/af-design-agent.md +15 -0
  319. package/.versions/0.0.5/.opencode/commands/af-doctor-agent-fleet.md +17 -0
  320. package/.versions/0.0.5/.opencode/commands/af-orchestrate.md +112 -0
  321. package/.versions/0.0.5/.opencode/commands/af-plan.md +16 -0
  322. package/.versions/0.0.5/.opencode/commands/af-prime.md +22 -0
  323. package/.versions/0.0.5/.opencode/commands/af-review.md +15 -0
  324. package/.versions/0.0.5/.opencode/commands/af-set-hermes-telegram.md +15 -0
  325. package/.versions/0.0.5/.opencode/commands/af-setup-agent-fleet.md +15 -0
  326. package/.versions/0.0.5/.opencode/commands/af-ship.md +16 -0
  327. package/.versions/0.0.5/.opencode/commands/af-spec.md +16 -0
  328. package/.versions/0.0.5/.opencode/commands/af-test.md +21 -0
  329. package/.versions/0.0.5/.opencode/commands/af-webperf.md +32 -0
  330. package/.versions/0.0.5/.opencode/orchestrate-teams.yaml +24 -0
  331. package/.versions/0.0.5/.pi/agents/dispatch-policy.yaml +32 -0
  332. package/.versions/0.0.5/.pi/agents/model-profiles.yaml +20 -0
  333. package/.versions/0.0.5/.pi/agents/peers.yaml +146 -0
  334. package/.versions/0.0.5/.pi/agents/teams.yaml +39 -0
  335. package/.versions/0.0.5/.pi/damage-control-rules.yaml +297 -0
  336. package/.versions/0.0.5/.pi/extensions/agent-fleet-update-check/README.md +58 -0
  337. package/.versions/0.0.5/.pi/extensions/agent-fleet-update-check/index.ts +161 -0
  338. package/.versions/0.0.5/.pi/extensions/agent-fleet-update-check/package.json +6 -0
  339. package/.versions/0.0.5/.pi/extensions/btw/README.md +118 -0
  340. package/.versions/0.0.5/.pi/extensions/btw/index.ts +917 -0
  341. package/.versions/0.0.5/.pi/extensions/btw/package.json +6 -0
  342. package/.versions/0.0.5/.pi/extensions/btw/state.js +179 -0
  343. package/.versions/0.0.5/.pi/extensions/chrome-devtools-mcp/README.md +58 -0
  344. package/.versions/0.0.5/.pi/extensions/chrome-devtools-mcp/index.ts +92 -0
  345. package/.versions/0.0.5/.pi/extensions/chrome-devtools-mcp/package.json +6 -0
  346. package/.versions/0.0.5/.pi/extensions/compact-and-continue/README.md +42 -0
  347. package/.versions/0.0.5/.pi/extensions/compact-and-continue/index.ts +120 -0
  348. package/.versions/0.0.5/.pi/extensions/compact-and-continue/package.json +6 -0
  349. package/.versions/0.0.5/.pi/extensions/mcp-bridge/README.md +46 -0
  350. package/.versions/0.0.5/.pi/extensions/mcp-bridge/index.ts +206 -0
  351. package/.versions/0.0.5/.pi/extensions/mcp-bridge/package.json +6 -0
  352. package/.versions/0.0.5/.pi/extensions/package-lock.json +1143 -0
  353. package/.versions/0.0.5/.pi/extensions/package.json +9 -0
  354. package/.versions/0.0.5/.pi/extensions/pi-voice-stt/README.md +201 -0
  355. package/.versions/0.0.5/.pi/extensions/pi-voice-stt/config.ts +198 -0
  356. package/.versions/0.0.5/.pi/extensions/pi-voice-stt/examples/stt.json +35 -0
  357. package/.versions/0.0.5/.pi/extensions/pi-voice-stt/index.ts +248 -0
  358. package/.versions/0.0.5/.pi/extensions/pi-voice-stt/package.json +6 -0
  359. package/.versions/0.0.5/.pi/extensions/pi-voice-stt/providers.ts +214 -0
  360. package/.versions/0.0.5/.pi/extensions/pi-voice-stt/recorder.ts +158 -0
  361. package/.versions/0.0.5/.pi/harnesses/agent-hub/README.md +798 -0
  362. package/.versions/0.0.5/.pi/harnesses/agent-hub/access-approval.ts +135 -0
  363. package/.versions/0.0.5/.pi/harnesses/agent-hub/artifacts.js +92 -0
  364. package/.versions/0.0.5/.pi/harnesses/agent-hub/backend-policy.js +153 -0
  365. package/.versions/0.0.5/.pi/harnesses/agent-hub/delegate.ts +386 -0
  366. package/.versions/0.0.5/.pi/harnesses/agent-hub/drift-watchdog.js +165 -0
  367. package/.versions/0.0.5/.pi/harnesses/agent-hub/evidence-rules.js +96 -0
  368. package/.versions/0.0.5/.pi/harnesses/agent-hub/footer.ts +29 -0
  369. package/.versions/0.0.5/.pi/harnesses/agent-hub/helpers.ts +214 -0
  370. package/.versions/0.0.5/.pi/harnesses/agent-hub/index.ts +8045 -0
  371. package/.versions/0.0.5/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
  372. package/.versions/0.0.5/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
  373. package/.versions/0.0.5/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
  374. package/.versions/0.0.5/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
  375. package/.versions/0.0.5/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
  376. package/.versions/0.0.5/.pi/harnesses/agent-hub/monitor-session-bridge.ts +11 -0
  377. package/.versions/0.0.5/.pi/harnesses/agent-hub/package.json +7 -0
  378. package/.versions/0.0.5/.pi/harnesses/agent-hub/research-retention.js +34 -0
  379. package/.versions/0.0.5/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
  380. package/.versions/0.0.5/.pi/harnesses/agent-hub/return-contract.js +215 -0
  381. package/.versions/0.0.5/.pi/harnesses/agent-hub/run-budget.js +155 -0
  382. package/.versions/0.0.5/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
  383. package/.versions/0.0.5/.pi/harnesses/agent-hub/scope-gate.js +103 -0
  384. package/.versions/0.0.5/.pi/harnesses/agent-hub/spawn.ts +246 -0
  385. package/.versions/0.0.5/.pi/harnesses/agent-hub/version.ts +18 -0
  386. package/.versions/0.0.5/.pi/harnesses/ask-user-remote/README.md +19 -0
  387. package/.versions/0.0.5/.pi/harnesses/ask-user-remote/index.ts +321 -0
  388. package/.versions/0.0.5/.pi/harnesses/ask-user-remote/race-core.js +106 -0
  389. package/.versions/0.0.5/.pi/harnesses/coms/README.md +92 -0
  390. package/.versions/0.0.5/.pi/harnesses/coms/index.ts +1745 -0
  391. package/.versions/0.0.5/.pi/harnesses/coms/package.json +7 -0
  392. package/.versions/0.0.5/.pi/harnesses/coms/version.ts +18 -0
  393. package/.versions/0.0.5/.pi/harnesses/damage-control-continue/README.md +117 -0
  394. package/.versions/0.0.5/.pi/harnesses/damage-control-continue/index.ts +536 -0
  395. package/.versions/0.0.5/.pi/harnesses/damage-control-continue/package.json +7 -0
  396. package/.versions/0.0.5/.pi/harnesses/damage-control-continue/version.ts +18 -0
  397. package/.versions/0.0.5/.pi/harnesses/lib/damage-control-shared.ts +197 -0
  398. package/.versions/0.0.5/.pi/harnesses/lib/herdr-client.ts +458 -0
  399. package/.versions/0.0.5/.pi/harnesses/lib/herdr-presence.ts +288 -0
  400. package/.versions/0.0.5/.pi/harnesses/lib/hermes-monitor-herdr.ts +28 -0
  401. package/.versions/0.0.5/.pi/harnesses/lib/hermes-monitor-model.ts +9 -0
  402. package/.versions/0.0.5/.pi/harnesses/lib/hermes-monitor-registry.ts +6 -0
  403. package/.versions/0.0.5/.pi/harnesses/lib/hermes-monitor-socket.ts +118 -0
  404. package/.versions/0.0.5/.pi/harnesses/lib/hermes-monitor-store.ts +31 -0
  405. package/.versions/0.0.5/.pi/harnesses/package-lock.json +35 -0
  406. package/.versions/0.0.5/.pi/harnesses/package.json +9 -0
  407. package/.versions/0.0.5/.pi/prompts/build.md +24 -0
  408. package/.versions/0.0.5/.pi/prompts/code-simplify.md +22 -0
  409. package/.versions/0.0.5/.pi/prompts/doctor-agent-fleet.md +15 -0
  410. package/.versions/0.0.5/.pi/prompts/plan.md +16 -0
  411. package/.versions/0.0.5/.pi/prompts/review.md +16 -0
  412. package/.versions/0.0.5/.pi/prompts/set-hermes-telegram.md +15 -0
  413. package/.versions/0.0.5/.pi/prompts/setup-agent-fleet.md +27 -0
  414. package/.versions/0.0.5/.pi/prompts/ship.md +17 -0
  415. package/.versions/0.0.5/.pi/prompts/spec.md +15 -0
  416. package/.versions/0.0.5/.pi/prompts/test.md +19 -0
  417. package/.versions/0.0.5/.pi/skills/bowser/SKILL.md +145 -0
  418. package/.versions/0.0.5/.version +1 -0
  419. package/.versions/0.0.5/agents/architect.md +23 -0
  420. package/.versions/0.0.5/agents/bowser.md +26 -0
  421. package/.versions/0.0.5/agents/builder.md +53 -0
  422. package/.versions/0.0.5/agents/code-reviewer.md +205 -0
  423. package/.versions/0.0.5/agents/deep-researcher.md +31 -0
  424. package/.versions/0.0.5/agents/documenter.md +18 -0
  425. package/.versions/0.0.5/agents/orchestrator.md +54 -0
  426. package/.versions/0.0.5/agents/plan-reviewer.md +60 -0
  427. package/.versions/0.0.5/agents/planner.md +69 -0
  428. package/.versions/0.0.5/agents/releaser.md +24 -0
  429. package/.versions/0.0.5/agents/researcher.md +28 -0
  430. package/.versions/0.0.5/agents/security-auditor.md +166 -0
  431. package/.versions/0.0.5/agents/test-engineer.md +151 -0
  432. package/.versions/0.0.5/agents/web-debugger.md +42 -0
  433. package/.versions/0.0.5/agents/web-performance-auditor.md +192 -0
  434. package/.versions/0.0.5/codex/CONDUCTOR.md +148 -0
  435. package/.versions/0.0.5/docs/ARCHITECTURE.md +210 -0
  436. package/.versions/0.0.5/docs/agent-fleet-setup.md +366 -0
  437. package/.versions/0.0.5/docs/claude-code-coms-bridge.md +103 -0
  438. package/.versions/0.0.5/docs/codex-remote-conductor.md +170 -0
  439. package/.versions/0.0.5/docs/coms-hermes-bridge.md +179 -0
  440. package/.versions/0.0.5/docs/getting-started.md +183 -0
  441. package/.versions/0.0.5/docs/npm-install.md +337 -0
  442. package/.versions/0.0.5/docs/opencode-setup.md +249 -0
  443. package/.versions/0.0.5/docs/pi-extensions.md +293 -0
  444. package/.versions/0.0.5/docs/pi-setup.md +472 -0
  445. package/.versions/0.0.5/docs/skill-anatomy.md +150 -0
  446. package/.versions/0.0.5/hermes/README.md +231 -0
  447. package/.versions/0.0.5/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
  448. package/.versions/0.0.5/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
  449. package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-cap.test.py +15 -0
  450. package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-discovery.test.py +19 -0
  451. package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-envelope.test.py +13 -0
  452. package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-forged-owner.test.py +11 -0
  453. package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-lease-list.test.py +9 -0
  454. package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-multihub.test.py +17 -0
  455. package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-output.test.py +34 -0
  456. package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +151 -0
  457. package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter.test.py +39 -0
  458. package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
  459. package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/plugin-api-validation.test.py +12 -0
  460. package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
  461. package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/review-live-wiring.red.test.py +22 -0
  462. package/.versions/0.0.5/hermes/skills/hub-conductor/SKILL.md +84 -0
  463. package/.versions/0.0.5/hermes/skills/hub-liaison/SKILL.md +84 -0
  464. package/.versions/0.0.5/hooks/SIMPLIFY-IGNORE.md +90 -0
  465. package/.versions/0.0.5/hooks/coms-stop-hook.mjs +73 -0
  466. package/.versions/0.0.5/hooks/hooks.json +14 -0
  467. package/.versions/0.0.5/hooks/session-start.sh +74 -0
  468. package/.versions/0.0.5/hooks/simplify-ignore.sh +302 -0
  469. package/.versions/0.0.5/justfile +245 -0
  470. package/.versions/0.0.5/references/accessibility-checklist.md +160 -0
  471. package/.versions/0.0.5/references/definition-of-done.md +67 -0
  472. package/.versions/0.0.5/references/fleet-coordination-patterns.md +151 -0
  473. package/.versions/0.0.5/references/observability-checklist.md +91 -0
  474. package/.versions/0.0.5/references/orchestration-patterns.md +370 -0
  475. package/.versions/0.0.5/references/performance-checklist.md +153 -0
  476. package/.versions/0.0.5/references/prompting-patterns.md +380 -0
  477. package/.versions/0.0.5/references/security-checklist.md +179 -0
  478. package/.versions/0.0.5/references/testing-patterns.md +236 -0
  479. package/.versions/0.0.5/scripts/codex-conductor.ts +41 -0
  480. package/.versions/0.0.5/scripts/codex-remote-control.ts +167 -0
  481. package/.versions/0.0.5/scripts/coms-claude-bridge.ts +286 -0
  482. package/.versions/0.0.5/scripts/coms-cli.ts +484 -0
  483. package/.versions/0.0.5/scripts/coms-hermes-bridge.ts +413 -0
  484. package/.versions/0.0.5/scripts/fleet.ts +141 -0
  485. package/.versions/0.0.5/scripts/hermes-monitor-capability-runner.ts +25 -0
  486. package/.versions/0.0.5/scripts/hermes-monitor-scenario.ts +7 -0
  487. package/.versions/0.0.5/scripts/lib/claude-bridge-core.ts +100 -0
  488. package/.versions/0.0.5/scripts/lib/codex-conductor.ts +88 -0
  489. package/.versions/0.0.5/scripts/lib/codex-remote-control.ts +480 -0
  490. package/.versions/0.0.5/scripts/lib/coms-envelope.ts +539 -0
  491. package/.versions/0.0.5/scripts/lib/fake-herdr-server.ts +88 -0
  492. package/.versions/0.0.5/scripts/lib/fleet-command.ts +109 -0
  493. package/.versions/0.0.5/scripts/lib/herdr-layout.ts +263 -0
  494. package/.versions/0.0.5/scripts/lib/hermes-bridge-core.ts +241 -0
  495. package/.versions/0.0.5/scripts/lib/hermes-monitor-herdr.ts +2 -0
  496. package/.versions/0.0.5/scripts/lib/hermes-monitor-model.ts +3 -0
  497. package/.versions/0.0.5/scripts/lib/hermes-monitor-registry.ts +2 -0
  498. package/.versions/0.0.5/scripts/lib/hermes-monitor-socket.ts +2 -0
  499. package/.versions/0.0.5/scripts/lib/hermes-monitor-store.ts +2 -0
  500. package/.versions/0.0.5/scripts/lib/persona-banner.ts +62 -0
  501. package/.versions/0.0.5/scripts/lib/spawn-stagger.ts +101 -0
  502. package/.versions/0.0.5/scripts/lib/team-project.ts +191 -0
  503. package/.versions/0.0.5/scripts/lib/team-snapshot.ts +147 -0
  504. package/.versions/0.0.5/scripts/peer-banner.ts +40 -0
  505. package/.versions/0.0.5/scripts/team-snapshot.ts +237 -0
  506. package/.versions/0.0.5/scripts/team-up.ts +351 -0
  507. package/.versions/0.0.5/skills/_internal/grilling.md +11 -0
  508. package/.versions/0.0.5/skills/browser-testing-with-devtools/SKILL.md +352 -0
  509. package/.versions/0.0.5/skills/code-review-and-quality/SKILL.md +381 -0
  510. package/.versions/0.0.5/skills/compound-learning/SKILL.md +137 -0
  511. package/.versions/0.0.5/skills/context-engineering/SKILL.md +291 -0
  512. package/.versions/0.0.5/skills/deprecation-and-migration/SKILL.md +206 -0
  513. package/.versions/0.0.5/skills/designing-agents/SKILL.md +394 -0
  514. package/.versions/0.0.5/skills/designing-agents/pi-harness-authoring.md +222 -0
  515. package/.versions/0.0.5/skills/frontend-ui-engineering/SKILL.md +328 -0
  516. package/.versions/0.0.5/skills/git-workflow-and-versioning/SKILL.md +316 -0
  517. package/.versions/0.0.5/skills/guided-workspace-setup/SKILL.md +542 -0
  518. package/.versions/0.0.5/skills/guided-workspace-setup/companion-manifest.json +35 -0
  519. package/.versions/0.0.5/skills/idea-refine/SKILL.md +182 -0
  520. package/.versions/0.0.5/skills/idea-refine/examples.md +238 -0
  521. package/.versions/0.0.5/skills/idea-refine/frameworks.md +99 -0
  522. package/.versions/0.0.5/skills/idea-refine/refinement-criteria.md +113 -0
  523. package/.versions/0.0.5/skills/idea-refine/scripts/idea-refine.sh +15 -0
  524. package/.versions/0.0.5/skills/incremental-implementation/SKILL.md +287 -0
  525. package/.versions/0.0.5/skills/interview-me/SKILL.md +226 -0
  526. package/.versions/0.0.5/skills/orchestration-verification/SKILL.md +181 -0
  527. package/.versions/0.0.5/skills/peer-coms/SKILL.md +90 -0
  528. package/.versions/0.0.5/skills/performance-optimization/SKILL.md +350 -0
  529. package/.versions/0.0.5/skills/planning-and-task-breakdown/SKILL.md +236 -0
  530. package/.versions/0.0.5/skills/security-and-hardening/SKILL.md +461 -0
  531. package/.versions/0.0.5/skills/spec-driven-development/SKILL.md +245 -0
  532. package/.versions/0.0.5/skills/using-agent-skills/SKILL.md +199 -0
  533. package/.versions/0.0.5/systemd/user/agent-fleet-codex-remote-control.service.in +23 -0
  534. package/.versions/0.0.5/vendor/agent-skills-upstream/LICENSE +21 -0
  535. package/.versions/0.0.5/vendor/agent-skills-upstream/README.md +11 -0
  536. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/api-and-interface-design/SKILL.md +294 -0
  537. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/browser-testing-with-devtools/SKILL.md +317 -0
  538. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/ci-cd-and-automation/SKILL.md +390 -0
  539. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/code-review-and-quality/SKILL.md +396 -0
  540. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/code-simplification/SKILL.md +331 -0
  541. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/context-engineering/SKILL.md +289 -0
  542. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/debugging-and-error-recovery/SKILL.md +300 -0
  543. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/deprecation-and-migration/SKILL.md +247 -0
  544. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/documentation-and-adrs/SKILL.md +278 -0
  545. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/doubt-driven-development/SKILL.md +243 -0
  546. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/frontend-ui-engineering/SKILL.md +328 -0
  547. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/git-workflow-and-versioning/SKILL.md +355 -0
  548. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/idea-refine/SKILL.md +178 -0
  549. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/idea-refine/examples.md +238 -0
  550. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/idea-refine/frameworks.md +99 -0
  551. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/idea-refine/refinement-criteria.md +113 -0
  552. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/idea-refine/scripts/idea-refine.sh +15 -0
  553. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/incremental-implementation/SKILL.md +249 -0
  554. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/interview-me/SKILL.md +225 -0
  555. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/observability-and-instrumentation/SKILL.md +203 -0
  556. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/performance-optimization/SKILL.md +350 -0
  557. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/planning-and-task-breakdown/SKILL.md +234 -0
  558. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/security-and-hardening/SKILL.md +467 -0
  559. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/shipping-and-launch/SKILL.md +310 -0
  560. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/source-driven-development/SKILL.md +194 -0
  561. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/spec-driven-development/SKILL.md +206 -0
  562. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/test-driven-development/SKILL.md +383 -0
  563. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/using-agent-skills/SKILL.md +191 -0
  564. package/CHANGELOG.md +62 -0
  565. package/README.md +17 -16
  566. package/agents/builder.md +1 -1
  567. package/agents/code-reviewer.md +1 -1
  568. package/agents/deep-researcher.md +3 -3
  569. package/agents/orchestrator.md +20 -11
  570. package/agents/plan-reviewer.md +3 -3
  571. package/agents/test-engineer.md +11 -4
  572. package/bin/cli.js +83 -1
  573. package/bin/lib/set-hermes-telegram.js +323 -0
  574. package/bin/lib/validate-overrides.js +19 -0
  575. package/bin/sync-harness-versions.js +94 -0
  576. package/docs/ARCHITECTURE.md +49 -4
  577. package/docs/agent-fleet-setup.md +11 -1
  578. package/docs/claude-code-coms-bridge.md +4 -4
  579. package/docs/codex-remote-conductor.md +12 -12
  580. package/docs/coms-hermes-bridge.md +62 -4
  581. package/docs/getting-started.md +4 -4
  582. package/docs/opencode-setup.md +1 -0
  583. package/docs/pi-extensions.md +73 -33
  584. package/docs/pi-setup.md +23 -8
  585. package/hermes/README.md +191 -8
  586. package/justfile +143 -158
  587. package/package.json +13 -5
  588. package/references/fleet-coordination-patterns.md +1 -1
  589. package/scripts/coms-hermes-bridge.ts +18 -8
  590. package/scripts/fleet.ts +141 -0
  591. package/scripts/lib/fake-herdr-server.ts +88 -0
  592. package/scripts/lib/fleet-command.ts +109 -0
  593. package/scripts/lib/hermes-bridge-core.ts +5 -2
  594. package/scripts/lib/hermes-monitor-herdr.ts +2 -0
  595. package/scripts/lib/hermes-monitor-model.ts +3 -0
  596. package/scripts/lib/hermes-monitor-registry.ts +2 -0
  597. package/scripts/lib/hermes-monitor-socket.ts +2 -0
  598. package/scripts/lib/hermes-monitor-store.ts +2 -0
  599. package/scripts/lib/team-project.ts +10 -3
  600. package/scripts/team-snapshot.ts +4 -5
  601. package/scripts/team-up.ts +24 -6
  602. package/skills/designing-agents/SKILL.md +2 -2
  603. package/skills/designing-agents/pi-harness-authoring.md +26 -13
  604. package/skills/guided-workspace-setup/SKILL.md +22 -12
  605. package/skills/guided-workspace-setup/companion-manifest.json +3 -1
  606. package/skills/peer-coms/SKILL.md +1 -1
  607. package/.pi/harnesses/damage-control/README.md +0 -65
  608. package/.pi/harnesses/damage-control/index.ts +0 -250
@@ -0,0 +1,191 @@
1
+ ---
2
+ name: using-agent-skills
3
+ description: Discovers and invokes agent skills. Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.
4
+ ---
5
+
6
+ # Using Agent Skills
7
+
8
+ ## Overview
9
+
10
+ Agent Skills is a collection of engineering workflow skills organized by development phase. Each skill encodes a specific process that senior engineers follow. This meta-skill helps you discover and apply the right skill for your current task.
11
+
12
+ ## Skill Discovery
13
+
14
+ When a task arrives, identify the development phase and apply the corresponding skill:
15
+
16
+ ```
17
+ Task arrives
18
+ │
19
+ ├── Don't know what you want yet? ──────→ interview-me
20
+ ├── Have a rough concept, need variants? → idea-refine
21
+ ├── New project/feature/change? ──→ spec-driven-development
22
+ ├── Have a spec, need tasks? ──────→ planning-and-task-breakdown
23
+ ├── Implementing code? ────────────→ incremental-implementation
24
+ │ ├── UI work? ─────────────────→ frontend-ui-engineering
25
+ │ ├── API work? ────────────────→ api-and-interface-design
26
+ │ ├── Need better context? ─────→ context-engineering
27
+ │ ├── Need doc-verified code? ───→ source-driven-development
28
+ │ └── Stakes high / unfamiliar code? ──→ doubt-driven-development
29
+ ├── Writing/running tests? ────────→ test-driven-development
30
+ │ └── Browser-based? ───────────→ browser-testing-with-devtools
31
+ ├── Something broke? ──────────────→ debugging-and-error-recovery
32
+ ├── Reviewing code? ───────────────→ code-review-and-quality
33
+ │ ├── Too complex? ─────────────→ code-simplification
34
+ │ ├── Security concerns? ───────→ security-and-hardening
35
+ │ └── Performance concerns? ────→ performance-optimization
36
+ ├── Committing/branching? ─────────→ git-workflow-and-versioning
37
+ ├── CI/CD pipeline work? ──────────→ ci-cd-and-automation
38
+ ├── Deprecating/migrating? ────────→ deprecation-and-migration
39
+ ├── Writing docs/ADRs? ───────────→ documentation-and-adrs
40
+ ├── Adding logs/metrics/alerts? ───→ observability-and-instrumentation
41
+ └── Deploying/launching? ─────────→ shipping-and-launch
42
+ ```
43
+
44
+ ## Core Operating Behaviors
45
+
46
+ These behaviors apply at all times, across all skills. They are non-negotiable.
47
+
48
+ ### 1. Surface Assumptions
49
+
50
+ Before implementing anything non-trivial, explicitly state your assumptions:
51
+
52
+ ```
53
+ ASSUMPTIONS I'M MAKING:
54
+ 1. [assumption about requirements]
55
+ 2. [assumption about architecture]
56
+ 3. [assumption about scope]
57
+ → Correct me now or I'll proceed with these.
58
+ ```
59
+
60
+ Don't silently fill in ambiguous requirements. The most common failure mode is making wrong assumptions and running with them unchecked. Surface uncertainty early — it's cheaper than rework.
61
+
62
+ ### 2. Manage Confusion Actively
63
+
64
+ When you encounter inconsistencies, conflicting requirements, or unclear specifications:
65
+
66
+ 1. **STOP.** Do not proceed with a guess.
67
+ 2. Name the specific confusion.
68
+ 3. Present the tradeoff or ask the clarifying question.
69
+ 4. Wait for resolution before continuing.
70
+
71
+ **Bad:** Silently picking one interpretation and hoping it's right.
72
+ **Good:** "I see X in the spec but Y in the existing code. Which takes precedence?"
73
+
74
+ ### 3. Push Back When Warranted
75
+
76
+ You are not a yes-machine. When an approach has clear problems:
77
+
78
+ - Point out the issue directly
79
+ - Explain the concrete downside (quantify when possible — "this adds ~200ms latency" not "this might be slower")
80
+ - Propose an alternative
81
+ - Accept the human's decision if they override with full information
82
+
83
+ Sycophancy is a failure mode. "Of course!" followed by implementing a bad idea helps no one. Honest technical disagreement is more valuable than false agreement.
84
+
85
+ ### 4. Enforce Simplicity
86
+
87
+ Your natural tendency is to overcomplicate. Actively resist it.
88
+
89
+ Before finishing any implementation, ask:
90
+ - Can this be done in fewer lines?
91
+ - Are these abstractions earning their complexity?
92
+ - Would a staff engineer look at this and say "why didn't you just..."?
93
+
94
+ If you build 1000 lines and 100 would suffice, you have failed. Prefer the boring, obvious solution. Cleverness is expensive.
95
+
96
+ ### 5. Maintain Scope Discipline
97
+
98
+ Touch only what you're asked to touch.
99
+
100
+ Do NOT:
101
+ - Remove comments you don't understand
102
+ - "Clean up" code orthogonal to the task
103
+ - Refactor adjacent systems as a side effect
104
+ - Delete code that seems unused without explicit approval
105
+ - Add features not in the spec because they "seem useful"
106
+
107
+ Your job is surgical precision, not unsolicited renovation.
108
+
109
+ ### 6. Verify, Don't Assume
110
+
111
+ Every skill includes a verification step. A task is not complete until verification passes. "Seems right" is never sufficient — there must be evidence (passing tests, build output, runtime data).
112
+
113
+ Per-skill verification is the local check. The project-wide bar that applies to *every* change, regardless of which skill is active, is the Definition of Done: tests pass, no regressions, behavior verified at runtime, docs updated. See `references/definition-of-done.md`. It complements each task's acceptance criteria rather than replacing them.
114
+
115
+ ## Failure Modes to Avoid
116
+
117
+ These are the subtle errors that look like productivity but create problems:
118
+
119
+ 1. Making wrong assumptions without checking
120
+ 2. Not managing your own confusion — plowing ahead when lost
121
+ 3. Not surfacing inconsistencies you notice
122
+ 4. Not presenting tradeoffs on non-obvious decisions
123
+ 5. Being sycophantic ("Of course!") to approaches with clear problems
124
+ 6. Overcomplicating code and APIs
125
+ 7. Modifying code or comments orthogonal to the task
126
+ 8. Removing things you don't fully understand
127
+ 9. Building without a spec because "it's obvious"
128
+ 10. Skipping verification because "it looks right"
129
+
130
+ ## Skill Rules
131
+
132
+ 1. **Check for an applicable skill before starting work.** Skills encode processes that prevent common mistakes.
133
+
134
+ 2. **Skills are workflows, not suggestions.** Follow the steps in order. Don't skip verification steps.
135
+
136
+ 3. **Multiple skills can apply.** A feature implementation might involve `idea-refine` → `spec-driven-development` → `planning-and-task-breakdown` → `incremental-implementation` → `test-driven-development` → `code-review-and-quality` → `code-simplification` → `shipping-and-launch` in sequence.
137
+
138
+ 4. **When in doubt, start with a spec.** If the task is non-trivial and there's no spec, begin with `spec-driven-development`.
139
+
140
+ ## Lifecycle Sequence
141
+
142
+ For a complete feature, the typical skill sequence is:
143
+
144
+ ```
145
+ 1. interview-me → Extract what the user actually wants
146
+ 2. idea-refine → Refine vague ideas
147
+ 3. spec-driven-development → Define what we're building
148
+ 4. planning-and-task-breakdown → Break into verifiable chunks
149
+ 5. context-engineering → Load the right context
150
+ 6. source-driven-development → Verify against official docs
151
+ 7. incremental-implementation → Build slice by slice
152
+ 8. observability-and-instrumentation → Instrument as you build (runs parallel with 7-9, not after)
153
+ 9. doubt-driven-development → Cross-examine non-trivial decisions in-flight
154
+ 10. test-driven-development → Prove each slice works
155
+ 11. code-review-and-quality → Review before merge
156
+ 12. code-simplification → Reduce unnecessary complexity while preserving behavior
157
+ 13. git-workflow-and-versioning → Clean commit history
158
+ 14. documentation-and-adrs → Document decisions
159
+ 15. deprecation-and-migration → Retire old systems and move users safely when needed
160
+ 16. shipping-and-launch → Deploy safely
161
+ ```
162
+
163
+ Not every task needs every skill. A bug fix might only need: `debugging-and-error-recovery` → `test-driven-development` → `code-review-and-quality`.
164
+
165
+ ## Quick Reference
166
+
167
+ | Phase | Skill | One-Line Summary |
168
+ |-------|-------|-----------------|
169
+ | Define | interview-me | Surface what the user actually wants before any plan, spec, or code exists |
170
+ | Define | idea-refine | Refine ideas through structured divergent and convergent thinking |
171
+ | Define | spec-driven-development | Requirements and acceptance criteria before code |
172
+ | Plan | planning-and-task-breakdown | Decompose into small, verifiable tasks |
173
+ | Build | incremental-implementation | Thin vertical slices, test each before expanding |
174
+ | Build | source-driven-development | Verify against official docs before implementing |
175
+ | Build | doubt-driven-development | Adversarial fresh-context review of every non-trivial decision |
176
+ | Build | context-engineering | Right context at the right time |
177
+ | Build | frontend-ui-engineering | Production-quality UI with accessibility |
178
+ | Build | api-and-interface-design | Stable interfaces with clear contracts |
179
+ | Verify | test-driven-development | Failing test first, then make it pass |
180
+ | Verify | browser-testing-with-devtools | Chrome DevTools MCP for runtime verification |
181
+ | Verify | debugging-and-error-recovery | Reproduce → localize → fix → guard |
182
+ | Review | code-review-and-quality | Five-axis review with quality gates |
183
+ | Review | code-simplification | Preserve behavior while reducing unnecessary complexity |
184
+ | Review | security-and-hardening | OWASP prevention, input validation, least privilege |
185
+ | Review | performance-optimization | Measure first, optimize only what matters |
186
+ | Ship | git-workflow-and-versioning | Atomic commits, clean history |
187
+ | Ship | ci-cd-and-automation | Automated quality gates on every change |
188
+ | Ship | deprecation-and-migration | Remove old systems and migrate users safely |
189
+ | Ship | documentation-and-adrs | Document the why, not just the what |
190
+ | Ship | observability-and-instrumentation | Structured logs, RED metrics, traces, symptom-based alerts |
191
+ | Ship | shipping-and-launch | Pre-launch checklist, monitoring, rollback plan |
package/CHANGELOG.md CHANGED
@@ -1,5 +1,67 @@
1
1
  # Agent Fleet changelog
2
2
 
3
+ ## 0.0.5
4
+
5
+ ### Patch Changes
6
+
7
+ - fb50bef: Add `/set-hermes-telegram` (`/af-set-hermes-telegram` on OpenCode) and the deterministic `agent-fleet set-hermes-telegram` CLI. It installs/status-checks the profile-scoped `hub-liaison` skill with drift protection, atomic backup/replacement, tool and gateway verification, and explicit restart control, then starts or stops the Telegram `ask_user` bridge in a dedicated pane in the current Herdr workspace. Bridge sends are pinned to the verified Hermes profile instead of relying on the sticky default.
8
+ - fb50bef: Add `just fleet` as the unified Pi runtime entry point. Fleet Core now guarantees Damage Control Continue, local/remote `ask_user`, Speech-to-Text, Compact & Continue, BTW, and update checks across the default session, Hub, standalone coms peers, and Herdr Pi peers. Add composable `peer`, `hub`, `team`, conductor, lifecycle, browser, and extension-discovery modes behind a single public Just recipe; the former Hub, team, coms, and conductor recipe aliases are removed.
9
+ - aa5630c: Fix symlinked Agent Hub launches after package-only updates. The hub monitor runtime now ships atomically under the shared harness library, and `ask-user-remote` canonicalizes its own package path before loading the bundled `pi-ask-user` dependency.
10
+ - d0e1914: Hoist MCP extension runtime dependencies into the published package so symlinked `chrome-devtools-mcp` peers can resolve the SDK from their real npm package path. Add package-surface regression coverage and strengthen setup/runtime verification guidance.
11
+
12
+ ## 0.0.4
13
+
14
+ ### Patch Changes
15
+
16
+ - ccefce7: Rework the guided-workspace-setup flow around the `pi-ask-user` widget: an Express question can resolve the whole install menu in one prompt, each group opens as a single-select quick screen with drill-in chunks only behind Customise, removal moves to an explicit "Remove some…" selection (the widget has no pre-checking), and every screen obeys a hard budget (≤ 9 options, ≤ 8 context lines) so nothing overflows the terminal. Doctor findings, overrides, method, and the confirm+installer-cleanup question all become native widget prompts; the old table format survives only as the no-widget fallback. The claude-code/opencode setup commands and doctor prompts mirror the same contract.
17
+ - b86362d: Fix fleet panes spawning with every pi provider "unconfigured": simultaneous pi boots race on the `~/.pi/agent/auth.json` file lock when the stored OAuth token is stale (the refresher holds the lock across its network call, and losers silently boot with an empty credential store). `team-up`, `hub-team`, and `team-resume` now pre-warm: when a stale OAuth credential is detected, one pi pane starts immediately to refresh the token and the other pi panes are staggered via `AGENT_FLEET_SPAWN_DELAY` (honored by the `_peer`/`_peer-plus` recipes). Fresh tokens spawn with zero delay; `claude-code` runner panes never wait.
18
+ - ac770c6: Add an experimental Linux Codex remote-control conductor: scoped and serialized `coms` delegation, a fail-closed conductor contract and wrapper rendered into an external user-state runtime workspace, typed Hermes/Codex team layouts, user-systemd lifecycle helpers, setup/package integration, and an operator runbook. This is intentionally a patch changeset to match the repository's forced-patch release policy.
19
+
20
+ **Pilot upgrade:** rerun `conductor-codex-reconfigure` before the next start so the owned configuration/unit and managed contract move to the external user-state runtime directory.
21
+
22
+ **Migration:** CLI spools now live at `~/.pi/coms/cli/projects/<project>/<name>/`. If an older name-only queue exists at `~/.pi/coms/cli/<name>/`, the CLI refuses queue operations until the operator stops that identity, inspects its pending/responses/inbound data, identifies the owning project, and moves the complete directory under the project-scoped path. Do not delete or merge ambiguous queues. The identity name `projects` is now reserved.
23
+
24
+ - 3503055: Show the root-stamped package version in persistent Pi harness footers, including agent-hub's custom footer, and keep the version deduplicated when supported harnesses are stacked.
25
+ - f44752f: Add the optional local Hermes task monitor source MVP, including an Agent Fleet-owned hub monitor boundary, Hermes backend adapter, and Desktop pane with manual installation guidance.
26
+ - 3503055: agent-hub: execution modes with enforced per-turn budgets, session recycling, and cheaper persona defaults — the fix for runaway over-orchestration (100+ dispatches / 100M+ tokens per task, mostly re-billed stale context).
27
+
28
+ - **Execution modes** `fast` / `standard` (default) / `strict` with per-user-turn budgets enforced in code: `dispatch_agent` and `spawn_research` refuse past the cap with "summarize and ask the user"; a new user message opens a fresh window. New `/hub-mode` command, `hub-mode` status chip, and mode-aware dispatcher prompt (fast: single specialist, ledger optional; standard: batched builds, one recon, one review gate; strict: full Verification Contract).
29
+ - **New overrides keys** under `## agent-hub`: `mode`, `max-dispatches-per-turn`, `max-research-per-turn`, `turn-wall-time-s`, `agent-turn-timeout-s`, `session-recycle-runs` (validated by `agent-fleet doctor`).
30
+ - **Whole-run deadline** (`turn_timeout`, exit 124, partial output preserved) for dispatched specialists, research helpers, and nested delegate children — a hung child can no longer hold its parent for hours. Complements the per-tool `recon-search-timeout-s` watchdog.
31
+ - **Session recycling + honest context measurement**: specialist context pressure now counts input + cacheRead + cacheWrite (previously cache reads were invisible, so the restart advice never fired); specialist sessions are recycled after N resumed runs or ≥60% measured context instead of resuming forever.
32
+ - **Dispatch key normalization**: `dispatch_agent(agent: "Test Engineer")` resolves to `test-engineer` instead of erroring.
33
+ - **Persona tuning**: orchestrator thinking xhigh→medium, builder/code-reviewer high→medium, plan-reviewer Sol→Terra + medium, test-engineer medium→low with scouts on Spark and the delegation pre-pass now conditional (first dispatch in an area only); orchestrator posture rewritten for batched execution (4–6 tasks per builder dispatch, narrow assertions, no researcher spawns to read return artifacts, "two reads" and deep research reserved for strict mode).
34
+
35
+ Existing behavior is restored with `mode: strict` in `.ai/agent-fleet-overrides.md`.
36
+
37
+ - 3503055: agent-hub: complexity triage, in-flight drift watchdog, dynamic teams, and per-turn cost reporting — the qualitative follow-up to the execution-modes/budgets guardrails (stop over-engineering simple asks and catch drifting specialists while they run, not after).
38
+
39
+ - **Task triage**: new `set_task_tier` dispatcher tool (`trivial`/`small`/`feature`/`project`); enforced caps drop to min(mode, tier) — a trivial ask gets 1 dispatch, not the whole standard envelope. The system prompt mandates triage-first, treats a provided plan as a spec (no re-planning/re-spec), calls out "using every persona" as a smell, and requires a four-part task template (objective, output format, files in scope, boundaries). A **duplicate-dispatch guard** refuses re-dispatching the same agent with a near-identical task within one turn (in code, `duplicate_refused`).
40
+ - **Drift watchdog** (`drift-watchdog.js` + a new `onControl`/`drift_stop` seam in `spawn.ts`): armed dispatches are observed live from the tool event stream — deterministic rules (write outside the declared `scope` globs, identical call repeated 4×, 5 consecutive failed tool calls, 200-call cap) escalate to a one-shot cheap LLM judge (single-flight, 90 s cooldown, fails open; model via `watchdog-judge-model`, default researcher persona's). A DRIFTING/STUCK verdict terminates the run as `drift_stop` (exit 125, partial output preserved) with a corrected-re-dispatch-once instruction. Dynamically enabled per dispatch (`watchdog` param) > per agent (`/watchdog <agent> on|off|clear`) > hub-wide (`/watchdog on|off|auto`, overrides key `watchdog`, default `auto`).
41
+ - **Dynamic teams**: `/agents-add`, `/agents-drop` (refuses running/last members), `/agents-save <team>` (targeted comment-preserving upsert into `.pi/agents/teams.yaml`), and a gated `team_adjust` dispatcher tool (reason required, off in fast mode, roster cap 8, human notified). The dispatcher prompt rebuilds every turn, so roster changes apply immediately.
42
+ - **`/hub-report`**: per-turn and session cost accounting — dispatches (agent/status/elapsed/billed+output tokens), research runs, session recycles, drift stops, budget/duplicate refusals. The `hub-mode` status chip now shows the declared tier.
43
+ - New overrides keys `watchdog`, `watchdog-judge-model` validated by `agent-fleet doctor`; orchestrator persona gains triage-first and plan-is-a-spec posture.
44
+
45
+ - c0701f6: Add `pi.image` gallery metadata so the pi.dev/packages listing shows the agent-hub dashboard screenshot as a preview
46
+ - 7a92825: Document the `--project` flag on every team recipe in the justfile and the README quickstart: scoping a team to its own coms pool (`just hub-team review --project af`) is what keeps teams launched from different repos out of each other's peer pool, and the bare `project=af` form is a just variable override that gets silently ignored (the team lands in the shared "default" pool and collides with other repos' peers — name suffixing like `code-reviewer2`, dispatches routed to the wrong repo's pane).
47
+ - 4037b36: README simplified into a landing page (676 → ~220 lines) — the hero screenshot and Quick Start (pi first) moved to the top, and the reference depth relocated with links instead of deleted:
48
+
49
+ - Full 29-skill tables → new `docs/skills-catalog.md` (now also listing `designing-agents` and `guided-workspace-setup`, so the count is honest).
50
+ - Full 15-persona roster, skill hooks, install matrix, and team composition → `docs/agents.md` (which previously pointed back at the README).
51
+ - Fleet hierarchy diagrams, runtime-stack diagram, and the external-dependencies ("Built on") table → `docs/ARCHITECTURE.md`.
52
+ - The end-to-end dispatch sequence diagram → the agent-hub harness README; its stale design-plan link fixed to `docs/plans/agent-hub/`.
53
+ - Origins condensed into Credits; a new Documentation index section links every guide.
54
+
55
+ - ae57f1c: agent-hub: research helpers no longer pile up after finishing, and the research/team command families are unified. Finished helpers are auto-pruned — auto-research pipe helpers (spawned for `NEEDS_RESEARCH:` pauses) disappear as soon as they finish since their findings persist as `findings/*.md` files, while manual/persona helpers keep only the most recently finished N (new `research-keep: <n>|all` key in the `## agent-hub` overrides section, default 4, LRU by finish time). Running helpers are never pruned and `rN` handles are never reused; `/agents-history` keeps its full timeline. The `agents-*` slash commands now address both target kinds the way `/zoom` already did: `/agents-kill <name|rN|all>` SIGTERMs a team specialist (its standing card stays), while on a research helper it kills **and removes** the card + session file — helpers are disposable by design — with `all` clearing every helper; `/agents-restart <name|rN>` accepts research handles (finished helpers re-run fresh); and a new `/agents-cont rN <prompt>` resumes a finished helper — `/research-cont`, `/research-rm`, and `/research-clear` remain as aliases. Retention selection lives in a new tested pure module (`research-retention.js`).
56
+ - 99759a2: Retire the hard-stop `.pi/harnesses/damage-control/` artifact and `just ext-damage-control` recipe. `damage-control-continue` is now the only supported safety harness and guards the Agent Hub dispatcher, native specialists, research helpers, and nested delegates. Protected deletions require explicit one-call approval, inherently dangerous command patterns remain non-exemptible, and missing child safety fails closed. Guided setup removes only owned, unchanged legacy hard-stop installs and preserves user-modified or unowned copies.
57
+ - 2613096: First-class symlink installs: remembered method, kept installer, symlink-safe script runs.
58
+
59
+ - `guided-workspace-setup` now reuses the `method:` recorded in `.ai/agent-fleet-setup.md` instead of re-asking copy vs symlink on every run (asked only on first install; overridable in the Step 9 summary), and a recorded `keep-installer: true` skips the installer-removal offer entirely — the summary just confirms the commands stay.
60
+ - The `justfile` runs the fleet TS scripts through a `node_ts` variable that adds `--preserve-symlinks --preserve-symlinks-main`. Without them, a symlink install (targets linked into the project-scoped `.pi/npm/node_modules/@chankov/agent-fleet` package) breaks: Node realpaths `scripts/*.ts` into `node_modules/`, where `--experimental-strip-types` is refused. Copy installs are unaffected — the fleet scripts import only relative paths and node builtins.
61
+
62
+ - 3e6b05f: Harden the ask-user-remote harness against a double-load of the stock `pi-ask-user` extension. When `npm:pi-ask-user` was also listed in pi settings `packages`, a load-order race could hard-crash the session (`Tool "ask_user" conflicts`) if the harness registered its wrapper first. The harness now runs a startup preflight over project (`.pi/settings.json`) and global (`~/.pi/agent/settings.json`) settings: if a `pi-ask-user` package entry is found, it warns and skips registering the wrapper so the stock package registers alone — the session survives regardless of load order (remote answer racing is disabled until the entry is removed). The repo's own `.pi/settings.json` no longer lists `npm:pi-ask-user`.
63
+ - 76b33a9: Scope herdr team workspace labels to the checkout so the same team can run from multiple repos/worktrees at once. Previously `just hub-team <team>` always labeled its workspace `pi-hub-<team>`, so launching the same team from a second repo/worktree failed with `herdr workspace "pi-hub-<team>" already exists`. Labels are now `<worktree-tag>-<mode>-<team>` (e.g. `wt2-hub-plan`, `end2-peers-docs`), where the worktree tag is the last dot-segment of the checkout directory's basename (`main.wt2` → `wt2`, `ringithub.end2` → `end2`, a plain `agent-fleet` checkout → `agent-fleet`). `team-up`, `hub-team`, `conductor`, and `team-snapshot`/`team-down`/`team-resume` all derive the tag the same way, so snapshot/resume still target the workspace they created. The `--project <name>` flag remains a separate axis for coms-pool scoping.
64
+
3
65
  All notable changes to `@chankov/agent-fleet` are documented here. Agent Fleet
4
66
  starts at 0.0.1; earlier `@chankov/agent-skills` releases remain available in
5
67
  git history. This file is generated from [changesets](https://github.com/changesets/changesets).
package/README.md CHANGED
@@ -39,8 +39,9 @@ pi install -l npm:@chankov/agent-fleet # project-scoped package: skills, promp
39
39
  # then, inside pi:
40
40
  # /setup-agent-fleet # guided install of harnesses, personas, extensions
41
41
  # and once set up:
42
- just hub # guarded multi-agent dispatcher
43
- just hub-team docs # hub + a whole peer team in one tiled herdr workspace
42
+ just fleet # guarded Pi + STT and core utilities
43
+ just fleet hub # guarded multi-agent dispatcher
44
+ just fleet team docs # hub + guarded peers in one tiled herdr workspace
44
45
  ```
45
46
 
46
47
  ### Claude Code / OpenCode
@@ -94,13 +95,13 @@ The optional Codex Remote-Control conductor is verified on Linux with Codex CLI
94
95
 
95
96
  ```bash
96
97
  cd /path/to/agent-fleet
97
- just conductor-codex-setup docs --project af # once per configured context
98
- just conductor-codex-pair # interactive; never capture the code
99
- just conductor-codex-start
100
- just hub-team docs --project af # hub + peers Codex can reach
98
+ just fleet conductor codex setup docs --project af # once per configured context
99
+ just fleet conductor codex pair # interactive; never capture the code
100
+ just fleet conductor codex start
101
+ just fleet team docs --project af # hub + peers Codex can reach
101
102
  ```
102
103
 
103
- In ChatGPT Android, open the paired Remote Control host and use the managed external workspace at `$HOME/.local/state/agent-fleet/codex-conductor/workspace`. Do not start a local `codex` process for the Android flow, and do not also launch `conductor-codex docs` when `hub-team docs` already owns the same peers.
104
+ In ChatGPT Android, open the paired Remote Control host and use the managed external workspace at `$HOME/.local/state/agent-fleet/codex-conductor/workspace`. Do not start a local `codex` process for the Android flow, and do not also launch `just fleet conductor codex docs` when `just fleet team docs` already owns the same peers.
104
105
 
105
106
  Lifecycle, approval flow, examples, recovery, and security boundaries: **[Codex Remote-Control conductor runbook](docs/codex-remote-conductor.md)**.
106
107
 
@@ -110,11 +111,11 @@ Versioned with [semver](https://semver.org) — [CHANGELOG.md](CHANGELOG.md) ·
110
111
 
111
112
  ## agent-hub: a thin-context dispatcher for pi
112
113
 
113
- `agent-hub` turns a single **pi** session into a **dispatcher that drives a live team of specialist subagents** — planner, builder, reviewer, test-engineer, documenter — with read-only research helpers fanning out beneath them, peer-to-peer `coms` messaging embedded, and a `damage-control` guardrail on every tool call.
114
+ `agent-hub` turns a single **pi** session into a **dispatcher that drives a live team of specialist subagents** — planner, builder, reviewer, test-engineer, documenter — with read-only research helpers fanning out beneath them, peer-to-peer `coms` messaging embedded, and a `damage-control-continue` guardrail on every tool call.
114
115
 
115
116
  What makes it different is what it **doesn't** put in front of the dispatcher LLM. Multi-agent setups usually drown the orchestrator: every subagent's output, every research dump flows back into one context window until it compacts and forgets. `agent-hub` is built the other way around:
116
117
 
117
- - **Research never enters the dispatcher context.** Specialists end their turn with `NEEDS_RESEARCH:` lines; the hub fans out read-only helpers, writes findings to disk, and resumes the specialist with file paths. The dispatcher sees a one-line notice — never the raw findings.
118
+ - **Research never enters the dispatcher context.** Specialists end their turn with `NEEDS_RESEARCH:` lines; the hub fans out read-only helpers, writes findings to disk, and resumes the specialist with file paths. The dispatcher sees a one-line notice — never the raw findings. Each local-disk research tool call has a parent-side 120-second watchdog (configurable as `recon-search-timeout-s` in `.ai/agent-fleet-overrides.md`), not a whole-agent deadline.
118
119
  - **The Verification Contract lives on disk.** A ledger of checkable acceptance assertions, built from the request *before* any builder runs, rendered as one status line (`Assertions: 2✓ 1○ 1✗ · open: A4`). A stated requirement is never silently dropped, and the contract survives compaction.
119
120
  - **Specialists run `--no-extensions`.** Tools and credentials stay scoped to the subagent that needs them instead of leaking up into the dispatcher.
120
121
 
@@ -123,17 +124,17 @@ What makes it different is what it **doesn't** put in front of the dispatcher LL
123
124
  Personas don't hardcode one frontier model — each declares a default plus a switch list on a three-tier policy (deep reasoning / workhorse / fast recon), switchable at runtime per persona (`/agent-model`) or fleet-wide (`/models <profile>`). `plan-reviewer` and `code-reviewer` can run as **Claude Code peers** for cross-model review.
124
125
 
125
126
  ```bash
126
- just hub # guarded dispatcher + research + coms + orchestrator persona
127
- just hub-solo # same, without the coms layer
127
+ just fleet hub # guarded dispatcher + research + coms + orchestrator persona
128
+ just fleet hub --solo # same, without the coms layer
128
129
 
129
130
  # fleet recipes (need a running herdr server — https://herdr.dev)
130
- just team-up full # spawn addressable peers into a tiled herdr workspace
131
- just hub-team docs # hub + a whole team in ONE workspace
132
- just team-down docs # snapshot + close cleanly
133
- just team-resume docs # rebuild the grid; pi peers continue their conversations
131
+ just fleet team full --no-hub # guarded addressable peers in a tiled workspace
132
+ just fleet team docs # hub + guarded peers in ONE workspace
133
+ just fleet down docs # snapshot + close cleanly
134
+ just fleet resume docs # rebuild the grid; pi peers continue their conversations
134
135
  ```
135
136
 
136
- Deep dive: [agent-hub harness README](.pi/harnesses/agent-hub/README.md) (the full dispatch loop, coms layer, configuration) · [fleet hierarchy](docs/ARCHITECTURE.md#fleet-hierarchy) · [pi extension catalog](docs/pi-extensions.md) · [Claude Code coms bridge](docs/claude-code-coms-bridge.md) · [Hermes bridge](docs/coms-hermes-bridge.md).
137
+ Deep dive: [agent-hub harness README](.pi/harnesses/agent-hub/README.md) (the full dispatch loop, coms layer, configuration) · [fleet hierarchy](docs/ARCHITECTURE.md#fleet-hierarchy) · [pi extension catalog](docs/pi-extensions.md) · [Claude Code coms bridge](docs/claude-code-coms-bridge.md) · [Hermes bridge](docs/coms-hermes-bridge.md) · [Hermes integration screenshots](hermes/README.md#integration-in-action).
137
138
 
138
139
  ---
139
140
 
package/agents/builder.md CHANGED
@@ -11,7 +11,7 @@ models:
11
11
  - ollama/kimi-k2.7-code:cloud
12
12
  - ollama/glm-5.2:cloud
13
13
  - ollama/nemotron-3-ultra:cloud
14
- thinking: high
14
+ thinking: medium
15
15
  delegate_depth: 1
16
16
  subagents:
17
17
  recon:
@@ -13,7 +13,7 @@ models:
13
13
  - ollama/kimi-k2.7-code:cloud
14
14
  - ollama/glm-5.2:cloud
15
15
  - ollama/minimax-m3:cloud
16
- thinking: high
16
+ thinking: medium
17
17
  delegate_depth: 1
18
18
  subagents:
19
19
  preflight:
@@ -3,13 +3,13 @@ name: deep-researcher
3
3
  description: Read-only deep reconnaissance for hard, ambiguous, or high-stakes questions — traces cross-cutting call paths, maps unfamiliar subsystems, and synthesizes findings across many files with file:line citations. Never edits or runs commands.
4
4
  tools: read,grep,find,ls
5
5
  kind: research
6
- model: openai-codex/gpt-5.6-sol
6
+ model: openai-codex/gpt-5.6-terra
7
7
  models:
8
- - openai-codex/gpt-5.6-terra
8
+ - openai-codex/gpt-5.6-sol
9
9
  - openai-codex/gpt-5.6-luna
10
10
  - ollama/nemotron-3-ultra:cloud
11
11
  - ollama/glm-5.2:cloud
12
- thinking: high
12
+ thinking: medium
13
13
  ---
14
14
 
15
15
  # Deep Researcher
@@ -8,7 +8,7 @@ models:
8
8
  - openai-codex/gpt-5.6-luna
9
9
  - ollama/minimax-m3:cloud
10
10
  - ollama/nemotron-3-ultra:cloud
11
- thinking: xhigh
11
+ thinking: medium
12
12
  ---
13
13
 
14
14
  # Verification-Contract Orchestrator
@@ -21,25 +21,34 @@ Before any non-trivial work, read `skills/orchestration-verification/SKILL.md`
21
21
 
22
22
  - **Build the assertion list first.** Before any builder runs, convert the request into the numbered, tagged acceptance assertions from `skills/orchestration-verification/SKILL.md` (`test` | `runtime-ui` | `code-grep` | `manual`, each one checkable pass condition). Pass the relevant assertions **verbatim** into every dispatch, and advance only on assertions that come back *proven with evidence* — propagation in prose is not verification.
23
23
  - **Inventory parity for "behave like" requests.** When the request is "make X behave like existing Y", commission a `deep-researcher` parity/touchpoint inventory **first** — every site where the exemplar is special-cased (flags, branches, display, validation, translations, fixtures, tests). Convert each site into an assertion that covers the *whole* set; this kills the dominant failure mode where the exemplar ships and its siblings are missed. The inventory is dispatcher-owned: downstream specialists *consume* it rather than re-deriving call sites.
24
- - **Gate every micro-slice.** Builders work **vertical micro-slices** (contract/flag → placement → visibility → payload → validation → display → cleanup), each with a **named gate** after it. No advancement while any relevant assertion is unproven — broad bundles dilute semantic intent behind mechanical bulk.
24
+ - **Batch slices; gate batches.** Builders work **vertical slices**, but dispatch them in coherent BATCHES of 4–6 related plan tasks with **one named gate per batch** — not one dispatch and one gate per micro-task (a 46-task plan is 8–10 batches, never 50+ builder runs). No advancement while a batch's assertions are unproven. Keep each assertion narrow (one subsystem, one behavior): compound "audit everything" assertions force full re-audits after every small fix. After a fix, re-verify only the assertions the fix touched.
25
25
  - **Require runtime proof for UI assertions.** A `runtime-ui` assertion (visibility, placement, "appears in the table") is closed only by an actual runtime observation via the `browser-testing-with-devtools` skill — never a static review or code reading; static-only approval is exactly how broken UI shipped before. In pi, route it by mode: **delegate a `bowser` subagent** for headless, scriptable `playwright-cli` evidence that runs as a dispatched child (survives `--no-extensions`), or **hand off to the `web-debugger` coms peer** for interactive headful Chrome — live DOM/console/network/performance via the `chrome_devtools__*` tools (those come from an extension, so they are reachable in a peer, not a `--no-extensions` subagent). Either path must save DOM/screenshot/network evidence under `.pi/agent-sessions/artifacts/evidence/` and name that existing artifact path in the structured return; a refused `update_assertion(status: "proven")` means produce real evidence, not rephrase prose.
26
26
  - **Accept only structured returns.** Specialists report assertion *status + evidence* in the structured-return schema, never a prose "approved". Demote any assertion claimed proven without named evidence to unproven and re-dispatch it; treat `assertions_unproven` and `assertions_failed` as not done.
27
27
  - **Reset on "wrong again".** When the user reports a delivered requirement is wrong again, run the requirement-regression reset: treat the stale "approved/proven" summaries for that area as unverified, rebuild the affected assertions from the **latest** correction (re-running the parity inventory if it is a "behave like" case), and only then dispatch.
28
- - **Use bounded read-only powers.** Get your own eyes on ground truth rather than relaying upward summaries blindly: read the requirement as the user states it, require each specialist's structured return to name file:line / command output / runtime observation as evidence (not prose), and call `get_assertions` to read the full ledger back — including the recorded evidence — after a compaction or before reporting done. In pi, `dispatch_agent` pre-parses assertion-carrying returns into `details.structuredReturn`, writes the raw return to `details.returnPath`, and flags evidence-less proven claims in `details.contractNotices`; use the digest first and spawn a reader for the path only when necessary. When you need to inspect the diff or code yourself, `spawn_research` a read-only helper rather than trusting a summary. You do **not** author implementation code, and you hold no file-write or bash tools; delegation stays the path to changes.
28
+ - **Use bounded read-only powers.** Get your own eyes on ground truth rather than relaying upward summaries blindly: read the requirement as the user states it, require each specialist's structured return to name file:line / command output / runtime observation as evidence (not prose), and call `get_assertions` to read the full ledger back — including the recorded evidence — after a compaction or before reporting done. In pi, `dispatch_agent` pre-parses assertion-carrying returns into `details.structuredReturn`, writes the raw return to `details.returnPath`, and flags evidence-less proven claims in `details.contractNotices`; use the digest first — NEVER spawn a research helper just to read a return artifact whose digest and path you already hold. When you need to inspect the diff or code yourself and the digest is genuinely insufficient, `spawn_research` a read-only helper rather than trusting a summary. You do **not** author implementation code, and you hold no file-write or bash tools; delegation stays the path to changes.
29
29
 
30
- ## Operating posture (correctness first)
30
+ ## Operating posture (correctness within budget)
31
31
 
32
- - **Recon before action.** When a request touches unfamiliar code, dispatch a researcher to map the terrain before dispatching a builder.
33
- - **Plan explicitly.** For anything beyond a trivial change, dispatch a planner (and a plan reviewer if the team has one) before any implementation. Relay document artifacts by path: plans, reviews, inventories, critiques, and evidence reports should be written under the real session path `.pi/agent-sessions/artifacts/<kind>/<agentKey>-run<N>.md` and passed downstream as artifact-relative `artifacts/<kind>/<agentKey>-run<N>.md` paths (while preserving planner PLAN_FILE behavior). Downstream dispatches should receive those paths through `artifacts: [...]` instead of pasted document bodies.
34
- - **Gate work through skills.** Before implementation or risky work, require skill discovery via `skills/using-agent-skills/SKILL.md`; unclear requirements go through spec/planning skills first, implementation tasks need plan/review gates, and security-sensitive work includes `security-and-hardening`. Name the selected skills in specialist tasks and ask each specialist to report which skills they followed plus verification evidence. Skills are active workflows, not passive docs.
32
+ The hub runs an execution mode (`fast` / `standard` / `strict` — see the Execution mode
33
+ section of your system prompt) with enforced per-turn budgets for dispatches, research
34
+ runs, and wall clock. The full Contract above applies in **strict** mode; in standard
35
+ mode apply it with batching and single gates; in fast mode a single specialist and its
36
+ own evidence suffice. When a budget refusal comes back, stop, summarize, and ask the
37
+ user — never retry the refused call in the same turn.
38
+
39
+ - **Triage first, then size the apparatus.** Call `set_task_tier` before your first dispatch and match the machinery to the tier: a trivial/small ask gets one specialist and its own evidence — no ledger, no plan/review pipeline, no parity inventories. Reserve the full apparatus for feature/project tiers. Classify by what the USER asked for, not by how much process the work could absorb.
40
+ - **A provided plan is a spec.** When the user hands you an existing plan or task list, do NOT re-plan, re-spec, or commission a plan review — batch the plan's tasks straight to the builder and turn the plan's own acceptance criteria into the assertions. Re-planning planned work is the signature over-engineering failure.
41
+ - **Recon before action — once.** When a request touches unfamiliar code, dispatch at most ONE researcher to map the terrain before the first builder. Skip recon entirely for familiar code or when the plan already names the files.
42
+ - **Plan explicitly — when no plan exists.** For anything beyond a trivial change that arrives WITHOUT a plan, dispatch a planner (and a plan reviewer if the team has one) before any implementation. Relay document artifacts by path: plans, reviews, inventories, critiques, and evidence reports should be written under the real session path `.pi/agent-sessions/artifacts/<kind>/<agentKey>-run<N>.md` and passed downstream as artifact-relative `artifacts/<kind>/<agentKey>-run<N>.md` paths (while preserving planner PLAN_FILE behavior). Downstream dispatches should receive those paths through `artifacts: [...]` instead of pasted document bodies.
43
+ - **Gate risky work through skills.** For implementation batches and risky work, name the relevant skills in the specialist task (spec/planning skills for unclear requirements, `security-and-hardening` for security-sensitive work) and ask the specialist to report the skills it followed plus verification evidence. Do NOT spawn a separate dispatch just to read skill files, and skip skill ceremony entirely for read-only or trivial asks — skills are active workflows for consequential changes, not a toll booth on every dispatch.
35
44
  - **Light research for simple reads.** For low-risk, read-only recon — simple counts, grep/search, docs reading, quick summaries — use `spawn_research(persona: "researcher")` (`openai-codex/gpt-5.6-luna` with low thinking for simple, low-risk read-only recon).
36
- - **Deep research for hard reconnaissance.** For ambiguous, cross-cutting, or high-stakes investigation — the parity inventory above, tracing tricky call paths, mapping unfamiliar subsystems, security-relevant reads, or weighing many files before a big change — use `spawn_research(persona: "deep-researcher")` (`openai-codex/gpt-5.6-sol` with high thinking). When evidence is thin, prefer a deep pass over guessing.
45
+ - **Deep research for hard reconnaissance — sparingly.** For ambiguous, cross-cutting, or high-stakes investigation — the parity inventory above, tracing tricky call paths, mapping unfamiliar subsystems, security-relevant reads — use `spawn_research(persona: "deep-researcher")` (`openai-codex/gpt-5.6-sol` with high thinking). It is the most expensive helper: budget 1–2 deep passes per task, reuse their written findings instead of commissioning new ones, and fall back to the light researcher for everything narrower.
37
46
  - **Escalate non-research complexity by persona.** For architecture planning, complex debugging, security audits, large refactors, or deep code review, dispatch the appropriate specialist — `dispatch_agent` takes no model argument, so routing IS persona selection.
38
47
  - **Personas carry their own model.** Both research personas bring their own model/thinking; any `model` argument is ignored when a `persona` is set. Pick the persona that fits the task — don't pass raw model strings.
39
48
  - **Use advisory dispatch scope for builders.** When dispatching a builder for a planned implementation task, derive `scope: [...]` from that task's file list/path inventory so side-changes are surfaced. Skip `scope` for exploratory, planning, or reconnaissance work where the file set is not known. Scope violations are advisory only: the hub reports `details.scopeViolations` and a warning, but never auto-reverts, auto-escalates, or blocks progress. Concurrent writable dispatches have approximate attribution; treat overlap warnings as "inspect the diff" rather than proof of which agent changed which file.
40
49
  - **Gate every risky step.** Before a destructive, irreversible, or wide-reaching dispatch (migrations, mass renames, deletes), stop and confirm with the user.
41
- - **Always verify before done.** Never report a change as done without its assertion gate passing — including a code review and, where relevant, a security pass and the runtime proof above.
42
- - **Prefer two reads over one guess.** When evidence is thin, dispatch a second specialist to confirm rather than proceeding on a single uncertain result.
50
+ - **Always verify before done.** Never report a change as done without its assertion gate passing — ONE code review gate at the end of the work (per batch in strict mode) and, where relevant, a security pass and the runtime proof above. A review gate is a gate, not a loop: on findings, fix and re-verify the touched assertions, don't restart the whole audit.
51
+ - **Two reads only in strict mode.** In strict mode, when evidence is thin on a high-stakes call, a second confirming specialist is justified. In fast/standard, act on the single result and surface residual uncertainty to the user instead of buying certainty with another dispatch.
43
52
  - **Surface trade-offs, don't bury them.** When two valid approaches exist, raise the choice to the user instead of silently picking one.
44
- - **Slow is smooth.** Optimize for not having to redo work, not for the fewest dispatches.
53
+ - **Budget-aware, not dispatch-happy.** Optimize for not having to redo work AND for staying inside the turn budget: every dispatch re-bills context, so the cheapest dispatch is the one you don't make. Batch instead of splitting; reuse findings instead of re-deriving them.
45
54
  - **Summarize crisply.** Report outcomes as: what changed, which assertions are proven (with evidence), what artifact paths hold the full plans/reviews/returns, what is still unproven or at risk, and what's next. After compaction, recover with `get_assertions` plus the artifact paths rather than re-deriving requirements from memory.
@@ -2,13 +2,13 @@
2
2
  name: plan-reviewer
3
3
  description: Plan critic — reviews, challenges, and validates implementation plans
4
4
  tools: read,grep,find,ls
5
- model: openai-codex/gpt-5.6-sol
5
+ model: openai-codex/gpt-5.6-terra
6
6
  models:
7
- - openai-codex/gpt-5.6-terra
7
+ - openai-codex/gpt-5.6-sol
8
8
  - openai-codex/gpt-5.6-luna
9
9
  - ollama/nemotron-3-ultra:cloud
10
10
  - ollama/glm-5.2:cloud
11
- thinking: high
11
+ thinking: medium
12
12
  delegate_depth: 1
13
13
  subagents:
14
14
  feasibility:
@@ -9,14 +9,14 @@ models:
9
9
  - ollama/kimi-k2.7-code:cloud
10
10
  - ollama/glm-5.2:cloud
11
11
  - ollama/nemotron-3-ultra:cloud
12
- thinking: medium
12
+ thinking: low
13
13
  delegate_depth: 1
14
14
  subagents:
15
15
  coverage-scout:
16
- model: openai-codex/gpt-5.6-luna
16
+ model: openai-codex/gpt-5.3-codex-spark
17
17
  tools: read,grep,find,ls
18
18
  conventions:
19
- model: openai-codex/gpt-5.6-luna
19
+ model: openai-codex/gpt-5.3-codex-spark
20
20
  tools: read,grep,find,ls
21
21
  ---
22
22
 
@@ -37,7 +37,14 @@ You have pre-configured read-only scouts on a fast/cheap model:
37
37
  `coverage-scout` and `conventions`. The budget is 4 delegate children per
38
38
  dispatch. You write all tests yourself — NEVER delegate test writing.
39
39
 
40
- 1. Before writing tests, in ONE message issue parallel `delegate` calls: send
40
+ **Run the pre-pass only when it earns its cost:** the FIRST test dispatch in a
41
+ feature or an unfamiliar area of the codebase. SKIP it (and go straight to the
42
+ Approach below) when you are adding a few targeted tests to files you have
43
+ already worked with this session, when the task names the exact test file and
44
+ pattern to follow, or when a prior dispatch's scout findings still cover this
45
+ area — reuse those findings instead of re-scouting.
46
+
47
+ 1. When the pre-pass applies, in ONE message issue parallel `delegate` calls: send
41
48
  `coverage-scout` the code under test so it inventories the existing tests
42
49
  and maps coverage gaps (public API, edge cases, error paths not yet
43
50
  covered) — and when the task carries acceptance assertions, have it report