@chankov/agent-fleet 0.0.3 → 0.0.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude/commands/set-hermes-telegram.md +15 -0
- package/.claude/commands/setup-agent-fleet.md +1 -1
- package/.opencode/commands/af-set-hermes-telegram.md +15 -0
- package/.opencode/commands/af-setup-agent-fleet.md +1 -1
- package/.pi/agents/dispatch-policy.yaml +1 -1
- package/.pi/agents/peers.yaml +4 -4
- package/.pi/extensions/chrome-devtools-mcp/README.md +1 -1
- package/.pi/extensions/mcp-bridge/README.md +1 -1
- package/.pi/harnesses/agent-hub/README.md +223 -40
- package/.pi/harnesses/agent-hub/access-approval.ts +135 -0
- package/.pi/harnesses/agent-hub/delegate.ts +32 -9
- package/.pi/harnesses/agent-hub/drift-watchdog.js +165 -0
- package/.pi/harnesses/agent-hub/footer.ts +29 -0
- package/.pi/harnesses/agent-hub/helpers.ts +49 -0
- package/.pi/harnesses/agent-hub/index.ts +1037 -246
- package/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
- package/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
- package/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
- package/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
- package/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
- package/.pi/harnesses/agent-hub/monitor-session-bridge.ts +11 -0
- package/.pi/harnesses/agent-hub/package.json +5 -4
- package/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
- package/.pi/harnesses/agent-hub/run-budget.js +155 -0
- package/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
- package/.pi/harnesses/agent-hub/spawn.ts +161 -94
- package/.pi/harnesses/agent-hub/version.ts +18 -0
- package/.pi/harnesses/ask-user-remote/README.md +1 -0
- package/.pi/harnesses/ask-user-remote/index.ts +36 -8
- package/.pi/harnesses/coms/README.md +15 -5
- package/.pi/harnesses/coms/index.ts +2 -0
- package/.pi/harnesses/coms/package.json +5 -4
- package/.pi/harnesses/coms/version.ts +18 -0
- package/.pi/harnesses/damage-control-continue/README.md +36 -35
- package/.pi/harnesses/damage-control-continue/index.ts +23 -9
- package/.pi/harnesses/damage-control-continue/package.json +5 -4
- package/.pi/harnesses/damage-control-continue/version.ts +18 -0
- package/.pi/harnesses/{damage-control/shared.ts → lib/damage-control-shared.ts} +20 -6
- package/.pi/harnesses/lib/hermes-monitor-herdr.ts +28 -0
- package/.pi/harnesses/lib/hermes-monitor-model.ts +9 -0
- package/.pi/harnesses/lib/hermes-monitor-registry.ts +6 -0
- package/.pi/harnesses/lib/hermes-monitor-socket.ts +118 -0
- package/.pi/harnesses/lib/hermes-monitor-store.ts +31 -0
- package/.pi/prompts/set-hermes-telegram.md +15 -0
- package/.pi/prompts/setup-agent-fleet.md +1 -1
- package/.versions/0.0.4/.claude/commands/build.md +44 -0
- package/.versions/0.0.4/.claude/commands/code-simplify.md +22 -0
- package/.versions/0.0.4/.claude/commands/design-agent.md +14 -0
- package/.versions/0.0.4/.claude/commands/doctor-agent-fleet.md +17 -0
- package/.versions/0.0.4/.claude/commands/orchestrate.md +112 -0
- package/.versions/0.0.4/.claude/commands/plan.md +16 -0
- package/.versions/0.0.4/.claude/commands/prime.md +22 -0
- package/.versions/0.0.4/.claude/commands/review.md +16 -0
- package/.versions/0.0.4/.claude/commands/setup-agent-fleet.md +25 -0
- package/.versions/0.0.4/.claude/commands/ship.md +72 -0
- package/.versions/0.0.4/.claude/commands/spec.md +15 -0
- package/.versions/0.0.4/.claude/commands/test.md +19 -0
- package/.versions/0.0.4/.claude/commands/webperf.md +32 -0
- package/.versions/0.0.4/.claude/orchestrate-teams.yaml +24 -0
- package/.versions/0.0.4/.opencode/commands/af-build.md +17 -0
- package/.versions/0.0.4/.opencode/commands/af-code-simplify.md +16 -0
- package/.versions/0.0.4/.opencode/commands/af-compound.md +16 -0
- package/.versions/0.0.4/.opencode/commands/af-design-agent.md +15 -0
- package/.versions/0.0.4/.opencode/commands/af-doctor-agent-fleet.md +17 -0
- package/.versions/0.0.4/.opencode/commands/af-orchestrate.md +112 -0
- package/.versions/0.0.4/.opencode/commands/af-plan.md +16 -0
- package/.versions/0.0.4/.opencode/commands/af-prime.md +22 -0
- package/.versions/0.0.4/.opencode/commands/af-review.md +15 -0
- package/.versions/0.0.4/.opencode/commands/af-setup-agent-fleet.md +15 -0
- package/.versions/0.0.4/.opencode/commands/af-ship.md +16 -0
- package/.versions/0.0.4/.opencode/commands/af-spec.md +16 -0
- package/.versions/0.0.4/.opencode/commands/af-test.md +21 -0
- package/.versions/0.0.4/.opencode/commands/af-webperf.md +32 -0
- package/.versions/0.0.4/.opencode/orchestrate-teams.yaml +24 -0
- package/.versions/0.0.4/.pi/agents/dispatch-policy.yaml +32 -0
- package/.versions/0.0.4/.pi/agents/model-profiles.yaml +20 -0
- package/.versions/0.0.4/.pi/agents/peers.yaml +146 -0
- package/.versions/0.0.4/.pi/agents/teams.yaml +39 -0
- package/.versions/0.0.4/.pi/damage-control-rules.yaml +297 -0
- package/.versions/0.0.4/.pi/extensions/agent-fleet-update-check/README.md +58 -0
- package/.versions/0.0.4/.pi/extensions/agent-fleet-update-check/index.ts +161 -0
- package/{.pi/harnesses/damage-control → .versions/0.0.4/.pi/extensions/agent-fleet-update-check}/package.json +1 -1
- package/.versions/0.0.4/.pi/extensions/btw/README.md +118 -0
- package/.versions/0.0.4/.pi/extensions/btw/index.ts +917 -0
- package/.versions/0.0.4/.pi/extensions/btw/package.json +6 -0
- package/.versions/0.0.4/.pi/extensions/btw/state.js +179 -0
- package/.versions/0.0.4/.pi/extensions/chrome-devtools-mcp/README.md +58 -0
- package/.versions/0.0.4/.pi/extensions/chrome-devtools-mcp/index.ts +92 -0
- package/.versions/0.0.4/.pi/extensions/chrome-devtools-mcp/package.json +6 -0
- package/.versions/0.0.4/.pi/extensions/compact-and-continue/README.md +42 -0
- package/.versions/0.0.4/.pi/extensions/compact-and-continue/index.ts +120 -0
- package/.versions/0.0.4/.pi/extensions/compact-and-continue/package.json +6 -0
- package/.versions/0.0.4/.pi/extensions/mcp-bridge/README.md +46 -0
- package/.versions/0.0.4/.pi/extensions/mcp-bridge/index.ts +206 -0
- package/.versions/0.0.4/.pi/extensions/mcp-bridge/package.json +6 -0
- package/.versions/0.0.4/.pi/extensions/package-lock.json +1143 -0
- package/.versions/0.0.4/.pi/extensions/package.json +9 -0
- package/.versions/0.0.4/.pi/extensions/pi-voice-stt/README.md +201 -0
- package/.versions/0.0.4/.pi/extensions/pi-voice-stt/config.ts +198 -0
- package/.versions/0.0.4/.pi/extensions/pi-voice-stt/examples/stt.json +35 -0
- package/.versions/0.0.4/.pi/extensions/pi-voice-stt/index.ts +248 -0
- package/.versions/0.0.4/.pi/extensions/pi-voice-stt/package.json +6 -0
- package/.versions/0.0.4/.pi/extensions/pi-voice-stt/providers.ts +214 -0
- package/.versions/0.0.4/.pi/extensions/pi-voice-stt/recorder.ts +158 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/README.md +798 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/access-approval.ts +135 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/artifacts.js +92 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/backend-policy.js +153 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/delegate.ts +386 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/drift-watchdog.js +165 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/evidence-rules.js +96 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/footer.ts +29 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/helpers.ts +214 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/index.ts +8045 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/monitor-session-bridge.ts +11 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/package.json +7 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/research-retention.js +34 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/return-contract.js +215 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/run-budget.js +155 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/scope-gate.js +103 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/spawn.ts +246 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/version.ts +18 -0
- package/.versions/0.0.4/.pi/harnesses/ask-user-remote/README.md +18 -0
- package/.versions/0.0.4/.pi/harnesses/ask-user-remote/index.ts +293 -0
- package/.versions/0.0.4/.pi/harnesses/ask-user-remote/race-core.js +106 -0
- package/.versions/0.0.4/.pi/harnesses/coms/README.md +92 -0
- package/.versions/0.0.4/.pi/harnesses/coms/index.ts +1745 -0
- package/.versions/0.0.4/.pi/harnesses/coms/package.json +7 -0
- package/.versions/0.0.4/.pi/harnesses/coms/version.ts +18 -0
- package/.versions/0.0.4/.pi/harnesses/damage-control-continue/README.md +117 -0
- package/.versions/0.0.4/.pi/harnesses/damage-control-continue/index.ts +536 -0
- package/.versions/0.0.4/.pi/harnesses/damage-control-continue/package.json +7 -0
- package/.versions/0.0.4/.pi/harnesses/damage-control-continue/version.ts +18 -0
- package/.versions/0.0.4/.pi/harnesses/lib/damage-control-shared.ts +197 -0
- package/.versions/0.0.4/.pi/harnesses/lib/herdr-client.ts +458 -0
- package/.versions/0.0.4/.pi/harnesses/lib/herdr-presence.ts +288 -0
- package/.versions/0.0.4/.pi/harnesses/package-lock.json +35 -0
- package/.versions/0.0.4/.pi/harnesses/package.json +9 -0
- package/.versions/0.0.4/.pi/prompts/build.md +24 -0
- package/.versions/0.0.4/.pi/prompts/code-simplify.md +22 -0
- package/.versions/0.0.4/.pi/prompts/doctor-agent-fleet.md +15 -0
- package/.versions/0.0.4/.pi/prompts/plan.md +16 -0
- package/.versions/0.0.4/.pi/prompts/review.md +16 -0
- package/.versions/0.0.4/.pi/prompts/setup-agent-fleet.md +27 -0
- package/.versions/0.0.4/.pi/prompts/ship.md +17 -0
- package/.versions/0.0.4/.pi/prompts/spec.md +15 -0
- package/.versions/0.0.4/.pi/prompts/test.md +19 -0
- package/.versions/0.0.4/.pi/skills/bowser/SKILL.md +145 -0
- package/.versions/0.0.4/.version +1 -0
- package/.versions/0.0.4/agents/architect.md +23 -0
- package/.versions/0.0.4/agents/bowser.md +26 -0
- package/.versions/0.0.4/agents/builder.md +53 -0
- package/.versions/0.0.4/agents/code-reviewer.md +205 -0
- package/.versions/0.0.4/agents/deep-researcher.md +31 -0
- package/.versions/0.0.4/agents/documenter.md +18 -0
- package/.versions/0.0.4/agents/orchestrator.md +54 -0
- package/.versions/0.0.4/agents/plan-reviewer.md +60 -0
- package/.versions/0.0.4/agents/planner.md +69 -0
- package/.versions/0.0.4/agents/releaser.md +24 -0
- package/.versions/0.0.4/agents/researcher.md +28 -0
- package/.versions/0.0.4/agents/security-auditor.md +166 -0
- package/.versions/0.0.4/agents/test-engineer.md +151 -0
- package/.versions/0.0.4/agents/web-debugger.md +42 -0
- package/.versions/0.0.4/agents/web-performance-auditor.md +192 -0
- package/.versions/0.0.4/codex/CONDUCTOR.md +148 -0
- package/.versions/0.0.4/docs/ARCHITECTURE.md +210 -0
- package/.versions/0.0.4/docs/agent-fleet-setup.md +366 -0
- package/.versions/0.0.4/docs/claude-code-coms-bridge.md +103 -0
- package/.versions/0.0.4/docs/codex-remote-conductor.md +170 -0
- package/.versions/0.0.4/docs/coms-hermes-bridge.md +121 -0
- package/.versions/0.0.4/docs/getting-started.md +183 -0
- package/.versions/0.0.4/docs/npm-install.md +337 -0
- package/.versions/0.0.4/docs/opencode-setup.md +248 -0
- package/.versions/0.0.4/docs/pi-extensions.md +288 -0
- package/.versions/0.0.4/docs/pi-setup.md +463 -0
- package/.versions/0.0.4/docs/skill-anatomy.md +150 -0
- package/.versions/0.0.4/hermes/README.md +228 -0
- package/.versions/0.0.4/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
- package/.versions/0.0.4/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-cap.test.py +15 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-discovery.test.py +19 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-envelope.test.py +13 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-forged-owner.test.py +11 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-lease-list.test.py +9 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-multihub.test.py +17 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-output.test.py +34 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +151 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter.test.py +39 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/plugin-api-validation.test.py +12 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/review-live-wiring.red.test.py +22 -0
- package/.versions/0.0.4/hermes/skills/hub-conductor/SKILL.md +84 -0
- package/.versions/0.0.4/hermes/skills/hub-liaison/SKILL.md +84 -0
- package/.versions/0.0.4/hooks/SIMPLIFY-IGNORE.md +90 -0
- package/.versions/0.0.4/hooks/coms-stop-hook.mjs +73 -0
- package/.versions/0.0.4/hooks/hooks.json +14 -0
- package/.versions/0.0.4/hooks/session-start.sh +74 -0
- package/.versions/0.0.4/hooks/simplify-ignore.sh +302 -0
- package/.versions/0.0.4/justfile +256 -0
- package/.versions/0.0.4/references/accessibility-checklist.md +160 -0
- package/.versions/0.0.4/references/definition-of-done.md +67 -0
- package/.versions/0.0.4/references/fleet-coordination-patterns.md +151 -0
- package/.versions/0.0.4/references/observability-checklist.md +91 -0
- package/.versions/0.0.4/references/orchestration-patterns.md +370 -0
- package/.versions/0.0.4/references/performance-checklist.md +153 -0
- package/.versions/0.0.4/references/prompting-patterns.md +380 -0
- package/.versions/0.0.4/references/security-checklist.md +179 -0
- package/.versions/0.0.4/references/testing-patterns.md +236 -0
- package/.versions/0.0.4/scripts/codex-conductor.ts +41 -0
- package/.versions/0.0.4/scripts/codex-remote-control.ts +167 -0
- package/.versions/0.0.4/scripts/coms-claude-bridge.ts +286 -0
- package/.versions/0.0.4/scripts/coms-cli.ts +484 -0
- package/.versions/0.0.4/scripts/coms-hermes-bridge.ts +403 -0
- package/.versions/0.0.4/scripts/hermes-monitor-capability-runner.ts +25 -0
- package/.versions/0.0.4/scripts/hermes-monitor-scenario.ts +7 -0
- package/.versions/0.0.4/scripts/lib/claude-bridge-core.ts +100 -0
- package/.versions/0.0.4/scripts/lib/codex-conductor.ts +88 -0
- package/.versions/0.0.4/scripts/lib/codex-remote-control.ts +480 -0
- package/.versions/0.0.4/scripts/lib/coms-envelope.ts +539 -0
- package/.versions/0.0.4/scripts/lib/fake-herdr-server.ts +88 -0
- package/.versions/0.0.4/scripts/lib/herdr-layout.ts +263 -0
- package/.versions/0.0.4/scripts/lib/hermes-bridge-core.ts +238 -0
- package/.versions/0.0.4/scripts/lib/hermes-monitor-herdr.ts +28 -0
- package/.versions/0.0.4/scripts/lib/hermes-monitor-model.ts +9 -0
- package/.versions/0.0.4/scripts/lib/hermes-monitor-registry.ts +6 -0
- package/.versions/0.0.4/scripts/lib/hermes-monitor-socket.ts +118 -0
- package/.versions/0.0.4/scripts/lib/hermes-monitor-store.ts +31 -0
- package/.versions/0.0.4/scripts/lib/persona-banner.ts +62 -0
- package/.versions/0.0.4/scripts/lib/spawn-stagger.ts +101 -0
- package/.versions/0.0.4/scripts/lib/team-project.ts +184 -0
- package/.versions/0.0.4/scripts/lib/team-snapshot.ts +147 -0
- package/.versions/0.0.4/scripts/peer-banner.ts +40 -0
- package/.versions/0.0.4/scripts/team-snapshot.ts +238 -0
- package/.versions/0.0.4/scripts/team-up.ts +333 -0
- package/.versions/0.0.4/skills/_internal/grilling.md +11 -0
- package/.versions/0.0.4/skills/browser-testing-with-devtools/SKILL.md +352 -0
- package/.versions/0.0.4/skills/code-review-and-quality/SKILL.md +381 -0
- package/.versions/0.0.4/skills/compound-learning/SKILL.md +137 -0
- package/.versions/0.0.4/skills/context-engineering/SKILL.md +291 -0
- package/.versions/0.0.4/skills/deprecation-and-migration/SKILL.md +206 -0
- package/.versions/0.0.4/skills/designing-agents/SKILL.md +394 -0
- package/.versions/0.0.4/skills/designing-agents/pi-harness-authoring.md +222 -0
- package/.versions/0.0.4/skills/frontend-ui-engineering/SKILL.md +328 -0
- package/.versions/0.0.4/skills/git-workflow-and-versioning/SKILL.md +316 -0
- package/.versions/0.0.4/skills/guided-workspace-setup/SKILL.md +535 -0
- package/.versions/0.0.4/skills/guided-workspace-setup/companion-manifest.json +33 -0
- package/.versions/0.0.4/skills/idea-refine/SKILL.md +182 -0
- package/.versions/0.0.4/skills/idea-refine/examples.md +238 -0
- package/.versions/0.0.4/skills/idea-refine/frameworks.md +99 -0
- package/.versions/0.0.4/skills/idea-refine/refinement-criteria.md +113 -0
- package/.versions/0.0.4/skills/idea-refine/scripts/idea-refine.sh +15 -0
- package/.versions/0.0.4/skills/incremental-implementation/SKILL.md +287 -0
- package/.versions/0.0.4/skills/interview-me/SKILL.md +226 -0
- package/.versions/0.0.4/skills/orchestration-verification/SKILL.md +181 -0
- package/.versions/0.0.4/skills/peer-coms/SKILL.md +90 -0
- package/.versions/0.0.4/skills/performance-optimization/SKILL.md +350 -0
- package/.versions/0.0.4/skills/planning-and-task-breakdown/SKILL.md +236 -0
- package/.versions/0.0.4/skills/security-and-hardening/SKILL.md +461 -0
- package/.versions/0.0.4/skills/spec-driven-development/SKILL.md +245 -0
- package/.versions/0.0.4/skills/using-agent-skills/SKILL.md +199 -0
- package/.versions/0.0.4/systemd/user/agent-fleet-codex-remote-control.service.in +23 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/LICENSE +21 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/README.md +11 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/api-and-interface-design/SKILL.md +294 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/browser-testing-with-devtools/SKILL.md +317 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/ci-cd-and-automation/SKILL.md +390 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/code-review-and-quality/SKILL.md +396 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/code-simplification/SKILL.md +331 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/context-engineering/SKILL.md +289 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/debugging-and-error-recovery/SKILL.md +300 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/deprecation-and-migration/SKILL.md +247 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/documentation-and-adrs/SKILL.md +278 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/doubt-driven-development/SKILL.md +243 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/frontend-ui-engineering/SKILL.md +328 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/git-workflow-and-versioning/SKILL.md +355 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/idea-refine/SKILL.md +178 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/idea-refine/examples.md +238 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/idea-refine/frameworks.md +99 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/idea-refine/refinement-criteria.md +113 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/idea-refine/scripts/idea-refine.sh +15 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/incremental-implementation/SKILL.md +249 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/interview-me/SKILL.md +225 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/observability-and-instrumentation/SKILL.md +203 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/performance-optimization/SKILL.md +350 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/planning-and-task-breakdown/SKILL.md +234 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/security-and-hardening/SKILL.md +467 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/shipping-and-launch/SKILL.md +310 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/source-driven-development/SKILL.md +194 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/spec-driven-development/SKILL.md +206 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/test-driven-development/SKILL.md +383 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/using-agent-skills/SKILL.md +191 -0
- package/.versions/0.0.5/.claude/commands/build.md +44 -0
- package/.versions/0.0.5/.claude/commands/code-simplify.md +22 -0
- package/.versions/0.0.5/.claude/commands/design-agent.md +14 -0
- package/.versions/0.0.5/.claude/commands/doctor-agent-fleet.md +17 -0
- package/.versions/0.0.5/.claude/commands/orchestrate.md +112 -0
- package/.versions/0.0.5/.claude/commands/plan.md +16 -0
- package/.versions/0.0.5/.claude/commands/prime.md +22 -0
- package/.versions/0.0.5/.claude/commands/review.md +16 -0
- package/.versions/0.0.5/.claude/commands/set-hermes-telegram.md +15 -0
- package/.versions/0.0.5/.claude/commands/setup-agent-fleet.md +25 -0
- package/.versions/0.0.5/.claude/commands/ship.md +72 -0
- package/.versions/0.0.5/.claude/commands/spec.md +15 -0
- package/.versions/0.0.5/.claude/commands/test.md +19 -0
- package/.versions/0.0.5/.claude/commands/webperf.md +32 -0
- package/.versions/0.0.5/.claude/orchestrate-teams.yaml +24 -0
- package/.versions/0.0.5/.opencode/commands/af-build.md +17 -0
- package/.versions/0.0.5/.opencode/commands/af-code-simplify.md +16 -0
- package/.versions/0.0.5/.opencode/commands/af-compound.md +16 -0
- package/.versions/0.0.5/.opencode/commands/af-design-agent.md +15 -0
- package/.versions/0.0.5/.opencode/commands/af-doctor-agent-fleet.md +17 -0
- package/.versions/0.0.5/.opencode/commands/af-orchestrate.md +112 -0
- package/.versions/0.0.5/.opencode/commands/af-plan.md +16 -0
- package/.versions/0.0.5/.opencode/commands/af-prime.md +22 -0
- package/.versions/0.0.5/.opencode/commands/af-review.md +15 -0
- package/.versions/0.0.5/.opencode/commands/af-set-hermes-telegram.md +15 -0
- package/.versions/0.0.5/.opencode/commands/af-setup-agent-fleet.md +15 -0
- package/.versions/0.0.5/.opencode/commands/af-ship.md +16 -0
- package/.versions/0.0.5/.opencode/commands/af-spec.md +16 -0
- package/.versions/0.0.5/.opencode/commands/af-test.md +21 -0
- package/.versions/0.0.5/.opencode/commands/af-webperf.md +32 -0
- package/.versions/0.0.5/.opencode/orchestrate-teams.yaml +24 -0
- package/.versions/0.0.5/.pi/agents/dispatch-policy.yaml +32 -0
- package/.versions/0.0.5/.pi/agents/model-profiles.yaml +20 -0
- package/.versions/0.0.5/.pi/agents/peers.yaml +146 -0
- package/.versions/0.0.5/.pi/agents/teams.yaml +39 -0
- package/.versions/0.0.5/.pi/damage-control-rules.yaml +297 -0
- package/.versions/0.0.5/.pi/extensions/agent-fleet-update-check/README.md +58 -0
- package/.versions/0.0.5/.pi/extensions/agent-fleet-update-check/index.ts +161 -0
- package/.versions/0.0.5/.pi/extensions/agent-fleet-update-check/package.json +6 -0
- package/.versions/0.0.5/.pi/extensions/btw/README.md +118 -0
- package/.versions/0.0.5/.pi/extensions/btw/index.ts +917 -0
- package/.versions/0.0.5/.pi/extensions/btw/package.json +6 -0
- package/.versions/0.0.5/.pi/extensions/btw/state.js +179 -0
- package/.versions/0.0.5/.pi/extensions/chrome-devtools-mcp/README.md +58 -0
- package/.versions/0.0.5/.pi/extensions/chrome-devtools-mcp/index.ts +92 -0
- package/.versions/0.0.5/.pi/extensions/chrome-devtools-mcp/package.json +6 -0
- package/.versions/0.0.5/.pi/extensions/compact-and-continue/README.md +42 -0
- package/.versions/0.0.5/.pi/extensions/compact-and-continue/index.ts +120 -0
- package/.versions/0.0.5/.pi/extensions/compact-and-continue/package.json +6 -0
- package/.versions/0.0.5/.pi/extensions/mcp-bridge/README.md +46 -0
- package/.versions/0.0.5/.pi/extensions/mcp-bridge/index.ts +206 -0
- package/.versions/0.0.5/.pi/extensions/mcp-bridge/package.json +6 -0
- package/.versions/0.0.5/.pi/extensions/package-lock.json +1143 -0
- package/.versions/0.0.5/.pi/extensions/package.json +9 -0
- package/.versions/0.0.5/.pi/extensions/pi-voice-stt/README.md +201 -0
- package/.versions/0.0.5/.pi/extensions/pi-voice-stt/config.ts +198 -0
- package/.versions/0.0.5/.pi/extensions/pi-voice-stt/examples/stt.json +35 -0
- package/.versions/0.0.5/.pi/extensions/pi-voice-stt/index.ts +248 -0
- package/.versions/0.0.5/.pi/extensions/pi-voice-stt/package.json +6 -0
- package/.versions/0.0.5/.pi/extensions/pi-voice-stt/providers.ts +214 -0
- package/.versions/0.0.5/.pi/extensions/pi-voice-stt/recorder.ts +158 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/README.md +798 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/access-approval.ts +135 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/artifacts.js +92 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/backend-policy.js +153 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/delegate.ts +386 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/drift-watchdog.js +165 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/evidence-rules.js +96 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/footer.ts +29 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/helpers.ts +214 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/index.ts +8045 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/monitor-session-bridge.ts +11 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/package.json +7 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/research-retention.js +34 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/return-contract.js +215 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/run-budget.js +155 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/scope-gate.js +103 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/spawn.ts +246 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/version.ts +18 -0
- package/.versions/0.0.5/.pi/harnesses/ask-user-remote/README.md +19 -0
- package/.versions/0.0.5/.pi/harnesses/ask-user-remote/index.ts +321 -0
- package/.versions/0.0.5/.pi/harnesses/ask-user-remote/race-core.js +106 -0
- package/.versions/0.0.5/.pi/harnesses/coms/README.md +92 -0
- package/.versions/0.0.5/.pi/harnesses/coms/index.ts +1745 -0
- package/.versions/0.0.5/.pi/harnesses/coms/package.json +7 -0
- package/.versions/0.0.5/.pi/harnesses/coms/version.ts +18 -0
- package/.versions/0.0.5/.pi/harnesses/damage-control-continue/README.md +117 -0
- package/.versions/0.0.5/.pi/harnesses/damage-control-continue/index.ts +536 -0
- package/.versions/0.0.5/.pi/harnesses/damage-control-continue/package.json +7 -0
- package/.versions/0.0.5/.pi/harnesses/damage-control-continue/version.ts +18 -0
- package/.versions/0.0.5/.pi/harnesses/lib/damage-control-shared.ts +197 -0
- package/.versions/0.0.5/.pi/harnesses/lib/herdr-client.ts +458 -0
- package/.versions/0.0.5/.pi/harnesses/lib/herdr-presence.ts +288 -0
- package/.versions/0.0.5/.pi/harnesses/lib/hermes-monitor-herdr.ts +28 -0
- package/.versions/0.0.5/.pi/harnesses/lib/hermes-monitor-model.ts +9 -0
- package/.versions/0.0.5/.pi/harnesses/lib/hermes-monitor-registry.ts +6 -0
- package/.versions/0.0.5/.pi/harnesses/lib/hermes-monitor-socket.ts +118 -0
- package/.versions/0.0.5/.pi/harnesses/lib/hermes-monitor-store.ts +31 -0
- package/.versions/0.0.5/.pi/harnesses/package-lock.json +35 -0
- package/.versions/0.0.5/.pi/harnesses/package.json +9 -0
- package/.versions/0.0.5/.pi/prompts/build.md +24 -0
- package/.versions/0.0.5/.pi/prompts/code-simplify.md +22 -0
- package/.versions/0.0.5/.pi/prompts/doctor-agent-fleet.md +15 -0
- package/.versions/0.0.5/.pi/prompts/plan.md +16 -0
- package/.versions/0.0.5/.pi/prompts/review.md +16 -0
- package/.versions/0.0.5/.pi/prompts/set-hermes-telegram.md +15 -0
- package/.versions/0.0.5/.pi/prompts/setup-agent-fleet.md +27 -0
- package/.versions/0.0.5/.pi/prompts/ship.md +17 -0
- package/.versions/0.0.5/.pi/prompts/spec.md +15 -0
- package/.versions/0.0.5/.pi/prompts/test.md +19 -0
- package/.versions/0.0.5/.pi/skills/bowser/SKILL.md +145 -0
- package/.versions/0.0.5/.version +1 -0
- package/.versions/0.0.5/agents/architect.md +23 -0
- package/.versions/0.0.5/agents/bowser.md +26 -0
- package/.versions/0.0.5/agents/builder.md +53 -0
- package/.versions/0.0.5/agents/code-reviewer.md +205 -0
- package/.versions/0.0.5/agents/deep-researcher.md +31 -0
- package/.versions/0.0.5/agents/documenter.md +18 -0
- package/.versions/0.0.5/agents/orchestrator.md +54 -0
- package/.versions/0.0.5/agents/plan-reviewer.md +60 -0
- package/.versions/0.0.5/agents/planner.md +69 -0
- package/.versions/0.0.5/agents/releaser.md +24 -0
- package/.versions/0.0.5/agents/researcher.md +28 -0
- package/.versions/0.0.5/agents/security-auditor.md +166 -0
- package/.versions/0.0.5/agents/test-engineer.md +151 -0
- package/.versions/0.0.5/agents/web-debugger.md +42 -0
- package/.versions/0.0.5/agents/web-performance-auditor.md +192 -0
- package/.versions/0.0.5/codex/CONDUCTOR.md +148 -0
- package/.versions/0.0.5/docs/ARCHITECTURE.md +210 -0
- package/.versions/0.0.5/docs/agent-fleet-setup.md +366 -0
- package/.versions/0.0.5/docs/claude-code-coms-bridge.md +103 -0
- package/.versions/0.0.5/docs/codex-remote-conductor.md +170 -0
- package/.versions/0.0.5/docs/coms-hermes-bridge.md +179 -0
- package/.versions/0.0.5/docs/getting-started.md +183 -0
- package/.versions/0.0.5/docs/npm-install.md +337 -0
- package/.versions/0.0.5/docs/opencode-setup.md +249 -0
- package/.versions/0.0.5/docs/pi-extensions.md +293 -0
- package/.versions/0.0.5/docs/pi-setup.md +472 -0
- package/.versions/0.0.5/docs/skill-anatomy.md +150 -0
- package/.versions/0.0.5/hermes/README.md +231 -0
- package/.versions/0.0.5/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
- package/.versions/0.0.5/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-cap.test.py +15 -0
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-discovery.test.py +19 -0
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-envelope.test.py +13 -0
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-forged-owner.test.py +11 -0
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-lease-list.test.py +9 -0
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-multihub.test.py +17 -0
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-output.test.py +34 -0
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +151 -0
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter.test.py +39 -0
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/plugin-api-validation.test.py +12 -0
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/review-live-wiring.red.test.py +22 -0
- package/.versions/0.0.5/hermes/skills/hub-conductor/SKILL.md +84 -0
- package/.versions/0.0.5/hermes/skills/hub-liaison/SKILL.md +84 -0
- package/.versions/0.0.5/hooks/SIMPLIFY-IGNORE.md +90 -0
- package/.versions/0.0.5/hooks/coms-stop-hook.mjs +73 -0
- package/.versions/0.0.5/hooks/hooks.json +14 -0
- package/.versions/0.0.5/hooks/session-start.sh +74 -0
- package/.versions/0.0.5/hooks/simplify-ignore.sh +302 -0
- package/.versions/0.0.5/justfile +245 -0
- package/.versions/0.0.5/references/accessibility-checklist.md +160 -0
- package/.versions/0.0.5/references/definition-of-done.md +67 -0
- package/.versions/0.0.5/references/fleet-coordination-patterns.md +151 -0
- package/.versions/0.0.5/references/observability-checklist.md +91 -0
- package/.versions/0.0.5/references/orchestration-patterns.md +370 -0
- package/.versions/0.0.5/references/performance-checklist.md +153 -0
- package/.versions/0.0.5/references/prompting-patterns.md +380 -0
- package/.versions/0.0.5/references/security-checklist.md +179 -0
- package/.versions/0.0.5/references/testing-patterns.md +236 -0
- package/.versions/0.0.5/scripts/codex-conductor.ts +41 -0
- package/.versions/0.0.5/scripts/codex-remote-control.ts +167 -0
- package/.versions/0.0.5/scripts/coms-claude-bridge.ts +286 -0
- package/.versions/0.0.5/scripts/coms-cli.ts +484 -0
- package/.versions/0.0.5/scripts/coms-hermes-bridge.ts +413 -0
- package/.versions/0.0.5/scripts/fleet.ts +141 -0
- package/.versions/0.0.5/scripts/hermes-monitor-capability-runner.ts +25 -0
- package/.versions/0.0.5/scripts/hermes-monitor-scenario.ts +7 -0
- package/.versions/0.0.5/scripts/lib/claude-bridge-core.ts +100 -0
- package/.versions/0.0.5/scripts/lib/codex-conductor.ts +88 -0
- package/.versions/0.0.5/scripts/lib/codex-remote-control.ts +480 -0
- package/.versions/0.0.5/scripts/lib/coms-envelope.ts +539 -0
- package/.versions/0.0.5/scripts/lib/fake-herdr-server.ts +88 -0
- package/.versions/0.0.5/scripts/lib/fleet-command.ts +109 -0
- package/.versions/0.0.5/scripts/lib/herdr-layout.ts +263 -0
- package/.versions/0.0.5/scripts/lib/hermes-bridge-core.ts +241 -0
- package/.versions/0.0.5/scripts/lib/hermes-monitor-herdr.ts +2 -0
- package/.versions/0.0.5/scripts/lib/hermes-monitor-model.ts +3 -0
- package/.versions/0.0.5/scripts/lib/hermes-monitor-registry.ts +2 -0
- package/.versions/0.0.5/scripts/lib/hermes-monitor-socket.ts +2 -0
- package/.versions/0.0.5/scripts/lib/hermes-monitor-store.ts +2 -0
- package/.versions/0.0.5/scripts/lib/persona-banner.ts +62 -0
- package/.versions/0.0.5/scripts/lib/spawn-stagger.ts +101 -0
- package/.versions/0.0.5/scripts/lib/team-project.ts +191 -0
- package/.versions/0.0.5/scripts/lib/team-snapshot.ts +147 -0
- package/.versions/0.0.5/scripts/peer-banner.ts +40 -0
- package/.versions/0.0.5/scripts/team-snapshot.ts +237 -0
- package/.versions/0.0.5/scripts/team-up.ts +351 -0
- package/.versions/0.0.5/skills/_internal/grilling.md +11 -0
- package/.versions/0.0.5/skills/browser-testing-with-devtools/SKILL.md +352 -0
- package/.versions/0.0.5/skills/code-review-and-quality/SKILL.md +381 -0
- package/.versions/0.0.5/skills/compound-learning/SKILL.md +137 -0
- package/.versions/0.0.5/skills/context-engineering/SKILL.md +291 -0
- package/.versions/0.0.5/skills/deprecation-and-migration/SKILL.md +206 -0
- package/.versions/0.0.5/skills/designing-agents/SKILL.md +394 -0
- package/.versions/0.0.5/skills/designing-agents/pi-harness-authoring.md +222 -0
- package/.versions/0.0.5/skills/frontend-ui-engineering/SKILL.md +328 -0
- package/.versions/0.0.5/skills/git-workflow-and-versioning/SKILL.md +316 -0
- package/.versions/0.0.5/skills/guided-workspace-setup/SKILL.md +542 -0
- package/.versions/0.0.5/skills/guided-workspace-setup/companion-manifest.json +35 -0
- package/.versions/0.0.5/skills/idea-refine/SKILL.md +182 -0
- package/.versions/0.0.5/skills/idea-refine/examples.md +238 -0
- package/.versions/0.0.5/skills/idea-refine/frameworks.md +99 -0
- package/.versions/0.0.5/skills/idea-refine/refinement-criteria.md +113 -0
- package/.versions/0.0.5/skills/idea-refine/scripts/idea-refine.sh +15 -0
- package/.versions/0.0.5/skills/incremental-implementation/SKILL.md +287 -0
- package/.versions/0.0.5/skills/interview-me/SKILL.md +226 -0
- package/.versions/0.0.5/skills/orchestration-verification/SKILL.md +181 -0
- package/.versions/0.0.5/skills/peer-coms/SKILL.md +90 -0
- package/.versions/0.0.5/skills/performance-optimization/SKILL.md +350 -0
- package/.versions/0.0.5/skills/planning-and-task-breakdown/SKILL.md +236 -0
- package/.versions/0.0.5/skills/security-and-hardening/SKILL.md +461 -0
- package/.versions/0.0.5/skills/spec-driven-development/SKILL.md +245 -0
- package/.versions/0.0.5/skills/using-agent-skills/SKILL.md +199 -0
- package/.versions/0.0.5/systemd/user/agent-fleet-codex-remote-control.service.in +23 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/LICENSE +21 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/README.md +11 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/api-and-interface-design/SKILL.md +294 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/browser-testing-with-devtools/SKILL.md +317 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/ci-cd-and-automation/SKILL.md +390 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/code-review-and-quality/SKILL.md +396 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/code-simplification/SKILL.md +331 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/context-engineering/SKILL.md +289 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/debugging-and-error-recovery/SKILL.md +300 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/deprecation-and-migration/SKILL.md +247 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/documentation-and-adrs/SKILL.md +278 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/doubt-driven-development/SKILL.md +243 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/frontend-ui-engineering/SKILL.md +328 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/git-workflow-and-versioning/SKILL.md +355 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/idea-refine/SKILL.md +178 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/idea-refine/examples.md +238 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/idea-refine/frameworks.md +99 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/idea-refine/refinement-criteria.md +113 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/idea-refine/scripts/idea-refine.sh +15 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/incremental-implementation/SKILL.md +249 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/interview-me/SKILL.md +225 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/observability-and-instrumentation/SKILL.md +203 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/performance-optimization/SKILL.md +350 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/planning-and-task-breakdown/SKILL.md +234 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/security-and-hardening/SKILL.md +467 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/shipping-and-launch/SKILL.md +310 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/source-driven-development/SKILL.md +194 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/spec-driven-development/SKILL.md +206 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/test-driven-development/SKILL.md +383 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/using-agent-skills/SKILL.md +191 -0
- package/CHANGELOG.md +62 -0
- package/README.md +17 -16
- package/agents/builder.md +1 -1
- package/agents/code-reviewer.md +1 -1
- package/agents/deep-researcher.md +3 -3
- package/agents/orchestrator.md +20 -11
- package/agents/plan-reviewer.md +3 -3
- package/agents/test-engineer.md +11 -4
- package/bin/cli.js +83 -1
- package/bin/lib/set-hermes-telegram.js +323 -0
- package/bin/lib/validate-overrides.js +19 -0
- package/bin/sync-harness-versions.js +94 -0
- package/docs/ARCHITECTURE.md +49 -4
- package/docs/agent-fleet-setup.md +11 -1
- package/docs/claude-code-coms-bridge.md +4 -4
- package/docs/codex-remote-conductor.md +12 -12
- package/docs/coms-hermes-bridge.md +62 -4
- package/docs/getting-started.md +4 -4
- package/docs/opencode-setup.md +1 -0
- package/docs/pi-extensions.md +73 -33
- package/docs/pi-setup.md +23 -8
- package/hermes/README.md +191 -8
- package/justfile +143 -158
- package/package.json +13 -5
- package/references/fleet-coordination-patterns.md +1 -1
- package/scripts/coms-hermes-bridge.ts +18 -8
- package/scripts/fleet.ts +141 -0
- package/scripts/lib/fake-herdr-server.ts +88 -0
- package/scripts/lib/fleet-command.ts +109 -0
- package/scripts/lib/hermes-bridge-core.ts +5 -2
- package/scripts/lib/hermes-monitor-herdr.ts +2 -0
- package/scripts/lib/hermes-monitor-model.ts +3 -0
- package/scripts/lib/hermes-monitor-registry.ts +2 -0
- package/scripts/lib/hermes-monitor-socket.ts +2 -0
- package/scripts/lib/hermes-monitor-store.ts +2 -0
- package/scripts/lib/team-project.ts +10 -3
- package/scripts/team-snapshot.ts +4 -5
- package/scripts/team-up.ts +24 -6
- package/skills/designing-agents/SKILL.md +2 -2
- package/skills/designing-agents/pi-harness-authoring.md +26 -13
- package/skills/guided-workspace-setup/SKILL.md +22 -12
- package/skills/guided-workspace-setup/companion-manifest.json +3 -1
- package/skills/peer-coms/SKILL.md +1 -1
- package/.pi/harnesses/damage-control/README.md +0 -65
- package/.pi/harnesses/damage-control/index.ts +0 -250
|
@@ -183,7 +183,7 @@ An Express answer other than `Custom` skips all seven group screens and goes str
|
|
|
183
183
|
|
|
184
184
|
1. **Quick screen** (single-select). Fresh: `Recommended ★ (n)` / `Everything (m)` / `Customise` / `Skip group`. Existing: `Keep as-is (n installed)` / `Apply updates (k changed)` / `Customise` / `Remove some…`. Counts come from the state table; a group with nothing installed and nothing recommended may go straight to its Customise chunks.
|
|
185
185
|
2. **Customise drill-in** (multi-select, only when picked). The group's items chunked by sub-category, ≤ 9 options per call (`part i/n`; ≤ 4 on `AskUserQuestion`). Titles: `<name> ★ [st]`. Descriptions: the purpose in ≤ ~6 words plus the state in plain words and its consequence (`mod` → "refreshing overwrites your local edits"). Selecting an item installs or refreshes it; **leaving an installed item unselected keeps it as-is — it does not remove it.** `cflt` rows are listed for visibility, but selecting one only queues its diff-then-ask exchange.
|
|
186
|
-
3. **Remove screen** (multi-select, only via `Remove some…` or when the user asks to remove). Lists **only** installed items the removal-scope rule allows (
|
|
186
|
+
3. **Remove screen** (multi-select, only via `Remove some…` or when the user asks to remove). Lists **only** installed items the removal-scope rule allows (current inventory + recorded / symlinked-to-source). Selecting an item marks it for removal in Step 9/10; an empty selection or cancel removes nothing. Items held by the mandatory Fleet Core closure (`damage-control-continue`, `ask-user-remote`, `pi-voice-stt`, `compact-and-continue`, `btw`, and `agent-fleet-update-check` while any harness stays kept) are not listed; explain the dependency if the user asks for them. A source-retired `damage-control` hard-stop harness is a `gone` cleanup, not a selectable inventory item; apply the retired-artifact ownership rule below.
|
|
187
187
|
|
|
188
188
|
**The three-way diff for `conflicting upgrade`.** For each `cflt` row, print the diff as normal agent text, comparing:
|
|
189
189
|
|
|
@@ -229,7 +229,7 @@ Groups, in order. Groups 1–4 apply to every agent; groups 5–7 are shown **on
|
|
|
229
229
|
- *pi-only* *(shown only when the agent is `pi`)* — `bowser`, `web-debugger`, `orchestrator`
|
|
230
230
|
|
|
231
231
|
For `claude-code`/`opencode`, installed rows are **generated artifacts** (see Step 3): record them with `transformed: true` in `## install-status`, and compute their status by comparing the installed file against `transform(current source)` — and for upgrades against `transform(.versions/<recorded>/agents/<name>.md)` — never against the raw canonical source, whose bytes legitimately differ from the generated output.
|
|
232
|
-
3. **Commands / prompts** *(single-type — no sub-category)* — mapped to the chosen agent; items without a per-agent source are filtered out, no cross-tool substitution. Full candidate list: `spec` ★, `plan` ★, `build` ★, `test` ★, `review` ★, `orchestrate` ★, `compound`, `code-simplify`, `ship`, `design-agent`, `prime`. The actual menu shows only items whose per-agent source file exists — for example, `.pi/prompts/design-agent.md` and `.pi/prompts/prime.md` are absent, so neither is offered when the agent is `pi`; and `orchestrate` has a source for `claude-code` (`.claude/commands/orchestrate.md`) and `opencode` (`.opencode/commands/af-orchestrate.md`) but **not** `pi` (no `.pi/prompts/orchestrate.md`), so the existing source-availability filter surfaces it for claude-code + opencode and hides it for pi automatically. `compound` follows the same pattern (`.claude/commands/compound.md` / `.opencode/commands/af-compound.md`, no pi prompt — the agent-hub harness ships its own `/compound` command); when `compound` is selected, recommend the `compound-learning` skill alongside it. *(`setup` and `doctor` are installer-only — never offered, since they live in the source agent-fleet repo and act on target workspaces from there.)*
|
|
232
|
+
3. **Commands / prompts** *(single-type — no sub-category)* — mapped to the chosen agent; items without a per-agent source are filtered out, no cross-tool substitution. Full candidate list: `spec` ★, `plan` ★, `build` ★, `test` ★, `review` ★, `orchestrate` ★, `compound`, `code-simplify`, `ship`, `design-agent`, `prime`, `set-hermes-telegram`. The actual menu shows only items whose per-agent source file exists — for example, `.pi/prompts/design-agent.md` and `.pi/prompts/prime.md` are absent, so neither is offered when the agent is `pi`; and `orchestrate` has a source for `claude-code` (`.claude/commands/orchestrate.md`) and `opencode` (`.opencode/commands/af-orchestrate.md`) but **not** `pi` (no `.pi/prompts/orchestrate.md`), so the existing source-availability filter surfaces it for claude-code + opencode and hides it for pi automatically. `compound` follows the same pattern (`.claude/commands/compound.md` / `.opencode/commands/af-compound.md`, no pi prompt — the agent-hub harness ships its own `/compound` command); when `compound` is selected, recommend the `compound-learning` skill alongside it. *(`setup` and `doctor` are installer-only — never offered, since they live in the source agent-fleet repo and act on target workspaces from there.)*
|
|
233
233
|
|
|
234
234
|
**`orchestrate` carries a team-config companion.** `orchestrate-teams.yaml` (the named-team roster the `/orchestrate` command reads) is not its own menu row — it is a companion of the `orchestrate` command (same idea as the pi harness `justfile` companion). Whenever `orchestrate` is installed/kept/removed, install/remove the agent's team config from source in the same pass — `.claude/orchestrate-teams.yaml` for claude-code, `.opencode/orchestrate-teams.yaml` for opencode. Treat it as a normal versioned artifact for the Step 6 status tokens: a user-edited copy is `mod`/`cflt` and gets the three-way-diff treatment, never a silent clobber of their team definitions. **Removal safety:** when `orchestrate` is removed, the team config is removed **only** if it still matches the shipped source (unedited); a user-edited `orchestrate-teams.yaml` is preserved and listed under "Skipped — user-modified" rather than deleted, so custom team definitions survive an uninstall.
|
|
235
235
|
4. **References & Hooks** *(sub-category = `reference` / `hook`)* — one group for the shared non-agent-specific artifacts:
|
|
@@ -243,6 +243,8 @@ Groups, in order. Groups 1–4 apply to every agent; groups 5–7 are shown **on
|
|
|
243
243
|
|
|
244
244
|
**Two complementary browser stacks.** `bowser` (runtime-skill, here) and `chrome-devtools-mcp` (extension, here) cover different browser needs and pair well — `bowser`/`playwright-cli` for headless, parallel, delegatable automation; `chrome-devtools-mcp` (driven by the `web-debugger` persona in group 2) for interactive headful debugging with live DOM/console/network. When the user wants full browser coverage, recommend both; when they only want one, fit it to the use case (automation vs interactive debug). See `docs/pi-extensions.md` ("Two browser stacks — when to use which").
|
|
245
245
|
|
|
246
|
+
**Extension runtime dependencies are companions.** Whenever any pi extension is installed or refreshed, also refresh `.pi/extensions/package.json` and `.pi/extensions/package-lock.json`, then run `npm ci --prefix .pi/extensions`. For a symlink install sourced from the published `@chankov/agent-fleet` package, verify every dependency in `.pi/extensions/package.json` is also declared in the package root's production `dependencies`: Node resolves imports from the symlink's real package path, and npm does not install a nested manifest automatically. A missing root declaration is a failed install, not a warning.
|
|
247
|
+
|
|
246
248
|
**`bowser` external CLI dependency.** The `bowser` runtime-skill drives the external **Playwright Agent CLI** (`playwright-cli`), which is **not** an agent-fleet artifact and is not copied from this repo (same idea as the `pi-ask-user` external package). Whenever `bowser` is selected (installed or kept), check whether `playwright-cli` is on `PATH` (`playwright-cli --help`, or `npx playwright-cli --help`). If it is missing, tell the user and offer the install — `npm install -g @playwright/cli@latest` (global) or note the `npx playwright-cli` ad-hoc fallback — then surface it in the Step 9 plan as an external dependency, not a file write. Record it under the same `external-pi-packages` / `project-packages` convention in `.ai/agent-fleet-setup.md` so re-runs re-verify it. Do not silently install a global package without the user's confirmation, and never block the `bowser` install on it — a missing CLI is a warning, not a hard stop. Install reference: <https://playwright.dev/agent-cli/installation>.
|
|
247
249
|
|
|
248
250
|
**`pi-voice-stt` provider configuration.** The `pi-voice-stt` extension (Alt+S voice dictation) is a **gated no-op until a provider is configured** — installing the files alone binds no hotkey. Whenever it is selected (installed or kept) **and** the workspace has no `.ai/stt.json` yet, offer (don't force) to configure it now; the user may skip and run `/stt doctor` later. The config write is a **companion** of the extension (same idea as the `orchestrate-teams.yaml` companion), applied in Step 10, not a separate menu row. When the user opts in, ask the provider:
|
|
@@ -255,18 +257,23 @@ Groups, in order. Groups 1–4 apply to every agent; groups 5–7 are shown **on
|
|
|
255
257
|
2. `<workspace>/.env` (repo root, auto-loaded by the `justfile`'s `dotenv-load`) — append the referenced secret variables as **empty placeholders** only if absent (`AZURE_SPEECH_KEY=`, `AZURE_SPEECH_ENDPOINT=`, or `OPENAI_API_KEY=`); never overwrite an existing value, and tell the user to fill them in. Ensure `.env` is gitignored — add a `.env` line to the workspace `.gitignore` if no `.env`/`.env*` rule already covers it.
|
|
256
258
|
|
|
257
259
|
Record `.ai/stt.json` (and the `.env` keys touched) in `## install-status`. On a later removal of `pi-voice-stt`, delete `.ai/stt.json` **only** if it still matches what setup wrote (unedited; a user-edited config is preserved and listed under "Skipped — user-modified"), and **never** delete `.env`, its values, or the `.gitignore` line. Secrets in `.env` outlive the extension.
|
|
258
|
-
6. **pi harnesses** *(pi only; sub-category = harness category — install many,
|
|
260
|
+
6. **pi harnesses** *(pi only; sub-category = harness category — install many, compose them only through the unified `just fleet` entry point; `just fleet hub` adds `agent-hub` on top of Fleet Core)* — one group for all harnesses:
|
|
259
261
|
- *orchestration* — `agent-hub`, `ask-user-remote`
|
|
260
|
-
- *safety* — `damage-control
|
|
262
|
+
- *safety* — `damage-control-continue`
|
|
261
263
|
- *messaging* — `coms`
|
|
262
264
|
|
|
263
|
-
**Mandatory
|
|
265
|
+
**Mandatory Fleet Core closure for every installed harness.** The canonical `just fleet` launcher and every Herdr Pi peer explicitly load `damage-control-continue`, `ask-user-remote`, `pi-voice-stt`, `compact-and-continue`, `btw`, and `agent-fleet-update-check`. Therefore, when any harness is selected or kept, auto-include both core harnesses (`damage-control-continue`, `ask-user-remote`) and all four core utility extensions (`pi-voice-stt`, `compact-and-continue`, `btw`, `agent-fleet-update-check`) in the same pass. State the auto-inclusion in the restate line and keep these dependencies off the remove screen while any harness remains. `pi-voice-stt` may remain unconfigured; in that state it binds no hotkey but `/stt doctor` remains available. The optional `chrome-devtools-mcp` extension is not part of Core and is loaded only with `just fleet --browser`, a Hub `--browser` capability, or a peer manifest `extensions:` entry.
|
|
266
|
+
|
|
267
|
+
**Hub child safety.** `just fleet hub` loads Fleet Core before `agent-hub`; the hub then re-loads `damage-control-continue` into every native specialist, researcher, and nested delegate. Removing the safety harness leaves child dispatch fail-closed, while removing `ask-user-remote` makes the hub's `askUserAvailable` probe omit `ask_user` from dispatcher tools. These dependencies remain selectable on their own only when no Fleet harness installation depends on the unified launcher.
|
|
268
|
+
|
|
269
|
+
**Retired hard-stop cleanup.** `damage-control` (the former hard-stop harness) is no longer inventory and must never be installed or offered. On an upgrade, classify an existing `.pi/harnesses/damage-control/` as an upstream-removed (`gone`) artifact. Propose removal only when it is recorded in `## install-status` and still matches the recorded-version snapshot, or is a symlink whose target path is inside the agent-fleet source root (including a now-broken link to the retired source path). Preserve a user-modified regular copy or any unrecorded/unowned copy as `Skipped — user-modified` / `Skipped — not owned`; never delete it silently. Itemise the cleanup in Step 9, and remove its install-status row only when the owned artifact is actually removed.
|
|
264
270
|
|
|
265
271
|
**Harness companions (refreshed with the group, not separate rows).** A harness directory does not run on its own — the launch recipes live in the `justfile`, and several harnesses shell out to support files. So whenever **any** harness in this group is installed, kept, or removed, refresh its companions from source in the same pass — they are not shown as their own menu rows:
|
|
266
272
|
- Every path in `companion-manifest.json` — the sole list for Codex/Hermes/systemd directories, conductor docs, top-level runtime scripts, and recursive `scripts/lib` imports. Do not recreate a partial hand-maintained list.
|
|
267
|
-
- `.pi/agents/peers.yaml`, `.pi/agents/teams.yaml`, and the peer personas they name (e.g. `architect`, `releaser`) — read by `team
|
|
273
|
+
- `.pi/agents/peers.yaml`, `.pi/agents/teams.yaml`, and the peer personas they name (e.g. `architect`, `releaser`) — read by `just fleet team`.
|
|
268
274
|
- `.pi/damage-control-rules.yaml` — the rule set the damage-control harness loads.
|
|
269
275
|
- `.pi/harnesses/package.json` (+ `npm install --prefix .pi/harnesses`) — the harness runtime deps (`yaml`, `@sinclair/typebox`).
|
|
276
|
+
- Fleet Core's `.pi/extensions/package.json` + lockfile (+ `npm ci --prefix .pi/extensions`) — required because the unified launcher explicitly loads the core utility extensions even when Pi auto-discovery is disabled.
|
|
270
277
|
|
|
271
278
|
**The `justfile` is the one that goes stale on upgrade.** Refresh it from the **current** source, never leave the installed copy as-is: the source `justfile` is canonical, so refreshing it prunes recipes for harnesses retired since the recorded version and adds recipes for new ones. A workspace whose harness set changed between versions but whose `justfile` was left untouched is the exact failure this rule prevents — `just --list` keeps recipes pointing at deleted `.pi/harnesses/<name>/` dirs and lacks recipes for the new harnesses. Treat the `justfile` as a normal versioned artifact subject to the Step 6 status rules: it carries its own state (`ok`/`upd`/`mod`/`cflt`) in the group's restate line, and a user-edited `justfile` gets the same `cflt` diff-then-ask treatment as any other modified file — never a silent clobber. The `.versions/<recorded>/justfile` snapshot is the recorded-side of that diff.
|
|
272
279
|
|
|
@@ -292,10 +299,10 @@ When an external pi package is selected during clone/symlink or manual pi setup
|
|
|
292
299
|
|
|
293
300
|
**Removal scope — what the remove screen (and `gone`/`brk` cleanup) may touch.** A target item is eligible for removal only when **both** are true:
|
|
294
301
|
|
|
295
|
-
1. **It is part of the agent-fleet inventory
|
|
296
|
-
2. **
|
|
302
|
+
1. **It is part of the current agent-fleet inventory, or is an owned artifact removed upstream.** Current inventory names match artifacts shipped in the source repo's canonical trees (`skills/`, `vendor/agent-skills-upstream/skills/`, `agents/`, `.claude/commands/`, `.pi/prompts/`, `.pi/extensions/`, `.pi/harnesses/`, `.pi/skills/`, `references/`, `hooks/`). A source-retired artifact is eligible only as a `gone` cleanup when its old path is present in the recorded-version snapshot; this exception currently covers the retired `.pi/harnesses/damage-control/` hard-stop harness. External pi packages are governed by the Group 7 ownership rule above. Other out-of-inventory items are never proposed for removal.
|
|
303
|
+
2. **Ownership is proven.** For current inventory, `## install-status` records the item or it is a symlink into the source root. For a source-retired artifact, it must be recorded and byte-match the recorded-version snapshot, or be a symlink whose stored target is inside the source root (a broken symlink caused by retirement still counts). A differing regular copy is user-modified and must be preserved.
|
|
297
304
|
|
|
298
|
-
If a candidate fails either test, list it once under
|
|
305
|
+
If a candidate fails either test, list it once under `Skipped — user-modified` or `Skipped — not owned by agent-fleet` in the Step 9 plan and leave it alone. Settings files (`.claude/settings.json`, `.opencode/config*`, env vars, MCP config) are touched **only** to remove agent-fleet' own hook registrations — never other keys, never user env vars, never third-party MCP entries.
|
|
299
306
|
|
|
300
307
|
**Tabular fallback rendering (no-widget runtimes only).** When Step 1 resolved to the tabular fallback, render each group as one compact markdown table and take the picks as a text reply — this legacy format keeps the old pre-checked semantics, since a printed table *can* show them:
|
|
301
308
|
|
|
@@ -370,6 +377,8 @@ For settings files (`.claude/settings.json` and equivalents), edit only the agen
|
|
|
370
377
|
- Refresh the `justfile` from the **current** source into its managed region (between the `# >>> agent-fleet:harnesses … >>>` / `# <<< agent-fleet:harnesses <<<` sentinels), preserving any user recipes outside it — this is what prunes retired-harness recipes and adds new ones. In symlink mode, link the whole `justfile` to source **only** when the target has no `justfile` or its existing one is wholly agent-fleet'; if the target carries user recipes, fall back to a copy-mode managed-region rewrite so those recipes survive.
|
|
371
378
|
- Record every manifest target under `harness-support` in `## install-status`. **Removal:** when the **last** pi harness is removed, strip the managed `justfile` region and remove only manifest targets recorded as owned (or symlinked into the source root). Preserve user recipes, unrecorded regular files, and any companion still needed by another selected harness. Never touch user systemd state, Codex auth, pairing material, or credentials.
|
|
372
379
|
|
|
380
|
+
**pi extension companions.** When this pass installs or refreshes any pi extension, refresh `.pi/extensions/package.json` and `.pi/extensions/package-lock.json`, run `npm ci --prefix .pi/extensions`, and record both manifests under `extension-support`. In symlink mode against an npm package, additionally compare the extension manifest's dependencies with the source package root's production dependencies and stop if any are missing; a target-local install cannot prove that imports resolving through the package's real path will work.
|
|
381
|
+
|
|
373
382
|
**`pi-voice-stt` config companion.** When this pass installs `pi-voice-stt` and the user opted into provider configuration (Step 6 group 5 note), write `.ai/stt.json` (non-secret config) and append the referenced env-var placeholders to the workspace root `.env` (creating it and the `.gitignore` rule if needed) in this same pass — never write key values into `.ai/`. On removal of `pi-voice-stt`, delete `.ai/stt.json` only if unedited, and leave `.env` untouched. Record both under `## install-status`.
|
|
374
383
|
|
|
375
384
|
Then write both `.ai/` files: the agreed override sections from Step 7 into `.ai/agent-fleet-overrides.md`, and the install record — artifacts, target paths, method, **package version**, date — into `.ai/agent-fleet-setup.md`. The `version:` line in `## workspace-summary` is set to the package version from Step 2; this is what the next re-run will compare against to compute the version delta.
|
|
@@ -397,7 +406,7 @@ If `cleanupInstaller` is available via the CLI (`npx @chankov/agent-fleet cleanu
|
|
|
397
406
|
|
|
398
407
|
### 11. Verify and report
|
|
399
408
|
|
|
400
|
-
Re-scan the install-target directories one more time and confirm: every selected artifact exists at its target path, every deselected one is gone, and zero broken symlinks remain. When pi harnesses were touched, also confirm the `justfile` is consistent with the installed harness set: every installed harness has its launch recipe, and **no recipe points at a `.pi/harnesses/<name>/` that is not installed** (a leftover recipe for a retired harness is the regression this check catches). Also re-read `.ai/agent-fleet-setup.md` and verify the `version:` line matches the package version from Step 2 — a mismatch here means the apply pass did not stamp the new version, and must be corrected before the next re-run computes the wrong delta. If the post-apply scan surfaces any new breakage, treat it as a doctor finding and offer the same repair options as Step 5, then append a second `## doctor-runs` line with `phase: postflight`. List what changed, point the user at `.ai/agent-fleet-overrides.md` and `.ai/agent-fleet-setup.md`, and suggest loading `using-agent-skills` first in their next session.
|
|
409
|
+
Re-scan the install-target directories one more time and confirm: every selected artifact exists at its target path, every deselected one is gone, and zero broken symlinks remain. When pi extensions were touched, verify their runtime imports from the **real source path** (not only the target symlink path); when `chrome-devtools-mcp` is selected, launch/reload pi and require `/chrome_devtools-status` to report `connected` with a non-zero registered tool count. Merely listing the extension under `[Extensions]` is not proof that its asynchronous MCP initialization succeeded. When pi harnesses were touched, also confirm the `justfile` is consistent with the installed harness set: every installed harness has its launch recipe, and **no recipe points at a `.pi/harnesses/<name>/` that is not installed** (a leftover recipe for a retired harness is the regression this check catches). Also re-read `.ai/agent-fleet-setup.md` and verify the `version:` line matches the package version from Step 2 — a mismatch here means the apply pass did not stamp the new version, and must be corrected before the next re-run computes the wrong delta. If the post-apply scan surfaces any new breakage, treat it as a doctor finding and offer the same repair options as Step 5, then append a second `## doctor-runs` line with `phase: postflight`. List what changed, point the user at `.ai/agent-fleet-overrides.md` and `.ai/agent-fleet-setup.md`, and suggest loading `using-agent-skills` first in their next session.
|
|
401
410
|
|
|
402
411
|
Close the report with one line explaining the installer-cleanup outcome:
|
|
403
412
|
|
|
@@ -474,7 +483,7 @@ Close the report with one line explaining the installer-cleanup outcome:
|
|
|
474
483
|
- An existing, differing target file overwritten without asking the user.
|
|
475
484
|
- A re-run that ignores the existing `## install-status` and reinstalls everything.
|
|
476
485
|
- A `pi` workspace using `agent-hub` reached Step 7 without being offered the `## agent-hub` / `language: <value>` override, or an existing language value was overwritten instead of preserved.
|
|
477
|
-
- `agent-hub` installed or kept without `damage-control` **and** `
|
|
486
|
+
- `agent-hub` installed or kept without `damage-control-continue` **and** `ask-user-remote` — the mandatory pairing was skipped, or removal of either required companion was accepted while `agent-hub` stayed selected.
|
|
478
487
|
- The `bowser` runtime-skill installed without checking for the external `playwright-cli` CLI — or a global `@playwright/cli` install run without the user's confirmation.
|
|
479
488
|
- The overrides file padded with install status, summaries, or prose instead of terse `key: value` sections.
|
|
480
489
|
- A re-run that detects a non-empty version delta but skips the "Changes since v<recorded> → v<current>" block in Step 9.
|
|
@@ -514,7 +523,8 @@ After completing the workflow, confirm:
|
|
|
514
523
|
- [ ] Settings-file edits were limited to agent-fleet' own hook entries; no user keys, env vars, or third-party MCP entries were modified.
|
|
515
524
|
- [ ] `.ai/agent-fleet-overrides.md` holds the agreed override sections as terse `key: value` lines, and nothing else.
|
|
516
525
|
- [ ] For `pi` workspaces using `agent-hub`, the `## agent-hub` language override was offered (an existing legacy `## agent-team` section kept its name), existing values were preserved, and omitting the section was treated as default English.
|
|
517
|
-
- [ ] If `agent-hub` was installed or kept, `damage-control`
|
|
526
|
+
- [ ] If `agent-hub` was installed or kept, `damage-control-continue` and `ask-user-remote` were installed/kept alongside it (mandatory pairing) and could not be deselected while `agent-hub` remained.
|
|
527
|
+
- [ ] Any retired `.pi/harnesses/damage-control/` copy was removed only when recorded and unchanged (or symlinked into source); user-modified or unowned copies were preserved.
|
|
518
528
|
- [ ] If the `bowser` runtime-skill was installed or kept, the external `playwright-cli` dependency was checked, and a missing CLI was surfaced with the install offer (`npm install -g @playwright/cli@latest`) rather than silently installed or treated as a hard failure.
|
|
519
529
|
- [ ] `.ai/agent-fleet-setup.md` holds an up-to-date install record, including at least one `## doctor-runs` entry for this session, and a `version:` line in `## workspace-summary` that matches the package version from Step 2.
|
|
520
530
|
- [ ] Step 9 was rendered as compact action-grouped lines (Add / Refresh / Remove / Keep-count / Records / Method) printed as agent text, followed by the single `inline` confirm question — not a wide `Target paths` + `Notes` table, and not a plan packed into the question's `context`.
|
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
"description": "Runtime closure refreshed with any pi harness selection. Paths are repository-relative and contain no user configuration or credentials.",
|
|
4
4
|
"directories": [
|
|
5
5
|
"codex",
|
|
6
|
-
"hermes",
|
|
6
|
+
"hermes/skills",
|
|
7
7
|
"systemd"
|
|
8
8
|
],
|
|
9
9
|
"files": [
|
|
@@ -16,6 +16,7 @@
|
|
|
16
16
|
"scripts/coms-claude-bridge.ts",
|
|
17
17
|
"scripts/coms-cli.ts",
|
|
18
18
|
"scripts/coms-hermes-bridge.ts",
|
|
19
|
+
"scripts/fleet.ts",
|
|
19
20
|
"scripts/peer-banner.ts",
|
|
20
21
|
"scripts/team-snapshot.ts",
|
|
21
22
|
"scripts/team-up.ts",
|
|
@@ -23,6 +24,7 @@
|
|
|
23
24
|
"scripts/lib/codex-conductor.ts",
|
|
24
25
|
"scripts/lib/codex-remote-control.ts",
|
|
25
26
|
"scripts/lib/coms-envelope.ts",
|
|
27
|
+
"scripts/lib/fleet-command.ts",
|
|
26
28
|
"scripts/lib/herdr-layout.ts",
|
|
27
29
|
"scripts/lib/hermes-bridge-core.ts",
|
|
28
30
|
"scripts/lib/persona-banner.ts",
|
|
@@ -8,7 +8,7 @@ description: Makes Claude Code a first-class peer in the local coms agent pool
|
|
|
8
8
|
## Overview
|
|
9
9
|
|
|
10
10
|
You may be running next to other live coding agents on this machine: pi peers spawned by
|
|
11
|
-
`just team
|
|
11
|
+
`just fleet team`, an Agent Hub orchestrator, or other bridged Claude Code panes. They form a
|
|
12
12
|
**coms pool** — addressable peers exchanging structured prompt/response envelopes. A
|
|
13
13
|
bridge process (`coms-claude-bridge`) registered YOU in that pool under a peer name, so
|
|
14
14
|
colleagues can message you, and a CLI (`coms-cli`) lets you message them.
|
|
@@ -1,65 +0,0 @@
|
|
|
1
|
-
# damage-control
|
|
2
|
-
|
|
3
|
-
Safety auditing — blocks destructive tool calls.
|
|
4
|
-
|
|
5
|
-
> Ported from [`pi-vs-claude-code`](https://github.com/disler/pi-vs-claude-code) by [disler](https://github.com/disler) (MIT). See the [extension catalog](../../../docs/pi-extensions.md).
|
|
6
|
-
|
|
7
|
-
## What it does
|
|
8
|
-
|
|
9
|
-
Intercepts every tool call and checks it against rules in `.pi/damage-control-rules.yaml`:
|
|
10
|
-
|
|
11
|
-
- `bashToolPatterns` — destructive shell commands (`rm -rf`, `git reset --hard`,
|
|
12
|
-
`DROP TABLE`, cloud-resource deletes, …); some are hard-blocked, some marked `ask`
|
|
13
|
-
- `zeroAccessPaths` — secrets and credentials that must never be read (`.env`, `*.pem`, …)
|
|
14
|
-
- `readOnlyPaths` — paths that may be read but not written (lockfiles, build output, …)
|
|
15
|
-
- `noDeletePaths` — paths that may be edited but not deleted (`README`, `.git/`, …)
|
|
16
|
-
|
|
17
|
-
On a match the tool result is replaced with a block message and the agent's turn is
|
|
18
|
-
aborted (`ctx.abort()`). For the softer variant that blocks but feeds back so the agent
|
|
19
|
-
adapts and keeps working, see [`damage-control-continue`](../damage-control-continue/README.md)
|
|
20
|
-
— the default guardrail for the `just hub` main session and spawned research helpers.
|
|
21
|
-
|
|
22
|
-
## Exemptions (pre-granted only)
|
|
23
|
-
|
|
24
|
-
The hard-stop variant honors **pre-granted exemptions** from the shared exemptions
|
|
25
|
-
file agent-hub passes down via `AGENT_HUB_EXEMPTIONS_FILE` (written by `/allow
|
|
26
|
-
<pattern> session` or an approved escalation in the dispatcher session). Exemptions
|
|
27
|
-
apply to the path categories only — `zeroAccessPaths`, `readOnlyPaths`,
|
|
28
|
-
`noDeletePaths` — never to the destructive `bashToolPatterns`. There is no
|
|
29
|
-
prompting and no escalation here by design: a specialist run never negotiates
|
|
30
|
-
access mid-flight; grants happen in the hub before or between dispatches.
|
|
31
|
-
Agent-scoped grants (`Allow for <agent>`) only reach the child whose
|
|
32
|
-
`AGENT_HUB_AGENT_ID` matches.
|
|
33
|
-
|
|
34
|
-
The exemption plumbing (file I/O + escalation protocol types) lives in
|
|
35
|
-
[`shared.ts`](./shared.ts), used by both variants and agent-hub.
|
|
36
|
-
|
|
37
|
-
## Commands & tools
|
|
38
|
-
|
|
39
|
-
None — it runs passively on the `tool_call` event.
|
|
40
|
-
|
|
41
|
-
## Requires
|
|
42
|
-
|
|
43
|
-
- `.pi/damage-control-rules.yaml` — the rule set (shipped in this repo)
|
|
44
|
-
|
|
45
|
-
## Usage
|
|
46
|
-
|
|
47
|
-
```bash
|
|
48
|
-
# standalone guardrail session
|
|
49
|
-
just ext-damage-control
|
|
50
|
-
pi -e .pi/harnesses/damage-control/index.ts
|
|
51
|
-
|
|
52
|
-
# the hub recipes load this harness first by default
|
|
53
|
-
just hub
|
|
54
|
-
just hub-solo
|
|
55
|
-
|
|
56
|
-
# direct guarded hub launch
|
|
57
|
-
pi -e .pi/harnesses/damage-control/index.ts -e .pi/harnesses/agent-hub/index.ts
|
|
58
|
-
```
|
|
59
|
-
|
|
60
|
-
## Upstream changes
|
|
61
|
-
|
|
62
|
-
- Theme integration removed — the `themeMap.ts` import and the `applyExtensionDefaults()`
|
|
63
|
-
call were stripped (this repo does not ship pi themes).
|
|
64
|
-
- Pre-granted exemptions from the hub session's shared file are honored (not in
|
|
65
|
-
upstream) — see the Exemptions section above.
|
|
@@ -1,250 +0,0 @@
|
|
|
1
|
-
import type { ExtensionAPI, ToolCallEvent } from "@mariozechner/pi-coding-agent";
|
|
2
|
-
import { isToolCallEventType } from "@mariozechner/pi-coding-agent";
|
|
3
|
-
import { parse as yamlParse } from "yaml";
|
|
4
|
-
import * as fs from "fs";
|
|
5
|
-
import * as path from "path";
|
|
6
|
-
import * as os from "os";
|
|
7
|
-
import { AGENT_ID_ENV, EXEMPTIONS_FILE_ENV, fileExemptionsFor, type Exemption } from "./shared.ts";
|
|
8
|
-
|
|
9
|
-
interface Rule {
|
|
10
|
-
pattern: string;
|
|
11
|
-
reason: string;
|
|
12
|
-
ask?: boolean;
|
|
13
|
-
}
|
|
14
|
-
|
|
15
|
-
interface Rules {
|
|
16
|
-
bashToolPatterns: Rule[];
|
|
17
|
-
zeroAccessPaths: string[];
|
|
18
|
-
readOnlyPaths: string[];
|
|
19
|
-
noDeletePaths: string[];
|
|
20
|
-
}
|
|
21
|
-
|
|
22
|
-
export default function (pi: ExtensionAPI) {
|
|
23
|
-
let rules: Rules = {
|
|
24
|
-
bashToolPatterns: [],
|
|
25
|
-
zeroAccessPaths: [],
|
|
26
|
-
readOnlyPaths: [],
|
|
27
|
-
noDeletePaths: [],
|
|
28
|
-
};
|
|
29
|
-
|
|
30
|
-
function resolvePath(p: string, cwd: string): string {
|
|
31
|
-
if (p.startsWith("~")) {
|
|
32
|
-
p = path.join(os.homedir(), p.slice(1));
|
|
33
|
-
}
|
|
34
|
-
return path.resolve(cwd, p);
|
|
35
|
-
}
|
|
36
|
-
|
|
37
|
-
function isPathMatch(targetPath: string, pattern: string, cwd: string): boolean {
|
|
38
|
-
// Simple glob-to-regex or substring match
|
|
39
|
-
// Expand tilde in pattern if present
|
|
40
|
-
const resolvedPattern = pattern.startsWith("~") ? path.join(os.homedir(), pattern.slice(1)) : pattern;
|
|
41
|
-
|
|
42
|
-
// If pattern ends with /, it's a directory match
|
|
43
|
-
if (resolvedPattern.endsWith("/")) {
|
|
44
|
-
const absolutePattern = path.isAbsolute(resolvedPattern) ? resolvedPattern : path.resolve(cwd, resolvedPattern);
|
|
45
|
-
return targetPath.startsWith(absolutePattern);
|
|
46
|
-
}
|
|
47
|
-
|
|
48
|
-
// Handle basic wildcards *
|
|
49
|
-
const regexPattern = resolvedPattern
|
|
50
|
-
.replace(/[.+^${}()|[\]\\]/g, "\\$&") // escape regex chars
|
|
51
|
-
.replace(/\*/g, ".*"); // convert * to .*
|
|
52
|
-
|
|
53
|
-
const regex = new RegExp(`^${regexPattern}$|^${regexPattern}/|/${regexPattern}$|/${regexPattern}/`);
|
|
54
|
-
|
|
55
|
-
// Match against absolute path and relative-to-cwd path
|
|
56
|
-
const relativePath = path.relative(cwd, targetPath);
|
|
57
|
-
|
|
58
|
-
return regex.test(targetPath) || regex.test(relativePath) || targetPath.includes(resolvedPattern) || relativePath.includes(resolvedPattern);
|
|
59
|
-
}
|
|
60
|
-
|
|
61
|
-
pi.on("session_start", async (_event, ctx) => {
|
|
62
|
-
const projectRulesPath = path.join(ctx.cwd, ".pi", "damage-control-rules.yaml");
|
|
63
|
-
const globalRulesPath = path.join(os.homedir(), ".pi", "damage-control-rules.yaml");
|
|
64
|
-
const rulesPath = fs.existsSync(projectRulesPath) ? projectRulesPath : fs.existsSync(globalRulesPath) ? globalRulesPath : null;
|
|
65
|
-
try {
|
|
66
|
-
if (rulesPath) {
|
|
67
|
-
const content = fs.readFileSync(rulesPath, "utf8");
|
|
68
|
-
const loaded = yamlParse(content) as Partial<Rules>;
|
|
69
|
-
rules = {
|
|
70
|
-
bashToolPatterns: loaded.bashToolPatterns || [],
|
|
71
|
-
zeroAccessPaths: loaded.zeroAccessPaths || [],
|
|
72
|
-
readOnlyPaths: loaded.readOnlyPaths || [],
|
|
73
|
-
noDeletePaths: loaded.noDeletePaths || [],
|
|
74
|
-
};
|
|
75
|
-
const source = rulesPath === projectRulesPath ? "project" : "global";
|
|
76
|
-
ctx.ui.notify(`🛡️ Damage-Control: Loaded ${rules.bashToolPatterns.length + rules.zeroAccessPaths.length + rules.readOnlyPaths.length + rules.noDeletePaths.length} rules (${source}).`);
|
|
77
|
-
} else {
|
|
78
|
-
ctx.ui.notify("🛡️ Damage-Control: No rules found at .pi/damage-control-rules.yaml (project or global)");
|
|
79
|
-
}
|
|
80
|
-
} catch (err) {
|
|
81
|
-
ctx.ui.notify(`🛡️ Damage-Control: Failed to load rules: ${err instanceof Error ? err.message : String(err)}`);
|
|
82
|
-
}
|
|
83
|
-
|
|
84
|
-
ctx.ui.setStatus(`🛡️ Damage-Control Active: ${rules.bashToolPatterns.length + rules.zeroAccessPaths.length + rules.readOnlyPaths.length + rules.noDeletePaths.length} Rules`);
|
|
85
|
-
});
|
|
86
|
-
|
|
87
|
-
pi.on("tool_call", async (event, ctx) => {
|
|
88
|
-
let violationReason: string | null = null;
|
|
89
|
-
let shouldAsk = false;
|
|
90
|
-
// The protected pattern that matched, set only for the path categories.
|
|
91
|
-
// Those can be pre-granted via the shared exemptions file agent-hub
|
|
92
|
-
// passes down (AGENT_HUB_EXEMPTIONS_FILE); destructive bashToolPatterns
|
|
93
|
-
// leave this null and are never exemptible.
|
|
94
|
-
let matchedPattern: string | null = null;
|
|
95
|
-
|
|
96
|
-
// 1. Check Zero Access Paths for all tools that use path or glob
|
|
97
|
-
const checkPaths = (pathsToCheck: string[]) => {
|
|
98
|
-
for (const p of pathsToCheck) {
|
|
99
|
-
const resolved = resolvePath(p, ctx.cwd);
|
|
100
|
-
for (const zap of rules.zeroAccessPaths) {
|
|
101
|
-
if (isPathMatch(resolved, zap, ctx.cwd)) {
|
|
102
|
-
matchedPattern = zap;
|
|
103
|
-
return `Access to zero-access path restricted: ${zap}`;
|
|
104
|
-
}
|
|
105
|
-
}
|
|
106
|
-
}
|
|
107
|
-
return null;
|
|
108
|
-
};
|
|
109
|
-
|
|
110
|
-
// Extract paths from tool input
|
|
111
|
-
const inputPaths: string[] = [];
|
|
112
|
-
if (isToolCallEventType("read", event) || isToolCallEventType("write", event) || isToolCallEventType("edit", event)) {
|
|
113
|
-
inputPaths.push(event.input.path);
|
|
114
|
-
} else if (isToolCallEventType("grep", event) || isToolCallEventType("find", event) || isToolCallEventType("ls", event)) {
|
|
115
|
-
inputPaths.push(event.input.path || ".");
|
|
116
|
-
}
|
|
117
|
-
|
|
118
|
-
if (isToolCallEventType("grep", event) && event.input.glob) {
|
|
119
|
-
// Check glob field as well
|
|
120
|
-
for (const zap of rules.zeroAccessPaths) {
|
|
121
|
-
if (event.input.glob.includes(zap) || isPathMatch(event.input.glob, zap, ctx.cwd)) {
|
|
122
|
-
violationReason = `Glob matches zero-access path: ${zap}`;
|
|
123
|
-
matchedPattern = zap;
|
|
124
|
-
break;
|
|
125
|
-
}
|
|
126
|
-
}
|
|
127
|
-
}
|
|
128
|
-
|
|
129
|
-
// find's required `pattern` is a filename glob (e.g. "*.env") — the `path` check
|
|
130
|
-
// above only sees the search root ("."), so check the pattern too, mirroring grep's glob.
|
|
131
|
-
if (!violationReason && isToolCallEventType("find", event) && event.input.pattern) {
|
|
132
|
-
for (const zap of rules.zeroAccessPaths) {
|
|
133
|
-
if (event.input.pattern.includes(zap) || isPathMatch(event.input.pattern, zap, ctx.cwd)) {
|
|
134
|
-
violationReason = `Find pattern matches zero-access path: ${zap}`;
|
|
135
|
-
matchedPattern = zap;
|
|
136
|
-
break;
|
|
137
|
-
}
|
|
138
|
-
}
|
|
139
|
-
}
|
|
140
|
-
|
|
141
|
-
if (!violationReason) {
|
|
142
|
-
violationReason = checkPaths(inputPaths);
|
|
143
|
-
}
|
|
144
|
-
|
|
145
|
-
// 2. Tool-specific logic
|
|
146
|
-
if (!violationReason) {
|
|
147
|
-
if (isToolCallEventType("bash", event)) {
|
|
148
|
-
const command = event.input.command;
|
|
149
|
-
|
|
150
|
-
// Check bashToolPatterns
|
|
151
|
-
for (const rule of rules.bashToolPatterns) {
|
|
152
|
-
const regex = new RegExp(rule.pattern);
|
|
153
|
-
if (regex.test(command)) {
|
|
154
|
-
violationReason = rule.reason;
|
|
155
|
-
shouldAsk = !!rule.ask;
|
|
156
|
-
break;
|
|
157
|
-
}
|
|
158
|
-
}
|
|
159
|
-
|
|
160
|
-
// Check if bash command interacts with restricted paths
|
|
161
|
-
if (!violationReason) {
|
|
162
|
-
for (const zap of rules.zeroAccessPaths) {
|
|
163
|
-
if (command.includes(zap)) {
|
|
164
|
-
violationReason = `Bash command references zero-access path: ${zap}`;
|
|
165
|
-
matchedPattern = zap;
|
|
166
|
-
break;
|
|
167
|
-
}
|
|
168
|
-
}
|
|
169
|
-
}
|
|
170
|
-
|
|
171
|
-
if (!violationReason) {
|
|
172
|
-
for (const rop of rules.readOnlyPaths) {
|
|
173
|
-
// Heuristic: check if command might modify a read-only path
|
|
174
|
-
// Redirects, sed -i, rm, mv to, etc.
|
|
175
|
-
if (command.includes(rop) && (/[\s>|]/.test(command) || command.includes("rm") || command.includes("mv") || command.includes("sed"))) {
|
|
176
|
-
violationReason = `Bash command may modify read-only path: ${rop}`;
|
|
177
|
-
matchedPattern = rop;
|
|
178
|
-
break;
|
|
179
|
-
}
|
|
180
|
-
}
|
|
181
|
-
}
|
|
182
|
-
|
|
183
|
-
if (!violationReason) {
|
|
184
|
-
for (const ndp of rules.noDeletePaths) {
|
|
185
|
-
if (command.includes(ndp) && (command.includes("rm") || command.includes("mv"))) {
|
|
186
|
-
violationReason = `Bash command attempts to delete/move protected path: ${ndp}`;
|
|
187
|
-
matchedPattern = ndp;
|
|
188
|
-
break;
|
|
189
|
-
}
|
|
190
|
-
}
|
|
191
|
-
}
|
|
192
|
-
} else if (isToolCallEventType("write", event) || isToolCallEventType("edit", event)) {
|
|
193
|
-
// Check Read-Only paths
|
|
194
|
-
for (const p of inputPaths) {
|
|
195
|
-
const resolved = resolvePath(p, ctx.cwd);
|
|
196
|
-
for (const rop of rules.readOnlyPaths) {
|
|
197
|
-
if (isPathMatch(resolved, rop, ctx.cwd)) {
|
|
198
|
-
violationReason = `Modification of read-only path restricted: ${rop}`;
|
|
199
|
-
matchedPattern = rop;
|
|
200
|
-
break;
|
|
201
|
-
}
|
|
202
|
-
}
|
|
203
|
-
}
|
|
204
|
-
}
|
|
205
|
-
}
|
|
206
|
-
|
|
207
|
-
if (violationReason) {
|
|
208
|
-
// Pre-granted exemptions from the hub session's shared file
|
|
209
|
-
// (AGENT_HUB_EXEMPTIONS_FILE, written by /allow or an approved
|
|
210
|
-
// escalation in the dispatcher). This is the ONLY unlock the
|
|
211
|
-
// hard-stop variant honors — no prompting, no escalation — and it
|
|
212
|
-
// applies to path categories only, never to bashToolPatterns.
|
|
213
|
-
if (matchedPattern) {
|
|
214
|
-
const command = isToolCallEventType("bash", event) ? event.input.command : null;
|
|
215
|
-
const applies = (ex: Exemption) =>
|
|
216
|
-
ex.pattern === matchedPattern ||
|
|
217
|
-
(command !== null && command.includes(ex.pattern)) ||
|
|
218
|
-
inputPaths.some((p) => isPathMatch(resolvePath(p, ctx.cwd), ex.pattern, ctx.cwd));
|
|
219
|
-
const exempted = fileExemptionsFor(process.env[EXEMPTIONS_FILE_ENV], process.env[AGENT_ID_ENV]).find(applies);
|
|
220
|
-
if (exempted) {
|
|
221
|
-
pi.appendEntry("damage-control-log", { tool: event.toolName, input: event.input, rule: violationReason, action: "exempted", pattern: exempted.pattern, scope: exempted.scope });
|
|
222
|
-
ctx.ui.notify(`🛡️ Damage-Control: ${event.toolName} allowed by exemption ${exempted.pattern} (${exempted.scope})`);
|
|
223
|
-
return { block: false };
|
|
224
|
-
}
|
|
225
|
-
}
|
|
226
|
-
|
|
227
|
-
if (shouldAsk) {
|
|
228
|
-
const confirmed = await ctx.ui.confirm("🛡️ Damage-Control Confirmation", `Dangerous command detected: ${violationReason}\n\nCommand: ${isToolCallEventType("bash", event) ? event.input.command : JSON.stringify(event.input)}\n\nDo you want to proceed?`, { timeout: 30000 });
|
|
229
|
-
|
|
230
|
-
if (!confirmed) {
|
|
231
|
-
ctx.ui.setStatus(`⚠️ Last Violation Blocked: ${violationReason.slice(0, 30)}...`);
|
|
232
|
-
pi.appendEntry("damage-control-log", { tool: event.toolName, input: event.input, rule: violationReason, action: "blocked_by_user" });
|
|
233
|
-
ctx.abort();
|
|
234
|
-
return { block: true, reason: `🛑 BLOCKED by Damage-Control: ${violationReason} (User denied)\n\nDO NOT attempt to work around this restriction. DO NOT retry with alternative commands, paths, or approaches that achieve the same result. Report this block to the user exactly as stated and ask how they would like to proceed.` };
|
|
235
|
-
} else {
|
|
236
|
-
pi.appendEntry("damage-control-log", { tool: event.toolName, input: event.input, rule: violationReason, action: "confirmed_by_user" });
|
|
237
|
-
return { block: false };
|
|
238
|
-
}
|
|
239
|
-
} else {
|
|
240
|
-
ctx.ui.notify(`🛑 Damage-Control: Blocked ${event.toolName} due to ${violationReason}`);
|
|
241
|
-
ctx.ui.setStatus(`⚠️ Last Violation: ${violationReason.slice(0, 30)}...`);
|
|
242
|
-
pi.appendEntry("damage-control-log", { tool: event.toolName, input: event.input, rule: violationReason, action: "blocked" });
|
|
243
|
-
ctx.abort();
|
|
244
|
-
return { block: true, reason: `🛑 BLOCKED by Damage-Control: ${violationReason}\n\nDO NOT attempt to work around this restriction. DO NOT retry with alternative commands, paths, or approaches that achieve the same result. Report this block to the user exactly as stated and ask how they would like to proceed.` };
|
|
245
|
-
}
|
|
246
|
-
}
|
|
247
|
-
|
|
248
|
-
return { block: false };
|
|
249
|
-
});
|
|
250
|
-
}
|