@kanvas/openclaw-plugin 0.1.19 → 0.1.20
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/package.json
CHANGED
|
@@ -118,6 +118,26 @@ For each task, in sequence order:
|
|
|
118
118
|
|
|
119
119
|
When you transition a task, the system emits a ledger event AND a Pusher broadcast — humans watching the kanban see your progress in real time. **You don't need to do anything extra to "notify" them**; status transitions are the notification.
|
|
120
120
|
|
|
121
|
+
### 4a. Roll up plan status after every task transition
|
|
122
|
+
|
|
123
|
+
After **every** task status change, look at the rest of the tasks in the plan and reconcile the plan's status. The plan should always reflect the aggregate state of its tasks:
|
|
124
|
+
|
|
125
|
+
| Task states in the plan | Plan status |
|
|
126
|
+
|---|---|
|
|
127
|
+
| All tasks `done` (and at least one task exists) | `done` |
|
|
128
|
+
| Any task `blocked` | `blocked` |
|
|
129
|
+
| At least one `in_progress` or `pending`, none blocked | `active` (leave it alone) |
|
|
130
|
+
| All tasks `failed` / `cancelled` | `failed` (use judgment — comment first) |
|
|
131
|
+
|
|
132
|
+
**Examples:**
|
|
133
|
+
|
|
134
|
+
- You just finished the last `pending` task → flip the plan to `done` (and set `output` JSON, see §10).
|
|
135
|
+
- You marked a task `blocked` because you're stuck → flip the plan to `blocked` (and add a comment, see §8).
|
|
136
|
+
- You marked a task `done` but other tasks are still `pending` → **leave the plan on `active`**. Do nothing more.
|
|
137
|
+
- A previously blocked task got unblocked and you moved it back to `in_progress` → if the plan was `blocked` and no other tasks are blocked, flip the plan back to `active`.
|
|
138
|
+
|
|
139
|
+
The status transition is what humans see on the kanban — keeping the plan in sync with its tasks is how the board stays trustworthy. **Never** leave a plan on `active` when all tasks are done, and **never** leave a plan on `active` when a task is blocked. If you forget this step, the human's dashboard lies.
|
|
140
|
+
|
|
121
141
|
---
|
|
122
142
|
|
|
123
143
|
## 5. Add files / artifacts as you produce them
|
|
@@ -291,6 +311,7 @@ Better to ask once than apologize a hundred times.
|
|
|
291
311
|
- [ ] If no tasks, write the checklist before doing anything (`kanvas_add_task` or include in `kanvas_create_plan`)
|
|
292
312
|
- [ ] If `requires_human_approval=true`, **don't act** — leave a comment with your proposed approach and wait
|
|
293
313
|
- [ ] Move tasks `pending → in_progress → done` one at a time, in sequence order
|
|
314
|
+
- [ ] **After every task transition, roll up the plan's status** — all tasks `done` → plan `done`; any task `blocked` → plan `blocked`; otherwise leave plan on `active`
|
|
294
315
|
- [ ] Comment when something non-obvious happens
|
|
295
316
|
- [ ] Block + comment if you can't proceed
|
|
296
317
|
- [ ] Set a useful `output` JSON before flipping to `done`
|