@apralabs/apra-fleet 0.3.6 → 0.4.0
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/README.md +245 -257
- package/dist/agents/backlog-groomer.md +287 -0
- package/dist/agents/deployer.md +52 -11
- package/dist/agents/doer.md +32 -7
- package/dist/agents/integ-test-runner.md +151 -61
- package/dist/agents/plan-reviewer.md +74 -17
- package/dist/agents/planner.md +94 -14
- package/dist/agents/regression-test-runner.md +216 -0
- package/dist/agents/reviewer.md +21 -6
- package/dist/agents/schemas/backlog-groomer-input.json +35 -0
- package/dist/agents/schemas/backlog-groomer-output.json +164 -0
- package/dist/agents/schemas/integ-test-runner-output.json +34 -0
- package/dist/agents/schemas/regression-test-runner-input.json +15 -0
- package/dist/agents/schemas/regression-test-runner-output.json +50 -0
- package/dist/agents/schemas/reviewer-output.json +4 -0
- package/dist/cli/agent-transform.d.ts +1 -0
- package/dist/cli/agent-transform.d.ts.map +1 -1
- package/dist/cli/agent-transform.js +77 -0
- package/dist/cli/agent-transform.js.map +1 -1
- package/dist/cli/auth.d.ts +3 -0
- package/dist/cli/auth.d.ts.map +1 -1
- package/dist/cli/auth.js +181 -5
- package/dist/cli/auth.js.map +1 -1
- package/dist/cli/config.d.ts +5 -1
- package/dist/cli/config.d.ts.map +1 -1
- package/dist/cli/config.js +7 -1
- package/dist/cli/config.js.map +1 -1
- package/dist/cli/dolt-install.d.ts +91 -0
- package/dist/cli/dolt-install.d.ts.map +1 -0
- package/dist/cli/dolt-install.js +334 -0
- package/dist/cli/dolt-install.js.map +1 -0
- package/dist/cli/install-guard.d.ts +29 -0
- package/dist/cli/install-guard.d.ts.map +1 -0
- package/dist/cli/install-guard.js +153 -0
- package/dist/cli/install-guard.js.map +1 -0
- package/dist/cli/install.d.ts +44 -3
- package/dist/cli/install.d.ts.map +1 -1
- package/dist/cli/install.js +604 -108
- package/dist/cli/install.js.map +1 -1
- package/dist/cli/join.d.ts +12 -0
- package/dist/cli/join.d.ts.map +1 -0
- package/dist/cli/join.js +87 -0
- package/dist/cli/join.js.map +1 -0
- package/dist/cli/register-member.d.ts +2 -0
- package/dist/cli/register-member.d.ts.map +1 -0
- package/dist/cli/register-member.js +193 -0
- package/dist/cli/register-member.js.map +1 -0
- package/dist/cli/restart.d.ts +2 -0
- package/dist/cli/restart.d.ts.map +1 -0
- package/dist/cli/restart.js +7 -0
- package/dist/cli/restart.js.map +1 -0
- package/dist/cli/spoke.d.ts +35 -0
- package/dist/cli/spoke.d.ts.map +1 -0
- package/dist/cli/spoke.js +212 -0
- package/dist/cli/spoke.js.map +1 -0
- package/dist/cli/start.d.ts +2 -0
- package/dist/cli/start.d.ts.map +1 -0
- package/dist/cli/start.js +92 -0
- package/dist/cli/start.js.map +1 -0
- package/dist/cli/status.d.ts +2 -0
- package/dist/cli/status.d.ts.map +1 -0
- package/dist/cli/status.js +83 -0
- package/dist/cli/status.js.map +1 -0
- package/dist/cli/stop.d.ts +2 -0
- package/dist/cli/stop.d.ts.map +1 -0
- package/dist/cli/stop.js +51 -0
- package/dist/cli/stop.js.map +1 -0
- package/dist/cli/uninstall.d.ts.map +1 -1
- package/dist/cli/uninstall.js +109 -9
- package/dist/cli/uninstall.js.map +1 -1
- package/dist/cli/update.d.ts.map +1 -1
- package/dist/cli/update.js +10 -1
- package/dist/cli/update.js.map +1 -1
- package/dist/cli/workflow-assets.d.ts +37 -0
- package/dist/cli/workflow-assets.d.ts.map +1 -0
- package/dist/cli/workflow-assets.js +144 -0
- package/dist/cli/workflow-assets.js.map +1 -0
- package/dist/cli/workflow.d.ts +75 -0
- package/dist/cli/workflow.d.ts.map +1 -0
- package/dist/cli/workflow.js +397 -0
- package/dist/cli/workflow.js.map +1 -0
- package/dist/hub-service/activity.d.ts +30 -0
- package/dist/hub-service/activity.d.ts.map +1 -0
- package/dist/hub-service/activity.js +20 -0
- package/dist/hub-service/activity.js.map +1 -0
- package/dist/hub-service/audit-log.d.ts +19 -0
- package/dist/hub-service/audit-log.d.ts.map +1 -0
- package/dist/hub-service/audit-log.js +13 -0
- package/dist/hub-service/audit-log.js.map +1 -0
- package/dist/hub-service/db/pool.d.ts +19 -0
- package/dist/hub-service/db/pool.d.ts.map +1 -0
- package/dist/hub-service/db/pool.js +53 -0
- package/dist/hub-service/db/pool.js.map +1 -0
- package/dist/hub-service/enrollment.d.ts +29 -0
- package/dist/hub-service/enrollment.d.ts.map +1 -0
- package/dist/hub-service/enrollment.js +48 -0
- package/dist/hub-service/enrollment.js.map +1 -0
- package/dist/hub-service/envelope-routes.d.ts +46 -0
- package/dist/hub-service/envelope-routes.d.ts.map +1 -0
- package/dist/hub-service/envelope-routes.js +94 -0
- package/dist/hub-service/envelope-routes.js.map +1 -0
- package/dist/hub-service/handlers/installers.d.ts +14 -0
- package/dist/hub-service/handlers/installers.d.ts.map +1 -0
- package/dist/hub-service/handlers/installers.js +8 -0
- package/dist/hub-service/handlers/installers.js.map +1 -0
- package/dist/hub-service/http-server.d.ts +31 -0
- package/dist/hub-service/http-server.d.ts.map +1 -0
- package/dist/hub-service/http-server.js +711 -0
- package/dist/hub-service/http-server.js.map +1 -0
- package/dist/hub-service/hub-jwt.d.ts +30 -0
- package/dist/hub-service/hub-jwt.d.ts.map +1 -0
- package/dist/hub-service/hub-jwt.js +105 -0
- package/dist/hub-service/hub-jwt.js.map +1 -0
- package/dist/hub-service/jwt-revocation.d.ts +20 -0
- package/dist/hub-service/jwt-revocation.d.ts.map +1 -0
- package/dist/hub-service/jwt-revocation.js +18 -0
- package/dist/hub-service/jwt-revocation.js.map +1 -0
- package/dist/hub-service/machines.d.ts +16 -0
- package/dist/hub-service/machines.d.ts.map +1 -0
- package/dist/hub-service/machines.js +14 -0
- package/dist/hub-service/machines.js.map +1 -0
- package/dist/hub-service/main.d.ts +3 -0
- package/dist/hub-service/main.d.ts.map +1 -0
- package/dist/hub-service/main.js +64 -0
- package/dist/hub-service/main.js.map +1 -0
- package/dist/hub-service/member-tokens.d.ts +11 -0
- package/dist/hub-service/member-tokens.d.ts.map +1 -0
- package/dist/hub-service/member-tokens.js +49 -0
- package/dist/hub-service/member-tokens.js.map +1 -0
- package/dist/hub-service/member-view.d.ts +20 -0
- package/dist/hub-service/member-view.d.ts.map +1 -0
- package/dist/hub-service/member-view.js +76 -0
- package/dist/hub-service/member-view.js.map +1 -0
- package/dist/hub-service/members.d.ts +44 -0
- package/dist/hub-service/members.d.ts.map +1 -0
- package/dist/hub-service/members.js +25 -0
- package/dist/hub-service/members.js.map +1 -0
- package/dist/hub-service/presence.d.ts +40 -0
- package/dist/hub-service/presence.d.ts.map +1 -0
- package/dist/hub-service/presence.js +44 -0
- package/dist/hub-service/presence.js.map +1 -0
- package/dist/hub-service/project-view.d.ts +12 -0
- package/dist/hub-service/project-view.d.ts.map +1 -0
- package/dist/hub-service/project-view.js +34 -0
- package/dist/hub-service/project-view.js.map +1 -0
- package/dist/hub-service/projects.d.ts +48 -0
- package/dist/hub-service/projects.d.ts.map +1 -0
- package/dist/hub-service/projects.js +80 -0
- package/dist/hub-service/projects.js.map +1 -0
- package/dist/hub-service/relay-queue.d.ts +115 -0
- package/dist/hub-service/relay-queue.d.ts.map +1 -0
- package/dist/hub-service/relay-queue.js +148 -0
- package/dist/hub-service/relay-queue.js.map +1 -0
- package/dist/hub-service/session-jwt.d.ts +10 -0
- package/dist/hub-service/session-jwt.d.ts.map +1 -0
- package/dist/hub-service/session-jwt.js +69 -0
- package/dist/hub-service/session-jwt.js.map +1 -0
- package/dist/hub-service/usage.d.ts +40 -0
- package/dist/hub-service/usage.d.ts.map +1 -0
- package/dist/hub-service/usage.js +25 -0
- package/dist/hub-service/usage.js.map +1 -0
- package/dist/hub-service/users.d.ts +56 -0
- package/dist/hub-service/users.d.ts.map +1 -0
- package/dist/hub-service/users.js +72 -0
- package/dist/hub-service/users.js.map +1 -0
- package/dist/hub-service/workspaces.d.ts +20 -0
- package/dist/hub-service/workspaces.d.ts.map +1 -0
- package/dist/hub-service/workspaces.js +10 -0
- package/dist/hub-service/workspaces.js.map +1 -0
- package/dist/index.js +179 -132
- package/dist/index.js.map +1 -1
- package/dist/os/linux.d.ts +13 -0
- package/dist/os/linux.d.ts.map +1 -1
- package/dist/os/linux.js +62 -3
- package/dist/os/linux.js.map +1 -1
- package/dist/os/os-commands.d.ts +10 -0
- package/dist/os/os-commands.d.ts.map +1 -1
- package/dist/os/windows.d.ts +1 -0
- package/dist/os/windows.d.ts.map +1 -1
- package/dist/os/windows.js +21 -1
- package/dist/os/windows.js.map +1 -1
- package/dist/paths.d.ts +23 -0
- package/dist/paths.d.ts.map +1 -1
- package/dist/paths.js +29 -0
- package/dist/paths.js.map +1 -1
- package/dist/providers/agy.d.ts +9 -2
- package/dist/providers/agy.d.ts.map +1 -1
- package/dist/providers/agy.js +127 -14
- package/dist/providers/agy.js.map +1 -1
- package/dist/providers/claude.d.ts +6 -2
- package/dist/providers/claude.d.ts.map +1 -1
- package/dist/providers/claude.js +248 -9
- package/dist/providers/claude.js.map +1 -1
- package/dist/providers/codex.d.ts +3 -2
- package/dist/providers/codex.d.ts.map +1 -1
- package/dist/providers/codex.js +7 -0
- package/dist/providers/codex.js.map +1 -1
- package/dist/providers/copilot.d.ts +3 -2
- package/dist/providers/copilot.d.ts.map +1 -1
- package/dist/providers/copilot.js +8 -1
- package/dist/providers/copilot.js.map +1 -1
- package/dist/providers/gemini.d.ts +3 -2
- package/dist/providers/gemini.d.ts.map +1 -1
- package/dist/providers/gemini.js +11 -1
- package/dist/providers/gemini.js.map +1 -1
- package/dist/providers/index.d.ts +1 -0
- package/dist/providers/index.d.ts.map +1 -1
- package/dist/providers/index.js +3 -0
- package/dist/providers/index.js.map +1 -1
- package/dist/providers/none.d.ts +51 -0
- package/dist/providers/none.d.ts.map +1 -0
- package/dist/providers/none.js +103 -0
- package/dist/providers/none.js.map +1 -0
- package/dist/providers/opencode.d.ts +4 -2
- package/dist/providers/opencode.d.ts.map +1 -1
- package/dist/providers/opencode.js +49 -0
- package/dist/providers/opencode.js.map +1 -1
- package/dist/providers/provider.d.ts +79 -1
- package/dist/providers/provider.d.ts.map +1 -1
- package/dist/providers/provider.js +10 -0
- package/dist/providers/provider.js.map +1 -1
- package/dist/services/agent-provisioner.d.ts +3 -3
- package/dist/services/agent-provisioner.d.ts.map +1 -1
- package/dist/services/agent-provisioner.js +12 -5
- package/dist/services/agent-provisioner.js.map +1 -1
- package/dist/services/auth-socket.d.ts.map +1 -1
- package/dist/services/auth-socket.js +2 -0
- package/dist/services/auth-socket.js.map +1 -1
- package/dist/services/budget-awareness.d.ts +130 -0
- package/dist/services/budget-awareness.d.ts.map +1 -0
- package/dist/services/budget-awareness.js +129 -0
- package/dist/services/budget-awareness.js.map +1 -0
- package/dist/services/cloud-sync.d.ts +35 -0
- package/dist/services/cloud-sync.d.ts.map +1 -0
- package/dist/services/cloud-sync.js +90 -0
- package/dist/services/cloud-sync.js.map +1 -0
- package/dist/services/context-admission.d.ts +82 -0
- package/dist/services/context-admission.d.ts.map +1 -0
- package/dist/services/context-admission.js +136 -0
- package/dist/services/context-admission.js.map +1 -0
- package/dist/services/event-bus.d.ts +27 -0
- package/dist/services/event-bus.d.ts.map +1 -0
- package/dist/services/event-bus.js +20 -0
- package/dist/services/event-bus.js.map +1 -0
- package/dist/services/file-chunker.d.ts +38 -0
- package/dist/services/file-chunker.d.ts.map +1 -0
- package/dist/services/file-chunker.js +63 -0
- package/dist/services/file-chunker.js.map +1 -0
- package/dist/services/file-transfer-relay.d.ts +55 -0
- package/dist/services/file-transfer-relay.d.ts.map +1 -0
- package/dist/services/file-transfer-relay.js +115 -0
- package/dist/services/file-transfer-relay.js.map +1 -0
- package/dist/services/github-app.d.ts.map +1 -1
- package/dist/services/github-app.js +1 -0
- package/dist/services/github-app.js.map +1 -1
- package/dist/services/http-transport.d.ts +25 -0
- package/dist/services/http-transport.d.ts.map +1 -0
- package/dist/services/http-transport.js +371 -0
- package/dist/services/http-transport.js.map +1 -0
- package/dist/services/hub-client.d.ts +69 -0
- package/dist/services/hub-client.d.ts.map +1 -0
- package/dist/services/hub-client.js +217 -0
- package/dist/services/hub-client.js.map +1 -0
- package/dist/services/jwt.d.ts +17 -0
- package/dist/services/jwt.d.ts.map +1 -0
- package/dist/services/jwt.js +70 -0
- package/dist/services/jwt.js.map +1 -0
- package/dist/services/known-sessions.d.ts +8 -0
- package/dist/services/known-sessions.d.ts.map +1 -0
- package/dist/services/known-sessions.js +40 -0
- package/dist/services/known-sessions.js.map +1 -0
- package/dist/services/model-pricing.d.ts +36 -0
- package/dist/services/model-pricing.d.ts.map +1 -0
- package/dist/services/model-pricing.js +108 -0
- package/dist/services/model-pricing.js.map +1 -0
- package/dist/services/orphan-recovery.d.ts +56 -0
- package/dist/services/orphan-recovery.d.ts.map +1 -0
- package/dist/services/orphan-recovery.js +111 -0
- package/dist/services/orphan-recovery.js.map +1 -0
- package/dist/services/pending-responses.d.ts +23 -0
- package/dist/services/pending-responses.d.ts.map +1 -0
- package/dist/services/pending-responses.js +52 -0
- package/dist/services/pending-responses.js.map +1 -0
- package/dist/services/registry.d.ts +4 -1
- package/dist/services/registry.d.ts.map +1 -1
- package/dist/services/registry.js +3 -0
- package/dist/services/registry.js.map +1 -1
- package/dist/services/relay-context.d.ts +23 -0
- package/dist/services/relay-context.d.ts.map +1 -0
- package/dist/services/relay-context.js +8 -0
- package/dist/services/relay-context.js.map +1 -0
- package/dist/services/relay-executor.d.ts +68 -0
- package/dist/services/relay-executor.d.ts.map +1 -0
- package/dist/services/relay-executor.js +70 -0
- package/dist/services/relay-executor.js.map +1 -0
- package/dist/services/relay-request.d.ts +65 -0
- package/dist/services/relay-request.d.ts.map +1 -0
- package/dist/services/relay-request.js +129 -0
- package/dist/services/relay-request.js.map +1 -0
- package/dist/services/relay-strategy.d.ts +19 -0
- package/dist/services/relay-strategy.d.ts.map +1 -0
- package/dist/services/relay-strategy.js +111 -0
- package/dist/services/relay-strategy.js.map +1 -0
- package/dist/services/service-manager/index.d.ts +5 -0
- package/dist/services/service-manager/index.d.ts.map +1 -0
- package/dist/services/service-manager/index.js +66 -0
- package/dist/services/service-manager/index.js.map +1 -0
- package/dist/services/service-manager/linux.d.ts +10 -0
- package/dist/services/service-manager/linux.d.ts.map +1 -0
- package/dist/services/service-manager/linux.js +97 -0
- package/dist/services/service-manager/linux.js.map +1 -0
- package/dist/services/service-manager/macos.d.ts +10 -0
- package/dist/services/service-manager/macos.d.ts.map +1 -0
- package/dist/services/service-manager/macos.js +94 -0
- package/dist/services/service-manager/macos.js.map +1 -0
- package/dist/services/service-manager/types.d.ts +18 -0
- package/dist/services/service-manager/types.d.ts.map +1 -0
- package/dist/services/service-manager/types.js +5 -0
- package/dist/services/service-manager/types.js.map +1 -0
- package/dist/services/service-manager/windows.d.ts +10 -0
- package/dist/services/service-manager/windows.d.ts.map +1 -0
- package/dist/services/service-manager/windows.js +73 -0
- package/dist/services/service-manager/windows.js.map +1 -0
- package/dist/services/session-registry.d.ts +70 -0
- package/dist/services/session-registry.d.ts.map +1 -0
- package/dist/services/session-registry.js +91 -0
- package/dist/services/session-registry.js.map +1 -0
- package/dist/services/singleton.d.ts +15 -0
- package/dist/services/singleton.d.ts.map +1 -0
- package/dist/services/singleton.js +98 -0
- package/dist/services/singleton.js.map +1 -0
- package/dist/services/sprint-coordination.d.ts +168 -0
- package/dist/services/sprint-coordination.d.ts.map +1 -0
- package/dist/services/sprint-coordination.js +564 -0
- package/dist/services/sprint-coordination.js.map +1 -0
- package/dist/services/ssh.d.ts.map +1 -1
- package/dist/services/ssh.js +70 -3
- package/dist/services/ssh.js.map +1 -1
- package/dist/services/stall/log-path-resolver.d.ts.map +1 -1
- package/dist/services/stall/log-path-resolver.js +8 -1
- package/dist/services/stall/log-path-resolver.js.map +1 -1
- package/dist/services/stall/stall-detector.d.ts.map +1 -1
- package/dist/services/stall/stall-detector.js +39 -7
- package/dist/services/stall/stall-detector.js.map +1 -1
- package/dist/services/stall/stall-poller.d.ts +16 -0
- package/dist/services/stall/stall-poller.d.ts.map +1 -1
- package/dist/services/stall/stall-poller.js +136 -18
- package/dist/services/stall/stall-poller.js.map +1 -1
- package/dist/services/strategy.d.ts.map +1 -1
- package/dist/services/strategy.js +55 -5
- package/dist/services/strategy.js.map +1 -1
- package/dist/services/substitution-engine.d.ts +20 -0
- package/dist/services/substitution-engine.d.ts.map +1 -0
- package/dist/services/substitution-engine.js +92 -0
- package/dist/services/substitution-engine.js.map +1 -0
- package/dist/services/task-cleanup.d.ts.map +1 -1
- package/dist/services/task-cleanup.js +1 -9
- package/dist/services/task-cleanup.js.map +1 -1
- package/dist/services/token-issuer.d.ts +47 -0
- package/dist/services/token-issuer.d.ts.map +1 -0
- package/dist/services/token-issuer.js +63 -0
- package/dist/services/token-issuer.js.map +1 -0
- package/dist/services/tool-registry.d.ts +3 -0
- package/dist/services/tool-registry.d.ts.map +1 -0
- package/dist/services/tool-registry.js +139 -0
- package/dist/services/tool-registry.js.map +1 -0
- package/dist/services/user-config.d.ts +14 -0
- package/dist/services/user-config.d.ts.map +1 -1
- package/dist/services/user-config.js +55 -0
- package/dist/services/user-config.js.map +1 -1
- package/dist/services/vcs/types.d.ts +44 -0
- package/dist/services/vcs/types.d.ts.map +1 -1
- package/dist/skills/fleet-sprint-cli/SKILL.md +103 -0
- package/dist/skills/pm/cost.md +3 -0
- package/dist/skills/pm/doer-reviewer-loop.md +3 -0
- package/dist/tools/check-status.d.ts.map +1 -1
- package/dist/tools/check-status.js +8 -2
- package/dist/tools/check-status.js.map +1 -1
- package/dist/tools/child-id-allocator.d.ts +45 -0
- package/dist/tools/child-id-allocator.d.ts.map +1 -0
- package/dist/tools/child-id-allocator.js +62 -0
- package/dist/tools/child-id-allocator.js.map +1 -0
- package/dist/tools/cloud-control.d.ts +2 -2
- package/dist/tools/compose-permissions.d.ts +12 -4
- package/dist/tools/compose-permissions.d.ts.map +1 -1
- package/dist/tools/compose-permissions.js +55 -4
- package/dist/tools/compose-permissions.js.map +1 -1
- package/dist/tools/dolt-push-mutex.d.ts +44 -0
- package/dist/tools/dolt-push-mutex.d.ts.map +1 -0
- package/dist/tools/dolt-push-mutex.js +83 -0
- package/dist/tools/dolt-push-mutex.js.map +1 -0
- package/dist/tools/execute-command.d.ts +11 -1
- package/dist/tools/execute-command.d.ts.map +1 -1
- package/dist/tools/execute-command.js +22 -5
- package/dist/tools/execute-command.js.map +1 -1
- package/dist/tools/execute-prompt.d.ts +72 -12
- package/dist/tools/execute-prompt.d.ts.map +1 -1
- package/dist/tools/execute-prompt.js +962 -71
- package/dist/tools/execute-prompt.js.map +1 -1
- package/dist/tools/get-member-model-pricing.d.ts +21 -0
- package/dist/tools/get-member-model-pricing.d.ts.map +1 -0
- package/dist/tools/get-member-model-pricing.js +29 -0
- package/dist/tools/get-member-model-pricing.js.map +1 -0
- package/dist/tools/list-members.d.ts.map +1 -1
- package/dist/tools/list-members.js +39 -7
- package/dist/tools/list-members.js.map +1 -1
- package/dist/tools/member-detail.d.ts +1 -1
- package/dist/tools/member-detail.d.ts.map +1 -1
- package/dist/tools/member-detail.js +8 -2
- package/dist/tools/member-detail.js.map +1 -1
- package/dist/tools/member-reservation.d.ts +29 -0
- package/dist/tools/member-reservation.d.ts.map +1 -0
- package/dist/tools/member-reservation.js +71 -0
- package/dist/tools/member-reservation.js.map +1 -0
- package/dist/tools/provision-vcs-auth.d.ts +7 -7
- package/dist/tools/provision-vcs-auth.js +1 -1
- package/dist/tools/provision-vcs-auth.js.map +1 -1
- package/dist/tools/register-member.d.ts +17 -5
- package/dist/tools/register-member.d.ts.map +1 -1
- package/dist/tools/register-member.js +144 -5
- package/dist/tools/register-member.js.map +1 -1
- package/dist/tools/remove-member.d.ts +1 -1
- package/dist/tools/report-status.d.ts +33 -0
- package/dist/tools/report-status.d.ts.map +1 -0
- package/dist/tools/report-status.js +44 -0
- package/dist/tools/report-status.js.map +1 -0
- package/dist/tools/respond-to-message.d.ts +21 -0
- package/dist/tools/respond-to-message.d.ts.map +1 -0
- package/dist/tools/respond-to-message.js +23 -0
- package/dist/tools/respond-to-message.js.map +1 -0
- package/dist/tools/send-files.d.ts +3 -0
- package/dist/tools/send-files.d.ts.map +1 -1
- package/dist/tools/send-files.js +88 -8
- package/dist/tools/send-files.js.map +1 -1
- package/dist/tools/send-message.d.ts +27 -0
- package/dist/tools/send-message.d.ts.map +1 -0
- package/dist/tools/send-message.js +46 -0
- package/dist/tools/send-message.js.map +1 -0
- package/dist/tools/shutdown-server.d.ts +2 -0
- package/dist/tools/shutdown-server.d.ts.map +1 -1
- package/dist/tools/shutdown-server.js +19 -0
- package/dist/tools/shutdown-server.js.map +1 -1
- package/dist/tools/update-member.d.ts +8 -8
- package/dist/tools/update-member.d.ts.map +1 -1
- package/dist/tools/update-member.js +11 -1
- package/dist/tools/update-member.js.map +1 -1
- package/dist/types.d.ts +15 -3
- package/dist/types.d.ts.map +1 -1
- package/dist/utils/agent-helpers.d.ts +2 -1
- package/dist/utils/agent-helpers.d.ts.map +1 -1
- package/dist/utils/agent-helpers.js +7 -2
- package/dist/utils/agent-helpers.js.map +1 -1
- package/dist/utils/pid-helpers.d.ts +15 -0
- package/dist/utils/pid-helpers.d.ts.map +1 -1
- package/dist/utils/pid-helpers.js +23 -0
- package/dist/utils/pid-helpers.js.map +1 -1
- package/dist/utils/process-utils.d.ts +3 -0
- package/dist/utils/process-utils.d.ts.map +1 -0
- package/dist/utils/process-utils.js +42 -0
- package/dist/utils/process-utils.js.map +1 -0
- package/dist/utils/prompt-errors.d.ts +2 -1
- package/dist/utils/prompt-errors.d.ts.map +1 -1
- package/dist/utils/prompt-errors.js +13 -3
- package/dist/utils/prompt-errors.js.map +1 -1
- package/dist/utils/workspace-trust.d.ts +24 -0
- package/dist/utils/workspace-trust.d.ts.map +1 -0
- package/dist/utils/workspace-trust.js +35 -0
- package/dist/utils/workspace-trust.js.map +1 -0
- package/dist/workflows/auto-sprint.js +450 -87
- package/package.json +35 -7
- package/packages/apra-fleet-client/package.json +26 -0
- package/packages/apra-fleet-client/src/client/api.mjs +396 -0
- package/packages/apra-fleet-client/src/client/client.mjs +146 -0
- package/packages/apra-fleet-client/src/client/errors.mjs +71 -0
- package/packages/apra-fleet-client/src/client/factory.mjs +65 -0
- package/packages/apra-fleet-client/src/client/server-resolution.mjs +265 -0
- package/packages/apra-fleet-client/src/client/transport.mjs +327 -0
- package/packages/apra-fleet-se/apra-pm/agents/backlog-groomer.md +287 -0
- package/packages/apra-fleet-se/apra-pm/agents/ci-watcher.md +89 -0
- package/packages/apra-fleet-se/apra-pm/agents/deployer.md +139 -0
- package/packages/apra-fleet-se/apra-pm/agents/doer.md +225 -0
- package/packages/apra-fleet-se/apra-pm/agents/harvester.md +169 -0
- package/packages/apra-fleet-se/apra-pm/agents/integ-test-runner.md +316 -0
- package/packages/apra-fleet-se/apra-pm/agents/plan-reviewer.md +188 -0
- package/packages/apra-fleet-se/apra-pm/agents/planner.md +239 -0
- package/packages/apra-fleet-se/apra-pm/agents/regression-test-runner.md +216 -0
- package/packages/apra-fleet-se/apra-pm/agents/reviewer.md +174 -0
- package/packages/apra-fleet-se/apra-pm/agents/schemas/backlog-groomer-input.json +35 -0
- package/packages/apra-fleet-se/apra-pm/agents/schemas/backlog-groomer-output.json +164 -0
- package/packages/apra-fleet-se/apra-pm/agents/schemas/ci-watcher-input.json +26 -0
- package/packages/apra-fleet-se/apra-pm/agents/schemas/ci-watcher-output.json +18 -0
- package/packages/apra-fleet-se/apra-pm/agents/schemas/deployer-input.json +19 -0
- package/packages/apra-fleet-se/apra-pm/agents/schemas/deployer-output.json +17 -0
- package/packages/apra-fleet-se/apra-pm/agents/schemas/doer-input.json +25 -0
- package/packages/apra-fleet-se/apra-pm/agents/schemas/doer-output.json +22 -0
- package/packages/apra-fleet-se/apra-pm/agents/schemas/harvester-input.json +31 -0
- package/packages/apra-fleet-se/apra-pm/agents/schemas/harvester-output.json +18 -0
- package/packages/apra-fleet-se/apra-pm/agents/schemas/integ-test-runner-input.json +20 -0
- package/packages/apra-fleet-se/apra-pm/agents/schemas/integ-test-runner-output.json +61 -0
- package/packages/apra-fleet-se/apra-pm/agents/schemas/plan-reviewer-input.json +15 -0
- package/packages/apra-fleet-se/apra-pm/agents/schemas/plan-reviewer-output.json +30 -0
- package/packages/apra-fleet-se/apra-pm/agents/schemas/regression-test-runner-input.json +15 -0
- package/packages/apra-fleet-se/apra-pm/agents/schemas/regression-test-runner-output.json +50 -0
- package/packages/apra-fleet-se/apra-pm/agents/schemas/reviewer-input.json +25 -0
- package/packages/apra-fleet-se/apra-pm/agents/schemas/reviewer-output.json +38 -0
- package/packages/apra-fleet-se/apra-pm/skills/pm/SKILL.md +402 -0
- package/packages/apra-fleet-se/apra-pm/skills/pm/beads.md +142 -0
- package/packages/apra-fleet-se/apra-pm/skills/pm/cost.md +157 -0
- package/packages/apra-fleet-se/apra-pm/skills/pm/doer-reviewer-loop.md +300 -0
- package/packages/apra-fleet-se/apra-pm/skills/pm/fleet-addendum.md +121 -0
- package/packages/apra-fleet-se/apra-pm/skills/pm/simple-sprint.md +65 -0
- package/packages/apra-fleet-se/apra-pm/skills/pm/sprint.md +327 -0
- package/packages/apra-fleet-se/apra-pm/skills/pm/worktrees.md +92 -0
- package/packages/apra-fleet-se/apra-pm/version.json +3 -0
- package/packages/apra-fleet-se/bin/cli.mjs +857 -0
- package/packages/apra-fleet-se/bin/serve.mjs +383 -0
- package/packages/apra-fleet-se/fleet-sprint/conflict-ladder.mjs +178 -0
- package/packages/apra-fleet-se/fleet-sprint/contracts.mjs +914 -0
- package/packages/apra-fleet-se/fleet-sprint/dispatch-safety-guard.mjs +177 -0
- package/packages/apra-fleet-se/fleet-sprint/docs/README.md +191 -0
- package/packages/apra-fleet-se/fleet-sprint/docs/coach-role-design.md +151 -0
- package/packages/apra-fleet-se/fleet-sprint/docs/dolt-tier2-runbook.md +127 -0
- package/packages/apra-fleet-se/fleet-sprint/docs/fleet-sprint-diagram.md +94 -0
- package/packages/apra-fleet-se/fleet-sprint/docs/stabilization-log.md +1125 -0
- package/packages/apra-fleet-se/fleet-sprint/dolt-literal-guard.mjs +72 -0
- package/packages/apra-fleet-se/fleet-sprint/dolt-recovery-path-b.mjs +339 -0
- package/packages/apra-fleet-se/fleet-sprint/dolt-recovery-tier2.mjs +360 -0
- package/packages/apra-fleet-se/fleet-sprint/dolt-recovery.mjs +363 -0
- package/packages/apra-fleet-se/fleet-sprint/dolt-sync.mjs +1244 -0
- package/packages/apra-fleet-se/fleet-sprint/errors.mjs +572 -0
- package/packages/apra-fleet-se/fleet-sprint/full-db-fetch-guard.mjs +118 -0
- package/packages/apra-fleet-se/fleet-sprint/runner.js +9447 -0
- package/packages/apra-fleet-se/fleet-sprint/skills/fleet-sprint-cli/SKILL.md +103 -0
- package/packages/apra-fleet-se/fleet-sprint/sprint-lock.mjs +140 -0
- package/packages/apra-fleet-se/fleet-sprint/vcs-module.mjs +435 -0
- package/packages/apra-fleet-se/fleet-sprint/vcs-providers/azure-devops.mjs +68 -0
- package/packages/apra-fleet-se/fleet-sprint/vcs-providers/bitbucket.mjs +53 -0
- package/packages/apra-fleet-se/fleet-sprint/vcs-providers/dolt.mjs +146 -0
- package/packages/apra-fleet-se/fleet-sprint/vcs-providers/generic-git.mjs +176 -0
- package/packages/apra-fleet-se/fleet-sprint/vcs-providers/github.mjs +222 -0
- package/packages/apra-fleet-se/fleet-sprint/vcs-providers/index.mjs +218 -0
- package/packages/apra-fleet-se/fleet-sprint/viewer-extensions.mjs +882 -0
- package/packages/apra-fleet-se/package.json +28 -0
- package/packages/apra-fleet-se/workflow.json +1 -0
- package/packages/apra-fleet-workflow/package.json +30 -0
- package/packages/apra-fleet-workflow/src/viewer/command-output-cap.mjs +112 -0
- package/packages/apra-fleet-workflow/src/viewer/debounced-writer.mjs +153 -0
- package/packages/apra-fleet-workflow/src/viewer/html-utils.mjs +31 -0
- package/packages/apra-fleet-workflow/src/viewer/index.mjs +1325 -0
- package/packages/apra-fleet-workflow/src/viewer/lean-state.mjs +237 -0
- package/packages/apra-fleet-workflow/src/viewer/run-state-paths.mjs +130 -0
- package/packages/apra-fleet-workflow/src/viewer/sprint-state-paths.mjs +29 -0
- package/packages/apra-fleet-workflow/src/workflow/engine.mjs +200 -0
- package/packages/apra-fleet-workflow/src/workflow/errors.mjs +146 -0
- package/packages/apra-fleet-workflow/src/workflow/index.mjs +1723 -0
- package/packages/apra-fleet-workflow/src/workflow/journal.mjs +291 -0
- package/packages/apra-fleet-workflow/src/workflow/pricing.mjs +99 -0
- package/packages/apra-fleet-workflow/src/workflow/vetting.mjs +111 -0
- package/scripts/agy-transcript-reader.js +1 -0
- package/scripts/fleet-statusline.sh +17 -13
- package/skills/fleet/SKILL.md +37 -2
- package/skills/fleet/beads.md +14 -7
- package/skills/fleet/permissions.md +50 -0
- package/skills/fleet/profiles/base-dev.json +1 -0
- package/skills/fleet/profiles/base-reviewer.json +1 -0
- package/skills/fleet/profiles/node.json +2 -2
- package/version.json +1 -1
- package/scripts/agy-settings-merge.js +0 -27
- /package/{dist → packages/apra-fleet-se/apra-pm}/agents/_shared/GRAPH-SEMANTICS.md +0 -0
|
@@ -0,0 +1,89 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: ci-watcher
|
|
3
|
+
description: Polls CI for the sprint HEAD SHA; returns green/red/not_configured/pending.
|
|
4
|
+
tools: [Bash]
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# CI Status Check
|
|
8
|
+
|
|
9
|
+
You check whether CI is passing for the sprint branch. You do not write code or modify files.
|
|
10
|
+
|
|
11
|
+
## Inputs
|
|
12
|
+
|
|
13
|
+
Your dispatch prompt must supply ONE of the two scoping forms:
|
|
14
|
+
|
|
15
|
+
- **Branch-scoped** (default): `branch` (required) -- the sprint branch to check CI for --
|
|
16
|
+
plus `expectedHeadSha` (required) -- the commit SHA CI should have run against.
|
|
17
|
+
- **PR-scoped** (post-PR dispatch): `prNumber` (required) -- the pull request whose checks
|
|
18
|
+
to watch. Used by orchestrators that raise the PR first and then watch its checks; the
|
|
19
|
+
`expectedHeadSha` requirement does not apply (the PR pins the commit range).
|
|
20
|
+
|
|
21
|
+
**Missing-input behavior**: if neither form is satisfied (no `prNumber`, and `branch` or
|
|
22
|
+
`expectedHeadSha` missing), do not guess or check an arbitrary branch. Return
|
|
23
|
+
`status: "pending"` with `notes` stating which input was missing.
|
|
24
|
+
|
|
25
|
+
## Step 1 -- List recent CI runs
|
|
26
|
+
|
|
27
|
+
Branch-scoped:
|
|
28
|
+
```bash
|
|
29
|
+
gh run list --branch <branch> --limit 5 --json databaseId,status,conclusion,headSha,url
|
|
30
|
+
```
|
|
31
|
+
|
|
32
|
+
PR-scoped:
|
|
33
|
+
```bash
|
|
34
|
+
gh run list --pr <prNumber> --limit 5 --json databaseId,status,conclusion,headSha,url
|
|
35
|
+
```
|
|
36
|
+
(In PR-scoped mode, apply Step 2 to the runs for the PR's head commit instead of
|
|
37
|
+
`expectedHeadSha`.)
|
|
38
|
+
|
|
39
|
+
## Step 2 -- Interpret the result
|
|
40
|
+
|
|
41
|
+
**No runs returned**: CI has never been triggered on this branch.
|
|
42
|
+
Return `status: "not_configured"`.
|
|
43
|
+
|
|
44
|
+
**Run found for the expected HEAD SHA with conclusion "success"**:
|
|
45
|
+
Return `status: "green"`.
|
|
46
|
+
|
|
47
|
+
**Run found with conclusion "failure" or "cancelled"**:
|
|
48
|
+
Return `status: "red"` with the run URL and a brief failure summary in `notes`.
|
|
49
|
+
|
|
50
|
+
**Run found with status "in_progress" or "queued"**:
|
|
51
|
+
Wait and poll. Use:
|
|
52
|
+
```bash
|
|
53
|
+
gh run watch <databaseId> --exit-status
|
|
54
|
+
```
|
|
55
|
+
Poll for up to 10 minutes. If it passes: `status: "green"`.
|
|
56
|
+
If it fails: `status: "red"` with notes.
|
|
57
|
+
If still running after 10 minutes: `status: "pending"` with notes.
|
|
58
|
+
|
|
59
|
+
**No run found for the expected HEAD SHA but older runs exist**:
|
|
60
|
+
CI may not have triggered for the latest push. Wait 60 seconds and check once more.
|
|
61
|
+
If still absent: `status: "pending"` with notes explaining what was found.
|
|
62
|
+
|
|
63
|
+
## Output schema
|
|
64
|
+
|
|
65
|
+
The canonical machine-readable contract for this output lives in the sibling file
|
|
66
|
+
`agents/schemas/ci-watcher-output.json`. Example instance (valid JSON, not a pseudo-JSON
|
|
67
|
+
placeholder):
|
|
68
|
+
|
|
69
|
+
```json
|
|
70
|
+
{
|
|
71
|
+
"status": "green",
|
|
72
|
+
"notes": "Run 123456789 succeeded for expected HEAD SHA a1b2c3d."
|
|
73
|
+
}
|
|
74
|
+
```
|
|
75
|
+
|
|
76
|
+
**Precedence**: If your dispatch prompt includes a JSON schema instruction, that schema is
|
|
77
|
+
authoritative -- respond with exactly that JSON and nothing else. It is expected to match
|
|
78
|
+
this contract; if it differs, follow the dispatch prompt.
|
|
79
|
+
|
|
80
|
+
**Graceful degradation**: If dispatched without a schema instruction (e.g. informal/manual
|
|
81
|
+
use), report the same decision fields, in this JSON shape if the caller is an orchestrator,
|
|
82
|
+
or as prose if you are answering a human directly.
|
|
83
|
+
|
|
84
|
+
## Rules
|
|
85
|
+
|
|
86
|
+
- Do NOT modify any files
|
|
87
|
+
- Do NOT trigger CI manually unless explicitly asked
|
|
88
|
+
- Do NOT interpret CI configuration files -- only observe run results
|
|
89
|
+
- Time limit: 10 minutes total before returning `pending`
|
|
@@ -0,0 +1,139 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: deployer
|
|
3
|
+
description: Follows deploy.md to deploy the software onto the target environment and verify it with the smoke test.
|
|
4
|
+
tools: [Read, Bash]
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Deployment
|
|
8
|
+
|
|
9
|
+
You deploy the software by executing the `deploy.md` runbook. You do not write
|
|
10
|
+
code or modify project files. You do NOT run `integ-test-playbook.md` -- the
|
|
11
|
+
test sandbox lifecycle (Setup / Reset / Teardown) and the tests themselves
|
|
12
|
+
belong to `integ-test-runner`, which owns that playbook end to end.
|
|
13
|
+
|
|
14
|
+
## Inputs
|
|
15
|
+
|
|
16
|
+
Your dispatch prompt must supply:
|
|
17
|
+
|
|
18
|
+
- `operation` (required) -- must be `deploy`. (`setup`, `reset`, and
|
|
19
|
+
`teardown` are no longer deployer operations; they moved to
|
|
20
|
+
`integ-test-runner`.)
|
|
21
|
+
- Repo root path (required) -- where `deploy.md` lives.
|
|
22
|
+
|
|
23
|
+
**Missing-input behavior**: if `operation` is not supplied, do not guess. Return
|
|
24
|
+
`deployed: false` with `notes` stating the operation was not specified. If
|
|
25
|
+
`operation` is `setup`, `reset`, or `teardown`, return `deployed: false` with
|
|
26
|
+
`notes` stating that operation moved to `integ-test-runner` -- do not run the
|
|
27
|
+
playbook yourself. If `deploy.md` is entirely absent (not just missing a
|
|
28
|
+
section), return `deployed: false` with `notes` naming the missing file -- do
|
|
29
|
+
not improvise deploy steps that are not written down in the runbook.
|
|
30
|
+
|
|
31
|
+
## Step 0 -- Check permissions before running anything
|
|
32
|
+
|
|
33
|
+
Read `deploy.md`. Look for a `## Permissions` section. If found, verify each
|
|
34
|
+
listed command prefix is covered by the MERGED effective permission set --
|
|
35
|
+
on Claude Code that means SOME entry in `permissions.allow` of EITHER
|
|
36
|
+
`.claude/settings.json` (the team-committed, shared baseline) OR
|
|
37
|
+
`.claude/settings.local.json` (the per-checkout, individual/gitignored file;
|
|
38
|
+
this is the ONLY file the fleet's `compose_permissions` tool ever writes to
|
|
39
|
+
for Claude Code members -- see `skills/fleet/permissions.md`). Claude Code
|
|
40
|
+
merges `permissions.allow` from both files, so a grant in EITHER one counts
|
|
41
|
+
as coverage; checking only `settings.json` misses every grant
|
|
42
|
+
`compose_permissions` delivered. A broader prefix entry counts as coverage
|
|
43
|
+
too -- e.g. `Bash(docker:*)` covers `docker compose`. Other providers keep
|
|
44
|
+
the equivalent allowlist in their own native config file (see
|
|
45
|
+
`src/providers/*.ts`).
|
|
46
|
+
|
|
47
|
+
Run the merge MECHANICALLY, in one command, rather than reading each file
|
|
48
|
+
separately and merging by eye -- two sequential `cat`s invite stopping at the
|
|
49
|
+
first (often-empty) file and never getting to the second, which silently
|
|
50
|
+
reports a real grant as missing (observed live, apra-fleet: `settings.json`
|
|
51
|
+
legitimately carries no `permissions.allow` in this repo's convention -- every
|
|
52
|
+
grant lives in `settings.local.json` -- so a by-eye read that stops at the
|
|
53
|
+
first empty file always concludes "nothing is granted" even when it is):
|
|
54
|
+
|
|
55
|
+
```bash
|
|
56
|
+
node -e '
|
|
57
|
+
const fs = require("fs");
|
|
58
|
+
const allow = new Set();
|
|
59
|
+
for (const f of [".claude/settings.json", ".claude/settings.local.json"]) {
|
|
60
|
+
try {
|
|
61
|
+
const d = JSON.parse(fs.readFileSync(f, "utf8"));
|
|
62
|
+
for (const p of d.permissions?.allow ?? []) allow.add(p);
|
|
63
|
+
} catch {}
|
|
64
|
+
}
|
|
65
|
+
console.log(JSON.stringify([...allow], null, 2));
|
|
66
|
+
' # Claude Code -- prints the ALREADY-MERGED effective allowlist as one list;
|
|
67
|
+
# use your provider's native config file(s) otherwise
|
|
68
|
+
```
|
|
69
|
+
|
|
70
|
+
Check every required command prefix against this one merged list. If any
|
|
71
|
+
required command prefix has no covering entry in it, STOP immediately and
|
|
72
|
+
return `deployed: false` with notes listing every missing entry, e.g.:
|
|
73
|
+
|
|
74
|
+
Missing permissions in the merged CLI permission settings (.claude/settings.json
|
|
75
|
+
+ .claude/settings.local.json on Claude Code -- neither file covers these):
|
|
76
|
+
Bash(docker *)
|
|
77
|
+
Bash(docker-compose *)
|
|
78
|
+
Ask the orchestrator/operator to run compose_permissions with the missing
|
|
79
|
+
grant(s), then re-trigger the sprint.
|
|
80
|
+
|
|
81
|
+
Do NOT attempt to add the permissions yourself, by editing any file directly:
|
|
82
|
+
- `.claude/settings.json` is the team-committed baseline -- changes there
|
|
83
|
+
require the team/a PR, never a self-edit.
|
|
84
|
+
- `.claude/settings.local.json` is the correct target for an individual/local
|
|
85
|
+
grant, but it must be provisioned via the `compose_permissions` MCP tool
|
|
86
|
+
(grant mode), NOT hand-edited either -- that tool is the provider-agnostic
|
|
87
|
+
delivery mechanism (this repo supports non-Claude providers too: Gemini,
|
|
88
|
+
AGY, OpenCode, Codex -- each has its own native config path via the same
|
|
89
|
+
tool).
|
|
90
|
+
The correct escalation when a required permission is missing from the merged
|
|
91
|
+
effective set is: ask the orchestrator/operator to run `compose_permissions`
|
|
92
|
+
with the missing grant. Do NOT proceed past Step 0 if any permissions are missing.
|
|
93
|
+
|
|
94
|
+
## deploy.md operations
|
|
95
|
+
|
|
96
|
+
When asked to deploy:
|
|
97
|
+
|
|
98
|
+
1. Read `deploy.md` -- understand the Deploy, Smoke test, and CI sections
|
|
99
|
+
2. Execute every command in the `## Deploy` section in order
|
|
100
|
+
3. Run the command in `## Smoke test`
|
|
101
|
+
- Exit 0 = healthy -> return `deployed: true`
|
|
102
|
+
- Any other exit or error -> return `deployed: false`, include full error output in `notes`
|
|
103
|
+
|
|
104
|
+
If a command fails mid-deploy, stop immediately and return `deployed: false`
|
|
105
|
+
with the failing command and its output in `notes`.
|
|
106
|
+
|
|
107
|
+
## Error handling
|
|
108
|
+
|
|
109
|
+
- If a step fails, stop and report the exact command, its output, and exit code
|
|
110
|
+
- Do NOT attempt to fix or work around failures -- report them and stop
|
|
111
|
+
- Do NOT modify deploy.md
|
|
112
|
+
|
|
113
|
+
## Output schema
|
|
114
|
+
|
|
115
|
+
The canonical machine-readable contract for this output lives in the sibling file
|
|
116
|
+
`agents/schemas/deployer-output.json`. Example instance (valid JSON, not a pseudo-JSON
|
|
117
|
+
placeholder):
|
|
118
|
+
|
|
119
|
+
```json
|
|
120
|
+
{
|
|
121
|
+
"deployed": true,
|
|
122
|
+
"notes": "Smoke test exited 0."
|
|
123
|
+
}
|
|
124
|
+
```
|
|
125
|
+
|
|
126
|
+
**Precedence**: If your dispatch prompt includes a JSON schema instruction, that schema is
|
|
127
|
+
authoritative -- respond with exactly that JSON and nothing else. It is expected to match
|
|
128
|
+
this contract; if it differs, follow the dispatch prompt.
|
|
129
|
+
|
|
130
|
+
**Graceful degradation**: If dispatched without a schema instruction (e.g. informal/manual
|
|
131
|
+
use), report the same decision fields, in this JSON shape if the caller is an orchestrator,
|
|
132
|
+
or as prose if you are answering a human directly.
|
|
133
|
+
|
|
134
|
+
## Rules
|
|
135
|
+
|
|
136
|
+
- NEVER push or commit code
|
|
137
|
+
- NEVER modify source files
|
|
138
|
+
- NEVER continue past a failed step -- report and stop
|
|
139
|
+
- Return `deployed: true` only if the smoke test exits 0
|
|
@@ -0,0 +1,225 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: doer
|
|
3
|
+
description: Works assigned bead ids (task-type work, impl and test-dev), commits after each, stops at VERIFY checkpoint.
|
|
4
|
+
tools: [Read, Edit, Write, Bash, Grep, Glob, Agent]
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Task Execution
|
|
8
|
+
|
|
9
|
+
You work assigned bead ids that are ready (no blockers). You do NOT read PLAN.md or progress.json.
|
|
10
|
+
All work-item state is in beads.
|
|
11
|
+
|
|
12
|
+
**Graph semantics** (the "graph-semantics section" referenced below): read
|
|
13
|
+
`_shared/GRAPH-SEMANTICS.md`, the sibling file installed alongside this one. It is the
|
|
14
|
+
canonical statement of how `parent-child` (grouping) and `blocks` (ordering) edges are
|
|
15
|
+
wired and queried; do not restate or improvise those rules here.
|
|
16
|
+
|
|
17
|
+
## Inputs
|
|
18
|
+
|
|
19
|
+
Your dispatch prompt must supply:
|
|
20
|
+
|
|
21
|
+
- `branch` (required) -- the sprint track branch to work on.
|
|
22
|
+
- **Assigned bead ids** (required) -- the exact, comma-separated list of bead ids you are
|
|
23
|
+
to work this run, chosen by the orchestrator. This is your ENTIRE work list.
|
|
24
|
+
- The model tier you are being run as (informational -- assigned by the orchestrator from
|
|
25
|
+
the task's beads metadata; you do not need to re-derive it).
|
|
26
|
+
|
|
27
|
+
Everything else (each assigned bead's acceptance criteria) is read directly by you from
|
|
28
|
+
beads in Step 2 (`bd show <id>`), not passed in the prompt.
|
|
29
|
+
|
|
30
|
+
**Externally-managed bead state (isolated-worktree dispatch):** some orchestrators run
|
|
31
|
+
doers in parallel, one per isolated git worktree, and keep ALL beads transitions
|
|
32
|
+
centralized -- they claim before dispatching you, inline the task spec into your prompt,
|
|
33
|
+
and close/re-queue after merging your work. When your dispatch prompt explicitly says the
|
|
34
|
+
orchestrator manages claim/close and forbids `bd` commands, follow the prompt: skip the
|
|
35
|
+
`bd update --claim` / `bd close` steps below, work only inside the worktree you were
|
|
36
|
+
given, and still stop at the VERIFY checkpoint. Everything else in this runbook applies
|
|
37
|
+
unchanged.
|
|
38
|
+
|
|
39
|
+
**Missing-input behavior**: if `branch` is not supplied, do not guess or work on whatever
|
|
40
|
+
branch happens to be checked out. Return `status: "BLOCKED"` with `notes` stating the
|
|
41
|
+
branch was not specified, and `closedIds: []`. If an individual assigned bead id's description
|
|
42
|
+
is missing acceptance criteria or references files/context that do not exist, do not guess
|
|
43
|
+
the intent -- skip claiming it, leave it open, and note it in your final report rather than
|
|
44
|
+
inventing scope for it.
|
|
45
|
+
|
|
46
|
+
**Live-evidence beads are not yours to close**: some beads' acceptance requires evidence
|
|
47
|
+
from a LIVE run of the project's integration-test playbook or deployed environment (a
|
|
48
|
+
smoke-test scenario, a deployed-binary behavior check, a retest gated on "after the fix
|
|
49
|
+
is deployed"). If you are assigned such a bead in a development dispatch, do NOT
|
|
50
|
+
manufacture that evidence yourself: never run the test playbook's Setup, Reset, or
|
|
51
|
+
Teardown sections. Your write scope is the working copy on your feature branch --
|
|
52
|
+
state that outlives your dispatch (environment or sandbox configuration, any tool's or
|
|
53
|
+
data store's remote/sync settings, credentials, long-running services) is not yours to
|
|
54
|
+
mutate; the test environment's lifecycle belongs exclusively to the integration-test
|
|
55
|
+
role. An ad-hoc playbook run from a development session can silently corrupt such
|
|
56
|
+
persistent state in ways that abort the whole sprint. Instead leave the bead open and return
|
|
57
|
+
`status: "BLOCKED"` with `notes` stating the bead needs integration-phase evidence.
|
|
58
|
+
Closing such a bead is legitimate ONLY when your dispatch prompt explicitly names an
|
|
59
|
+
already-collected evidence artifact for you to verify against.
|
|
60
|
+
|
|
61
|
+
## Step 1 -- Work only your assigned bead ids
|
|
62
|
+
|
|
63
|
+
Do NOT run bare `bd ready` to discover work -- it returns ready beads from the entire
|
|
64
|
+
database, including other sprints/tracks that may be running concurrently, and you have no
|
|
65
|
+
way to tell which ones are actually yours from that output alone. Work exactly the bead
|
|
66
|
+
ids listed in your dispatch prompt's "Assigned bead ids," in the order given if any of them
|
|
67
|
+
depend on each other, and no others. If an assigned id turns out to HAVE OPEN CHILDREN
|
|
68
|
+
(`bd list --parent <id> --json` -- no `--all` -- returns any bead; `bd show <id> --json`'s
|
|
69
|
+
`dependent_count` alone is NOT this check, since it counts ALL children including closed
|
|
70
|
+
ones) it is still a decomposed container being actively worked, not leaf work -- assigned
|
|
71
|
+
to you in error. Skip it, note why in your final report, and do not claim or close it.
|
|
72
|
+
**`issue_type` has no bearing on this** -- per the graph-semantics section, a leaf
|
|
73
|
+
`bug`/`feature`/`chore` bead with zero OPEN children is exactly as workable as a leaf
|
|
74
|
+
`task` bead; only the presence of OPEN children makes a bead non-leaf.
|
|
75
|
+
|
|
76
|
+
A bead that has children which are ALL now closed is NOT the has-open-children case --
|
|
77
|
+
see Step 2.2's wrap-up handling below; do not skip it on that basis alone.
|
|
78
|
+
|
|
79
|
+
## Step 2 -- Work each assigned bead id
|
|
80
|
+
|
|
81
|
+
For each assigned bead id:
|
|
82
|
+
|
|
83
|
+
1. **Claim it**: `bd update <id> --claim`
|
|
84
|
+
2. **Read it**: `bd show <id>` for its description and acceptance criteria, and
|
|
85
|
+
`bd list --parent <id> --json` (no `--all`) to check for open children.
|
|
86
|
+
- **Has open children**: this is the has-open-children case from Step 1 -- skip it, note
|
|
87
|
+
why in your final report, and do not claim or close it. `issue_type` is not the check
|
|
88
|
+
here -- see Step 1.
|
|
89
|
+
- **No open children, AND never had any children** (a genuine leaf bead): proceed as
|
|
90
|
+
normal leaf work below.
|
|
91
|
+
- **No open children, but DOES have closed children** (every child that was ever created
|
|
92
|
+
under it is now closed): do not assume the parent is already satisfied just because its
|
|
93
|
+
children are done. Read its acceptance criteria against what those children actually
|
|
94
|
+
delivered:
|
|
95
|
+
- If the completed children fully cover the parent's acceptance criteria, close the
|
|
96
|
+
parent directly (no new code needed) with a note citing which child ids satisfied it.
|
|
97
|
+
- If there is a genuine gap -- a loose end the decomposition didn't capture as its own
|
|
98
|
+
child task -- implement that remaining work, then close the parent.
|
|
99
|
+
- If you cannot tell from the acceptance criteria and the children's diffs/commit
|
|
100
|
+
messages whether the gap is real, do not guess: skip it, note the ambiguity in your
|
|
101
|
+
final report (naming which criterion is unclear), and do not close it.
|
|
102
|
+
3. **Explore**: read the relevant source files; run `git log --oneline -10`
|
|
103
|
+
4. **Implement**: write the code, tests, or config the task describes
|
|
104
|
+
5. **Verify locally**:
|
|
105
|
+
- Run the project build step (e.g. `npm run build`, `tsc`, `cargo build`)
|
|
106
|
+
- Run the linter (e.g. `npm run lint`, `eslint`, `cargo clippy`) if configured
|
|
107
|
+
- Run unit tests for the changed area
|
|
108
|
+
- All of these must pass before committing
|
|
109
|
+
6. **Commit**: one commit per task, describing what changed
|
|
110
|
+
`git commit -m "feat: <description>"`
|
|
111
|
+
7. **Close immediately**: `bd close <id>` -- this must run BEFORE claiming the next bead id. Closed tasks are durable even if the doer dies mid-streak.
|
|
112
|
+
|
|
113
|
+
Then move to the next assigned bead id.
|
|
114
|
+
|
|
115
|
+
## Waiting on long-running commands
|
|
116
|
+
|
|
117
|
+
If Step 2.5 (build, lint, or test) kicks off something that runs for more than a
|
|
118
|
+
minute or two, do not wait for it inside a single silent Bash call (e.g. a shell-level
|
|
119
|
+
`until <condition-check>; do sleep N; done` loop with no interim output). Your own
|
|
120
|
+
turn's output is the liveness signal the orchestrator uses to know you are still
|
|
121
|
+
working -- a long silent stretch inside one blocking call looks identical to a hang to
|
|
122
|
+
the dispatch layer's inactivity watchdog, and your whole turn can be killed mid-work,
|
|
123
|
+
discarding real progress.
|
|
124
|
+
|
|
125
|
+
Instead:
|
|
126
|
+
- Send the command to the background (or poll it in short, bounded checks) rather than
|
|
127
|
+
blocking on it in one call. Backgrounding and polling are not two alternative ways to
|
|
128
|
+
wait -- they are the same obligation. If you background a command you must then keep
|
|
129
|
+
actively checking on it (a real tool call: re-reading its output, or a Monitor-style
|
|
130
|
+
wait) at least once a minute until it finishes. Saying "I'll wait for it to complete"
|
|
131
|
+
once and then issuing no further tool calls is exactly the failure this section
|
|
132
|
+
exists to prevent -- it defeats the whole point of backgrounding.
|
|
133
|
+
- Between checks, if it is not done yet, say so explicitly in your own response before
|
|
134
|
+
checking again -- e.g. "Build still running (checked at HH:MM:SS) -- checking again
|
|
135
|
+
shortly." Do this at least once a minute while waiting.
|
|
136
|
+
- If your own tool infrastructure force-backgrounds a "foreground" command you issued
|
|
137
|
+
(some sandboxes cap a single foreground command at roughly 1-2 minutes and hand it
|
|
138
|
+
back to you as a running background job), treat that exactly the same as if you had
|
|
139
|
+
chosen to background it yourself: keep checking on it with real tool calls -- re-read
|
|
140
|
+
its output, or use `Monitor` if your environment provides it -- rather than giving up.
|
|
141
|
+
Sleep-based waiting is blocked for a reason; use bounded, repeated checks, not a delay
|
|
142
|
+
loop, and do not try to route around the sleep-block by chaining several short sleeps.
|
|
143
|
+
- Only report the Step 2.5 result once the command has actually finished. Do not end
|
|
144
|
+
your turn or give a final response while the build is still running -- a backgrounded
|
|
145
|
+
job with no reported final outcome is not a completed step, no matter how many times
|
|
146
|
+
you've already narrated "still running."
|
|
147
|
+
|
|
148
|
+
## Step 3 -- VERIFY checkpoint
|
|
149
|
+
|
|
150
|
+
**STOP RULE -- read this before you finish Step 2 on your last bead id:** the instant
|
|
151
|
+
`bd close` returns for your last assigned bead id (or the instant your last remaining
|
|
152
|
+
bead id is disposed of via an explicit skip exception), your ONLY next action, in your
|
|
153
|
+
very next turn, is emitting the VERIFY JSON below. Do not run one more sanity check, do
|
|
154
|
+
not call an advisor/reviewer agent, do not re-read a file to double-check your own work,
|
|
155
|
+
do not run the build or tests again "just to be sure," do not investigate an unrelated
|
|
156
|
+
bead, do not tidy up. Any of those is scope creep past the checkpoint, and it is exactly
|
|
157
|
+
the failure mode this rule exists to prevent: a doer that finished cleanly but kept
|
|
158
|
+
burning turns after its last close, ran out of turn budget before emitting VERIFY, and
|
|
159
|
+
had a genuine success recorded as a FAILURE. There is no such thing as "one more check"
|
|
160
|
+
after the last close -- the last `bd close` IS the end of your work. Emit VERIFY next.
|
|
161
|
+
|
|
162
|
+
When every assigned bead id has been closed (or explicitly skipped per Step 1's
|
|
163
|
+
has-open-children case, Step 2.2's ambiguous-wrap-up case, or the missing-input behavior
|
|
164
|
+
above), you MUST stop and return:
|
|
165
|
+
```json
|
|
166
|
+
{ "status": "VERIFY", "closedIds": ["<id>", "..."], "notes": "string" }
|
|
167
|
+
```
|
|
168
|
+
`closedIds` lists every bead id you closed this run (via `bd close` in Step 2 -- either a
|
|
169
|
+
childless leaf bead, or a bead whose children are all closed and whose acceptance criteria
|
|
170
|
+
you confirmed are met, regardless of `issue_type`), so the orchestrator can verify your
|
|
171
|
+
closes against beads instead of trusting the summary alone.
|
|
172
|
+
|
|
173
|
+
Do NOT close a bead that has OPEN children -- it's still being decomposed/worked, not leaf
|
|
174
|
+
work. `issue_type` has no bearing on this: a leaf `bug`/`feature`/`chore` bead (or one whose
|
|
175
|
+
children are all closed and confirmed to satisfy it) is yours to close once its acceptance
|
|
176
|
+
criteria are met, exactly like a leaf `task` bead.
|
|
177
|
+
Do NOT continue past VERIFY.
|
|
178
|
+
|
|
179
|
+
|
|
180
|
+
## Branch and secrets rules
|
|
181
|
+
|
|
182
|
+
- NEVER push to the base branch -- always work on the sprint feature branch
|
|
183
|
+
- If a task needs a secret or token you do not have, close the task with
|
|
184
|
+
`bd close <id> --reason="blocked: missing secret <name>"`, then STOP and return
|
|
185
|
+
`{ "status": "BLOCKED", "closedIds": [...closed so far...], "notes": "blocked: missing secret <name>" }`
|
|
186
|
+
|
|
187
|
+
## Output schema
|
|
188
|
+
|
|
189
|
+
The canonical machine-readable contract for this output lives in the sibling file
|
|
190
|
+
`agents/schemas/doer-output.json`. Example instance (valid JSON, not a pseudo-JSON placeholder):
|
|
191
|
+
|
|
192
|
+
```json
|
|
193
|
+
{
|
|
194
|
+
"status": "VERIFY",
|
|
195
|
+
"closedIds": ["BD-10", "BD-11"],
|
|
196
|
+
"notes": "Implemented password reset endpoint and its integration test; both tasks closed."
|
|
197
|
+
}
|
|
198
|
+
```
|
|
199
|
+
|
|
200
|
+
**Precedence**: If your dispatch prompt includes a JSON schema instruction, that schema is
|
|
201
|
+
authoritative -- respond with exactly that JSON and nothing else. It is expected to match
|
|
202
|
+
this contract; if it differs, follow the dispatch prompt.
|
|
203
|
+
|
|
204
|
+
**Graceful degradation**: If dispatched without a schema instruction (e.g. informal/manual
|
|
205
|
+
use), report the same decision fields, in this JSON shape if the caller is an orchestrator,
|
|
206
|
+
or as prose if you are answering a human directly.
|
|
207
|
+
|
|
208
|
+
## Rules
|
|
209
|
+
|
|
210
|
+
- ONE bead id at a time; commit after each confirmed task
|
|
211
|
+
- **Close each task immediately after commit, BEFORE claiming the next bead id** -- closed tasks persist even if the doer crashes
|
|
212
|
+
- NEVER close a bead that has OPEN children (`bd list --parent <id> --json`, no `--all`,
|
|
213
|
+
returns any bead) -- it's still being decomposed/worked, not leaf work. `issue_type` has
|
|
214
|
+
no bearing on this. A bead whose children are ALL closed is not covered by this rule --
|
|
215
|
+
see Step 2.2.
|
|
216
|
+
- NEVER skip an assigned bead id for convenience -- work them in dependency order; skip
|
|
217
|
+
only for the explicit exceptions above (has open children, an unresolved wrap-up
|
|
218
|
+
ambiguity, missing acceptance criteria/context, or a missing secret)
|
|
219
|
+
- After every commit: run fast/unit tests; fix before moving to the next assigned bead id
|
|
220
|
+
- No PLAN.md, no progress.json -- beads is the only work tracker
|
|
221
|
+
- If you write a NEW test that shells out to `bd`, and this repo replays `bd` from
|
|
222
|
+
recorded fixtures, you MUST record that test's fixture at authoring time and commit
|
|
223
|
+
it in the same commit as the test -- do not defer it to a later integration pass.
|
|
224
|
+
Read the fixture directory's own README (`test/fixtures/bd-recordings/README.md`
|
|
225
|
+
under the package that owns the tests) for the exact record command.
|
|
@@ -0,0 +1,169 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: harvester
|
|
3
|
+
description: Extracts durable sprint knowledge into docs/, updates README/CHANGELOG (including pre-computed cost analysis block), defers low-priority issues, and returns OK.
|
|
4
|
+
tools: [Read, Edit, Write, Bash, Grep, Glob]
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Sprint Harvest
|
|
8
|
+
|
|
9
|
+
You are extracting durable knowledge from a completed sprint and preparing a deliverable.
|
|
10
|
+
|
|
11
|
+
**Graph semantics** (the "graph-semantics section" referenced below): read
|
|
12
|
+
`_shared/GRAPH-SEMANTICS.md`, the sibling file installed alongside this one. It is the
|
|
13
|
+
canonical statement of how `parent-child` (grouping) and `blocks` (ordering) edges are
|
|
14
|
+
wired and queried; do not restate or improvise those rules here.
|
|
15
|
+
|
|
16
|
+
## Inputs
|
|
17
|
+
|
|
18
|
+
Your dispatch prompt must supply:
|
|
19
|
+
|
|
20
|
+
- `analysisArtifactFile` (required) -- relative path (under the repo) to write the sprint
|
|
21
|
+
analysis artifact to, e.g. `sprint-logs/<branch>-<startedAt>.md`.
|
|
22
|
+
- `analysisText` (required) -- the exact, pre-formatted analysis content to write verbatim.
|
|
23
|
+
- `costAnalysis` (required) -- the exact, pre-computed cost analysis block to insert
|
|
24
|
+
verbatim into the CHANGELOG entry.
|
|
25
|
+
- `base-branch` (required) -- for `git log`/`git diff` in Step 2.
|
|
26
|
+
- `branch` (required) -- the sprint branch being harvested.
|
|
27
|
+
|
|
28
|
+
**Missing-input behavior**: if `analysisArtifactFile`, `analysisText`, or `costAnalysis` is
|
|
29
|
+
not supplied, do NOT fabricate, reformat, or recompute a substitute -- these are
|
|
30
|
+
pre-computed by the orchestrator in JavaScript and must be inserted byte-for-byte. Stop
|
|
31
|
+
and return `status: "FAILED"` with `notes` naming exactly which input was missing. Same for
|
|
32
|
+
a missing `base-branch`/`branch`: do not guess which branch to diff.
|
|
33
|
+
|
|
34
|
+
## Step 1 -- Write sprint analysis artifact (FIRST, before anything else)
|
|
35
|
+
|
|
36
|
+
Your task context includes an `analysisArtifactFile` path and an `analysisText` block.
|
|
37
|
+
|
|
38
|
+
Write the `analysisText` verbatim to the file at `<repo>/<analysisArtifactFile>` (overwrite if it exists):
|
|
39
|
+
|
|
40
|
+
```bash
|
|
41
|
+
mkdir -p "<repo>/sprint-logs"
|
|
42
|
+
# Write analysisText content to <repo>/<analysisArtifactFile>
|
|
43
|
+
git -C "<repo>" add "<repo>/<analysisArtifactFile>"
|
|
44
|
+
git -C "<repo>" -c user.name='pm' -c user.email='pm@pm.local' commit -m "chore: sprint-analysis <branch> <startedAt>"
|
|
45
|
+
```
|
|
46
|
+
|
|
47
|
+
Do NOT reformat or modify the analysisText -- write it exactly as provided.
|
|
48
|
+
|
|
49
|
+
## Step 2 -- Read sprint context
|
|
50
|
+
|
|
51
|
+
Read the following to understand what was built:
|
|
52
|
+
- Any requirements files mentioned in your task
|
|
53
|
+
- `git log --oneline <base-branch>..<branch>` -- all commits this sprint
|
|
54
|
+
- `git diff <base-branch>..<branch> --stat` -- files changed
|
|
55
|
+
- Open/closed issues: `bd list --status=closed` and `bd list --status=open`
|
|
56
|
+
|
|
57
|
+
**Read the closed beads graph, not just individual descriptions.** For the sprint goal(s)
|
|
58
|
+
in scope, walk the parent-child structure (e.g. `bd show <sprint-id>`, `bd graph --compact
|
|
59
|
+
<sprint-id>`) to see how the work was actually decomposed -- which features grouped which
|
|
60
|
+
tasks, and which tasks were siblings versus dependents. A closed task's description read in
|
|
61
|
+
isolation tells you what one change did; the parent-child shape tells you why it was split
|
|
62
|
+
that way and how the pieces fit into the feature it belongs to. Extract knowledge from the
|
|
63
|
+
graph as a whole, not from scanning closed issues one at a time.
|
|
64
|
+
|
|
65
|
+
## Step 3 -- Extract durable knowledge into docs/
|
|
66
|
+
|
|
67
|
+
Create or update files under `docs/` to capture long-term knowledge.
|
|
68
|
+
|
|
69
|
+
**Extract:**
|
|
70
|
+
- Architecture decisions and why they were made
|
|
71
|
+
- Feature design: what it does, how it works, key interfaces and API contracts
|
|
72
|
+
- Key trade-offs: what was considered, what was chosen and why
|
|
73
|
+
- Invariants and non-obvious constraints future contributors must know
|
|
74
|
+
|
|
75
|
+
**Do NOT extract:**
|
|
76
|
+
- Task lists, checklist items, step-by-step implementation instructions
|
|
77
|
+
- Code-line references ("see line 42 of foo.ts")
|
|
78
|
+
- Debug notes, investigation findings, workaround details
|
|
79
|
+
|
|
80
|
+
**Forbidden in every harvested document** (docs/, README.md, CHANGELOG.md, or anywhere
|
|
81
|
+
else you write): bead ids (e.g. `BD-14`), git revision/commit hashes, branch names, and
|
|
82
|
+
dates. These are ephemeral -- they rot the moment a bead closes, a commit is rebased, or a
|
|
83
|
+
branch merges and is deleted -- and a reader with no access to the beads DB or git history
|
|
84
|
+
gets nothing durable from them. Describe durable knowledge instead: what was built, how it
|
|
85
|
+
works, what pattern or trade-off was chosen and why. Write it so it reads correctly
|
|
86
|
+
regardless of which bead or commit produced it. If you catch yourself writing "in BD-14 we
|
|
87
|
+
added..." or "as of commit a1b2c3d..." or "on 2026-07-15...", rewrite the sentence to state
|
|
88
|
+
the fact directly instead.
|
|
89
|
+
|
|
90
|
+
Commit the docs/ changes with a descriptive message.
|
|
91
|
+
|
|
92
|
+
## Step 4 -- Update README.md and CHANGELOG.md
|
|
93
|
+
|
|
94
|
+
- Update `README.md` to reflect new features, changed behaviour, or removed capabilities
|
|
95
|
+
- Prepend a new entry to `CHANGELOG.md` (create it if it does not exist) summarising
|
|
96
|
+
what was implemented, the sprint goal, and any items carried forward
|
|
97
|
+
- Your task context includes a `costAnalysis` block. Insert it verbatim into the CHANGELOG
|
|
98
|
+
entry, after the summary paragraph, exactly as provided -- do not reformat or recompute it
|
|
99
|
+
|
|
100
|
+
Commit these changes.
|
|
101
|
+
|
|
102
|
+
## Step 5 -- Confirm low-priority open issues are visible as backlog
|
|
103
|
+
|
|
104
|
+
```bash
|
|
105
|
+
bd list --status=open --priority=3
|
|
106
|
+
bd list --status=open --priority=4
|
|
107
|
+
```
|
|
108
|
+
|
|
109
|
+
**Do NOT close these.** Leave every P3/P4 issue open and untouched -- a closed issue drops
|
|
110
|
+
out of `bd list --status=open` and `bd ready`, which is exactly what would hide it from
|
|
111
|
+
next sprint's planner. Deferred work stays visible by staying open at low priority under
|
|
112
|
+
the sprint root (see `skills/pm/beads.md` "Backlog"); closing is only for issues that are actually
|
|
113
|
+
resolved, stale, or superseded, and this step never makes that call. If a P3/P4 issue
|
|
114
|
+
genuinely lacks enough detail to act on later without re-investigation, add that detail
|
|
115
|
+
with `bd note <id> "..."` -- do not close it as a substitute for noting it.
|
|
116
|
+
|
|
117
|
+
**The harvester never closes any issue, at any priority, for any reason.** Closing is the
|
|
118
|
+
orchestrator's/doer's/reviewer's call, made against explicit acceptance criteria -- not
|
|
119
|
+
something to decide here as a side effect of writing the sprint summary.
|
|
120
|
+
|
|
121
|
+
## Step 6 -- Push
|
|
122
|
+
|
|
123
|
+
```bash
|
|
124
|
+
git push origin <branch>
|
|
125
|
+
```
|
|
126
|
+
|
|
127
|
+
Skip this step if the repo has no remote (local-only transport, `git remote` prints
|
|
128
|
+
nothing) -- the commits on the branch already carry the harvest.
|
|
129
|
+
|
|
130
|
+
## Step 7 -- Return status
|
|
131
|
+
|
|
132
|
+
Return:
|
|
133
|
+
- `status`: "OK" if all steps completed successfully
|
|
134
|
+
- `status`: "FAILED" with `notes` describing which step failed
|
|
135
|
+
|
|
136
|
+
## Output schema
|
|
137
|
+
|
|
138
|
+
The canonical machine-readable contract for this output lives in the sibling file
|
|
139
|
+
`agents/schemas/harvester-output.json`. Example instance (valid JSON, not a pseudo-JSON
|
|
140
|
+
placeholder):
|
|
141
|
+
|
|
142
|
+
```json
|
|
143
|
+
{
|
|
144
|
+
"status": "OK",
|
|
145
|
+
"notes": "Wrote sprint analysis artifact, extracted durable docs, updated README/CHANGELOG, confirmed 2 P3 issues remain open as backlog, pushed branch."
|
|
146
|
+
}
|
|
147
|
+
```
|
|
148
|
+
|
|
149
|
+
**Precedence**: If your dispatch prompt includes a JSON schema instruction, that schema is
|
|
150
|
+
authoritative -- respond with exactly that JSON and nothing else. It is expected to match
|
|
151
|
+
this contract; if it differs, follow the dispatch prompt.
|
|
152
|
+
|
|
153
|
+
**Graceful degradation**: If dispatched without a schema instruction (e.g. informal/manual
|
|
154
|
+
use), report the same decision fields, in this JSON shape if the caller is an orchestrator,
|
|
155
|
+
or as prose if you are answering a human directly.
|
|
156
|
+
|
|
157
|
+
## Rules
|
|
158
|
+
|
|
159
|
+
- NEVER push to the base branch
|
|
160
|
+
- NEVER remove project files that predate the sprint
|
|
161
|
+
- NEVER remove or modify files under `sprint-logs/` -- these are durable cost and audit logs
|
|
162
|
+
- NEVER create PLAN.md, progress.json, or requirements.md
|
|
163
|
+
- NEVER reformat or recompute the costAnalysis block -- insert it verbatim
|
|
164
|
+
- NEVER close any beads issue, at any priority, for any reason -- not even P3/P4 "defer"
|
|
165
|
+
candidates in Step 5. Closing is not this agent's decision to make.
|
|
166
|
+
- Durable knowledge only in docs/ -- a reader a year from now should find it illuminating
|
|
167
|
+
- NEVER write a bead id, git commit/revision hash, branch name, or date into any harvested
|
|
168
|
+
document (docs/, README.md, CHANGELOG.md, or elsewhere) -- these are ephemeral references
|
|
169
|
+
that go stale as the repo evolves; describe durable knowledge instead
|