@windyroad/itil 0.44.1 → 0.44.2-preview.507

package/.claude-plugin/plugin.json

@@ -497,5 +497,5 @@
     }
   },
   "name": "wr-itil",
-  "version": "0.44.1"
+  "version": "0.44.2"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@windyroad/itil",
-  "version": "0.44.1",
+  "version": "0.44.2-preview.507",
   "description": "ITIL-aligned IT service management for Claude Code (problem, and future incident/change skills)",
   "bin": {
     "windyroad-itil": "./bin/install.mjs"
@@ -26,6 +26,7 @@
     "skills/",
     "scripts/",
     ".claude-plugin/",
-    "lib/"
+    "lib/",
+    "!skills/*/eval/"
   ]
 }

package/skills/manage-problem/SKILL.md

@@ -687,11 +687,23 @@ Update the "Status" field in the file to "Known Error".
 
 **Known Error → Verification Pending** (fix released, per ADR-022):
 
-When the fix for a Known Error ships, transition the ticket in a single commit:
+When the fix for a Known Error ships, transition the ticket in a single commit.
+
+**Seed `Release vehicle` reference BEFORE the rename (P330).** BEFORE the `git mv` to `.verifying.md`, edit the `.known-error.md` ticket body to append a `**Release vehicle**: .changeset/<name>.md` paragraph at the END of the `## Fix Strategy` section (create the section if absent). The `<name>.md` is the kebab-case slug of the changeset file the fix commit authored under `.changeset/` (e.g. `wr-itil-p330-option-b.md`). The seed eliminates the `wr-itil-derive-release-vehicle <NNN>` helper's exit-2 routing on standalone K→V iters — the helper greps the ticket body for `.changeset/<name>.md` and exits 2 when absent; seeding the reference at fix-ship time (when the changeset name is fresh in scope, since the fix commit just created it) makes the helper exit 0 deterministically on first call. The exit-2 recovery routing documented in `/wr-itil:transition-problem` Step 6 remains as the legacy-ticket fallback. Matches the user's documented workaround pattern across 3 of 4 standalone K→V dogfoods in the 2026-05-30 session (P316 / P281 / P302 — see P330 § Symptoms).
+
+> **Two P057 staging-trap windows on K→V (seed + rename).** The seed Edit on `.known-error.md` is the FIRST P057 window; the Edit that updates Status / writes `## Fix Released` AFTER the `git mv` is the SECOND. Consolidate staging into a SINGLE `git add docs/problems/<NNN>-<title>.verifying.md` AFTER both Edits + the `git mv`. `git mv` operates on the index entry — the body content the index references at rename time is the post-seed content, so the seed Edit's content is carried across the rename automatically; the single final `git add` re-stages the post-rename file with the post-`Edit` Status + `## Fix Released` content. The seed step does NOT introduce a separate `git add` of the `.known-error.md` path — staging discipline stays single-call by riding the rename's index entry.
 
 ```bash
+# Step 1 — seed `**Release vehicle**: .changeset/<name>.md` in the Fix Strategy section
+# ... use the Edit tool to append the seed paragraph to docs/problems/<NNN>-<title>.known-error.md ...
+
+# Step 2 — rename
 git mv docs/problems/<NNN>-<title>.known-error.md docs/problems/<NNN>-<title>.verifying.md
-# ... use the Edit tool to update Status and add the `## Fix Released` section ...
+
+# Step 3 — update Status + add `## Fix Released` section
+# ... use the Edit tool on docs/problems/<NNN>-<title>.verifying.md ...
+
+# Step 4 — single re-stage covers both Edit windows
 git add docs/problems/<NNN>-<title>.verifying.md
 ```
 
@@ -699,7 +711,7 @@ Then edit the file:
 - Update the "Status" field to "Verification Pending"
 - Add a `## Fix Released` section with: release marker (version, commit SHA, or date), one-sentence fix summary, "Awaiting user verification" line, and any exercise evidence from the releasing session.
 
-Re-stage the `.verifying.md` file explicitly after the `Edit` tool runs (P057). The second `git add` above is NOT redundant — `git mv` alone stages only the rename, not the subsequent content edit.
+Re-stage the `.verifying.md` file explicitly after the `Edit` tool runs (P057). The trailing `git add` above is NOT redundant — `git mv` alone stages only the rename, not the subsequent content edit; the same `git add` also re-stages the seed Edit content carried across the rename (single staging call, two Edit windows; P330 + P057).
 
 Both the `git mv` and the file edits belong in the same commit as the fix implementation per ADR-014 (governance skills commit their own work). The `.verifying.md` suffix signals to every downstream consumer (work-problems classifier, review step 9d, README rendering) that the remaining work is user-side verification — no file-body scan needed.
 

package/skills/manage-problem/test/manage-problem-release-vehicle-seed.bats

@@ -0,0 +1,83 @@
+#!/usr/bin/env bats
+# tdd-review: structural-permitted (justification: deferred-retrofit per P330 Investigation Task #3 — behavioural K→V-mock test deferred to follow-up commit; this structural backstop guards the SKILL prose carrying the Release-vehicle seed instruction in the meantime per ADR-052 § Surface 2 marker)
+#
+# Doc-lint guard: manage-problem SKILL.md Step 7 Known Error → Verification Pending block
+# must document the P330 Option B seed step that appends a `**Release vehicle**: .changeset/<name>.md`
+# paragraph to the ticket's Fix Strategy section BEFORE the `git mv` to `.verifying.md`.
+# The same instruction must be mirrored in `transition-problem` SKILL.md Step 6 per ADR-010 amended
+# (copy-not-move; P093 split-skill execution ownership).
+#
+# Cross-reference:
+#   P330: docs/problems/known-error/330-derive-release-vehicle-helper-requires-pre-edit-of-ticket-changeset-reference-three-touch-when-one-touch-would-suffice.md
+#   ADR-010: docs/decisions/010-rename-wr-problem-to-wr-itil.proposed.md (P093 amendment — copy-not-move)
+#   ADR-014: docs/decisions/014-governance-skills-commit-their-own-work.proposed.md (single-commit grain)
+#   ADR-022: docs/decisions/022-problem-lifecycle-verification-pending-status.proposed.md (Verifying status)
+#   ADR-052: docs/decisions/052-behavioural-tests-default-for-skill-testing.proposed.md (Surface 2 marker)
+#   @jtbd JTBD-002 (ship with confidence — audit trail self-documents the release vehicle)
+#   @jtbd JTBD-006 (progress backlog AFK — eliminates the 3-of-4-dogfoods exit-2 routing friction)
+
+setup() {
+  TEST_DIR="$(cd "$(dirname "$BATS_TEST_FILENAME")" && pwd)"
+  REPO_ROOT="$(cd "${TEST_DIR}/../../../../.." && pwd)"
+  MANAGE_PROBLEM_SKILL="${REPO_ROOT}/packages/itil/skills/manage-problem/SKILL.md"
+  TRANSITION_PROBLEM_SKILL="${REPO_ROOT}/packages/itil/skills/transition-problem/SKILL.md"
+}
+
+@test "manage-problem SKILL.md exists (P330 precondition)" {
+  [ -f "$MANAGE_PROBLEM_SKILL" ]
+}
+
+@test "transition-problem SKILL.md exists (P330 precondition)" {
+  [ -f "$TRANSITION_PROBLEM_SKILL" ]
+}
+
+@test "manage-problem SKILL.md Step 7 documents the Release vehicle seed step (P330)" {
+  # The K→V transition block must instruct authors to seed a `**Release vehicle**: .changeset/<name>.md`
+  # paragraph in the ticket's `## Fix Strategy` section BEFORE the `git mv` to `.verifying.md`.
+  run grep -inE 'Release vehicle.*\.changeset/' "$MANAGE_PROBLEM_SKILL"
+  [ "$status" -eq 0 ]
+}
+
+@test "manage-problem SKILL.md Step 7 seed instruction precedes the K→V git mv (P330)" {
+  # Verify ordering: the "Seed `Release vehicle`" instruction must appear BEFORE the
+  # `git mv ... .known-error.md ... .verifying.md` block in Step 7. If the seed instruction
+  # lands AFTER the rename in the prose, the agent reading top-to-bottom would do the
+  # rename first and the seed-on-known-error-path would target a non-existent file.
+  seed_line=$(grep -nE 'Seed `Release vehicle` reference BEFORE the rename' "$MANAGE_PROBLEM_SKILL" | head -1 | cut -d: -f1)
+  rename_line=$(grep -nE 'git mv docs/problems/<NNN>-<title>\.known-error\.md docs/problems/<NNN>-<title>\.verifying\.md' "$MANAGE_PROBLEM_SKILL" | head -1 | cut -d: -f1)
+  [ -n "$seed_line" ]
+  [ -n "$rename_line" ]
+  [ "$seed_line" -lt "$rename_line" ]
+}
+
+@test "manage-problem SKILL.md Step 7 cites P330 on the seed instruction (P330 traceability)" {
+  # The seed instruction must cite P330 so reviewers can chase the rationale.
+  run grep -nE 'P330' "$MANAGE_PROBLEM_SKILL"
+  [ "$status" -eq 0 ]
+}
+
+@test "manage-problem SKILL.md Step 7 documents the two P057 staging-trap windows (seed + rename)" {
+  # The amendment introduces a second Edit-tool window (seed Edit on .known-error.md).
+  # The SKILL prose must explicitly call out that the existing single-`git add` shape covers
+  # BOTH windows by riding the rename's index entry.
+  run grep -inE 'Two P057 staging-trap windows|two .* Edit windows|seed Edit.*FIRST.*P057' "$MANAGE_PROBLEM_SKILL"
+  [ "$status" -eq 0 ]
+}
+
+@test "transition-problem SKILL.md Step 6 mirrors the Release vehicle seed step (ADR-010 copy-not-move)" {
+  # Per ADR-010 amended (P093 split-skill execution ownership), the manage-problem Step 7
+  # block and the transition-problem Step 6 block must stay in sync. Both surfaces are user-
+  # initiated K→V entry points (manage-problem fold-fix path + transition-problem standalone path).
+  run grep -inE 'Release vehicle.*\.changeset/' "$TRANSITION_PROBLEM_SKILL"
+  [ "$status" -eq 0 ]
+}
+
+@test "transition-problem SKILL.md Step 6 cites P330 on the seed instruction (ADR-010 copy-not-move)" {
+  run grep -nE 'P330' "$TRANSITION_PROBLEM_SKILL"
+  [ "$status" -eq 0 ]
+}
+
+@test "transition-problem SKILL.md Step 6 documents the two P057 staging-trap windows (seed + rename)" {
+  run grep -inE 'Two P057 staging-trap windows|two .* Edit windows|seed Edit.*FIRST.*P057' "$TRANSITION_PROBLEM_SKILL"
+  [ "$status" -eq 0 ]
+}

package/skills/transition-problem/SKILL.md

@@ -147,9 +147,21 @@ git add docs/problems/<NNN>-<title>.known-error.md
 
 **Known Error → Verification Pending** (per ADR-022, on release):
 
+**Seed `Release vehicle` reference BEFORE the rename (P330).** BEFORE the `git mv` to `.verifying.md`, edit the `.known-error.md` ticket body to append a `**Release vehicle**: .changeset/<name>.md` paragraph at the END of the `## Fix Strategy` section (create the section if absent). The `<name>.md` is the kebab-case slug of the changeset file the fix commit authored under `.changeset/` (e.g. `wr-itil-p330-option-b.md`). The seed makes the `wr-itil-derive-release-vehicle <NNN>` helper invocation below exit 0 deterministically on first call (the helper greps the ticket body for `.changeset/<name>.md` and exits 2 when absent — Option B-codified per P330 closes that exit-2 routing on standalone K→V iters). The exit-2 fallback in the routing table below remains as the legacy-ticket recovery path for tickets shipped before P330's codification. Mirrors the `/wr-itil:manage-problem` Step 7 seed step (copy-not-move per ADR-010 amended / P093).
+
+> **Two P057 staging-trap windows on K→V (seed + rename).** The seed Edit on `.known-error.md` is the FIRST P057 window; the Edit that updates Status / writes `## Fix Released` AFTER the `git mv` is the SECOND. Consolidate staging into a SINGLE `git add docs/problems/<NNN>-<title>.verifying.md` AFTER both Edits + the `git mv`. `git mv` operates on the index entry — the body content the index references at rename time is the post-seed content, so the seed Edit's content is carried across the rename automatically; the single final `git add` re-stages the post-rename file with the post-`Edit` Status + `## Fix Released` content. The seed step does NOT introduce a separate `git add` of the `.known-error.md` path — staging discipline stays single-call by riding the rename's index entry.
+
 ```bash
+# Step 1 — seed `**Release vehicle**: .changeset/<name>.md` in the Fix Strategy section
+# ... use the Edit tool to append the seed paragraph to docs/problems/<NNN>-<title>.known-error.md ...
+
+# Step 2 — rename
 git mv docs/problems/<NNN>-<title>.known-error.md docs/problems/<NNN>-<title>.verifying.md
-# ... use the Edit tool to update Status to "Verification Pending" AND add the `## Fix Released` section ...
+
+# Step 3 — update Status to "Verification Pending" AND add the `## Fix Released` section
+# ... use the Edit tool on docs/problems/<NNN>-<title>.verifying.md ...
+
+# Step 4 — single re-stage covers both Edit windows (P057 + P330)
 git add docs/problems/<NNN>-<title>.verifying.md
 ```