@ze-norm/cli 0.11.5 → 0.13.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.
@@ -107,12 +107,13 @@ or any task is still `active`.
107
107
 
108
108
  ## Fail-fast / partial-completion rules
109
109
 
110
- - Do **not** call `task complete` on a blocked task.
111
- - Do **not** claim the spec is complete in your final user-facing
112
- message if any task is `active` or any AC is unmet.
113
- - The blocker reason lives in the chat transcript today (no
114
- `task block` command exists). Surface it in the final report and, if
115
- the work needed is non-trivial, capture it as a follow-up task:
110
+ The bucketing in Step 1 already covers the core rule (never `task complete` a
111
+ blocked task; never claim completion when something is `active` or unmet). One
112
+ thing it doesn't cover capturing the blocker durably:
113
+
114
+ - The blocker reason lives in the chat transcript today (no `task block`
115
+ command exists). Surface it in the final report and, if the work needed is
116
+ non-trivial, capture it as a follow-up task:
116
117
  `zenorm task create <spec-key> --title="Unblock <task>: <reason>"`.
117
118
 
118
119
  ## Rules
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@ze-norm/cli",
3
3
  "private": false,
4
- "version": "0.11.5",
4
+ "version": "0.13.0",
5
5
  "license": "SEE LICENSE IN README.md",
6
6
  "type": "module",
7
7
  "repository": {