@windyroad/itil 0.4.0 → 0.4.1-preview.92

package/.claude-plugin/plugin.json

@@ -1,5 +1,5 @@
 {
   "name": "wr-itil",
-  "version": "0.1.0",
+  "version": "0.4.0",
   "description": "ITIL-aligned IT service management for Claude Code"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@windyroad/itil",
-  "version": "0.4.0",
+  "version": "0.4.1-preview.92",
   "description": "ITIL-aligned IT service management for Claude Code (problem, and future incident/change skills)",
   "bin": {
     "windyroad-itil": "./bin/install.mjs"

package/skills/work-problems/SKILL.md

@@ -96,6 +96,28 @@ Format as a brief status line, not a wall of text. The user will read these when
 [Iteration 3] Skipped P016 (Multi-concern ticket splitting) — fix released, awaiting user verification. Worked P024 (Risk scorer WIP flag) — implemented fix, closed. 6 problems remain.
 ```
 
+### Step 6.5: Release-cadence check (per ADR-018)
+
+After the iteration's commit lands but before starting the next iteration, check whether the unreleased queue would push pipeline risk to or above appetite. If so, drain the queue before continuing. This prevents silent accumulation of unreleased changesets across AFK iterations (P041).
+
+**Mechanism — delegate, do not re-implement scoring:**
+
+1. Invoke the risk scorer to score cumulative pipeline state. Two paths are valid (per ADR-015):
+   - **Primary**: delegate to subagent type `wr-risk-scorer:pipeline` via the Agent tool.
+   - **Fallback**: if that subagent type is not available, invoke skill `/wr-risk-scorer:assess-release` via the Skill tool. The skill wraps the same pipeline subagent.
+2. Read the returned `RISK_SCORES: commit=X push=Y release=Z` line.
+3. **Threshold**: if `push` or `release` is at or above appetite (4/25, "Low" band per `RISK-POLICY.md`), drain the queue.
+
+**Drain action (non-interactive, policy-authorised per ADR-013 Rule 6):**
+
+1. Run `npm run push:watch` (push + wait for CI to pass).
+2. If `.changeset/` is non-empty after push, run `npm run release:watch` (merge the release PR + wait for npm publish).
+3. Resume the loop only after the release lands on npm.
+
+**Failure handling**: If `release:watch` fails (CI failure, publish failure), stop the loop and report the failure in the AFK summary. Do not retry non-interactively — the user must intervene.
+
+`push:watch` and `release:watch` are policy-authorised actions when residual risk is within appetite per RISK-POLICY.md, so no `AskUserQuestion` is required for the drain itself (ADR-013 Rule 6).
+
 ### Step 7: Loop
 
 Go back to step 1. The backlog may have changed — new problems may have been created during fixes, priorities may have shifted, and the README.md cache will be stale.
@@ -111,6 +133,7 @@ When `AskUserQuestion` is unavailable or the user is AFK, the skill (and the del
 | Scope expansion during work | Update problem file, re-score WSJF, move to next problem instead of continuing |
 | Commit when risk within appetite | Auto-commit (manage-problem step 9e fallback) |
 | Commit when risk above appetite | Skip commit, report uncommitted state |
+| Pipeline risk at appetite (push or release >= 4/25) | Drain release queue (`push:watch` then `release:watch`) before next iteration — per ADR-018 (Step 6.5) |
 | Fix verification needed | Skip problem, add to "needs verification" list |
 
 ## Edge Cases

package/skills/work-problems/test/work-problems-release-cadence.bats

@@ -0,0 +1,63 @@
+#!/usr/bin/env bats
+# Doc-lint guard: work-problems SKILL.md must include the inter-iteration
+# release-cadence check per ADR-018.
+#
+# Structural assertion — Permitted Exception to the source-grep ban (ADR-005 / P011).
+# These tests assert that the skill specification document contains the
+# release-cadence step so the AFK orchestrator does not silently accumulate
+# unreleased changesets across iterations.
+#
+# Cross-reference:
+#   P041 (work-problems does not enforce release cadence)
+#   ADR-018 (inter-iteration release cadence for AFK loops)
+#   @jtbd JTBD-006 (Progress the Backlog While I'm Away)
+
+setup() {
+  SKILL_DIR="$(cd "$(dirname "$BATS_TEST_FILENAME")/.." && pwd)"
+  SKILL_FILE="${SKILL_DIR}/SKILL.md"
+}
+
+@test "SKILL.md exists" {
+  [ -f "$SKILL_FILE" ]
+}
+
+@test "SKILL.md cites ADR-018 (release cadence)" {
+  # ADR-018 confirmation criterion: skill must reference the ADR.
+  run grep -n "ADR-018" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}
+
+@test "SKILL.md delegates to wr-risk-scorer:assess-release (preserves pure-scorer contract from ADR-015)" {
+  # ADR-018 mechanism: must delegate to the assess-release skill rather than
+  # re-implementing risk scoring inline.
+  run grep -n "assess-release" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}
+
+@test "SKILL.md references release:watch as the drain mechanism" {
+  # ADR-018 mechanism: drain action runs npm run release:watch (after
+  # push:watch) when the queue hits appetite.
+  run grep -n "release:watch" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}
+
+@test "SKILL.md references push:watch as part of the drain mechanism" {
+  # ADR-018 mechanism: drain action runs push:watch before release:watch.
+  run grep -n "push:watch" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}
+
+@test "SKILL.md has a release-cadence step between iterations" {
+  # The inter-iteration check should appear as a discrete step or subsection
+  # so it is not buried in prose.
+  run grep -niE "release.cadence|cadence check|release queue" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}
+
+@test "SKILL.md Non-Interactive Decision Making table covers pipeline risk at appetite" {
+  # ADR-018 confirmation criterion: the non-interactive defaults table must
+  # include a row for the release-drain decision, otherwise an AFK reader
+  # cannot find the rule.
+  run grep -niE "Pipeline risk at appetite|release queue.*appetite|drain.*release" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}