@staff0rd/assist 0.1142.0 → 0.1143.1

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.
@@ -42,7 +42,17 @@ If Step 3 produced a design, link it from the description as `/design` describes
42
42
 
43
43
  - (conditions that confirm the bug is fixed)
44
44
 
45
- Do NOT generate a plan — the implementer will determine how to fix it.
45
+ **Plan:** (optional phases)
46
+
47
+ - Phase 1: (name) — tasks...
48
+
49
+ Phases go in the plan, never in the acceptance criteria — an acceptance criterion that reads as a phase (e.g. `Phase 1: ...`) is rejected by `propose`.
50
+
51
+ - If the user said how to split or sequence the fix (e.g. "make phase 1 do X"), author those phases as they asked.
52
+ - Otherwise, author phases only when your investigation makes the fix clear — you know which code changes and how. Keep them to vertical slices that each pass `assist verify` on their own (usually one phase for a bug).
53
+ - If the fix is not clear, leave the plan empty; the implementer will determine how to fix it.
54
+
55
+ Do not author a `Review` phase — the runner appends it to every plan, and `propose` rejects one.
46
56
 
47
57
  ### Writing the description
48
58
 
@@ -69,11 +79,16 @@ cat <<'JSON' | assist backlog propose --json - 2>&1
69
79
  "name": "Bug title",
70
80
  "type": "bug",
71
81
  "description": "**Repro:**\n\n1. ...\n2. ...\n\n**Expected:** ...\n\n**Actual:** ...",
72
- "acceptanceCriteria": ["criterion 1", "criterion 2"]
82
+ "acceptanceCriteria": ["criterion 1", "criterion 2"],
83
+ "phases": [
84
+ { "name": "Phase one name", "tasks": ["Task 1", "Task 2"] }
85
+ ]
73
86
  }
74
87
  JSON
75
88
  ```
76
89
 
90
+ Omit `phases` when you are not authoring a plan. Each phase needs at least one task; add `manualChecks` to a phase only when its checks are genuinely hard to automate.
91
+
77
92
  The payload is strict JSON — an unknown key is an error. `\n` inside the `description` string is a JSON escape and becomes a real newline, which is what the markdown rendering needs.
78
93
 
79
94
  Always run `propose` **as a background task**, and do no other work until it returns. In a web session it blocks on the preview pane until the user decides, which can take far longer than the default command timeout, and the pending preview dies with the process — a killed `propose` abandons the item. To revise the report while its preview is still pending, re-run `propose` with the revised payload directly — do not stop the earlier task. The pane swaps to the new version, and the earlier task exits 0 printing `Superseded by a newer preview — no decision; ignore this result.` without creating anything: ignore it.
@@ -1 +1 @@
1
- 0.1142.0
1
+ 0.1143.1