@llipe.com/dev-tasks 0.16.2 → 0.17.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude/agents/developer.md +8 -3
- package/.claude/agents/github-ops.md +187 -59
- package/.claude/agents/technical-writer.md +1 -1
- package/.claude/agents/verifier.md +10 -5
- package/.claude/commands/planner.md +110 -15
- package/.claude/commands/product-engineer.md +27 -3
- package/.claude/hooks/git-guard.sh +2 -2
- package/.claude/skills/activity-init/SKILL.md +4 -0
- package/.claude/skills/activity-publish-github/SKILL.md +84 -15
- package/.claude/skills/git-ops/SKILL.md +6 -6
- package/.claude/skills/implement/SKILL.md +29 -13
- package/.claude/skills/memo-cli-usage/REFERENCE.md +1 -0
- package/.claude/skills/memo-cli-usage/SKILL.md +3 -1
- package/.claude/skills/plan/SKILL.md +6 -0
- package/.github/agents/developer.agent.md +8 -3
- package/.github/agents/github-ops.agent.md +182 -64
- package/.github/agents/planner.agent.md +123 -28
- package/.github/agents/product-engineer.agent.md +27 -3
- package/.github/agents/technical-writer.agent.md +1 -1
- package/.github/agents/verifier.agent.md +10 -5
- package/.github/instructions/implement.instructions.md +29 -13
- package/.github/instructions/plan.instructions.md +6 -0
- package/.github/skills/activity-init/SKILL.md +4 -0
- package/.github/skills/activity-publish-github/SKILL.md +84 -15
- package/.github/skills/git-ops/SKILL.md +6 -6
- package/.github/skills/memo-cli-usage/REFERENCE.md +1 -0
- package/.github/skills/memo-cli-usage/SKILL.md +3 -1
- package/.kiro/agents/developer.md +8 -3
- package/.kiro/agents/github-ops.md +182 -64
- package/.kiro/agents/planner.md +123 -28
- package/.kiro/agents/product-engineer.md +27 -3
- package/.kiro/agents/technical-writer.md +1 -1
- package/.kiro/agents/verifier.md +10 -5
- package/.kiro/skills/activity-init/SKILL.md +4 -0
- package/.kiro/skills/activity-publish-github/SKILL.md +84 -15
- package/.kiro/skills/git-ops/SKILL.md +6 -6
- package/.kiro/skills/memo-cli-usage/REFERENCE.md +1 -0
- package/.kiro/skills/memo-cli-usage/SKILL.md +3 -1
- package/.kiro/steering/implement.md +29 -13
- package/.kiro/steering/plan.md +6 -0
- package/CHANGELOG.md +42 -0
- package/README.md +79 -7
- package/TESTING.md +108 -30
- package/dist/bin/dev-tasks.d.ts +1 -1
- package/dist/bin/dev-tasks.js +126 -4
- package/dist/bin/dev-tasks.js.map +1 -1
- package/dist/bin/parse-args.d.ts +49 -1
- package/dist/bin/parse-args.d.ts.map +1 -1
- package/dist/bin/parse-args.js +132 -11
- package/dist/bin/parse-args.js.map +1 -1
- package/dist/core/checks/decision-log-format.d.ts +24 -3
- package/dist/core/checks/decision-log-format.d.ts.map +1 -1
- package/dist/core/checks/decision-log-format.js +43 -3
- package/dist/core/checks/decision-log-format.js.map +1 -1
- package/dist/core/checks/index.d.ts +2 -0
- package/dist/core/checks/index.d.ts.map +1 -1
- package/dist/core/checks/index.js +1 -0
- package/dist/core/checks/index.js.map +1 -1
- package/dist/core/checks/roadmap.d.ts +40 -0
- package/dist/core/checks/roadmap.d.ts.map +1 -0
- package/dist/core/checks/roadmap.js +78 -0
- package/dist/core/checks/roadmap.js.map +1 -0
- package/dist/core/migrate-projects/answers.d.ts +63 -0
- package/dist/core/migrate-projects/answers.d.ts.map +1 -0
- package/dist/core/migrate-projects/answers.js +79 -0
- package/dist/core/migrate-projects/answers.js.map +1 -0
- package/dist/core/migrate-projects/apply.d.ts +51 -0
- package/dist/core/migrate-projects/apply.d.ts.map +1 -0
- package/dist/core/migrate-projects/apply.js +828 -0
- package/dist/core/migrate-projects/apply.js.map +1 -0
- package/dist/core/migrate-projects/classify.d.ts +93 -0
- package/dist/core/migrate-projects/classify.d.ts.map +1 -0
- package/dist/core/migrate-projects/classify.js +170 -0
- package/dist/core/migrate-projects/classify.js.map +1 -0
- package/dist/core/migrate-projects/conventions.d.ts +118 -0
- package/dist/core/migrate-projects/conventions.d.ts.map +1 -0
- package/dist/core/migrate-projects/conventions.js +213 -0
- package/dist/core/migrate-projects/conventions.js.map +1 -0
- package/dist/core/migrate-projects/gh.d.ts +40 -0
- package/dist/core/migrate-projects/gh.d.ts.map +1 -0
- package/dist/core/migrate-projects/gh.js +115 -0
- package/dist/core/migrate-projects/gh.js.map +1 -0
- package/dist/core/migrate-projects/index.d.ts +61 -0
- package/dist/core/migrate-projects/index.d.ts.map +1 -0
- package/dist/core/migrate-projects/index.js +183 -0
- package/dist/core/migrate-projects/index.js.map +1 -0
- package/dist/core/migrate-projects/local-reader.d.ts +8 -0
- package/dist/core/migrate-projects/local-reader.d.ts.map +1 -0
- package/dist/core/migrate-projects/local-reader.js +30 -0
- package/dist/core/migrate-projects/local-reader.js.map +1 -0
- package/dist/core/migrate-projects/map.d.ts +36 -0
- package/dist/core/migrate-projects/map.d.ts.map +1 -0
- package/dist/core/migrate-projects/map.js +75 -0
- package/dist/core/migrate-projects/map.js.map +1 -0
- package/dist/core/migrate-projects/plan.d.ts +71 -0
- package/dist/core/migrate-projects/plan.d.ts.map +1 -0
- package/dist/core/migrate-projects/plan.js +638 -0
- package/dist/core/migrate-projects/plan.js.map +1 -0
- package/dist/core/migrate-projects/planfile.d.ts +149 -0
- package/dist/core/migrate-projects/planfile.d.ts.map +1 -0
- package/dist/core/migrate-projects/planfile.js +608 -0
- package/dist/core/migrate-projects/planfile.js.map +1 -0
- package/dist/core/migrate-projects/roadmap.d.ts +43 -0
- package/dist/core/migrate-projects/roadmap.d.ts.map +1 -0
- package/dist/core/migrate-projects/roadmap.js +54 -0
- package/dist/core/migrate-projects/roadmap.js.map +1 -0
- package/dist/core/migrate-projects/snapshot.d.ts +91 -0
- package/dist/core/migrate-projects/snapshot.d.ts.map +1 -0
- package/dist/core/migrate-projects/snapshot.js +285 -0
- package/dist/core/migrate-projects/snapshot.js.map +1 -0
- package/dist/core/migrate-projects/summary.d.ts +27 -0
- package/dist/core/migrate-projects/summary.d.ts.map +1 -0
- package/dist/core/migrate-projects/summary.js +35 -0
- package/dist/core/migrate-projects/summary.js.map +1 -0
- package/package.json +8 -6
|
@@ -119,10 +119,26 @@ When `workstream/decisions-<feature>.md` exists and was read per step 2 above:
|
|
|
119
119
|
- If drift is detected between local and GitHub, you **MUST** reconcile immediately and report the reconciliation.
|
|
120
120
|
- If schema/data-model changes are in scope, migration artifacts **MUST** be tracked in the task list unless an explicit opt-out rationale is documented.
|
|
121
121
|
|
|
122
|
-
###
|
|
123
|
-
|
|
124
|
-
- You **
|
|
125
|
-
- You **SHOULD** route
|
|
122
|
+
### Status Comment
|
|
123
|
+
|
|
124
|
+
- You **MUST** keep the story's status comment current per `github-ops` § Status comment: create it at the first sub-task completion, edit it in place at every later sub-task completion, at PR open, at each gate recorded, and on block. The template (marker, prefix line, story table) lives in `github-ops` and is never restated here.
|
|
125
|
+
- You **SHOULD** route the status-comment write through `github-ops` whenever possible; when delegation is unavailable, run the commands below directly.
|
|
126
|
+
- Procedure, for story issue `{n}` of `repos/{o}/{r}`:
|
|
127
|
+
1. Find the comment by its marker: `gh api repos/{o}/{r}/issues/{n}/comments --paginate --jq '.[] | select(.body | startswith("<!-- dev-tasks:status -->")) | .id'`.
|
|
128
|
+
2. Absent → create it: `gh issue comment {n} --body-file <path>`.
|
|
129
|
+
3. Present → edit it in place: `gh api -X PATCH repos/{o}/{r}/issues/comments/{id} -F body=@<path>`.
|
|
130
|
+
4. Two or more comments carry the marker → edit the oldest (lowest id), never post another, and report `status_comment: failed(duplicate marker)` so a human removes the extra one.
|
|
131
|
+
5. The marker is the first byte of the body file — no leading blank line, whitespace or BOM — because the `startswith` match on line one is how the comment is found; a marker on line two means a second comment gets posted. The body always goes through a file, never inline.
|
|
132
|
+
- Each write is reported as `status_comment: written | failed(<reason>) | skipped(no issue)`. A task list with no GitHub Issue skips the comment and reports `skipped(no issue)`; a refused write (permissions, locked issue) reports `failed(<reason>)`. A failed write never blocks the sub-task — it is reported, never dropped silently.
|
|
133
|
+
|
|
134
|
+
### Wave Status Update (Main Thread Only)
|
|
135
|
+
|
|
136
|
+
- Under the `planner`, the wave's status comment belongs to the planner: report `wave_status: owned-by-planner` and do nothing further.
|
|
137
|
+
- In the main thread with no planner (the interactive `/developer` command), after PR open and at PR ready you **MUST** look up the story's parent: `gh api repos/{o}/{r}/issues/{n}/parent`.
|
|
138
|
+
- `200` → edit this story's row (state, PR, sub-task count) in the wave issue's status comment, found and edited by the same marker procedure above, and report `wave_status: written`. If the wave issue has no status comment yet, create it from the wave table in `github-ops` § Status comment and report `wave_status: written`.
|
|
139
|
+
- Header lines on this path, which has no integration branch (D-75, RD-17): `Current story` names this story; `Last merged PR` and `Integration HEAD` keep the existing comment's values when editing it and read `none` when creating the comment; `Gates` carries this story's gates.
|
|
140
|
+
- `404` → the story has no parent (published before the hierarchy convention); report `wave_status: skipped(no parent)`. This is expected, not an error.
|
|
141
|
+
- A refused read or write → `wave_status: failed(<reason>)`; it never blocks the sub-task.
|
|
126
142
|
|
|
127
143
|
---
|
|
128
144
|
|
|
@@ -153,19 +169,19 @@ When `workstream/decisions-<feature>.md` exists and was read per step 2 above:
|
|
|
153
169
|
- PRs targeting **`main`**: the **user** reviews and approves.
|
|
154
170
|
|
|
155
171
|
11. The PR **MUST** be merged by the authorized party (planner for integration branches, user for `main`).
|
|
156
|
-
12.
|
|
157
|
-
13. You **MUST NOT** close the issue
|
|
172
|
+
12. Nobody closes the GitHub Issue: not the implementing agent, not the `planner`. It closes when a PR against the default branch carrying `Closes #N` merges: under the `planner` that is the consolidated PR, and in a main-thread run with no planner (the interactive `/developer` command) it is the story PR itself. A story PR into an integration branch closes nothing, because GitHub ignores closing keywords on a PR whose base is not the default branch.
|
|
173
|
+
13. You **MUST NOT** close the issue by hand at any point, before or after the merge; if it is still open after the closing PR merged, report that instead of closing it.
|
|
158
174
|
14. You **MUST** notify the user when the PR is ready for review — explicitly inform them so they can review and merge.
|
|
159
175
|
|
|
160
176
|
---
|
|
161
177
|
|
|
162
178
|
## GitHub Execution Rules Summary
|
|
163
179
|
|
|
164
|
-
| Phase | Rule
|
|
165
|
-
| ------------------ |
|
|
166
|
-
| **Before coding** | Confirm issue open → Create branch (`github-ops`) → First commit → Open draft PR (`github-ops`) → Sync checklists
|
|
167
|
-
| **During coding** | One sub-task at a time → Mark `[x]` locally + GitHub → Wait for approval
|
|
168
|
-
| **Before closing** | All ACs verified → Quality gates pass (test/lint/format/typecheck/audit) → migration confirmation/apply/verify (when applicable) → docs drift check clear → coverage_gate recorded → verifier audit run + summary posted (non-blocking on drift) → PR ready → Approved → Merged →
|
|
180
|
+
| Phase | Rule |
|
|
181
|
+
| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
182
|
+
| **Before coding** | Confirm issue open → Create branch (`github-ops`) → First commit → Open draft PR (`github-ops`) → Sync checklists |
|
|
183
|
+
| **During coding** | One sub-task at a time → Mark `[x]` locally + GitHub → Update the status comment (`github-ops` § Status comment) → Wait for approval |
|
|
184
|
+
| **Before closing** | All ACs verified → Quality gates pass (test/lint/format/typecheck/audit) → migration confirmation/apply/verify (when applicable) → docs drift check clear → coverage_gate recorded → verifier audit run + summary posted (non-blocking on drift) → PR ready → Approved → Merged → GitHub closes the issue (`Closes #N` on a default-branch PR) |
|
|
169
185
|
|
|
170
186
|
---
|
|
171
187
|
|
|
@@ -178,7 +194,7 @@ When `workstream/decisions-<feature>.md` exists and was read per step 2 above:
|
|
|
178
194
|
## Final Instructions
|
|
179
195
|
|
|
180
196
|
1. You **MUST** always respect the task list execution order.
|
|
181
|
-
2. You **MUST** keep the GitHub Issue updated with checklist and
|
|
197
|
+
2. You **MUST** keep the GitHub Issue updated with its checklist and its status comment.
|
|
182
198
|
3. You **MUST** ensure branch, PR, and issue naming follow `github-ops` conventions.
|
|
183
199
|
4. You **MUST** stop after each sub-task and request user approval.
|
|
184
|
-
5. You **MUST NOT** close a GitHub Issue
|
|
200
|
+
5. You **MUST NOT** close a GitHub Issue by hand: nobody closes it; it closes when a PR against the default branch carrying `Closes #N` merges.
|
|
@@ -118,6 +118,7 @@ memo write \
|
|
|
118
118
|
--entry-type decision \
|
|
119
119
|
--source agent \
|
|
120
120
|
--provenance "<csv of episodic entry ids this consolidates, if any>" \
|
|
121
|
+
--on-duplicate create-new \
|
|
121
122
|
--json
|
|
122
123
|
```
|
|
123
124
|
|
|
@@ -166,7 +167,8 @@ A `semantic` entry with `--source agent` **MUST** carry `--provenance <csv>` unl
|
|
|
166
167
|
## Agent Mode Rules
|
|
167
168
|
|
|
168
169
|
- Always pass `--json` for parseable output
|
|
169
|
-
- Always pass `--on-duplicate
|
|
170
|
+
- Always pass `--on-duplicate` for writes; in `--json` mode memo-cli fails on a duplicate without it
|
|
171
|
+
- Pass `create-new` for distinct decisions, one entry per decision row (a feature's decision write-back); pass `consolidate` only when restating or updating the same decision, such as re-writing an entry after an amendment on the same story and commit to correct its rationale (D-78)
|
|
170
172
|
- Never log API keys or secrets
|
|
171
173
|
- Bulk delete is blocked in `--json` mode (safety guard)
|
|
172
174
|
|
|
@@ -26,8 +26,10 @@ This activity adapts to the input — it works with a user stories file (from th
|
|
|
26
26
|
2. **Review Available Work:** You **MUST** read the source and list available stories or the issue scope.
|
|
27
27
|
3. **Select Scope:** In Stories Mode, you **MUST** ask which stories to include. In Issue Mode, the scope is the single issue.
|
|
28
28
|
4. **Generate Task List:** You **MUST** produce a `tasks-*.md` file in the required format.
|
|
29
|
+
- **Plan header:** The header carries `Source:` (the source document) and, on the next line, `Wave issue: #N`, its own line with no bold or backticks so the planner can read it at Phase 0. In Stories Mode, take the number from the publication report's `Wave issue` line (`workstream/github-publication-<prd-name>.md`, written by `activity-publish-github`). When the report predates the tracking hierarchy or has no `Wave issue` line, or in Issue Mode, write `Wave issue: none` and add a `> Note:` line under it saying the planner will search for the wave issue at Phase 0. When the plan fully resolves follow-up issues outside its story set, add a `Resolves: #N, #M` line after `Wave issue:`; the planner carries `Closes #N` for each on the consolidated PR (planner D-74). Omit the line when there are none.
|
|
29
30
|
5. **Publish to GitHub:** You **MUST** update the corresponding GitHub Issue(s) with the task checklist by delegating to `github-ops` whenever possible.
|
|
30
31
|
6. **Save Output.**
|
|
32
|
+
7. **Set the Task Plan Line:** When the plan header reads `Wave issue: #N`, set the wave issue body's `Task plan:` line under `## Artifacts` to a root-relative link to the saved task list, after the file is saved: read the body with `gh issue view <N> --json body --jq .body` into a file, change only that line, and write it back with `gh issue edit <N> --body-file <path>`. With `Wave issue: none` there is no wave issue body to edit, and the line stays `pending` until a later plan names the wave issue.
|
|
31
33
|
|
|
32
34
|
## Package Manager and Command Standards
|
|
33
35
|
|
|
@@ -56,6 +58,9 @@ The task list **MUST** follow this structure:
|
|
|
56
58
|
```markdown
|
|
57
59
|
# Implementation Plan - [Name]
|
|
58
60
|
|
|
61
|
+
Source: `[path to the user stories file or refined issue]`
|
|
62
|
+
Wave issue: #N
|
|
63
|
+
|
|
59
64
|
## Relevant Files
|
|
60
65
|
|
|
61
66
|
- `path/to/file1.ts` - [Description]
|
|
@@ -184,4 +189,5 @@ If this is a **greenfield project** or a **new component**, you **MUST** include
|
|
|
184
189
|
8. For schema/data-model changes, you **MUST** include migration lifecycle tasks and an explicit user-confirmation gate before applying migrations unless an opt-out rationale is documented.
|
|
185
190
|
9. You **MUST** update the corresponding GitHub Issue(s) with the task checklist by delegating to `github-ops` whenever possible. If no issue exists, you **MUST** ask the user whether to create one first.
|
|
186
191
|
10. You **MUST** save the task list file.
|
|
192
|
+
10a. When the wave issue is known, you **MUST** set its body's `Task plan:` Artifacts line to the saved task list (Process step 7).
|
|
187
193
|
11. You **MUST** inform the user they can now use the **implement** activity to start coding.
|
|
@@ -62,6 +62,7 @@ If the user provides a feature description or asks to create a PRD/spec/stories
|
|
|
62
62
|
3. **Task synchronization:** Whenever a sub-task is completed, you **MUST** immediately mark `[x]` in:
|
|
63
63
|
- The local task file in `/workstream/`
|
|
64
64
|
- The GitHub Issue checklist
|
|
65
|
+
- The story's status comment on the GitHub Issue, kept current per the `implement` procedure's `### Status Comment` section — the procedure and the `github-ops` § Status comment template are referenced by name and never restated here; report each outcome as `status_comment:` and `wave_status:` in the closeout payload
|
|
65
66
|
4. **Branch + PR discipline (before coding):** You **MUST** follow `github-ops` conventions:
|
|
66
67
|
- Create branch per `github-ops` branch naming rules (e.g., `issue/42-short-description`, `story/S-003-short-description`)
|
|
67
68
|
- Open a Draft PR against the default branch unless a base branch override is provided. A PR requires at least one commit, so open it immediately after the first commit on the branch — never before. You **MUST NOT** continue past that first commit without the Draft PR open.
|
|
@@ -69,7 +70,7 @@ If the user provides a feature description or asks to create a PRD/spec/stories
|
|
|
69
70
|
- Use the `github-ops` PR description template (What / Why / How / Testing / Checklist)
|
|
70
71
|
- Include `Closes #<issue-number>` in the PR description
|
|
71
72
|
5. **Stop-gate rule:** If mode is `step-gated`, you **MUST** stop after each sub-task and request user approval.
|
|
72
|
-
6. **Do not close issue
|
|
73
|
+
6. **Do not close the issue:** You **MUST NOT** close the issue; GitHub closes it when the consolidated PR merges to main under the `planner`, and when the story PR itself merges to the default branch in single-issue work without a planner. Either way the closing PR targets the default branch and carries `Closes #<issue-number>`, and nobody closes it by hand. A story PR into an integration branch closes nothing, because GitHub ignores closing keywords on a PR whose base is not the default branch.
|
|
73
74
|
7. **Keep scope tight:** You **MUST** work only on the selected issue/stories unless the user explicitly expands scope.
|
|
74
75
|
8. **Update Relevant Files:** You **MUST** keep the task file's Relevant Files section accurate.
|
|
75
76
|
9. **English-only outputs:** You **MUST** produce English-only output for docs, comments, and generated content.
|
|
@@ -101,7 +102,7 @@ Follow `.github/instructions/implement.instructions.md`:
|
|
|
101
102
|
- If HEAD is already a valid feature branch (matching `issue/*` or `story/*`), confirm the Draft PR exists and proceed. If the branch has no commits yet, no PR can exist — open it immediately after the first commit.
|
|
102
103
|
5. **memo intent (when memo is available):** Before writing any implementation code, run the memo-cli Availability Check and write the intent entry (see **memo-cli Integration → Intent Entry**). Record `memo_intent` as `written(<id>)`, `failed(<reason>)`, or `skipped(<reason>)`.
|
|
103
104
|
6. Execute one sub-task at a time in checklist order. For each behavioral sub-task, follow **test-first**: write/update tests first, verify they fail for the right reason, then implement to make them pass.
|
|
104
|
-
7. After each completed sub-task: mark `[x]` locally and in GitHub, pause for approval if step-gated.
|
|
105
|
+
7. After each completed sub-task: mark `[x]` locally and in GitHub, update the status comment per `implement` § Status Comment, pause for approval if step-gated.
|
|
105
106
|
8. When all sub-tasks are complete:
|
|
106
107
|
- Verify all acceptance criteria.
|
|
107
108
|
|
|
@@ -301,7 +302,7 @@ Before marking a Story/Issue done:
|
|
|
301
302
|
9. `/workstream` **SHOULD** be cleaned (active artifacts retained, obsolete artifacts archived/removed).
|
|
302
303
|
10. The memo intent and outcome writes **MUST** have been attempted when memo-cli is available (`memo write --kind episodic --session ISSUE-<n> --bank developer-memory …`, before PR conversion), and `memo_intent` / `memo_outcome` **MUST** be recorded as `written(<id>)`, `failed(<reason>)`, or `skipped(<reason>)`. A `failed` or `skipped` value does not block completion; an omitted field does.
|
|
303
304
|
11. PR **MUST** be ready, approved, and merged.
|
|
304
|
-
12. You **MUST NOT** close the GitHub Issue
|
|
305
|
+
12. You **MUST NOT** close the GitHub Issue; nobody closes it by hand. It closes when a PR against the default branch carrying `Closes #N` merges: under the `planner` that is the consolidated PR, and in single-issue work without a planner it is the story PR itself (rule 6).
|
|
305
306
|
13. For multi-story implementations, you **MUST** run a checklist cross-check between GitHub Issue tasks and `/workstream/tasks-*.md` and report any mismatch resolution.
|
|
306
307
|
|
|
307
308
|
---
|
|
@@ -319,6 +320,7 @@ For each run, return a compact status report with:
|
|
|
319
320
|
- Files updated in `/docs/` and ADR path (if created)
|
|
320
321
|
- Test results for the current step
|
|
321
322
|
- Quality gate results (`test`, `lint`, `format:check`, `typecheck`, `audit`)
|
|
323
|
+
- Status comment outcome (`status_comment`, `wave_status`)
|
|
322
324
|
- Next exact sub-task awaiting approval or currently executing
|
|
323
325
|
|
|
324
326
|
When finishing a story/issue execution cycle, return a **complete closeout summary** that includes:
|
|
@@ -363,6 +365,8 @@ workstream_files:
|
|
|
363
365
|
memo_intent: written(<id>) | failed(<reason>) | skipped(<reason>)
|
|
364
366
|
memo_outcome: written(<id>) | failed(<reason>) | skipped(<reason>)
|
|
365
367
|
checklist_sync: synced | mismatch-fixed | blocked
|
|
368
|
+
status_comment: written | failed(<reason>) | skipped(<reason>)
|
|
369
|
+
wave_status: written | failed(<reason>) | skipped(<reason>) | owned-by-planner
|
|
366
370
|
verifier_audit: run | blocked
|
|
367
371
|
fidelity_verdict: High | Medium | Low | none
|
|
368
372
|
highest_drift_impact: Critical | Major | Minor | None
|
|
@@ -377,5 +381,6 @@ Rules for this payload:
|
|
|
377
381
|
- Every field is required. Use `none`, `NOT RUN`, or `blocked` when a value does not exist.
|
|
378
382
|
- `memo_intent` and `memo_outcome` are always present. `skipped(<reason>)` (memo not installed, not configured, or unavailable in this session) and `failed(<reason>)` (the write was attempted and errored after one retry) are valid values that do not block the merge; `planner` treats an absent field as an incomplete story.
|
|
379
383
|
- `planner` may treat the story as incomplete if either marker or any required field is missing.
|
|
384
|
+
- `status_comment` and `wave_status` are always present; `skipped(<reason>)` is the floor, never an omission — a task list with no GitHub Issue reports `skipped(no issue)` for both (D-28). Under `planner` the wave comment belongs to the planner, so `wave_status: owned-by-planner` is the expected value in this agent's default subagent-delegation context; `written`, `skipped(no parent)` and `failed(<reason>)` come from the main-thread wave update defined in `implement`.
|
|
380
385
|
|
|
381
386
|
Do not dump full files unless explicitly requested.
|