@windyroad/itil 2.1.7 → 2.1.8-preview.1160

package/.claude-plugin/plugin.json

@@ -497,5 +497,5 @@
     }
   },
   "name": "wr-itil",
-  "version": "2.1.7"
+  "version": "2.1.8"
 }

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "wr-itil",
-  "version": "2.1.7",
+  "version": "2.1.8",
   "description": "ITIL problem-management workflows for AI coding agents",
   "author": {
     "name": "Windy Road Technology",

package/lib/enumerate-postrelease-kv-candidates.sh

@@ -83,6 +83,18 @@ enumerate_postrelease_kv_candidates() {
 
     case "$derive_exit" in
       0)
+        local reopened_date release_date
+        reopened_date="$(grep -oE '^## Reopened [0-9]{4}-[0-9]{2}-[0-9]{2}$' "$f" \
+          | sed 's/^## Reopened //' \
+          | tail -1)"
+        release_date="$(printf '%s\n' "$derive_out" \
+          | sed -n 's/^[[:space:]]*release-date:[[:space:]]*//p' \
+          | head -1)"
+        if [ -n "$reopened_date" ] && [ -n "$release_date" ] \
+          && [[ "$reopened_date" > "$release_date" ]]; then
+          continue
+        fi
+
         local changeset
         changeset="$(printf '%s\n' "$derive_out" \
           | grep -oE '\.changeset/[a-z0-9._-]+\.md' \

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@windyroad/itil",
-  "version": "2.1.7",
+  "version": "2.1.8-preview.1160",
   "description": "ITIL-aligned IT service management for Claude Code and Codex",
   "bin": {
     "windyroad-itil": "./bin/install.mjs"

package/skills/transition-problem/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wr-itil:transition-problem
-description: "Advance a problem ticket's lifecycle status — Open → Known Error, Known Error → Verification Pending (verifying), Verification Pending → Closed. Renames the ticket file, updates the Status field, and refreshes docs/problems/README.md in the same commit. Hosts the transition execution inline (pre-flight checks, the \"Problem 057: `git mv` + Edit + `git add` staging-ordering trap drops content edits from the commit\" problem staging-trap handling, the \"Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external\" problem external-root-cause detection, the \"Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently\" problem README refresh, the \"Governance Skills Commit Their Own Completed Work\" architecture rule commit) per the \"Rename `wr-problem` Plugin to `wr-itil`\" architecture rule amended \"Split-skill execution ownership\". Use when the user asks to \"transition\", \"close\", \"mark known-error\", or \"release\" a specific ticket."
+description: "Advance a problem ticket's lifecycle status — Open → Known Error, Open or Known Error → Verification Pending (verifying), Verification Pending → Closed. Renames the ticket file, updates the Status field, and refreshes docs/problems/README.md in the same commit. Hosts the transition execution inline (pre-flight checks, the \"Problem 057: `git mv` + Edit + `git add` staging-ordering trap drops content edits from the commit\" problem staging-trap handling, the \"Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external\" problem external-root-cause detection, the \"Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently\" problem README refresh, the \"Governance Skills Commit Their Own Completed Work\" architecture rule commit) per the \"Rename `wr-problem` Plugin to `wr-itil`\" architecture rule amended \"Split-skill execution ownership\". Use when the user asks to \"transition\", \"close\", \"mark known-error\", or \"release\" a specific ticket."
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, Skill
 ---
 
@@ -25,7 +25,7 @@ The `<NNN>` and `<status>` tokens are **data parameters**, not word-subcommands.
 ## Scope
 
 **In scope:**
-- Validate that the ticket file exists and the destination status is reachable from the current status (e.g. an `.open.md` file cannot transition directly to Verification Pending — it must go through Known Error first).
+- Validate that the ticket file exists and the destination status is reachable from the current status, including the "Problem lifecycle — add a Verification Pending status between Known Error and Closed" architecture rule's folded Open → Verification Pending route when both stages' checks pass inline.
 - Execute the transition inline: pre-flight checks, the "Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external" problem external-root-cause detection (for the Open → Known Error destination), `git mv` to the new suffix, Status field edit, `## Fix Released` section write (for the Known Error → Verification Pending destination), the "Problem 057: `git mv` + Edit + `git add` staging-ordering trap drops content edits from the commit" problem staging re-stage, the "Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently" problem README.md refresh, the "Governance Skills Commit Their Own Completed Work" architecture rule commit.
 - Report the outcome (new filename, new Status, commit SHA).
 
@@ -66,6 +66,7 @@ Check the current filename suffix and verify the destination status is reachable
 | Current suffix | Destination argument | Valid? |
 |----------------|----------------------|--------|
 | `.open.md` | `known-error` | yes |
+| `.open.md` | `verifying` | yes — **fix on capture**: the "Problem lifecycle — add a Verification Pending status between Known Error and Closed" architecture rule folds both forward stages only when the composed pre-flight below passes. |
 | `.known-error.md` | `verifying` | yes |
 | `.verifying.md` | `close` | yes |
 | `.verifying.md` | `known-error` | yes — **flip-back**: the fix recurred or proved incomplete. Required by `review-problems` Bucket 3, `manage-problem`, and `run-retro` Step 4a, all of which already instruct it. |
@@ -95,6 +96,8 @@ Destination-specific pre-flight checks gate the transition. If any check fails,
 - [ ] A release marker is available (version, commit SHA, or date) so the `## Fix Released` section can name it
 - [ ] **Conditional-deferral check (the "Agent treats conditionally-deferred work (deferred-pending-X-graduation) as permanently out of scope — prematurely transitions parent ticket when X graduates" problem)** — see the dedicated subsection below; halt the transition if any conditional deferral has lifted with unticked work remaining
 
+**Open → Verification Pending** (`<status>` = `verifying`) requires all **Open → Known Error** checks, all **Known Error → Verification Pending** checks, and a populated objective `## Fix Released` section. This is the "Problem lifecycle — add a Verification Pending status between Known Error and Closed" architecture rule's fix-on-capture fold, not a pre-flight bypass: root cause, investigation, reproduction, workaround, effort/WSJF, implementation, release marker, and conditional-deferral checks all run before the single rename. The `## Fix Released` section must name the released version, commit SHA, or date; the heading alone does not satisfy the route.
+
 #### Conditional-deferral check on K→V (the "Agent treats conditionally-deferred work (deferred-pending-X-graduation) as permanently out of scope — prematurely transitions parent ticket when X graduates" problem) — copy-not-move sibling
 
 This subsection is the **copy-not-move sibling** of `/wr-itil:manage-problem` SKILL.md Step 7's "Conditional-deferral check BEFORE the rename (the "Agent treats conditionally-deferred work (deferred-pending-X-graduation) as permanently out of scope — prematurely transitions parent ticket when X graduates" problem)" block per [the "Rename `wr-problem` Plugin to `wr-itil`" architecture rule](../../../docs/decisions/010-rename-wr-problem-to-wr-itil.proposed.md) amended "Split-skill execution ownership" rule (the "Problem 093: `/wr-itil:transition-problem` ↔ `/wr-itil:manage-problem` circular delegation for `<NNN> <status>` args" problem). Both surfaces must carry the check; drift between the two copies re-opens the "Agent treats conditionally-deferred work (deferred-pending-X-graduation) as permanently out of scope — prematurely transitions parent ticket when X graduates" problem's silent-loss failure mode on whichever surface lacks the check.
@@ -224,6 +227,15 @@ git mv docs/problems/known-error/<NNN>-<title>.md docs/problems/verifying/<NNN>-
 git add docs/problems/verifying/<NNN>-<title>.md
 ```
 
+**Open → Verification Pending** (the "Problem lifecycle — add a Verification Pending status between Known Error and Closed" architecture rule fix-on-capture fold):
+
+```bash
+git mv docs/problems/open/<NNN>-<title>.md docs/problems/verifying/<NNN>-<title>.md
+# Edit Status to "Verification Pending" and preserve the populated
+# ## Fix Released section that passed the composed pre-flight.
+git add docs/problems/verifying/<NNN>-<title>.md
+```
+
 The `## Fix Released` section contains: release marker (version, commit SHA, or date), one-sentence fix summary, "Awaiting user verification" line, and any exercise evidence from the releasing session. The `.verifying.md` suffix signals to every downstream consumer (work-problems classifier, review step 9d, README rendering) that the remaining work is verification — by evidence or by the user — no file-body scan needed.
 
 When this transition is folded into a `fix(<scope>): ... (closes P<NNN>)` commit (the common case), the `git mv` + `Edit` + re-stage + README refresh all join that single commit — never split across commits.
@@ -357,7 +369,7 @@ Release draining is owned by the caller — `/wr-itil:manage-problem` Step 12 (i
 `transition-problem` owns (for the user-initiated transition path):
 - Argument parsing (`<NNN> <status>`).
 - Ticket-file discovery via the dual-tolerant lookup `ls docs/problems/<NNN>-*.md docs/problems/*/<NNN>-*.md` (the ": docs/problems/ flat layout migration — per-state subdirs + adopter auto-migration" release design transitional shape; both layouts).
-- Destination-reachability validation (Open → Known Error → Verification Pending → Closed, one step at a time).
+- Destination-reachability validation (ordinary one-step transitions plus the "Problem lifecycle — add a Verification Pending status between Known Error and Closed" architecture rule's composed Open → Verification Pending fix-on-capture fold).
 - Pre-flight checks for the supplied destination.
 - the "Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external" problem external-root-cause detection (Open → Known Error only) — including the AFK fallback that appends the stable `- **Upstream report pending** —` marker.
 - `git mv` rename + Status field edit + (for `verifying`) `## Fix Released` section write + explicit the "Problem 057: `git mv` + Edit + `git add` staging-ordering trap drops content edits from the commit" problem re-stage.

package/skills/transition-problems/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wr-itil:transition-problems
-description: "Batch-advance multiple problem tickets through the lifecycle in one invocation — Open → Known Error, Known Error → Verification Pending, Verification Pending → Closed. Loops the per-ticket /wr-itil:transition-problem mechanic (rename, Status edit, the \"Problem 057: `git mv` + Edit + `git add` staging-ordering trap drops content edits from the commit\" problem re-stage, the \"Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external\" problem external-root-cause detection, the \"Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently\" problem README refresh) without paying N× SKILL.md reload latency or violating split-skill execution ownership. Produces ONE shared commit covering all surviving transitions per the \"Governance Skills Commit Their Own Completed Work\" architecture rule batch-grain. Use when closing the Verification Queue at the end of a `/wr-retrospective:run-retro` Step 4a pass, batch-closing release-aged verifyings during `/wr-itil:work-problems` AFK orchestration, or confirming multiple Step 9d verifications in `/wr-itil:manage-problem review`. Singular sibling — `/wr-itil:transition-problem` (one ticket per invocation)."
+description: "Batch-advance multiple problem tickets through the lifecycle in one invocation — Open → Known Error, Open or Known Error → Verification Pending, Verification Pending → Closed. Loops the per-ticket /wr-itil:transition-problem mechanic (rename, Status edit, the \"Problem 057: `git mv` + Edit + `git add` staging-ordering trap drops content edits from the commit\" problem re-stage, the \"Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external\" problem external-root-cause detection, the \"Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently\" problem README refresh) without paying N× SKILL.md reload latency or violating split-skill execution ownership. Produces ONE shared commit covering all surviving transitions per the \"Governance Skills Commit Their Own Completed Work\" architecture rule batch-grain. Use when closing the Verification Queue at the end of a `/wr-retrospective:run-retro` Step 4a pass, batch-closing release-aged verifyings during `/wr-itil:work-problems` AFK orchestration, or confirming multiple Step 9d verifications in `/wr-itil:manage-problem review`. Singular sibling — `/wr-itil:transition-problem` (one ticket per invocation)."
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, Skill, Agent
 ---
 
@@ -98,6 +98,7 @@ If no file is found OR multiple files are found (suffix-exclusive lifecycle viol
 | Current suffix | `<status>` | Valid? |
 |----------------|------------|--------|
 | `.open.md` | `known-error` | yes |
+| `.open.md` | `verifying` | yes — **fix on capture**: the "Problem lifecycle — add a Verification Pending status between Known Error and Closed" architecture rule folds both forward stages only when the composed pre-flight below passes. |
 | `.known-error.md` | `verifying` | yes |
 | `.verifying.md` | `close` | yes |
 | `.verifying.md` | `known-error` | yes — **flip-back**: the fix recurred or proved incomplete. `review-problems` Bucket 3 already instructs this and had no batch path. |
@@ -110,6 +111,7 @@ Lockstep with `/wr-itil:transition-problem` Step 3 per the drift clause below
 
 - Open → Known Error (`known-error`): root cause documented; ≥ 1 investigation task ticked; reproduction test or reference; workaround documented; effort bucket re-rated if scope shifted (the "Problem 047: WSJF effort buckets are coarse and not re-rated at lifecycle transitions" problem); status multiplier re-rated from Open 1.0 to Known Error 2.0 and WSJF recomputed with the post-transition status and current Effort (the "WSJF uses the pre-transition status multiplier" problem).
 - Known Error → Verification Pending (`verifying`): fix implemented; release marker available (version, commit SHA, or date) for the `## Fix Released` section.
+- Open → Verification Pending (`verifying`): all Open → Known Error checks and all Known Error → Verification Pending checks above pass inline, including the conditional-deferral check, and the ticket has a populated objective `## Fix Released` section naming a version, commit SHA, or date. The heading alone is insufficient.
 - Verification Pending → Closed (`close`): cited observed evidence or explicit user confirmation authorizes closure. Evidence-backed closure is mechanical and does not require another question. Record the citation and recovery path (`/wr-itil:transition-problem <NNN> known-error`) in each ticket's Status line. A provenance-proven GitHub issue on this project's tracker receives the gated comment and closes; unresolved or non-issue inbound provenance performs no issue mutation. A foreign issue receives the comment but stays open on local evidence alone; that upstream party's confirmation may authorize closure. Pull requests remain comment-only.
 
   **Never close on inference** — absence of evidence is not evidence. A pair whose ticket carries no citation records as `pre-flight-failed` with reason `no-evidence` and stays Verification Pending; age, plausibility, and "the fix is on disk" are not observations. **Do-not-close marker check** — run `wr-itil-is-close-blocked <NNN> docs/problems` per pair before closing. Exit 0 → record the pair as `pre-flight-failed` with reason `close-blocked` plus the matched marker line, and continue to the next pair; do NOT close it whatever the evidence says. Exit 2 (unresolvable ref) is a pre-flight failure, not permission.
@@ -154,6 +156,14 @@ git mv docs/problems/known-error/<NNN>-<title>.md docs/problems/verifying/<NNN>-
 git add docs/problems/verifying/<NNN>-<title>.md
 ```
 
+```bash
+# Open → Verification Pending (the "Problem lifecycle — add a Verification Pending status between Known Error and Closed" architecture rule fix-on-capture fold)
+git mv docs/problems/open/<NNN>-<title>.md docs/problems/verifying/<NNN>-<title>.md
+# Edit Status to "Verification Pending" and preserve the populated
+# ## Fix Released section that passed the composed pre-flight.
+git add docs/problems/verifying/<NNN>-<title>.md
+```
+
 ```bash
 # Verification Pending → Closed
 git mv docs/problems/verifying/<NNN>-<title>.md docs/problems/closed/<NNN>-<title>.md

package/skills-codex/transition-problem/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: transition-problem
-description: "Advance a problem ticket's lifecycle status — Open → Known Error, Known Error → Verification Pending (verifying), Verification Pending → Closed. Renames the ticket file, updates the Status field, and refreshes docs/problems/README.md in the same commit. Hosts the transition execution inline (pre-flight checks, the \"Problem 057: `git mv` + Edit + `git add` staging-ordering trap drops content edits from the commit\" problem staging-trap handling, the \"Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external\" problem external-root-cause detection, the \"Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently\" problem README refresh, the \"Governance Skills Commit Their Own Completed Work\" architecture rule commit) per the \"Rename `wr-problem` Plugin to `wr-itil`\" architecture rule amended \"Split-skill execution ownership\". Use when the user asks to \"transition\", \"close\", \"mark known-error\", or \"release\" a specific ticket."
+description: "Advance a problem ticket's lifecycle status — Open → Known Error, Open or Known Error → Verification Pending (verifying), Verification Pending → Closed. Renames the ticket file, updates the Status field, and refreshes docs/problems/README.md in the same commit. Hosts the transition execution inline (pre-flight checks, the \"Problem 057: `git mv` + Edit + `git add` staging-ordering trap drops content edits from the commit\" problem staging-trap handling, the \"Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external\" problem external-root-cause detection, the \"Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently\" problem README refresh, the \"Governance Skills Commit Their Own Completed Work\" architecture rule commit) per the \"Rename `wr-problem` Plugin to `wr-itil`\" architecture rule amended \"Split-skill execution ownership\". Use when the user asks to \"transition\", \"close\", \"mark known-error\", or \"release\" a specific ticket."
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, request_user_input, Skill
 ---
 
@@ -36,7 +36,7 @@ The `<NNN>` and `<status>` tokens are **data parameters**, not word-subcommands.
 ## Scope
 
 **In scope:**
-- Validate that the ticket file exists and the destination status is reachable from the current status (e.g. an `.open.md` file cannot transition directly to Verification Pending — it must go through Known Error first).
+- Validate that the ticket file exists and the destination status is reachable from the current status, including the "Problem lifecycle — add a Verification Pending status between Known Error and Closed" architecture rule's folded Open → Verification Pending route when both stages' checks pass inline.
 - Execute the transition inline: pre-flight checks, the "Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external" problem external-root-cause detection (for the Open → Known Error destination), `git mv` to the new suffix, Status field edit, `## Fix Released` section write (for the Known Error → Verification Pending destination), the "Problem 057: `git mv` + Edit + `git add` staging-ordering trap drops content edits from the commit" problem staging re-stage, the "Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently" problem README.md refresh, the "Governance Skills Commit Their Own Completed Work" architecture rule commit.
 - Report the outcome (new filename, new Status, commit SHA).
 
@@ -77,6 +77,7 @@ Check the current filename suffix and verify the destination status is reachable
 | Current suffix | Destination argument | Valid? |
 |----------------|----------------------|--------|
 | `.open.md` | `known-error` | yes |
+| `.open.md` | `verifying` | yes — **fix on capture**: the "Problem lifecycle — add a Verification Pending status between Known Error and Closed" architecture rule folds both forward stages only when the composed pre-flight below passes. |
 | `.known-error.md` | `verifying` | yes |
 | `.verifying.md` | `close` | yes |
 | `.verifying.md` | `known-error` | yes — **flip-back**: the fix recurred or proved incomplete. Required by `review-problems` Bucket 3, `manage-problem`, and `run-retro` Step 4a, all of which already instruct it. |
@@ -106,6 +107,8 @@ Destination-specific pre-flight checks gate the transition. If any check fails,
 - [ ] A release marker is available (version, commit SHA, or date) so the `## Fix Released` section can name it
 - [ ] **Conditional-deferral check (the "Agent treats conditionally-deferred work (deferred-pending-X-graduation) as permanently out of scope — prematurely transitions parent ticket when X graduates" problem)** — see the dedicated subsection below; halt the transition if any conditional deferral has lifted with unticked work remaining
 
+**Open → Verification Pending** (`<status>` = `verifying`) requires all **Open → Known Error** checks, all **Known Error → Verification Pending** checks, and a populated objective `## Fix Released` section. This is the "Problem lifecycle — add a Verification Pending status between Known Error and Closed" architecture rule's fix-on-capture fold, not a pre-flight bypass: root cause, investigation, reproduction, workaround, effort/WSJF, implementation, release marker, and conditional-deferral checks all run before the single rename. The `## Fix Released` section must name the released version, commit SHA, or date; the heading alone does not satisfy the route.
+
 #### Conditional-deferral check on K→V (the "Agent treats conditionally-deferred work (deferred-pending-X-graduation) as permanently out of scope — prematurely transitions parent ticket when X graduates" problem) — copy-not-move sibling
 
 This subsection is the **copy-not-move sibling** of `/wr-itil:manage-problem` SKILL.md Step 7's "Conditional-deferral check BEFORE the rename (the "Agent treats conditionally-deferred work (deferred-pending-X-graduation) as permanently out of scope — prematurely transitions parent ticket when X graduates" problem)" block per [the "Rename `wr-problem` Plugin to `wr-itil`" architecture rule](../../../docs/decisions/010-rename-wr-problem-to-wr-itil.proposed.md) amended "Split-skill execution ownership" rule (the "Problem 093: `/wr-itil:transition-problem` ↔ `/wr-itil:manage-problem` circular delegation for `<NNN> <status>` args" problem). Both surfaces must carry the check; drift between the two copies re-opens the "Agent treats conditionally-deferred work (deferred-pending-X-graduation) as permanently out of scope — prematurely transitions parent ticket when X graduates" problem's silent-loss failure mode on whichever surface lacks the check.
@@ -235,6 +238,15 @@ git mv docs/problems/known-error/<NNN>-<title>.md docs/problems/verifying/<NNN>-
 git add docs/problems/verifying/<NNN>-<title>.md
 ```
 
+**Open → Verification Pending** (the "Problem lifecycle — add a Verification Pending status between Known Error and Closed" architecture rule fix-on-capture fold):
+
+```bash
+git mv docs/problems/open/<NNN>-<title>.md docs/problems/verifying/<NNN>-<title>.md
+# Edit Status to "Verification Pending" and preserve the populated
+# ## Fix Released section that passed the composed pre-flight.
+git add docs/problems/verifying/<NNN>-<title>.md
+```
+
 The `## Fix Released` section contains: release marker (version, commit SHA, or date), one-sentence fix summary, "Awaiting user verification" line, and any exercise evidence from the releasing session. The `.verifying.md` suffix signals to every downstream consumer (work-problems classifier, review step 9d, README rendering) that the remaining work is verification — by evidence or by the user — no file-body scan needed.
 
 When this transition is folded into a `fix(<scope>): ... (closes P<NNN>)` commit (the common case), the `git mv` + `Edit` + re-stage + README refresh all join that single commit — never split across commits.
@@ -368,7 +380,7 @@ Release draining is owned by the caller — `/wr-itil:manage-problem` Step 12 (i
 `transition-problem` owns (for the user-initiated transition path):
 - Argument parsing (`<NNN> <status>`).
 - Ticket-file discovery via the dual-tolerant lookup `ls docs/problems/<NNN>-*.md docs/problems/*/<NNN>-*.md` (the ": docs/problems/ flat layout migration — per-state subdirs + adopter auto-migration" release design transitional shape; both layouts).
-- Destination-reachability validation (Open → Known Error → Verification Pending → Closed, one step at a time).
+- Destination-reachability validation (ordinary one-step transitions plus the "Problem lifecycle — add a Verification Pending status between Known Error and Closed" architecture rule's composed Open → Verification Pending fix-on-capture fold).
 - Pre-flight checks for the supplied destination.
 - the "Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external" problem external-root-cause detection (Open → Known Error only) — including the AFK fallback that appends the stable `- **Upstream report pending** —` marker.
 - `git mv` rename + Status field edit + (for `verifying`) `## Fix Released` section write + explicit the "Problem 057: `git mv` + Edit + `git add` staging-ordering trap drops content edits from the commit" problem re-stage.

package/skills-codex/transition-problems/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: transition-problems
-description: "Batch-advance multiple problem tickets through the lifecycle in one invocation — Open → Known Error, Known Error → Verification Pending, Verification Pending → Closed. Loops the per-ticket /wr-itil:transition-problem mechanic (rename, Status edit, the \"Problem 057: `git mv` + Edit + `git add` staging-ordering trap drops content edits from the commit\" problem re-stage, the \"Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external\" problem external-root-cause detection, the \"Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently\" problem README refresh) without paying N× SKILL.md reload latency or violating split-skill execution ownership. Produces ONE shared commit covering all surviving transitions per the \"Governance Skills Commit Their Own Completed Work\" architecture rule batch-grain. Use when closing the Verification Queue at the end of a `/wr-retrospective:run-retro` Step 4a pass, batch-closing release-aged verifyings during `/wr-itil:work-problems` AFK orchestration, or confirming multiple Step 9d verifications in `/wr-itil:manage-problem review`. Singular sibling — `/wr-itil:transition-problem` (one ticket per invocation)."
+description: "Batch-advance multiple problem tickets through the lifecycle in one invocation — Open → Known Error, Open or Known Error → Verification Pending, Verification Pending → Closed. Loops the per-ticket /wr-itil:transition-problem mechanic (rename, Status edit, the \"Problem 057: `git mv` + Edit + `git add` staging-ordering trap drops content edits from the commit\" problem re-stage, the \"Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external\" problem external-root-cause detection, the \"Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently\" problem README refresh) without paying N× SKILL.md reload latency or violating split-skill execution ownership. Produces ONE shared commit covering all surviving transitions per the \"Governance Skills Commit Their Own Completed Work\" architecture rule batch-grain. Use when closing the Verification Queue at the end of a `/wr-retrospective:run-retro` Step 4a pass, batch-closing release-aged verifyings during `/wr-itil:work-problems` AFK orchestration, or confirming multiple Step 9d verifications in `/wr-itil:manage-problem review`. Singular sibling — `/wr-itil:transition-problem` (one ticket per invocation)."
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, request_user_input, Skill, Agent
 ---
 
@@ -109,6 +109,7 @@ If no file is found OR multiple files are found (suffix-exclusive lifecycle viol
 | Current suffix | `<status>` | Valid? |
 |----------------|------------|--------|
 | `.open.md` | `known-error` | yes |
+| `.open.md` | `verifying` | yes — **fix on capture**: the "Problem lifecycle — add a Verification Pending status between Known Error and Closed" architecture rule folds both forward stages only when the composed pre-flight below passes. |
 | `.known-error.md` | `verifying` | yes |
 | `.verifying.md` | `close` | yes |
 | `.verifying.md` | `known-error` | yes — **flip-back**: the fix recurred or proved incomplete. `review-problems` Bucket 3 already instructs this and had no batch path. |
@@ -121,6 +122,7 @@ Lockstep with `/wr-itil:transition-problem` Step 3 per the drift clause below
 
 - Open → Known Error (`known-error`): root cause documented; ≥ 1 investigation task ticked; reproduction test or reference; workaround documented; effort bucket re-rated if scope shifted (the "Problem 047: WSJF effort buckets are coarse and not re-rated at lifecycle transitions" problem); status multiplier re-rated from Open 1.0 to Known Error 2.0 and WSJF recomputed with the post-transition status and current Effort (the "WSJF uses the pre-transition status multiplier" problem).
 - Known Error → Verification Pending (`verifying`): fix implemented; release marker available (version, commit SHA, or date) for the `## Fix Released` section.
+- Open → Verification Pending (`verifying`): all Open → Known Error checks and all Known Error → Verification Pending checks above pass inline, including the conditional-deferral check, and the ticket has a populated objective `## Fix Released` section naming a version, commit SHA, or date. The heading alone is insufficient.
 - Verification Pending → Closed (`close`): cited observed evidence or explicit user confirmation authorizes closure. Evidence-backed closure is mechanical and does not require another question. Record the citation and recovery path (`/wr-itil:transition-problem <NNN> known-error`) in each ticket's Status line. A provenance-proven GitHub issue on this project's tracker receives the gated comment and closes; unresolved or non-issue inbound provenance performs no issue mutation. A foreign issue receives the comment but stays open on local evidence alone; that upstream party's confirmation may authorize closure. Pull requests remain comment-only.
 
   **Never close on inference** — absence of evidence is not evidence. A pair whose ticket carries no citation records as `pre-flight-failed` with reason `no-evidence` and stays Verification Pending; age, plausibility, and "the fix is on disk" are not observations. **Do-not-close marker check** — run `<itil-plugin-root>/bin/wr-itil-is-close-blocked <NNN> docs/problems` per pair before closing. Exit 0 → record the pair as `pre-flight-failed` with reason `close-blocked` plus the matched marker line, and continue to the next pair; do NOT close it whatever the evidence says. Exit 2 (unresolvable ref) is a pre-flight failure, not permission.
@@ -165,6 +167,14 @@ git mv docs/problems/known-error/<NNN>-<title>.md docs/problems/verifying/<NNN>-
 git add docs/problems/verifying/<NNN>-<title>.md
 ```
 
+```bash
+# Open → Verification Pending (the "Problem lifecycle — add a Verification Pending status between Known Error and Closed" architecture rule fix-on-capture fold)
+git mv docs/problems/open/<NNN>-<title>.md docs/problems/verifying/<NNN>-<title>.md
+# Edit Status to "Verification Pending" and preserve the populated
+# ## Fix Released section that passed the composed pre-flight.
+git add docs/problems/verifying/<NNN>-<title>.md
+```
+
 ```bash
 # Verification Pending → Closed
 git mv docs/problems/verifying/<NNN>-<title>.md docs/problems/closed/<NNN>-<title>.md