@windyroad/itil 2.1.1 → 2.1.2-preview.1130

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.
@@ -497,5 +497,5 @@
497
497
  }
498
498
  },
499
499
  "name": "wr-itil",
500
- "version": "2.1.1"
500
+ "version": "2.1.2"
501
501
  }
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "wr-itil",
3
- "version": "2.1.1",
3
+ "version": "2.1.2",
4
4
  "description": "ITIL problem-management workflows for AI coding agents",
5
5
  "author": {
6
6
  "name": "Windy Road Technology",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@windyroad/itil",
3
- "version": "2.1.1",
3
+ "version": "2.1.2-preview.1130",
4
4
  "description": "ITIL-aligned IT service management for Claude Code and Codex",
5
5
  "bin": {
6
6
  "windyroad-itil": "./bin/install.mjs"
@@ -23,7 +23,16 @@ Continuously work the highest-priority actionable problem until the backlog is d
23
23
  1. If `docs/problems/` is absent, direct the user to `/wr-itil:scaffold-intake` and stop.
24
24
  2. Run the installed ITIL maintenance commands required by the repository, including layout migration, README reconciliation, catch-up scanning, stale upstream-cache checks, and unresolved-response checks. Resolve them from the plugin's bundled `bin/`; do not use source-repository paths.
25
25
  3. Resolve the exact checkout with `git rev-parse --show-toplevel`. Preserve unrelated working-tree changes and record the pre-iteration status. Revert only paths proven to have been created by a failed iteration.
26
- 4. If the task has a persistent Codex goal, keep it active until this drain reaches a genuine terminal state. A slow process is not a blocker.
26
+ 4. Anchor the orchestrator with the native persisted Goal tools exposed by Codex. These are Goal tool calls, not a slash command:
27
+ - Call `thread/goal/get`. Reuse the active Goal only when it carries the canonical condition below; otherwise call `thread/goal/set` with that condition and active status before entering the loop.
28
+ - Call `thread/goal/get` again at every continue-or-stop decision. Keep the Goal active while any ticket remains dispatchable. A slow process is not a blocker.
29
+ - Call `thread/goal/clear` only after the final summary prints a fresh Step 2.4 Gate (0) table showing zero dispatchable tickets followed by `ALL_DONE`, or after the summary records another canonical terminal condition: a Hard-fail halt naming the gate that could not complete, or quota exhaustion.
30
+
31
+ **Canonical Goal condition:**
32
+
33
+ ```text
34
+ The /wr-itil:work-problems AFK backlog drain is complete: the final summary printed in the conversation contains a Step 2.4 Gate (0) re-scan table (fresh open/known-error glob) classifying every ticket and showing ZERO dispatchable tickets, followed by the ALL_DONE sentinel — or the session ends with a Hard-fail halt directive naming the gate that could not complete — or the summary reports quota exhaustion.
35
+ ```
27
36
 
28
37
  ## Loop
29
38