@apralabs/apra-fleet 0.4.2 → 0.4.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +38 -5
- package/dist/agents/backlog-groomer.md +25 -0
- package/dist/agents/ci-watcher.md +11 -0
- package/dist/agents/deployer.md +37 -2
- package/dist/agents/doer.md +36 -12
- package/dist/agents/harvester.md +11 -0
- package/dist/agents/integ-test-runner.md +11 -0
- package/dist/agents/kb-reconciler.md +9 -0
- package/dist/agents/plan-reviewer.md +110 -22
- package/dist/agents/planner.md +125 -37
- package/dist/agents/regression-test-runner.md +11 -0
- package/dist/agents/reviewer.md +13 -2
- package/dist/agents/schemas/plan-reviewer-output.json +37 -0
- package/dist/cli/agent-transform.d.ts +83 -2
- package/dist/cli/agent-transform.d.ts.map +1 -1
- package/dist/cli/agent-transform.js +266 -21
- package/dist/cli/agent-transform.js.map +1 -1
- package/dist/cli/auth.d.ts.map +1 -1
- package/dist/cli/auth.js +28 -9
- package/dist/cli/auth.js.map +1 -1
- package/dist/cli/config.d.ts +7 -5
- package/dist/cli/config.d.ts.map +1 -1
- package/dist/cli/config.js +44 -34
- package/dist/cli/config.js.map +1 -1
- package/dist/cli/install.d.ts +33 -0
- package/dist/cli/install.d.ts.map +1 -1
- package/dist/cli/install.js +290 -23
- package/dist/cli/install.js.map +1 -1
- package/dist/cli/kb-directives.d.ts.map +1 -1
- package/dist/cli/kb-directives.js +2 -1
- package/dist/cli/kb-directives.js.map +1 -1
- package/dist/cli/register-member.d.ts.map +1 -1
- package/dist/cli/register-member.js +6 -2
- package/dist/cli/register-member.js.map +1 -1
- package/dist/commands/kb-server.d.ts +3 -0
- package/dist/commands/kb-server.d.ts.map +1 -1
- package/dist/commands/kb-server.js +43 -3
- package/dist/commands/kb-server.js.map +1 -1
- package/dist/index.js +3 -3
- package/dist/os/linux.d.ts +6 -0
- package/dist/os/linux.d.ts.map +1 -1
- package/dist/os/linux.js +35 -2
- package/dist/os/linux.js.map +1 -1
- package/dist/os/os-commands.d.ts +61 -2
- package/dist/os/os-commands.d.ts.map +1 -1
- package/dist/os/windows-gitbash.d.ts +5 -0
- package/dist/os/windows-gitbash.d.ts.map +1 -1
- package/dist/os/windows-gitbash.js +15 -0
- package/dist/os/windows-gitbash.js.map +1 -1
- package/dist/os/windows.d.ts +6 -0
- package/dist/os/windows.d.ts.map +1 -1
- package/dist/os/windows.js +46 -3
- package/dist/os/windows.js.map +1 -1
- package/dist/providers/agy.d.ts +115 -6
- package/dist/providers/agy.d.ts.map +1 -1
- package/dist/providers/agy.js +569 -53
- package/dist/providers/agy.js.map +1 -1
- package/dist/providers/claude.d.ts +81 -3
- package/dist/providers/claude.d.ts.map +1 -1
- package/dist/providers/claude.js +344 -10
- package/dist/providers/claude.js.map +1 -1
- package/dist/providers/codex.d.ts +4 -2
- package/dist/providers/codex.d.ts.map +1 -1
- package/dist/providers/codex.js +19 -2
- package/dist/providers/codex.js.map +1 -1
- package/dist/providers/copilot.d.ts +4 -2
- package/dist/providers/copilot.d.ts.map +1 -1
- package/dist/providers/copilot.js +20 -2
- package/dist/providers/copilot.js.map +1 -1
- package/dist/providers/none.d.ts +4 -2
- package/dist/providers/none.d.ts.map +1 -1
- package/dist/providers/none.js +17 -2
- package/dist/providers/none.js.map +1 -1
- package/dist/providers/opencode.d.ts +3 -1
- package/dist/providers/opencode.d.ts.map +1 -1
- package/dist/providers/opencode.js +22 -2
- package/dist/providers/opencode.js.map +1 -1
- package/dist/providers/provider.d.ts +201 -6
- package/dist/providers/provider.d.ts.map +1 -1
- package/dist/providers/provider.js +56 -0
- package/dist/providers/provider.js.map +1 -1
- package/dist/services/agy-project.d.ts +102 -0
- package/dist/services/agy-project.d.ts.map +1 -0
- package/dist/services/agy-project.js +356 -0
- package/dist/services/agy-project.js.map +1 -0
- package/dist/services/auth-socket.js +4 -4
- package/dist/services/auth-web.js +1 -1
- package/dist/services/cloud/lifecycle.d.ts.map +1 -1
- package/dist/services/cloud/lifecycle.js +33 -4
- package/dist/services/cloud/lifecycle.js.map +1 -1
- package/dist/services/credential-cleanup.d.ts.map +1 -1
- package/dist/services/credential-cleanup.js +35 -17
- package/dist/services/credential-cleanup.js.map +1 -1
- package/dist/services/exit-drain.d.ts +44 -0
- package/dist/services/exit-drain.d.ts.map +1 -0
- package/dist/services/exit-drain.js +52 -0
- package/dist/services/exit-drain.js.map +1 -0
- package/dist/services/github-app.d.ts.map +1 -1
- package/dist/services/github-app.js +32 -4
- package/dist/services/github-app.js.map +1 -1
- package/dist/services/http-transport.d.ts +1 -0
- package/dist/services/http-transport.d.ts.map +1 -1
- package/dist/services/http-transport.js +48 -1
- package/dist/services/http-transport.js.map +1 -1
- package/dist/services/knowledge/kb-config.d.ts +42 -0
- package/dist/services/knowledge/kb-config.d.ts.map +1 -0
- package/dist/services/knowledge/kb-config.js +54 -0
- package/dist/services/knowledge/kb-config.js.map +1 -0
- package/dist/services/knowledge/kb-providers.d.ts +7 -1
- package/dist/services/knowledge/kb-providers.d.ts.map +1 -1
- package/dist/services/knowledge/kb-providers.js +191 -17
- package/dist/services/knowledge/kb-providers.js.map +1 -1
- package/dist/services/knowledge/require-sqlite-project.d.ts +32 -0
- package/dist/services/knowledge/require-sqlite-project.d.ts.map +1 -0
- package/dist/services/knowledge/require-sqlite-project.js +38 -0
- package/dist/services/knowledge/require-sqlite-project.js.map +1 -0
- package/dist/services/model-pricing.d.ts.map +1 -1
- package/dist/services/model-pricing.js +7 -3
- package/dist/services/model-pricing.js.map +1 -1
- package/dist/services/secret-token.d.ts +38 -0
- package/dist/services/secret-token.d.ts.map +1 -0
- package/dist/services/secret-token.js +51 -0
- package/dist/services/secret-token.js.map +1 -0
- package/dist/services/service-manager/types.d.ts +3 -1
- package/dist/services/service-manager/types.d.ts.map +1 -1
- package/dist/services/service-manager/windows.d.ts +14 -2
- package/dist/services/service-manager/windows.d.ts.map +1 -1
- package/dist/services/service-manager/windows.js +65 -7
- package/dist/services/service-manager/windows.js.map +1 -1
- package/dist/services/ssh.d.ts.map +1 -1
- package/dist/services/ssh.js +58 -2
- package/dist/services/ssh.js.map +1 -1
- package/dist/services/stall/read-log-tail.d.ts.map +1 -1
- package/dist/services/stall/read-log-tail.js +20 -10
- package/dist/services/stall/read-log-tail.js.map +1 -1
- package/dist/services/stall/stall-detector.d.ts +53 -4
- package/dist/services/stall/stall-detector.d.ts.map +1 -1
- package/dist/services/stall/stall-detector.js +212 -34
- package/dist/services/stall/stall-detector.js.map +1 -1
- package/dist/services/strategy.d.ts.map +1 -1
- package/dist/services/strategy.js +79 -2
- package/dist/services/strategy.js.map +1 -1
- package/dist/services/substitution-engine.js +2 -2
- package/dist/services/substitution-engine.js.map +1 -1
- package/dist/services/tool-registry.d.ts.map +1 -1
- package/dist/services/tool-registry.js +5 -3
- package/dist/services/tool-registry.js.map +1 -1
- package/dist/services/vcs/azure-devops.d.ts +66 -1
- package/dist/services/vcs/azure-devops.d.ts.map +1 -1
- package/dist/services/vcs/azure-devops.js +192 -21
- package/dist/services/vcs/azure-devops.js.map +1 -1
- package/dist/services/vcs/types.d.ts +1 -1
- package/dist/skills/fleet-sprint-cli/SKILL.md +18 -0
- package/dist/skills/pm/SKILL.md +1 -1
- package/dist/skills/pm/cost.md +0 -3
- package/dist/skills/pm/fleet-addendum.md +2 -2
- package/dist/tools/check-status.d.ts +7 -4
- package/dist/tools/check-status.d.ts.map +1 -1
- package/dist/tools/check-status.js +2 -0
- package/dist/tools/check-status.js.map +1 -1
- package/dist/tools/compose-permissions.d.ts +6 -0
- package/dist/tools/compose-permissions.d.ts.map +1 -1
- package/dist/tools/compose-permissions.js +182 -34
- package/dist/tools/compose-permissions.js.map +1 -1
- package/dist/tools/credential-store-set.js +1 -1
- package/dist/tools/execute-command.d.ts.map +1 -1
- package/dist/tools/execute-command.js +31 -20
- package/dist/tools/execute-command.js.map +1 -1
- package/dist/tools/execute-prompt.d.ts +15 -2
- package/dist/tools/execute-prompt.d.ts.map +1 -1
- package/dist/tools/execute-prompt.js +1196 -892
- package/dist/tools/execute-prompt.js.map +1 -1
- package/dist/tools/kb-capture.d.ts +2 -2
- package/dist/tools/kb-capture.d.ts.map +1 -1
- package/dist/tools/kb-capture.js +29 -5
- package/dist/tools/kb-capture.js.map +1 -1
- package/dist/tools/kb-export.d.ts +2 -2
- package/dist/tools/kb-export.d.ts.map +1 -1
- package/dist/tools/kb-export.js +3 -28
- package/dist/tools/kb-export.js.map +1 -1
- package/dist/tools/kb-feedback.d.ts.map +1 -1
- package/dist/tools/kb-feedback.js +3 -1
- package/dist/tools/kb-feedback.js.map +1 -1
- package/dist/tools/kb-freshness-sweep.d.ts.map +1 -1
- package/dist/tools/kb-freshness-sweep.js +3 -1
- package/dist/tools/kb-freshness-sweep.js.map +1 -1
- package/dist/tools/kb-import.d.ts.map +1 -1
- package/dist/tools/kb-import.js +2 -1
- package/dist/tools/kb-import.js.map +1 -1
- package/dist/tools/kb-list.d.ts.map +1 -1
- package/dist/tools/kb-list.js +3 -1
- package/dist/tools/kb-list.js.map +1 -1
- package/dist/tools/kb-query.d.ts +2 -2
- package/dist/tools/kb-reconcile-prefilter.d.ts.map +1 -1
- package/dist/tools/kb-reconcile-prefilter.js +3 -1
- package/dist/tools/kb-reconcile-prefilter.js.map +1 -1
- package/dist/tools/kb-resolve-contradiction.d.ts.map +1 -1
- package/dist/tools/kb-resolve-contradiction.js +3 -1
- package/dist/tools/kb-resolve-contradiction.js.map +1 -1
- package/dist/tools/kb-setup.d.ts.map +1 -1
- package/dist/tools/kb-setup.js +125 -20
- package/dist/tools/kb-setup.js.map +1 -1
- package/dist/tools/kb-stats.d.ts.map +1 -1
- package/dist/tools/kb-stats.js +64 -43
- package/dist/tools/kb-stats.js.map +1 -1
- package/dist/tools/list-members.d.ts +2 -2
- package/dist/tools/list-members.d.ts.map +1 -1
- package/dist/tools/list-members.js +1 -0
- package/dist/tools/list-members.js.map +1 -1
- package/dist/tools/member-detail.d.ts +2 -2
- package/dist/tools/member-detail.d.ts.map +1 -1
- package/dist/tools/member-detail.js +17 -0
- package/dist/tools/member-detail.js.map +1 -1
- package/dist/tools/member-reservation.d.ts +58 -1
- package/dist/tools/member-reservation.d.ts.map +1 -1
- package/dist/tools/member-reservation.js +61 -20
- package/dist/tools/member-reservation.js.map +1 -1
- package/dist/tools/provision-auth.d.ts +80 -1
- package/dist/tools/provision-auth.d.ts.map +1 -1
- package/dist/tools/provision-auth.js +142 -54
- package/dist/tools/provision-auth.js.map +1 -1
- package/dist/tools/provision-vcs-auth.d.ts +91 -1
- package/dist/tools/provision-vcs-auth.d.ts.map +1 -1
- package/dist/tools/provision-vcs-auth.js +209 -49
- package/dist/tools/provision-vcs-auth.js.map +1 -1
- package/dist/tools/register-member.d.ts +12 -9
- package/dist/tools/register-member.d.ts.map +1 -1
- package/dist/tools/register-member.js +99 -12
- package/dist/tools/register-member.js.map +1 -1
- package/dist/tools/remove-member.d.ts.map +1 -1
- package/dist/tools/remove-member.js +27 -2
- package/dist/tools/remove-member.js.map +1 -1
- package/dist/tools/send-email.d.ts +2 -2
- package/dist/tools/setup-git-app.d.ts.map +1 -1
- package/dist/tools/setup-git-app.js +11 -7
- package/dist/tools/setup-git-app.js.map +1 -1
- 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 +23 -1
- package/dist/tools/shutdown-server.js.map +1 -1
- package/dist/tools/update-member.d.ts +12 -9
- package/dist/tools/update-member.d.ts.map +1 -1
- package/dist/tools/update-member.js +43 -11
- package/dist/tools/update-member.js.map +1 -1
- package/dist/tools/vcs-credential-exec.d.ts +127 -0
- package/dist/tools/vcs-credential-exec.d.ts.map +1 -0
- package/dist/tools/vcs-credential-exec.js +197 -0
- package/dist/tools/vcs-credential-exec.js.map +1 -0
- package/dist/types.d.ts +13 -0
- package/dist/types.d.ts.map +1 -1
- package/dist/utils/log-helpers.d.ts.map +1 -1
- package/dist/utils/log-helpers.js +2 -2
- package/dist/utils/log-helpers.js.map +1 -1
- package/dist/utils/prompt-errors.d.ts.map +1 -1
- package/dist/utils/prompt-errors.js +7 -1
- package/dist/utils/prompt-errors.js.map +1 -1
- package/dist/utils/shell-escape.d.ts +16 -0
- package/dist/utils/shell-escape.d.ts.map +1 -1
- package/dist/utils/shell-escape.js +22 -2
- package/dist/utils/shell-escape.js.map +1 -1
- package/dist/utils/vcs-provider-detect.d.ts +65 -0
- package/dist/utils/vcs-provider-detect.d.ts.map +1 -0
- package/dist/utils/vcs-provider-detect.js +109 -0
- package/dist/utils/vcs-provider-detect.js.map +1 -0
- package/dist/utils/workspace-trust.d.ts +20 -17
- package/dist/utils/workspace-trust.d.ts.map +1 -1
- package/dist/utils/workspace-trust.js +87 -1
- package/dist/utils/workspace-trust.js.map +1 -1
- package/dist/workflows/auto-sprint.js +176 -15
- package/package.json +6 -4
- package/packages/apra-fleet-client/src/client/api.mjs +319 -17
- package/packages/apra-fleet-client/src/client/errors.mjs +6 -2
- package/packages/apra-fleet-se/apra-pm/agents/_shared/GRAPH-SEMANTICS.md +10 -2
- package/packages/apra-fleet-se/apra-pm/agents/backlog-groomer.md +25 -0
- package/packages/apra-fleet-se/apra-pm/agents/ci-watcher.md +11 -0
- package/packages/apra-fleet-se/apra-pm/agents/deployer.md +37 -2
- package/packages/apra-fleet-se/apra-pm/agents/doer.md +36 -12
- package/packages/apra-fleet-se/apra-pm/agents/harvester.md +11 -0
- package/packages/apra-fleet-se/apra-pm/agents/integ-test-runner.md +11 -0
- package/packages/apra-fleet-se/apra-pm/agents/kb-reconciler.md +9 -0
- package/packages/apra-fleet-se/apra-pm/agents/plan-reviewer.md +110 -22
- package/packages/apra-fleet-se/apra-pm/agents/planner.md +125 -37
- package/packages/apra-fleet-se/apra-pm/agents/regression-test-runner.md +11 -0
- package/packages/apra-fleet-se/apra-pm/agents/reviewer.md +13 -2
- package/packages/apra-fleet-se/apra-pm/agents/schemas/plan-reviewer-output.json +37 -0
- package/packages/apra-fleet-se/apra-pm/skills/pm/SKILL.md +1 -1
- package/packages/apra-fleet-se/apra-pm/skills/pm/cost.md +0 -3
- package/packages/apra-fleet-se/apra-pm/skills/pm/fleet-addendum.md +2 -2
- package/packages/apra-fleet-se/bin/cli.mjs +149 -1
- package/packages/apra-fleet-se/bin/serve.mjs +78 -4
- package/packages/apra-fleet-se/fleet-sprint/abort.mjs +481 -0
- package/packages/apra-fleet-se/fleet-sprint/beads-children.mjs +491 -0
- package/packages/apra-fleet-se/fleet-sprint/beads-identity-check.mjs +282 -0
- package/packages/apra-fleet-se/fleet-sprint/beads-identity.mjs +208 -0
- package/packages/apra-fleet-se/fleet-sprint/beads-scope.mjs +638 -0
- package/packages/apra-fleet-se/fleet-sprint/beads-transitions.mjs +301 -0
- package/packages/apra-fleet-se/fleet-sprint/branch-ensure.mjs +96 -0
- package/packages/apra-fleet-se/fleet-sprint/conflict-ladder.mjs +8 -0
- package/packages/apra-fleet-se/fleet-sprint/contracts.mjs +61 -14
- package/packages/apra-fleet-se/fleet-sprint/coordination.mjs +516 -0
- package/packages/apra-fleet-se/fleet-sprint/dispatch-failure.mjs +184 -0
- package/packages/apra-fleet-se/fleet-sprint/dispatch-role.mjs +1121 -0
- package/packages/apra-fleet-se/fleet-sprint/dispatch-safety-guard.mjs +216 -4
- package/packages/apra-fleet-se/fleet-sprint/docs/README.md +1 -1
- package/packages/apra-fleet-se/fleet-sprint/docs/dolt-sync-redesign.md +276 -0
- package/packages/apra-fleet-se/fleet-sprint/docs/escalate-to-llm-design.md +1 -1
- package/packages/apra-fleet-se/fleet-sprint/docs/run-sprint-cycle-prelude-decision.md +215 -0
- package/packages/apra-fleet-se/fleet-sprint/dolt-literal-guard.mjs +56 -1
- package/packages/apra-fleet-se/fleet-sprint/dolt-sync.mjs +996 -32
- package/packages/apra-fleet-se/fleet-sprint/errors.mjs +267 -0
- package/packages/apra-fleet-se/fleet-sprint/explicit-id-create-guard.mjs +501 -0
- package/packages/apra-fleet-se/fleet-sprint/fatal-diagnostics.mjs +134 -0
- package/packages/apra-fleet-se/fleet-sprint/full-db-fetch-guard.mjs +102 -0
- package/packages/apra-fleet-se/fleet-sprint/git-sync.mjs +556 -0
- package/packages/apra-fleet-se/fleet-sprint/git-topology.mjs +495 -0
- package/packages/apra-fleet-se/fleet-sprint/guarded-modules.mjs +564 -0
- package/packages/apra-fleet-se/fleet-sprint/inline-ladder-guard.mjs +216 -0
- package/packages/apra-fleet-se/fleet-sprint/kb.mjs +728 -0
- package/packages/apra-fleet-se/fleet-sprint/mcp-result.mjs +75 -0
- package/packages/apra-fleet-se/fleet-sprint/member-provisioning.mjs +252 -0
- package/packages/apra-fleet-se/fleet-sprint/member-sync.mjs +581 -0
- package/packages/apra-fleet-se/fleet-sprint/member-target.mjs +93 -0
- package/packages/apra-fleet-se/fleet-sprint/newtask-text.mjs +266 -0
- package/packages/apra-fleet-se/fleet-sprint/parent-notes-staleness.mjs +201 -0
- package/packages/apra-fleet-se/fleet-sprint/phases/deploy.mjs +136 -0
- package/packages/apra-fleet-se/fleet-sprint/phases/develop.mjs +822 -0
- package/packages/apra-fleet-se/fleet-sprint/phases/ensure-sprint-branch.mjs +294 -0
- package/packages/apra-fleet-se/fleet-sprint/phases/final-review.mjs +403 -0
- package/packages/apra-fleet-se/fleet-sprint/phases/harvest.mjs +180 -0
- package/packages/apra-fleet-se/fleet-sprint/phases/integ-test.mjs +358 -0
- package/packages/apra-fleet-se/fleet-sprint/phases/plan.mjs +390 -0
- package/packages/apra-fleet-se/fleet-sprint/phases/publish-pr.mjs +323 -0
- package/packages/apra-fleet-se/fleet-sprint/phases/re-review.mjs +232 -0
- package/packages/apra-fleet-se/fleet-sprint/phases/regression-test.mjs +174 -0
- package/packages/apra-fleet-se/fleet-sprint/phases/replan.mjs +197 -0
- package/packages/apra-fleet-se/fleet-sprint/phases/review.mjs +305 -0
- package/packages/apra-fleet-se/fleet-sprint/prompts.mjs +559 -0
- package/packages/apra-fleet-se/fleet-sprint/role-policies.mjs +1416 -0
- package/packages/apra-fleet-se/fleet-sprint/round-session.mjs +100 -0
- package/packages/apra-fleet-se/fleet-sprint/runner.js +1467 -9798
- package/packages/apra-fleet-se/fleet-sprint/se-posix.mjs +17 -12
- package/packages/apra-fleet-se/fleet-sprint/shell-command-guard.mjs +304 -0
- package/packages/apra-fleet-se/fleet-sprint/skills/fleet-sprint-cli/SKILL.md +18 -0
- package/packages/apra-fleet-se/fleet-sprint/skills/fleet-supervisor/SKILL.md +21 -2
- package/packages/apra-fleet-se/fleet-sprint/sprint-args.mjs +454 -0
- package/packages/apra-fleet-se/fleet-sprint/sprint-report.mjs +239 -0
- package/packages/apra-fleet-se/fleet-sprint/sprint-state.mjs +163 -0
- package/packages/apra-fleet-se/fleet-sprint/unbracketed-push-guard.mjs +234 -0
- package/packages/apra-fleet-se/fleet-sprint/usage-limit-controller.mjs +211 -0
- package/packages/apra-fleet-se/fleet-sprint/vcs-auth.mjs +1279 -0
- package/packages/apra-fleet-se/fleet-sprint/vcs-module.mjs +153 -19
- package/packages/apra-fleet-se/fleet-sprint/vcs-providers/azure-devops.mjs +71 -21
- package/packages/apra-fleet-se/fleet-sprint/vcs-providers/bitbucket.mjs +28 -0
- package/packages/apra-fleet-se/fleet-sprint/vcs-providers/github.mjs +131 -0
- package/packages/apra-fleet-se/fleet-sprint/vcs-providers/index.mjs +140 -16
- package/packages/apra-fleet-se/fleet-sprint/vcs-providers/shell-helpers.mjs +1 -0
- package/packages/apra-fleet-se/fleet-sprint/viewer-extensions.mjs +77 -2
- package/packages/apra-fleet-se/fleet-sprint/worklists.mjs +559 -0
- package/packages/apra-fleet-se/package.json +1 -1
- package/packages/apra-fleet-workflow/src/viewer/index.mjs +17 -6
- package/packages/apra-fleet-workflow/src/workflow/index.mjs +49 -7
- package/skills/fleet/SKILL.md +8 -8
- package/skills/fleet/auth-azdevops.md +14 -3
- package/skills/fleet/auth-bitbucket.md +2 -2
- package/skills/fleet/auth-github.md +5 -4
- package/skills/fleet/onboarding.md +3 -3
- package/skills/fleet/permissions.md +5 -1
- package/skills/fleet/profiles/node.json +1 -1
- package/skills/fleet/troubleshooting.md +3 -3
- package/version.json +1 -1
package/dist/agents/planner.md
CHANGED
|
@@ -30,8 +30,14 @@ orchestrator that planning has no input to work from -- do not create speculativ
|
|
|
30
30
|
|
|
31
31
|
## Step 0 -- Knowledge Bank (required -- do this BEFORE any other work)
|
|
32
32
|
|
|
33
|
+
<!-- if-tool: ToolSearch -->
|
|
33
34
|
1. Run ToolSearch with query
|
|
34
35
|
`"select:mcp__apra-fleet__kb_session_prime,mcp__apra-fleet__kb_query,mcp__apra-fleet__kb_stats,mcp__apra-fleet__kb_capture,mcp__apra-fleet__kb_feedback"`
|
|
36
|
+
<!-- else-tool: ToolSearch -->
|
|
37
|
+
1. No tool-discovery step is needed on this provider: every step below names the KB
|
|
38
|
+
tool it wants directly. Confirm your environment exposes those tools, then call
|
|
39
|
+
them as written.
|
|
40
|
+
<!-- end-tool: ToolSearch -->
|
|
35
41
|
2. Call `mcp__apra-fleet__kb_session_prime` with `repo_path` set to the repo you are
|
|
36
42
|
planning for, and `hint_symbols`/`hint_modules` derived from the sprint goals /
|
|
37
43
|
requirements you are about to decompose (skim them first to extract key symbol
|
|
@@ -64,7 +70,12 @@ orchestrator that planning has no input to work from -- do not create speculativ
|
|
|
64
70
|
5. If a KB entry you retrieved proves wrong in practice, call `mcp__apra-fleet__kb_feedback`
|
|
65
71
|
with the entry id and what was wrong.
|
|
66
72
|
|
|
73
|
+
<!-- if-tool: ToolSearch -->
|
|
67
74
|
If ToolSearch returns no KB tools (MCP server not running), skip these steps and proceed.
|
|
75
|
+
<!-- else-tool: ToolSearch -->
|
|
76
|
+
If those KB tools are not available in your environment (MCP server not running), skip
|
|
77
|
+
these steps and proceed.
|
|
78
|
+
<!-- end-tool: ToolSearch -->
|
|
68
79
|
|
|
69
80
|
## Step 1 -- Explore the backlog
|
|
70
81
|
|
|
@@ -96,6 +107,23 @@ anywhere in the title, so the doubled `[regression][carry-over]` prefix is found
|
|
|
96
107
|
extra quoting; and it EXCLUDES closed issues by default -- add `--status all` only when
|
|
97
108
|
auditing history.
|
|
98
109
|
|
|
110
|
+
**Read NOTES before decomposing.** Before decomposing any bead -- sprint goal, feature,
|
|
111
|
+
or task -- that has a non-empty NOTES section, read NOTES in full, in chronological
|
|
112
|
+
order, as part of understanding the bead's current scope, not merely as optional
|
|
113
|
+
background context. A bead's NOTES section functions as an append-only changelog:
|
|
114
|
+
corrections, amendments, and design-review findings accumulate there over the bead's
|
|
115
|
+
lifetime, often after its DESCRIPTION was written. Treat a NOTES entry that explicitly
|
|
116
|
+
corrects, amends, or supersedes something in DESCRIPTION -- recognizable by language such
|
|
117
|
+
as "CORRECTION", "AMENDMENT", "SUPERSEDES", "REVISED", or an explicit "do X, not Y"
|
|
118
|
+
statement -- as authoritative over the DESCRIPTION passage it contradicts. When writing a
|
|
119
|
+
child's own DESCRIPTION/acceptance criteria (Steps 2 and 3 below), do not copy stale
|
|
120
|
+
DESCRIPTION language verbatim if a later NOTES entry corrected it -- write the child from
|
|
121
|
+
the corrected understanding. It is fine, and often preferable, for the child to
|
|
122
|
+
explicitly cite which correction it incorporates, so a later reader does not need to
|
|
123
|
+
cross-reference the parent's full history. This does not change how you decompose a bead
|
|
124
|
+
whose NOTES is empty or purely procedural (e.g. claim/close log lines) -- it applies only
|
|
125
|
+
when NOTES contains substantive corrections to DESCRIPTION.
|
|
126
|
+
|
|
99
127
|
## Step 2 -- Decompose sprint goals into features
|
|
100
128
|
|
|
101
129
|
Every title you write below (Steps 2 and 3) is plain text only -- letters,
|
|
@@ -121,7 +149,11 @@ making them independent siblings.
|
|
|
121
149
|
For each feature create two classes of tasks:
|
|
122
150
|
|
|
123
151
|
**Implementation tasks** (`[impl]` prefix optional but helpful):
|
|
124
|
-
- One task per
|
|
152
|
+
- One task per independently verifiable change. A task is the unit the doer commits and
|
|
153
|
+
closes; the LANE (below) is the unit the reviewer reviews. Keep a task small enough to
|
|
154
|
+
have crisp acceptance criteria (typically 1-4 files), but do NOT split a change into
|
|
155
|
+
several tasks just to keep each one small -- a chain of tiny dependent tasks is more
|
|
156
|
+
expensive to review than one lane that holds them together.
|
|
125
157
|
- Title: specific and imperative ("Add password reset endpoint to auth router")
|
|
126
158
|
- Description includes: expected files to change, expected behaviour, acceptance
|
|
127
159
|
criteria. The file list is a best-effort scope estimate, NOT an allowlist -- phrase it
|
|
@@ -182,35 +214,75 @@ Pick from the models actually available in the current environment. A user overr
|
|
|
182
214
|
always wins.
|
|
183
215
|
|
|
184
216
|
**Streak lane metadata** (required on every task, both impl and test): in addition to
|
|
185
|
-
`model`, record
|
|
217
|
+
`model`, record three lane fields through the SAME beads metadata channel at creation time --
|
|
186
218
|
never in `--notes`, a METADATA-section comment, or anywhere else:
|
|
187
219
|
```bash
|
|
188
|
-
bd create ... --metadata '{"model": "<cheap|standard|premium>", "streak": "<lane-id>", "streakOrder": <n>}'
|
|
220
|
+
bd create ... --metadata '{"model": "<cheap|standard|premium>", "size": "<S|M|L>", "streak": "<lane-id>", "streakOrder": <n>}'
|
|
189
221
|
```
|
|
190
222
|
- `streak` -- a stable lane identifier (any short opaque string) shared by every task to
|
|
191
223
|
be dispatched together to a single doer; read back via `bd show <id>` like `model`.
|
|
192
224
|
- `streakOrder` -- an integer giving this task's intended position within its lane. Lower
|
|
193
|
-
runs first; ties
|
|
194
|
-
|
|
195
|
-
|
|
196
|
-
|
|
197
|
-
|
|
198
|
-
|
|
199
|
-
|
|
200
|
-
|
|
201
|
-
|
|
202
|
-
|
|
203
|
-
|
|
204
|
-
|
|
205
|
-
|
|
206
|
-
|
|
207
|
-
|
|
208
|
-
|
|
209
|
-
|
|
210
|
-
|
|
211
|
-
|
|
212
|
-
|
|
213
|
-
|
|
225
|
+
runs first; ties break by insertion order -- do NOT use a `blocks` edge to break an
|
|
226
|
+
intra-lane tie (see the dependency-wiring rules below).
|
|
227
|
+
- `size` -- `S`/`M`/`L`, used for lane sizing below.
|
|
228
|
+
|
|
229
|
+
**Lanes are review units.** The engine dispatches every task in one lane to ONE doer in
|
|
230
|
+
`streakOrder`, and the reviewer reviews a whole Develop ROUND at once -- every lane
|
|
231
|
+
dispatched in that round together. A lane is therefore the SMALLEST thing a review can
|
|
232
|
+
cover: never split one coherent increment across two lanes joined by a `blocks` edge,
|
|
233
|
+
because each extra link in that chain costs a full review round (diff read + full test
|
|
234
|
+
run). Lanes with no `blocks` edge between them dispatch and review in the SAME round
|
|
235
|
+
whenever the round's doer count and effort budget allow (unlaned-but-independent lanes
|
|
236
|
+
overflow to the next round only under doer/budget pressure, not because they were kept
|
|
237
|
+
separate), so normally that costs nothing extra -- keep genuinely independent work in
|
|
238
|
+
separate lanes rather than merging it for size alone; merging removes parallelism without
|
|
239
|
+
reliably saving a review.
|
|
240
|
+
|
|
241
|
+
Put tasks in the SAME lane when they are highly coupled or cohesive -- any of:
|
|
242
|
+
- they touch the same files, module, or component, or the same test suite;
|
|
243
|
+
- one exists to enable the next (add a helper, then use it; change a schema, then its
|
|
244
|
+
consumer; implement, then its `[test]` task) -- an `[impl]` task and its paired `[test]`
|
|
245
|
+
task ALWAYS share a lane, UNLESS the feature's impl work itself had to span multiple
|
|
246
|
+
lanes under the sizing rules below -- then the feature's `[test]` task takes the LAST
|
|
247
|
+
impl lane, or ends its own final lane wired cross-lane to every impl lane it verifies;
|
|
248
|
+
- they contend for a **mutex resource** -- a resource only one change may hold at a time,
|
|
249
|
+
e.g. the same submodule pointer, a shared version/manifest field, or the same test
|
|
250
|
+
fixture -- these MUST share a lane and MUST NOT be separated into different streaks;
|
|
251
|
+
- reviewing one without the other would leave the reviewer unable to judge whether the
|
|
252
|
+
feature actually works.
|
|
253
|
+
|
|
254
|
+
Put tasks in DIFFERENT lanes only when at least one of these holds:
|
|
255
|
+
- they are genuinely independent (different feature areas, no shared files, no enabling
|
|
256
|
+
relationship) -- so multiple doers can run them in parallel;
|
|
257
|
+
- they sit on different sides of a RISK BOUNDARY: a change the reviewer must sign off
|
|
258
|
+
before further work is safe to build on (a public contract change, a data migration, a
|
|
259
|
+
security-sensitive path, a destructive operation);
|
|
260
|
+
- a later task cannot be reviewed until the earlier one's outcome has been judged (true
|
|
261
|
+
design uncertainty) -- write the later task's criteria as conditional on that outcome,
|
|
262
|
+
not left blank, and state the dependency explicitly in its description so the criteria
|
|
263
|
+
are never read as unconditional; the earlier task ends its lane, and the later one
|
|
264
|
+
starts a new lane in the next round;
|
|
265
|
+
- the lane would exceed the sizing limits below.
|
|
266
|
+
|
|
267
|
+
**Sizing a lane.** Size buckets are the same ones the plan reviewer classifies with:
|
|
268
|
+
S = 1 file/narrow, M = 2-3 files/moderate logic, L = 3+ files or non-trivial design (see
|
|
269
|
+
the `bd create ... --metadata` example above -- `size` is recorded there, alongside
|
|
270
|
+
`model`/`streak`/`streakOrder`, not as a separate call). Then check each lane against
|
|
271
|
+
these LANE SIZING PARAMETERS (fixed defaults for now -- no per-dispatch override channel
|
|
272
|
+
exists yet):
|
|
273
|
+
- `laneMaxTasks` (default `6`): hard cap on tasks per lane -- a reviewer must be able to
|
|
274
|
+
verify the whole lane in one pass.
|
|
275
|
+
- `laneMaxEffort` (default `200`): `effort = (sum of size points S=1/M=2/L=4) x (max model
|
|
276
|
+
weight in the lane, cheap=1/standard=10/premium=20)`; caps one doer session's load.
|
|
277
|
+
- `laneTargetEffort` (default `60`): a lane BELOW this that has a cohesive neighbour (per
|
|
278
|
+
the SAME-lane rules above) should be MERGED with it, not left as its own review round.
|
|
279
|
+
State in the lane's first task description why a lane was left below target if it was.
|
|
280
|
+
|
|
281
|
+
A lane over either cap is split ONLY at a point where the earlier part is a self-contained,
|
|
282
|
+
reviewable increment (never mid-refactor, never between mutex-resource members). An
|
|
283
|
+
`[impl]` lane may be split from its feature's `[test]` task ONLY as the exception above
|
|
284
|
+
describes -- the test task then ends the chain, cross-lane blocked on every impl lane it
|
|
285
|
+
verifies; it is never itself mid-split. Give each part its own `streak` id and renumber
|
|
214
286
|
`streakOrder` from the start within it.
|
|
215
287
|
|
|
216
288
|
Wire dependencies (semantics: `bd dep add A B` means A is blocked by B -- B must finish before A can close):
|
|
@@ -218,9 +290,16 @@ Wire dependencies (semantics: `bd dep add A B` means A is blocked by B -- B must
|
|
|
218
290
|
do NOT `bd dep add <feature-id> <impl-task>` or `<feature-id> <test-task>`; a feature's
|
|
219
291
|
"not done until its tasks close" status comes from its children, never from a `blocks`
|
|
220
292
|
edge back onto them)
|
|
221
|
-
-
|
|
222
|
-
|
|
223
|
-
-
|
|
293
|
+
- INSIDE a lane, order comes from `streakOrder` ONLY. Do NOT add a `blocks` edge between
|
|
294
|
+
two tasks in the same lane -- the engine dispatches only currently-unblocked tasks, so an
|
|
295
|
+
intra-lane edge would push the later task into a separate review round and silently
|
|
296
|
+
defeat the lane. This includes the `[test]` task: it follows its `[impl]` task by
|
|
297
|
+
`streakOrder`, not by an edge.
|
|
298
|
+
- BETWEEN lanes, order comes from `blocks` edges: when lane B must not start until lane A
|
|
299
|
+
is done, add `bd dep add <B-task> <A-last-task>` for EVERY task in lane B against the
|
|
300
|
+
LAST (highest `streakOrder`) task of lane A. Wiring only B's first task would let B's
|
|
301
|
+
later tasks become ready out of order.
|
|
302
|
+
- Sibling tasks in different lanes with no enabling relationship get no edge.
|
|
224
303
|
|
|
225
304
|
## Step 4 -- Validate your own DAG
|
|
226
305
|
|
|
@@ -257,11 +336,18 @@ direction, and re-run the scoped `--ready` query to confirm issues are unblocked
|
|
|
257
336
|
Also check each open feature:
|
|
258
337
|
- Has at least one [impl] task AND one [test] task?
|
|
259
338
|
- Every task description has clear acceptance criteria?
|
|
260
|
-
-
|
|
261
|
-
|
|
262
|
-
-
|
|
263
|
-
|
|
264
|
-
|
|
339
|
+
- Every task carries `model`, `size`, `streak`, `streakOrder` metadata via `--metadata`
|
|
340
|
+
(see Step 3) -- never `--notes`?
|
|
341
|
+
- Does every lane hold ONE reviewable increment (impl + its test, all mutex members, all
|
|
342
|
+
enabling chains), within `laneMaxTasks` / `laneMaxEffort`?
|
|
343
|
+
- Is every lane below `laneTargetEffort` either justified in its first task description or
|
|
344
|
+
merged with a cohesive neighbour?
|
|
345
|
+
- Is there NO `blocks` edge between two tasks that share a `streak` id?
|
|
346
|
+
- Does every cross-lane `blocks` edge target the upstream lane's LAST task and originate
|
|
347
|
+
from EVERY task of the downstream lane?
|
|
348
|
+
- Expected review rounds (= longest chain of lanes joined by `blocks` edges): state the
|
|
349
|
+
number in your `notes`. If it exceeds 3 for one sprint goal, re-examine whether the
|
|
350
|
+
chain can be shortened by merging lanes.
|
|
265
351
|
- Where `kb_stats` backed a model tier choice, does the task description cite the
|
|
266
352
|
coverage number (see Step 3)? Not required for tiers set on qualitative KB signals
|
|
267
353
|
alone or when `kb_stats` was unavailable.
|
|
@@ -290,7 +376,7 @@ array (see Step 0.4 -- omit or send `[]` to capture nothing). Example instance:
|
|
|
290
376
|
```json
|
|
291
377
|
{
|
|
292
378
|
"status": "OK",
|
|
293
|
-
"notes": "Created 2 features, 6 tasks across 3 streak lanes.",
|
|
379
|
+
"notes": "Created 2 features, 6 tasks across 3 streak lanes; expected review rounds: 2.",
|
|
294
380
|
"featureIds": ["BD-20", "BD-21"],
|
|
295
381
|
"taskIds": ["BD-22", "BD-23", "BD-24", "BD-25", "BD-26", "BD-27"],
|
|
296
382
|
"kb_captures": []
|
|
@@ -304,7 +390,9 @@ array (see Step 0.4 -- omit or send `[]` to capture nothing). Example instance:
|
|
|
304
390
|
- NEVER add scope beyond the sprint goals you were given and open bugs/features
|
|
305
391
|
- Every task must be completable in one agent session
|
|
306
392
|
- A task with no acceptance criteria is incomplete -- fix it before finishing
|
|
307
|
-
- Every task must carry
|
|
308
|
-
|
|
309
|
-
|
|
310
|
-
|
|
393
|
+
- Every task must carry `model`, `size`, `streak` and `streakOrder` in the SAME
|
|
394
|
+
`--metadata` channel at creation time -- never `--notes` -- fix before finishing
|
|
395
|
+
- Lanes must respect `laneMaxEffort`/`laneMaxTasks` and never split mutex-resource members
|
|
396
|
+
apart
|
|
397
|
+
- Never place a `blocks` edge between two tasks that share a `streak` id -- it silently
|
|
398
|
+
defeats the lane by pushing the later task into a separate review round
|
|
@@ -8,7 +8,13 @@ tools: [Read, Bash, Grep, Glob, ToolSearch]
|
|
|
8
8
|
|
|
9
9
|
## Step 0 -- Knowledge Bank (required -- do this BEFORE bringing the sandbox up)
|
|
10
10
|
|
|
11
|
+
<!-- if-tool: ToolSearch -->
|
|
11
12
|
1. Run ToolSearch with query `"select:mcp__apra-fleet__kb_session_prime,mcp__apra-fleet__kb_capture"`
|
|
13
|
+
<!-- else-tool: ToolSearch -->
|
|
14
|
+
1. No tool-discovery step is needed on this provider: every step below names the KB
|
|
15
|
+
tool it wants directly. Confirm your environment exposes those tools, then call
|
|
16
|
+
them as written.
|
|
17
|
+
<!-- end-tool: ToolSearch -->
|
|
12
18
|
2. Call `mcp__apra-fleet__kb_session_prime` with `repo_path` set to the repo under test, and
|
|
13
19
|
`hint_modules` naming the subsystems `regression-test-playbook.md` exercises. Trust
|
|
14
20
|
CONFIRMED entries fully. Use INFERRED entries as hints, not facts. Known-flaky tests and
|
|
@@ -19,7 +25,12 @@ tools: [Read, Bash, Grep, Glob, ToolSearch]
|
|
|
19
25
|
"runbook" or "learning". A regression gotcha you had to rediscover is exactly what the
|
|
20
26
|
next sprint's run needs.
|
|
21
27
|
|
|
28
|
+
<!-- if-tool: ToolSearch -->
|
|
22
29
|
If ToolSearch returns no KB tools (MCP server not running), skip these steps and proceed.
|
|
30
|
+
<!-- else-tool: ToolSearch -->
|
|
31
|
+
If those KB tools are not available in your environment (MCP server not running), skip
|
|
32
|
+
these steps and proceed.
|
|
33
|
+
<!-- end-tool: ToolSearch -->
|
|
23
34
|
|
|
24
35
|
You own `regression-test-playbook.md` end to end: bring the test sandbox
|
|
25
36
|
up, run both playbook parts, and ALWAYS tear the sandbox down -- pass or
|
package/dist/agents/reviewer.md
CHANGED
|
@@ -31,11 +31,17 @@ stating exactly which input is missing and `reopenIds: []`, `newTasks: []`.
|
|
|
31
31
|
|
|
32
32
|
## Step 0 -- Knowledge Bank (required -- do this BEFORE any other work)
|
|
33
33
|
|
|
34
|
+
<!-- if-tool: ToolSearch -->
|
|
34
35
|
1. Run ToolSearch with query
|
|
35
36
|
`"select:mcp__apra-fleet__kb_session_prime,mcp__apra-fleet__kb_query,mcp__apra-fleet__kb_feedback,mcp__apra-fleet__code_context,mcp__apra-fleet__code_graph,mcp__apra-fleet__code_impact,mcp__apra-fleet__code_query"`
|
|
36
|
-
|
|
37
|
+
<!-- else-tool: ToolSearch -->
|
|
38
|
+
1. No tool-discovery step is needed on this provider: every step below names the KB
|
|
39
|
+
tool it wants directly. Confirm your environment exposes those tools, then call
|
|
40
|
+
them as written.
|
|
41
|
+
<!-- end-tool: ToolSearch -->
|
|
42
|
+
Do not call `kb_list`/`kb_promote`/`kb_capture` directly -- captures and
|
|
37
43
|
promotions both go through your structured output, not a direct tool call; see
|
|
38
|
-
Step 5 for promotions and item 3 below for captures.
|
|
44
|
+
Step 5 for promotions and item 3 below for captures.
|
|
39
45
|
The `code_*` tools answer what the KB cannot: what the changed code actually connects
|
|
40
46
|
to. Use `code_impact` on each changed file to judge blast radius, and
|
|
41
47
|
`code_context`/`code_graph`/`code_query` to trace callers before accepting a signature
|
|
@@ -56,7 +62,12 @@ stating exactly which input is missing and `reopenIds: []`, `newTasks: []`.
|
|
|
56
62
|
directly with the entry id and what was wrong -- this is a read/feedback operation, not
|
|
57
63
|
a mutation, so it does not go through structured output.
|
|
58
64
|
|
|
65
|
+
<!-- if-tool: ToolSearch -->
|
|
59
66
|
If ToolSearch returns no KB tools (MCP server not running), skip these steps and proceed.
|
|
67
|
+
<!-- else-tool: ToolSearch -->
|
|
68
|
+
If those KB tools are not available in your environment (MCP server not running), skip
|
|
69
|
+
these steps and proceed.
|
|
70
|
+
<!-- end-tool: ToolSearch -->
|
|
60
71
|
|
|
61
72
|
## Step 1 -- Context recovery
|
|
62
73
|
|
|
@@ -14,6 +14,43 @@
|
|
|
14
14
|
"notes": {
|
|
15
15
|
"type": "string"
|
|
16
16
|
},
|
|
17
|
+
"findings": {
|
|
18
|
+
"type": "array",
|
|
19
|
+
"description": "Machine-readable per-bead findings: one entry per bead that must change, so a caller can route a CHANGES_NEEDED verdict without parsing notes. Populate on every CHANGES_NEEDED verdict. Return an empty array when the objection is genuinely plan-wide and names no individual bead -- an empty array is the explicit 'plan-wide' signal. Omit or return an empty array on APPROVED. Optional, and deliberately absent-tolerant for one release: a verdict produced against the previous contract still validates, and a caller may fall back to reading notes. notes stays the narration channel.",
|
|
20
|
+
"items": {
|
|
21
|
+
"type": "object",
|
|
22
|
+
"required": ["id", "kind", "detail"],
|
|
23
|
+
"properties": {
|
|
24
|
+
"id": {
|
|
25
|
+
"type": "string",
|
|
26
|
+
"description": "The bead this finding concerns, written exactly as it appears in taskAssignments (e.g. BD-14)."
|
|
27
|
+
},
|
|
28
|
+
"kind": {
|
|
29
|
+
"type": "string",
|
|
30
|
+
"description": "Which quality criterion failed, as a closed vocabulary mirroring the numbered criteria in the prose contract's Step 2. Use other only when no listed kind fits, and explain it in detail.",
|
|
31
|
+
"enum": [
|
|
32
|
+
"coverage",
|
|
33
|
+
"missing_test_task",
|
|
34
|
+
"acceptance_criteria",
|
|
35
|
+
"task_size",
|
|
36
|
+
"dependency_wiring",
|
|
37
|
+
"scope_creep",
|
|
38
|
+
"duplicate_work",
|
|
39
|
+
"feasibility",
|
|
40
|
+
"ready_work",
|
|
41
|
+
"model_metadata",
|
|
42
|
+
"lane_cohesion",
|
|
43
|
+
"other"
|
|
44
|
+
]
|
|
45
|
+
},
|
|
46
|
+
"detail": {
|
|
47
|
+
"type": "string",
|
|
48
|
+
"minLength": 1,
|
|
49
|
+
"description": "The human explanation for this bead: what is wrong and what would make it pass."
|
|
50
|
+
}
|
|
51
|
+
}
|
|
52
|
+
}
|
|
53
|
+
},
|
|
17
54
|
"taskAssignments": {
|
|
18
55
|
"type": "array",
|
|
19
56
|
"items": {
|
|
@@ -4,9 +4,90 @@
|
|
|
4
4
|
* Claude frontmatter: name, description, tools (comma/list)
|
|
5
5
|
* OpenCode frontmatter: description, mode: subagent, permission map (no name)
|
|
6
6
|
*
|
|
7
|
-
* NOTE:
|
|
8
|
-
*
|
|
7
|
+
* NOTE: packages/apra-fleet-se/apra-pm/install.mjs is NOT an npm workspace (see the
|
|
8
|
+
* comment at its own transformAgentForAgy/transformAgentForOpenCode) and carries its
|
|
9
|
+
* own copies of the following symbols from this file -- keep BOTH sides in sync
|
|
10
|
+
* whenever adding new tool mappings or frontmatter fields:
|
|
11
|
+
* - transformAgentForOpenCode
|
|
12
|
+
* - transformAgentForAgy
|
|
13
|
+
* - agyToolMap
|
|
14
|
+
* - OPENCODE_NATIVE_TOOLS
|
|
15
|
+
* - CONDITIONAL_MARKER_RE
|
|
16
|
+
* - resolveConditionalBody
|
|
17
|
+
* - toolAvailability
|
|
18
|
+
* - readFrontmatterTools
|
|
19
|
+
* tests/agent-transform-apra-pm-sync.test.ts guards ALL of the above, in three
|
|
20
|
+
* complementary ways:
|
|
21
|
+
* - SOURCE-TEXT guard: agyToolMap and OPENCODE_NATIVE_TOOLS are extracted from
|
|
22
|
+
* both files and compared as parsed values, so an edit to one literal
|
|
23
|
+
* without the other fails the suite.
|
|
24
|
+
* - BEHAVIOURAL guard (frontmatter-less): one shared fixture corpus (if/else,
|
|
25
|
+
* else-less if, nested, repeated, tool-present, tool-absent, plus the four
|
|
26
|
+
* malformed cases) is fed through BOTH implementations for agy and
|
|
27
|
+
* opencode, and the outputs must be byte-identical strings / the thrown
|
|
28
|
+
* MESSAGES must match. That drives CONDITIONAL_MARKER_RE,
|
|
29
|
+
* resolveConditionalBody and toolAvailability's `declared === null` branch
|
|
30
|
+
* transitively through the exported transform entry points -- none of
|
|
31
|
+
* those three is exported on either side, and the test does not widen
|
|
32
|
+
* exports to reach them.
|
|
33
|
+
* - BEHAVIOURAL guard (declared frontmatter tools, apra-fleet-oomh.15): a
|
|
34
|
+
* second fixture corpus adds real `tools:` frontmatter declarations --
|
|
35
|
+
* including `tools: [*]` -- so toolAvailability's INTERSECTION branch
|
|
36
|
+
* (the intersection of declared tools and provider-supported tools) and isWildcardTools() /
|
|
37
|
+
* install.mjs's inlined `declared.some(t => t === '*')` are also driven on
|
|
38
|
+
* both sides, alongside readFrontmatterTools. Because transformAgentForAgy/
|
|
39
|
+
* ForOpenCode also rewrite the frontmatter itself when one is present
|
|
40
|
+
* (unlike .mjs's resolveAgentConditionals, see below), each fixture body is
|
|
41
|
+
* wrapped in sentinel strings and outputs are compared only in the
|
|
42
|
+
* sentinel-delimited region -- this keeps the comparison scoped to marker
|
|
43
|
+
* resolution and inert to frontmatter-rewrite differences.
|
|
44
|
+
*
|
|
45
|
+
* Note the two structural asymmetries the test documents and works around: the
|
|
46
|
+
* .mjs body resolver is named resolveAgentConditionals (not
|
|
47
|
+
* resolveConditionalBody) and takes a provider string rather than a predicate,
|
|
48
|
+
* and the .mjs transformAgentForAgy/ForOpenCode do NOT resolve body markers
|
|
49
|
+
* (install() does that in a separate pass). The one residual gap after
|
|
50
|
+
* apra-fleet-oomh.15: drift in the frontmatter-REWRITING half of
|
|
51
|
+
* transformAgentForAgy/transformAgentForOpenCode (name/description echoing,
|
|
52
|
+
* Claude-name -> provider-tool-name mapping, the agy auto-approve rules block,
|
|
53
|
+
* opencode's permission map) is still unguarded by this suite -- update those
|
|
54
|
+
* by hand on both sides.
|
|
55
|
+
*/
|
|
56
|
+
/**
|
|
57
|
+
* Thrown when a conditional block is unclosed, unmatched, or mismatched. Surfaced
|
|
58
|
+
* at install time rather than swallowed -- see the note above.
|
|
59
|
+
*/
|
|
60
|
+
export declare class ConditionalMarkerError extends Error {
|
|
61
|
+
constructor(label: string, detail: string);
|
|
62
|
+
}
|
|
63
|
+
/**
|
|
64
|
+
* Resolve every conditional block in `text` against a tool-availability predicate.
|
|
65
|
+
*
|
|
66
|
+
* @param text any agent file content (frontmatter carries no markers)
|
|
67
|
+
* @param isAvailable answers "does this provider give the agent this tool?"
|
|
68
|
+
* @param label file label used in error messages
|
|
9
69
|
*/
|
|
70
|
+
export declare function resolveConditionalBody(text: string, isAvailable: (tool: string) => boolean, label: string): string;
|
|
71
|
+
/**
|
|
72
|
+
* OpenCode's native subagent toolset, in Claude tool names.
|
|
73
|
+
*
|
|
74
|
+
* transformAgentForOpenCode emits no `tools:` line at all (OpenCode grants its
|
|
75
|
+
* built-ins and gates the dangerous ones through the permission map), so unlike
|
|
76
|
+
* agy there is no emitted frontmatter to read availability back off. It has to be
|
|
77
|
+
* stated explicitly, and this is that statement: anything NOT listed here is
|
|
78
|
+
* unavailable under OpenCode and its prose is resolved to the else-branch.
|
|
79
|
+
*/
|
|
80
|
+
export declare const OPENCODE_NATIVE_TOOLS: string[];
|
|
10
81
|
export declare function transformAgentForOpenCode(content: string, _filename: string): string;
|
|
82
|
+
/**
|
|
83
|
+
* The Claude/raw install path. Claude reads the source frontmatter as-authored, so
|
|
84
|
+
* nothing is rewritten -- but the markers themselves must still be stripped, or they
|
|
85
|
+
* ship verbatim into the installed agent file. Every conditional keeps its if-branch,
|
|
86
|
+
* because for Claude the tool map is the identity map over the declared tools.
|
|
87
|
+
*
|
|
88
|
+
* Non-agent assets travel this path too (schemas/*.json, _shared/*.md); they carry no
|
|
89
|
+
* frontmatter and no markers, so they pass through untouched.
|
|
90
|
+
*/
|
|
91
|
+
export declare function transformAgentForClaude(content: string, filename: string): string;
|
|
11
92
|
export declare function transformAgentForAgy(content: string, _filename: string): string;
|
|
12
93
|
//# sourceMappingURL=agent-transform.d.ts.map
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"agent-transform.d.ts","sourceRoot":"","sources":["../../src/cli/agent-transform.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;
|
|
1
|
+
{"version":3,"file":"agent-transform.d.ts","sourceRoot":"","sources":["../../src/cli/agent-transform.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAsDG;AAgEH;;;GAGG;AACH,qBAAa,sBAAuB,SAAQ,KAAK;gBACnC,KAAK,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM;CAI1C;AAiBD;;;;;;GAMG;AACH,wBAAgB,sBAAsB,CACpC,IAAI,EAAE,MAAM,EACZ,WAAW,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,OAAO,EACtC,KAAK,EAAE,MAAM,GACZ,MAAM,CAkER;AAgBD;;;;;;;;GAQG;AACH,eAAO,MAAM,qBAAqB,UAA6D,CAAC;AAkDhG,wBAAgB,yBAAyB,CAAC,OAAO,EAAE,MAAM,EAAE,SAAS,EAAE,MAAM,GAAG,MAAM,CAmDpF;AAED;;;;;;;;GAQG;AACH,wBAAgB,uBAAuB,CAAC,OAAO,EAAE,MAAM,EAAE,QAAQ,EAAE,MAAM,GAAG,MAAM,CAGjF;AAaD,wBAAgB,oBAAoB,CAAC,OAAO,EAAE,MAAM,EAAE,SAAS,EAAE,MAAM,GAAG,MAAM,CA2G/E"}
|