@nyxa/nyx-agent 0.4.0 → 0.4.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.
package/package.json
CHANGED
|
@@ -1,8 +1,12 @@
|
|
|
1
|
-
Close the selected work item
|
|
1
|
+
Close the selected work item now that its implementation is complete.
|
|
2
2
|
|
|
3
3
|
Before committing or closing anything, inspect the current diff and `git status`.
|
|
4
|
-
|
|
5
|
-
it
|
|
4
|
+
If a per-task review ran this iteration (`phase_results.review` in the runtime
|
|
5
|
+
state), it already approved the work — the workflow only routes to closure after an
|
|
6
|
+
approval, so there is no need to re-confirm it. If no review phase ran (the workflow
|
|
7
|
+
may use a global end-of-run review, or no review at all), run a lightweight final
|
|
8
|
+
validation yourself when it is cheap and relevant. A missing review phase is expected
|
|
9
|
+
in those modes and is not a reason to block closure.
|
|
6
10
|
|
|
7
11
|
Commit only the selected work item's changes, using the project's commit message
|
|
8
12
|
conventions.
|
|
@@ -20,6 +24,7 @@ Report the outcome in the structured result:
|
|
|
20
24
|
|
|
21
25
|
- `closed` when the commit succeeded and the issue/work item was actually closed.
|
|
22
26
|
Set `committed` and `issue_closed` to reflect what truly happened.
|
|
23
|
-
- `failed` when something blocked closure (e.g. `gh issue close`
|
|
24
|
-
|
|
25
|
-
|
|
27
|
+
- `failed` only when something genuinely blocked closure (e.g. `gh issue close`
|
|
28
|
+
errored, or the diff does not apply). Explain what remains in `summary`. Do not
|
|
29
|
+
report `failed` merely because no review phase ran. Do not pretend the item is
|
|
30
|
+
closed when it is not — a `failed` outcome stops the run so the problem is visible.
|