@chankov/agent-fleet 0.0.5 → 0.0.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude/commands/set-hermes-watchdog.md +6 -0
- package/.opencode/commands/af-set-hermes-watchdog.md +6 -0
- package/.pi/extensions/agent-fleet-update-check/README.md +4 -4
- package/.pi/extensions/btw/README.md +10 -10
- package/.pi/extensions/btw/index.ts +11 -11
- package/.pi/extensions/chrome-devtools-mcp/README.md +2 -2
- package/.pi/extensions/chrome-devtools-mcp/index.ts +1 -0
- package/.pi/extensions/compact-and-continue/README.md +2 -2
- package/.pi/extensions/pi-voice-stt/README.md +7 -7
- package/.pi/extensions/pi-voice-stt/index.ts +4 -4
- package/.pi/harnesses/agent-hub/README.md +133 -74
- package/.pi/harnesses/agent-hub/artifacts.js +56 -2
- package/.pi/harnesses/agent-hub/assertion-ledger.js +58 -0
- package/.pi/harnesses/agent-hub/backend-policy.js +1 -1
- package/.pi/harnesses/agent-hub/context-window.js +106 -0
- package/.pi/harnesses/agent-hub/delegate.ts +61 -12
- package/.pi/harnesses/agent-hub/drift-watchdog.js +55 -9
- package/.pi/harnesses/agent-hub/helpers.ts +34 -0
- package/.pi/harnesses/agent-hub/index.ts +970 -406
- package/.pi/harnesses/agent-hub/monitor-invoke-journal.ts +131 -0
- package/.pi/harnesses/agent-hub/monitor-invoke.ts +92 -0
- package/.pi/harnesses/agent-hub/monitor-lifecycle.ts +2 -2
- package/.pi/harnesses/agent-hub/monitor-session-bridge.ts +257 -11
- package/.pi/harnesses/agent-hub/package.json +1 -1
- package/.pi/harnesses/agent-hub/provider-semaphore.js +138 -0
- package/.pi/harnesses/agent-hub/return-contract.js +78 -0
- package/.pi/harnesses/agent-hub/return-extract.js +75 -0
- package/.pi/harnesses/agent-hub/run-budget.js +30 -4
- package/.pi/harnesses/agent-hub/session-health.js +110 -0
- package/.pi/harnesses/agent-hub/spawn.ts +109 -1
- package/.pi/harnesses/agent-hub/spawned-peers.js +74 -0
- package/.pi/harnesses/coms/README.md +6 -5
- package/.pi/harnesses/coms/index.ts +92 -70
- package/.pi/harnesses/coms/package.json +1 -1
- package/.pi/harnesses/damage-control-continue/README.md +9 -9
- package/.pi/harnesses/damage-control-continue/index.ts +11 -11
- package/.pi/harnesses/damage-control-continue/package.json +1 -1
- package/.pi/harnesses/lib/coms-registry-entry.ts +94 -0
- package/.pi/harnesses/lib/herdr-client.ts +7 -2
- package/.pi/harnesses/lib/herdr-presence.ts +141 -30
- package/.pi/harnesses/lib/hermes-monitor-events.ts +136 -0
- package/.pi/harnesses/lib/hermes-monitor-model.ts +9 -0
- package/.pi/harnesses/lib/hermes-monitor-registry.ts +1 -1
- package/.pi/harnesses/lib/hermes-monitor-socket.ts +47 -2
- package/.pi/prompts/{doctor-agent-fleet.md → af-doctor-agent-fleet.md} +1 -1
- package/.pi/prompts/af-set-hermes-watchdog.md +6 -0
- package/.pi/prompts/{setup-agent-fleet.md → af-setup-agent-fleet.md} +1 -1
- package/.versions/0.0.6/.claude/commands/build.md +44 -0
- package/.versions/0.0.6/.claude/commands/code-simplify.md +22 -0
- package/.versions/0.0.6/.claude/commands/design-agent.md +14 -0
- package/.versions/0.0.6/.claude/commands/doctor-agent-fleet.md +17 -0
- package/.versions/0.0.6/.claude/commands/orchestrate.md +112 -0
- package/.versions/0.0.6/.claude/commands/plan.md +16 -0
- package/.versions/0.0.6/.claude/commands/prime.md +22 -0
- package/.versions/0.0.6/.claude/commands/review.md +16 -0
- package/.versions/0.0.6/.claude/commands/set-hermes-telegram.md +15 -0
- package/.versions/0.0.6/.claude/commands/setup-agent-fleet.md +25 -0
- package/.versions/0.0.6/.claude/commands/ship.md +72 -0
- package/.versions/0.0.6/.claude/commands/spec.md +15 -0
- package/.versions/0.0.6/.claude/commands/test.md +19 -0
- package/.versions/0.0.6/.claude/commands/webperf.md +32 -0
- package/.versions/0.0.6/.claude/orchestrate-teams.yaml +24 -0
- package/.versions/0.0.6/.opencode/commands/af-build.md +17 -0
- package/.versions/0.0.6/.opencode/commands/af-code-simplify.md +16 -0
- package/.versions/0.0.6/.opencode/commands/af-compound.md +16 -0
- package/.versions/0.0.6/.opencode/commands/af-design-agent.md +15 -0
- package/.versions/0.0.6/.opencode/commands/af-doctor-agent-fleet.md +17 -0
- package/.versions/0.0.6/.opencode/commands/af-orchestrate.md +112 -0
- package/.versions/0.0.6/.opencode/commands/af-plan.md +16 -0
- package/.versions/0.0.6/.opencode/commands/af-prime.md +22 -0
- package/.versions/0.0.6/.opencode/commands/af-review.md +15 -0
- package/.versions/0.0.6/.opencode/commands/af-set-hermes-telegram.md +15 -0
- package/.versions/0.0.6/.opencode/commands/af-setup-agent-fleet.md +15 -0
- package/.versions/0.0.6/.opencode/commands/af-ship.md +16 -0
- package/.versions/0.0.6/.opencode/commands/af-spec.md +16 -0
- package/.versions/0.0.6/.opencode/commands/af-test.md +21 -0
- package/.versions/0.0.6/.opencode/commands/af-webperf.md +32 -0
- package/.versions/0.0.6/.opencode/orchestrate-teams.yaml +24 -0
- package/.versions/0.0.6/.pi/agents/dispatch-policy.yaml +32 -0
- package/.versions/0.0.6/.pi/agents/model-profiles.yaml +20 -0
- package/.versions/0.0.6/.pi/agents/peers.yaml +146 -0
- package/.versions/0.0.6/.pi/agents/teams.yaml +39 -0
- package/.versions/0.0.6/.pi/damage-control-rules.yaml +297 -0
- package/.versions/0.0.6/.pi/extensions/agent-fleet-update-check/README.md +58 -0
- package/.versions/0.0.6/.pi/extensions/agent-fleet-update-check/index.ts +161 -0
- package/.versions/0.0.6/.pi/extensions/agent-fleet-update-check/package.json +6 -0
- package/.versions/0.0.6/.pi/extensions/btw/README.md +118 -0
- package/.versions/0.0.6/.pi/extensions/btw/index.ts +917 -0
- package/.versions/0.0.6/.pi/extensions/btw/package.json +6 -0
- package/.versions/0.0.6/.pi/extensions/btw/state.js +179 -0
- package/.versions/0.0.6/.pi/extensions/chrome-devtools-mcp/README.md +58 -0
- package/.versions/0.0.6/.pi/extensions/chrome-devtools-mcp/index.ts +93 -0
- package/.versions/0.0.6/.pi/extensions/chrome-devtools-mcp/package.json +6 -0
- package/.versions/0.0.6/.pi/extensions/compact-and-continue/README.md +42 -0
- package/.versions/0.0.6/.pi/extensions/compact-and-continue/index.ts +120 -0
- package/.versions/0.0.6/.pi/extensions/compact-and-continue/package.json +6 -0
- package/.versions/0.0.6/.pi/extensions/mcp-bridge/README.md +46 -0
- package/.versions/0.0.6/.pi/extensions/mcp-bridge/index.ts +206 -0
- package/.versions/0.0.6/.pi/extensions/mcp-bridge/package.json +6 -0
- package/.versions/0.0.6/.pi/extensions/package-lock.json +1143 -0
- package/.versions/0.0.6/.pi/extensions/package.json +9 -0
- package/.versions/0.0.6/.pi/extensions/pi-voice-stt/README.md +201 -0
- package/.versions/0.0.6/.pi/extensions/pi-voice-stt/config.ts +198 -0
- package/.versions/0.0.6/.pi/extensions/pi-voice-stt/examples/stt.json +35 -0
- package/.versions/0.0.6/.pi/extensions/pi-voice-stt/index.ts +248 -0
- package/.versions/0.0.6/.pi/extensions/pi-voice-stt/package.json +6 -0
- package/.versions/0.0.6/.pi/extensions/pi-voice-stt/providers.ts +214 -0
- package/.versions/0.0.6/.pi/extensions/pi-voice-stt/recorder.ts +158 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/README.md +798 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/access-approval.ts +135 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/artifacts.js +92 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/backend-policy.js +153 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/delegate.ts +386 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/drift-watchdog.js +165 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/evidence-rules.js +96 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/footer.ts +29 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/helpers.ts +214 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/index.ts +8045 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/monitor-session-bridge.ts +11 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/package.json +7 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/research-retention.js +34 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/return-contract.js +215 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/run-budget.js +155 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/scope-gate.js +103 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/spawn.ts +246 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/version.ts +18 -0
- package/.versions/0.0.6/.pi/harnesses/ask-user-remote/README.md +19 -0
- package/.versions/0.0.6/.pi/harnesses/ask-user-remote/index.ts +321 -0
- package/.versions/0.0.6/.pi/harnesses/ask-user-remote/race-core.js +106 -0
- package/.versions/0.0.6/.pi/harnesses/coms/README.md +92 -0
- package/.versions/0.0.6/.pi/harnesses/coms/index.ts +1745 -0
- package/.versions/0.0.6/.pi/harnesses/coms/package.json +7 -0
- package/.versions/0.0.6/.pi/harnesses/coms/version.ts +18 -0
- package/.versions/0.0.6/.pi/harnesses/damage-control-continue/README.md +117 -0
- package/.versions/0.0.6/.pi/harnesses/damage-control-continue/index.ts +536 -0
- package/.versions/0.0.6/.pi/harnesses/damage-control-continue/package.json +7 -0
- package/.versions/0.0.6/.pi/harnesses/damage-control-continue/version.ts +18 -0
- package/.versions/0.0.6/.pi/harnesses/lib/damage-control-shared.ts +197 -0
- package/.versions/0.0.6/.pi/harnesses/lib/herdr-client.ts +458 -0
- package/.versions/0.0.6/.pi/harnesses/lib/herdr-presence.ts +288 -0
- package/.versions/0.0.6/.pi/harnesses/lib/hermes-monitor-herdr.ts +28 -0
- package/.versions/0.0.6/.pi/harnesses/lib/hermes-monitor-model.ts +9 -0
- package/.versions/0.0.6/.pi/harnesses/lib/hermes-monitor-registry.ts +6 -0
- package/.versions/0.0.6/.pi/harnesses/lib/hermes-monitor-socket.ts +118 -0
- package/.versions/0.0.6/.pi/harnesses/lib/hermes-monitor-store.ts +31 -0
- package/.versions/0.0.6/.pi/harnesses/package-lock.json +35 -0
- package/.versions/0.0.6/.pi/harnesses/package.json +9 -0
- package/.versions/0.0.6/.pi/prompts/af-build.md +24 -0
- package/.versions/0.0.6/.pi/prompts/af-code-simplify.md +22 -0
- package/.versions/0.0.6/.pi/prompts/af-doctor-agent-fleet.md +15 -0
- package/.versions/0.0.6/.pi/prompts/af-plan.md +16 -0
- package/.versions/0.0.6/.pi/prompts/af-review.md +16 -0
- package/.versions/0.0.6/.pi/prompts/af-set-hermes-telegram.md +15 -0
- package/.versions/0.0.6/.pi/prompts/af-setup-agent-fleet.md +27 -0
- package/.versions/0.0.6/.pi/prompts/af-ship.md +17 -0
- package/.versions/0.0.6/.pi/prompts/af-spec.md +15 -0
- package/.versions/0.0.6/.pi/prompts/af-test.md +19 -0
- package/.versions/0.0.6/.pi/skills/bowser/SKILL.md +145 -0
- package/.versions/0.0.6/.version +1 -0
- package/.versions/0.0.6/agents/architect.md +23 -0
- package/.versions/0.0.6/agents/bowser.md +26 -0
- package/.versions/0.0.6/agents/builder.md +53 -0
- package/.versions/0.0.6/agents/code-reviewer.md +205 -0
- package/.versions/0.0.6/agents/deep-researcher.md +31 -0
- package/.versions/0.0.6/agents/documenter.md +18 -0
- package/.versions/0.0.6/agents/orchestrator.md +54 -0
- package/.versions/0.0.6/agents/plan-reviewer.md +60 -0
- package/.versions/0.0.6/agents/planner.md +69 -0
- package/.versions/0.0.6/agents/releaser.md +24 -0
- package/.versions/0.0.6/agents/researcher.md +28 -0
- package/.versions/0.0.6/agents/security-auditor.md +166 -0
- package/.versions/0.0.6/agents/test-engineer.md +151 -0
- package/.versions/0.0.6/agents/web-debugger.md +42 -0
- package/.versions/0.0.6/agents/web-performance-auditor.md +192 -0
- package/.versions/0.0.6/codex/CONDUCTOR.md +148 -0
- package/.versions/0.0.6/docs/ARCHITECTURE.md +210 -0
- package/.versions/0.0.6/docs/agent-fleet-setup.md +366 -0
- package/.versions/0.0.6/docs/claude-code-coms-bridge.md +103 -0
- package/.versions/0.0.6/docs/codex-remote-conductor.md +170 -0
- package/.versions/0.0.6/docs/coms-hermes-bridge.md +179 -0
- package/.versions/0.0.6/docs/getting-started.md +183 -0
- package/.versions/0.0.6/docs/npm-install.md +337 -0
- package/.versions/0.0.6/docs/opencode-setup.md +249 -0
- package/.versions/0.0.6/docs/pi-extensions.md +293 -0
- package/.versions/0.0.6/docs/pi-setup.md +476 -0
- package/.versions/0.0.6/docs/skill-anatomy.md +150 -0
- package/.versions/0.0.6/hermes/README.md +231 -0
- package/.versions/0.0.6/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
- package/.versions/0.0.6/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
- package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +151 -0
- package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
- package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
- package/.versions/0.0.6/hermes/skills/hub-conductor/SKILL.md +84 -0
- package/.versions/0.0.6/hermes/skills/hub-liaison/SKILL.md +84 -0
- package/.versions/0.0.6/hooks/SIMPLIFY-IGNORE.md +90 -0
- package/.versions/0.0.6/hooks/coms-stop-hook.mjs +73 -0
- package/.versions/0.0.6/hooks/hooks.json +14 -0
- package/.versions/0.0.6/hooks/session-start.sh +74 -0
- package/.versions/0.0.6/hooks/simplify-ignore.sh +302 -0
- package/.versions/0.0.6/justfile +245 -0
- package/.versions/0.0.6/references/accessibility-checklist.md +160 -0
- package/.versions/0.0.6/references/definition-of-done.md +67 -0
- package/.versions/0.0.6/references/fleet-coordination-patterns.md +151 -0
- package/.versions/0.0.6/references/observability-checklist.md +91 -0
- package/.versions/0.0.6/references/orchestration-patterns.md +370 -0
- package/.versions/0.0.6/references/performance-checklist.md +153 -0
- package/.versions/0.0.6/references/prompting-patterns.md +380 -0
- package/.versions/0.0.6/references/security-checklist.md +179 -0
- package/.versions/0.0.6/references/testing-patterns.md +236 -0
- package/.versions/0.0.6/scripts/codex-conductor.ts +41 -0
- package/.versions/0.0.6/scripts/codex-remote-control.ts +167 -0
- package/.versions/0.0.6/scripts/coms-claude-bridge.ts +286 -0
- package/.versions/0.0.6/scripts/coms-cli.ts +484 -0
- package/.versions/0.0.6/scripts/coms-hermes-bridge.ts +413 -0
- package/.versions/0.0.6/scripts/fleet.ts +141 -0
- package/.versions/0.0.6/scripts/hermes-monitor-capability-runner.ts +25 -0
- package/.versions/0.0.6/scripts/hermes-monitor-scenario.ts +7 -0
- package/.versions/0.0.6/scripts/lib/claude-bridge-core.ts +100 -0
- package/.versions/0.0.6/scripts/lib/codex-conductor.ts +88 -0
- package/.versions/0.0.6/scripts/lib/codex-remote-control.ts +480 -0
- package/.versions/0.0.6/scripts/lib/coms-envelope.ts +539 -0
- package/.versions/0.0.6/scripts/lib/fake-herdr-server.ts +88 -0
- package/.versions/0.0.6/scripts/lib/fleet-command.ts +109 -0
- package/.versions/0.0.6/scripts/lib/herdr-layout.ts +263 -0
- package/.versions/0.0.6/scripts/lib/hermes-bridge-core.ts +241 -0
- package/.versions/0.0.6/scripts/lib/hermes-monitor-herdr.ts +2 -0
- package/.versions/0.0.6/scripts/lib/hermes-monitor-model.ts +3 -0
- package/.versions/0.0.6/scripts/lib/hermes-monitor-registry.ts +2 -0
- package/.versions/0.0.6/scripts/lib/hermes-monitor-socket.ts +2 -0
- package/.versions/0.0.6/scripts/lib/hermes-monitor-store.ts +2 -0
- package/.versions/0.0.6/scripts/lib/persona-banner.ts +62 -0
- package/.versions/0.0.6/scripts/lib/spawn-stagger.ts +101 -0
- package/.versions/0.0.6/scripts/lib/team-project.ts +191 -0
- package/.versions/0.0.6/scripts/lib/team-snapshot.ts +147 -0
- package/.versions/0.0.6/scripts/peer-banner.ts +40 -0
- package/.versions/0.0.6/scripts/team-snapshot.ts +237 -0
- package/.versions/0.0.6/scripts/team-up.ts +351 -0
- package/.versions/0.0.6/skills/_internal/grilling.md +11 -0
- package/.versions/0.0.6/skills/browser-testing-with-devtools/SKILL.md +352 -0
- package/.versions/0.0.6/skills/code-review-and-quality/SKILL.md +381 -0
- package/.versions/0.0.6/skills/compound-learning/SKILL.md +137 -0
- package/.versions/0.0.6/skills/context-engineering/SKILL.md +291 -0
- package/.versions/0.0.6/skills/deprecation-and-migration/SKILL.md +206 -0
- package/.versions/0.0.6/skills/designing-agents/SKILL.md +394 -0
- package/.versions/0.0.6/skills/designing-agents/pi-harness-authoring.md +222 -0
- package/.versions/0.0.6/skills/frontend-ui-engineering/SKILL.md +328 -0
- package/.versions/0.0.6/skills/git-workflow-and-versioning/SKILL.md +316 -0
- package/.versions/0.0.6/skills/guided-workspace-setup/SKILL.md +544 -0
- package/.versions/0.0.6/skills/guided-workspace-setup/companion-manifest.json +35 -0
- package/.versions/0.0.6/skills/idea-refine/SKILL.md +182 -0
- package/.versions/0.0.6/skills/idea-refine/examples.md +238 -0
- package/.versions/0.0.6/skills/idea-refine/frameworks.md +99 -0
- package/.versions/0.0.6/skills/idea-refine/refinement-criteria.md +113 -0
- package/.versions/0.0.6/skills/idea-refine/scripts/idea-refine.sh +15 -0
- package/.versions/0.0.6/skills/incremental-implementation/SKILL.md +287 -0
- package/.versions/0.0.6/skills/interview-me/SKILL.md +226 -0
- package/.versions/0.0.6/skills/orchestration-verification/SKILL.md +181 -0
- package/.versions/0.0.6/skills/peer-coms/SKILL.md +90 -0
- package/.versions/0.0.6/skills/performance-optimization/SKILL.md +350 -0
- package/.versions/0.0.6/skills/planning-and-task-breakdown/SKILL.md +236 -0
- package/.versions/0.0.6/skills/security-and-hardening/SKILL.md +461 -0
- package/.versions/0.0.6/skills/spec-driven-development/SKILL.md +245 -0
- package/.versions/0.0.6/skills/using-agent-skills/SKILL.md +199 -0
- package/.versions/0.0.6/systemd/user/agent-fleet-codex-remote-control.service.in +23 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/LICENSE +21 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/README.md +11 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/api-and-interface-design/SKILL.md +294 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/browser-testing-with-devtools/SKILL.md +317 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/ci-cd-and-automation/SKILL.md +390 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/code-review-and-quality/SKILL.md +396 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/code-simplification/SKILL.md +331 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/context-engineering/SKILL.md +289 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/debugging-and-error-recovery/SKILL.md +300 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/deprecation-and-migration/SKILL.md +247 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/documentation-and-adrs/SKILL.md +278 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/doubt-driven-development/SKILL.md +243 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/frontend-ui-engineering/SKILL.md +328 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/git-workflow-and-versioning/SKILL.md +355 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/idea-refine/SKILL.md +178 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/idea-refine/examples.md +238 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/idea-refine/frameworks.md +99 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/idea-refine/refinement-criteria.md +113 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/idea-refine/scripts/idea-refine.sh +15 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/incremental-implementation/SKILL.md +249 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/interview-me/SKILL.md +225 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/observability-and-instrumentation/SKILL.md +203 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/performance-optimization/SKILL.md +350 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/planning-and-task-breakdown/SKILL.md +234 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/security-and-hardening/SKILL.md +467 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/shipping-and-launch/SKILL.md +310 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/source-driven-development/SKILL.md +194 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/spec-driven-development/SKILL.md +206 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/test-driven-development/SKILL.md +383 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/using-agent-skills/SKILL.md +191 -0
- package/.versions/0.0.7/.claude/commands/build.md +44 -0
- package/.versions/0.0.7/.claude/commands/code-simplify.md +22 -0
- package/.versions/0.0.7/.claude/commands/design-agent.md +14 -0
- package/.versions/0.0.7/.claude/commands/doctor-agent-fleet.md +17 -0
- package/.versions/0.0.7/.claude/commands/orchestrate.md +112 -0
- package/.versions/0.0.7/.claude/commands/plan.md +16 -0
- package/.versions/0.0.7/.claude/commands/prime.md +22 -0
- package/.versions/0.0.7/.claude/commands/review.md +16 -0
- package/.versions/0.0.7/.claude/commands/set-hermes-telegram.md +15 -0
- package/.versions/0.0.7/.claude/commands/set-hermes-watchdog.md +6 -0
- package/.versions/0.0.7/.claude/commands/setup-agent-fleet.md +25 -0
- package/.versions/0.0.7/.claude/commands/ship.md +72 -0
- package/.versions/0.0.7/.claude/commands/spec.md +15 -0
- package/.versions/0.0.7/.claude/commands/test.md +19 -0
- package/.versions/0.0.7/.claude/commands/webperf.md +32 -0
- package/.versions/0.0.7/.claude/orchestrate-teams.yaml +24 -0
- package/.versions/0.0.7/.opencode/commands/af-build.md +17 -0
- package/.versions/0.0.7/.opencode/commands/af-code-simplify.md +16 -0
- package/.versions/0.0.7/.opencode/commands/af-compound.md +16 -0
- package/.versions/0.0.7/.opencode/commands/af-design-agent.md +15 -0
- package/.versions/0.0.7/.opencode/commands/af-doctor-agent-fleet.md +17 -0
- package/.versions/0.0.7/.opencode/commands/af-orchestrate.md +112 -0
- package/.versions/0.0.7/.opencode/commands/af-plan.md +16 -0
- package/.versions/0.0.7/.opencode/commands/af-prime.md +22 -0
- package/.versions/0.0.7/.opencode/commands/af-review.md +15 -0
- package/.versions/0.0.7/.opencode/commands/af-set-hermes-telegram.md +15 -0
- package/.versions/0.0.7/.opencode/commands/af-set-hermes-watchdog.md +6 -0
- package/.versions/0.0.7/.opencode/commands/af-setup-agent-fleet.md +15 -0
- package/.versions/0.0.7/.opencode/commands/af-ship.md +16 -0
- package/.versions/0.0.7/.opencode/commands/af-spec.md +16 -0
- package/.versions/0.0.7/.opencode/commands/af-test.md +21 -0
- package/.versions/0.0.7/.opencode/commands/af-webperf.md +32 -0
- package/.versions/0.0.7/.opencode/orchestrate-teams.yaml +24 -0
- package/.versions/0.0.7/.pi/agents/dispatch-policy.yaml +32 -0
- package/.versions/0.0.7/.pi/agents/model-profiles.yaml +20 -0
- package/.versions/0.0.7/.pi/agents/peers.yaml +146 -0
- package/.versions/0.0.7/.pi/agents/teams.yaml +39 -0
- package/.versions/0.0.7/.pi/damage-control-rules.yaml +297 -0
- package/.versions/0.0.7/.pi/extensions/agent-fleet-update-check/README.md +58 -0
- package/.versions/0.0.7/.pi/extensions/agent-fleet-update-check/index.ts +161 -0
- package/.versions/0.0.7/.pi/extensions/agent-fleet-update-check/package.json +6 -0
- package/.versions/0.0.7/.pi/extensions/btw/README.md +118 -0
- package/.versions/0.0.7/.pi/extensions/btw/index.ts +917 -0
- package/.versions/0.0.7/.pi/extensions/btw/package.json +6 -0
- package/.versions/0.0.7/.pi/extensions/btw/state.js +179 -0
- package/.versions/0.0.7/.pi/extensions/chrome-devtools-mcp/README.md +58 -0
- package/.versions/0.0.7/.pi/extensions/chrome-devtools-mcp/index.ts +93 -0
- package/.versions/0.0.7/.pi/extensions/chrome-devtools-mcp/package.json +6 -0
- package/.versions/0.0.7/.pi/extensions/compact-and-continue/README.md +42 -0
- package/.versions/0.0.7/.pi/extensions/compact-and-continue/index.ts +120 -0
- package/.versions/0.0.7/.pi/extensions/compact-and-continue/package.json +6 -0
- package/.versions/0.0.7/.pi/extensions/mcp-bridge/README.md +46 -0
- package/.versions/0.0.7/.pi/extensions/mcp-bridge/index.ts +206 -0
- package/.versions/0.0.7/.pi/extensions/mcp-bridge/package.json +6 -0
- package/.versions/0.0.7/.pi/extensions/package-lock.json +1143 -0
- package/.versions/0.0.7/.pi/extensions/package.json +9 -0
- package/.versions/0.0.7/.pi/extensions/pi-voice-stt/README.md +201 -0
- package/.versions/0.0.7/.pi/extensions/pi-voice-stt/config.ts +198 -0
- package/.versions/0.0.7/.pi/extensions/pi-voice-stt/examples/stt.json +35 -0
- package/.versions/0.0.7/.pi/extensions/pi-voice-stt/index.ts +248 -0
- package/.versions/0.0.7/.pi/extensions/pi-voice-stt/package.json +6 -0
- package/.versions/0.0.7/.pi/extensions/pi-voice-stt/providers.ts +214 -0
- package/.versions/0.0.7/.pi/extensions/pi-voice-stt/recorder.ts +158 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/README.md +857 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/access-approval.ts +135 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/artifacts.js +146 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/assertion-ledger.js +58 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/backend-policy.js +153 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/context-window.js +106 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/delegate.ts +435 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/drift-watchdog.js +211 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/evidence-rules.js +96 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/footer.ts +29 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/helpers.ts +248 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/index.ts +8609 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/monitor-invoke-journal.ts +131 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/monitor-invoke.ts +92 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/monitor-session-bridge.ts +257 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/package.json +7 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/provider-semaphore.js +138 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/research-retention.js +34 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/return-contract.js +293 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/return-extract.js +75 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/run-budget.js +181 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/scope-gate.js +103 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/session-health.js +110 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/spawn.ts +354 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/spawned-peers.js +74 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/version.ts +18 -0
- package/.versions/0.0.7/.pi/harnesses/ask-user-remote/README.md +19 -0
- package/.versions/0.0.7/.pi/harnesses/ask-user-remote/index.ts +321 -0
- package/.versions/0.0.7/.pi/harnesses/ask-user-remote/race-core.js +106 -0
- package/.versions/0.0.7/.pi/harnesses/coms/README.md +93 -0
- package/.versions/0.0.7/.pi/harnesses/coms/index.ts +1767 -0
- package/.versions/0.0.7/.pi/harnesses/coms/package.json +7 -0
- package/.versions/0.0.7/.pi/harnesses/coms/version.ts +18 -0
- package/.versions/0.0.7/.pi/harnesses/damage-control-continue/README.md +117 -0
- package/.versions/0.0.7/.pi/harnesses/damage-control-continue/index.ts +536 -0
- package/.versions/0.0.7/.pi/harnesses/damage-control-continue/package.json +7 -0
- package/.versions/0.0.7/.pi/harnesses/damage-control-continue/version.ts +18 -0
- package/.versions/0.0.7/.pi/harnesses/lib/coms-registry-entry.ts +94 -0
- package/.versions/0.0.7/.pi/harnesses/lib/damage-control-shared.ts +197 -0
- package/.versions/0.0.7/.pi/harnesses/lib/herdr-client.ts +463 -0
- package/.versions/0.0.7/.pi/harnesses/lib/herdr-presence.ts +399 -0
- package/.versions/0.0.7/.pi/harnesses/lib/hermes-monitor-events.ts +136 -0
- package/.versions/0.0.7/.pi/harnesses/lib/hermes-monitor-herdr.ts +28 -0
- package/.versions/0.0.7/.pi/harnesses/lib/hermes-monitor-model.ts +18 -0
- package/.versions/0.0.7/.pi/harnesses/lib/hermes-monitor-registry.ts +6 -0
- package/.versions/0.0.7/.pi/harnesses/lib/hermes-monitor-socket.ts +163 -0
- package/.versions/0.0.7/.pi/harnesses/lib/hermes-monitor-store.ts +31 -0
- package/.versions/0.0.7/.pi/harnesses/package-lock.json +35 -0
- package/.versions/0.0.7/.pi/harnesses/package.json +9 -0
- package/.versions/0.0.7/.pi/prompts/af-build.md +24 -0
- package/.versions/0.0.7/.pi/prompts/af-code-simplify.md +22 -0
- package/.versions/0.0.7/.pi/prompts/af-doctor-agent-fleet.md +15 -0
- package/.versions/0.0.7/.pi/prompts/af-plan.md +16 -0
- package/.versions/0.0.7/.pi/prompts/af-review.md +16 -0
- package/.versions/0.0.7/.pi/prompts/af-set-hermes-telegram.md +15 -0
- package/.versions/0.0.7/.pi/prompts/af-set-hermes-watchdog.md +6 -0
- package/.versions/0.0.7/.pi/prompts/af-setup-agent-fleet.md +27 -0
- package/.versions/0.0.7/.pi/prompts/af-ship.md +17 -0
- package/.versions/0.0.7/.pi/prompts/af-spec.md +15 -0
- package/.versions/0.0.7/.pi/prompts/af-test.md +19 -0
- package/.versions/0.0.7/.pi/skills/bowser/SKILL.md +145 -0
- package/.versions/0.0.7/.version +1 -0
- package/.versions/0.0.7/agents/architect.md +23 -0
- package/.versions/0.0.7/agents/bowser.md +26 -0
- package/.versions/0.0.7/agents/builder.md +53 -0
- package/.versions/0.0.7/agents/code-reviewer.md +205 -0
- package/.versions/0.0.7/agents/deep-researcher.md +31 -0
- package/.versions/0.0.7/agents/documenter.md +18 -0
- package/.versions/0.0.7/agents/orchestrator.md +65 -0
- package/.versions/0.0.7/agents/plan-reviewer.md +60 -0
- package/.versions/0.0.7/agents/planner.md +69 -0
- package/.versions/0.0.7/agents/releaser.md +24 -0
- package/.versions/0.0.7/agents/researcher.md +28 -0
- package/.versions/0.0.7/agents/security-auditor.md +166 -0
- package/.versions/0.0.7/agents/test-engineer.md +151 -0
- package/.versions/0.0.7/agents/web-debugger.md +42 -0
- package/.versions/0.0.7/agents/web-performance-auditor.md +192 -0
- package/.versions/0.0.7/codex/CONDUCTOR.md +148 -0
- package/.versions/0.0.7/docs/ARCHITECTURE.md +262 -0
- package/.versions/0.0.7/docs/agent-fleet-setup.md +366 -0
- package/.versions/0.0.7/docs/claude-code-coms-bridge.md +109 -0
- package/.versions/0.0.7/docs/codex-remote-conductor.md +170 -0
- package/.versions/0.0.7/docs/coms-hermes-bridge.md +189 -0
- package/.versions/0.0.7/docs/getting-started.md +231 -0
- package/.versions/0.0.7/docs/npm-install.md +337 -0
- package/.versions/0.0.7/docs/opencode-setup.md +249 -0
- package/.versions/0.0.7/docs/pi-extensions.md +293 -0
- package/.versions/0.0.7/docs/pi-setup.md +476 -0
- package/.versions/0.0.7/docs/skill-anatomy.md +150 -0
- package/.versions/0.0.7/hermes/README.md +347 -0
- package/.versions/0.0.7/hermes/desktop-plugins/agent-fleet-herdr/plugin.js +1291 -0
- package/.versions/0.0.7/hermes/desktop-plugins/agent-fleet-herdr/presentation.js +672 -0
- package/.versions/0.0.7/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
- package/.versions/0.0.7/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
- package/.versions/0.0.7/hermes/gates/gate-o-capability.md +8 -0
- package/.versions/0.0.7/hermes/gates/gate-o-validator-fixtures.json +1 -0
- package/.versions/0.0.7/hermes/plugins/agent-fleet-herdr/dashboard/activity.py +770 -0
- package/.versions/0.0.7/hermes/plugins/agent-fleet-herdr/dashboard/coms_registry.py +134 -0
- package/.versions/0.0.7/hermes/plugins/agent-fleet-herdr/dashboard/coms_send.py +350 -0
- package/.versions/0.0.7/hermes/plugins/agent-fleet-herdr/dashboard/herdr_source.py +193 -0
- package/.versions/0.0.7/hermes/plugins/agent-fleet-herdr/dashboard/manifest.json +4 -0
- package/.versions/0.0.7/hermes/plugins/agent-fleet-herdr/dashboard/plugin_api.py +444 -0
- package/.versions/0.0.7/hermes/plugins/agent-fleet-herdr/dashboard/sessions.py +205 -0
- package/.versions/0.0.7/hermes/plugins/agent-fleet-herdr/dashboard/tasks.py +300 -0
- package/.versions/0.0.7/hermes/plugins/agent-fleet-herdr/dashboard/watch.py +819 -0
- package/.versions/0.0.7/hermes/plugins/agent-fleet-herdr/plugin.yaml +8 -0
- package/.versions/0.0.7/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +139 -0
- package/.versions/0.0.7/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
- package/.versions/0.0.7/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
- package/.versions/0.0.7/hermes/skills/hub-conductor/SKILL.md +84 -0
- package/.versions/0.0.7/hermes/skills/hub-liaison/SKILL.md +84 -0
- package/.versions/0.0.7/hermes/skills/hub-watchdog/SKILL.md +76 -0
- package/.versions/0.0.7/hermes/skills/hub-watchdog/manifest.json +1 -0
- package/.versions/0.0.7/hermes/skills/hub-watchdog/scripts/watchdog.py +249 -0
- package/.versions/0.0.7/hermes/skills/hub-watchdog/scripts/watchdog_actions.py +124 -0
- package/.versions/0.0.7/hermes/skills/hub-watchdog/scripts/watchdog_contract.py +76 -0
- package/.versions/0.0.7/hermes/skills/hub-watchdog/scripts/watchdog_delivery.py +10 -0
- package/.versions/0.0.7/hermes/skills/hub-watchdog/scripts/watchdog_engine.py +128 -0
- package/.versions/0.0.7/hermes/skills/hub-watchdog/scripts/watchdog_judgment.py +41 -0
- package/.versions/0.0.7/hermes/skills/hub-watchdog/scripts/watchdog_recovery.py +103 -0
- package/.versions/0.0.7/hermes/skills/hub-watchdog/scripts/watchdog_state.py +163 -0
- package/.versions/0.0.7/hermes/skills/hub-watchdog/scripts/watchdog_transport.py +138 -0
- package/.versions/0.0.7/hermes/watchdog-tests/__init__.py +0 -0
- package/.versions/0.0.7/hooks/SIMPLIFY-IGNORE.md +90 -0
- package/.versions/0.0.7/hooks/coms-stop-hook.mjs +84 -0
- package/.versions/0.0.7/hooks/hooks.json +14 -0
- package/.versions/0.0.7/hooks/session-start.sh +74 -0
- package/.versions/0.0.7/hooks/simplify-ignore.sh +302 -0
- package/.versions/0.0.7/justfile +245 -0
- package/.versions/0.0.7/references/accessibility-checklist.md +160 -0
- package/.versions/0.0.7/references/definition-of-done.md +67 -0
- package/.versions/0.0.7/references/fleet-coordination-patterns.md +151 -0
- package/.versions/0.0.7/references/observability-checklist.md +91 -0
- package/.versions/0.0.7/references/orchestration-patterns.md +370 -0
- package/.versions/0.0.7/references/performance-checklist.md +153 -0
- package/.versions/0.0.7/references/prompting-patterns.md +380 -0
- package/.versions/0.0.7/references/security-checklist.md +179 -0
- package/.versions/0.0.7/references/testing-patterns.md +236 -0
- package/.versions/0.0.7/scripts/codex-conductor.ts +41 -0
- package/.versions/0.0.7/scripts/codex-remote-control.ts +167 -0
- package/.versions/0.0.7/scripts/coms-claude-bridge.ts +401 -0
- package/.versions/0.0.7/scripts/coms-cli.ts +484 -0
- package/.versions/0.0.7/scripts/coms-hermes-bridge.ts +413 -0
- package/.versions/0.0.7/scripts/fleet.ts +149 -0
- package/.versions/0.0.7/scripts/hermes-monitor-capability-runner.ts +25 -0
- package/.versions/0.0.7/scripts/hermes-monitor-scenario.ts +474 -0
- package/.versions/0.0.7/scripts/hermes-watchdog-capability-probe.ts +45 -0
- package/.versions/0.0.7/scripts/install-hermes-plugin.sh +180 -0
- package/.versions/0.0.7/scripts/lib/claude-bridge-core.ts +165 -0
- package/.versions/0.0.7/scripts/lib/codex-conductor.ts +88 -0
- package/.versions/0.0.7/scripts/lib/codex-remote-control.ts +480 -0
- package/.versions/0.0.7/scripts/lib/coms-envelope.ts +582 -0
- package/.versions/0.0.7/scripts/lib/fake-herdr-server.ts +88 -0
- package/.versions/0.0.7/scripts/lib/fleet-command.ts +109 -0
- package/.versions/0.0.7/scripts/lib/herdr-layout.ts +263 -0
- package/.versions/0.0.7/scripts/lib/hermes-bridge-core.ts +241 -0
- package/.versions/0.0.7/scripts/lib/hermes-monitor-events.ts +1 -0
- package/.versions/0.0.7/scripts/lib/hermes-monitor-herdr.ts +2 -0
- package/.versions/0.0.7/scripts/lib/hermes-monitor-model.ts +3 -0
- package/.versions/0.0.7/scripts/lib/hermes-monitor-registry.ts +2 -0
- package/.versions/0.0.7/scripts/lib/hermes-monitor-socket.ts +2 -0
- package/.versions/0.0.7/scripts/lib/hermes-monitor-store.ts +2 -0
- package/.versions/0.0.7/scripts/lib/monitor-env.ts +120 -0
- package/.versions/0.0.7/scripts/lib/persona-banner.ts +62 -0
- package/.versions/0.0.7/scripts/lib/spawn-stagger.ts +101 -0
- package/.versions/0.0.7/scripts/lib/team-project.ts +191 -0
- package/.versions/0.0.7/scripts/lib/team-snapshot.ts +147 -0
- package/.versions/0.0.7/scripts/peer-banner.ts +40 -0
- package/.versions/0.0.7/scripts/team-snapshot.ts +237 -0
- package/.versions/0.0.7/scripts/team-up.ts +360 -0
- package/.versions/0.0.7/skills/_internal/grilling.md +11 -0
- package/.versions/0.0.7/skills/browser-testing-with-devtools/SKILL.md +352 -0
- package/.versions/0.0.7/skills/code-review-and-quality/SKILL.md +381 -0
- package/.versions/0.0.7/skills/compound-learning/SKILL.md +137 -0
- package/.versions/0.0.7/skills/context-engineering/SKILL.md +291 -0
- package/.versions/0.0.7/skills/deprecation-and-migration/SKILL.md +206 -0
- package/.versions/0.0.7/skills/designing-agents/SKILL.md +394 -0
- package/.versions/0.0.7/skills/designing-agents/pi-harness-authoring.md +222 -0
- package/.versions/0.0.7/skills/frontend-ui-engineering/SKILL.md +328 -0
- package/.versions/0.0.7/skills/git-workflow-and-versioning/SKILL.md +316 -0
- package/.versions/0.0.7/skills/guided-workspace-setup/SKILL.md +544 -0
- package/.versions/0.0.7/skills/guided-workspace-setup/companion-manifest.json +35 -0
- package/.versions/0.0.7/skills/idea-refine/SKILL.md +182 -0
- package/.versions/0.0.7/skills/idea-refine/examples.md +238 -0
- package/.versions/0.0.7/skills/idea-refine/frameworks.md +99 -0
- package/.versions/0.0.7/skills/idea-refine/refinement-criteria.md +113 -0
- package/.versions/0.0.7/skills/idea-refine/scripts/idea-refine.sh +15 -0
- package/.versions/0.0.7/skills/incremental-implementation/SKILL.md +287 -0
- package/.versions/0.0.7/skills/interview-me/SKILL.md +226 -0
- package/.versions/0.0.7/skills/orchestration-verification/SKILL.md +181 -0
- package/.versions/0.0.7/skills/peer-coms/SKILL.md +90 -0
- package/.versions/0.0.7/skills/performance-optimization/SKILL.md +350 -0
- package/.versions/0.0.7/skills/planning-and-task-breakdown/SKILL.md +236 -0
- package/.versions/0.0.7/skills/security-and-hardening/SKILL.md +461 -0
- package/.versions/0.0.7/skills/spec-driven-development/SKILL.md +245 -0
- package/.versions/0.0.7/skills/using-agent-skills/SKILL.md +199 -0
- package/.versions/0.0.7/systemd/user/agent-fleet-codex-remote-control.service.in +23 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/LICENSE +21 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/README.md +11 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/api-and-interface-design/SKILL.md +294 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/browser-testing-with-devtools/SKILL.md +317 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/ci-cd-and-automation/SKILL.md +390 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/code-review-and-quality/SKILL.md +396 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/code-simplification/SKILL.md +331 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/context-engineering/SKILL.md +289 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/debugging-and-error-recovery/SKILL.md +300 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/deprecation-and-migration/SKILL.md +247 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/documentation-and-adrs/SKILL.md +278 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/doubt-driven-development/SKILL.md +243 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/frontend-ui-engineering/SKILL.md +328 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/git-workflow-and-versioning/SKILL.md +355 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/idea-refine/SKILL.md +178 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/idea-refine/examples.md +238 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/idea-refine/frameworks.md +99 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/idea-refine/refinement-criteria.md +113 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/idea-refine/scripts/idea-refine.sh +15 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/incremental-implementation/SKILL.md +249 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/interview-me/SKILL.md +225 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/observability-and-instrumentation/SKILL.md +203 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/performance-optimization/SKILL.md +350 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/planning-and-task-breakdown/SKILL.md +234 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/security-and-hardening/SKILL.md +467 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/shipping-and-launch/SKILL.md +310 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/source-driven-development/SKILL.md +194 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/spec-driven-development/SKILL.md +206 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/test-driven-development/SKILL.md +383 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/using-agent-skills/SKILL.md +191 -0
- package/CHANGELOG.md +140 -0
- package/README.md +198 -40
- package/agents/code-reviewer.md +2 -2
- package/agents/documenter.md +1 -1
- package/agents/orchestrator.md +11 -0
- package/agents/plan-reviewer.md +1 -1
- package/agents/planner.md +1 -1
- package/agents/releaser.md +1 -1
- package/agents/security-auditor.md +1 -1
- package/bin/cli.js +60 -21
- package/bin/lib/bootstrap.js +16 -16
- package/bin/lib/doctor.js +1 -1
- package/bin/lib/hermes-profile-artifact.js +144 -0
- package/bin/lib/set-hermes-watchdog.js +173 -0
- package/bin/set-hermes-watchdog.js +26 -0
- package/docs/ARCHITECTURE.md +67 -15
- package/docs/agent-fleet-setup.md +13 -13
- package/docs/claude-code-coms-bridge.md +7 -1
- package/docs/coms-hermes-bridge.md +18 -8
- package/docs/getting-started.md +48 -0
- package/docs/hermes-watchdog-supervisor.md +140 -0
- package/docs/npm-install.md +21 -21
- package/docs/pi-extensions.md +7 -7
- package/docs/pi-setup.md +51 -47
- package/hermes/README.md +135 -19
- package/hermes/desktop-plugins/agent-fleet-herdr/plugin.js +1291 -0
- package/hermes/desktop-plugins/agent-fleet-herdr/presentation.js +672 -0
- package/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
- package/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
- package/hermes/plugins/agent-fleet-herdr/dashboard/activity.py +770 -0
- package/hermes/plugins/agent-fleet-herdr/dashboard/coms_registry.py +134 -0
- package/hermes/plugins/agent-fleet-herdr/dashboard/coms_send.py +350 -0
- package/hermes/plugins/agent-fleet-herdr/dashboard/herdr_source.py +193 -0
- package/hermes/plugins/agent-fleet-herdr/dashboard/manifest.json +4 -0
- package/hermes/plugins/agent-fleet-herdr/dashboard/plugin_api.py +444 -0
- package/hermes/plugins/agent-fleet-herdr/dashboard/sessions.py +205 -0
- package/hermes/plugins/agent-fleet-herdr/dashboard/tasks.py +300 -0
- package/hermes/plugins/agent-fleet-herdr/dashboard/watch.py +819 -0
- package/hermes/plugins/agent-fleet-herdr/plugin.yaml +8 -0
- package/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +139 -0
- package/hermes/plugins/agent-fleet-monitor/dashboard/dist/index.js +10 -0
- package/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
- package/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
- package/hermes/skills/hub-watchdog/SKILL.md +76 -0
- package/hermes/skills/hub-watchdog/manifest.json +1 -0
- package/hermes/skills/hub-watchdog/scripts/watchdog.py +249 -0
- package/hermes/skills/hub-watchdog/scripts/watchdog_actions.py +124 -0
- package/hermes/skills/hub-watchdog/scripts/watchdog_contract.py +76 -0
- package/hermes/skills/hub-watchdog/scripts/watchdog_delivery.py +10 -0
- package/hermes/skills/hub-watchdog/scripts/watchdog_engine.py +128 -0
- package/hermes/skills/hub-watchdog/scripts/watchdog_judgment.py +41 -0
- package/hermes/skills/hub-watchdog/scripts/watchdog_recovery.py +103 -0
- package/hermes/skills/hub-watchdog/scripts/watchdog_state.py +163 -0
- package/hermes/skills/hub-watchdog/scripts/watchdog_transport.py +138 -0
- package/hooks/coms-stop-hook.mjs +12 -1
- package/package.json +11 -2
- package/references/fleet-coordination-patterns.md +2 -2
- package/scripts/coms-claude-bridge.ts +154 -39
- package/scripts/fleet.ts +9 -1
- package/scripts/hermes-watchdog-capability-probe.ts +45 -0
- package/scripts/lib/claude-bridge-core.ts +65 -0
- package/scripts/lib/coms-envelope.ts +44 -1
- package/scripts/lib/hermes-monitor-events.ts +1 -0
- package/scripts/lib/monitor-env.ts +120 -0
- package/scripts/team-snapshot.ts +1 -1
- package/scripts/team-up.ts +10 -1
- package/skills/browser-testing-with-devtools/SKILL.md +1 -1
- package/skills/compound-learning/SKILL.md +3 -3
- package/skills/guided-workspace-setup/SKILL.md +16 -14
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-cap.test.py +0 -15
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-discovery.test.py +0 -19
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-envelope.test.py +0 -13
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-forged-owner.test.py +0 -11
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-lease-list.test.py +0 -9
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-multihub.test.py +0 -17
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-output.test.py +0 -34
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter.test.py +0 -39
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/plugin-api-validation.test.py +0 -12
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/review-live-wiring.red.test.py +0 -22
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-cap.test.py +0 -15
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-discovery.test.py +0 -19
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-envelope.test.py +0 -13
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-forged-owner.test.py +0 -11
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-lease-list.test.py +0 -9
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-multihub.test.py +0 -17
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-output.test.py +0 -34
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter.test.py +0 -39
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/plugin-api-validation.test.py +0 -12
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/review-live-wiring.red.test.py +0 -22
- /package/.pi/prompts/{build.md → af-build.md} +0 -0
- /package/.pi/prompts/{code-simplify.md → af-code-simplify.md} +0 -0
- /package/.pi/prompts/{plan.md → af-plan.md} +0 -0
- /package/.pi/prompts/{review.md → af-review.md} +0 -0
- /package/.pi/prompts/{set-hermes-telegram.md → af-set-hermes-telegram.md} +0 -0
- /package/.pi/prompts/{ship.md → af-ship.md} +0 -0
- /package/.pi/prompts/{spec.md → af-spec.md} +0 -0
- /package/.pi/prompts/{test.md → af-test.md} +0 -0
package/docs/ARCHITECTURE.md
CHANGED
|
@@ -13,7 +13,8 @@ the runtime responsibilities and where each module lives in the repository.
|
|
|
13
13
|
| **coms** | Peer communication protocol/data plane — envelope-based P2P messaging between agents | `.pi/harnesses/coms/`, `scripts/lib/coms-envelope.ts`, `scripts/coms-cli.ts` |
|
|
14
14
|
| **Claude Code bridge** | Makes an interactive Claude Code pane a bidirectional coms peer | `scripts/coms-claude-bridge.ts`, `hooks/coms-stop-hook.mjs`, `skills/peer-coms/` — see [claude-code-coms-bridge.md](claude-code-coms-bridge.md) |
|
|
15
15
|
| **Hermes bridge** | Remote human control — relays hub questions to Telegram, races phone vs. local answers, conductor/liaison skills | `scripts/coms-hermes-bridge.ts`, `.pi/harnesses/ask-user-remote/`, `hermes/skills/` — see [coms-hermes-bridge.md](coms-hermes-bridge.md) |
|
|
16
|
-
| **Hermes local monitor transport** | Local, authenticated
|
|
16
|
+
| **Hermes local monitor transport** | Local, authenticated monitor contract for Hub-owned task generations; consumers supply their own presentation | `.pi/harnesses/agent-hub/monitor-*.ts`, `.pi/harnesses/lib/hermes-monitor-{model,store,registry,socket}.ts` (with compatibility re-exports under `scripts/lib/`) — see [Hermes artifacts](../hermes/README.md#local-agent-hub-monitor-integration) and [watchdog limits](hermes-watchdog-supervisor.md) |
|
|
17
|
+
| **Hermes Desktop plugin** (`agent-fleet-herdr`) | Fleet observability surface — read-only panel of every live session joined from the coms registry, herdr presence, agent transcripts, and the monitor transport; `focus` and subagent `cancel` are its only write doors | `hermes/desktop-plugins/agent-fleet-herdr/` (Electron pane), `hermes/plugins/agent-fleet-herdr/dashboard/` (FastAPI backend), installed by `scripts/install-hermes-plugin.sh` — see [hermes-desktop-plugins.md](hermes-desktop-plugins.md) |
|
|
17
18
|
| **Codex remote-control conductor** | Experimental outbound-only, user-systemd-managed Android conductor; verified on Codex CLI 0.144.x | `scripts/codex-remote-control.ts`, `scripts/codex-conductor.ts`, `codex/CONDUCTOR.md`, `systemd/user/`; runtime under `~/.local/state/agent-fleet/codex-conductor/` — see [codex-remote-conductor.md](codex-remote-conductor.md) |
|
|
18
19
|
| **Skill library** | Lifecycle workflows and quality gates every agent follows | `skills/` (native) + `vendor/agent-skills-upstream/skills/` (vendored) — see [UPSTREAM-SKILLS.md](UPSTREAM-SKILLS.md) |
|
|
19
20
|
| **Personas** | Reusable specialist definitions, transformed per harness | `agents/`, `bin/lib/transform-persona.js` |
|
|
@@ -96,12 +97,20 @@ The hub enforces per-user-turn budgets in code (`run-budget.js`): `fast`/`standa
|
|
|
96
97
|
modes cap `dispatch_agent` calls, `spawn_research` calls, and wall clock per turn, set the
|
|
97
98
|
per-run deadline above, and control nested delegation. Exhausted budgets make the dispatch
|
|
98
99
|
tools refuse with "summarize and ask the user"; a new user message opens a fresh window.
|
|
99
|
-
Specialist context pressure is measured over input + cacheRead + cacheWrite
|
|
100
|
-
|
|
101
|
-
|
|
102
|
-
|
|
100
|
+
Specialist context pressure is measured over input + cacheRead + cacheWrite against **that
|
|
101
|
+
agent's own** model window, resolved from pi's model registry with the source recorded
|
|
102
|
+
(`context-window.js`) — measuring a 49k local model against the dispatcher's window is what
|
|
103
|
+
made readings like "315%" unactionable; anything over 100% now emits a one-time diagnostic
|
|
104
|
+
naming the window and where it came from. Specialist sessions are recycled (fresh spawn
|
|
105
|
+
instead of `-c` resume) after `session-recycle-runs` runs, at ≥60% measured context, and
|
|
106
|
+
unconditionally at a full window; a resumed session whose *projected* prompt would overflow
|
|
107
|
+
is recycled before the spawn rather than after the run. Requests to one provider are capped
|
|
108
|
+
per process (`provider-semaphore.js`: 2 in flight for `custom/*` by default, unlimited
|
|
109
|
+
elsewhere, `AGENT_HUB_PROVIDER_LIMITS` to override) — the cap is per level of the delegation
|
|
110
|
+
tree, and a nested spawn reuses its parent's permit so it can never wait on its own ancestor.
|
|
111
|
+
Configured under `## agent-hub` (`mode`, `max-dispatches-per-turn`,
|
|
103
112
|
`max-research-per-turn`, `turn-wall-time-s`, `agent-turn-timeout-s`, `session-recycle-runs`);
|
|
104
|
-
switched live with `/hub-mode`.
|
|
113
|
+
switched live with `/af-hub-mode`.
|
|
105
114
|
|
|
106
115
|
On top of the mode sit three qualitative guardrails. **Task triage**: the dispatcher
|
|
107
116
|
classifies each turn via the `set_task_tier` tool (`trivial`/`small`/`feature`/`project`)
|
|
@@ -111,10 +120,14 @@ observed in-flight from the JSON event stream — deterministic rules (out-of-sc
|
|
|
111
120
|
against the declared `scope` globs, tool-call loops, consecutive failures, tool-call cap)
|
|
112
121
|
escalate to a one-shot cheap LLM judge whose DRIFTING/STUCK verdict terminates the run as
|
|
113
122
|
`drift_stop` (exit 125, partial output preserved); enabled per hub/agent/dispatch
|
|
114
|
-
(`watchdog` key, `/watchdog`, `watchdog` param).
|
|
115
|
-
|
|
123
|
+
(`watchdog` key, `/af-watchdog`, `watchdog` param). Two rules about scope: the session's
|
|
124
|
+
own `artifacts/`, `findings/`, and `delegations/` subtrees are implicitly in scope (the
|
|
125
|
+
deliverable protocol *orders* specialists to write there, and the judge is told so), and the
|
|
126
|
+
`scope` rule is non-terminal — it reports a drift advisory on the result and never stops a
|
|
127
|
+
run by itself, matching the post-run scope gate, which reverts nothing. **Dynamic teams**: `/af-agents-add`,
|
|
128
|
+
`/af-agents-drop`, `/af-agents-save` restructure the roster live (the system prompt rebuilds
|
|
116
129
|
every turn), and the gated `team_adjust` tool lets the dispatcher itself adjust the roster
|
|
117
|
-
outside fast mode, with user notification. `/hub-report` accounts each turn's dispatches,
|
|
130
|
+
outside fast mode, with user notification. `/af-hub-report` accounts each turn's dispatches,
|
|
118
131
|
tokens (billed = input + cacheRead + cacheWrite), recycles, drift stops, and refusals.
|
|
119
132
|
|
|
120
133
|
## Runtime stack (tools the fleet sits on)
|
|
@@ -126,7 +139,7 @@ flowchart TD
|
|
|
126
139
|
AF -->|control plane| HERDR["<b>herdr</b><br/>tiled peer workspaces,<br/>presence, snapshot/resume"]
|
|
127
140
|
AF -->|peer + install target| CC["<b>Claude Code</b><br/>bidirectional peer via<br/>the coms bridge"]
|
|
128
141
|
AF -->|install target| OC["<b>OpenCode</b><br/>skill-driven execution<br/>(AGENTS.md + skill tool)"]
|
|
129
|
-
AF -->|remote human| HERMES["<b>Hermes</b><br/>hub questions relayed
|
|
142
|
+
AF -->|remote human| HERMES["<b>Hermes</b><br/>hub questions relayed to your phone,<br/>plus the Desktop fleet panel"]
|
|
130
143
|
AF -->|outbound remote delegation| CODEX["<b>Codex Remote Control</b><br/>Android-approved calls to<br/>listed coms peers (experimental)"]
|
|
131
144
|
```
|
|
132
145
|
|
|
@@ -140,7 +153,7 @@ These are the external systems Agent Fleet assumes or integrates with — not np
|
|
|
140
153
|
| **[herdr](https://herdr.dev)** | Workspace control plane: tiled peer panes, presence push events, team snapshot/resume | Yes for team mode (`just fleet team`); optional for `just fleet hub` |
|
|
141
154
|
| **[Claude Code](https://docs.anthropic.com/en/docs/claude-code)** | First-class peer via the [coms bridge](claude-code-coms-bridge.md); also a supported install target for skills/personas | Optional peer / alternate harness |
|
|
142
155
|
| **[OpenCode](https://opencode.ai)** | Skill-driven execution target (`AGENTS.md` + `skill` tool); `af-*` slash commands | Optional alternate harness |
|
|
143
|
-
| **Hermes** | Remote human-in-the-loop (Telegram relay for hub questions
|
|
156
|
+
| **Hermes** | Remote human-in-the-loop (Telegram relay for hub questions — [coms-hermes-bridge](coms-hermes-bridge.md)) and the Desktop fleet panel ([hermes-desktop-plugins](hermes-desktop-plugins.md), needs v0.19.0+ and the Desktop app) | Optional |
|
|
144
157
|
| **Codex CLI + ChatGPT Android** | Experimental outbound remote-control conductor on supported `0.144.x`; requires Node `22.6+`, user systemd, interactive pairing, and per-command mobile approvals — [runbook](codex-remote-conductor.md) | Optional / revalidate after minor-version or mobile-client changes |
|
|
145
158
|
| **[addyosmani/agent-skills](https://github.com/addyosmani/agent-skills)** | Upstream skill library (manually vendored) | Bundled (vendored) |
|
|
146
159
|
| **[disler/pi-vs-claude-code](https://github.com/disler/pi-vs-claude-code)** | Source inspiration / MIT port origin for pi harnesses | Design lineage (ported in-repo) |
|
|
@@ -179,6 +192,32 @@ packages/hermes-bridge/ # future Hermes integration package
|
|
|
179
192
|
- **Thin dispatcher context.** Nothing lands persistently in the dispatcher's
|
|
180
193
|
context if it can live on disk or in a one-line status. Research findings,
|
|
181
194
|
the Verification Contract ledger, and team snapshots are all disk-first.
|
|
195
|
+
- **A harness fault must never look like a specialist fault.** The hub passes
|
|
196
|
+
`--session <file>` on every run, so one corrupt session file used to fail a
|
|
197
|
+
persona in ~1s with no output — indistinguishable from a bad agent, and
|
|
198
|
+
unrecoverable by drop + re-add. Unusable session files are now validated and
|
|
199
|
+
quarantined (`session-health.js`) with the reset named in the result. Same rule
|
|
200
|
+
for the return contract: a report the parser cannot read gets one cheap
|
|
201
|
+
read-only extraction pass (`return-extract.js`) before its assertions are
|
|
202
|
+
written off as unproven, and extracted evidence is always labelled as weaker
|
|
203
|
+
than declared evidence. The converse also holds: a run that errored or timed
|
|
204
|
+
out writes to `artifacts/failures/`, never `returns/` — an error stub filed
|
|
205
|
+
as a return reads as a specialist verdict and gets acted on as one.
|
|
206
|
+
- **A pool status field beats reading the screen.** `coms_list` publishes each
|
|
207
|
+
peer's `pane_id` and `status` (`idle`/`working`/`booting`), and
|
|
208
|
+
`herdr_spawn_peer` waits for the peer to register and returns `peer_ready`
|
|
209
|
+
rather than a bare pane id. A spawned peer boots idle and does nothing until
|
|
210
|
+
addressed, so peers spawned and never sent to are named at turn end and in
|
|
211
|
+
`/af-hub-report` (`spawned-peers.js`); closing stays the human's call.
|
|
212
|
+
- **A declared requirement carries its origin.** Every assertion in the ledger
|
|
213
|
+
names its source (`assertion-ledger.js`), and the open ledger is soft-capped
|
|
214
|
+
at 8 — an id nobody can trace back to a plan line costs a dispatch and an
|
|
215
|
+
ASK_USER cycle to re-derive.
|
|
216
|
+
- **Pre-flight validation is free.** Anything the hub can reject before spawning
|
|
217
|
+
— an unresolvable artifact path, an unknown research persona — is refused
|
|
218
|
+
without spending a turn-budget slot. Artifact paths also resolve across
|
|
219
|
+
artifact kinds when the name is unique, since the hub writes every auto-return
|
|
220
|
+
under `returns/` while dispatchers reasonably guess `reviews/`.
|
|
182
221
|
- **Herdr owns panes, presence, and lifecycle; coms owns messages.** Fleet
|
|
183
222
|
recipes hard-require a running herdr server and refuse with an actionable
|
|
184
223
|
message otherwise; non-fleet recipes never touch herdr.
|
|
@@ -187,10 +226,23 @@ packages/hermes-bridge/ # future Hermes integration package
|
|
|
187
226
|
the fleet core stays agent-agnostic. Hermes remains the inbound `ask_user`/
|
|
188
227
|
Telegram route; the experimental Codex conductor is outbound-initiated only,
|
|
189
228
|
approval-gated, and restricted to listed peers through the validated wrapper.
|
|
190
|
-
- **Hermes monitor presentation is outside the fleet core.** Agent Fleet
|
|
191
|
-
|
|
192
|
-
|
|
193
|
-
|
|
229
|
+
- **Hermes monitor presentation is outside the fleet core.** Agent Fleet exposes owner-only
|
|
230
|
+
local monitor operations for Hub-owned state; a consumer owns its UI and lifecycle. The
|
|
231
|
+
worktree contains additive monitor/event/invoke code, but that implementation and its local
|
|
232
|
+
tests are not proof of a durable external identity or live delivery contract. `invoke`, where
|
|
233
|
+
available, is Hub-owned and queues dispatcher work rather than exposing tools directly.
|
|
234
|
+
- **Packaged Hermes source is opt-in, never auto-installed.** The npm tarball carries the
|
|
235
|
+
`hub-watchdog` skill (`hermes/skills/`) plus the backend and Desktop monitor plugin source
|
|
236
|
+
(`hermes/plugins/`, `hermes/desktop-plugins/`) as runtime-only source. Shipping that source
|
|
237
|
+
makes it available to an operator; installing it into a Hermes profile is always an explicit
|
|
238
|
+
action through `agent-fleet set-hermes-watchdog` (skill) or the consumer's own flow (plugins).
|
|
239
|
+
Nothing is enabled, launched, or configured by installing the package.
|
|
240
|
+
- **Watchdog delivery is capability-gated and currently unproven.** No checked-in
|
|
241
|
+
Gate O live artifact proves Hermes origin identity, updates, reconnect, or two-chat isolation,
|
|
242
|
+
so its supported posture is journal-only/dormant: no delivery, steering, or surgical use. It
|
|
243
|
+
never manages services, gateways, Herdr, or shell commands. Local runtime evidence — including
|
|
244
|
+
a real foreground watcher against a disposable Hub UDS — is `synthetic-local` and proves none of
|
|
245
|
+
those capabilities; see [the watchdog runbook](hermes-watchdog-supervisor.md).
|
|
194
246
|
- **External conductor contracts are advisory.** Pi damage-control wraps Pi
|
|
195
247
|
tool calls, not Hermes or Codex processes; human approvals and their
|
|
196
248
|
contracts reduce risk but do not provide an OS command allowlist.
|
|
@@ -38,7 +38,7 @@ it here, and the reader picks it up.
|
|
|
38
38
|
built-in default.
|
|
39
39
|
- **Validation.** Because an unknown section or key silently falls back to the
|
|
40
40
|
default, typos are invisible at runtime. `agent-fleet doctor` (and the
|
|
41
|
-
|
|
41
|
+
runtime's Agent Fleet doctor command) validates the file — unknown sections,
|
|
42
42
|
unknown keys in known sections, invalid values for the mechanically parsed
|
|
43
43
|
`agent-hub` keys, missing `rules:` folders, and unset `## env` vars — as
|
|
44
44
|
**advisory, warn-only findings**; it never edits the file.
|
|
@@ -91,29 +91,29 @@ override files keep working unchanged. When both sections are present their keys
|
|
|
91
91
|
with later lines winning.
|
|
92
92
|
|
|
93
93
|
The `rules:` and `docs:` keys are also read outside the harness: the `compound-learning`
|
|
94
|
-
skill (and the `/compound`
|
|
94
|
+
skill (and the `/compound` Claude Code / `/af-compound` OpenCode commands built on it) resolves them as the
|
|
95
95
|
targets an end-of-session compound pass writes lessons to.
|
|
96
96
|
|
|
97
97
|
| Key | Default | Meaning |
|
|
98
98
|
|-----|---------|---------|
|
|
99
99
|
| `language` | `English` | User-facing language the dispatcher uses for every `ask_user` question, every `context` field, and every summary. Specialist task strings always stay in English regardless. |
|
|
100
100
|
| `persona-gate` | `off` | When `on`, blocks input at session start until an orchestrator persona is picked. |
|
|
101
|
-
| `model.<persona>` | persona frontmatter `model:` | Replaces the named persona's default model for this project (a full pi model spec). |
|
|
102
|
-
| `models.<persona>` | persona frontmatter `models:` | Replaces the named persona's model-candidate list for `/agent-model` and `/models` profiles (comma-separated pi model specs). |
|
|
103
|
-
| `thinking.<persona>` | persona frontmatter `thinking:` | Replaces the named persona's pi `--thinking` reasoning level for this project: one of `off`, `minimal`, `low`, `medium`, `high`, `xhigh`. Switchable at runtime with `/agent-model-thinking <persona>`. An invalid value is ignored with a session-start warning. |
|
|
104
|
-
| `subagents.<persona>.<role>` | persona frontmatter `subagents:` | Replaces or adds one delegate sub-role for this project: `<model>[, tools=<caps>]`. Other declared roles keep their frontmatter values. |
|
|
101
|
+
| `model.<persona>` | persona frontmatter `model:` | Replaces the named persona's default model for this project (a full pi model spec). If the override reports a model/provider error or aborted request before producing text or starting a tool (including a local-model memory-limit failure), agent-hub restores the child session and retries once with the original frontmatter model; it does not fallback after work starts, cancellation, timeout, drift stop, or process-spawn failure. |
|
|
102
|
+
| `models.<persona>` | persona frontmatter `models:` | Replaces the named persona's model-candidate list for `/af-agent-model` and `/af-models` profiles (comma-separated pi model specs). |
|
|
103
|
+
| `thinking.<persona>` | persona frontmatter `thinking:` | Replaces the named persona's pi `--thinking` reasoning level for this project: one of `off`, `minimal`, `low`, `medium`, `high`, `xhigh`. Switchable at runtime with `/af-agent-model-thinking <persona>`. An invalid value is ignored with a session-start warning. |
|
|
104
|
+
| `subagents.<persona>.<role>` | persona frontmatter `subagents:` | Replaces or adds one delegate sub-role for this project: `<model>[, tools=<caps>]`. Other declared roles keep their frontmatter values. Existing roles retain their original frontmatter model as the same one-shot, pre-work-only runtime fallback; model-only overrides retain the declared tool cap. |
|
|
105
105
|
| `delegate-depth.<persona>` | persona frontmatter `delegate_depth:` (default/max 1) | Replaces the persona's delegation depth budget: `0` makes its delegate tool refuse (delegation off for this project), `1` lets it spawn terminal children. Values above 1 are clamped to 1; children at remaining depth 0 do not receive delegate tooling. |
|
|
106
106
|
| `rules` | none | Comma-separated repo-relative folders holding the project's own rule files (HOW — implementation patterns the work must comply with). Resolution is **index-first**: when a folder has a top-level `README.md`/`index.md`, personas read it first and follow its loading manifest (session bundles, conditional-load lists) instead of bulk-reading the tree; a folder without an index is searched **recursively** through all subfolders. The harness tells every dispatched specialist where the rules live and how to resolve them; the planner and code-reviewer personas read the relevant rules, validate their subject against them, and pass them on (cited in plan acceptance criteria / handed to delegate sub-reviewers). Missing folders produce a session-start warning. |
|
|
107
107
|
| `docs` | none | Comma-separated repo-relative documentation **entry points** (WHAT/WHY — architecture, standards, decisions): canonical files (e.g. `Docs/AGENTS.md`) or doc folders (personas start from a folder's `README.md`/index). Unlike `rules`, docs orient rather than bind: every dispatched specialist and research helper is told to read the entry points relevant to its task and follow their links instead of bulk-reading doc trees; the code-reviewer flags changes that alter documented behavior without a doc update; the documenter treats the entry points and the trees they link as the docs it maintains. Missing paths produce a session-start warning. |
|
|
108
|
-
| `research-keep` | `4` | How many **finished** manual/persona research helpers the hub retains (LRU by finish time) so they stay resumable via `/agents-cont rN`; older ones are pruned along with their session files. `all` disables the cap. Auto-research pipe helpers (spawned for `NEEDS_RESEARCH:` pauses) are always pruned as soon as they finish — their findings persist as files under `.pi/agent-sessions/findings/`. Running helpers are never pruned. An invalid value is ignored with a session-start warning. |
|
|
108
|
+
| `research-keep` | `4` | How many **finished** manual/persona research helpers the hub retains (LRU by finish time) so they stay resumable via `/af-agents-cont rN`; older ones are pruned along with their session files. `all` disables the cap. Auto-research pipe helpers (spawned for `NEEDS_RESEARCH:` pauses) are always pruned as soon as they finish — their findings persist as files under `.pi/agent-sessions/findings/`. Running helpers are never pruned. An invalid value is ignored with a session-start warning. |
|
|
109
109
|
| `recon-search-timeout-s` | `120` | Parent-side deadline, in seconds, for each `read`, `grep`, `find`, or `ls` call made by a native research helper or nested delegate child. Accepts an integer `1`–`3600` or `off`; invalid input warns and falls back to `120`. This is **not** an agent/turn deadline: non-tool work can run indefinitely. On timeout the hub returns `tool_timeout` with call metadata, sends SIGTERM to its owned process group, escalates to SIGKILL after a finite grace period, and settles even if the child never closes or a descendant holds a pipe. If that bounded cleanup cannot confirm child/process-group death, the metadata reports `terminationConfirmed: false`; this prevents a parent hang but may indicate an uninterruptible OS-level process needing operator attention. |
|
|
110
|
-
| `mode` | `standard` | Execution mode for the hub's per-turn budgets: `fast` (single-specialist path, no nested delegation, assertion ledger optional), `standard` (batched execution with moderate budgets), or `strict` (full Verification Contract with wide budgets). Budgets are per **user turn** — exhausted budgets make `dispatch_agent`/`spawn_research` refuse with "summarize and ask the user"; the next user message opens a fresh window. Switchable live with `/hub-mode`. |
|
|
110
|
+
| `mode` | `standard` | Execution mode for the hub's per-turn budgets: `fast` (single-specialist path, no nested delegation, assertion ledger optional), `standard` (batched execution with moderate budgets), or `strict` (full Verification Contract with wide budgets). Budgets are per **user turn** — exhausted budgets make `dispatch_agent`/`spawn_research` refuse with "summarize and ask the user"; the next user message opens a fresh window. Switchable live with `/af-hub-mode`. |
|
|
111
111
|
| `max-dispatches-per-turn` | mode default (2/8/24) | `dispatch_agent` calls allowed per user turn. Positive integer or `off` (unlimited). |
|
|
112
|
-
| `max-research-per-turn` | mode default (1/4/12) | `spawn_research` calls allowed per user turn (the auto-research pipe and the `/research` command are exempt). Positive integer or `off`. |
|
|
112
|
+
| `max-research-per-turn` | mode default (1/4/12) | `spawn_research` calls allowed per user turn (the auto-research pipe and the `/af-research` command are exempt). Positive integer or `off`. |
|
|
113
113
|
| `turn-wall-time-s` | mode default (900/3600/14400) | Wall-clock budget, in seconds, per user turn; once exceeded, further dispatch/research calls refuse. Positive integer or `off`. |
|
|
114
114
|
| `agent-turn-timeout-s` | mode default (600/1800/off) | Whole-run deadline, in seconds, for each spawned specialist, research helper, and nested delegate child (unlike `recon-search-timeout-s`, this bounds the entire run). On expiry the run terminates as `turn_timeout` (exit 124) with partial output preserved. Positive integer or `off`. |
|
|
115
115
|
| `session-recycle-runs` | mode default (3/5/5) | Recycle a specialist's accumulated session (fresh spawn instead of `-c` resume) after this many resumed runs. Context is also always recycled at ≥60% measured context (input + cacheRead + cacheWrite). Positive integer or `off` (context threshold still applies). |
|
|
116
|
-
| `watchdog` | `auto` | Drift watchdog default for dispatched specialists: `auto`/`on` arm the in-flight rules (out-of-scope writes, tool-call loops, repeated failures, tool-call cap) with LLM-judge escalation; `off` disarms. Overridable live per hub (`/watchdog on\|off\|auto`), per agent (`/watchdog <agent> on\|off\|clear`), and per dispatch (the `watchdog` param). A DRIFTING/STUCK verdict terminates the run as `drift_stop` (exit 125) with partial output preserved. |
|
|
116
|
+
| `watchdog` | `auto` | Drift watchdog default for dispatched specialists: `auto`/`on` arm the in-flight rules (out-of-scope writes, tool-call loops, repeated failures, tool-call cap) with LLM-judge escalation; `off` disarms. Overridable live per hub (`/af-watchdog on\|off\|auto`), per agent (`/af-watchdog <agent> on\|off\|clear`), and per dispatch (the `watchdog` param). A DRIFTING/STUCK verdict terminates the run as `drift_stop` (exit 125) with partial output preserved. |
|
|
117
117
|
| `watchdog-judge-model` | researcher persona's model | pi model spec for the one-shot drift judge (e.g. `openai-codex/gpt-5.3-codex-spark`). Falls back to the researcher persona's resolved model, then the dispatcher's. |
|
|
118
118
|
|
|
119
119
|
Example — switch the dispatcher to Bulgarian, pin the builder to sonnet, raise the
|
|
@@ -152,7 +152,7 @@ required: APP_TEST_ADMIN_USER, APP_TEST_ADMIN_PASS, AZURE_SPEECH_KEY
|
|
|
152
152
|
```
|
|
153
153
|
|
|
154
154
|
No skill or harness loads this section. Its only reader is `agent-fleet doctor`
|
|
155
|
-
(and
|
|
155
|
+
(and the runtime's Agent Fleet doctor command), which warns when a declared name is neither set in
|
|
156
156
|
the environment nor declared in the workspace root `.env`.
|
|
157
157
|
|
|
158
158
|
### Per-peer env files (`env_file:` in peers.yaml)
|
|
@@ -243,12 +243,12 @@ available). The reader differs by runtime: pi's harness parses its YAML, while
|
|
|
243
243
|
| pi | `.pi/agents/teams.yaml` | via the `agent-hub` harness (no `/orchestrate`) |
|
|
244
244
|
|
|
245
245
|
Switch teams at runtime with `/orchestrate <team> "<task>"` (parallel of pi's
|
|
246
|
-
`/agents-team`); use `/orchestrate team=<name> <task>` to disambiguate when the
|
|
246
|
+
`/af-agents-team`); use `/orchestrate team=<name> <task>` to disambiguate when the
|
|
247
247
|
task text starts with a word that collides with a team key.
|
|
248
248
|
|
|
249
249
|
**Guided-setup behaviour.** `guided-workspace-setup` offers `/orchestrate`
|
|
250
250
|
**`★`-recommended** for claude-code + opencode (hidden for pi via the existing
|
|
251
|
-
source-availability filter — there is no `.pi/prompts/orchestrate.md`), and
|
|
251
|
+
source-availability filter — there is no `.pi/prompts/af-orchestrate.md`), and
|
|
252
252
|
installs the agent's `orchestrate-teams.yaml` as a **companion** of the command
|
|
253
253
|
(a user-edited config is preserved on uninstall, never silently clobbered).
|
|
254
254
|
Two artifacts stay **claude-only**: the lifecycle **hooks** (they register into
|
|
@@ -91,7 +91,13 @@ Older releases used the ambiguous name-only path `~/.pi/coms/cli/<name>/`. If th
|
|
|
91
91
|
## Behavior notes
|
|
92
92
|
|
|
93
93
|
- **Serialization:** one prompt at a time per pane; queue depth shows in the peer's
|
|
94
|
-
agent card and the herdr sidebar (
|
|
94
|
+
agent card and the herdr sidebar (`q<depth>`).
|
|
95
|
+
- **Presence:** the bridge annotates its pane through the shared `HerdrPresence`
|
|
96
|
+
(same dialect negotiation as pi peers — `tokens` on herdr >= 0.7.4, one latched
|
|
97
|
+
fallback to `custom_status`), so the pane carries `coms`/`proj` and the fleet panel
|
|
98
|
+
can join it to the registry entry. It writes the annotation ONLY, never
|
|
99
|
+
`pane.report_agent`: the pane's `agent_status` is herdr's own Claude detection and
|
|
100
|
+
the bridge polls it back as its turn-completion signal.
|
|
95
101
|
- **Blocked panes:** a Claude waiting on a permission prompt returns a readable error
|
|
96
102
|
envelope ("blocked on a permission prompt — a human must approve it") instead of
|
|
97
103
|
hanging until timeout.
|
|
@@ -1,5 +1,13 @@
|
|
|
1
1
|
# coms Hermes bridge
|
|
2
2
|
|
|
3
|
+
> The optional `hub-watchdog` is not this bridge and is not a coms conductor. It has no
|
|
4
|
+
> Herdr, shell, direct-tool, peer-delegation, service, or gateway authority. `hermes send --to`
|
|
5
|
+
> is an explicit destination mechanism, never origin-route evidence. Gate O has no checked-in
|
|
6
|
+
> live proof, so the supported watchdog posture is journal-only/dormant: no delivery,
|
|
7
|
+
> steering, cancellation, or recovery. It must not send an out-of-turn update, wake a chat, or
|
|
8
|
+
> fall back to another route. See [the watchdog runbook](hermes-watchdog-supervisor.md).
|
|
9
|
+
|
|
10
|
+
|
|
3
11
|
Protocol contract for the Hermes ⇄ pi `coms` bridge. The first implemented daemon is `scripts/coms-hermes-bridge.ts`, which registers a `user-remote` peer and turns coms prompt envelopes into Hermes/Telegram questions.
|
|
4
12
|
|
|
5
13
|
## Pieces
|
|
@@ -76,6 +84,8 @@ If options exist and the trimmed answer is a 1-based number for an option, the r
|
|
|
76
84
|
|
|
77
85
|
For a pending qid, cancel clears the timeout, removes the pending question, records terminal state `cancelled`, appends a `cancelled` log event, and sends a Telegram note: `✖ [HUB-Q:<qid>] The question was cancelled — it was answered from the console.` Cancel for a non-pending or invalid qid is a no-op after the envelope ack. A later answer file for a closed qid is treated as `late_answer`: logged, removed, and answered in Telegram with a polite ignored note; no response envelope is sent.
|
|
78
86
|
|
|
87
|
+
**Cancellation is local wait abandonment.** Cancelling a coms-backed run ends only this side's wait. The remote peer is not signalled and may keep working, so a `cancelled` state here is a statement about the local wait, never about the remote task. It follows that watchdog auto-recovery is forbidden for coms runs: no automatic retry, re-dispatch, retarget, or recovery invoke may follow a coms cancellation, and a cancelled coms run is never a recovery target. An explicit `hermes send --to <destination>` remains a destination-only mechanism chosen by a human; it is not evidence of an origin route and must not be used to "reply" to a cancelled run.
|
|
88
|
+
|
|
79
89
|
### Timeouts
|
|
80
90
|
|
|
81
91
|
The per-question remote timeout defaults to `PI_COMS_TIMEOUT_MS`, or `1800000` ms when unset/invalid; `--timeout <ms>` overrides it. On timeout, the bridge removes the pending question, records terminal state `timeout`, logs `timeout`, sends the Telegram note `⌛ [HUB-Q:<qid>] The question timed out after <ms>ms.`, and sends an error response envelope with error `no remote answer within <ms>ms` and `response: null`.
|
|
@@ -101,19 +111,19 @@ just fleet conductor hermes docs --dry-run # preview; no Herdr calls
|
|
|
101
111
|
|
|
102
112
|
The live recipe reuses `scripts/team-up.ts --conductor`: it creates a normal herdr workspace labeled `<worktree-tag>-conductor-<team>` (the tag is the last dot-segment of the checkout's basename, so the same team from a different worktree gets its own workspace), places a `conductor` pane running `hermes -p dev`, and tiles the chosen team beside it. Team peers keep their normal coms harness and herdr presence reporting, so they continue to show agent state in the sidebar; Hermes' own herdr-agent-state plugin is responsible for the conductor pane's state.
|
|
103
113
|
|
|
104
|
-
###
|
|
114
|
+
### Telegram bridge control command
|
|
105
115
|
|
|
106
|
-
The outbound `hermes send` path needs a configured Telegram channel but no skill. Full reply round-trip additionally needs Agent Fleet's `hub-liaison` skill in the profile that owns the running Telegram gateway.
|
|
116
|
+
The outbound `hermes send` path needs a configured Telegram channel but no skill. Full reply round-trip additionally needs Agent Fleet's `hub-liaison` skill in the profile that owns the running Telegram gateway. Pi and OpenCode use the namespaced command:
|
|
107
117
|
|
|
108
118
|
```text
|
|
109
|
-
/set-hermes-telegram status --profile default
|
|
110
|
-
/set-hermes-telegram install --profile default
|
|
111
|
-
/set-hermes-telegram install --profile default --force --restart
|
|
112
|
-
/set-hermes-telegram on 7883056502:1735 --profile default
|
|
113
|
-
/set-hermes-telegram off 7883056502:1735
|
|
119
|
+
/af-set-hermes-telegram status --profile default
|
|
120
|
+
/af-set-hermes-telegram install --profile default
|
|
121
|
+
/af-set-hermes-telegram install --profile default --force --restart
|
|
122
|
+
/af-set-hermes-telegram on 7883056502:1735 --profile default
|
|
123
|
+
/af-set-hermes-telegram off 7883056502:1735
|
|
114
124
|
```
|
|
115
125
|
|
|
116
|
-
|
|
126
|
+
Claude Code exposes the unprefixed `/set-hermes-telegram`; the arguments and backend are identical. The deterministic CLI can also be called directly with `agent-fleet set-hermes-telegram ...`.
|
|
117
127
|
|
|
118
128
|
#### `status` and profile resolution
|
|
119
129
|
|
package/docs/getting-started.md
CHANGED
|
@@ -18,6 +18,46 @@ Each skill is a Markdown file (`SKILL.md`) that describes a specific engineering
|
|
|
18
18
|
|
|
19
19
|
All three converge on the same `guided-workspace-setup` skill — they only differ in how the source files reach your workspace. None is being deprecated.
|
|
20
20
|
|
|
21
|
+
## Optional: see the fleet in Hermes Desktop
|
|
22
|
+
|
|
23
|
+
Once you are running more than one or two agents, `agent-fleet-herdr` gives you
|
|
24
|
+
a live panel of every Agent Fleet session — grouped by project, sorted so the
|
|
25
|
+
agent blocked on a human is at the top, with a toast when one gets stuck or
|
|
26
|
+
dies mid-work.
|
|
27
|
+
|
|
28
|
+
**You need:** Hermes v0.19.0+ with the Desktop app (`hermes` on `PATH`), this
|
|
29
|
+
repo checked out, and a fleet that has run at least once so
|
|
30
|
+
`~/.pi/coms/projects/` exists. [herdr](https://herdr.dev) is optional; without
|
|
31
|
+
it every row reads `unknown` instead of a live state.
|
|
32
|
+
|
|
33
|
+
```bash
|
|
34
|
+
# 1. link both halves into the profile and open the enable gate
|
|
35
|
+
scripts/install-hermes-plugin.sh agent-fleet-herdr # --profile dev / --copy / --dry-run
|
|
36
|
+
|
|
37
|
+
# 2. restart the HERMES DESKTOP APP
|
|
38
|
+
# (not `hermes gateway restart` — the pane talks to the gateway Desktop spawns for itself,
|
|
39
|
+
# and backend routes only mount when that app starts)
|
|
40
|
+
|
|
41
|
+
# 3. start a fleet and open the "Agent Fleet" tab
|
|
42
|
+
just fleet team default
|
|
43
|
+
```
|
|
44
|
+
|
|
45
|
+
Nothing about how you launch a fleet changes: the panel reads what the fleet
|
|
46
|
+
already writes (the coms registry, herdr presence, and each agent's own
|
|
47
|
+
transcript). It is read-only apart from `Focus pane` and cancelling a hub's
|
|
48
|
+
subagent. Uninstall with `scripts/install-hermes-plugin.sh agent-fleet-herdr
|
|
49
|
+
--uninstall`.
|
|
50
|
+
|
|
51
|
+

|
|
52
|
+
|
|
53
|
+
Full runbook — prerequisites, API, join rules, event kinds, the optional
|
|
54
|
+
Telegram fan-out, and the failure modes that all look like an empty panel:
|
|
55
|
+
**[hermes-desktop-plugins.md](hermes-desktop-plugins.md)**.
|
|
56
|
+
|
|
57
|
+
Separately, the [coms ⇄ Hermes bridge](coms-hermes-bridge.md) relays an agent's
|
|
58
|
+
`ask_user` question to Telegram and races your phone's answer against a local
|
|
59
|
+
one. The two are independent; you can run either without the other.
|
|
60
|
+
|
|
21
61
|
## Optional experimental Android conductor
|
|
22
62
|
|
|
23
63
|
Linux/pi fleet users can pair Codex Remote Control with ChatGPT Android and delegate one approval-gated task at a time to peers already running in a coms project. It is optional, supports only Codex CLI `0.144.x`, requires Node `22.6+` and user systemd, and does not replace Hermes as the inbound `ask_user` route.
|
|
@@ -174,6 +214,14 @@ The `/spec` and `/plan` commands create working artifacts (`SPEC.md`, `tasks/pla
|
|
|
174
214
|
- Update them when scope or decisions change.
|
|
175
215
|
- If your repo doesn’t want these files long‑term, delete them before merge or add the folder to `.gitignore` — the workflow doesn’t require them to be permanent.
|
|
176
216
|
|
|
217
|
+
## Contributor verification
|
|
218
|
+
|
|
219
|
+
The live Agent Fleet hub delegation smoke is intentionally outside the default unit suite. It uses the current checkout's `HEAD` and a deterministic local Pi fixture (no network/model call):
|
|
220
|
+
|
|
221
|
+
```bash
|
|
222
|
+
node --test scripts/agent-fleet-head-count-smoke.test.mjs
|
|
223
|
+
```
|
|
224
|
+
|
|
177
225
|
## Tips
|
|
178
226
|
|
|
179
227
|
1. **Start with spec-driven-development** for any non-trivial work
|
|
@@ -0,0 +1,140 @@
|
|
|
1
|
+
# Hermes watchdog supervisor
|
|
2
|
+
|
|
3
|
+
`hub-watchdog` is an optional, foreground Python skill packaged with Agent Fleet. It is a consumer of the local Agent Hub monitor transport, not a Hermes service, Herdr controller, coms conductor, or second dispatcher.
|
|
4
|
+
|
|
5
|
+
## Current boundary and Gate O
|
|
6
|
+
|
|
7
|
+
The repository has **no proven Hermes API for an invoking chat's identity, incremental updates, wake/reconnect, or session attachment**. `hermes send --to …` selects an explicit destination; it does not prove an origin route.
|
|
8
|
+
|
|
9
|
+
Gate O has no checked-in live proof. Therefore the supported operational posture is:
|
|
10
|
+
|
|
11
|
+
- `originDelivery=false`;
|
|
12
|
+
- local decision journaling only;
|
|
13
|
+
- no chat delivery, steering, cancellation, or recovery; and
|
|
14
|
+
- no claim that live origin delivery, A6, or live watchdog autonomy has passed.
|
|
15
|
+
|
|
16
|
+
The capability probe and local tests validate a proposed artifact shape and fail-closed behavior only. They do not establish a real Hermes capability. Do not supply a synthetic artifact, a fixture, or an explicit `--to` target as Gate O evidence.
|
|
17
|
+
|
|
18
|
+
## Safe out-of-turn policy
|
|
19
|
+
|
|
20
|
+
Run a watch only as an explicit, foreground operator action. It must not create a background service, wake a conversation, reopen a session, select a "last chat," redirect to another route, or act while the Hub is offline. Until Gate O is independently proven, any material event or deviation is recorded locally and nothing is sent or changed. Stop the foreground process to stop observation.
|
|
21
|
+
|
|
22
|
+
The watcher has no shell, PID-search, `pkill`, Herdr, gateway, service, direct Pi-tool, or peer-delegation authority. It does not replace the Hub's task ownership. Coms cancellation remains a local wait cancellation; a remote peer can continue, so it is never an automatic recovery target.
|
|
23
|
+
|
|
24
|
+
## Installed skill and source package
|
|
25
|
+
|
|
26
|
+
`hermes/skills/hub-watchdog/` is the packaged **source artifact**, and the npm tarball also carries the backend and Desktop monitor plugin source under `hermes/plugins/` and `hermes/desktop-plugins/`. Packaging makes that source available to the installer and to a consumer that chooses to use it; it neither installs anything into a Hermes profile nor enables, launches, or configures a watcher or plugin. Installation into a profile is always an explicit opt-in operator action. The repository does not provide a supported live Hermes origin adapter.
|
|
27
|
+
|
|
28
|
+
Python test modules, bytecode, caches, and the local scenario fixtures are excluded from the tarball; the shipped Python is runtime-only and needs no dependency beyond the standard library.
|
|
29
|
+
|
|
30
|
+
The installed skill manifest defaults and caps autonomy at `observe`. The Python entrypoint also lowers `steer` or `surgical` to `observe` when Gate O is not valid. These checks are defensive code paths, not evidence that those higher tiers are approved for use.
|
|
31
|
+
|
|
32
|
+
## Profile lifecycle
|
|
33
|
+
|
|
34
|
+
Use the deterministic controller or the matching guided command:
|
|
35
|
+
|
|
36
|
+
```bash
|
|
37
|
+
agent-fleet set-hermes-watchdog status --profile <profile>
|
|
38
|
+
agent-fleet set-hermes-watchdog install --profile <profile>
|
|
39
|
+
agent-fleet set-hermes-watchdog update --profile <profile>
|
|
40
|
+
agent-fleet set-hermes-watchdog uninstall --profile <profile>
|
|
41
|
+
```
|
|
42
|
+
|
|
43
|
+
`status` is read-only: it reports the resolved profile, whether that profile's gateway is running, the skill state (`missing`/`current`/`drifted`), the receipt state (`managed`/`unmanaged`/`drifted`), whether a watcher lock is active, and `originDelivery: false`. It writes nothing. `--dry-run` reports the write an `install`/`update` would make without making it.
|
|
44
|
+
|
|
45
|
+
`install` and `update` behave the same way and are chosen by intent:
|
|
46
|
+
|
|
47
|
+
| Skill state | Receipt state | Result |
|
|
48
|
+
| --- | --- | --- |
|
|
49
|
+
| missing | — | Atomic install plus a mode-0600 receipt |
|
|
50
|
+
| current | managed | No change |
|
|
51
|
+
| current | unmanaged | **Adopted**: the tree is re-fingerprinted and only the receipt is written |
|
|
52
|
+
| current | drifted | Refused; `--force` backs the tree up and reinstalls it |
|
|
53
|
+
| drifted | any | Refused; `--force` backs the tree up and replaces it |
|
|
54
|
+
|
|
55
|
+
Adoption is deliberately narrow: an unmanaged tree is adopted only when a fresh, symlink-free fingerprint exactly equals the packaged source at the moment of the write. An extra file, a symlink, an unsupported entry, or any drift is refused and left untouched — adoption never rewrites the tree it adopts, and never creates a backup.
|
|
56
|
+
|
|
57
|
+
`uninstall` removes only a `current`/`managed` tree by default, moving it to `backups/agent-fleet/` and deleting its receipt; anything else requires `--force`. It preserves `watchdog.json` and every journal. An active watcher lock is reported and never killed — stop the foreground process yourself first.
|
|
58
|
+
|
|
59
|
+
An install writes the profile's default configuration only when it is absent; it never overwrites an operator's edits.
|
|
60
|
+
|
|
61
|
+
The controller resolves the selected Hermes profile but does not start, stop, restart, or kill a gateway or watcher; change Hermes tools or permissions; send a test message; or manage Herdr. Use an explicit profile when automatic profile selection is not available.
|
|
62
|
+
|
|
63
|
+
The initial configuration written only when absent is:
|
|
64
|
+
|
|
65
|
+
```json
|
|
66
|
+
{
|
|
67
|
+
"schemaVersion": 1,
|
|
68
|
+
"autonomy": "observe",
|
|
69
|
+
"maximumAutonomy": "observe",
|
|
70
|
+
"surgicalAllowlist": [],
|
|
71
|
+
"originDelivery": "required",
|
|
72
|
+
"runtimeDir": null
|
|
73
|
+
}
|
|
74
|
+
```
|
|
75
|
+
|
|
76
|
+
Keep `autonomy` and `maximumAutonomy` at `observe` while Gate O is unproven. `runtimeDir: null` is not permission to scan runtime directories; a real watch invocation needs explicit validated monitor inputs.
|
|
77
|
+
|
|
78
|
+
## Running and stopping a watch
|
|
79
|
+
|
|
80
|
+
A watch is a foreground process you start and stop yourself:
|
|
81
|
+
|
|
82
|
+
```bash
|
|
83
|
+
python3 <profile>/skills/hub-watchdog/scripts/watchdog.py watch --invocation-json '<json>'
|
|
84
|
+
```
|
|
85
|
+
|
|
86
|
+
The invocation names the profile, the validated `profileKey`/`hubKey` namespace, the hub instance, the monitor runtime directory, and the private state and lock directories. It takes a single `watch.lock` per profile under the lock directory; a second watcher for the same profile fails closed with `watcher_locked` rather than sharing state.
|
|
87
|
+
|
|
88
|
+
Send `SIGINT` (Ctrl-C) to stop it. On exit the watcher releases `watch.lock`, closes its UDS clients and any long-poll waiter, and leaves the local journal in place. It never daemonizes, re-execs, or restarts itself, and there is no service unit to disable.
|
|
89
|
+
|
|
90
|
+
## Local monitor boundary
|
|
91
|
+
|
|
92
|
+
The Hub's owner-only UDS remains the source of task state. Existing monitor operations include bounded snapshot, task output, and exact-generation cancellation; `events` and `invoke` are additive on top of that baseline. Do not interpret implementation names, cursors, discovery fields, fixtures, or unit tests as a cross-process identity proof or a live watcher guarantee. A consumer must treat malformed discovery, ownership change, unavailable transport, and reconciliation uncertainty as stop conditions for action.
|
|
93
|
+
|
|
94
|
+
### `events` and `invoke` responses
|
|
95
|
+
|
|
96
|
+
`events` replays the Hub's bounded event journal from a caller-held cursor. A request names `afterSequence`, a `limit` of 1–100, and a `waitMs` long-poll window of 0–25000. Set a read timeout that covers the window you ask the Hub to hold, otherwise a quiet poll expires locally and looks like an outage:
|
|
97
|
+
|
|
98
|
+
```json
|
|
99
|
+
{"ok": true, "events": {"firstAvailableSequence": 1, "latestSequence": 4, "items": [], "timedOut": true}}
|
|
100
|
+
```
|
|
101
|
+
|
|
102
|
+
When the cursor is older than the retained window the Hub refuses it instead of silently skipping facts, and the consumer must reconcile from a fresh snapshot and resume from sequence 0:
|
|
103
|
+
|
|
104
|
+
```json
|
|
105
|
+
{"ok": false, "error": "cursor_too_old", "snapshotRequired": true, "firstAvailableSequence": 9, "latestSequence": 12}
|
|
106
|
+
```
|
|
107
|
+
|
|
108
|
+
`invoke` submits one typed request and returns an admission status, never a result of work:
|
|
109
|
+
|
|
110
|
+
```json
|
|
111
|
+
{"ok": true, "result": {"status": "accepted"}}
|
|
112
|
+
```
|
|
113
|
+
|
|
114
|
+
`status` is one of `accepted`, `duplicate`, `queue_full`, `stale_generation`, `owner_changed`, `already_terminal`, `idempotency_conflict`, `unsupported`, or `rejected`. `accepted` means the Hub queued a visible follow-up for its operator to act on; it does not mean anything ran. A duplicate `requestId` returns `duplicate` and adds no second follow-up; the same `requestId` with different parameters returns `idempotency_conflict`.
|
|
115
|
+
|
|
116
|
+
### Owner and profile mismatch
|
|
117
|
+
|
|
118
|
+
Identity is bound on every request: the configured profile key, hub instance, and owner must all equal what live discovery reports. A mismatch — a rolled-over owner, a different profile, a stale token — is a refusal, not a fallback. The watcher must rediscover the namespace and never reuse a previous owner's token or socket, and it must never search another profile's runtime tree. An accepted request is never re-driven across a rollover or restart.
|
|
119
|
+
|
|
120
|
+
The watchdog's local journal is a decision trace, not authoritative Hub history. It must not be used to infer a task's identity, completion, route, or delivery outcome beyond what the Hub has explicitly returned.
|
|
121
|
+
|
|
122
|
+
## Migration, rollback, and incident handling
|
|
123
|
+
|
|
124
|
+
The monitor additions are intended to remain additive: older snapshot/output/cancel consumers continue to be the compatibility baseline. A consumer written against snapshot/output/cancel keeps working unchanged and needs no migration — `events` and `invoke` are new request types on the same socket, and a Hub that does not implement them answers `unsupported` rather than failing the connection.
|
|
125
|
+
|
|
126
|
+
To move such a consumer onto `events`, take a bounded snapshot first, then poll `events` from sequence 0 and treat `cursor_too_old` as an instruction to re-snapshot and restart the cursor. Keep the snapshot path: it is the only recovery route after a retention gap, an ownership change, or a reconnect. Output cursors stay per-task and are not comparable to event sequences. There is no migration that converts historical output cursors into a proven global event identity, and no migration that creates a Hermes origin route.
|
|
127
|
+
|
|
128
|
+
To roll back watchdog use:
|
|
129
|
+
|
|
130
|
+
1. set the profile configuration to `observe` (or leave the default unchanged);
|
|
131
|
+
2. stop the foreground watcher with `SIGINT` and confirm `watch.lock` is gone; and
|
|
132
|
+
3. optionally run `uninstall` only after reviewing its status/backup behavior.
|
|
133
|
+
|
|
134
|
+
Rolling back to `observe` leaves the local journal intact and stops nothing else: the Hub keeps running, no task is cancelled, and no queued follow-up is withdrawn. Rollback is always to observe-and-journal, never to a different delivery route.
|
|
135
|
+
|
|
136
|
+
Do not delete a journal, lock, runtime directory, or profile tree to force recovery. Preserve suspect files for inspection. On a transport error, Gate O failure, owner/profile mismatch, ambiguous generation, or journal problem, leave the watcher stopped or journal-only; do not retry through Herdr, a gateway restart, a shell command, or coms.
|
|
137
|
+
|
|
138
|
+
## Checks and evidence
|
|
139
|
+
|
|
140
|
+
The focused checks currently cover the capability-artifact validator, installer lifecycle, packaging boundary, and a small foreground watcher fixture. They are useful regression checks, but they do not prove live Hermes delivery, origin identity, wake/reconnect, multi-chat isolation, steering, or surgical recovery. Those claims remain blocked pending a sanitized, human-reviewed disposable live artifact naming the actual Hermes API and observed behavior.
|