@windyroad/itil 0.6.0-preview.118 → 0.7.0-preview.120

package/.claude-plugin/plugin.json

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

package/package.json

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

package/skills/manage-problem/SKILL.md

@@ -325,7 +325,8 @@ fi
 If the command produces **no output** (no problem files have been committed or modified since the last README.md update), the cache is fresh:
 - Read `docs/problems/README.md` only — it contains the ranked table from the last review
 - Skip steps 9a–9b entirely
-- Proceed directly to step 9c (work selection) using the cached table
+- Proceed to step 9c (work selection) using the cached table
+- **Step 9d always fires even on the fast-path cache hit** (P048 Candidate 1): the verification prompt surface must not depend on whether the cache is fresh — pending verifications accumulate across sessions and the user expects the prompts to appear on every `review`. Skipping 9d alongside 9a–9b would suppress verification prompts whenever the cache is fresh, which is exactly when the user is most likely to verify.
 - Note in the output: "Using cached ranking from [timestamp in README.md]"
 
 If the command prints "stale", or `README.md` does not exist in git, run the full review (steps 9a–9e) and refresh the cache.
@@ -359,10 +360,14 @@ After reviewing all problems, present a WSJF-ranked table for open/known-error p
 | WSJF | ID | Title | Severity | Status | Effort | Notes |
 |------|-----|-------|----------|--------|--------|-------|
 
-Then present a separate **Verification Queue** section for `.verifying.md` files (per ADR-022 — ranked by release age, oldest first; no WSJF because the multiplier is 0):
+Then present a separate **Verification Queue** section for `.verifying.md` files (per ADR-022 — ranked by release age, oldest first; no WSJF because the multiplier is 0). Highlight each ticket whose release age is **≥ 14 days** (the within-skill default per P048 Candidate 4 — tunable; if it needs cross-skill consistency later, promote to policy) with a `likely verified` marker in the final column. This makes the Verification Queue not just a list but a ranked view of which verifications are most likely ready to close:
 
-| ID | Title | Released | Fix summary |
-|----|-------|----------|-------------|
+| ID | Title | Released | Fix summary | Likely verified? |
+|----|-------|----------|-------------|------------------|
+
+The `Likely verified?` column takes values:
+- `yes (N days)` — release age ≥ 14 days; the user is unlikely to revert a landed fix after this long. Surface these first in step 9d's verification prompt so the user can batch-close them.
+- `no (N days)` — release age < 14 days; may still be in validation. Fire step 9d for these too, but without the highlight.
 
 Then present a separate **Parked** section listing `.parked.md` files (no ranking):
 

package/skills/manage-problem/test/manage-problem-verification-detection.bats

@@ -0,0 +1,64 @@
+#!/usr/bin/env bats
+# Doc-lint guard: manage-problem SKILL.md must surface Verification Pending
+# tickets whose fix path has been exercised in practice — the detection-layer
+# fix for P048. Minimal-scope candidates per P048:
+#   - Fix 1: step 9d always fires even on the fast-path cache hit.
+#   - Fix 4: step 9c / Verification Queue highlights tickets whose release
+#     age is >= 14 days as "likely verified" candidates.
+#
+# Candidates 2 (standalone verify-fixes op), 3 (exercise observations with a
+# new file-level state dimension), and 5 (AFK-mode hook) are deferred —
+# candidate 3 needs an ADR-scope decision per P048 investigation tasks.
+#
+# Structural assertion — Permitted Exception to the source-grep ban
+# (ADR-005 / P011).
+#
+# Cross-reference:
+#   P048: docs/problems/048-manage-problem-does-not-detect-verification-candidates.open.md
+#   ADR-022 (Verification Pending status): docs/decisions/022-problem-lifecycle-verification-pending-status.proposed.md
+#   ADR-013 Rule 1: docs/decisions/013-structured-user-interaction-for-governance-decisions.proposed.md
+#   @jtbd JTBD-001 (enforce governance without slowing down)
+#   @jtbd JTBD-006 (progress the backlog while I'm away)
+#   @jtbd JTBD-101 (extend the suite with clear patterns)
+
+setup() {
+  SKILL_DIR="$(cd "$(dirname "$BATS_TEST_FILENAME")/.." && pwd)"
+  SKILL_FILE="${SKILL_DIR}/SKILL.md"
+}
+
+@test "SKILL.md exists (P048 precondition)" {
+  [ -f "$SKILL_FILE" ]
+}
+
+@test "SKILL.md fast-path explicitly fires step 9d on cache hit (P048 Candidate 1)" {
+  # The fast-path currently reads: "Skip steps 9a-9b entirely / Proceed
+  # directly to step 9c". P048 reports step 9d being treated as skipped
+  # alongside 9a-9b. Fix: add explicit wording that step 9d fires even on
+  # cache hit, so verification candidates are always offered on review.
+  run grep -inE "step 9d.*(always fires?|still fires?|fires? (even|on) (cache|fast-path))|fast-path.*step 9d fires|cache hit.*step 9d" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}
+
+@test "SKILL.md step 9c Verification Queue highlights release-age candidates (P048 Candidate 4)" {
+  # Review output must surface Verification Pending tickets whose release
+  # age crosses a threshold as "likely verified" candidates. Accept either
+  # a literal "likely verified" callout OR an explicit age-based criterion
+  # (>= 14 days) in the Verification Queue presentation.
+  run grep -inE "likely verified|release age|age.*(>=|greater than|over|older than).*(days?|d)|stale verification" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}
+
+@test "SKILL.md step 9c Verification Queue documents the 14-day default threshold (P048 Candidate 4)" {
+  # The 14-day threshold is a within-skill default per architect review;
+  # the default must be named in the SKILL.md so implementations stay
+  # consistent until a policy-level decision moves it.
+  run grep -inE "14[ -]day|14 days|fourteen days" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}
+
+@test "SKILL.md cites P048 for the detection-layer extension" {
+  # Traceability: the SKILL.md must name the problem ticket this
+  # detection extension addresses so reviewers can chase history.
+  run grep -n "P048" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}