@windyroad/itil 1.2.0 → 2.0.0-preview.1111

package/.agents/plugins/marketplace.json

@@ -0,0 +1,12 @@
+{
+  "name": "windyroad-itil-local",
+  "interface": { "displayName": "Windy Road ITIL" },
+  "plugins": [
+    {
+      "name": "wr-itil",
+      "source": { "source": "local", "path": "." },
+      "policy": { "installation": "AVAILABLE", "authentication": "ON_INSTALL" },
+      "category": "Developer Tools"
+    }
+  ]
+}

package/.claude-plugin/plugin.json

@@ -497,5 +497,5 @@
     }
   },
   "name": "wr-itil",
-  "version": "1.2.0"
+  "version": "2.0.0"
 }

package/.codex-plugin/plugin.json

@@ -0,0 +1,42 @@
+{
+  "name": "wr-itil",
+  "version": "2.0.0",
+  "description": "ITIL problem-management workflows for AI coding agents",
+  "author": {
+    "name": "Windy Road Technology",
+    "url": "https://windyroad.com.au"
+  },
+  "homepage": "https://github.com/windyroad/agent-plugins/tree/main/packages/itil",
+  "repository": "https://github.com/windyroad/agent-plugins",
+  "license": "MIT",
+  "keywords": [
+    "itil",
+    "problem-management",
+    "governance",
+    "codex",
+    "claude-code"
+  ],
+  "skills": "./skills-codex/",
+  "interface": {
+    "displayName": "Windy Road ITIL",
+    "shortDescription": "Manage ITIL problems, incidents, RFCs, stories, and maps",
+    "longDescription": "Complete ITIL workflow support for Codex: capture, prioritise, investigate, transition, review, reconcile, and report service-management records.",
+    "developerName": "Windy Road Technology",
+    "category": "Developer Tools",
+    "capabilities": [
+      "Interactive",
+      "Read",
+      "Write"
+    ],
+    "websiteURL": "https://windyroad.com.au",
+    "privacyPolicyURL": "https://windyroad.com.au/privacy",
+    "termsOfServiceURL": "https://windyroad.com.au/terms",
+    "defaultPrompt": [
+      "Work the highest-priority problem",
+      "Manage this incident",
+      "Review and reconcile the ITIL backlog"
+    ],
+    "brandColor": "#0F766E",
+    "screenshots": []
+  }
+}

package/README.md

@@ -1,6 +1,6 @@
 # @windyroad/itil
 
-**ITIL-aligned IT service management for Claude Code.** Track recurring incidents, perform root cause analysis, and prioritise fixes using WSJF -- all inside your coding sessions. *Maturity: Experimental (suite-bootstrap window; 327 invocations / 30d).*
+**ITIL-aligned IT service management for Claude Code and Codex.** Track recurring incidents, perform root cause analysis, and prioritise fixes using WSJF -- all inside your coding sessions. *Maturity: Experimental.*
 
 Part of [Windy Road Agent Plugins](../../README.md).
 
@@ -34,9 +34,18 @@ npx @windyroad/itil
 
 Restart Claude Code after installing.
 
+For Codex:
+
+```bash
+npx @windyroad/itil --runtime codex --scope user
+```
+
+Restart Codex after installing. Codex exposes the complete ITIL skill set, the
+exact `wr-itil:hang-off-check` agent, and five consolidated lifecycle hooks.
+
 > **Requires:** [`@windyroad/risk-scorer`](../risk-scorer/). The installer warns if it's missing.
 >
-> **Renamed from `@windyroad/problem`** — see [ADR-010](../../docs/decisions/010-rename-wr-problem-to-wr-itil.proposed.md). If you had the old package installed, uninstall it (`npx @windyroad/problem --uninstall`) before installing `@windyroad/itil`.
+> **Renamed from `@windyroad/problem`** — see [the "Rename `wr-problem` Plugin to `wr-itil`" architecture rule](../../docs/decisions/010-rename-wr-problem-to-wr-itil.proposed.md). If you had the old package installed, uninstall it (`npx @windyroad/problem --uninstall`) before installing `@windyroad/itil`.
 
 ## Usage
 
@@ -56,7 +65,7 @@ Supports creating new problems, updating root cause analysis, transitioning stat
 
 Supports declaring new incidents, recording evidence-first observations and hypotheses, logging mitigation attempts, transitioning lifecycle (Investigating → Mitigating → Restored → Closed), and automatically handing off to `manage-problem` when service is restored.
 
-See [ADR-011](../../docs/decisions/011-manage-incident-skill.proposed.md) for the incident-vs-problem split.
+See [the "Add `manage-incident` Skill to `wr-itil` Plugin" architecture rule](../../docs/decisions/011-manage-incident-skill.proposed.md) for the incident-vs-problem split.
 
 ## How It Works
 
@@ -64,13 +73,13 @@ See [ADR-011](../../docs/decisions/011-manage-incident-skill.proposed.md) for th
 |------|---------|-------------|
 | `bin/check-deps.sh` | Session start | Verifies that `wr-risk-scorer` is installed |
 | `itil-assistant-output-gate.sh` | Every prompt | Detects classes of assistant output (e.g. prose-asks vs `AskUserQuestion`) that indicate ITIL-discipline regressions |
-| `itil-correction-detect.sh` | Every prompt | Surfaces strong-signal user corrections (FFS / DO NOT / contradictions) and offers a problem ticket capture per P078 |
-| `itil-runtime-sid-marker.sh` | Bash, Edit, Write, Read | Records per-session ID for runtime instrumentation (ADR-050) |
+| `itil-correction-detect.sh` | Every prompt | Surfaces strong-signal user corrections (FFS / DO NOT / contradictions) and offers a problem ticket capture per the "Problem 078: Assistant does not offer to capture a problem ticket when the user delivers strong-signal correction" problem |
+| `itil-runtime-sid-marker.sh` | Bash, Edit, Write, Read | Records per-session ID for runtime instrumentation (the "Capture the runtime stdin session_id via a PreToolUse hook so the create-gate marker binds to the same SID the runtime hook will see" architecture rule) |
 | `manage-problem-enforce-create.sh` | Write | Blocks creation of `docs/problems/*.md` outside the `/wr-itil:manage-problem` workflow |
-| `itil-claude-space-protection.sh` | Write, Edit | Prevents project-generated artefacts from being written under `.claude/` (P131) |
-| `p057-staging-trap-detect.sh` | Bash | Detects the P057 staging trap during ticket transitions |
-| `pre-publish-intake-gate.sh` | Bash | Blocks `npm publish` when downstream OSS intake scaffolding is missing (ADR-036) |
-| `itil-changeset-discipline.sh` | Bash | Gates `git commit` on changeset coverage for source-package changes (P141) |
+| `itil-claude-space-protection.sh` | Write, Edit | Prevents project-generated artefacts from being written under `.claude/` (the "Agents write project-generated artefacts under `.claude/` (user-controlled config space) — gate exclusions are read tolerance, not write permission" problem) |
+| `p057-staging-trap-detect.sh` | Bash | Detects the "Problem 057: `git mv` + Edit + `git add` staging-ordering trap drops content edits from the commit" problem staging trap during ticket transitions |
+| `pre-publish-intake-gate.sh` | Bash | Blocks `npm publish` when downstream OSS intake scaffolding is missing (the "Scaffold downstream OSS intake — skill + layered triggers" architecture rule) |
+| `itil-changeset-discipline.sh` | Bash | Gates `git commit` on changeset coverage for source-package changes (the "AFK iter `packages/<plugin>/` commits without changesets — orchestrator-main-turn back-fill is fragile recovery, hook-level enforcement preferable" problem) |
 | `itil-assistant-output-review.sh` | Stop | Reviews assistant output at session end for ITIL-discipline patterns |
 
 ## Skills
@@ -78,30 +87,30 @@ See [ADR-011](../../docs/decisions/011-manage-incident-skill.proposed.md) for th
 | Skill | Purpose | Maturity |
 | ------- | --------- | --- |
 | `/wr-itil:manage-problem` | Create, update, and close problem tickets through the Open → Known Error → Verifying → Closed lifecycle | Alpha |
-| `/wr-itil:capture-problem` | Foreground-lightweight aside-invocation variant of `manage-problem` (per ADR-032 background-capture pattern + P078 capture-on-correction) — drafts a ticket scaffold without losing the operational thread when a problem signal surfaces mid-conversation | Experimental |
+| `/wr-itil:capture-problem` | Foreground-lightweight aside-invocation variant of `manage-problem` (per the "Governance skill invocation patterns — foreground + background with deferred-question resumption" architecture rule background-capture pattern + the "Problem 078: Assistant does not offer to capture a problem ticket when the user delivers strong-signal correction" problem capture-on-correction) — drafts a ticket scaffold without losing the operational thread when a problem signal surfaces mid-conversation | Experimental |
 | `/wr-itil:work-problem` | Pick the highest-WSJF actionable ticket and work it to completion | Experimental |
 | `/wr-itil:work-problems` | AFK orchestrator — batch-work the problem backlog by WSJF priority while the user is away | Experimental |
 | `/wr-itil:list-problems` | Read-only display of the open and known-error backlog sorted by WSJF | Experimental |
 | `/wr-itil:transition-problem` / `/wr-itil:transition-problems` | Advance one or many tickets through the lifecycle | Experimental |
 | `/wr-itil:review-problems` | Re-rate every open and known-error ticket and refresh the WSJF ranking | Experimental |
 | `/wr-itil:reconcile-readme` | Detect and correct drift between `docs/problems/README.md` and on-disk ticket inventory | Experimental |
-| `/wr-itil:report-upstream` | Report a local problem as a structured issue against an upstream repository (ADR-024) | Experimental |
-| `/wr-itil:check-upstream-responses` | Poll upstream issues we filed via `/wr-itil:report-upstream` and surface new comments / state changes / label changes since last check (P249 Phase 1; outbound symmetric counterpart to ADR-062 inbound discovery) | Experimental |
-| `/wr-itil:update-upstream` | Post a lifecycle-update comment to an upstream issue when a local problem ticket transitions — root-cause confirmed / fix released / closed; reciprocal sibling to `/wr-itil:report-upstream` (ADR-024 amendment 2026-06-09, P080 Phase 1) | Experimental |
-| `/wr-itil:capture-rfc` | Lightweight RFC-capture skill — mandatory problem-trace per ADR-060 I1 invariant; opens a coordinated multi-commit change traceable to ≥ 1 driving problem (Phase 1 of the Problem-RFC-Story framework, P170 / ADR-060) | Experimental |
-| `/wr-itil:manage-rfc` | Heavyweight RFC intake + lifecycle management — proposed → accepted → in-progress → verifying → closed; sibling to `manage-problem` at the RFC tier (ADR-060) | Experimental |
-| `/wr-itil:capture-story` | Lightweight story-capture skill — mandatory problem-trace AND JTBD-trace per ADR-060 I6 + I9 invariants; optional `--rfc` / `--story-map` flags (I7 + I8 enforce at `accepted` transition); drafts an INVEST-shaped sub-workstream entity under a parent RFC (Phase 2 of the Problem-RFC-Story framework, P170 / ADR-060) | Experimental |
-| `/wr-itil:list-stories` | Read-only display of stories grouped by lifecycle state, with optional `--rfc RFC-<NNN>` filter rendering the RFC's ordered story list per ADR-060 line 259 (Phase 2 / P170) | Experimental |
-| `/wr-itil:reconcile-stories` | Detect and correct drift between `docs/stories/README.md` and on-disk story inventory + reverse-trace `## Stories` sections on driving problems / RFCs / JTBDs (Phase 2 / P170) | Experimental |
-| `/wr-itil:manage-story` | Heavyweight story lifecycle management — draft → accepted → in-progress → done → archived; I7+I8+I10+I12 hard-block at accepted transition; INVEST 4-axis check; auto-transitions on `Refs: STORY-NNN` commit trailer + linked RFC closure (Phase 2 / P170). **I12 (ADR-103)**: `accepted` requires the story to be approved, and an implementing commit against an unapproved story is blocked. Approval is the story map's — ratify the map and every story on it is approved with it | Experimental |
-| `/wr-itil:capture-story-map` | Lightweight story-map-capture skill — mandatory problem-trace AND JTBD-trace per ADR-060 I3 + I4 invariants; HTML skeleton at `docs/story-maps/draft/STORY-MAP-NNN-<slug>.html` per ADR-060 § Phase 2 encoding amendment 2026-05-12 (Phase 2 / P170) | Experimental |
-| `/wr-itil:manage-story-map` | Heavyweight story-map lifecycle management — draft → accepted → in-progress → completed → archived; backbone/ribs/slices authoring guidance; reverse-trace `## Story Maps` refresh on driving problems + JTBDs (Phase 2 / P170) | Experimental |
-| `/wr-itil:reconcile-story-maps` | Detect and correct drift between `docs/story-maps/README.md` and on-disk story-map HTML inventory (Phase 2 / P170) | Experimental |
-| `/wr-itil:list-story-maps` | Read-only display of story-maps grouped by lifecycle state; no WSJF (I5 invariant — maps are planning artefacts, not work items) (Phase 2 / P170) | Experimental |
+| `/wr-itil:report-upstream` | Report a local problem as a structured issue against an upstream repository (the "Cross-project problem-reporting contract — `report-upstream` skill in `@windyroad/itil`" architecture rule) | Experimental |
+| `/wr-itil:check-upstream-responses` | Poll upstream issues we filed via `/wr-itil:report-upstream` and surface new comments / state changes / label changes since last check (the "No process for issue reporters to check for responses — symmetric gap to inbound discovery" problem Phase 1; outbound symmetric counterpart to the "Inbound upstream-report discovery + assessment pipeline (peer of )" architecture rule inbound discovery) | Experimental |
+| `/wr-itil:update-upstream` | Post a lifecycle-update comment to an upstream issue when a local problem ticket transitions — root-cause confirmed / fix released / closed; reciprocal sibling to `/wr-itil:report-upstream` (the "Cross-project problem-reporting contract — `report-upstream` skill in `@windyroad/itil`" architecture rule amendment 2026-06-09, the "Problem 080: No bidirectional update of upstream-reported problems — local lifecycle transitions never propagate back to the reporter" problem Phase 1) | Experimental |
+| `/wr-itil:capture-rfc` | Lightweight RFC-capture skill — mandatory problem-trace per the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule I1 invariant; opens a coordinated multi-commit change traceable to ≥ 1 driving problem (Phase 1 of the Problem-RFC-Story framework, the "Problem tickets strain as fixes decompose into multiple coordinated changes — need an RFC framework that ties all changes back to problems (and unifies technical with user/business problems)" problem / the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule) | Experimental |
+| `/wr-itil:manage-rfc` | Heavyweight RFC intake + lifecycle management — proposed → accepted → in-progress → verifying → closed; sibling to `manage-problem` at the RFC tier (the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule) | Experimental |
+| `/wr-itil:capture-story` | Lightweight story-capture skill — mandatory problem-trace AND JTBD-trace per the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule I6 + I9 invariants; optional `--rfc` / `--story-map` flags (I7 + I8 enforce at `accepted` transition); drafts an INVEST-shaped sub-workstream entity under a parent RFC (Phase 2 of the Problem-RFC-Story framework, the "Problem tickets strain as fixes decompose into multiple coordinated changes — need an RFC framework that ties all changes back to problems (and unifies technical with user/business problems)" problem / the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule) | Experimental |
+| `/wr-itil:list-stories` | Read-only display of stories grouped by lifecycle state, with optional `--rfc RFC-<NNN>` filter rendering the RFC's ordered story list per the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule line 259 (Phase 2 / the "Problem tickets strain as fixes decompose into multiple coordinated changes — need an RFC framework that ties all changes back to problems (and unifies technical with user/business problems)" problem) | Experimental |
+| `/wr-itil:reconcile-stories` | Detect and correct drift between `docs/stories/README.md` and on-disk story inventory + reverse-trace `## Stories` sections on driving problems / RFCs / JTBDs (Phase 2 / the "Problem tickets strain as fixes decompose into multiple coordinated changes — need an RFC framework that ties all changes back to problems (and unifies technical with user/business problems)" problem) | Experimental |
+| `/wr-itil:manage-story` | Heavyweight story lifecycle management — draft → accepted → in-progress → done → archived; I7+I8+I10+I12 hard-block at accepted transition; INVEST 4-axis check; auto-transitions on `Refs: STORY-NNN` commit trailer + linked RFC closure (Phase 2 / the "Problem tickets strain as fixes decompose into multiple coordinated changes — need an RFC framework that ties all changes back to problems (and unifies technical with user/business problems)" problem). **I12 (the "A release row is the RFC, and the map is the approval surface" architecture rule)**: `accepted` requires the story to be approved, and an implementing commit against an unapproved story is blocked. Approval is the story map's — ratify the map and every story on it is approved with it | Experimental |
+| `/wr-itil:capture-story-map` | Lightweight story-map-capture skill — mandatory problem-trace AND JTBD-trace per the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule I3 + I4 invariants; HTML skeleton at `docs/story-maps/draft/STORY-MAP-NNN-<slug>.html` per the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule § Phase 2 encoding amendment 2026-05-12 (Phase 2 / the "Problem tickets strain as fixes decompose into multiple coordinated changes — need an RFC framework that ties all changes back to problems (and unifies technical with user/business problems)" problem) | Experimental |
+| `/wr-itil:manage-story-map` | Heavyweight story-map lifecycle management — draft → accepted → in-progress → completed → archived; backbone/ribs/slices authoring guidance; reverse-trace `## Story Maps` refresh on driving problems + JTBDs (Phase 2 / the "Problem tickets strain as fixes decompose into multiple coordinated changes — need an RFC framework that ties all changes back to problems (and unifies technical with user/business problems)" problem) | Experimental |
+| `/wr-itil:reconcile-story-maps` | Detect and correct drift between `docs/story-maps/README.md` and on-disk story-map HTML inventory (Phase 2 / the "Problem tickets strain as fixes decompose into multiple coordinated changes — need an RFC framework that ties all changes back to problems (and unifies technical with user/business problems)" problem) | Experimental |
+| `/wr-itil:list-story-maps` | Read-only display of story-maps grouped by lifecycle state; no WSJF (I5 invariant — maps are planning artefacts, not work items) (Phase 2 / the "Problem tickets strain as fixes decompose into multiple coordinated changes — need an RFC framework that ties all changes back to problems (and unifies technical with user/business problems)" problem) | Experimental |
 | `/wr-itil:manage-incident` | Declare, triage, mitigate, and close an incident with evidence-first discipline | Experimental |
 | `/wr-itil:list-incidents` | Read-only display of active incidents by severity | Experimental |
-| `/wr-itil:mitigate-incident` / `/wr-itil:restore-incident` / `/wr-itil:close-incident` / `/wr-itil:link-incident` | Incident lifecycle transitions (ADR-011) | Experimental |
-| `/wr-itil:scaffold-intake` | Scaffold OSS intake surfaces (`.github/ISSUE_TEMPLATE/`, `SECURITY.md`, `SUPPORT.md`, `CONTRIBUTING.md`) for downstream adopters (ADR-036) | Experimental |
+| `/wr-itil:mitigate-incident` / `/wr-itil:restore-incident` / `/wr-itil:close-incident` / `/wr-itil:link-incident` | Incident lifecycle transitions (the "Add `manage-incident` Skill to `wr-itil` Plugin" architecture rule) | Experimental |
+| `/wr-itil:scaffold-intake` | Scaffold OSS intake surfaces (`.github/ISSUE_TEMPLATE/`, `SECURITY.md`, `SUPPORT.md`, `CONTRIBUTING.md`) for downstream adopters (the "Scaffold downstream OSS intake — skill + layered triggers" architecture rule) | Experimental |
 
 ## Configuration
 

package/agents/hang-off-check.md

@@ -6,8 +6,8 @@ description: Capture-time inflow-discipline arbiter for problem tickets. Given a
   Investigation Tasks expansion / Phase N section on an existing parent ticket,
   or PROCEED_NEW when no candidate absorbs the new scope. Spawned fresh from
   inside /wr-itil:capture-problem and /wr-itil:manage-problem Step 2 to avoid
-  the calling agent's session-context bias. Read-only. Codified as ADR-032's
-  5th invocation pattern under the P346 amendment.
+  the calling agent's session-context bias. Read-only. Codified as the "Governance skill invocation patterns — foreground + background with deferred-question resumption" architecture rule's
+  5th invocation pattern under the "`/wr-itil:review-problems` has no path to close tickets that are no longer relevant (evidence-based, NOT age-based) — structural outflow gap drives monotonic backlog growth" problem amendment.
 tools:
   - Read
   - Glob
@@ -15,7 +15,7 @@ tools:
 model: inherit
 ---
 
-# @jtbd JTBD-001, JTBD-006, JTBD-101, JTBD-201
+# @jtbd the ": Enforce Governance Without Slowing Down" user outcome, the ": Progress the Backlog While I'm Away" user outcome, the "Extend the Suite with New Plugins" user outcome, the "Restore Service Fast with an Audit Trail" user outcome
 
 You are the Hang-Off Check arbiter. You decide — for a new problem-ticket capture, given a mechanically pre-filtered set of candidate parent tickets — whether the new scope belongs absorbed into an existing parent (`HANG_OFF: P<NNN>`) or genuinely deserves its own new ticket (`PROCEED_NEW`).
 
@@ -23,16 +23,16 @@ You are a reviewer, not an editor. You read inputs and emit a structured verdict
 
 ## Driver
 
-You exist because session-context bias on the calling main agent is structurally guaranteed: the main agent mid-iter has just been working on related artefacts and pattern-matches existing capture flows, missing hang-off opportunities (the wrongly-captured P347 sibling of P346 on 2026-05-31 is the canonical regression). Your fresh context is the fix — you read only the structured inputs and reason about candidate absorption without the bias.
+You exist because session-context bias on the calling main agent is structurally guaranteed: the main agent mid-iter has just been working on related artefacts and pattern-matches existing capture flows, missing hang-off opportunities (the wrongly-captured the "Phase 2 — extend `evaluate-relevance.sh` with 4 more evidence shapes + fix Phase 1 file-no-longer-exists false-positive class" problem sibling of the "`/wr-itil:review-problems` has no path to close tickets that are no longer relevant (evidence-based, NOT age-based) — structural outflow gap drives monotonic backlog growth" problem on 2026-05-31 is the canonical regression). Your fresh context is the fix — you read only the structured inputs and reason about candidate absorption without the bias.
 
-Same architectural pattern as `wr-architect:agent` / `wr-jtbd:agent` / `tdd:review-test` / `wr-risk-scorer:pipeline` — codified in ADR-032 as the 5th invocation pattern (P346 amendment, 2026-05-31).
+Same architectural pattern as `wr-architect:agent` / `wr-jtbd:agent` / `tdd:review-test` / `wr-risk-scorer:pipeline` — codified in the "Governance skill invocation patterns — foreground + background with deferred-question resumption" architecture rule as the 5th invocation pattern (the "`/wr-itil:review-problems` has no path to close tickets that are no longer relevant (evidence-based, NOT age-based) — structural outflow gap drives monotonic backlog growth" problem amendment, 2026-05-31).
 
 ## Your Inputs
 
 The calling skill passes you a structured prompt containing two payloads:
 
 1. **New capture description** — the free-text observation the user / agent wants to capture as a new problem ticket (the leading flags stripped, kebab-title slug derivable but not yet committed).
-2. **Filtered candidate ticket list** — the result of the calling skill's mechanical pre-filter: candidates from `docs/problems/open/` + `docs/problems/verifying/` that share ≥1 signal with the description (ADR-NNN ref, SKILL path, file path, or named feature). The list is capped at 5 candidates per ADR-032's latency-bound contract; wider filtered sets short-circuit to PROCEED_NEW without invoking you.
+2. **Filtered candidate ticket list** — the result of the calling skill's mechanical pre-filter: candidates from `docs/problems/open/` + `docs/problems/verifying/` that share ≥1 signal with the description (ADR-NNN ref, SKILL path, file path, or named feature). The list is capped at 5 candidates per the "Governance skill invocation patterns — foreground + background with deferred-question resumption" architecture rule's latency-bound contract; wider filtered sets short-circuit to PROCEED_NEW without invoking you.
 
 For each candidate the calling skill passes:
 - Ticket ID (`P<NNN>`)
@@ -48,7 +48,7 @@ For each candidate, ask: **does the new capture belong inside this candidate as
 
 A new capture HANGS OFF a candidate when:
 
-- The candidate is a **master ticket** for a multi-phase fix and the new capture is one phase / one sub-class of that work (P346's three-phase scope is the canonical example — Phase 3 work belongs inside P346 as Phase 3, not as a sibling P347).
+- The candidate is a **master ticket** for a multi-phase fix and the new capture is one phase / one sub-class of that work (the "`/wr-itil:review-problems` has no path to close tickets that are no longer relevant (evidence-based, NOT age-based) — structural outflow gap drives monotonic backlog growth" problem's three-phase scope is the canonical example — Phase 3 work belongs inside the "`/wr-itil:review-problems` has no path to close tickets that are no longer relevant (evidence-based, NOT age-based) — structural outflow gap drives monotonic backlog growth" problem as Phase 3, not as a sibling the "Phase 2 — extend `evaluate-relevance.sh` with 4 more evidence shapes + fix Phase 1 file-no-longer-exists false-positive class" problem).
 - The candidate's `## Multi-phase scope` / `## Investigation Tasks` / `## Root Cause Analysis` section explicitly names work the new capture is doing (or is a natural extension of work the candidate names as in-scope).
 - The candidate's root cause + the new capture's root cause are the same observable phenomenon, just surfaced at different times or by different signals.
 - The new capture's description IS the candidate's deferred follow-up (the candidate's `## Fix Strategy` or `## Investigation Tasks` flags the work as "deferred to sibling ticket" but the sibling is actually scope expansion on this very ticket).
@@ -63,7 +63,7 @@ A new capture PROCEEDS as new when:
 
 When in doubt, prefer **PROCEED_NEW** — false-negative on hang-off is cheaper than false-positive (false-positive silently swallows distinct work into the wrong parent; false-negative just defers consolidation to the next `/wr-itil:review-problems` cluster pass). This mirrors `/wr-itil:capture-problem` Step 2's existing "false-positives are cheaper than false-negatives" framing.
 
-Under `--no-prompt` / AFK propagation, ambiguous-multi-parent cases also collapse to **PROCEED_NEW** (safe-default, no `AskUserQuestion` fallback — ADR-013 Rule 6 fail-safe per ADR-032 amendment).
+Under `--no-prompt` / AFK propagation, ambiguous-multi-parent cases also collapse to **PROCEED_NEW** (safe-default, no `AskUserQuestion` fallback — the "Structured User Interaction for Governance-Skill Decisions" architecture rule Rule 6 fail-safe per the "Governance skill invocation patterns — foreground + background with deferred-question resumption" architecture rule amendment).
 
 ## How to Report
 
@@ -76,7 +76,7 @@ HANG_OFF: P<NNN>
 
 **Rationale**: <one or two sentences naming the candidate's master-ticket / multi-phase / scope-expansion shape and why this new capture belongs inside it>.
 
-**Signals matched**: <comma-separated list of the specific signals — e.g. "shared ADR-079 reference", "candidate's Investigation Tasks Phase 3 section names this work", "shared `packages/itil/agents/hang-off-check.md` file path", "candidate's Fix Strategy deferred this exact scope">.
+**Signals matched**: <comma-separated list of the specific signals — e.g. "shared the "Evidence-based relevance-close pass for the problem backlog (Phase 1: file-no-longer-exists; Phase 2: ADR-shipped-confirmed + named-skill-exists + self-marker-in-body + driver-child-closed + Phase 1 false-positive fixes)" architecture rule reference", "candidate's Investigation Tasks Phase 3 section names this work", "shared `packages/itil/agents/hang-off-check.md` file path", "candidate's Fix Strategy deferred this exact scope">.
 
 **Where to absorb**: <one sentence naming where on the candidate ticket the new scope lands — e.g. "amend candidate's Investigation Tasks checklist with [the deliverable]", "expand candidate's `### Phase N — <name>` section with [the new substance]", "append to candidate's Symptoms / Workaround section">.
 ```
@@ -93,15 +93,15 @@ PROCEED_NEW
 
 ## Output Formatting
 
-When referencing decision IDs (ADR-<NNN>), problem IDs (P<NNN>), RFC IDs (RFC-<NNN>), or JTBD IDs in prose, always include a human-readable hint on first mention. Use `P346 (review-problems backlog-flow-control master ticket)`, not bare `P346`. This matches `wr-architect:agent` / `wr-jtbd:agent` output formatting conventions per their P032 contracts.
+When referencing decision IDs (ADR-<NNN>), problem IDs (P<NNN>), RFC IDs (RFC-<NNN>), or JTBD IDs in prose, always include a human-readable hint on first mention. Use `the "`/wr-itil:review-problems` has no path to close tickets that are no longer relevant (evidence-based, NOT age-based) — structural outflow gap drives monotonic backlog growth" problem (review-problems backlog-flow-control master ticket)`, not bare `the "`/wr-itil:review-problems` has no path to close tickets that are no longer relevant (evidence-based, NOT age-based) — structural outflow gap drives monotonic backlog growth" problem`. This matches `wr-architect:agent` / `wr-jtbd:agent` output formatting conventions per their the "Problem 032: Agent output references opaque problem/ADR IDs without human-readable titles" problem contracts.
 
 ## Scope and Firewalls
 
-### Maintainer-side only (JTBD-301 firewall)
+### Maintainer-side only (the "Report a Problem Without Pre-Classifying It" user outcome firewall)
 
 You fire on maintainer-side `/wr-itil:capture-problem` and maintainer-internal `/wr-itil:manage-problem` invocations only. You DO NOT fire on:
 
-- Plugin-user-side intake via `.github/ISSUE_TEMPLATE/problem-report.yml` (plugin-user descriptions do not carry the same authorial intent as maintainer-internal captures — a plugin-user describing their friction in maintainer vocabulary could plausibly trigger a wrong-parent HANG_OFF). Triage during `/wr-itil:manage-problem` ingestion stays user-judgement per JTBD-301.
+- Plugin-user-side intake via `.github/ISSUE_TEMPLATE/problem-report.yml` (plugin-user descriptions do not carry the same authorial intent as maintainer-internal captures — a plugin-user describing their friction in maintainer vocabulary could plausibly trigger a wrong-parent HANG_OFF). Triage during `/wr-itil:manage-problem` ingestion stays user-judgement per the "Report a Problem Without Pre-Classifying It" user outcome.
 - `/wr-itil:manage-problem`'s ingestion-of-plugin-user-reports path (mirrors the lexical-classifier firewall at `packages/itil/skills/capture-problem/SKILL.md` line 116).
 
 ### Cardinality
@@ -116,31 +116,31 @@ One verdict per invocation. The calling skill captures one ticket per invocation
 
 ## Behavioural verification
 
-The canonical behavioural fixture is the P347-vs-P346 regression — `packages/itil/agents/test/fixtures/regression-p347-vs-p346.md` captures the input shape:
-- New capture description: P347's original description (about "Phase 2 evidence shape expansion" work).
-- Candidate set: contains P346 (the master backlog-flow-control ticket with its Multi-phase scope section explicitly naming Phase 2 as in-scope).
-- Expected verdict: `HANG_OFF: P346` with rationale citing the shared ADR-079 reference + the candidate's Multi-phase scope section explicitly naming Phase 2.
+The canonical behavioural fixture is the "Phase 2 — extend `evaluate-relevance.sh` with 4 more evidence shapes + fix Phase 1 file-no-longer-exists false-positive class" problem-vs-the "`/wr-itil:review-problems` has no path to close tickets that are no longer relevant (evidence-based, NOT age-based) — structural outflow gap drives monotonic backlog growth" problem regression — `packages/itil/agents/test/fixtures/regression-p347-vs-p346.md` captures the input shape:
+- New capture description: the "Phase 2 — extend `evaluate-relevance.sh` with 4 more evidence shapes + fix Phase 1 file-no-longer-exists false-positive class" problem's original description (about "Phase 2 evidence shape expansion" work).
+- Candidate set: contains the "`/wr-itil:review-problems` has no path to close tickets that are no longer relevant (evidence-based, NOT age-based) — structural outflow gap drives monotonic backlog growth" problem (the master backlog-flow-control ticket with its Multi-phase scope section explicitly naming Phase 2 as in-scope).
+- Expected verdict: `HANG_OFF: the "`/wr-itil:review-problems` has no path to close tickets that are no longer relevant (evidence-based, NOT age-based) — structural outflow gap drives monotonic backlog growth" problem` with rationale citing the shared the "Evidence-based relevance-close pass for the problem backlog (Phase 1: file-no-longer-exists; Phase 2: ADR-shipped-confirmed + named-skill-exists + self-marker-in-body + driver-child-closed + Phase 1 false-positive fixes)" architecture rule reference + the candidate's Multi-phase scope section explicitly naming Phase 2.
 
-Two further canonical fixtures live under the same path: `fixtures/proceed-new-genuinely-new.md` (no real candidates → PROCEED_NEW) and `fixtures/proceed-new-subtle-sibling.md` (P070 vs a new report-upstream surface ticket on a different SKILL → PROCEED_NEW with reasoned per-candidate rationale).
+Two further canonical fixtures live under the same path: `fixtures/proceed-new-genuinely-new.md` (no real candidates → PROCEED_NEW) and `fixtures/proceed-new-subtle-sibling.md` (the "Problem 070: /wr-itil:report-upstream does not check for existing upstream issues before filing" problem vs a new report-upstream surface ticket on a different SKILL → PROCEED_NEW with reasoned per-candidate rationale).
 
-Behavioural execution of these fixtures lands under RFC-012 (promptfoo eval harness — proposed). Until RFC-012 ships, the bats fixtures at `packages/itil/agents/test/hang-off-check.bats` are structural assertions on this agent's prose contract per ADR-052 Surface 2 (with the P176 harness-gap carve-out the architect and JTBD reviewer agents document); they verify the verdict format is documented, the firewall is named, the safe-default behaviour is specified, and the fixture files exist with the expected input shape.
+Behavioural execution of these fixtures lands under the ": Build the promptfoo agent-prose AND SKILL-prose verdict eval harness" release design (promptfoo eval harness — proposed). Until the ": Build the promptfoo agent-prose AND SKILL-prose verdict eval harness" release design ships, the bats fixtures at `packages/itil/agents/test/hang-off-check.bats` are structural assertions on this agent's prose contract per the "Behavioural-tests-default for skill testing" architecture rule Surface 2 (with the "Agent-side I2 (no type-branching) coverage gap — SKILL.md type-branching invariant not behaviourally testable until skill-invocation harness lands" problem harness-gap carve-out the architect and JTBD reviewer agents document); they verify the verdict format is documented, the firewall is named, the safe-default behaviour is specified, and the fixture files exist with the expected input shape.
 
 ## Related
 
-- **ADR-032** (Governance-skill invocation patterns) — the 5th invocation pattern (Foreground fresh-context-subagent-as-decision-arbiter) under the P346 amendment 2026-05-31. This agent IS the worked example.
-- **ADR-013** (Structured user interaction for governance decisions) — Rule 6 fail-safe; you never invoke `AskUserQuestion`; ambiguous-multi-parent collapses to PROCEED_NEW under AFK propagation.
-- **ADR-026** (Agent output grounding) — your rationale MUST cite observable signals (specific ADR refs, specific file paths, specific candidate ticket section names); no qualitative claims.
-- **ADR-049** (Plugin scripts via `bin/` on PATH) — not directly relevant; this agent is loaded via Agent tool, not PATH.
-- **ADR-052** (Behavioural-tests default) — bats fixtures for this agent are structural per Surface 2 carve-out + P176 harness gap; behavioural eval lands under RFC-012.
-- **ADR-075** (promptfoo as agent-prose verdict harness) — future home of the behavioural fixtures.
-- **RFC-012** (promptfoo retrofit, proposed) — will run the canonical behavioural fixtures.
-- **RFC-013** (P346 backlog flow control multi-phase, proposed) — traces P346 Phases 1+2+3; this agent is part of Phase 3's deliverable.
-- **P346** (review-problems backlog-flow-control master ticket — `docs/problems/open/346-...md`) — driver ticket. Phase 3 spec authored in P346's body; codified as ADR-032's 5th pattern.
-- **P347** (closed as duplicate-of-P346) — the wrongly-captured sibling that motivated this agent's existence; the canonical regression fixture.
-- **P176** (agent-side I2 / harness gap) — the structural-bats Surface 2 carve-out precedent.
-- **JTBD-001** (Enforce Governance Without Slowing Down) — the pre-filter latency cap + verdict-acts contract keeps capture under the 60s flow budget.
-- **JTBD-006** (Progress the Backlog While I'm Away) — verdict is deterministic, never blocks on AskUserQuestion; AFK-safe.
-- **JTBD-101** (Extend the Suite with New Plugins) — the fresh-context-subagent-as-decision-arbiter pattern is reusable for future capture-time discipline needs.
-- **JTBD-201** (Restore Service Fast with an Audit Trail) — HANG_OFF rationale is recorded on the absorbing ticket's Investigation Tasks bullet; PROCEED_NEW rationale lands on the captured ticket's `## Related` section so the next reviewer sees what was considered.
+- **the "Governance skill invocation patterns — foreground + background with deferred-question resumption" architecture rule** (Governance-skill invocation patterns) — the 5th invocation pattern (Foreground fresh-context-subagent-as-decision-arbiter) under the "`/wr-itil:review-problems` has no path to close tickets that are no longer relevant (evidence-based, NOT age-based) — structural outflow gap drives monotonic backlog growth" problem amendment 2026-05-31. This agent IS the worked example.
+- **the "Structured User Interaction for Governance-Skill Decisions" architecture rule** (Structured user interaction for governance decisions) — Rule 6 fail-safe; you never invoke `AskUserQuestion`; ambiguous-multi-parent collapses to PROCEED_NEW under AFK propagation.
+- **the "Agent output grounding — no fabricated quantitative estimates, cite + persist + uncertainty" architecture rule** (Agent output grounding) — your rationale MUST cite observable signals (specific ADR refs, specific file paths, specific candidate ticket section names); no qualitative claims.
+- **the "Plugin-bundled scripts invoked from SKILL.md resolve via `bin/` on `$PATH`" architecture rule** (Plugin scripts via `bin/` on PATH) — not directly relevant; this agent is loaded via Agent tool, not PATH.
+- **the "Behavioural-tests-default for skill testing" architecture rule** (Behavioural-tests default) — bats fixtures for this agent are structural per Surface 2 carve-out + the "Agent-side I2 (no type-branching) coverage gap — SKILL.md type-branching invariant not behaviourally testable until skill-invocation harness lands" problem harness gap; behavioural eval lands under the ": Build the promptfoo agent-prose AND SKILL-prose verdict eval harness" release design.
+- **the ": promptfoo as the behavioural test harness for agent-prose verdicts" architecture rule** (promptfoo as agent-prose verdict harness) — future home of the behavioural fixtures.
+- **the ": Build the promptfoo agent-prose AND SKILL-prose verdict eval harness" release design** (promptfoo retrofit, proposed) — will run the canonical behavioural fixtures.
+- **the ": backlog flow control multi-phase" release design** (the "`/wr-itil:review-problems` has no path to close tickets that are no longer relevant (evidence-based, NOT age-based) — structural outflow gap drives monotonic backlog growth" problem backlog flow control multi-phase, proposed) — traces the "`/wr-itil:review-problems` has no path to close tickets that are no longer relevant (evidence-based, NOT age-based) — structural outflow gap drives monotonic backlog growth" problem Phases 1+2+3; this agent is part of Phase 3's deliverable.
+- **the "`/wr-itil:review-problems` has no path to close tickets that are no longer relevant (evidence-based, NOT age-based) — structural outflow gap drives monotonic backlog growth" problem** (review-problems backlog-flow-control master ticket — `docs/problems/open/346-...md`) — driver ticket. Phase 3 spec authored in the "`/wr-itil:review-problems` has no path to close tickets that are no longer relevant (evidence-based, NOT age-based) — structural outflow gap drives monotonic backlog growth" problem's body; codified as the "Governance skill invocation patterns — foreground + background with deferred-question resumption" architecture rule's 5th pattern.
+- **the "Phase 2 — extend `evaluate-relevance.sh` with 4 more evidence shapes + fix Phase 1 file-no-longer-exists false-positive class" problem** (closed as duplicate-of-the "`/wr-itil:review-problems` has no path to close tickets that are no longer relevant (evidence-based, NOT age-based) — structural outflow gap drives monotonic backlog growth" problem) — the wrongly-captured sibling that motivated this agent's existence; the canonical regression fixture.
+- **the "Agent-side I2 (no type-branching) coverage gap — SKILL.md type-branching invariant not behaviourally testable until skill-invocation harness lands" problem** (agent-side I2 / harness gap) — the structural-bats Surface 2 carve-out precedent.
+- **the ": Enforce Governance Without Slowing Down" user outcome** (Enforce Governance Without Slowing Down) — the pre-filter latency cap + verdict-acts contract keeps capture under the 60s flow budget.
+- **the ": Progress the Backlog While I'm Away" user outcome** (Progress the Backlog While I'm Away) — verdict is deterministic, never blocks on AskUserQuestion; AFK-safe.
+- **the "Extend the Suite with New Plugins" user outcome** (Extend the Suite with New Plugins) — the fresh-context-subagent-as-decision-arbiter pattern is reusable for future capture-time discipline needs.
+- **the "Restore Service Fast with an Audit Trail" user outcome** (Restore Service Fast with an Audit Trail) — HANG_OFF rationale is recorded on the absorbing ticket's Investigation Tasks bullet; PROCEED_NEW rationale lands on the captured ticket's `## Related` section so the next reviewer sees what was considered.
 - **`/wr-itil:capture-problem`** (`packages/itil/skills/capture-problem/SKILL.md` Step 2) — primary dispatch site.
-- **`/wr-itil:manage-problem`** (`packages/itil/skills/manage-problem/SKILL.md` Step 2) — secondary dispatch site (maintainer-internal new-problem path only; plugin-user-report ingestion path skips per JTBD-301 firewall).
+- **`/wr-itil:manage-problem`** (`packages/itil/skills/manage-problem/SKILL.md` Step 2) — secondary dispatch site (maintainer-internal new-problem path only; plugin-user-report ingestion path skips per the "Report a Problem Without Pre-Classifying It" user outcome firewall).

package/bin/install.mjs

@@ -1,16 +1,34 @@
 #!/usr/bin/env node
 
-import { resolve, dirname } from "node:path";
+import { execSync } from "node:child_process";
+import { cpSync, existsSync, mkdirSync, readFileSync, rmSync } from "node:fs";
+import { homedir } from "node:os";
+import { resolve, dirname, join } from "node:path";
 import { fileURLToPath } from "node:url";
 
 const __dirname = dirname(fileURLToPath(import.meta.url));
 const utils = await import(resolve(__dirname, "../lib/install-utils.mjs"));
+const agents = await import(resolve(__dirname, "../scripts/codex-agent.mjs"));
 
 const PLUGIN = "wr-itil";
+const CODEX_MARKETPLACE = "windyroad-itil-local";
 const DEPS = ["wr-risk-scorer"];
+const PACKAGE_ROOT = resolve(__dirname, "..");
+const PACKAGE_VERSION = JSON.parse(readFileSync(join(PACKAGE_ROOT, "package.json"), "utf8")).version;
+
+function codexMarketplaceRoot() {
+  const home = process.env.CODEX_HOME || join(homedir(), ".codex");
+  return join(home, ".tmp", "marketplaces", `wr-itil-${PACKAGE_VERSION}`);
+}
 
 const flags = utils.parseStandardArgs(process.argv);
 
+if (flags.runtime === "codex" || flags.runtime === "both") {
+  const bundled = "/Applications/ChatGPT.app/Contents/Resources/codex";
+  const binary = process.env.CODEX_BINARY || (existsSync(bundled) ? bundled : null);
+  if (binary?.includes("/")) process.env.PATH = `${dirname(binary)}:${process.env.PATH || ""}`;
+}
+
 if (flags.help) {
   console.log(`
 Usage: npx @windyroad/itil [options]
@@ -21,6 +39,7 @@ Options:
   --update     Update this plugin and its skills
   --uninstall  Remove this plugin
   --scope      Installation scope: project (default) or user
+  --runtime    Runtime to install for: claude (default), codex, or both
   --dry-run    Show what would be done without executing
   --help, -h   Show this help
 `);
@@ -32,12 +51,59 @@ if (flags.dryRun) {
   console.log("[dry-run mode — no commands will be executed]\n");
 }
 
-utils.checkPrerequisites();
+utils.checkPrerequisites({ runtime: flags.runtime });
+
+function warnMissingCodexDependency() {
+  if (flags.dryRun) return;
+  try {
+    const installed = execSync("codex plugin list", { encoding: "utf8" });
+    if (!installed.includes("wr-risk-scorer@")) {
+      console.warn("Warning: wr-itil requires wr-risk-scorer; install @windyroad/risk-scorer for Codex.");
+    }
+  } catch {
+    console.warn("Warning: could not verify the wr-risk-scorer Codex dependency.");
+  }
+}
+
+function codexInstall() {
+  const root = codexMarketplaceRoot();
+  if (!flags.dryRun) {
+    rmSync(root, { recursive: true, force: true });
+    mkdirSync(dirname(root), { recursive: true });
+    cpSync(PACKAGE_ROOT, root, { recursive: true });
+    cpSync(join(root, "hooks-codex", "hooks.json"), join(root, "hooks", "hooks.json"));
+  }
+  if (!utils.run(`codex plugin marketplace add ${JSON.stringify(root)}`, `Codex marketplace: ${CODEX_MARKETPLACE}`)) return false;
+  if (!utils.run(`codex plugin add ${PLUGIN}@${CODEX_MARKETPLACE}`, PLUGIN)) return false;
+  if (!flags.dryRun) agents.installAgent(agents.agentDir(flags.scope));
+  warnMissingCodexDependency();
+  return true;
+}
+
+function codexUninstall() {
+  const removed = utils.run(`codex plugin remove ${PLUGIN}@${CODEX_MARKETPLACE}`, `Removing ${PLUGIN}`);
+  utils.run(`codex plugin marketplace remove ${CODEX_MARKETPLACE}`, `Removing ${CODEX_MARKETPLACE}`);
+  if (!flags.dryRun) {
+    for (const target of new Set([agents.agentDir(flags.scope), agents.agentDir("user")])) agents.uninstallAgent(target);
+    rmSync(codexMarketplaceRoot(), { recursive: true, force: true });
+  }
+  return removed;
+}
 
 if (flags.uninstall) {
-  utils.uninstallPackage(PLUGIN);
+  if (flags.runtime === "claude" || flags.runtime === "both") utils.uninstallPackage(PLUGIN, { runtime: "claude" });
+  if ((flags.runtime === "codex" || flags.runtime === "both") && !codexUninstall()) process.exit(1);
 } else if (flags.update) {
-  utils.updatePackage(PLUGIN, { scope: flags.scope });
+  if (flags.runtime === "claude" || flags.runtime === "both") utils.updatePackage(PLUGIN, { scope: flags.scope, runtime: "claude" });
+  if ((flags.runtime === "codex" || flags.runtime === "both") && !codexInstall()) process.exit(1);
+} else if (flags.runtime === "codex") {
+  console.log(`\nInstalling @windyroad/itil (${flags.scope} scope)...\n`);
+  if (!codexInstall()) process.exit(1);
+  console.log("\nDone! Restart Codex to activate.\n");
+} else if (flags.runtime === "both") {
+  utils.installPackage(PLUGIN, { deps: DEPS, scope: flags.scope, runtime: "claude" });
+  if (!codexInstall()) process.exit(1);
+  console.log("\nDone! Restart Claude Code and Codex to activate.\n");
 } else {
-  utils.installPackage(PLUGIN, { deps: DEPS, scope: flags.scope });
+  utils.installPackage(PLUGIN, { deps: DEPS, scope: flags.scope, runtime: "claude" });
 }

package/bin/wr-itil-catchup-scan

@@ -4,7 +4,7 @@
 # shim files in packages/*/bin/wr-* directly; edit the template + run
 # `npm run sync:shim-wrappers` to regenerate.
 #
-# Resolution (ADR-080):
+# Resolution (highest-version-wins-shim-wrapper-for-plugin-scaffold-template-shims-architecture-rule):
 #   1. If the wrapper's parent dir is semver-shaped, treat as installed-
 #      cache execution and resolve to the highest-version sibling's
 #      scripts/ entry below.
@@ -15,9 +15,9 @@
 #   3. If the cache parent contains zero semver-shaped siblings, exit
 #      127 with a stderr message naming the cache parent (per SQ-080-2).
 #
-# @adr ADR-080 (highest-version-wins shim wrapper plugin scaffold)
-# @adr ADR-049 (plugin-bundled scripts resolve via bin/ on $PATH — amended)
-# @problem P343 (mid-session staleness window)
+# @adr highest-version-wins-shim-wrapper-for-plugin-scaffold-template-shims-architecture-rule (highest-version-wins shim wrapper plugin scaffold)
+# @adr plugin-bundled-scripts-invoked-from-skill-md-resolve-via-bin-on-path-architecture-rule (plugin-bundled scripts resolve via bin/ on $PATH — amended)
+# @problem install-updates-refreshes-the-global-plugin-cache-but-does-not-fix-path-ordering-stale-plugin-version-shims-stay-first-on-path-so-subsequent-shim-invocations-run-old-code-problem (mid-session staleness window)
 
 set -euo pipefail
 

package/bin/wr-itil-check-deferred-placeholder-staleness

@@ -4,7 +4,7 @@
 # shim files in packages/*/bin/wr-* directly; edit the template + run
 # `npm run sync:shim-wrappers` to regenerate.
 #
-# Resolution (ADR-080):
+# Resolution (highest-version-wins-shim-wrapper-for-plugin-scaffold-template-shims-architecture-rule):
 #   1. If the wrapper's parent dir is semver-shaped, treat as installed-
 #      cache execution and resolve to the highest-version sibling's
 #      scripts/ entry below.
@@ -15,9 +15,9 @@
 #   3. If the cache parent contains zero semver-shaped siblings, exit
 #      127 with a stderr message naming the cache parent (per SQ-080-2).
 #
-# @adr ADR-080 (highest-version-wins shim wrapper plugin scaffold)
-# @adr ADR-049 (plugin-bundled scripts resolve via bin/ on $PATH — amended)
-# @problem P343 (mid-session staleness window)
+# @adr highest-version-wins-shim-wrapper-for-plugin-scaffold-template-shims-architecture-rule (highest-version-wins shim wrapper plugin scaffold)
+# @adr plugin-bundled-scripts-invoked-from-skill-md-resolve-via-bin-on-path-architecture-rule (plugin-bundled scripts resolve via bin/ on $PATH — amended)
+# @problem install-updates-refreshes-the-global-plugin-cache-but-does-not-fix-path-ordering-stale-plugin-version-shims-stay-first-on-path-so-subsequent-shim-invocations-run-old-code-problem (mid-session staleness window)
 
 set -euo pipefail
 

package/bin/wr-itil-check-fail-soft-skip-discipline

@@ -4,7 +4,7 @@
 # shim files in packages/*/bin/wr-* directly; edit the template + run
 # `npm run sync:shim-wrappers` to regenerate.
 #
-# Resolution (ADR-080):
+# Resolution (highest-version-wins-shim-wrapper-for-plugin-scaffold-template-shims-architecture-rule):
 #   1. If the wrapper's parent dir is semver-shaped, treat as installed-
 #      cache execution and resolve to the highest-version sibling's
 #      scripts/ entry below.
@@ -15,9 +15,9 @@
 #   3. If the cache parent contains zero semver-shaped siblings, exit
 #      127 with a stderr message naming the cache parent (per SQ-080-2).
 #
-# @adr ADR-080 (highest-version-wins shim wrapper plugin scaffold)
-# @adr ADR-049 (plugin-bundled scripts resolve via bin/ on $PATH — amended)
-# @problem P343 (mid-session staleness window)
+# @adr highest-version-wins-shim-wrapper-for-plugin-scaffold-template-shims-architecture-rule (highest-version-wins shim wrapper plugin scaffold)
+# @adr plugin-bundled-scripts-invoked-from-skill-md-resolve-via-bin-on-path-architecture-rule (plugin-bundled scripts resolve via bin/ on $PATH — amended)
+# @problem install-updates-refreshes-the-global-plugin-cache-but-does-not-fix-path-ordering-stale-plugin-version-shims-stay-first-on-path-so-subsequent-shim-invocations-run-old-code-problem (mid-session staleness window)
 
 set -euo pipefail
 

package/bin/wr-itil-check-fix-rfc-trace

@@ -4,7 +4,7 @@
 # shim files in packages/*/bin/wr-* directly; edit the template + run
 # `npm run sync:shim-wrappers` to regenerate.
 #
-# Resolution (ADR-080):
+# Resolution (highest-version-wins-shim-wrapper-for-plugin-scaffold-template-shims-architecture-rule):
 #   1. If the wrapper's parent dir is semver-shaped, treat as installed-
 #      cache execution and resolve to the highest-version sibling's
 #      scripts/ entry below.
@@ -15,9 +15,9 @@
 #   3. If the cache parent contains zero semver-shaped siblings, exit
 #      127 with a stderr message naming the cache parent (per SQ-080-2).
 #
-# @adr ADR-080 (highest-version-wins shim wrapper plugin scaffold)
-# @adr ADR-049 (plugin-bundled scripts resolve via bin/ on $PATH — amended)
-# @problem P343 (mid-session staleness window)
+# @adr highest-version-wins-shim-wrapper-for-plugin-scaffold-template-shims-architecture-rule (highest-version-wins shim wrapper plugin scaffold)
+# @adr plugin-bundled-scripts-invoked-from-skill-md-resolve-via-bin-on-path-architecture-rule (plugin-bundled scripts resolve via bin/ on $PATH — amended)
+# @problem install-updates-refreshes-the-global-plugin-cache-but-does-not-fix-path-ordering-stale-plugin-version-shims-stay-first-on-path-so-subsequent-shim-invocations-run-old-code-problem (mid-session staleness window)
 
 set -euo pipefail
 

package/bin/wr-itil-check-locale-discipline

@@ -4,7 +4,7 @@
 # shim files in packages/*/bin/wr-* directly; edit the template + run
 # `npm run sync:shim-wrappers` to regenerate.
 #
-# Resolution (ADR-080):
+# Resolution (highest-version-wins-shim-wrapper-for-plugin-scaffold-template-shims-architecture-rule):
 #   1. If the wrapper's parent dir is semver-shaped, treat as installed-
 #      cache execution and resolve to the highest-version sibling's
 #      scripts/ entry below.
@@ -15,9 +15,9 @@
 #   3. If the cache parent contains zero semver-shaped siblings, exit
 #      127 with a stderr message naming the cache parent (per SQ-080-2).
 #
-# @adr ADR-080 (highest-version-wins shim wrapper plugin scaffold)
-# @adr ADR-049 (plugin-bundled scripts resolve via bin/ on $PATH — amended)
-# @problem P343 (mid-session staleness window)
+# @adr highest-version-wins-shim-wrapper-for-plugin-scaffold-template-shims-architecture-rule (highest-version-wins shim wrapper plugin scaffold)
+# @adr plugin-bundled-scripts-invoked-from-skill-md-resolve-via-bin-on-path-architecture-rule (plugin-bundled scripts resolve via bin/ on $PATH — amended)
+# @problem install-updates-refreshes-the-global-plugin-cache-but-does-not-fix-path-ordering-stale-plugin-version-shims-stay-first-on-path-so-subsequent-shim-invocations-run-old-code-problem (mid-session staleness window)
 
 set -euo pipefail
 

package/bin/wr-itil-check-outbound-responses-staleness

@@ -4,7 +4,7 @@
 # shim files in packages/*/bin/wr-* directly; edit the template + run
 # `npm run sync:shim-wrappers` to regenerate.
 #
-# Resolution (ADR-080):
+# Resolution (highest-version-wins-shim-wrapper-for-plugin-scaffold-template-shims-architecture-rule):
 #   1. If the wrapper's parent dir is semver-shaped, treat as installed-
 #      cache execution and resolve to the highest-version sibling's
 #      scripts/ entry below.
@@ -15,9 +15,9 @@
 #   3. If the cache parent contains zero semver-shaped siblings, exit
 #      127 with a stderr message naming the cache parent (per SQ-080-2).
 #
-# @adr ADR-080 (highest-version-wins shim wrapper plugin scaffold)
-# @adr ADR-049 (plugin-bundled scripts resolve via bin/ on $PATH — amended)
-# @problem P343 (mid-session staleness window)
+# @adr highest-version-wins-shim-wrapper-for-plugin-scaffold-template-shims-architecture-rule (highest-version-wins shim wrapper plugin scaffold)
+# @adr plugin-bundled-scripts-invoked-from-skill-md-resolve-via-bin-on-path-architecture-rule (plugin-bundled scripts resolve via bin/ on $PATH — amended)
+# @problem install-updates-refreshes-the-global-plugin-cache-but-does-not-fix-path-ordering-stale-plugin-version-shims-stay-first-on-path-so-subsequent-shim-invocations-run-old-code-problem (mid-session staleness window)
 
 set -euo pipefail