@windyroad/itil 2.4.2-preview.1241 → 2.4.2-preview.1243

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,6 +1,6 @@
1
1
  {
2
2
  "name": "@windyroad/itil",
3
- "version": "2.4.2-preview.1241",
3
+ "version": "2.4.2-preview.1243",
4
4
  "description": "ITIL-aligned IT service management for Claude Code and Codex",
5
5
  "bin": {
6
6
  "windyroad-itil": "./bin/install.mjs"
@@ -1182,7 +1182,7 @@ When `AskUserQuestion` is unavailable or the user is AFK, the skill (and the del
1182
1182
 
1183
1183
  **Being gated is not being out-of-scope.** The external-comms gate (the "External-comms gate — voice-tone + risk/leak evaluators on shared PreToolUse surface" architecture rule) exists precisely so that low-risk outbound prose *proceeds without stopping for anyone* — `wr-risk-scorer:external-comms` § PASS Output states that policy-authorised drafts proceed silently. An agent that meets an external-comms obligation mid-pass and declines it as "an external-comms action outside this pre-flight's scope" has read the guard as a wall, and the obligation is stranded with nothing left to pick it up. User correction 2026-07-26: **"External comms is NOT out of pre-flight scope."**
1184
1184
 
1185
- The cost is measured, not hypothetical (2026-09-19): of 53 converted inbound reports, **41 have never been acknowledged**, and the oldest has been silent for **75 days**; **24 lifecycle updates are owed to reporters right now**, 23 of them to inbound reporters. Every one of those is a promise the "Report a Problem Without Pre-Classifying It" user outcome makes on our behalf — that a submitted report gets an acknowledgement and eventually a verdict — and this reasoning error is what breaks it.
1185
+ The cost is observable: converted inbound reports remain unacknowledged, and lifecycle updates remain owed to reporters. Each is a promise the "Report a Problem Without Pre-Classifying It" user outcome makes on our behalf — that a submitted report gets an acknowledgement and eventually a verdict — and this reasoning error is what breaks it.
1186
1186
 
1187
1187
  **Authorised — dispatch, do not defer.** Each of these rides the external-comms gate and silent-passes on a low-risk verdict. Only an above-appetite verdict queues, and queuing does not halt the loop:
1188
1188