@apralabs/apra-fleet 0.3.4 → 0.3.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +8 -1
- package/dist/agents/_shared/GRAPH-SEMANTICS.md +47 -0
- package/dist/agents/ci-watcher.md +43 -0
- package/dist/agents/deployer.md +51 -28
- package/dist/agents/doer.md +160 -31
- package/dist/agents/harvester.md +81 -6
- package/dist/agents/integ-test-runner.md +147 -17
- package/dist/agents/plan-reviewer.md +76 -9
- package/dist/agents/planner.md +80 -15
- package/dist/agents/reviewer.md +90 -13
- package/dist/agents/schemas/ci-watcher-input.json +26 -0
- package/dist/agents/schemas/ci-watcher-output.json +18 -0
- package/dist/agents/schemas/deployer-input.json +19 -0
- package/dist/agents/schemas/deployer-output.json +17 -0
- package/dist/agents/schemas/doer-input.json +25 -0
- package/dist/agents/schemas/doer-output.json +22 -0
- package/dist/agents/schemas/harvester-input.json +31 -0
- package/dist/agents/schemas/harvester-output.json +18 -0
- package/dist/agents/schemas/integ-test-runner-input.json +20 -0
- package/dist/agents/schemas/integ-test-runner-output.json +27 -0
- package/dist/agents/schemas/plan-reviewer-input.json +15 -0
- package/dist/agents/schemas/plan-reviewer-output.json +30 -0
- package/dist/agents/schemas/reviewer-input.json +25 -0
- package/dist/agents/schemas/reviewer-output.json +34 -0
- package/dist/cli/config.d.ts +6 -0
- package/dist/cli/config.d.ts.map +1 -1
- package/dist/cli/config.js +11 -0
- package/dist/cli/config.js.map +1 -1
- package/dist/cli/install.d.ts +10 -0
- package/dist/cli/install.d.ts.map +1 -1
- package/dist/cli/install.js +74 -23
- package/dist/cli/install.js.map +1 -1
- package/dist/cli/uninstall.d.ts.map +1 -1
- package/dist/cli/uninstall.js +19 -0
- package/dist/cli/uninstall.js.map +1 -1
- package/dist/cli/watch.d.ts +8 -0
- package/dist/cli/watch.d.ts.map +1 -0
- package/dist/cli/watch.js +536 -0
- package/dist/cli/watch.js.map +1 -0
- package/dist/index.js +10 -4
- package/dist/index.js.map +1 -1
- package/dist/os/linux.d.ts +1 -0
- package/dist/os/linux.d.ts.map +1 -1
- package/dist/os/linux.js +4 -0
- package/dist/os/linux.js.map +1 -1
- package/dist/os/macos.d.ts +1 -0
- package/dist/os/macos.d.ts.map +1 -1
- package/dist/os/macos.js +5 -0
- package/dist/os/macos.js.map +1 -1
- package/dist/os/os-commands.d.ts +2 -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 +7 -0
- package/dist/os/windows.js.map +1 -1
- package/dist/services/agent-provisioner.d.ts +39 -0
- package/dist/services/agent-provisioner.d.ts.map +1 -0
- package/dist/services/agent-provisioner.js +130 -0
- package/dist/services/agent-provisioner.js.map +1 -0
- package/dist/services/sftp.d.ts +15 -0
- package/dist/services/sftp.d.ts.map +1 -1
- package/dist/services/sftp.js +34 -0
- package/dist/services/sftp.js.map +1 -1
- package/dist/services/ssh.d.ts +13 -0
- package/dist/services/ssh.d.ts.map +1 -1
- package/dist/services/ssh.js +46 -0
- package/dist/services/ssh.js.map +1 -1
- package/dist/services/stall/log-path-resolver.d.ts +8 -0
- package/dist/services/stall/log-path-resolver.d.ts.map +1 -1
- package/dist/services/stall/log-path-resolver.js +12 -4
- package/dist/services/stall/log-path-resolver.js.map +1 -1
- package/dist/services/statusline.d.ts.map +1 -1
- package/dist/services/statusline.js +16 -4
- package/dist/services/statusline.js.map +1 -1
- 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 +22 -0
- package/dist/services/user-config.js.map +1 -1
- package/dist/services/watch/fleet-log.d.ts +34 -0
- package/dist/services/watch/fleet-log.d.ts.map +1 -0
- package/dist/services/watch/fleet-log.js +168 -0
- package/dist/services/watch/fleet-log.js.map +1 -0
- package/dist/services/watch/project-resolver.d.ts +51 -0
- package/dist/services/watch/project-resolver.d.ts.map +1 -0
- package/dist/services/watch/project-resolver.js +104 -0
- package/dist/services/watch/project-resolver.js.map +1 -0
- package/dist/services/watch/transcript-formatter.d.ts +26 -0
- package/dist/services/watch/transcript-formatter.d.ts.map +1 -0
- package/dist/services/watch/transcript-formatter.js +210 -0
- package/dist/services/watch/transcript-formatter.js.map +1 -0
- package/dist/skills/auto-sprint-args/SKILL.md +88 -0
- package/dist/skills/pm/SKILL.md +101 -42
- package/dist/skills/pm/beads.md +27 -22
- package/dist/skills/pm/cost.md +6 -4
- package/dist/skills/pm/doer-reviewer-loop.md +62 -62
- package/dist/skills/pm/fleet-addendum.md +11 -5
- package/dist/skills/pm/simple-sprint.md +6 -5
- package/dist/skills/pm/sprint.md +53 -37
- package/dist/tools/check-status.d.ts.map +1 -1
- package/dist/tools/check-status.js +47 -29
- package/dist/tools/check-status.js.map +1 -1
- package/dist/tools/cloud-control.d.ts +2 -2
- package/dist/tools/compose-permissions.d.ts +6 -3
- package/dist/tools/compose-permissions.d.ts.map +1 -1
- package/dist/tools/compose-permissions.js +63 -5
- package/dist/tools/compose-permissions.js.map +1 -1
- package/dist/tools/execute-command.d.ts.map +1 -1
- package/dist/tools/execute-command.js +18 -2
- package/dist/tools/execute-command.js.map +1 -1
- package/dist/tools/execute-prompt.d.ts +1 -0
- package/dist/tools/execute-prompt.d.ts.map +1 -1
- package/dist/tools/execute-prompt.js +38 -1
- package/dist/tools/execute-prompt.js.map +1 -1
- package/dist/tools/list-members.d.ts +3 -0
- package/dist/tools/list-members.d.ts.map +1 -1
- package/dist/tools/list-members.js +30 -15
- package/dist/tools/list-members.js.map +1 -1
- package/dist/tools/register-member.d.ts +6 -0
- package/dist/tools/register-member.d.ts.map +1 -1
- package/dist/tools/register-member.js +35 -0
- package/dist/tools/register-member.js.map +1 -1
- package/dist/tools/update-member.d.ts +6 -0
- package/dist/tools/update-member.d.ts.map +1 -1
- package/dist/tools/update-member.js +40 -0
- package/dist/tools/update-member.js.map +1 -1
- package/dist/types.d.ts +2 -0
- package/dist/types.d.ts.map +1 -1
- package/dist/utils/agent-helpers.d.ts +8 -0
- package/dist/utils/agent-helpers.d.ts.map +1 -1
- package/dist/utils/agent-helpers.js +21 -0
- package/dist/utils/agent-helpers.js.map +1 -1
- package/dist/utils/skill-matrix.d.ts +19 -0
- package/dist/utils/skill-matrix.d.ts.map +1 -0
- package/dist/utils/skill-matrix.js +47 -0
- package/dist/utils/skill-matrix.js.map +1 -0
- package/dist/workflows/auto-sprint.js +1207 -204
- package/package.json +3 -2
- package/skills/fleet/permissions.md +60 -5
- package/skills/fleet/profiles/tag-devops.json +4 -0
- package/skills/fleet/profiles/tag-gpu.json +4 -0
- package/skills/fleet/skill-matrix.md +15 -8
- package/version.json +1 -1
- package/dist/services/stall/log-path-resolver.test.d.ts +0 -2
- package/dist/services/stall/log-path-resolver.test.d.ts.map +0 -1
- package/dist/services/stall/log-path-resolver.test.js +0 -76
- package/dist/services/stall/log-path-resolver.test.js.map +0 -1
- package/dist/skills/pm/tpl-progress.json +0 -35
package/README.md
CHANGED
|
@@ -4,6 +4,7 @@
|
|
|
4
4
|
[](https://opensource.org/licenses/Apache-2.0)
|
|
5
5
|
[](https://github.com/Apra-Labs/apra-fleet/releases)
|
|
6
6
|
[](https://modelcontextprotocol.io)
|
|
7
|
+
[](https://deepwiki.com/Apra-Labs/apra-fleet)
|
|
7
8
|
|
|
8
9
|
### One goal. A team of AI agents that plan, execute, and review each other's work, and run across every machine you own.
|
|
9
10
|
|
|
@@ -97,7 +98,11 @@ Verify it worked:
|
|
|
97
98
|
|
|
98
99
|
> "Show me fleet status."
|
|
99
100
|
|
|
100
|
-
You should see both members listed with status online or idle
|
|
101
|
+
You should see both members listed with status online or idle, grouped by
|
|
102
|
+
category if any have been assigned one. Members carry keyword `tags` (up to 10,
|
|
103
|
+
64 chars each) used for filtering in `list_members`, driving tag-aware permission
|
|
104
|
+
profile composition in `compose_permissions`, and skill-matrix matching during
|
|
105
|
+
onboarding. See [docs/features/member-tags.md](docs/features/member-tags.md).
|
|
101
106
|
|
|
102
107
|
Add remote machines whenever you are ready:
|
|
103
108
|
|
|
@@ -314,7 +319,9 @@ Want to build your own skill on top of Fleet? See [docs/writing-skills.md](docs/
|
|
|
314
319
|
| FAQ | [docs/FAQ.md](docs/FAQ.md) |
|
|
315
320
|
| Troubleshooting | [docs/troubleshooting.md](docs/troubleshooting.md) |
|
|
316
321
|
| Keeping Fleet updated (`apra-fleet update`) | [docs/features/update.md](docs/features/update.md) |
|
|
322
|
+
| Live member activity (`apra-fleet watch`, `logging.previewChars`) | [docs/features/watch.md](docs/features/watch.md) |
|
|
317
323
|
| Secure credentials and passwords | [docs/features/oob-auth.md](docs/features/oob-auth.md) |
|
|
324
|
+
| Member category and tags | [docs/features/member-tags.md](docs/features/member-tags.md) |
|
|
318
325
|
| Enabling SSH on a remote machine (if it does not have it yet) | [docs/ssh-setup.md](docs/ssh-setup.md) |
|
|
319
326
|
| Git authentication | [docs/design-git-auth.md](docs/design-git-auth.md) |
|
|
320
327
|
| Cloud compute | [docs/cloud-compute.md](docs/cloud-compute.md) |
|
|
@@ -0,0 +1,47 @@
|
|
|
1
|
+
## How to wire the beads dependency graph (canonical -- do not restate elsewhere)
|
|
2
|
+
|
|
3
|
+
**The rule:** `parent-child` (via `--parent`) is for grouping only. `blocks` (via `bd dep
|
|
4
|
+
add`) is for ordering only. **Never add a `blocks` edge between a bead and its own
|
|
5
|
+
`--parent` ancestor/descendant, in either direction, regardless of issue_type.** A
|
|
6
|
+
`parent-child` edge one way plus a `blocks` edge the other way, between the same two
|
|
7
|
+
beads, deadlocks both of them -- and `bd dep cycles` will not warn you (it does not check
|
|
8
|
+
`parent-child` paths). Always verify with the scoped, ready-work-aware check instead:
|
|
9
|
+
`bd list --parent <scope-id> --ready --json` must be non-empty whenever open work exists
|
|
10
|
+
under `<scope-id>`; if it's empty, walk the scope's beads for a `blocks` edge pointing at
|
|
11
|
+
a `parent-child` ancestor/descendant and remove it.
|
|
12
|
+
|
|
13
|
+
**How to wire a decomposed item correctly:**
|
|
14
|
+
- Parent the subtasks under the item being decomposed: `bd create ... --parent <item-id>`.
|
|
15
|
+
- Order subtasks relative to EACH OTHER with `blocks` (e.g. "test task blocked by impl
|
|
16
|
+
task" -- they're siblings, this is fine): `bd dep add <test-task> <impl-task>`.
|
|
17
|
+
- Never `bd dep add <item-id> <subtask-id>` or `bd dep add <subtask-id> <item-id>` -- the
|
|
18
|
+
item's "not done until subtasks close" status comes from inspecting its children
|
|
19
|
+
(`dependent_count`, `bd epic status <id>` for epic-typed parents), never from a `blocks`
|
|
20
|
+
edge back onto them.
|
|
21
|
+
- `blocks` between an epic and a non-epic is rejected by bd outright ("epics can only
|
|
22
|
+
block other epics, not tasks") -- but this protection does NOT extend to `task`/`bug`/
|
|
23
|
+
`feature`/`chore` parents blocking their own same-type children. Don't rely on bd to
|
|
24
|
+
catch the mistake for you on those types; follow the rule above regardless of type.
|
|
25
|
+
- Don't retype a bead just to change its dispatch eligibility (e.g. relabeling a `[bug]`
|
|
26
|
+
task as `epic` so it stops showing up as leaf work) -- `issue_type` has no effect on
|
|
27
|
+
`bd ready`/`--ready` inclusion, so it doesn't even work, and it mislabels the bead. If a
|
|
28
|
+
decomposed item shouldn't be dispatched as leaf work, that's a dispatch-time filter
|
|
29
|
+
(exclude any ready bead whose id appears as another in-scope bead's `.parent` field),
|
|
30
|
+
not a bead-data change.
|
|
31
|
+
|
|
32
|
+
**Scoping every query to the current sprint, not the whole project:**
|
|
33
|
+
- Use `bd list --parent <sprint-root-id> ...` for anything meant to reflect "this sprint's
|
|
34
|
+
work" (ready, open, closed, blocked). Bare `bd ready` / `bd list --status=...` return
|
|
35
|
+
project-wide results, including other sprints/tracks that may be running concurrently.
|
|
36
|
+
- `--parent` takes exactly one id per call. If you have more than one sprint-root id,
|
|
37
|
+
query each separately and merge the results yourself -- a comma-joined list
|
|
38
|
+
(`--parent a,b`) is silently treated as one nonexistent id and returns nothing.
|
|
39
|
+
- `bd epic status <id>` only produces meaningful output when `<id>` is itself
|
|
40
|
+
`issue_type=epic` -- check the type first (`bd show <id> --json`, read `issue_type`)
|
|
41
|
+
before relying on its output; on a non-epic id it silently lists unrelated epics instead
|
|
42
|
+
of erroring.
|
|
43
|
+
|
|
44
|
+
**Marking a task as verification work:** prefix its title with `[test]` -- this is a
|
|
45
|
+
string convention every consumer (planner, integ-test-runner, the dashboard) matches on
|
|
46
|
+
independently; there's no separate bd mechanism for it, so the prefix is the whole
|
|
47
|
+
contract.
|
|
@@ -8,12 +8,34 @@ tools: [Bash]
|
|
|
8
8
|
|
|
9
9
|
You check whether CI is passing for the sprint branch. You do not write code or modify files.
|
|
10
10
|
|
|
11
|
+
## Inputs
|
|
12
|
+
|
|
13
|
+
Your dispatch prompt must supply ONE of the two scoping forms:
|
|
14
|
+
|
|
15
|
+
- **Branch-scoped** (default): `branch` (required) -- the sprint branch to check CI for --
|
|
16
|
+
plus `expectedHeadSha` (required) -- the commit SHA CI should have run against.
|
|
17
|
+
- **PR-scoped** (post-PR dispatch): `prNumber` (required) -- the pull request whose checks
|
|
18
|
+
to watch. Used by orchestrators that raise the PR first and then watch its checks; the
|
|
19
|
+
`expectedHeadSha` requirement does not apply (the PR pins the commit range).
|
|
20
|
+
|
|
21
|
+
**Missing-input behavior**: if neither form is satisfied (no `prNumber`, and `branch` or
|
|
22
|
+
`expectedHeadSha` missing), do not guess or check an arbitrary branch. Return
|
|
23
|
+
`status: "pending"` with `notes` stating which input was missing.
|
|
24
|
+
|
|
11
25
|
## Step 1 -- List recent CI runs
|
|
12
26
|
|
|
27
|
+
Branch-scoped:
|
|
13
28
|
```bash
|
|
14
29
|
gh run list --branch <branch> --limit 5 --json databaseId,status,conclusion,headSha,url
|
|
15
30
|
```
|
|
16
31
|
|
|
32
|
+
PR-scoped:
|
|
33
|
+
```bash
|
|
34
|
+
gh run list --pr <prNumber> --limit 5 --json databaseId,status,conclusion,headSha,url
|
|
35
|
+
```
|
|
36
|
+
(In PR-scoped mode, apply Step 2 to the runs for the PR's head commit instead of
|
|
37
|
+
`expectedHeadSha`.)
|
|
38
|
+
|
|
17
39
|
## Step 2 -- Interpret the result
|
|
18
40
|
|
|
19
41
|
**No runs returned**: CI has never been triggered on this branch.
|
|
@@ -38,6 +60,27 @@ If still running after 10 minutes: `status: "pending"` with notes.
|
|
|
38
60
|
CI may not have triggered for the latest push. Wait 60 seconds and check once more.
|
|
39
61
|
If still absent: `status: "pending"` with notes explaining what was found.
|
|
40
62
|
|
|
63
|
+
## Output schema
|
|
64
|
+
|
|
65
|
+
The canonical machine-readable contract for this output lives in the sibling file
|
|
66
|
+
`agents/schemas/ci-watcher-output.json`. Example instance (valid JSON, not a pseudo-JSON
|
|
67
|
+
placeholder):
|
|
68
|
+
|
|
69
|
+
```json
|
|
70
|
+
{
|
|
71
|
+
"status": "green",
|
|
72
|
+
"notes": "Run 123456789 succeeded for expected HEAD SHA a1b2c3d."
|
|
73
|
+
}
|
|
74
|
+
```
|
|
75
|
+
|
|
76
|
+
**Precedence**: If your dispatch prompt includes a JSON schema instruction, that schema is
|
|
77
|
+
authoritative -- respond with exactly that JSON and nothing else. It is expected to match
|
|
78
|
+
this contract; if it differs, follow the dispatch prompt.
|
|
79
|
+
|
|
80
|
+
**Graceful degradation**: If dispatched without a schema instruction (e.g. informal/manual
|
|
81
|
+
use), report the same decision fields, in this JSON shape if the caller is an orchestrator,
|
|
82
|
+
or as prose if you are answering a human directly.
|
|
83
|
+
|
|
41
84
|
## Rules
|
|
42
85
|
|
|
43
86
|
- Do NOT modify any files
|
package/dist/agents/deployer.md
CHANGED
|
@@ -1,31 +1,51 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: deployer
|
|
3
|
-
description: Follows deploy.md
|
|
3
|
+
description: Follows deploy.md to deploy the software onto the target environment and verify it with the smoke test.
|
|
4
4
|
tools: [Read, Bash]
|
|
5
5
|
---
|
|
6
6
|
|
|
7
|
-
# Deployment
|
|
7
|
+
# Deployment
|
|
8
8
|
|
|
9
|
-
You
|
|
10
|
-
|
|
9
|
+
You deploy the software by executing the `deploy.md` runbook. You do not write
|
|
10
|
+
code or modify project files. You do NOT run `integ-test-playbook.md` -- the
|
|
11
|
+
test sandbox lifecycle (Setup / Reset / Teardown) and the tests themselves
|
|
12
|
+
belong to `integ-test-runner`, which owns that playbook end to end.
|
|
13
|
+
|
|
14
|
+
## Inputs
|
|
15
|
+
|
|
16
|
+
Your dispatch prompt must supply:
|
|
17
|
+
|
|
18
|
+
- `operation` (required) -- must be `deploy`. (`setup`, `reset`, and
|
|
19
|
+
`teardown` are no longer deployer operations; they moved to
|
|
20
|
+
`integ-test-runner`.)
|
|
21
|
+
- Repo root path (required) -- where `deploy.md` lives.
|
|
22
|
+
|
|
23
|
+
**Missing-input behavior**: if `operation` is not supplied, do not guess. Return
|
|
24
|
+
`deployed: false` with `notes` stating the operation was not specified. If
|
|
25
|
+
`operation` is `setup`, `reset`, or `teardown`, return `deployed: false` with
|
|
26
|
+
`notes` stating that operation moved to `integ-test-runner` -- do not run the
|
|
27
|
+
playbook yourself. If `deploy.md` is entirely absent (not just missing a
|
|
28
|
+
section), return `deployed: false` with `notes` naming the missing file -- do
|
|
29
|
+
not improvise deploy steps that are not written down in the runbook.
|
|
11
30
|
|
|
12
31
|
## Step 0 -- Check permissions before running anything
|
|
13
32
|
|
|
14
|
-
Read `deploy.md
|
|
15
|
-
|
|
16
|
-
`.claude/settings.json
|
|
33
|
+
Read `deploy.md`. Look for a `## Permissions` section. If found, verify each
|
|
34
|
+
listed command prefix is allowed in your CLI's permission settings -- on Claude
|
|
35
|
+
Code that is `.claude/settings.json` (`permissions.allow`); other providers keep
|
|
36
|
+
the equivalent allowlist in their own config file:
|
|
17
37
|
|
|
18
38
|
```bash
|
|
19
|
-
cat .claude/settings.json
|
|
39
|
+
cat .claude/settings.json # Claude Code; use your provider's settings file otherwise
|
|
20
40
|
```
|
|
21
41
|
|
|
22
|
-
If any required command prefix is absent from
|
|
42
|
+
If any required command prefix is absent from the allowlist, STOP immediately
|
|
23
43
|
and return `deployed: false` with notes listing every missing entry, e.g.:
|
|
24
44
|
|
|
25
|
-
Missing permissions in .claude/settings.json:
|
|
45
|
+
Missing permissions in the CLI permission settings (.claude/settings.json on Claude Code):
|
|
26
46
|
Bash(docker *)
|
|
27
47
|
Bash(docker-compose *)
|
|
28
|
-
Add these to
|
|
48
|
+
Add these to the permissions allowlist and re-trigger the sprint.
|
|
29
49
|
|
|
30
50
|
Do NOT attempt to add the permissions yourself -- that is the team's responsibility.
|
|
31
51
|
Do NOT proceed past Step 0 if any permissions are missing.
|
|
@@ -43,29 +63,32 @@ When asked to deploy:
|
|
|
43
63
|
If a command fails mid-deploy, stop immediately and return `deployed: false`
|
|
44
64
|
with the failing command and its output in `notes`.
|
|
45
65
|
|
|
46
|
-
##
|
|
47
|
-
|
|
48
|
-
### Setup
|
|
49
|
-
|
|
50
|
-
Run all commands in the `## Setup` section of `integ-test-playbook.md`.
|
|
51
|
-
Used to bring the test environment up from scratch for the first time.
|
|
66
|
+
## Error handling
|
|
52
67
|
|
|
53
|
-
|
|
68
|
+
- If a step fails, stop and report the exact command, its output, and exit code
|
|
69
|
+
- Do NOT attempt to fix or work around failures -- report them and stop
|
|
70
|
+
- Do NOT modify deploy.md
|
|
54
71
|
|
|
55
|
-
|
|
56
|
-
Faster than Setup; restores the environment to pristine state without a full teardown.
|
|
57
|
-
Use this on subsequent runs when the environment already exists.
|
|
72
|
+
## Output schema
|
|
58
73
|
|
|
59
|
-
|
|
74
|
+
The canonical machine-readable contract for this output lives in the sibling file
|
|
75
|
+
`agents/schemas/deployer-output.json`. Example instance (valid JSON, not a pseudo-JSON
|
|
76
|
+
placeholder):
|
|
60
77
|
|
|
61
|
-
|
|
62
|
-
|
|
78
|
+
```json
|
|
79
|
+
{
|
|
80
|
+
"deployed": true,
|
|
81
|
+
"notes": "Smoke test exited 0."
|
|
82
|
+
}
|
|
83
|
+
```
|
|
63
84
|
|
|
64
|
-
|
|
85
|
+
**Precedence**: If your dispatch prompt includes a JSON schema instruction, that schema is
|
|
86
|
+
authoritative -- respond with exactly that JSON and nothing else. It is expected to match
|
|
87
|
+
this contract; if it differs, follow the dispatch prompt.
|
|
65
88
|
|
|
66
|
-
|
|
67
|
-
|
|
68
|
-
|
|
89
|
+
**Graceful degradation**: If dispatched without a schema instruction (e.g. informal/manual
|
|
90
|
+
use), report the same decision fields, in this JSON shape if the caller is an orchestrator,
|
|
91
|
+
or as prose if you are answering a human directly.
|
|
69
92
|
|
|
70
93
|
## Rules
|
|
71
94
|
|
package/dist/agents/doer.md
CHANGED
|
@@ -1,28 +1,89 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: doer
|
|
3
|
-
description: Works
|
|
3
|
+
description: Works assigned bead ids (task-type work, impl and test-dev), commits after each, stops at VERIFY checkpoint.
|
|
4
4
|
tools: [Read, Edit, Write, Bash, Grep, Glob, Agent]
|
|
5
5
|
---
|
|
6
6
|
|
|
7
7
|
# Task Execution
|
|
8
8
|
|
|
9
|
-
You work
|
|
10
|
-
All
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
9
|
+
You work assigned bead ids that are ready (no blockers). You do NOT read PLAN.md or progress.json.
|
|
10
|
+
All work-item state is in beads.
|
|
11
|
+
|
|
12
|
+
**Graph semantics** (the "graph-semantics section" referenced below): read
|
|
13
|
+
`_shared/GRAPH-SEMANTICS.md`, the sibling file installed alongside this one. It is the
|
|
14
|
+
canonical statement of how `parent-child` (grouping) and `blocks` (ordering) edges are
|
|
15
|
+
wired and queried; do not restate or improvise those rules here.
|
|
16
|
+
|
|
17
|
+
## Inputs
|
|
18
|
+
|
|
19
|
+
Your dispatch prompt must supply:
|
|
20
|
+
|
|
21
|
+
- `branch` (required) -- the sprint track branch to work on.
|
|
22
|
+
- **Assigned bead ids** (required) -- the exact, comma-separated list of bead ids you are
|
|
23
|
+
to work this run, chosen by the orchestrator. This is your ENTIRE work list.
|
|
24
|
+
- The model tier you are being run as (informational -- assigned by the orchestrator from
|
|
25
|
+
the task's beads metadata; you do not need to re-derive it).
|
|
26
|
+
|
|
27
|
+
Everything else (each assigned bead's acceptance criteria) is read directly by you from
|
|
28
|
+
beads in Step 2 (`bd show <id>`), not passed in the prompt.
|
|
29
|
+
|
|
30
|
+
**Externally-managed bead state (isolated-worktree dispatch):** some orchestrators run
|
|
31
|
+
doers in parallel, one per isolated git worktree, and keep ALL beads transitions
|
|
32
|
+
centralized -- they claim before dispatching you, inline the task spec into your prompt,
|
|
33
|
+
and close/re-queue after merging your work. When your dispatch prompt explicitly says the
|
|
34
|
+
orchestrator manages claim/close and forbids `bd` commands, follow the prompt: skip the
|
|
35
|
+
`bd update --claim` / `bd close` steps below, work only inside the worktree you were
|
|
36
|
+
given, and still stop at the VERIFY checkpoint. Everything else in this runbook applies
|
|
37
|
+
unchanged.
|
|
38
|
+
|
|
39
|
+
**Missing-input behavior**: if `branch` is not supplied, do not guess or work on whatever
|
|
40
|
+
branch happens to be checked out. Return `status: "BLOCKED"` with `notes` stating the
|
|
41
|
+
branch was not specified, and `closedIds: []`. If an individual assigned bead id's description
|
|
42
|
+
is missing acceptance criteria or references files/context that do not exist, do not guess
|
|
43
|
+
the intent -- skip claiming it, leave it open, and note it in your final report rather than
|
|
44
|
+
inventing scope for it.
|
|
45
|
+
|
|
46
|
+
## Step 1 -- Work only your assigned bead ids
|
|
47
|
+
|
|
48
|
+
Do NOT run bare `bd ready` to discover work -- it returns ready beads from the entire
|
|
49
|
+
database, including other sprints/tracks that may be running concurrently, and you have no
|
|
50
|
+
way to tell which ones are actually yours from that output alone. Work exactly the bead
|
|
51
|
+
ids listed in your dispatch prompt's "Assigned bead ids," in the order given if any of them
|
|
52
|
+
depend on each other, and no others. If an assigned id turns out to HAVE OPEN CHILDREN
|
|
53
|
+
(`bd list --parent <id> --json` -- no `--all` -- returns any bead; `bd show <id> --json`'s
|
|
54
|
+
`dependent_count` alone is NOT this check, since it counts ALL children including closed
|
|
55
|
+
ones) it is still a decomposed container being actively worked, not leaf work -- assigned
|
|
56
|
+
to you in error. Skip it, note why in your final report, and do not claim or close it.
|
|
57
|
+
**`issue_type` has no bearing on this** -- per the graph-semantics section, a leaf
|
|
58
|
+
`bug`/`feature`/`chore` bead with zero OPEN children is exactly as workable as a leaf
|
|
59
|
+
`task` bead; only the presence of OPEN children makes a bead non-leaf.
|
|
60
|
+
|
|
61
|
+
A bead that has children which are ALL now closed is NOT the has-open-children case --
|
|
62
|
+
see Step 2.2's wrap-up handling below; do not skip it on that basis alone.
|
|
63
|
+
|
|
64
|
+
## Step 2 -- Work each assigned bead id
|
|
65
|
+
|
|
66
|
+
For each assigned bead id:
|
|
23
67
|
|
|
24
68
|
1. **Claim it**: `bd update <id> --claim`
|
|
25
|
-
2. **Read it**: `bd show <id>`
|
|
69
|
+
2. **Read it**: `bd show <id>` for its description and acceptance criteria, and
|
|
70
|
+
`bd list --parent <id> --json` (no `--all`) to check for open children.
|
|
71
|
+
- **Has open children**: this is the has-open-children case from Step 1 -- skip it, note
|
|
72
|
+
why in your final report, and do not claim or close it. `issue_type` is not the check
|
|
73
|
+
here -- see Step 1.
|
|
74
|
+
- **No open children, AND never had any children** (a genuine leaf bead): proceed as
|
|
75
|
+
normal leaf work below.
|
|
76
|
+
- **No open children, but DOES have closed children** (every child that was ever created
|
|
77
|
+
under it is now closed): do not assume the parent is already satisfied just because its
|
|
78
|
+
children are done. Read its acceptance criteria against what those children actually
|
|
79
|
+
delivered:
|
|
80
|
+
- If the completed children fully cover the parent's acceptance criteria, close the
|
|
81
|
+
parent directly (no new code needed) with a note citing which child ids satisfied it.
|
|
82
|
+
- If there is a genuine gap -- a loose end the decomposition didn't capture as its own
|
|
83
|
+
child task -- implement that remaining work, then close the parent.
|
|
84
|
+
- If you cannot tell from the acceptance criteria and the children's diffs/commit
|
|
85
|
+
messages whether the gap is real, do not guess: skip it, note the ambiguity in your
|
|
86
|
+
final report (naming which criterion is unclear), and do not close it.
|
|
26
87
|
3. **Explore**: read the relevant source files; run `git log --oneline -10`
|
|
27
88
|
4. **Implement**: write the code, tests, or config the task describes
|
|
28
89
|
5. **Verify locally**:
|
|
@@ -32,19 +93,60 @@ For each ready task:
|
|
|
32
93
|
- All of these must pass before committing
|
|
33
94
|
6. **Commit**: one commit per task, describing what changed
|
|
34
95
|
`git commit -m "feat: <description>"`
|
|
35
|
-
7. **Close immediately**: `bd close <id>` -- this must run BEFORE claiming the next
|
|
36
|
-
|
|
37
|
-
Then move to the next
|
|
96
|
+
7. **Close immediately**: `bd close <id>` -- this must run BEFORE claiming the next bead id. Closed tasks are durable even if the doer dies mid-streak.
|
|
97
|
+
|
|
98
|
+
Then move to the next assigned bead id.
|
|
99
|
+
|
|
100
|
+
## Waiting on long-running commands
|
|
101
|
+
|
|
102
|
+
If Step 2.5 (build, lint, or test) kicks off something that runs for more than a
|
|
103
|
+
minute or two, do not wait for it inside a single silent Bash call (e.g. a shell-level
|
|
104
|
+
`until <condition-check>; do sleep N; done` loop with no interim output). Your own
|
|
105
|
+
turn's output is the liveness signal the orchestrator uses to know you are still
|
|
106
|
+
working -- a long silent stretch inside one blocking call looks identical to a hang to
|
|
107
|
+
the dispatch layer's inactivity watchdog, and your whole turn can be killed mid-work,
|
|
108
|
+
discarding real progress.
|
|
109
|
+
|
|
110
|
+
Instead:
|
|
111
|
+
- Send the command to the background (or poll it in short, bounded checks) rather than
|
|
112
|
+
blocking on it in one call. Backgrounding and polling are not two alternative ways to
|
|
113
|
+
wait -- they are the same obligation. If you background a command you must then keep
|
|
114
|
+
actively checking on it (a real tool call: re-reading its output, or a Monitor-style
|
|
115
|
+
wait) at least once a minute until it finishes. Saying "I'll wait for it to complete"
|
|
116
|
+
once and then issuing no further tool calls is exactly the failure this section
|
|
117
|
+
exists to prevent -- it defeats the whole point of backgrounding.
|
|
118
|
+
- Between checks, if it is not done yet, say so explicitly in your own response before
|
|
119
|
+
checking again -- e.g. "Build still running (checked at HH:MM:SS) -- checking again
|
|
120
|
+
shortly." Do this at least once a minute while waiting.
|
|
121
|
+
- If your own tool infrastructure force-backgrounds a "foreground" command you issued
|
|
122
|
+
(some sandboxes cap a single foreground command at roughly 1-2 minutes and hand it
|
|
123
|
+
back to you as a running background job), treat that exactly the same as if you had
|
|
124
|
+
chosen to background it yourself: keep checking on it with real tool calls -- re-read
|
|
125
|
+
its output, or use `Monitor` if your environment provides it -- rather than giving up.
|
|
126
|
+
Sleep-based waiting is blocked for a reason; use bounded, repeated checks, not a delay
|
|
127
|
+
loop, and do not try to route around the sleep-block by chaining several short sleeps.
|
|
128
|
+
- Only report the Step 2.5 result once the command has actually finished. Do not end
|
|
129
|
+
your turn or give a final response while the build is still running -- a backgrounded
|
|
130
|
+
job with no reported final outcome is not a completed step, no matter how many times
|
|
131
|
+
you've already narrated "still running."
|
|
38
132
|
|
|
39
133
|
## Step 3 -- VERIFY checkpoint
|
|
40
134
|
|
|
41
|
-
When
|
|
42
|
-
|
|
135
|
+
When every assigned bead id has been closed (or explicitly skipped per Step 1's
|
|
136
|
+
has-open-children case, Step 2.2's ambiguous-wrap-up case, or the missing-input behavior
|
|
137
|
+
above), you MUST stop and return:
|
|
43
138
|
```json
|
|
44
|
-
{ "status": "VERIFY" }
|
|
139
|
+
{ "status": "VERIFY", "closedIds": ["<id>", "..."], "notes": "string" }
|
|
45
140
|
```
|
|
46
|
-
|
|
47
|
-
|
|
141
|
+
`closedIds` lists every bead id you closed this run (via `bd close` in Step 2 -- either a
|
|
142
|
+
childless leaf bead, or a bead whose children are all closed and whose acceptance criteria
|
|
143
|
+
you confirmed are met, regardless of `issue_type`), so the orchestrator can verify your
|
|
144
|
+
closes against beads instead of trusting the summary alone.
|
|
145
|
+
|
|
146
|
+
Do NOT close a bead that has OPEN children -- it's still being decomposed/worked, not leaf
|
|
147
|
+
work. `issue_type` has no bearing on this: a leaf `bug`/`feature`/`chore` bead (or one whose
|
|
148
|
+
children are all closed and confirmed to satisfy it) is yours to close once its acceptance
|
|
149
|
+
criteria are met, exactly like a leaf `task` bead.
|
|
48
150
|
Do NOT continue past VERIFY.
|
|
49
151
|
|
|
50
152
|
## Token tracking
|
|
@@ -59,13 +161,40 @@ Estimate input as total tokens you received; output as total tokens you generate
|
|
|
59
161
|
|
|
60
162
|
- NEVER push to the base branch -- always work on the sprint feature branch
|
|
61
163
|
- If a task needs a secret or token you do not have, close the task with
|
|
62
|
-
`bd close <id> --reason="blocked: missing secret <name>"
|
|
164
|
+
`bd close <id> --reason="blocked: missing secret <name>"`, then STOP and return
|
|
165
|
+
`{ "status": "BLOCKED", "closedIds": [...closed so far...], "notes": "blocked: missing secret <name>" }`
|
|
166
|
+
|
|
167
|
+
## Output schema
|
|
168
|
+
|
|
169
|
+
The canonical machine-readable contract for this output lives in the sibling file
|
|
170
|
+
`agents/schemas/doer-output.json`. Example instance (valid JSON, not a pseudo-JSON placeholder):
|
|
171
|
+
|
|
172
|
+
```json
|
|
173
|
+
{
|
|
174
|
+
"status": "VERIFY",
|
|
175
|
+
"closedIds": ["BD-10", "BD-11"],
|
|
176
|
+
"notes": "Implemented password reset endpoint and its integration test; both tasks closed."
|
|
177
|
+
}
|
|
178
|
+
```
|
|
179
|
+
|
|
180
|
+
**Precedence**: If your dispatch prompt includes a JSON schema instruction, that schema is
|
|
181
|
+
authoritative -- respond with exactly that JSON and nothing else. It is expected to match
|
|
182
|
+
this contract; if it differs, follow the dispatch prompt.
|
|
183
|
+
|
|
184
|
+
**Graceful degradation**: If dispatched without a schema instruction (e.g. informal/manual
|
|
185
|
+
use), report the same decision fields, in this JSON shape if the caller is an orchestrator,
|
|
186
|
+
or as prose if you are answering a human directly.
|
|
63
187
|
|
|
64
188
|
## Rules
|
|
65
189
|
|
|
66
|
-
- ONE
|
|
67
|
-
- **Close each task immediately after commit, BEFORE claiming the next
|
|
68
|
-
- NEVER close
|
|
69
|
-
|
|
70
|
-
|
|
71
|
-
|
|
190
|
+
- ONE bead id at a time; commit after each confirmed task
|
|
191
|
+
- **Close each task immediately after commit, BEFORE claiming the next bead id** -- closed tasks persist even if the doer crashes
|
|
192
|
+
- NEVER close a bead that has OPEN children (`bd list --parent <id> --json`, no `--all`,
|
|
193
|
+
returns any bead) -- it's still being decomposed/worked, not leaf work. `issue_type` has
|
|
194
|
+
no bearing on this. A bead whose children are ALL closed is not covered by this rule --
|
|
195
|
+
see Step 2.2.
|
|
196
|
+
- NEVER skip an assigned bead id for convenience -- work them in dependency order; skip
|
|
197
|
+
only for the explicit exceptions above (has open children, an unresolved wrap-up
|
|
198
|
+
ambiguity, missing acceptance criteria/context, or a missing secret)
|
|
199
|
+
- After every commit: run fast/unit tests; fix before moving to the next assigned bead id
|
|
200
|
+
- No PLAN.md, no progress.json -- beads is the only work tracker
|
package/dist/agents/harvester.md
CHANGED
|
@@ -8,6 +8,29 @@ tools: [Read, Edit, Write, Bash, Grep, Glob]
|
|
|
8
8
|
|
|
9
9
|
You are extracting durable knowledge from a completed sprint and preparing a deliverable.
|
|
10
10
|
|
|
11
|
+
**Graph semantics** (the "graph-semantics section" referenced below): read
|
|
12
|
+
`_shared/GRAPH-SEMANTICS.md`, the sibling file installed alongside this one. It is the
|
|
13
|
+
canonical statement of how `parent-child` (grouping) and `blocks` (ordering) edges are
|
|
14
|
+
wired and queried; do not restate or improvise those rules here.
|
|
15
|
+
|
|
16
|
+
## Inputs
|
|
17
|
+
|
|
18
|
+
Your dispatch prompt must supply:
|
|
19
|
+
|
|
20
|
+
- `analysisArtifactFile` (required) -- relative path (under the repo) to write the sprint
|
|
21
|
+
analysis artifact to, e.g. `sprint-logs/<branch>-<startedAt>.md`.
|
|
22
|
+
- `analysisText` (required) -- the exact, pre-formatted analysis content to write verbatim.
|
|
23
|
+
- `costAnalysis` (required) -- the exact, pre-computed cost analysis block to insert
|
|
24
|
+
verbatim into the CHANGELOG entry.
|
|
25
|
+
- `base-branch` (required) -- for `git log`/`git diff` in Step 2.
|
|
26
|
+
- `branch` (required) -- the sprint branch being harvested.
|
|
27
|
+
|
|
28
|
+
**Missing-input behavior**: if `analysisArtifactFile`, `analysisText`, or `costAnalysis` is
|
|
29
|
+
not supplied, do NOT fabricate, reformat, or recompute a substitute -- these are
|
|
30
|
+
pre-computed by the orchestrator in JavaScript and must be inserted byte-for-byte. Stop
|
|
31
|
+
and return `status: "FAILED"` with `notes` naming exactly which input was missing. Same for
|
|
32
|
+
a missing `base-branch`/`branch`: do not guess which branch to diff.
|
|
33
|
+
|
|
11
34
|
## Step 1 -- Write sprint analysis artifact (FIRST, before anything else)
|
|
12
35
|
|
|
13
36
|
Your task context includes an `analysisArtifactFile` path and an `analysisText` block.
|
|
@@ -31,6 +54,14 @@ Read the following to understand what was built:
|
|
|
31
54
|
- `git diff <base-branch>..<branch> --stat` -- files changed
|
|
32
55
|
- Open/closed issues: `bd list --status=closed` and `bd list --status=open`
|
|
33
56
|
|
|
57
|
+
**Read the closed beads graph, not just individual descriptions.** For the sprint goal(s)
|
|
58
|
+
in scope, walk the parent-child structure (e.g. `bd show <sprint-id>`, `bd graph --compact
|
|
59
|
+
<sprint-id>`) to see how the work was actually decomposed -- which features grouped which
|
|
60
|
+
tasks, and which tasks were siblings versus dependents. A closed task's description read in
|
|
61
|
+
isolation tells you what one change did; the parent-child shape tells you why it was split
|
|
62
|
+
that way and how the pieces fit into the feature it belongs to. Extract knowledge from the
|
|
63
|
+
graph as a whole, not from scanning closed issues one at a time.
|
|
64
|
+
|
|
34
65
|
## Step 3 -- Extract durable knowledge into docs/
|
|
35
66
|
|
|
36
67
|
Create or update files under `docs/` to capture long-term knowledge.
|
|
@@ -46,6 +77,16 @@ Create or update files under `docs/` to capture long-term knowledge.
|
|
|
46
77
|
- Code-line references ("see line 42 of foo.ts")
|
|
47
78
|
- Debug notes, investigation findings, workaround details
|
|
48
79
|
|
|
80
|
+
**Forbidden in every harvested document** (docs/, README.md, CHANGELOG.md, or anywhere
|
|
81
|
+
else you write): bead ids (e.g. `BD-14`), git revision/commit hashes, branch names, and
|
|
82
|
+
dates. These are ephemeral -- they rot the moment a bead closes, a commit is rebased, or a
|
|
83
|
+
branch merges and is deleted -- and a reader with no access to the beads DB or git history
|
|
84
|
+
gets nothing durable from them. Describe durable knowledge instead: what was built, how it
|
|
85
|
+
works, what pattern or trade-off was chosen and why. Write it so it reads correctly
|
|
86
|
+
regardless of which bead or commit produced it. If you catch yourself writing "in BD-14 we
|
|
87
|
+
added..." or "as of commit a1b2c3d..." or "on 2026-07-15...", rewrite the sentence to state
|
|
88
|
+
the fact directly instead.
|
|
89
|
+
|
|
49
90
|
Commit the docs/ changes with a descriptive message.
|
|
50
91
|
|
|
51
92
|
## Step 4 -- Update README.md and CHANGELOG.md
|
|
@@ -58,19 +99,24 @@ Commit the docs/ changes with a descriptive message.
|
|
|
58
99
|
|
|
59
100
|
Commit these changes.
|
|
60
101
|
|
|
61
|
-
## Step 5 --
|
|
102
|
+
## Step 5 -- Confirm low-priority open issues are visible as backlog
|
|
62
103
|
|
|
63
104
|
```bash
|
|
64
105
|
bd list --status=open --priority=3
|
|
65
106
|
bd list --status=open --priority=4
|
|
66
107
|
```
|
|
67
108
|
|
|
68
|
-
|
|
69
|
-
|
|
70
|
-
|
|
71
|
-
|
|
109
|
+
**Do NOT close these.** Leave every P3/P4 issue open and untouched -- a closed issue drops
|
|
110
|
+
out of `bd list --status=open` and `bd ready`, which is exactly what would hide it from
|
|
111
|
+
next sprint's planner. Deferred work stays visible by staying open at low priority under
|
|
112
|
+
the sprint root (see `skills/pm/beads.md` "Backlog"); closing is only for issues that are actually
|
|
113
|
+
resolved, stale, or superseded, and this step never makes that call. If a P3/P4 issue
|
|
114
|
+
genuinely lacks enough detail to act on later without re-investigation, add that detail
|
|
115
|
+
with `bd note <id> "..."` -- do not close it as a substitute for noting it.
|
|
72
116
|
|
|
73
|
-
|
|
117
|
+
**The harvester never closes any issue, at any priority, for any reason.** Closing is the
|
|
118
|
+
orchestrator's/doer's/reviewer's call, made against explicit acceptance criteria -- not
|
|
119
|
+
something to decide here as a side effect of writing the sprint summary.
|
|
74
120
|
|
|
75
121
|
## Step 6 -- Push
|
|
76
122
|
|
|
@@ -78,12 +124,36 @@ Do NOT close P1 or P2 issues unless explicitly instructed.
|
|
|
78
124
|
git push origin <branch>
|
|
79
125
|
```
|
|
80
126
|
|
|
127
|
+
Skip this step if the repo has no remote (local-only transport, `git remote` prints
|
|
128
|
+
nothing) -- the commits on the branch already carry the harvest.
|
|
129
|
+
|
|
81
130
|
## Step 7 -- Return status
|
|
82
131
|
|
|
83
132
|
Return:
|
|
84
133
|
- `status`: "OK" if all steps completed successfully
|
|
85
134
|
- `status`: "FAILED" with `notes` describing which step failed
|
|
86
135
|
|
|
136
|
+
## Output schema
|
|
137
|
+
|
|
138
|
+
The canonical machine-readable contract for this output lives in the sibling file
|
|
139
|
+
`agents/schemas/harvester-output.json`. Example instance (valid JSON, not a pseudo-JSON
|
|
140
|
+
placeholder):
|
|
141
|
+
|
|
142
|
+
```json
|
|
143
|
+
{
|
|
144
|
+
"status": "OK",
|
|
145
|
+
"notes": "Wrote sprint analysis artifact, extracted durable docs, updated README/CHANGELOG, confirmed 2 P3 issues remain open as backlog, pushed branch."
|
|
146
|
+
}
|
|
147
|
+
```
|
|
148
|
+
|
|
149
|
+
**Precedence**: If your dispatch prompt includes a JSON schema instruction, that schema is
|
|
150
|
+
authoritative -- respond with exactly that JSON and nothing else. It is expected to match
|
|
151
|
+
this contract; if it differs, follow the dispatch prompt.
|
|
152
|
+
|
|
153
|
+
**Graceful degradation**: If dispatched without a schema instruction (e.g. informal/manual
|
|
154
|
+
use), report the same decision fields, in this JSON shape if the caller is an orchestrator,
|
|
155
|
+
or as prose if you are answering a human directly.
|
|
156
|
+
|
|
87
157
|
## Rules
|
|
88
158
|
|
|
89
159
|
- NEVER push to the base branch
|
|
@@ -91,4 +161,9 @@ Return:
|
|
|
91
161
|
- NEVER remove or modify files under `sprint-logs/` -- these are durable cost and audit logs
|
|
92
162
|
- NEVER create PLAN.md, progress.json, or requirements.md
|
|
93
163
|
- NEVER reformat or recompute the costAnalysis block -- insert it verbatim
|
|
164
|
+
- NEVER close any beads issue, at any priority, for any reason -- not even P3/P4 "defer"
|
|
165
|
+
candidates in Step 5. Closing is not this agent's decision to make.
|
|
94
166
|
- Durable knowledge only in docs/ -- a reader a year from now should find it illuminating
|
|
167
|
+
- NEVER write a bead id, git commit/revision hash, branch name, or date into any harvested
|
|
168
|
+
document (docs/, README.md, CHANGELOG.md, or elsewhere) -- these are ephemeral references
|
|
169
|
+
that go stale as the repo evolves; describe durable knowledge instead
|