@chankov/agent-fleet 2.2.2 → 2.2.3
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/.pi/harnesses/agent-hub/README.md +18 -2
- package/.pi/harnesses/agent-hub/budget-recovery.ts +28 -0
- package/.pi/harnesses/agent-hub/commands/recover.ts +28 -9
- package/.pi/harnesses/agent-hub/context/assertion-journal.ts +133 -0
- package/.pi/harnesses/agent-hub/index.ts +100 -17
- package/.pi/harnesses/agent-hub/no-progress.ts +133 -19
- package/.pi/harnesses/agent-hub/operator-current-state.ts +51 -6
- package/.pi/harnesses/agent-hub/package.json +1 -1
- package/.pi/harnesses/agent-hub/policy/work-mode.ts +2 -1
- package/.pi/harnesses/agent-hub/process-obligations.ts +1 -1
- package/.pi/harnesses/agent-hub/recover-policy.ts +1 -1
- package/.pi/harnesses/agent-hub/recover-state.ts +46 -6
- package/.pi/harnesses/agent-hub/recovery-continuation.ts +134 -0
- package/.pi/harnesses/agent-hub/tools/action-executors.ts +24 -3
- package/.pi/harnesses/agent-hub/tools/context.ts +2 -0
- package/.pi/harnesses/agent-hub/tools/dispatch-execution.ts +60 -17
- package/.pi/harnesses/agent-hub/tools/execution-orchestration.ts +2 -1
- package/.pi/harnesses/agent-hub/tools/recover-task.ts +16 -0
- package/.pi/harnesses/agent-hub/verification-diagnostics.ts +23 -0
- package/.pi/harnesses/agent-hub/work-mode.ts +4 -2
- package/.pi/harnesses/coms/package.json +1 -1
- package/.pi/harnesses/damage-control-continue/index.ts +7 -5
- package/.pi/harnesses/damage-control-continue/package.json +1 -1
- package/.pi/harnesses/lib/bash-policy-analysis.ts +9 -1
- package/.pi/harnesses/lib/exact-permission-port.ts +6 -4
- package/.versions/2.2.3/.pi/agent-fleet/hermes/README.md +347 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/desktop-plugins/agent-fleet-herdr/plugin.js +1291 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/desktop-plugins/agent-fleet-herdr/presentation.js +672 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/gates/gate-o-capability.md +8 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/gates/gate-o-validator-fixtures.json +1 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/activity.py +773 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/coms_registry.py +134 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/coms_send.py +350 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/herdr_source.py +193 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/manifest.json +4 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/plugin_api.py +444 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/sessions.py +205 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/tasks.py +300 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/watch.py +819 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/plugin.yaml +8 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +139 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/skills/hub-conductor/SKILL.md +84 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/skills/hub-liaison/SKILL.md +84 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/skills/hub-watchdog/SKILL.md +76 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/skills/hub-watchdog/manifest.json +1 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog.py +249 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_actions.py +124 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_contract.py +76 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_delivery.py +10 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_engine.py +128 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_judgment.py +41 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_recovery.py +103 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_state.py +163 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_transport.py +138 -0
- package/.versions/2.2.3/.pi/agent-fleet/hermes/watchdog-tests/__init__.py +0 -0
- package/.versions/2.2.3/.pi/agent-fleet/hooks/coms-stop-hook.mjs +124 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/claude-code-preflight.ts +70 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/coms-claude-bridge.ts +440 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/coms-cli.ts +430 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/coms-hermes-bridge.ts +416 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/exec-at-target.ts +10 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/fixtures/codex-notification-contracts/0.167-shared.json +1900 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/fixtures/codex-notification-contracts/README.md +223 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/fixtures/codex-notification-contracts/assessment.md +83 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/fixtures/codex-notification-contracts/bootstrap-profile-0.167.json +5627 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/fixtures/codex-notification-contracts/bootstrap-profile.md +43 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/fixtures/codex-notification-contracts/bootstrap.md +45 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/fixtures/codex-notification-contracts/capture-profile.ts +53 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/fixtures/codex-notification-contracts/capture.ts +102 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/fixtures/codex-notification-contracts/catalog.md +91 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/fixtures/codex-notification-contracts/channel.md +21 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/fixtures/codex-notification-contracts/measurement.md +133 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/fixtures/codex-notification-contracts/measurements.json +74 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/fixtures/codex-notification-contracts/notification-profile-0.167.json +2679 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/fixtures/codex-notification-contracts/observer.md +101 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/fixtures/codex-notification-contracts/opaque-response.md +57 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/fixtures/codex-notification-contracts/open-sent.md +68 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/fixtures/codex-notification-contracts/probe-reader.md +51 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/fixtures/codex-notification-contracts/profile.md +71 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/fixtures/codex-notification-contracts/projection.md +147 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/fixtures/codex-notification-contracts/reconnect.md +40 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/fixtures/codex-notification-contracts/response-unions.md +74 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/fixtures/codex-notification-contracts/semver.md +124 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/fixtures/codex-notification-contracts/surface.md +73 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/fixtures/fleet-codex-allowlist-store-child.ts +31 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/fixtures/response-fixture.ts +23 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/fleet-codex-local-mcp.mjs +26 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/fleet-codex-local-mcp.ts +63 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/fleet.ts +244 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/flow.ts +166 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/hermes-monitor-capability-runner.ts +25 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/hermes-monitor-scenario.ts +474 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/hermes-watchdog-capability-probe.ts +45 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/install-hermes-plugin.sh +180 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/claude-bridge-core.ts +208 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/codex-bootstrap-files.ts +46 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/codex-bootstrap-probe.ts +52 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/codex-bootstrap-producer.ts +131 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/codex-connection-history.ts +51 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/codex-daemon-observer.ts +137 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/codex-desktop-discovery.ts +84 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/codex-desktop-preflight.ts +130 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/codex-desktop-queue-host.ts +113 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/codex-measurement.ts +218 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/codex-native-presence.ts +61 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/codex-probe-transcript.ts +135 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/codex-send-lineage.ts +72 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/codex-unix-queue-rpc.ts +101 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/coms-envelope.ts +582 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/fake-herdr-server.ts +88 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/fleet-codex-allowlist-store.ts +453 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/fleet-codex-allowlist.ts +175 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/fleet-codex-answer-transport.ts +73 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/fleet-codex-answers.ts +74 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/fleet-codex-bootstrap.ts +207 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/fleet-codex-connections.ts +76 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/fleet-codex-event-reply.ts +58 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/fleet-codex-event-runtime.ts +132 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/fleet-codex-instruction-store.ts +428 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/fleet-codex-instruction-transport.ts +160 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/fleet-codex-instructions.ts +175 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/fleet-codex-local-mcp.ts +435 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/fleet-codex-native-history.ts +215 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/fleet-codex-observation-store.ts +208 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/fleet-codex-observe-transport.ts +49 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/fleet-codex-observe.ts +93 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/fleet-codex-overview.ts +52 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/fleet-codex-permission-transport.ts +44 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/fleet-codex-permissions.ts +83 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/fleet-codex-readonly.ts +213 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/fleet-codex-relay-latency.ts +45 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/fleet-codex-response-read.ts +26 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/fleet-codex-response-transport.ts +38 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/fleet-codex-resync.ts +212 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/fleet-command.ts +264 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/flow-command.ts +107 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/flow-maintenance.ts +239 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/herdr-layout.ts +281 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/hermes-bridge-core.ts +241 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/hermes-monitor-events.ts +1 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/hermes-monitor-herdr.ts +2 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/hermes-monitor-model.ts +3 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/hermes-monitor-registry.ts +2 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/hermes-monitor-socket.ts +2 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/hermes-monitor-store.ts +2 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/monitor-env.ts +146 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/peer-launch.ts +318 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/peer-target.ts +1 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/persona-banner.ts +62 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/persona-dirs.ts +25 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/resource-closure.js +1 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/runtime-dependencies.js +124 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/session-launch.ts +56 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/spawn-stagger.ts +101 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/team-project.ts +176 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/lib/team-snapshot.ts +160 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/package-lock.json +57 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/package.json +10 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/peer-banner.ts +41 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/peer-launch.ts +289 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/pi-session.ts +9 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/team-snapshot.ts +245 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/team-up.ts +378 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/workflows/lib/agent-phase.ts +181 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/workflows/lib/changes.ts +61 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/workflows/lib/debate.ts +149 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/workflows/lib/env.ts +36 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/workflows/lib/envelopes.ts +169 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/workflows/lib/gates.ts +81 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/workflows/lib/git.ts +108 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/workflows/lib/isolated-snapshot.ts +130 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/workflows/lib/merge.ts +95 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/workflows/lib/model-profile.ts +22 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/workflows/lib/model-visibility.ts +92 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/workflows/lib/permissions.ts +137 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/workflows/lib/personas.ts +57 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/workflows/lib/poll.ts +86 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/workflows/lib/project-policy.ts +37 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/workflows/lib/quality.ts +78 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/workflows/lib/run.ts +109 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/workflows/lib/scout-data-boundary.ts +55 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/workflows/lib/trace.ts +52 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/workflows/lib/voices.ts +128 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/workflows/lib/writer-lease-race.worker.mjs +36 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/workflows/lib/writer-lease.ts +148 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/workflows/tsconfig.json +22 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/workflows/wf-build-test.ts +61 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/workflows/wf-debate.ts +87 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/workflows/wf-document.ts +50 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/workflows/wf-poll.ts +95 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/workflows/wf-quality.ts +20 -0
- package/.versions/2.2.3/.pi/agent-fleet/scripts/workflows/wf-scout.ts +40 -0
- package/.versions/2.2.3/.pi/agents/dispatch-policy.yaml +32 -0
- package/.versions/2.2.3/.pi/agents/model-profiles.yaml +132 -0
- package/.versions/2.2.3/.pi/agents/peers.yaml +147 -0
- package/.versions/2.2.3/.pi/agents/teams.yaml +41 -0
- package/.versions/2.2.3/.pi/agents/voices.yaml +13 -0
- package/.versions/2.2.3/.pi/damage-control-rules.yaml +297 -0
- package/.versions/2.2.3/.pi/extensions/btw/README.md +120 -0
- package/.versions/2.2.3/.pi/extensions/btw/index.ts +916 -0
- package/.versions/2.2.3/.pi/extensions/btw/package.json +6 -0
- package/.versions/2.2.3/.pi/extensions/btw/state.js +179 -0
- package/.versions/2.2.3/.pi/extensions/chrome-devtools-mcp/README.md +55 -0
- package/.versions/2.2.3/.pi/extensions/chrome-devtools-mcp/index.ts +93 -0
- package/.versions/2.2.3/.pi/extensions/chrome-devtools-mcp/package.json +6 -0
- package/.versions/2.2.3/.pi/extensions/compact-and-continue/README.md +42 -0
- package/.versions/2.2.3/.pi/extensions/compact-and-continue/index.ts +136 -0
- package/.versions/2.2.3/.pi/extensions/compact-and-continue/package.json +6 -0
- package/.versions/2.2.3/.pi/extensions/mcp-bridge/README.md +46 -0
- package/.versions/2.2.3/.pi/extensions/mcp-bridge/index.ts +206 -0
- package/.versions/2.2.3/.pi/extensions/mcp-bridge/package.json +6 -0
- package/.versions/2.2.3/.pi/extensions/package-lock.json +1175 -0
- package/.versions/2.2.3/.pi/extensions/package.json +9 -0
- package/.versions/2.2.3/.pi/extensions/pi-voice-stt/README.md +224 -0
- package/.versions/2.2.3/.pi/extensions/pi-voice-stt/config.ts +199 -0
- package/.versions/2.2.3/.pi/extensions/pi-voice-stt/examples/stt.json +35 -0
- package/.versions/2.2.3/.pi/extensions/pi-voice-stt/index.ts +248 -0
- package/.versions/2.2.3/.pi/extensions/pi-voice-stt/package.json +6 -0
- package/.versions/2.2.3/.pi/extensions/pi-voice-stt/providers.ts +214 -0
- package/.versions/2.2.3/.pi/extensions/pi-voice-stt/recorder.ts +158 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/README.md +1657 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/acceptance.ts +204 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/access-approval.ts +266 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/action-authorization.ts +10 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/agentic-contract.ts +43 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/agentic-evidence.ts +64 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/agentic-hub.ts +55 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/agentic-runtime.ts +56 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/agentic-sources-worker.mjs +4 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/agentic-sources.ts +74 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/agentic-state.ts +23 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/approval-wait.ts +1 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/artifacts.js +146 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/assertion-ledger.js +68 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/assist-profile.ts +19 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/backend-policy.js +174 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/bounded-output.ts +26 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/budget-recovery.ts +151 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/capability-confirmation.ts +47 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/capability-packs.ts +187 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/codex-bootstrap.ts +117 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/commands/agent-model-thinking.ts +10 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/commands/agent-model.ts +10 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/commands/agent-models-substitute.ts +10 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/commands/agents-add.ts +9 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/commands/agents-drop.ts +9 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/commands/agents-history.ts +9 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/commands/agents-kill.ts +10 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/commands/agents-list.ts +9 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/commands/agents-restart.ts +10 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/commands/agents-save.ts +9 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/commands/agents-team.ts +9 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/commands/audit.ts +9 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/commands/compound.ts +9 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/commands/coms.ts +9 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/commands/config.ts +9 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/commands/context-command.ts +9 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/commands/context.ts +43 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/commands/debate.ts +9 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/commands/dispatch-policy.ts +9 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/commands/handoff.ts +10 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/commands/hub-report.ts +9 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/commands/models.ts +10 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/commands/poll.ts +9 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/commands/recover.ts +81 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/commands/retry.ts +10 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/commands/task-triage-recover.ts +12 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/commands/task-triage-waive.ts +12 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/commands/watchdog.ts +9 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/commands/zoom.ts +10 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/config/agents.ts +183 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/config/model-profiles.ts +240 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/config/overrides.ts +166 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/context/agent-state.ts +30 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/context/assertion-journal.ts +133 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/context/assertions-artifacts.ts +234 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/context/budgets.ts +152 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/context/hub-state.ts +40 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/context-budget-snapshot.ts +105 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/context-compaction-monitor.ts +35 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/context-compaction-preflight.ts +21 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/context-compaction-runtime.ts +69 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/context-compaction.ts +34 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/context-continuity-broker.ts +44 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/context-continuity-child.ts +83 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/context-continuity-client.ts +22 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/context-continuity-compat.ts +45 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/context-continuity-owners.ts +17 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/context-continuity-registry.ts +8 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/context-continuity.ts +82 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/context-pressure.ts +222 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/context-window.js +108 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/damage-guard-approval.ts +83 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/damage-guard-broker.ts +125 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/damage-guard-contract.ts +22 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/damage-guard-descendant.ts +76 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/damage-guard-hub.ts +263 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/damage-guard-identity.ts +12 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/damage-guard-owners.ts +59 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/damage-guard-state.ts +43 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/damage-guard-test-tsconfig.json +19 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/debate-command.ts +176 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/delegate.ts +478 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/deterministic-fs.ts +195 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/diagnostic-probe-extension.ts +26 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/diagnostic-series-budget.ts +178 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/dispatch-coms.ts +258 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/dispatch-core.ts +27 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/dispatch-native-complete.ts +176 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/dispatch-native-prepare.ts +318 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/dispatch-native-spawn.ts +264 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/dispatch-native-types.ts +297 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/dispatch-native.ts +242 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/dispatch-observability.ts +225 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/dispatch-triage-contract.ts +27 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/dispatch-triage-eval.ts +77 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/dispatch-triage-policy.ts +29 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/dispatch-triage-runtime.ts +55 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/dispatch-triage-state.ts +33 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/docs-lane.js +123 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/drift-judge.ts +352 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/drift-runtime.ts +480 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/drift-system1-policy.ts +39 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/drift-system1.ts +469 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/drift-watchdog.js +344 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/evidence-manifest.ts +51 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/evidence-rules.js +96 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/execution-evidence.ts +96 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/execution-trace.ts +241 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/external-blocker.js +92 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/file-discovery/adapters.ts +88 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/file-discovery/broker-client.ts +62 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/file-discovery/broker.ts +128 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/file-discovery/child-extension.ts +42 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/file-discovery/descendant.ts +67 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/file-discovery/discovery-worker.mjs +15 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/file-discovery/discovery.ts +126 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/file-discovery/evaluate.ts +57 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/file-discovery/hub.ts +170 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/file-discovery/native-context.ts +8 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/file-discovery/native-fixture.test-support.ts +108 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/file-discovery/owners.ts +100 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/file-discovery/results.ts +55 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/file-discovery/runtime.ts +130 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/file-discovery/semantic-profiles.ts +18 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/file-discovery/sources.ts +69 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/file-discovery/state.ts +22 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/filesystem-tool.ts +166 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/fixtures/registration-surface.json +69 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/fixtures/t0a-synthetic/catalog.ts +189 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/footer.ts +29 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/helpers.ts +269 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/history-projection.ts +116 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/hub-state-audit.js +41 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/index.ts +2805 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/input/completions.ts +82 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/input/shortcuts.ts +16 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/lifecycle/context-pressure.ts +231 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/lifecycle/monitor-session.ts +104 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/lifecycle/session-orchestration.ts +143 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/lifecycle/turn-handlers.ts +90 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/monitor-invoke-journal.ts +131 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/monitor-invoke.ts +92 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/monitor-session-bridge.ts +266 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/no-progress.ts +741 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/operator-current-state.ts +102 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/operator-watchdog.ts +97 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/orchestration-activation.ts +109 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/orchestration-metrics.ts +78 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/orchestration-route.ts +68 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/package.json +7 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/peer-spawn-plan.ts +116 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/permission-channel.ts +87 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/permission-relay.ts +84 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/policy/models.ts +153 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/policy/profile-activation.ts +62 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/policy/profile-runtime.ts +120 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/policy/roster.ts +103 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/policy/work-mode.ts +104 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/poll-command.ts +184 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/presentation.ts +54 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/private-config-current-state.ts +81 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/private-config-fixtures.ts +26 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/private-config-review.ts +100 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/proactive-config.ts +22 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/proactive-evaluate.ts +138 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/proactive-external-git.ts +82 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/proactive-external.ts +142 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/proactive-feedback.ts +104 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/proactive-findings.ts +115 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/proactive-local.ts +89 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/proactive-observer.ts +106 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/proactive-rules.ts +171 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/proactive-runtime.ts +318 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/proactive-selection.ts +68 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/proactive-snapshot-worker.mjs +12 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/proactive-snapshot.ts +287 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/proactive-types.ts +70 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/process-obligations.ts +210 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/prompts/context.ts +72 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/prompts/fragments.ts +94 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/prompts/session-start.ts +89 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/prompts/system-prompt.ts +142 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/provider-semaphore.js +143 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/reconcile.ts +26 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/recover-policy.ts +44 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/recover-state.ts +144 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/recovery-continuation.ts +134 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/recovery-contract.ts +151 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/rerun-policy.ts +40 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/research/controls.ts +74 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/research/runtime.ts +215 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/research/spawn-run.ts +221 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/return-contract.js +371 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/return-extract.js +77 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/review-closure.ts +43 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/review-continuity.ts +76 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/review-findings.js +96 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/review-reuse.ts +48 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/review-verdict.ts +6 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/routing-observation.ts +41 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/routing-proposal.ts +46 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/run-budget.js +362 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/run-namespace.js +93 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/runtime-receipts.ts +63 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/runtime-test-check.ts +85 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/safety-routing.ts +28 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/scope-gate.js +271 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/scope-overlap.ts +46 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/session-audit.ts +331 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/session-health.js +110 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/session-start.ts +42 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/spawn.ts +702 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/specialist-result-receipt.ts +13 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/specialist-result.ts +78 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/system1-activity.ts +625 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/system1-communication-store.ts +225 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/system1-report.ts +275 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/system1-runtime.ts +271 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/task-brief.ts +98 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/task-continuation.ts +4 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/task-resume-contract.ts +80 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/task-triage-authorization.ts +170 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/task-triage-config.ts +21 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/task-triage-contract.ts +14 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/task-triage-live-stage-boundary.mjs +49 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/task-triage-obligations.ts +120 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/task-triage-policy.ts +16 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/task-triage-review-contract.mjs +43 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/task-triage-reviewer-only-contract.mjs +156 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/task-triage-reviewer-only-diagnostics.mjs +112 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/task-triage-runtime.ts +132 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/task-triage-stage-guard.ts +21 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/task-triage-state.ts +46 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/timeline.ts +72 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/tool-catalog-runtime.ts +83 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/tool-catalog-state.ts +125 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/tool-protocol.ts +134 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/tools/action-executors.ts +237 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/tools/ask-system1-files.ts +15 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/tools/ask-system1.ts +25 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/tools/coms-tools.ts +139 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/tools/context.ts +151 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/tools/dispatch-agent.ts +93 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/tools/dispatch-execution.ts +971 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/tools/dispatch-triage.ts +16 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/tools/execution-orchestration.ts +23 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/tools/fleet-tools.ts +201 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/tools/herdr-executors.ts +100 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/tools/poll-panel-core.ts +30 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/tools/poll-panel.ts +33 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/tools/recover-task.ts +16 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/tools/run-flow.ts +177 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/tools/set-task-tier.ts +31 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/tools/spawn-research.ts +67 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/tools/team-adjust.ts +29 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/tools/verification-contract.ts +81 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/tsconfig.json +22 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/types.ts +66 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/ui/activity-dots.ts +25 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/ui/context-budget.ts +89 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/ui/detail-panel.ts +192 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/ui/fleet-actions.ts +78 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/ui/fleet-dashboard.ts +173 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/ui/fleet-editor.ts +44 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/ui/fleet-source.ts +179 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/ui/grid.ts +159 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/ui/history-store.ts +137 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/ui/history.ts +234 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/ui/pool.ts +103 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/ui/running-strip.ts +2 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/ui/system1-communication.ts +59 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/ui/zoom.ts +206 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/unknown-tool-counter.ts +116 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/verification-diagnostics.ts +23 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/version.ts +42 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/watchdog-evaluation.ts +110 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/work-mode.ts +185 -0
- package/.versions/2.2.3/.pi/harnesses/agent-hub/write-isolation.ts +232 -0
- package/.versions/2.2.3/.pi/harnesses/ask-user-remote/README.md +59 -0
- package/.versions/2.2.3/.pi/harnesses/ask-user-remote/index.ts +571 -0
- package/.versions/2.2.3/.pi/harnesses/ask-user-remote/questions.ts +206 -0
- package/.versions/2.2.3/.pi/harnesses/ask-user-remote/race-core.js +124 -0
- package/.versions/2.2.3/.pi/harnesses/ask-user-remote/runtime-ask.ts +90 -0
- package/.versions/2.2.3/.pi/harnesses/coms/README.md +105 -0
- package/.versions/2.2.3/.pi/harnesses/coms/index.ts +308 -0
- package/.versions/2.2.3/.pi/harnesses/coms/package.json +7 -0
- package/.versions/2.2.3/.pi/harnesses/coms/version.ts +42 -0
- package/.versions/2.2.3/.pi/harnesses/damage-control-continue/README.md +161 -0
- package/.versions/2.2.3/.pi/harnesses/damage-control-continue/index.ts +661 -0
- package/.versions/2.2.3/.pi/harnesses/damage-control-continue/package.json +7 -0
- package/.versions/2.2.3/.pi/harnesses/damage-control-continue/result-screen.ts +98 -0
- package/.versions/2.2.3/.pi/harnesses/damage-control-continue/system1-child.ts +45 -0
- package/.versions/2.2.3/.pi/harnesses/damage-control-continue/system1-client.ts +85 -0
- package/.versions/2.2.3/.pi/harnesses/damage-control-continue/system1-guard.ts +65 -0
- package/.versions/2.2.3/.pi/harnesses/damage-control-continue/version.ts +42 -0
- package/.versions/2.2.3/.pi/harnesses/lib/approval-wait.ts +17 -0
- package/.versions/2.2.3/.pi/harnesses/lib/bash-policy-analysis.ts +193 -0
- package/.versions/2.2.3/.pi/harnesses/lib/changed-file-diagnostics.ts +642 -0
- package/.versions/2.2.3/.pi/harnesses/lib/clarification-policy.ts +9 -0
- package/.versions/2.2.3/.pi/harnesses/lib/codex-compat.ts +97 -0
- package/.versions/2.2.3/.pi/harnesses/lib/codex-contract.ts +259 -0
- package/.versions/2.2.3/.pi/harnesses/lib/codex-notification-profile.ts +75 -0
- package/.versions/2.2.3/.pi/harnesses/lib/coms-core-io.ts +422 -0
- package/.versions/2.2.3/.pi/harnesses/lib/coms-core.ts +738 -0
- package/.versions/2.2.3/.pi/harnesses/lib/coms-instruction-receipts.ts +113 -0
- package/.versions/2.2.3/.pi/harnesses/lib/coms-observation.ts +74 -0
- package/.versions/2.2.3/.pi/harnesses/lib/coms-registry-entry.ts +99 -0
- package/.versions/2.2.3/.pi/harnesses/lib/coms-response-read.ts +107 -0
- package/.versions/2.2.3/.pi/harnesses/lib/context-budget-child-prompt.ts +214 -0
- package/.versions/2.2.3/.pi/harnesses/lib/context-budget-hub-prompt.ts +124 -0
- package/.versions/2.2.3/.pi/harnesses/lib/context-budget-view.ts +112 -0
- package/.versions/2.2.3/.pi/harnesses/lib/context-budget.ts +114 -0
- package/.versions/2.2.3/.pi/harnesses/lib/context-compaction-policy.js +35 -0
- package/.versions/2.2.3/.pi/harnesses/lib/damage-action-hash.ts +28 -0
- package/.versions/2.2.3/.pi/harnesses/lib/damage-auto-policy.ts +52 -0
- package/.versions/2.2.3/.pi/harnesses/lib/damage-control-presentation.ts +14 -0
- package/.versions/2.2.3/.pi/harnesses/lib/damage-control-shared.ts +276 -0
- package/.versions/2.2.3/.pi/harnesses/lib/damage-guard-port.ts +25 -0
- package/.versions/2.2.3/.pi/harnesses/lib/damage-policy.ts +35 -0
- package/.versions/2.2.3/.pi/harnesses/lib/damage-result-evidence.ts +25 -0
- package/.versions/2.2.3/.pi/harnesses/lib/damage-result-view.ts +16 -0
- package/.versions/2.2.3/.pi/harnesses/lib/deterministic-handle-path.ts +25 -0
- package/.versions/2.2.3/.pi/harnesses/lib/exact-permission-port.ts +40 -0
- package/.versions/2.2.3/.pi/harnesses/lib/execution-trace.ts +45 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fixtures/context-budget-profiles.json +11 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fixtures/hub-prompt-operator.legacy.txt +73 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fixtures/hub-prompt-orchestrator.legacy.txt +73 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fleet-bootstrap-channel.ts +148 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fleet-codex-catalog.ts +30 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fleet-codex-chat-view.ts +55 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fleet-codex-event-bridge.ts +82 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fleet-codex-namespace.ts +2 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fleet-codex-policy-snapshot.ts +10 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fleet-config/cli-bridge.ts +111 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fleet-config/mutations.ts +201 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fleet-config/snapshot.ts +417 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fleet-config/transition.ts +68 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fleet-config/ui.ts +269 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fleet-config/view.ts +338 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fleet-connection-control.ts +94 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fleet-connection-diagnostics.ts +7 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fleet-dashboard-ops.ts +178 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fleet-dashboard-view.ts +174 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fleet-detail-view.ts +339 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fleet-event-source.ts +21 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fleet-notification-admission.ts +32 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fleet-notification-bootstrap.ts +172 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fleet-notification-validation.ts +122 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fleet-overlay.ts +26 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fleet-panel.ts +34 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fleet-question-reference.ts +42 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fleet-read-model.ts +609 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fleet-selection.ts +24 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fleet-strip-controller.ts +75 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fleet-strip-view.ts +179 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fleet-target-identity.ts +9 -0
- package/.versions/2.2.3/.pi/harnesses/lib/fleet-transcript-store.ts +244 -0
- package/.versions/2.2.3/.pi/harnesses/lib/herdr-client.ts +472 -0
- package/.versions/2.2.3/.pi/harnesses/lib/herdr-presence.ts +399 -0
- package/.versions/2.2.3/.pi/harnesses/lib/hermes-monitor-events.ts +136 -0
- package/.versions/2.2.3/.pi/harnesses/lib/hermes-monitor-herdr.ts +28 -0
- package/.versions/2.2.3/.pi/harnesses/lib/hermes-monitor-model.ts +18 -0
- package/.versions/2.2.3/.pi/harnesses/lib/hermes-monitor-registry.ts +6 -0
- package/.versions/2.2.3/.pi/harnesses/lib/hermes-monitor-socket.ts +163 -0
- package/.versions/2.2.3/.pi/harnesses/lib/hermes-monitor-store.ts +31 -0
- package/.versions/2.2.3/.pi/harnesses/lib/identical-dialog.ts +27 -0
- package/.versions/2.2.3/.pi/harnesses/lib/installation-state.js +62 -0
- package/.versions/2.2.3/.pi/harnesses/lib/peer-target.ts +24 -0
- package/.versions/2.2.3/.pi/harnesses/lib/policy-roots.js +117 -0
- package/.versions/2.2.3/.pi/harnesses/lib/policy-roots.ts +32 -0
- package/.versions/2.2.3/.pi/harnesses/lib/process-shared.ts +9 -0
- package/.versions/2.2.3/.pi/harnesses/lib/resource-closure.js +26 -0
- package/.versions/2.2.3/.pi/harnesses/lib/safe-source-read.js +29 -0
- package/.versions/2.2.3/.pi/harnesses/lib/semantic-approval.ts +80 -0
- package/.versions/2.2.3/.pi/harnesses/lib/session-target.ts +62 -0
- package/.versions/2.2.3/.pi/harnesses/lib/spawned-peers.js +191 -0
- package/.versions/2.2.3/.pi/harnesses/lib/system1/config-agentic.js +15 -0
- package/.versions/2.2.3/.pi/harnesses/lib/system1/config-context-compaction.js +16 -0
- package/.versions/2.2.3/.pi/harnesses/lib/system1/config-damage-guard.js +24 -0
- package/.versions/2.2.3/.pi/harnesses/lib/system1/config-file-discovery.js +23 -0
- package/.versions/2.2.3/.pi/harnesses/lib/system1/config-json.js +37 -0
- package/.versions/2.2.3/.pi/harnesses/lib/system1/config-loader.js +53 -0
- package/.versions/2.2.3/.pi/harnesses/lib/system1/config-proactive.js +68 -0
- package/.versions/2.2.3/.pi/harnesses/lib/system1/config-triage.js +42 -0
- package/.versions/2.2.3/.pi/harnesses/lib/system1/config-v2.js +112 -0
- package/.versions/2.2.3/.pi/harnesses/lib/system1/config.js +50 -0
- package/.versions/2.2.3/.pi/harnesses/lib/system1/contracts.ts +154 -0
- package/.versions/2.2.3/.pi/harnesses/lib/system1/demo.ts +95 -0
- package/.versions/2.2.3/.pi/harnesses/lib/system1/jev.ts +503 -0
- package/.versions/2.2.3/.pi/harnesses/lib/system1/payload-screen.ts +65 -0
- package/.versions/2.2.3/.pi/harnesses/lib/system1/selection.js +11 -0
- package/.versions/2.2.3/.pi/harnesses/lib/system1/service.ts +245 -0
- package/.versions/2.2.3/.pi/harnesses/lib/system1/worktree-scopes.js +110 -0
- package/.versions/2.2.3/.pi/harnesses/lib/system1/worktree-scopes.ts +13 -0
- package/.versions/2.2.3/.pi/harnesses/lib/system1/worktree-service.ts +24 -0
- package/.versions/2.2.3/.pi/harnesses/lib/target-capabilities.js +7 -0
- package/.versions/2.2.3/.pi/harnesses/lib/update-check.ts +227 -0
- package/.versions/2.2.3/.pi/harnesses/lib/workspace-context.js +115 -0
- package/.versions/2.2.3/.pi/harnesses/lib/workspace-context.ts +22 -0
- package/.versions/2.2.3/.pi/harnesses/package-lock.json +2121 -0
- package/.versions/2.2.3/.pi/harnesses/package.json +13 -0
- package/.versions/2.2.3/.pi/prompts/af-build.md +27 -0
- package/.versions/2.2.3/.pi/prompts/af-code-simplify.md +22 -0
- package/.versions/2.2.3/.pi/prompts/af-constraints.md +31 -0
- package/.versions/2.2.3/.pi/prompts/af-plan.md +17 -0
- package/.versions/2.2.3/.pi/prompts/af-review.md +16 -0
- package/.versions/2.2.3/.pi/prompts/af-set-hermes-telegram.md +15 -0
- package/.versions/2.2.3/.pi/prompts/af-set-hermes-watchdog.md +6 -0
- package/.versions/2.2.3/.pi/prompts/af-setup-rules.md +20 -0
- package/.versions/2.2.3/.pi/prompts/af-ship.md +17 -0
- package/.versions/2.2.3/.pi/prompts/af-spec.md +15 -0
- package/.versions/2.2.3/.pi/prompts/af-test.md +19 -0
- package/.versions/2.2.3/.pi/skills/bowser/SKILL.md +145 -0
- package/.versions/2.2.3/.version +1 -0
- package/.versions/2.2.3/agents/architect.md +24 -0
- package/.versions/2.2.3/agents/bowser.md +28 -0
- package/.versions/2.2.3/agents/builder.md +55 -0
- package/.versions/2.2.3/agents/code-reviewer.md +209 -0
- package/.versions/2.2.3/agents/deep-researcher.md +32 -0
- package/.versions/2.2.3/agents/documenter.md +22 -0
- package/.versions/2.2.3/agents/plan-reviewer.md +83 -0
- package/.versions/2.2.3/agents/planner.md +107 -0
- package/.versions/2.2.3/agents/releaser.md +24 -0
- package/.versions/2.2.3/agents/researcher.md +30 -0
- package/.versions/2.2.3/agents/security-auditor.md +167 -0
- package/.versions/2.2.3/agents/test-engineer.md +153 -0
- package/.versions/2.2.3/agents/web-debugger.md +44 -0
- package/.versions/2.2.3/agents/web-performance-auditor.md +194 -0
- package/.versions/2.2.3/bin/catalog/harness-runtime-closure.json +85 -0
- package/.versions/2.2.3/docs/ARCHITECTURE.md +1291 -0
- package/.versions/2.2.3/docs/agent-fleet-setup.md +1161 -0
- package/.versions/2.2.3/docs/claude-code-coms-bridge.md +147 -0
- package/.versions/2.2.3/docs/codex-local-mcp.md +520 -0
- package/.versions/2.2.3/docs/codex-session-bridge.md +44 -0
- package/.versions/2.2.3/docs/codex-setup.md +183 -0
- package/.versions/2.2.3/docs/coms-hermes-bridge.md +188 -0
- package/.versions/2.2.3/docs/fleet-native-voice.md +151 -0
- package/.versions/2.2.3/docs/getting-started.md +126 -0
- package/.versions/2.2.3/docs/npm-install.md +535 -0
- package/.versions/2.2.3/docs/pi-extensions.md +450 -0
- package/.versions/2.2.3/docs/pi-setup.md +92 -0
- package/.versions/2.2.3/docs/skill-anatomy.md +150 -0
- package/.versions/2.2.3/install-manifest.json +3227 -0
- package/.versions/2.2.3/justfile +246 -0
- package/.versions/2.2.3/manifest-meta.json +1099 -0
- package/.versions/2.2.3/references/accessibility-checklist.md +160 -0
- package/.versions/2.2.3/references/communication-contract.md +26 -0
- package/.versions/2.2.3/references/definition-of-done.md +67 -0
- package/.versions/2.2.3/references/fleet-coordination-patterns.md +171 -0
- package/.versions/2.2.3/references/observability-checklist.md +92 -0
- package/.versions/2.2.3/references/orchestration-patterns.md +370 -0
- package/.versions/2.2.3/references/performance-checklist.md +236 -0
- package/.versions/2.2.3/references/prompting-patterns.md +380 -0
- package/.versions/2.2.3/references/security-checklist.md +245 -0
- package/.versions/2.2.3/references/testing-patterns.md +235 -0
- package/.versions/2.2.3/references/workflow-authoring.md +304 -0
- package/.versions/2.2.3/skills/_internal/grilling.md +59 -0
- package/.versions/2.2.3/skills/browser-testing-with-devtools/SKILL.md +351 -0
- package/.versions/2.2.3/skills/code-review-and-quality/SKILL.md +396 -0
- package/.versions/2.2.3/skills/compound-learning/SKILL.md +137 -0
- package/.versions/2.2.3/skills/constraint-driven-development/SKILL.md +338 -0
- package/.versions/2.2.3/skills/constraint-driven-development/references/floor-guard.md +99 -0
- package/.versions/2.2.3/skills/context-engineering/SKILL.md +341 -0
- package/.versions/2.2.3/skills/deprecation-and-migration/SKILL.md +247 -0
- package/.versions/2.2.3/skills/designing-agents/SKILL.md +394 -0
- package/.versions/2.2.3/skills/designing-agents/pi-harness-authoring.md +222 -0
- package/.versions/2.2.3/skills/drafting-workflows/SKILL.md +143 -0
- package/.versions/2.2.3/skills/drafting-workflows/scripts/make-workflow.ts +177 -0
- package/.versions/2.2.3/skills/fleet-connect/SKILL.md +29 -0
- package/.versions/2.2.3/skills/fleet-connect.zip +0 -0
- package/.versions/2.2.3/skills/fleet-native-voice/SKILL.md +103 -0
- package/.versions/2.2.3/skills/fleet-native-voice/agents/openai.yaml +4 -0
- package/.versions/2.2.3/skills/fleet-native-voice.zip +0 -0
- package/.versions/2.2.3/skills/frontend-ui-engineering/SKILL.md +328 -0
- package/.versions/2.2.3/skills/git-workflow-and-versioning/SKILL.md +316 -0
- package/.versions/2.2.3/skills/idea-refine/SKILL.md +182 -0
- package/.versions/2.2.3/skills/idea-refine/examples.md +238 -0
- package/.versions/2.2.3/skills/idea-refine/frameworks.md +99 -0
- package/.versions/2.2.3/skills/idea-refine/refinement-criteria.md +113 -0
- package/.versions/2.2.3/skills/idea-refine/scripts/idea-refine.sh +15 -0
- package/.versions/2.2.3/skills/incremental-implementation/SKILL.md +353 -0
- package/.versions/2.2.3/skills/incremental-implementation.zip +0 -0
- package/.versions/2.2.3/skills/interview-me/SKILL.md +226 -0
- package/.versions/2.2.3/skills/orchestration-verification/SKILL.md +182 -0
- package/.versions/2.2.3/skills/peer-coms/SKILL.md +90 -0
- package/.versions/2.2.3/skills/performance-optimization/SKILL.md +496 -0
- package/.versions/2.2.3/skills/planning-and-task-breakdown/SKILL.md +318 -0
- package/.versions/2.2.3/skills/planning-and-task-breakdown.zip +0 -0
- package/.versions/2.2.3/skills/repository-ai-setup/SKILL.md +135 -0
- package/.versions/2.2.3/skills/repository-ai-setup/references/agent-fleet-ai-state.template.json +4 -0
- package/.versions/2.2.3/skills/repository-ai-setup/references/apply-contract.md +74 -0
- package/.versions/2.2.3/skills/repository-ai-setup/references/provenance-template.md +16 -0
- package/.versions/2.2.3/skills/repository-ai-setup/references/setup-flow.md +108 -0
- package/.versions/2.2.3/skills/repository-ai-setup/references/verify-setup.md +20 -0
- package/.versions/2.2.3/skills/repository-ai-setup.zip +0 -0
- package/.versions/2.2.3/skills/security-and-hardening/SKILL.md +524 -0
- package/.versions/2.2.3/skills/spec-driven-development/SKILL.md +295 -0
- package/.versions/2.2.3/skills/spec-driven-development.zip +0 -0
- package/.versions/2.2.3/skills/using-agent-skills/SKILL.md +198 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/LICENSE +21 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/README.md +430 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/skills/api-and-interface-design/SKILL.md +367 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/skills/browser-testing-with-devtools/SKILL.md +317 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/skills/ci-cd-and-automation/SKILL.md +390 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/skills/code-review-and-quality/SKILL.md +396 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/skills/code-simplification/SKILL.md +331 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/skills/constraint-driven-development/SKILL.md +311 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/skills/constraint-driven-development/references/floor-guard.md +99 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/skills/context-engineering/SKILL.md +337 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/skills/debugging-and-error-recovery/SKILL.md +300 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/skills/deprecation-and-migration/SKILL.md +247 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/skills/documentation-and-adrs/SKILL.md +288 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/skills/doubt-driven-development/SKILL.md +243 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/skills/frontend-ui-engineering/SKILL.md +328 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/skills/git-workflow-and-versioning/SKILL.md +355 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/skills/idea-refine/SKILL.md +178 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/skills/idea-refine/examples.md +238 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/skills/idea-refine/frameworks.md +99 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/skills/idea-refine/refinement-criteria.md +113 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/skills/idea-refine/scripts/idea-refine.sh +15 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/skills/incremental-implementation/SKILL.md +249 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/skills/interview-me/SKILL.md +225 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/skills/observability-and-instrumentation/SKILL.md +238 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/skills/performance-optimization/SKILL.md +496 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/skills/planning-and-task-breakdown/SKILL.md +257 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/skills/security-and-hardening/SKILL.md +524 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/skills/shipping-and-launch/SKILL.md +330 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/skills/source-driven-development/SKILL.md +216 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/skills/spec-driven-development/SKILL.md +245 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/skills/test-driven-development/SKILL.md +398 -0
- package/.versions/2.2.3/vendor/agent-skills-upstream/skills/using-agent-skills/SKILL.md +192 -0
- package/CHANGELOG.md +19 -0
- package/docs/hub-task-continuation.md +23 -0
- package/install-manifest.json +1 -1
- package/package.json +4 -3
|
@@ -0,0 +1,318 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: planning-and-task-breakdown
|
|
3
|
+
description: Breaks work into a sequential implementation plan and grills unresolved material design decisions before writing tasks. Use when you have a spec or clear requirements and need locally verifiable implementation tasks. A plan is an implementation plan unless the human explicitly asks for another kind. Close one task before starting the next. Do not include environment, operator, deploy, publish, activation, or rollout work.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Planning and Task Breakdown
|
|
7
|
+
|
|
8
|
+
## Overview
|
|
9
|
+
|
|
10
|
+
Decompose work into small, verifiable tasks with explicit acceptance criteria. Good task breakdown is the difference between an agent that completes work reliably and one that produces a tangled mess. Every task should be small enough to implement, test, and verify in a single focused session.
|
|
11
|
+
|
|
12
|
+
Unless the human explicitly asks for another kind of plan (research, migration design, retirement, or a deployment checklist), the plan is an **implementation plan**: ordered work to implement the stated requirements and verify them locally. Do not add a rollout, publish, delivery, or deployment phase. Do not add any task whose closure requires an environment, an operator, deploy, publish, activation, a post-deploy script, live mail, a live queue, or any other runtime that is not a local check. Those items are not numbered tasks. Mention them at most once, under "Out of scope / noticed", as belonging to a separate deployment checklist. Do not write that checklist unless the human explicitly asked for a deployment plan.
|
|
13
|
+
|
|
14
|
+
Tasks are a sequence, not a parallel batch. Close task N — its acceptance criteria met and its local verification done — before starting task N+1. A checkpoint is a gate after closed tasks, not permission to run several tasks at once. Vertical slices describe the shape of each task (one complete, locally testable path). They are not permission to execute slices in parallel. Parallel execution is allowed only when the human explicitly asks for it.
|
|
15
|
+
|
|
16
|
+
Do not choose how the plan will be executed. Do not ask whether to run it slice by slice or at once, and do not infer that from plan size or a worktree. Do not write `Execution: whole-plan` yourself. At execution time, `incremental-implementation` keeps per-slice human review unless the operator explicitly requests whole-plan execution. A checkpoint's human review applies only to that default. When the operator has already opted in, a checkpoint is local verification only. An unresolved material plan or PRD decision during execution still interrupts and is grilled with `ask_user`. This skill does not waive that.
|
|
17
|
+
|
|
18
|
+
## When to Use
|
|
19
|
+
|
|
20
|
+
- You have a spec and need to break it into implementable units
|
|
21
|
+
- A task feels too large or vague to start
|
|
22
|
+
- You need to communicate scope to a human
|
|
23
|
+
- The implementation order isn't obvious
|
|
24
|
+
- An unresolved material decision must be settled before dependent tasks are written; equivalent local patterns are routine technical choices
|
|
25
|
+
|
|
26
|
+
**When NOT to use:** Single-file changes with obvious scope, or when the spec already contains well-defined tasks. Skipping a plan file does **not** skip grilling: resolve routine technical choices independently; ask before coding only when an unresolved material decision affects the work.
|
|
27
|
+
|
|
28
|
+
## Proportionality gate (check before writing anything)
|
|
29
|
+
|
|
30
|
+
A plan is overhead the human pays for. Before you write one, size it against the ask:
|
|
31
|
+
|
|
32
|
+
| The ask | The right artifact |
|
|
33
|
+
|---|---|
|
|
34
|
+
| One obvious change, one file, low risk | **No plan.** Make the change and say what you did. |
|
|
35
|
+
| A contained change in familiar code | A task list in your reply — 3–6 lines, no plan file. |
|
|
36
|
+
| Multi-step work, unfamiliar code, or real risk | A plan file, as below. |
|
|
37
|
+
|
|
38
|
+
Rules that follow from this:
|
|
39
|
+
|
|
40
|
+
- **Never write a plan longer than the work it plans.** If the plan document would take longer to read than the change takes to make, it is the wrong artifact.
|
|
41
|
+
- **A safety requirement is a task, not a subsystem.** "Don't remove existing permissions" is one acceptance criterion with one verification step — not a hash-pinned manifest, an immutable evidence namespace, and a fixture suite. Provenance machinery is warranted only when the human asked for an audit trail or the change is irreversible at scale.
|
|
42
|
+
- **Plan the ask, not the neighbourhood.** Adjacent problems you notice go in a short "Out of scope / noticed" list at the end for the human to decide on. They do not become tasks.
|
|
43
|
+
- **Split by phase when the phases have different owners.** Repository work, cloud/infrastructure preparation, deployment, and retirement belong in separate plans only when the human explicitly asks for that other plan. An implementation plan does not include those phases. Bundling them blocks the whole plan on whichever phase stalls, and every review re-reads all of it.
|
|
44
|
+
- **No task that cannot close locally.** If closing the task needs a deployed or shared environment, an operator action, schema publish, a post-deploy script, activation, live mail, or a live queue, it is not an implementation task. Naming it "verification", "follow-up", or "rollout" does not make it one. Leave it off the task list.
|
|
45
|
+
- **Review findings do not silently enlarge the plan.** When a plan revision adds requirements nobody asked for, say so explicitly and let the human accept or drop them.
|
|
46
|
+
- **Unspecified forks still get grilled.** Skipping a plan file does not skip a load-bearing choice. Already-stated requirements (chat, prompt, PRD, rules) are not re-asked.
|
|
47
|
+
|
|
48
|
+
## Output Location
|
|
49
|
+
|
|
50
|
+
By default, save the plan to `docs/plans/{area}/PLAN-{prd-name}-{phase}.md`:
|
|
51
|
+
|
|
52
|
+
- `{area}` — the functional area; match the area of the PRD this plan implements.
|
|
53
|
+
- `{prd-name}` — the name of the PRD this plan implements (e.g. `PRD3-tournament-copy`). If there is no PRD, use a short kebab-case topic slug instead.
|
|
54
|
+
- `{phase}` — include a phase suffix **only** when the plan is deliberately split across more than one plan file. For a single-file plan, drop it (`PLAN-{prd-name}.md`).
|
|
55
|
+
|
|
56
|
+
The task list is **embedded** in the plan file as the `## Task List` section. Do **not** create a separate `todo.md`.
|
|
57
|
+
|
|
58
|
+
Match the project's existing `docs` vs `Docs` capitalization, and create the directory if it does not exist.
|
|
59
|
+
|
|
60
|
+
**Project overrides:** if `.ai/agent-fleet-overrides.md` has a `## planning-and-task-breakdown` section, its keys (`plan-dir`, `naming`, `todo`) override these defaults — `todo: separate` restores a standalone `todo.md`, and `todo: tracker` routes tasks to an external issue tracker (below). See [docs/agent-fleet-setup.md](../../docs/agent-fleet-setup.md).
|
|
61
|
+
|
|
62
|
+
### Task List Target
|
|
63
|
+
|
|
64
|
+
The **task list target** is where tasks and checkpoints are recorded. It is defined once, here; every other reference in this skill defers to it.
|
|
65
|
+
|
|
66
|
+
- **Default (`todo: embedded`)** — the `## Task List` section of the plan file itself. No separate file.
|
|
67
|
+
- **`todo: separate`** — a standalone checklist-style `todo.md` next to the plan.
|
|
68
|
+
- **`todo: tracker`** — one item per task in the designated issue tracker (GitHub Issues, Jira, Linear, `bd`/beads). Map the Step 4 structure onto the tracker's fields: acceptance criteria and verification steps in the item body, dependencies via the tracker's linking mechanism (`bd dep add`, "blocked by", etc.). Record Step 5 checkpoints as tracker items too, or keep them as a checklist in the plan document if the tracker has no natural equivalent.
|
|
69
|
+
|
|
70
|
+
With a tracker, name it in the plan (e.g. "Tasks tracked in Linear project FOO") so downstream steps and future sessions know where to look, and keep the plan's `## Task List` section as an ordered index of tracker item IDs or links rather than a duplicate checklist.
|
|
71
|
+
|
|
72
|
+
**Never overwrite an incomplete plan.** Before writing the resolved plan path, check whether it already exists and still contains unchecked tasks:
|
|
73
|
+
|
|
74
|
+
- Same work being replanned (the user asked to revise or extend this plan) → update the existing file in place.
|
|
75
|
+
- Different work → **stop and ask.** The unchecked tasks may be mid-build in another session or another flow worktree. Do not delete, overwrite, or rename the existing plan on your own; present the conflict and let the user decide (finish the old plan first, explicitly discard it, or say where the new plan should go).
|
|
76
|
+
|
|
77
|
+
The same rule applies to a tracker target: never bulk-close or delete another plan's open items to make room for new ones.
|
|
78
|
+
|
|
79
|
+
## The Planning Process
|
|
80
|
+
|
|
81
|
+
### Step 1: Enter Plan Mode
|
|
82
|
+
|
|
83
|
+
Before writing any code, operate in read-only mode:
|
|
84
|
+
|
|
85
|
+
- Read the spec and relevant codebase sections
|
|
86
|
+
- Identify existing patterns and conventions
|
|
87
|
+
- Map dependencies between components
|
|
88
|
+
- Note risks and unknowns
|
|
89
|
+
|
|
90
|
+
**Do NOT write code during planning.** The output is a plan document and a task list recorded in the task list target (see Output Location), not implementation.
|
|
91
|
+
|
|
92
|
+
**Grilling (required before writing tasks):** Read the shared internal helper at [`../_internal/grilling.md`](../_internal/grilling.md). Inventory load-bearing decisions. Skip anything already explicit in chat, prompt, PRD, spec, or rules. Research facts and decide routine implementation choices independently, recording their basis. Grill only unresolved material decisions one question at a time, with a recommended option; specialists route questions through the orchestrator first. Multiple valid ways alone do not require human input. Do not write tasks while a load-bearing choice is still silently assumed. Update Architecture Decisions, Risks, and Open Questions with accepted, rejected, or deferred choices. If nothing is open, note that grilling found no unspecified forks and continue.
|
|
93
|
+
|
|
94
|
+
**Model poll (planner, when `delegate` is available):** On an unresolved architectural fork at task tier `feature` or `project`, run `voice-1`, `voice-2`, and `voice-3` **after** recon (`scout`/`rules`), never in the same message, with a character-for-character identical instruction. Do not poll on `trivial`/`small` (delegation is off) and do not invent a poll if `delegate` is missing. Agreement informs a recommendation; it does not settle a material decision on behalf of the human. Record the voices; write a `POLL-{prd-name}.md` digest next to the plan and cite it. An unresolved material decision becomes one `ASK_USER:` question for orchestrator triage with one option per position plus a recommendation and reason — do not write the plan in that same turn. The optional communication contract at [`../../references/communication-contract.md`](../../references/communication-contract.md) is not loaded automatically; enable it with `append-prompt: references/communication-contract.md` in `## agent-hub`.
|
|
95
|
+
|
|
96
|
+
### Step 2: Identify the Dependency Graph
|
|
97
|
+
|
|
98
|
+
Map what depends on what:
|
|
99
|
+
|
|
100
|
+
```
|
|
101
|
+
Database schema
|
|
102
|
+
│
|
|
103
|
+
├── API models/types
|
|
104
|
+
│ │
|
|
105
|
+
│ ├── API endpoints
|
|
106
|
+
│ │ │
|
|
107
|
+
│ │ └── Frontend API client
|
|
108
|
+
│ │ │
|
|
109
|
+
│ │ └── UI components
|
|
110
|
+
│ │
|
|
111
|
+
│ └── Validation logic
|
|
112
|
+
│
|
|
113
|
+
└── Seed data / migrations
|
|
114
|
+
```
|
|
115
|
+
|
|
116
|
+
Implementation order follows the dependency graph bottom-up: build foundations first.
|
|
117
|
+
|
|
118
|
+
### Step 3: Slice Vertically
|
|
119
|
+
|
|
120
|
+
Instead of building all the database, then all the API, then all the UI — build one complete feature path at a time:
|
|
121
|
+
|
|
122
|
+
**Bad (horizontal slicing):**
|
|
123
|
+
```
|
|
124
|
+
Task 1: Build entire database schema
|
|
125
|
+
Task 2: Build all API endpoints
|
|
126
|
+
Task 3: Build all UI components
|
|
127
|
+
Task 4: Connect everything
|
|
128
|
+
```
|
|
129
|
+
|
|
130
|
+
**Good (vertical slicing):**
|
|
131
|
+
```
|
|
132
|
+
Task 1: User can create an account (schema + API + UI for registration)
|
|
133
|
+
Task 2: User can log in (auth schema + API + UI for login)
|
|
134
|
+
Task 3: User can create a task (task schema + API + UI for creation)
|
|
135
|
+
Task 4: User can view task list (query + API + UI for list view)
|
|
136
|
+
```
|
|
137
|
+
|
|
138
|
+
Each vertical slice delivers working, locally testable functionality. "Locally testable" means tests, builds, and checks that run without a deployed environment or an operator.
|
|
139
|
+
|
|
140
|
+
Execute slices strictly in order. Finish and close one slice — acceptance criteria and local verification — before opening the next. Do not schedule independent slices as a parallel batch. Looking independent is not permission to parallelize.
|
|
141
|
+
|
|
142
|
+
### Step 4: Write Tasks
|
|
143
|
+
|
|
144
|
+
Each task follows this structure, whether it lands in the plan's `## Task List`, a standalone `todo.md`, or an external tracker item (see Output Location):
|
|
145
|
+
|
|
146
|
+
```markdown
|
|
147
|
+
## Task [N]: [Short descriptive title]
|
|
148
|
+
|
|
149
|
+
**Description:** One paragraph explaining what this task accomplishes.
|
|
150
|
+
|
|
151
|
+
**Acceptance criteria:**
|
|
152
|
+
- [ ] [Specific, testable condition]
|
|
153
|
+
- [ ] [Specific, testable condition]
|
|
154
|
+
|
|
155
|
+
**Verification:**
|
|
156
|
+
- [ ] Tests pass: [the project's `quality:` command, or the repository's focused-test command]
|
|
157
|
+
- [ ] Build succeeds: [the repository's build command]
|
|
158
|
+
- [ ] Local manual check, if needed: [description of what to verify without an environment or an operator]
|
|
159
|
+
|
|
160
|
+
**Dependencies:** [Task numbers this depends on, or "None"]
|
|
161
|
+
|
|
162
|
+
**Closes locally:** Yes. Acceptance and verification use only local tests, builds, and static checks. If this task cannot close without an environment, an operator, deploy, publish, activation, a post-deploy script, live mail, or a live queue, delete it from this plan.
|
|
163
|
+
|
|
164
|
+
**Files likely touched:**
|
|
165
|
+
- `src/path/to/file.ts`
|
|
166
|
+
- `tests/path/to/test.ts`
|
|
167
|
+
```
|
|
168
|
+
|
|
169
|
+
### Step 5: Order and Checkpoint
|
|
170
|
+
|
|
171
|
+
Arrange tasks so that:
|
|
172
|
+
|
|
173
|
+
1. Dependencies are satisfied (build foundation first)
|
|
174
|
+
2. Each task leaves the system in a working state
|
|
175
|
+
3. Verification checkpoints occur after every 2-3 closed tasks
|
|
176
|
+
4. High-risk tasks are early (fail fast)
|
|
177
|
+
5. The next task does not start until the previous task is closed. Do not mark a set of tasks as parallelizable unless the human explicitly asked for parallel execution
|
|
178
|
+
|
|
179
|
+
Add explicit checkpoints to the task list target:
|
|
180
|
+
|
|
181
|
+
```markdown
|
|
182
|
+
## Checkpoint: After Tasks 1-3
|
|
183
|
+
- [ ] All tests pass
|
|
184
|
+
- [ ] Application builds without errors
|
|
185
|
+
- [ ] Core user flow works end-to-end in local tests or a local run
|
|
186
|
+
- [ ] Review with human before starting the next task (default execution only; when the operator has explicitly requested whole-plan execution, this line is local verification only)
|
|
187
|
+
- [ ] No later task was started before this checkpoint's tasks were closed
|
|
188
|
+
```
|
|
189
|
+
|
|
190
|
+
## Task Sizing Guidelines
|
|
191
|
+
|
|
192
|
+
If a task is 5-8 files (Multi-component feature , such as Search with filtering and pagination) or larger, it should be broken into smaller tasks. An agent performs best on 1-5 file tasks.
|
|
193
|
+
|
|
194
|
+
**When to break a task down further:**
|
|
195
|
+
- It would take more than one focused session (roughly 2+ hours of agent work)
|
|
196
|
+
- You cannot describe the acceptance criteria in 3 or fewer bullet points
|
|
197
|
+
- It touches two or more independent subsystems (e.g., auth and billing)
|
|
198
|
+
- You find yourself writing "and" in the task title (a sign it is two tasks)
|
|
199
|
+
|
|
200
|
+
## Plan Document Template
|
|
201
|
+
|
|
202
|
+
```markdown
|
|
203
|
+
# Implementation Plan: [Feature/Project Name]
|
|
204
|
+
|
|
205
|
+
## Overview
|
|
206
|
+
[One paragraph summary of what we're building]
|
|
207
|
+
|
|
208
|
+
## Architecture Decisions
|
|
209
|
+
- [Key decision 1 and rationale]
|
|
210
|
+
- [Key decision 2 and rationale]
|
|
211
|
+
|
|
212
|
+
## Task List
|
|
213
|
+
|
|
214
|
+
Execution is strictly sequential. Close one task before starting the next. No parallel batch.
|
|
215
|
+
|
|
216
|
+
### Phase 1: Foundation
|
|
217
|
+
- [ ] Task 1: ...
|
|
218
|
+
- [ ] Task 2: ...
|
|
219
|
+
|
|
220
|
+
### Checkpoint: Foundation
|
|
221
|
+
- [ ] Local tests pass, builds clean
|
|
222
|
+
|
|
223
|
+
### Phase 2: Core Features
|
|
224
|
+
- [ ] Task 3: ...
|
|
225
|
+
- [ ] Task 4: ...
|
|
226
|
+
|
|
227
|
+
### Checkpoint: Core Features
|
|
228
|
+
- [ ] End-to-end flow works
|
|
229
|
+
|
|
230
|
+
### Phase 3: Polish
|
|
231
|
+
- [ ] Task 5: ...
|
|
232
|
+
- [ ] Task 6: ...
|
|
233
|
+
|
|
234
|
+
### Checkpoint: Complete
|
|
235
|
+
- [ ] All acceptance criteria met
|
|
236
|
+
- [ ] Ready for review
|
|
237
|
+
|
|
238
|
+
## Risks and Mitigations
|
|
239
|
+
| Risk | Impact | Mitigation |
|
|
240
|
+
|------|--------|------------|
|
|
241
|
+
| [Risk] | [High/Med/Low] | [Strategy] |
|
|
242
|
+
|
|
243
|
+
## Open Questions
|
|
244
|
+
- [Question needing human input]
|
|
245
|
+
```
|
|
246
|
+
|
|
247
|
+
When tasks live in an external tracker, keep the Task List section above as an ordered index of tracker item IDs or links instead of a duplicate checklist.
|
|
248
|
+
|
|
249
|
+
## Parallel execution is not the default
|
|
250
|
+
|
|
251
|
+
Do not plan tasks for parallel agents or sessions unless the human explicitly asks for parallel execution.
|
|
252
|
+
|
|
253
|
+
- **Default:** one ordered sequence. Close the current task before starting the next, including when several slices look independent.
|
|
254
|
+
- **Explicit parallel request only:** the human asked to parallelize. Even then, database migrations, shared-state changes, and dependency chains stay sequential. No parallel task may require an environment, an operator, deploy, or publish to close.
|
|
255
|
+
- **Deployment checklist:** not part of an implementation plan. Write one only when the human explicitly asks for a deployment or rollout plan. Do not append environment verification, operator actions, publish, activation, or delivery as the next numbered tasks.
|
|
256
|
+
|
|
257
|
+
## Common Rationalizations
|
|
258
|
+
|
|
259
|
+
| Rationalization | Reality |
|
|
260
|
+
|---|---|
|
|
261
|
+
| "I'll figure it out as I go" | That's how you end up with a tangled mess and rework. 10 minutes of planning saves hours. |
|
|
262
|
+
| "The tasks are obvious" | Write them down anyway. Explicit tasks surface hidden dependencies and forgotten edge cases. |
|
|
263
|
+
| "Planning is overhead" | Planning is the task. Implementation without a plan is just typing. |
|
|
264
|
+
| "I can hold it all in my head" | Context windows are finite. Written plans survive session boundaries and compaction. |
|
|
265
|
+
| "The old plan is stale, I'll just replace it" | Unchecked tasks may be mid-build in another session or flow worktree. Overwriting them destroys work state that exists nowhere else. Stop and ask. |
|
|
266
|
+
| "The PRD already covers everything, no need to grill" | Then grilling produces zero questions. Still run the inventory so silent forks do not slip through. |
|
|
267
|
+
| "I'll pick the obvious variant and note it in Architecture Decisions" | If more than one variant exists and none was mandated, it is not obvious to the programmer who was not in the room. Ask, then record the choice. |
|
|
268
|
+
| "Re-confirming the PRD points shows thoroughness" | Re-asking settled requirements wastes the user and implies the agent did not read them. Skip them. |
|
|
269
|
+
| "These slices are independent, so plan them in parallel" | Independence is not permission. Close one slice before the next unless the human explicitly asked to parallelize. |
|
|
270
|
+
| "The plan is small, or it will run on a worktree, so I'll record whole-plan" | No. The operator writes that opt-in. The planner does not ask which execution mode to use and does not infer it. |
|
|
271
|
+
| "The next tasks are just environment verification, not rollout" | If a task cannot close without an environment or an operator, it is not an implementation task. It belongs on a separate deployment checklist, not in this plan. |
|
|
272
|
+
| "The requirements mention deploy, so the implementation plan should include it" | A mention of deploy, publish, or delivery does not add those phases. Record them once under Out of scope unless the human explicitly asked for a deployment plan. |
|
|
273
|
+
|
|
274
|
+
## Red Flags
|
|
275
|
+
|
|
276
|
+
- Starting implementation without a written task list
|
|
277
|
+
- Overwriting a plan that still has unchecked tasks for different work, without asking
|
|
278
|
+
- Writing a `todo.md` when the project has designated an external tracker (or scattering tasks across both)
|
|
279
|
+
- Tasks that say "implement the feature" without acceptance criteria
|
|
280
|
+
- No verification steps in the plan
|
|
281
|
+
- All tasks touches more than 8+ files
|
|
282
|
+
- No checkpoints between tasks
|
|
283
|
+
- Dependency order isn't considered
|
|
284
|
+
- Writing tasks that silently pick a library, pattern, or behavior not mandated in chat/PRD/rules
|
|
285
|
+
- Re-asking a requirement already explicit in chat, prompt, PRD, spec, or rules
|
|
286
|
+
- Leaving an unresolved material decision as an Open Question while proceeding with dependent work
|
|
287
|
+
- Planning tasks as a parallel batch without an explicit human request to parallelize
|
|
288
|
+
- Asking, during planning, whether to execute the plan at once
|
|
289
|
+
- Writing `Execution: whole-plan` into the plan to waive the human review gate
|
|
290
|
+
- A rollout, publish, delivery, or deployment phase in an implementation plan
|
|
291
|
+
- A numbered task whose closure needs an environment, an operator, deploy, publish, activation, a post-deploy script, live mail, or a live queue
|
|
292
|
+
- Numbering deployment-checklist items as implementation tasks, including under a "verification" or "follow-up" heading
|
|
293
|
+
|
|
294
|
+
## Verification
|
|
295
|
+
|
|
296
|
+
Before starting implementation, confirm:
|
|
297
|
+
|
|
298
|
+
- [ ] Every task has acceptance criteria
|
|
299
|
+
- [ ] Every task has a verification step
|
|
300
|
+
- [ ] Task dependencies are identified and ordered correctly
|
|
301
|
+
- [ ] Tasks are recorded in the task list target resolved from `todo` (default: the plan's `## Task List`)
|
|
302
|
+
- [ ] No pre-existing incomplete plan was overwritten without explicit user confirmation
|
|
303
|
+
- [ ] No task touches more than ~5 files
|
|
304
|
+
- [ ] Checkpoints exist between major phases
|
|
305
|
+
- [ ] The human has reviewed and approved the plan
|
|
306
|
+
- [ ] Grilling ran before tasks were written (inventory of load-bearing decisions)
|
|
307
|
+
- [ ] Already-stated requirements (chat, prompt, PRD, spec, rules) were not re-asked
|
|
308
|
+
- [ ] Each remaining load-bearing decision has an accepted/rejected/deferred status in the plan
|
|
309
|
+
- [ ] No open questions left (All are resolved/answered/commented)
|
|
310
|
+
- [ ] The plan is an implementation plan unless the human explicitly asked for another kind
|
|
311
|
+
- [ ] Every task can close with local tests, builds, or static checks
|
|
312
|
+
- [ ] No task requires an environment, an operator, deploy, publish, activation, a post-deploy script, live mail, or a live queue
|
|
313
|
+
- [ ] Rollout, publish, delivery, and deployment are absent from the task list; if noticed, they appear at most once under Out of scope
|
|
314
|
+
- [ ] Tasks are ordered for sequential execution: each task closes before the next starts, unless the human explicitly asked to parallelize
|
|
315
|
+
|
|
316
|
+
## See Also
|
|
317
|
+
|
|
318
|
+
Acceptance criteria are per-task and answer "did we build the right thing?". They sit on top of the project-wide Definition of Done, the standing bar every task clears before it counts as done. See `../../references/definition-of-done.md`.
|
|
Binary file
|
|
@@ -0,0 +1,135 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: repository-ai-setup
|
|
3
|
+
description: Sets up repository AI rules from the packaged Fleet catalogue — discover target evidence, propose semantic adaptations, grill unresolved decisions one question at a time, then diff, apply, and verify. Use for initial .ai/rules setup and repeated additions or updates via an optional change request.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Repository AI Setup
|
|
7
|
+
|
|
8
|
+
Initial and repeated setup of a target repository's `.ai/rules`, `.ai/commands`,
|
|
9
|
+
and `.ai/agent-prompts` from the Fleet catalogue, plus the Fleet settings handoff
|
|
10
|
+
that makes the result load automatically. Follow
|
|
11
|
+
`references/setup-flow.md` for the phase checklists,
|
|
12
|
+
`references/apply-contract.md` for the deterministic write rules, and
|
|
13
|
+
`references/provenance-template.md` for the file metadata contract.
|
|
14
|
+
|
|
15
|
+
## When to Use
|
|
16
|
+
|
|
17
|
+
Apply this skill when the user invokes `/af-setup-rules` (optionally with a
|
|
18
|
+
free-text change request such as "add API compatibility rules"), or asks to set
|
|
19
|
+
up, review, or extend a repository's AI rules from the Fleet catalogue.
|
|
20
|
+
|
|
21
|
+
**When NOT to use:**
|
|
22
|
+
|
|
23
|
+
- Ordinary planning, building, or reviewing — read the already-installed
|
|
24
|
+
`.ai/rules` index instead of re-running setup.
|
|
25
|
+
- Deterministic installation (`agent-fleet setup`) — that path stays
|
|
26
|
+
non-interactive and never runs this interview.
|
|
27
|
+
- Editing Fleet settings by hand or via any path other than the CLI below.
|
|
28
|
+
|
|
29
|
+
## Non-negotiable boundaries
|
|
30
|
+
|
|
31
|
+
1. **Catalogue source is the installed Fleet npm package only.** Resolve it with
|
|
32
|
+
`requirePackageCatalogue(packageRoot)` from `bin/lib/project-provenance.js`
|
|
33
|
+
before any selection. If the package has no `catalog/` payload, stop this
|
|
34
|
+
capability with a clear error — other Fleet functionality keeps working.
|
|
35
|
+
Never copy the catalogue beneath `.pi/`, never infer one from a source
|
|
36
|
+
checkout, never download it silently. This skill consumes the library; the
|
|
37
|
+
library is not part of any repository's own policy.
|
|
38
|
+
2. **Missing rules/docs paths warn and continue, never fail setup.** A
|
|
39
|
+
configured root that does not exist on disk is advisory, not fatal.
|
|
40
|
+
3. **This skill never edits overrides and contains no overrides merge
|
|
41
|
+
algorithm.** All settings changes go through the deterministic CLI:
|
|
42
|
+
preview with `agent-fleet configure --rules <dirs> --docs <paths> --dry-run`,
|
|
43
|
+
then apply the reviewed preview with `--expect-hash <expectedHash> --yes`.
|
|
44
|
+
There is no second Markdown merge writer in this skill or its references.
|
|
45
|
+
4. **Provenance is the single sidecar `.ai/agent-fleet-ai-state.json`.**
|
|
46
|
+
Read, classify, and write it only via `bin/lib/project-provenance.js`
|
|
47
|
+
(`readProjectProvenance`, `classifyProjectFile`, `applyAcceptedProjectFiles`).
|
|
48
|
+
Template-derived files carry `fleet-template` / `fleet-source-version`
|
|
49
|
+
frontmatter; repo-derived files never get an invented template identity.
|
|
50
|
+
`appliedHash` lives in the sidecar, never in the hashed file. The sidecar is
|
|
51
|
+
preserved on uninstall and is not installer ownership.
|
|
52
|
+
5. **Existing explicit policy is preserved without redundant confirmation.**
|
|
53
|
+
A rule inferred only from code frequency or consistency is a proposal with
|
|
54
|
+
cited evidence — never normative — until the user explicitly accepts it.
|
|
55
|
+
|
|
56
|
+
## External content destinations
|
|
57
|
+
|
|
58
|
+
Keep overrides, provenance and lifecycle state in the checkout's real `.ai/`.
|
|
59
|
+
Read `rules:`/`docs:` grants do not authorize writes. For an explicitly reviewed
|
|
60
|
+
external generation destination, pass `contentDestination: { root,
|
|
61
|
+
acceptedDecision, evidence }` to the provenance API and retain logical `.ai/...`
|
|
62
|
+
change paths. The destination must be an existing real directory separate from
|
|
63
|
+
the checkout. Supply the same reviewed destination for classification and later
|
|
64
|
+
apply; adoption/conflicts and per-content hashes remain mandatory. Content and
|
|
65
|
+
the local sidecar roll back together under the local lifecycle lock/journal.
|
|
66
|
+
|
|
67
|
+
Configure external read references separately through the existing configure
|
|
68
|
+
CLI. Exact-file docs grants never expand to parents; child references resolve
|
|
69
|
+
before spawning. Native command/skill registration needs local adapters or
|
|
70
|
+
explicit Pi paths, not a read grant. External System 1 capture needs separate
|
|
71
|
+
include consent, and non-Git history gaps must remain visible. See
|
|
72
|
+
`../../docs/external-project-ai-content.md` for the complete layout contract.
|
|
73
|
+
|
|
74
|
+
## The workflow
|
|
75
|
+
|
|
76
|
+
Run these phases in order. The detail for each step lives in
|
|
77
|
+
`references/setup-flow.md`; the gates below are normative.
|
|
78
|
+
|
|
79
|
+
### 1. Discover before asking
|
|
80
|
+
|
|
81
|
+
Resolve target root and git state. Read existing `.ai/` files, Fleet overrides,
|
|
82
|
+
the docs policy and indexes. Inventory manifests, formatter/linter/analyzers,
|
|
83
|
+
build/test commands, CI, module boundaries, and templates using representative
|
|
84
|
+
implementations and callers — not extension counts. Skip generated, vendor,
|
|
85
|
+
build, and cache trees; never read secret values. For each recommendation
|
|
86
|
+
record evidence source, scope, status (confirmed / proposed / conflicting),
|
|
87
|
+
proposed file, reason, and check. Unknown stays unknown.
|
|
88
|
+
|
|
89
|
+
### 2. Present a concrete proposal
|
|
90
|
+
|
|
91
|
+
Show the proposed tree, selected profiles/roles/commands, files to update, new
|
|
92
|
+
files, and conflicts. Keep working structure; never move an intact catalogue to
|
|
93
|
+
match a template. Adaptations are complete project files with concrete rules,
|
|
94
|
+
paths, templates, and verification steps — never placeholder-only substitution,
|
|
95
|
+
never imported reference-repository defaults without target evidence.
|
|
96
|
+
|
|
97
|
+
### 3. Grill unresolved important decisions
|
|
98
|
+
|
|
99
|
+
Follow `skills/_internal/grilling.md`. Never re-ask what is already explicit in
|
|
100
|
+
chat, plan, spec, rules, or a recorded decision. For each remaining
|
|
101
|
+
load-bearing fork ask **one question at a time**, each with the found evidence,
|
|
102
|
+
2–4 real options, your **recommendation with reason**, and the material
|
|
103
|
+
trade-off. Use the native user-question tool; where none exists, ask a real
|
|
104
|
+
text question and wait — never simulate a tool call or an answer. Let each
|
|
105
|
+
answer shape the next question. Record accepted / rejected / deferred in the
|
|
106
|
+
proposal; a deferred decision never authorizes its dependent change. If every
|
|
107
|
+
decision is already explicit, report the zero-open-decisions case instead of
|
|
108
|
+
inventing questions. Headless runs may produce analysis and a proposal only:
|
|
109
|
+
no fake interview, no auto-acceptance, no apply of undecided policy.
|
|
110
|
+
|
|
111
|
+
### 4. Apply reviewed changes and verify
|
|
112
|
+
|
|
113
|
+
Show the concrete diff with the recorded decisions before writing. Honor
|
|
114
|
+
authorization already given; do not re-ask for the same actions. Re-check file
|
|
115
|
+
bytes immediately before writing if the repo changed since preview. Apply
|
|
116
|
+
content and provenance per `references/apply-contract.md` (current bytes vs
|
|
117
|
+
`appliedHash`: no-op, local-edit, source-update, conflict, unknown); settings
|
|
118
|
+
go through the CLI handoff. On error report exactly what was written and what remains, and
|
|
119
|
+
restore only your own changes when safe. Then verify per `references/verify-setup.md`: links, triggers, stale
|
|
120
|
+
placeholders, overrides content, target-local command discovery, prompt
|
|
121
|
+
reference resolution, and clean-session policy use. An unchanged accepted state
|
|
122
|
+
is a byte-identical no-op with no regeneration.
|
|
123
|
+
|
|
124
|
+
## Repeated runs and change requests
|
|
125
|
+
|
|
126
|
+
Rules and commands are the default scope; include agent prompts when the change
|
|
127
|
+
needs them or the user asks. A scoped request updates only affected files and
|
|
128
|
+
their necessary indexes, references, and adapters. Repeating a fulfilled
|
|
129
|
+
request adds no duplicates. A new change request re-opens its affected scope
|
|
130
|
+
even when template versions are unchanged.
|
|
131
|
+
|
|
132
|
+
## Headless and unanswered decisions
|
|
133
|
+
|
|
134
|
+
Without a live user: discover, propose, stop. Unanswered decisions never lead
|
|
135
|
+
to dependent apply. Say what is blocked and what the user must decide.
|
|
@@ -0,0 +1,74 @@
|
|
|
1
|
+
# Apply contract: candidate diff → reviewed apply → verified provenance
|
|
2
|
+
|
|
3
|
+
Deterministic rules for writing target `.ai/` content, sidecar entries,
|
|
4
|
+
pointer edits, and adapters. This reference holds no merge algorithm for
|
|
5
|
+
overrides and no transaction subsystem: content and sidecar go through
|
|
6
|
+
`applyAcceptedProjectFiles` in `bin/lib/project-provenance.js` (backed by
|
|
7
|
+
`bin/lib/transaction.js`), pointer regions through `extractRegion` /
|
|
8
|
+
`replaceRegion` in `bin/lib/merge-forms.js`, and settings through
|
|
9
|
+
`agent-fleet configure`. The model produces candidate bytes; only reviewed,
|
|
10
|
+
accepted bytes are written.
|
|
11
|
+
|
|
12
|
+
## Candidate diff
|
|
13
|
+
|
|
14
|
+
Show a concrete diff before every write: file path, classification, the
|
|
15
|
+
recorded decision it implements, and the full new bytes (or region-scoped
|
|
16
|
+
hunk for pointer edits). Unrelated files and unrelated hunks are explicitly
|
|
17
|
+
out of scope in the diff header. A stale preview — bytes changed after the
|
|
18
|
+
diff was shown — is re-shown, never applied blindly.
|
|
19
|
+
|
|
20
|
+
## Classification → action
|
|
21
|
+
|
|
22
|
+
Computed by `classifyProjectFile` (current bytes vs `appliedHash`, source
|
|
23
|
+
identity/version/hash vs the sidecar record):
|
|
24
|
+
|
|
25
|
+
| Status | Action |
|
|
26
|
+
|---|---|
|
|
27
|
+
| `unchanged`, no requested change | Byte-identical no-op. No generator call, no timestamp or metadata touch. |
|
|
28
|
+
| `unknown` (missing / corrupt / unrecorded / unknown template / deleted) | Human-owned or broken state. Propose adoption or repair; apply only with explicit `adopt` acceptance. Never overwrite or auto-restore. |
|
|
29
|
+
| `local-edit` | Preserve the file. On a requested update touching it, reconcile: keep the accepted local lines, add the new decision's content, and say what was kept. |
|
|
30
|
+
| `source-update` | Template changed, local bytes clean. Candidate shows the adapted update (re-adapted to the target, not pasted); review before apply. |
|
|
31
|
+
| `conflict` (source and local both changed) | Explicit reconciliation preserving accepted local choices. No automatic three-way merge; a missing base snapshot is reported, never invented. |
|
|
32
|
+
|
|
33
|
+
An apply that meets anything but clean `unchanged` / `source-update`
|
|
34
|
+
without `adopt` / `reconciled` fails loudly instead of overwriting.
|
|
35
|
+
|
|
36
|
+
## Write and record
|
|
37
|
+
|
|
38
|
+
- `applyAcceptedProjectFiles` writes only changes carrying explicit
|
|
39
|
+
`accepted: true`, then records the sidecar entry (origin, evidence,
|
|
40
|
+
accepted decision, inputs, `appliedHash` of the exact bytes written)
|
|
41
|
+
**only for files successfully written and re-read**. Preserve / skip never
|
|
42
|
+
changes `appliedHash`.
|
|
43
|
+
- Partial apply and interruption leave a visible mismatch, never a success
|
|
44
|
+
report: the transaction rolls project files and sidecar back together, and
|
|
45
|
+
the error states exactly what was written and what remains.
|
|
46
|
+
- Repeating a fulfilled request writes nothing new: same bytes re-classify as
|
|
47
|
+
`unchanged`, no duplicate files, adapters, or index entries.
|
|
48
|
+
|
|
49
|
+
## Pointer edits and adapters
|
|
50
|
+
|
|
51
|
+
- Small pointer edits in human-owned files (`AGENTS.md`, docs indexes) are
|
|
52
|
+
key- or region-scoped (`extractRegion` / `replaceRegion`): the managed
|
|
53
|
+
region is replaced, everything outside the sentinels is preserved
|
|
54
|
+
byte-for-byte. They never convert the host file into a generated file and
|
|
55
|
+
never gain provenance entries.
|
|
56
|
+
- Target-local slash adapters resolve their canonical `.ai/commands` source
|
|
57
|
+
and pass invocation inputs; they copy no policy. One adapter per selected
|
|
58
|
+
command, created once, never duplicated on repeat runs. Adapters and
|
|
59
|
+
human-owned files are not installer-owned items.
|
|
60
|
+
|
|
61
|
+
## CLI integration
|
|
62
|
+
|
|
63
|
+
Settings are not written here. The skill shows the `agent-fleet configure`
|
|
64
|
+
preview (`--dry-run`), the user reviews `before` / `after` /
|
|
65
|
+
`expectedHash`, and the CLI applies (`--expect-hash … --yes`). Omitted keys
|
|
66
|
+
stay byte-identical. See `setup-flow.md` §4 for the exact commands.
|
|
67
|
+
|
|
68
|
+
## Semantic bar
|
|
69
|
+
|
|
70
|
+
Every adapted file is checked for meaning, not just paths: no imported
|
|
71
|
+
reference-repository defaults without target evidence, no invented
|
|
72
|
+
paths/checks/commands, no dropped applicable constraint, and consistency
|
|
73
|
+
across the adapted rules, commands, and agent prompts. A path-substitution-only
|
|
74
|
+
result fails review.
|
|
@@ -0,0 +1,16 @@
|
|
|
1
|
+
# Accepted target-file metadata template
|
|
2
|
+
|
|
3
|
+
For accepted template-derived Markdown files under `.ai/rules`, `.ai/commands`, or `.ai/agent-prompts`, prepend:
|
|
4
|
+
|
|
5
|
+
```yaml
|
|
6
|
+
---
|
|
7
|
+
fleet-template: <stable catalog entry id>
|
|
8
|
+
fleet-source-version: <source version>
|
|
9
|
+
---
|
|
10
|
+
```
|
|
11
|
+
|
|
12
|
+
The repository-specific content follows. Native slash adapters must first satisfy their runtime dialect's metadata/registration requirements. For repo-derived files, do **not** invent either template field. The exact final target bytes (including frontmatter) are hashed in the separate sidecar; never put `appliedHash` in the file itself.
|
|
13
|
+
|
|
14
|
+
Read/write `.ai/agent-fleet-ai-state.json` via `bin/lib/project-provenance.js`. Each entry is keyed by a repo-relative path within the three `.ai` catalogues and records `origin`, `evidence` (repo-relative references), `acceptedDecision` (the actual accepted decision), `inputs` (relevant generation inputs) and `appliedHash`. Template origin additionally requires `templateId`, `sourceVersion`, `sourceHash` (SHA-256 of source template bytes). The schema is version 1. A repo-derived origin has no template identity. The sidecar is not installer install-state/ownership and remains on uninstall.
|
|
15
|
+
|
|
16
|
+
The setup capability must resolve the catalogue from the installed Fleet **npm package** using `requirePackageCatalogue(packageRoot)` before any selection; failure is advisory to other Fleet functionality but blocks this setup capability. Never copy the catalogue beneath `.pi/`, infer one from a source checkout when missing from the package, or download it silently. Classification hashes distinguish changes; they are not old bodies or three-way merge bases. Show a candidate diff and require review for updates/conflicts, adopting unknown files explicitly. Do not turn code-derived evidence into normative policy without an accepted decision.
|