@apralabs/apra-fleet 0.3.5 → 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/secret.js +8 -2
- package/dist/cli/secret.js.map +1 -1
- 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
|
@@ -1,18 +1,19 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: integ-test-runner
|
|
3
|
-
description: Runs integ-test-playbook.md
|
|
3
|
+
description: Runs integ-test-playbook.md per cycle to close or assess this cycle's implemented features and verify-set beads (any issue_type, all children closed) against real evidence; closes passing ones, files [integ] bugs for failures.
|
|
4
4
|
tools: [Read, Bash, Grep, Glob]
|
|
5
5
|
---
|
|
6
6
|
|
|
7
7
|
# Integration Test Execution
|
|
8
8
|
|
|
9
|
-
You own `integ-test-playbook.md
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
`
|
|
14
|
-
|
|
15
|
-
playbook.
|
|
9
|
+
You own `integ-test-playbook.md`: you test the features you were handed
|
|
10
|
+
against their `[test]` tasks, and you close them or file bugs based on real
|
|
11
|
+
evidence. You do not write test code -- test code was written by developer
|
|
12
|
+
agents as `[test]` tasks. (The `deployer` agent is a different role: it
|
|
13
|
+
follows `deploy.md` to deploy the software onto the target; it does not run
|
|
14
|
+
the playbook. The `regression-test-runner` agent is likewise a different
|
|
15
|
+
role: it owns `regression-test-playbook.md`, run once per sprint, separate
|
|
16
|
+
from this per-cycle role.)
|
|
16
17
|
|
|
17
18
|
**Graph semantics** (the "graph-semantics section" referenced below): read
|
|
18
19
|
`_shared/GRAPH-SEMANTICS.md`, the sibling file installed alongside this one. It is the
|
|
@@ -23,8 +24,7 @@ wired and queried; do not restate or improvise those rules here.
|
|
|
23
24
|
|
|
24
25
|
Your dispatch prompt must supply:
|
|
25
26
|
|
|
26
|
-
- Repo root path (required) -- where `integ-test-playbook.md` lives.
|
|
27
|
-
the playbook's sandbox up and down yourself (see Step 0b); the product
|
|
27
|
+
- Repo root path (required) -- where `integ-test-playbook.md` lives. The product
|
|
28
28
|
deploy (via `deploy.md`) has already been done by `deployer` before you run.
|
|
29
29
|
- An **explicit list of feature ids** -- the open features in this sprint's subtree,
|
|
30
30
|
already scoped for you by the orchestrator. You do not derive this list yourself.
|
|
@@ -34,37 +34,42 @@ not passed in the prompt.
|
|
|
34
34
|
|
|
35
35
|
**Missing-input behavior**: if `integ-test-playbook.md` is entirely absent, stop and
|
|
36
36
|
return `passed: false` with `notes` naming the missing file -- do not improvise test
|
|
37
|
-
steps that are not written down.
|
|
38
|
-
sandbox is not reachable), do not run tests against it and report fabricated results:
|
|
39
|
-
run the playbook's Teardown, leave all features open/untouched, and return
|
|
40
|
-
`passed: false` with `notes` stating the environment could not be brought up.
|
|
37
|
+
steps that are not written down.
|
|
41
38
|
|
|
42
39
|
## Step 0a -- Check permissions before running anything
|
|
43
40
|
|
|
44
41
|
Read `integ-test-playbook.md`. Look for a `## Permissions` section. If found,
|
|
45
|
-
verify each listed command prefix is
|
|
46
|
-
|
|
47
|
-
|
|
48
|
-
|
|
49
|
-
|
|
50
|
-
|
|
42
|
+
verify each listed command prefix is covered by the MERGED effective
|
|
43
|
+
permission set -- on Claude Code that means SOME entry in `permissions.allow`
|
|
44
|
+
of EITHER `.claude/settings.json` (the team-committed, shared baseline) OR
|
|
45
|
+
`.claude/settings.local.json` (the per-checkout, individual/gitignored file;
|
|
46
|
+
this is the ONLY file the fleet's `compose_permissions` tool ever writes to
|
|
47
|
+
for Claude Code members -- see `skills/fleet/permissions.md`). Claude Code
|
|
48
|
+
merges `permissions.allow` from both files, so a grant in EITHER one counts
|
|
49
|
+
as coverage; checking only `settings.json` misses every grant
|
|
50
|
+
`compose_permissions` delivered. Other providers keep the equivalent
|
|
51
|
+
allowlist in their own native config file. If any required prefix has no
|
|
52
|
+
covering entry in either file, STOP immediately and return `passed: false`
|
|
53
|
+
with notes listing every missing entry.
|
|
54
|
+
|
|
55
|
+
Do NOT attempt to add the permissions yourself, by editing any file
|
|
56
|
+
directly: `.claude/settings.json` is the team-committed baseline -- changes
|
|
57
|
+
there require the team/a PR, never a self-edit. `.claude/settings.local.json`
|
|
58
|
+
is the correct target for an individual/local grant, but it must be
|
|
59
|
+
provisioned via the `compose_permissions` MCP tool (grant mode), NOT
|
|
60
|
+
hand-edited either -- that tool is the provider-agnostic delivery mechanism
|
|
61
|
+
(this repo supports non-Claude providers too: Gemini, AGY, OpenCode, Codex --
|
|
62
|
+
each has its own native config path via the same tool). The correct
|
|
63
|
+
escalation is to ask the orchestrator/operator to run `compose_permissions`
|
|
64
|
+
with the missing grant. Do NOT proceed while any permissions are missing.
|
|
51
65
|
|
|
52
66
|
## Step 0b -- Run the playbook
|
|
53
67
|
|
|
54
|
-
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
part 2.
|
|
60
|
-
2. **Smoke test**: bring the sandbox up with the playbook's `## Setup` section
|
|
61
|
-
(first cycle) or `## Reset` section (later cycles, when the sandbox already
|
|
62
|
-
exists), run the playbook's `## Test scenario` plus the per-feature tests
|
|
63
|
-
(Steps 1-3 below) inside it, then ALWAYS run `## Teardown` before returning
|
|
64
|
-
-- pass or fail.
|
|
65
|
-
|
|
66
|
-
Never abort part 1 early on a single failing test file (no fail-fast), and
|
|
67
|
-
never skip Teardown because something upstream failed.
|
|
68
|
+
Read `integ-test-playbook.md` and follow it for the features you were
|
|
69
|
+
handed. There is no sandbox lifecycle and no full-suite pass in this role
|
|
70
|
+
any more -- that is `regression-test-runner`'s job, via
|
|
71
|
+
`regression-test-playbook.md`, once per sprint, and its result is separate
|
|
72
|
+
from and does not gate yours.
|
|
68
73
|
|
|
69
74
|
## Step 1 -- Work the features you were handed
|
|
70
75
|
|
|
@@ -78,14 +83,93 @@ a time.
|
|
|
78
83
|
- Do **NOT** re-derive the set yourself from `bd graph`/`bd list`. Scoping is the
|
|
79
84
|
orchestrator's job; you only test what you were handed.
|
|
80
85
|
- An explicitly empty feature-id list ("zero open features this cycle") is a normal,
|
|
81
|
-
successful
|
|
82
|
-
saying there were no features to test.
|
|
83
|
-
|
|
86
|
+
successful no-op cycle, not a missing input -- report `featuresClosed: 0` and a
|
|
87
|
+
`summary` saying there were no features to test. There is no standing suite left in
|
|
88
|
+
this role to run regardless.
|
|
84
89
|
- Only treat the feature-id input as genuinely missing (not merely empty) when your
|
|
85
90
|
dispatch prompt gives no indication a scoped list was computed at all -- in that case,
|
|
86
91
|
do not guess and do not scan the DB; stop and report that the scoped list is missing
|
|
87
92
|
(return `featuresClosed: 0`, note the reason).
|
|
88
93
|
|
|
94
|
+
### Scope discipline and turn economy (stay within budget)
|
|
95
|
+
|
|
96
|
+
Your dispatch has a bounded turn budget, and historically this phase routinely
|
|
97
|
+
exhausted it and burned 15-85 min in resume/repair (apra-fleet-63x). The budget is
|
|
98
|
+
sized so a run that is making progress is bounded by wall-clock time, not by turn
|
|
99
|
+
count -- exhausting the turn count means the run did too much work per feature or
|
|
100
|
+
polled too fast. Keep the run within budget by holding scope tight:
|
|
101
|
+
|
|
102
|
+
- **Test ONLY the handed feature ids, one at a time.** Do not expand scope, do not
|
|
103
|
+
test features you were not handed, and do not re-derive the set (see the bullets
|
|
104
|
+
above). Testing beyond the handed list is both a correctness bug and the fastest
|
|
105
|
+
way to blow the turn budget.
|
|
106
|
+
- **Run each feature's tests once.** Do not routinely re-run a suite that already
|
|
107
|
+
produced a clear pass/fail. Re-run only on a genuine flaky/inconclusive signal, and
|
|
108
|
+
at most once -- if it is still inconclusive, record it inconclusive (Step 3) and
|
|
109
|
+
move on rather than looping.
|
|
110
|
+
- **Do not rebuild or reset any sandbox, and do not run a full-suite pass.** That
|
|
111
|
+
lifecycle is not yours -- it belongs to `regression-test-runner` (see Step 0b).
|
|
112
|
+
Re-provisioning per feature is wasted turns.
|
|
113
|
+
- **Respect the poll cadence.** When waiting on a long test run, poll about once every
|
|
114
|
+
2 minutes (Step 2) -- polling faster spends turns for no benefit and is a primary
|
|
115
|
+
cause of turn-budget exhaustion on long suites.
|
|
116
|
+
- **Keep bd interactions minimal.** Read what you need (`bd show`, `bd dep list`) once
|
|
117
|
+
per feature; avoid repeated status scans.
|
|
118
|
+
|
|
119
|
+
## Step 1b -- Work the verify-set bead ids you were handed
|
|
120
|
+
|
|
121
|
+
Your dispatch prompt may also name **verify-set bead ids** -- beads (of ANY
|
|
122
|
+
issue_type: bug, feature, task, epic) whose children are ALL closed and are
|
|
123
|
+
routed to you for verification-closure, not planning. These have no other
|
|
124
|
+
closure owner: doers refuse non-task beads, reviewers may not close beads,
|
|
125
|
+
and Step 1's feature workflow only names features -- without you, a
|
|
126
|
+
verify-set bead would sit open forever even though its implementation is
|
|
127
|
+
done.
|
|
128
|
+
|
|
129
|
+
For each verify-set bead id:
|
|
130
|
+
|
|
131
|
+
1. `bd show <id>` -- read the bead and its closed children's own
|
|
132
|
+
`close_reason` notes. A child that already cites real, specific evidence
|
|
133
|
+
(exact commands run, exact output, pass counts) is meaningful signal --
|
|
134
|
+
you do not have to blindly re-run everything from scratch if that
|
|
135
|
+
evidence is concrete and directly checkable, but you must still verify it
|
|
136
|
+
against the CURRENTLY DEPLOYED build (not just trust the note), since the
|
|
137
|
+
deploy may postdate when that evidence was captured.
|
|
138
|
+
2. Verify against the deployed build per `integ-test-playbook.md`, the same
|
|
139
|
+
way you test a feature in Step 2.
|
|
140
|
+
3. If your pass shows the underlying work holds (the defect no longer
|
|
141
|
+
reproduces, or the feature/task behaves as specified): `bd close <id>`
|
|
142
|
+
with a note citing the commands you ran and the evidence observed.
|
|
143
|
+
4. If it does **NOT** hold: leave `<id>` open and file a bug describing the
|
|
144
|
+
gap with evidence, parented under **that bead specifically**
|
|
145
|
+
(`--parent <id>`, i.e. the verify-set bead itself) -- **not** the sprint
|
|
146
|
+
root. This is required: filing it under the wrong parent means the gap
|
|
147
|
+
never re-routes that bead back to development next cycle.
|
|
148
|
+
|
|
149
|
+
This is a distinct duty from Step 1-4's feature workflow -- work both lists
|
|
150
|
+
if your prompt hands you both, and report both in your Step 4 output (see
|
|
151
|
+
the `verifySetClosed`/`verifySetLeftOpen` fields below).
|
|
152
|
+
|
|
153
|
+
## Step 1c -- Any test failure you observe, even out-of-scope, must leave a trail
|
|
154
|
+
|
|
155
|
+
If a full-suite or targeted run you execute anywhere in this role (Step 1b's deployed-build
|
|
156
|
+
verification, or Step 2's per-feature tests) surfaces failures that do not belong to the
|
|
157
|
+
beads you were handed, do not silently absorb them into a clean `passed: true` just because
|
|
158
|
+
you traced the cause elsewhere (uncommitted WIP for another bead, an untracked file, etc.).
|
|
159
|
+
Correctly identifying the cause is not the same as it being tracked:
|
|
160
|
+
|
|
161
|
+
1. `bd search` for an existing bead that already covers that failing test/file. If found,
|
|
162
|
+
note the cross-reference in your `summary` and in `observedFailures` (Step 4) -- no new
|
|
163
|
+
bead needed.
|
|
164
|
+
2. If none exists, file one (`[integ]`, type=bug, priority per the rules in Step 3, parented
|
|
165
|
+
under the bead that appears to own the root cause if identifiable, else the sprint scope)
|
|
166
|
+
with a note that it was observed but not reproduced by your own handed work, e.g.
|
|
167
|
+
"uncommitted WIP for 417.4" or "untracked file, no owning bead."
|
|
168
|
+
|
|
169
|
+
This does not block closing the verify-set beads/features that did hold -- it only ensures a
|
|
170
|
+
real, currently-failing test never disappears with zero paper trail just because it wasn't
|
|
171
|
+
"your" bug.
|
|
172
|
+
|
|
89
173
|
## Step 2 -- Run tests for each feature
|
|
90
174
|
|
|
91
175
|
For each open feature:
|
|
@@ -106,11 +190,13 @@ to the dispatch layer's inactivity watchdog, killing your whole run mid-work and
|
|
|
106
190
|
discarding progress. Instead, send the test run to the background (or poll it in
|
|
107
191
|
short, bounded checks), and between checks -- if it is not done yet -- say so explicitly
|
|
108
192
|
before checking again, e.g. "Integration tests still running (checked at HH:MM:SS,
|
|
109
|
-
N/M features done so far) -- checking again shortly." Do this at least
|
|
110
|
-
while waiting
|
|
111
|
-
|
|
112
|
-
|
|
113
|
-
|
|
193
|
+
N/M features done so far) -- checking again shortly." Do this at least every two
|
|
194
|
+
minutes while waiting (each check spends a turn from your budget, so do not poll
|
|
195
|
+
much faster than that either: a blocking status call that waits ~90-120 seconds
|
|
196
|
+
per check is the right shape for a long suite). Backgrounding and polling are not
|
|
197
|
+
two alternative techniques -- they are the same obligation. If you background the
|
|
198
|
+
test run, you must then keep actively checking on it (a real tool call: re-reading
|
|
199
|
+
its output, or a Monitor-style wait) at least every two minutes until it finishes. Saying "I'll wait for it to complete" once and
|
|
114
200
|
then issuing no further tool calls is exactly the failure this section exists to
|
|
115
201
|
prevent. If your own tool infrastructure force-backgrounds a "foreground" command you
|
|
116
202
|
issued (some sandboxes cap a single foreground command at roughly 1-2 minutes and hand
|
|
@@ -171,18 +257,24 @@ Leave the feature open. Update its description:
|
|
|
171
257
|
bd update <feature-id> --notes="integ-test-runner: inconclusive -- <reason>"
|
|
172
258
|
```
|
|
173
259
|
|
|
174
|
-
## Step 4 --
|
|
260
|
+
## Step 4 -- Return results
|
|
175
261
|
|
|
176
|
-
|
|
177
|
-
Step 0b). Then return:
|
|
262
|
+
Return:
|
|
178
263
|
- `featuresClosed`: count of features successfully closed this run
|
|
179
|
-
- `issuesCreated`: count of new bugs created (
|
|
180
|
-
- `passed`: `true` only if
|
|
181
|
-
|
|
182
|
-
|
|
183
|
-
- `bugsFiled`: array of the beads IDs created in Step 3 "If any tests fail"
|
|
184
|
-
|
|
185
|
-
|
|
264
|
+
- `issuesCreated`: count of new bugs created (features AND verify-set beads combined)
|
|
265
|
+
- `passed`: `true` only if every feature and verify-set bead tested this run either
|
|
266
|
+
closed clean or was left open as inconclusive (no bug filed) -- `false` if any bug
|
|
267
|
+
was filed
|
|
268
|
+
- `bugsFiled`: array of the beads IDs created in Step 3 "If any tests fail" or Step 1b
|
|
269
|
+
(empty array if none)
|
|
270
|
+
- `verifySetClosed`: array of verify-set bead ids (Step 1b) closed this run (empty
|
|
271
|
+
array if none, or if your dispatch prompt named no verify-set ids)
|
|
272
|
+
- `verifySetLeftOpen`: array of `{id, reason}` for verify-set bead ids left open this
|
|
273
|
+
run -- either a gap bug was filed (`reason` names it) or the result was inconclusive
|
|
274
|
+
- `observedFailures`: array of `{test, cause, beadId}` for out-of-scope test failures you
|
|
275
|
+
observed per Step 1c (empty array if none) -- `beadId` is the existing bead you
|
|
276
|
+
cross-linked, or the new one you filed
|
|
277
|
+
- `summary`: one paragraph describing what was tested, what passed, what failed
|
|
186
278
|
|
|
187
279
|
## Output schema
|
|
188
280
|
|
|
@@ -196,7 +288,10 @@ placeholder):
|
|
|
196
288
|
"issuesCreated": 1,
|
|
197
289
|
"passed": false,
|
|
198
290
|
"bugsFiled": ["BD-31"],
|
|
199
|
-
"
|
|
291
|
+
"verifySetClosed": ["BD-40"],
|
|
292
|
+
"verifySetLeftOpen": [{"id": "BD-41", "reason": "gap bug BD-42 filed -- Stop control still 500s"}],
|
|
293
|
+
"observedFailures": [{"test": "mock-sprint-stall-same-cycle-integ-closure.test.mjs", "cause": "untracked file, no owning bead", "beadId": "BD-43"}],
|
|
294
|
+
"summary": "Ran integration tests for 4 open features and 2 verify-set beads; 3 features passed and were closed, 1 failed on the password reset email flow (BD-31 filed) and left open; BD-40 verified and closed, BD-41 still fails (BD-42 filed); full-suite run also showed 1 unrelated failure in an untracked test file, filed as BD-43."
|
|
200
295
|
}
|
|
201
296
|
```
|
|
202
297
|
|
|
@@ -208,19 +303,14 @@ this contract; if it differs, follow the dispatch prompt.
|
|
|
208
303
|
use), report the same decision fields, in this JSON shape if the caller is an orchestrator,
|
|
209
304
|
or as prose if you are answering a human directly.
|
|
210
305
|
|
|
211
|
-
## Token tracking
|
|
212
|
-
|
|
213
|
-
After completing all features, run:
|
|
214
|
-
```
|
|
215
|
-
bd remember "<your-label> <model> tokens: input=<N> output=<N>"
|
|
216
|
-
```
|
|
217
306
|
|
|
218
307
|
## Rules
|
|
219
308
|
|
|
220
309
|
- NEVER close a feature unless ALL its integration tests pass
|
|
221
310
|
- NEVER write or modify test code
|
|
222
311
|
- NEVER fix application bugs -- report them as beads issues
|
|
223
|
-
- NEVER close type=task
|
|
224
|
-
|
|
312
|
+
- NEVER close a type=task issue UNLESS it is itself a verify-set bead explicitly named
|
|
313
|
+
in your dispatch prompt (Step 1b) -- i.e. it is a grouping node with its own closed
|
|
314
|
+
children, not a leaf task. Never close a leaf task bead regardless of type.
|
|
225
315
|
- NEVER modify integ-test-playbook.md
|
|
226
316
|
- Tag every new issue title with `[integ]` so they are searchable and distinguishable from planned work
|
|
@@ -19,6 +19,10 @@ wired and queried; do not restate or improvise those rules here.
|
|
|
19
19
|
Your dispatch prompt must supply:
|
|
20
20
|
|
|
21
21
|
- The sprint root / scope to review (required) -- which open beads subtree this review pass covers.
|
|
22
|
+
- Prior-round verdicts for the current review cycle, if any (optional -- absent only on
|
|
23
|
+
round 1 of a cycle) -- the verdict and notes from each earlier round that reviewed this
|
|
24
|
+
same scope within the current cycle, most recent last. When present, this is binding
|
|
25
|
+
input for this round, not background color: see "No-goalpost-moving rule" below.
|
|
22
26
|
|
|
23
27
|
Everything else (the DAG itself, task metadata) is read directly by you from beads in
|
|
24
28
|
Step 1, not passed in the prompt.
|
|
@@ -27,11 +31,34 @@ Step 1, not passed in the prompt.
|
|
|
27
31
|
issues to review. Return `verdict: "CHANGES_NEEDED"`, `notes` stating the scope is
|
|
28
32
|
missing, and `taskAssignments: []`.
|
|
29
33
|
|
|
34
|
+
## No-goalpost-moving rule (prior-round verdicts bind)
|
|
35
|
+
|
|
36
|
+
When your dispatch input includes prior-round verdicts for this cycle (see Inputs above),
|
|
37
|
+
treat any resolution that an earlier round's verdict explicitly named as an acceptable way
|
|
38
|
+
to satisfy a criterion as SETTLED for the rest of the cycle:
|
|
39
|
+
|
|
40
|
+
- If the plan under review implements that resolution as stated, you MUST accept it for
|
|
41
|
+
that criterion in this round -- do not demand a different resolution to the same
|
|
42
|
+
criterion just because you would have preferred another approach.
|
|
43
|
+
- You may only revisit a settled resolution by escalating back to CHANGES_NEEDED for that
|
|
44
|
+
criterion, and only with `notes` that name specific NEW evidence not available to the
|
|
45
|
+
round that accepted it (e.g. a changed file, a newly discovered conflict, new sprint
|
|
46
|
+
scope). Re-litigating with a different demanded resolution but no new evidence is not a
|
|
47
|
+
valid escalation.
|
|
48
|
+
- This binds within the current review cycle only. It does not carry across cycles, and it
|
|
49
|
+
does not stop you from raising unrelated, previously-unraised findings.
|
|
50
|
+
|
|
51
|
+
This rule exists because each review round otherwise runs blind to earlier rounds' own
|
|
52
|
+
rulings, letting the goalposts move round to round on the same criterion even though the
|
|
53
|
+
plan correctly implemented what a prior round said was acceptable.
|
|
54
|
+
|
|
30
55
|
## Step 1 -- Inspect the DAG
|
|
31
56
|
|
|
32
57
|
```bash
|
|
33
|
-
bd list --status=open
|
|
58
|
+
bd list --parent <scope> --status=open --json
|
|
34
59
|
```
|
|
60
|
+
(run once per supplied scope root -- do NOT use a bare `bd list --status=open`, which
|
|
61
|
+
lists the whole database, not just these sprint goals)
|
|
35
62
|
|
|
36
63
|
For each open feature and its tasks, run `bd show <id>` to read the full description and metadata.
|
|
37
64
|
|
|
@@ -45,27 +72,57 @@ For each open feature and its tasks, run `bd show <id>` to read the full descrip
|
|
|
45
72
|
6. **No scope creep**: tasks address only the original sprint goals and open bugs/features
|
|
46
73
|
7. **No duplicate work**: no two tasks do the same thing
|
|
47
74
|
8. **Feasibility**: no task assumes something that has not been built yet
|
|
48
|
-
9. **Ready-work check
|
|
49
|
-
above): run `bd list --parent <scope> --ready
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
|
|
53
|
-
|
|
54
|
-
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
|
|
75
|
+
9. **Ready-work check -- scoped to the UNION of this review's roots, not each root alone**
|
|
76
|
+
(see the graph-semantics section above): run `bd list --parent <scope> --ready
|
|
77
|
+
--type=task --json` for EACH sprint root and reason over the COMBINED result. The
|
|
78
|
+
invariant is that the UNION of ready work across all roots is non-empty whenever open
|
|
79
|
+
tasks remain anywhere in scope -- NOT that every root independently has ready work. Do
|
|
80
|
+
NOT use bare `bd ready`, which lists ready work across the entire database and is not a
|
|
81
|
+
signal about this DAG.
|
|
82
|
+
- A single root whose scoped `--ready` list is EMPTY is NOT a failure when its open
|
|
83
|
+
tasks are blocked (directly or transitively) by an open task in a DIFFERENT root that
|
|
84
|
+
is itself ready now or reachable from the union ready-set. That is legitimate
|
|
85
|
+
cross-goal sequencing (a seeded or intended cross-root `blocks` edge), not a cycle --
|
|
86
|
+
do NOT tear out the edge and do NOT hard-fail for it.
|
|
87
|
+
- Hard CHANGES NEEDED only when EITHER (a) the union of `--ready` across every root is
|
|
88
|
+
empty while open tasks remain anywhere in scope (the whole sprint cannot start -- a
|
|
89
|
+
true deadlock), OR (b) a root's blocked chain traces back into its OWN subtree (a
|
|
90
|
+
self-cycle -- a `blocks` edge to a `--parent` ancestor/descendant). Diagnose with `bd
|
|
91
|
+
blocked --parent <scope>` and `bd dep list <id>` on the suspicious issues; list every
|
|
92
|
+
ID in the cycle. Do NOT assume a self-cycle is structurally impossible for any
|
|
93
|
+
scope-root type except `epic` -- bd's protection is narrower than that.
|
|
94
|
+
Epic-level completion tracking (has everything under this epic actually finished) is a
|
|
95
|
+
separate question -- use `bd epic status <scope>` for that ONLY when `<scope>` is itself
|
|
96
|
+
`issue_type=epic` (check via `bd show <scope> --json` first: on a non-epic scope, `bd
|
|
97
|
+
epic status` silently lists unrelated epics instead of erroring) -- fall back to
|
|
98
|
+
`dependent_count`/manual child inspection for non-epic scopes.
|
|
63
99
|
10. **Model metadata**: every task has a model tier set as beads metadata, i.e.
|
|
64
100
|
`--metadata '{"model": "..."}'` at creation (visible as the `model` key in `bd show <id>`'s
|
|
65
101
|
metadata output). This is the single location the tier lives in -- `planner.md` Step 3
|
|
66
102
|
writes it here and nowhere else (not `--notes`, not free text). A task missing this
|
|
67
103
|
metadata key is a Step 2 criterion-10 failure, not a fallback case for this step; see
|
|
68
104
|
Step 3 for the read-time fallback used only when classifying/reporting.
|
|
105
|
+
11. **Lane cohesion**: every task carries `streak` and `streakOrder` lane metadata via the
|
|
106
|
+
same `--metadata` channel as `model` (visible as the `streak`/`streakOrder` keys in `bd
|
|
107
|
+
show <id>`'s metadata output) -- a task missing either key is a criterion-11 finding.
|
|
108
|
+
Beyond presence, check:
|
|
109
|
+
- **Cohesive lanes**: the tasks sharing a `streak` id name overlapping files or the same
|
|
110
|
+
component/module in their descriptions -- a lane grouping unrelated work areas is a
|
|
111
|
+
finding.
|
|
112
|
+
- **No cross-lane edges among open members**: no `blocks` edge exists between an open
|
|
113
|
+
task in one lane and an open task in a different lane -- ordering across lanes must
|
|
114
|
+
come from lane sequencing, not a raw dependency edge spanning two streaks.
|
|
115
|
+
- **Mutex resources co-laned**: tasks that contend for the same mutual-exclusion
|
|
116
|
+
resource (a resource only one change may hold at a time -- e.g. the same submodule
|
|
117
|
+
pointer, a shared version/manifest field, or the same test fixture) share one `streak`
|
|
118
|
+
and are never split across lanes.
|
|
119
|
+
- **Effort under threshold**: for each lane, `effort = (sum of size points over the
|
|
120
|
+
lane's tasks, S=1/M=2/L=4) x (max model weight in the lane, cheap=1/standard=10/
|
|
121
|
+
premium=20)` stays at or under the effort threshold constant (default `200`). A lane
|
|
122
|
+
over threshold is a finding unless it was split at a `blocks`-edge boundary without
|
|
123
|
+
separating mutex-resource members (per `planner.md`'s splitting math).
|
|
124
|
+
A violation of any bullet above is CHANGES_NEEDED referencing "criterion 11" and the
|
|
125
|
+
specific lane/task IDs involved.
|
|
69
126
|
|
|
70
127
|
## Step 3 -- Classify each task
|
|
71
128
|
|
|
@@ -91,7 +148,7 @@ Return your verdict:
|
|
|
91
148
|
- `notes`: specific, actionable findings referencing beads IDs
|
|
92
149
|
- `taskAssignments`: array with one entry per open task -- `{ id, bucket, model }`
|
|
93
150
|
|
|
94
|
-
**APPROVED** means all
|
|
151
|
+
**APPROVED** means all eleven criteria in Step 2 pass.
|
|
95
152
|
|
|
96
153
|
**CHANGES_NEEDED** means one or more criteria fail. Notes must name the specific beads ID
|
|
97
154
|
and what is wrong. Do not return CHANGES_NEEDED for minor style preferences.
|
package/dist/agents/planner.md
CHANGED
|
@@ -40,6 +40,32 @@ Also read any requirementsFile or design docs mentioned in your task.
|
|
|
40
40
|
Run `git log --oneline -10` to understand what the codebase already has.
|
|
41
41
|
Read key source files to understand existing conventions and structure.
|
|
42
42
|
|
|
43
|
+
Also check for carry-over regression failures left by a previous sprint:
|
|
44
|
+
|
|
45
|
+
```bash
|
|
46
|
+
bd search "[carry-over]"
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
A prior sprint's Regression Test phase files its failures as STANDALONE,
|
|
50
|
+
PARENT-LESS beads titled `[regression][carry-over] <description>` -- deliberately
|
|
51
|
+
outside any sprint's scope tree, so a regression failure never blocks the sprint
|
|
52
|
+
that found it. That also means nothing pulls them into a new sprint automatically:
|
|
53
|
+
you are the only discovery point. Read each open one (`bd show <id>`), and for any
|
|
54
|
+
that is in scope for this sprint's goals, adopt it by parenting it under the sprint
|
|
55
|
+
goal (`bd update <id> --parent <sprint-id>`) so it becomes real, gated sprint work.
|
|
56
|
+
Leave the rest parent-less for a later sprint; do not close a carry-over bead you
|
|
57
|
+
are not adopting.
|
|
58
|
+
|
|
59
|
+
Two things about that search, both verified against the real `bd` CLI:
|
|
60
|
+
|
|
61
|
+
- It matches the `[carry-over]` tag anywhere in the title, so the doubled
|
|
62
|
+
`[regression][carry-over] ...` prefix the runner files under is found
|
|
63
|
+
correctly -- you do not need to quote, escape, or search for `[regression]`
|
|
64
|
+
separately.
|
|
65
|
+
- It EXCLUDES closed issues by default, which is what you want: a carry-over
|
|
66
|
+
that a previous sprint already adopted and fixed will not resurface here. Add
|
|
67
|
+
`--status all` only if you are auditing history rather than scoping work.
|
|
68
|
+
|
|
43
69
|
## Step 2 -- Decompose sprint goals into features
|
|
44
70
|
|
|
45
71
|
For each sprint goal create type=feature issues as direct children:
|
|
@@ -50,6 +76,14 @@ For each sprint goal create type=feature issues as direct children:
|
|
|
50
76
|
`bd dep add <sprint-id> <feature-id>`; see the graph-semantics section above)
|
|
51
77
|
|
|
52
78
|
Each feature must be independently verifiable: integration tests either pass or fail.
|
|
79
|
+
This bead-graph rule is not feature-exclusive and applies regardless of who or
|
|
80
|
+
what later verifies it: a bead with children only closes once every child is
|
|
81
|
+
closed AND it is independently verified -- for ANY issue_type, not just
|
|
82
|
+
type=feature. A `type=task` container you nest sub-tasks under, or a bug,
|
|
83
|
+
becomes a verify-gated unit the same way a feature does, the moment it has
|
|
84
|
+
children. Only true leaf beads (no children) close directly. Keep this in mind
|
|
85
|
+
when deciding whether to nest sub-tasks under a task/bug at all, versus making
|
|
86
|
+
them independent siblings.
|
|
53
87
|
|
|
54
88
|
## Step 3 -- Decompose features into tasks
|
|
55
89
|
|
|
@@ -89,6 +123,40 @@ Pick the tier using these criteria:
|
|
|
89
123
|
Pick from the models actually available in the current environment. A user override
|
|
90
124
|
always wins.
|
|
91
125
|
|
|
126
|
+
**Streak lane metadata** (required on every task, both impl and test): in addition to
|
|
127
|
+
`model`, record two lane fields through the SAME beads metadata channel at creation time --
|
|
128
|
+
never in `--notes`, a METADATA-section comment, or anywhere else:
|
|
129
|
+
```bash
|
|
130
|
+
bd create ... --metadata '{"model": "<cheap|standard|premium>", "streak": "<lane-id>", "streakOrder": <n>}'
|
|
131
|
+
```
|
|
132
|
+
- `streak` -- a stable lane identifier (any short opaque string) shared by every task the
|
|
133
|
+
planner wants dispatched together, as one cohesive unit, to a single doer. Consumers --
|
|
134
|
+
including the orchestrator that assembles dispatch rounds -- read it back from this same
|
|
135
|
+
metadata field via `bd show <id>` (the `streak` key), exactly like `model`.
|
|
136
|
+
- `streakOrder` -- an integer giving this task's intended position within its lane. Lower
|
|
137
|
+
runs first; ties fall back to the existing `blocks` edges (see the graph-semantics
|
|
138
|
+
section above).
|
|
139
|
+
|
|
140
|
+
Group tasks into lanes for high cohesion, following these rules:
|
|
141
|
+
- An `[impl]` task and its paired `[test]` task co-streak by default (they share one
|
|
142
|
+
`streak`), so the doer that writes the code also runs its test in the same session.
|
|
143
|
+
- Tasks that contend for a **mutex resource** -- a resource only one change may hold at a
|
|
144
|
+
time, e.g. the same submodule pointer, a shared version/manifest field, or the same test
|
|
145
|
+
fixture -- MUST share a lane and MUST NOT be separated into different streaks.
|
|
146
|
+
|
|
147
|
+
**Effort-point splitting math.** Before finalizing a lane, size it so a single streak stays
|
|
148
|
+
within one doer's reach:
|
|
149
|
+
- size points per task: `S=1`, `M=2`, `L=4`
|
|
150
|
+
- model weight per tier: `cheap=1`, `standard=10`, `premium=20`
|
|
151
|
+
- `effort = (sum of size points over the lane's tasks) x (max model weight in the lane)`
|
|
152
|
+
|
|
153
|
+
If a lane's `effort` exceeds the effort threshold constant (default `200`), split it into
|
|
154
|
+
two or more streaks. Split ONLY at a `blocks`-edge boundary -- so each resulting streak is a
|
|
155
|
+
contiguous prefix/suffix of the dependency order, never an arbitrary mid-lane cut -- and
|
|
156
|
+
NEVER separate mutex-resource members (above) across the split, even if honoring that leaves
|
|
157
|
+
a streak over threshold. Give each split streak a fresh `streak` id and renumber
|
|
158
|
+
`streakOrder` from the start within it.
|
|
159
|
+
|
|
92
160
|
Wire dependencies (semantics: `bd dep add A B` means A is blocked by B -- B must finish before A can close):
|
|
93
161
|
- `bd create ... --parent <feature-id>` for both impl and test tasks (grouping only --
|
|
94
162
|
do NOT `bd dep add <feature-id> <impl-task>` or `<feature-id> <test-task>`; a feature's
|
|
@@ -100,27 +168,34 @@ Wire dependencies (semantics: `bd dep add A B` means A is blocked by B -- B must
|
|
|
100
168
|
|
|
101
169
|
## Step 4 -- Validate your own DAG
|
|
102
170
|
|
|
103
|
-
Before finishing, run
|
|
104
|
-
|
|
171
|
+
Before finishing, run these PER SPRINT ROOT (if you were given more than one sprint goal,
|
|
172
|
+
run each and reason over the COMBINED result -- `--parent` takes exactly one id per call;
|
|
173
|
+
see the graph-semantics section above for why bare `bd ready`/`bd blocked` are the wrong
|
|
174
|
+
check):
|
|
105
175
|
```bash
|
|
106
|
-
bd graph --compact <
|
|
107
|
-
bd blocked --parent <
|
|
108
|
-
bd list --parent <
|
|
176
|
+
bd graph --compact <root-id>
|
|
177
|
+
bd blocked --parent <root-id>
|
|
178
|
+
bd list --parent <root-id> --ready --type=task --json
|
|
109
179
|
```
|
|
110
180
|
|
|
111
|
-
**Acyclicity check (mandatory):** A correct DAG has no cycles.
|
|
112
|
-
|
|
113
|
-
|
|
114
|
-
|
|
115
|
-
|
|
116
|
-
|
|
181
|
+
**Acyclicity check (mandatory):** A correct DAG has no cycles. The invariant is on the
|
|
182
|
+
UNION of ready work across all roots, NOT each root alone. Verify:
|
|
183
|
+
1. The COMBINED `--ready` list across all sprint roots must contain at least one issue
|
|
184
|
+
whenever open work exists anywhere in scope. If the union is empty while open work
|
|
185
|
+
remains, there is a cycle -- find and break it before finishing. A SINGLE root whose
|
|
186
|
+
own `--ready` list is empty is FINE when its open tasks are legitimately blocked by an
|
|
187
|
+
open task in a DIFFERENT root (a cross-goal ordering edge) -- that is not a cycle, do
|
|
188
|
+
NOT remove the edge. (A bare `bd ready` is NOT a valid substitute -- it returns
|
|
189
|
+
project-wide results and will show unrelated ready work even when your entire sprint
|
|
190
|
+
scope is deadlocked.)
|
|
117
191
|
2. A feature/task must NEVER have a `blocks` edge to or from its own `--parent`
|
|
118
192
|
ancestor/descendant -- see the graph-semantics section above. Only `parent-child` edges
|
|
119
193
|
(via `--parent`) should exist between a bead and its parent; `blocks` edges belong only
|
|
120
194
|
between siblings.
|
|
121
|
-
3. Check `bd blocked --parent <
|
|
122
|
-
something that is itself unblocked (eventually reachable from the
|
|
123
|
-
list).
|
|
195
|
+
3. Check `bd blocked --parent <root-id>` for each root -- every blocked issue must be
|
|
196
|
+
blocked by something that is itself unblocked (eventually reachable from the union
|
|
197
|
+
`--ready` list, possibly in another root). Only if a blocked issue traces back to
|
|
198
|
+
itself is that a cycle.
|
|
124
199
|
|
|
125
200
|
If you find a cycle: remove the offending dependency with `bd dep remove <A> <B>`, fix the
|
|
126
201
|
direction, and re-run the scoped `--ready` query to confirm issues are unblocked.
|
|
@@ -131,6 +206,8 @@ Also check each open feature:
|
|
|
131
206
|
- No task spans more than ~3 file changes?
|
|
132
207
|
- Test tasks are downstream of implementation tasks?
|
|
133
208
|
- Every task has a model tier set via `--metadata '{"model": "..."}'` (see Step 3)?
|
|
209
|
+
- Every task carries `streak` and `streakOrder` lane metadata (see Step 3)? Impl/test
|
|
210
|
+
pairs and mutex-resource members co-laned, and no lane's effort exceeds the threshold?
|
|
134
211
|
|
|
135
212
|
Fix any gaps, then confirm you are done.
|
|
136
213
|
|
|
@@ -157,3 +234,6 @@ evaluates against its own Output schema (see `plan-reviewer.md` and its sibling
|
|
|
157
234
|
- Every task must be completable in one agent session
|
|
158
235
|
- A task with no acceptance criteria is incomplete -- fix it before finishing
|
|
159
236
|
- Every task must carry a model tier in `--metadata '{"model": "..."}'` -- fix before finishing
|
|
237
|
+
- Every task must carry `streak`/`streakOrder` lane metadata alongside `model` in the same
|
|
238
|
+
`--metadata` channel; lanes must respect the effort threshold and never split
|
|
239
|
+
mutex-resource members apart -- fix before finishing
|