@windyroad/itil 1.2.0 → 2.0.0-preview.1111

package/hooks/manage-problem-enforce-create.sh

@@ -1,20 +1,16 @@
 #!/bin/bash
-# P119: PreToolUse:Write enforcement hook for new problem ticket creation.
-# P170 / ADR-060: extended to also gate new RFC ticket creation under docs/rfcs/.
+# agent-bypasses-wr-itil-manage-problem-step-2-duplicate-check-by-writing-tickets-directly-to-docs-problems-problem: PreToolUse:Write enforcement hook for new problem ticket creation.
+# New RFC documents are denied; fix proposals use release rows and stories.
 #
 # BLOCKS Write to:
 #   - docs/problems/<NNN>-*.<status>.md      (when file does not yet exist
 #                                             and Step-2 grep marker absent)
-#   - docs/rfcs/RFC-<NNN>-*.<status>.md      (when file does not yet exist
-#                                             and capture-rfc marker absent)
+#   - docs/rfcs/RFC-<NNN>-*.<status>.md      (when file does not yet exist)
 #
 # Marker convention:
 #   - /tmp/manage-problem-grep-${SESSION_ID}        (problems tier;
 #                                                    set by manage-problem /
 #                                                    capture-problem Step 2)
-#   - /tmp/wr-itil-rfc-capture-grep-${SESSION_ID}   (RFC tier;
-#                                                    set by capture-rfc Step 2 /
-#                                                    manage-rfc creation flow)
 #
 # Out of scope (allow-listed):
 #   - docs/problems/README.md  — regenerated by manage-problem Steps 5/6/7
@@ -30,24 +26,20 @@
 #                                Other docs (NOTES.md, archive/, etc.)
 #                                are project housekeeping, not tickets
 #
-# ADR-031 forward-compat: matcher uses path-prefix + ticket-shape basename,
+# problem-ticket-directory-layout-per-state-subdirectories-under-docs-problems-architecture-rule forward-compat: matcher uses path-prefix + ticket-shape basename,
 # agnostic to current suffix-based layout vs. future per-state subdirectory
-# layout. Branch deny message names the right skill (manage-problem /
-# capture-problem for problems-tier; capture-rfc / manage-rfc for RFC-tier).
+# layout. The RFC branch redirects to the release-row capture flow.
 #
 # References:
-#   ADR-009  — gate marker lifecycle (per-session /tmp markers).
-#   ADR-013 Rule 1 — deny redirects to the relevant skill (manage-problem
+#   gate-marker-lifecycle-ttl-drift-not-stop-hook-reset-architecture-rule  — gate marker lifecycle (per-session /tmp markers).
+#   structured-user-interaction-for-governance-skill-decisions-architecture-rule Rule 1 — deny redirects to the relevant skill (manage-problem
 #                    for problems; capture-rfc for RFCs) where Step 2 fires.
-#   ADR-022  — problem lifecycle (status suffixes covered: open / known-error /
+#   problem-lifecycle-add-a-verification-pending-status-between-known-error-and-closed-architecture-rule  — problem lifecycle (status suffixes covered: open / known-error /
 #              verifying / parked).
-#   ADR-038  — progressive disclosure (deny message stays terse + actionable).
-#   ADR-051  — load-bearing-from-the-start (RFC I1 trace-to-problem invariant
-#              ships as a hard-block from day one, not advisory-then-escalate).
-#   ADR-060  — Problem-RFC-Story framework; introduces RFC tier + I1
-#              hard-block at capture-rfc.
-#   P119     — agent bypasses Step 2 by writing tickets directly.
-#   P170     — driver problem ticket for the RFC framework introduction.
+#   progressive-disclosure-once-per-session-budget-for-userpromptsubmit-governance-prose-architecture-rule  — progressive disclosure (deny message stays terse + actionable).
+#   problem-rfc-story-framework-with-mandatory-problem-trace-and-unified-problem-ontology-architecture-rule  — Problem-RFC-Story framework.
+#   agent-bypasses-wr-itil-manage-problem-step-2-duplicate-check-by-writing-tickets-directly-to-docs-problems-problem     — agent bypasses Step 2 by writing tickets directly.
+#   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     — driver problem ticket for the RFC framework introduction.
 
 SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
 # shellcheck source=lib/create-gate.sh
@@ -145,11 +137,11 @@ if [ -f "$FILE_PATH" ]; then
   exit 0
 fi
 
-# P142 / ADR-050: the runtime-SID instrumentation hook
+# phase-4-get-current-session-id-helper-system-priority-bug-subprocess-sids-win-mtime-selection-over-orchestrator-sid-problem / 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: the runtime-SID instrumentation hook
 # (itil-runtime-sid-marker.sh) writes the runtime stdin session_id to a
 # per-machine marker on every PreToolUse:Bash|Write|Edit|Read event. The
 # `get_current_session_id` helper reads that marker as the authoritative
-# SID, so the marker `mark_step2_complete` / `mark_rfc_capture_complete`
+# SID, so the marker `mark_step2_complete`
 # writes is bound to the same session_id this hook will see on the
 # subsequent Write. SID-mismatch denial is structurally eliminated; the
 # only remaining deny path is the routine "duplicate-check / capture
@@ -161,14 +153,11 @@ case "$TIER" in
     if check_create_gate "$SESSION_ID"; then
       exit 0
     fi
-    create_gate_deny "BLOCKED: Cannot Write '${BASENAME}' under docs/problems/ without running /wr-itil:manage-problem Step 2 (duplicate-check) first. New problem tickets MUST be created via the skill so the duplicate-prevention grep fires before the file lands. Invoke the Skill tool with skill='wr-itil:manage-problem' and a description of the new problem; Step 2 will grep for related existing tickets and surface any matches via AskUserQuestion before creating the new ticket. (P119)"
+    create_gate_deny "BLOCKED: Cannot Write '${BASENAME}' under docs/problems/ without running /wr-itil:manage-problem Step 2 (duplicate-check) first. New problem tickets MUST be created via the skill so the duplicate-prevention grep fires before the file lands. Invoke the Skill tool with skill='wr-itil:manage-problem' and a description of the new problem; Step 2 will grep for related existing tickets and surface any matches via AskUserQuestion before creating the new ticket. (agent-bypasses-wr-itil-manage-problem-step-2-duplicate-check-by-writing-tickets-directly-to-docs-problems-problem)"
     exit 0
     ;;
   rfcs)
-    if check_rfc_capture_gate "$SESSION_ID"; then
-      exit 0
-    fi
-    create_gate_deny "BLOCKED: Cannot Write '${BASENAME}' under docs/rfcs/ without running /wr-itil:capture-rfc Step 2 (problem-trace validation) first. New RFC tickets MUST be created via the skill so the I1 trace-to-problem invariant is enforced before the file lands. Invoke the Skill tool with skill='wr-itil:capture-rfc' supplying the leading problem-trace argument (P<NNN> or P<NNN>,P<NNN>,...); Step 2 will validate that each traced problem exists. Without a problem-trace, capture-rfc emits a deny log entry to logs/rfc-capture-denials.jsonl per ADR-060 § Confirmation criterion 1 + § Reassessment trace-violation-rate criterion. (P170 / ADR-060)"
+    create_gate_deny "BLOCKED: New RFC documents are retired. Use /wr-itil:capture-rfc to draw a problem-traced release row with at least one story on an existing story map. Existing RFC documents remain editable for legacy lifecycle transitions."
     exit 0
     ;;
 esac

package/hooks/p057-staging-trap-detect.sh

@@ -1,12 +1,12 @@
 #!/bin/bash
-# P125: PreToolUse:Bash hook — denies `git commit` invocations that
-# would land in the P057 staging-trap shape (rename + post-rename
+# staging-trap-recurs-despite-documentation-hook-level-enforcement-candidate-problem: PreToolUse:Bash hook — denies `git commit` invocations that
+# would land in the problem-057-git-mv-edit-git-add-staging-ordering-trap-drops-content-edits-from-the-commit-problem staging-trap shape (rename + post-rename
 # Edit without re-stage).
 #
 # Detection delegates to `lib/staging-detect.sh::detect_p057_trap`.
 # When the helper returns 1, this hook emits PreToolUse deny JSON
 # with the trap'd path inline and the literal `git add <path>`
-# recovery command, satisfying ADR-013 Rule 1's "deny redirects to
+# recovery command, satisfying structured-user-interaction-for-governance-skill-decisions-architecture-rule Rule 1's "deny redirects to
 # a recovery path" contract via the mechanical-recovery shape (no
 # skill wrapper required — re-staging a file is a single command).
 #
@@ -14,7 +14,7 @@
 # `lib/command-detect.sh::command_invokes_git_commit`, which strips
 # common prefix shapes (leading whitespace, env-var assignments,
 # `cd <path> &&`) and checks whether the residual leading token pair
-# is literally `git commit`. P273: replaced the prior substring match
+# is literally `git commit`. p057-staging-trap-detect-sh-hook-substring-matches-git-commit-anywhere-in-bash-command-sibling-problem: replaced the prior substring match
 # `*"git commit"*` that misfired on non-commit Bash whose argument
 # vectors merely mentioned the phrase (grep / sed / cat-heredoc /
 # echo / `git log --grep`).
@@ -28,21 +28,21 @@
 #   - parse failure on stdin      (mirrors create-gate.sh fail-open)
 #
 # References:
-#   ADR-005 — plugin testing strategy (hook bats live under hooks/test/).
-#   ADR-009 — gate marker lifecycle (this hook deliberately does NOT
+#   plugin-testing-strategy-architecture-rule — plugin testing strategy (hook bats live under hooks/test/).
+#   gate-marker-lifecycle-ttl-drift-not-stop-hook-reset-architecture-rule — gate marker lifecycle (this hook deliberately does NOT
 #             use markers; detection is per-invocation deterministic).
-#   ADR-013 Rule 1 — deny redirects with mechanical recovery.
-#   ADR-017 — shared-code sync pattern (command-detect.sh canonical at
+#   structured-user-interaction-for-governance-skill-decisions-architecture-rule Rule 1 — deny redirects with mechanical recovery.
+#   shared-code-duplicated-into-per-package-lib-kept-in-sync-by-script-ci-drift-check-architecture-rule — shared-code sync pattern (command-detect.sh canonical at
 #             packages/shared/hooks/lib/; synced into per-package
 #             hooks/lib/ via scripts/sync-command-detect.sh).
-#   ADR-038 — progressive disclosure / deny-message terseness budget.
-#   P057    — original staging-trap ticket; this hook is the
+#   progressive-disclosure-once-per-session-budget-for-userpromptsubmit-governance-prose-architecture-rule — progressive disclosure / deny-message terseness budget.
+#   problem-057-git-mv-edit-git-add-staging-ordering-trap-drops-content-edits-from-the-commit-problem    — original staging-trap ticket; this hook is the
 #             enforcement layer the documentation alone didn't provide.
-#   P119    — sibling create-gate hook (PreToolUse:Write + lib/create-gate.sh).
-#   P125    — this hook.
-#   P268    — shared `command_invokes_git_commit` helper landed for
+#   agent-bypasses-wr-itil-manage-problem-step-2-duplicate-check-by-writing-tickets-directly-to-docs-problems-problem    — sibling create-gate hook (PreToolUse:Write + lib/create-gate.sh).
+#   staging-trap-recurs-despite-documentation-hook-level-enforcement-candidate-problem    — this hook.
+#   hook-substring-matches-git-commit-anywhere-in-bash-command-not-just-actual-git-commit-invocations-problem    — shared `command_invokes_git_commit` helper landed for
 #             `itil-readme-refresh-discipline.sh`.
-#   P273    — sibling-hook refactor: substring-match → helper here.
+#   p057-staging-trap-detect-sh-hook-substring-matches-git-commit-anywhere-in-bash-command-sibling-problem    — sibling-hook refactor: substring-match → helper here.
 
 SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
 # shellcheck source=lib/staging-detect.sh
@@ -79,7 +79,7 @@ except:
 # `lib/command-detect.sh::command_invokes_git_commit`, which strips
 # common prefix shapes (leading whitespace, env-var assignments,
 # `cd <path> &&`) and checks whether the residual leading token pair
-# is literally `git commit`. P273: replaces the prior substring match.
+# is literally `git commit`. p057-staging-trap-detect-sh-hook-substring-matches-git-commit-anywhere-in-bash-command-sibling-problem: replaces the prior substring match.
 command_invokes_git_commit "$COMMAND" || exit 0
 
 # Run detection. Helper echoes trap'd path on stdout when detected;
@@ -88,10 +88,10 @@ command_invokes_git_commit "$COMMAND" || exit 0
 TRAPPED_PATH=$(detect_p057_trap 2>/dev/null) && exit 0
 
 # Trap detected — emit deny with terse recovery.
-# Voice-tone draft target ~245 bytes; ADR-038 progressive-disclosure
-# budget. Keeps the rule cite (P057), the trap'd file path, and the
+# Voice-tone draft target ~245 bytes; progressive-disclosure-once-per-session-budget-for-userpromptsubmit-governance-prose-architecture-rule progressive-disclosure
+# budget. Keeps the rule cite (problem-057-git-mv-edit-git-add-staging-ordering-trap-drops-content-edits-from-the-commit-problem), the trap'd file path, and the
 # literal recovery command inline.
-REASON="BLOCKED: P057 staging-trap. Renamed file has unstaged post-rename edits: ${TRAPPED_PATH}. Run \`git add ${TRAPPED_PATH}\` then retry commit. Otherwise rename lands without the edit; edit drifts into next commit (audit-trail break)."
+REASON="BLOCKED: problem-057-git-mv-edit-git-add-staging-ordering-trap-drops-content-edits-from-the-commit-problem staging-trap. Renamed file has unstaged post-rename edits: ${TRAPPED_PATH}. Run \`git add ${TRAPPED_PATH}\` then retry commit. Otherwise rename lands without the edit; edit drifts into next commit (audit-trail break)."
 
 cat <<EOF
 {

package/hooks/pre-publish-intake-gate.sh

@@ -1,9 +1,9 @@
 #!/bin/bash
-# PreToolUse:Bash hook (P065 / ADR-036 Trigger 2): blocks `npm publish`
+# PreToolUse:Bash hook (problem-065-no-skill-scaffolds-intake-files-issue-template-security-md-contributing-md-support-md-in-downstream-projects-problem / scaffold-downstream-oss-intake-skill-layered-triggers-architecture-rule Trigger 2): blocks `npm publish`
 # and `gh pr merge` of a `changeset-release/*` PR when the project is
 # missing one or more of the five intake files.
 #
-# Required intake files (per ADR-036 Detection step 5):
+# Required intake files (per scaffold-downstream-oss-intake-skill-layered-triggers-architecture-rule Detection step 5):
 #   .github/ISSUE_TEMPLATE/config.yml
 #   .github/ISSUE_TEMPLATE/problem-report.yml
 #   SECURITY.md
@@ -15,7 +15,7 @@
 #                                      (consistent with RISK_BYPASS naming
 #                                      convention in external-comms-gate.sh)
 #   2. .claude/.intake-scaffold-declined marker present -> permit
-#                                      (ADR-009 marker semantics; explicit
+#                                      (gate-marker-lifecycle-ttl-drift-not-stop-hook-reset-architecture-rule marker semantics; explicit
 #                                      decline by adopter, persistent until
 #                                      file deleted)
 #   3. All five intake files present -> permit (idempotent default)
@@ -73,7 +73,7 @@ fi
 
 [ "$IN_SCOPE" = "1" ] || exit 0
 
-# ---------- 2. Decline marker (ADR-009 persistent marker) ----------
+# ---------- 2. Decline marker (gate-marker-lifecycle-ttl-drift-not-stop-hook-reset-architecture-rule persistent marker) ----------
 if [ -f ".claude/.intake-scaffold-declined" ]; then
     exit 0
 fi
@@ -100,7 +100,7 @@ deny_reason() {
     local missing_list
     missing_list=$(printf '  - %s\n' "${MISSING[@]}")
     cat <<EOF
-BLOCKED (P065 / ADR-036 pre-publish intake gate): ${#MISSING[@]} of 5 intake files missing — downstream reporters would hit a blank issue form and have no declared security-disclosure channel.
+BLOCKED (problem-065-no-skill-scaffolds-intake-files-issue-template-security-md-contributing-md-support-md-in-downstream-projects-problem / scaffold-downstream-oss-intake-skill-layered-triggers-architecture-rule pre-publish intake gate): ${#MISSING[@]} of 5 intake files missing — downstream reporters would hit a blank issue form and have no declared security-disclosure channel.
 
 Missing:
 ${missing_list}

package/hooks/staleness-check.sh

@@ -1,5 +1,5 @@
 #!/bin/bash
-# Plugin-staleness surfacer — UserPromptSubmit hook (ADR-088 / RFC-036 / P045 / P375).
+# Plugin-staleness surfacer — UserPromptSubmit hook (plugin-staleness-surfacer-per-plugin-per-turn-userpromptsubmit-surface-not-install-network-free-architecture-rule / plugin-staleness-surfacer-release-design / problem-045-auto-plugin-install-on-user-s-machine-after-governance-release-problem / repo-conflates-a-named-re-entry-point-with-a-self-firing-cadence-deferrals-not-transitively-reachable-from-an-automatic-trigger-rot-problem).
 #
 # Every turn, compare THIS session's running plugin version (inferred from the
 # hook's own script path in the plugin cache) against the highest version
@@ -7,17 +7,17 @@
 # ONE advisory line telling the user to restart to pick up the newer code.
 #
 # Network-free (own version from script path vs highest semver cache dir),
-# warn-only (never installs or restarts — P343 restart-required means an
+# warn-only (never installs or restarts — 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 restart-required means an
 # auto-refresh can't help THIS session anyway), fails quiet on any error
 # (fail-open), silent when the session is current, and emits at most once per
-# newly-detected version (a version-keyed extension of ADR-038's per-session
+# newly-detected version (a version-keyed extension of progressive-disclosure-once-per-session-budget-for-userpromptsubmit-governance-prose-architecture-rule's per-session
 # announcement marker) so it costs ~0 tokens on unchanged turns.
 #
 # Each plugin ships its own copy and emits its own line independently — no
-# cross-plugin coordination (eliminates the P260 shared-marker race).
+# cross-plugin coordination (eliminates the create-gate-marker-race-between-concurrent-claude-sessions-via-shared-runtime-sid-file-problem shared-marker race).
 #
 # Canonical source: packages/shared/hooks/staleness-check.sh. Synced to each
-# consumer plugin by scripts/sync-staleness-check.sh (ADR-017); CI
+# consumer plugin by scripts/sync-staleness-check.sh (shared-code-duplicated-into-per-package-lib-kept-in-sync-by-script-ci-drift-check-architecture-rule); CI
 # `npm run check:staleness-check` fails on drift.
 
 # Fail-open: any unexpected error → silent success, never block a turn.
@@ -56,7 +56,7 @@ HIGHEST="$(ls "$KEY_DIR" 2>/dev/null | grep -E '^[0-9]+\.[0-9]+\.[0-9]+$' | sort
 [ "$(printf '%s\n%s\n' "$SELF_VERSION" "$HIGHEST" | sort -V | tail -1)" = "$HIGHEST" ] || exit 0
 
 # Emit once per (session, key, detected-version): a version-keyed extension of
-# ADR-038's /tmp/${SYSTEM}-announced-${SESSION_ID} marker. A newer version
+# progressive-disclosure-once-per-session-budget-for-userpromptsubmit-governance-prose-architecture-rule's /tmp/${SYSTEM}-announced-${SESSION_ID} marker. A newer version
 # detected mid-session yields a new marker key → re-emitted once. Empty
 # SESSION_ID (test/manual) → no marker written, no dedup.
 SESSION_ID="$(cat 2>/dev/null | jq -r '.session_id // empty' 2>/dev/null)"

package/hooks-codex/hooks.json

@@ -0,0 +1,57 @@
+{
+  "hooks": {
+    "SessionStart": [
+      {
+        "matcher": "startup",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "${CLAUDE_PLUGIN_ROOT}/hooks/itil-codex-dispatch.sh session-start"
+          }
+        ]
+      }
+    ],
+    "UserPromptSubmit": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "${CLAUDE_PLUGIN_ROOT}/hooks/itil-codex-dispatch.sh user-prompt"
+          }
+        ]
+      }
+    ],
+    "PreToolUse": [
+      {
+        "matcher": "Bash|Write|Edit|Read|request_user_input|AskUserQuestion",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "${CLAUDE_PLUGIN_ROOT}/hooks/itil-codex-dispatch.sh pre-tool"
+          }
+        ]
+      }
+    ],
+    "PostToolUse": [
+      {
+        "matcher": "Bash|Write|Edit",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "${CLAUDE_PLUGIN_ROOT}/hooks/itil-codex-dispatch.sh post-tool"
+          }
+        ]
+      }
+    ],
+    "Stop": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "${CLAUDE_PLUGIN_ROOT}/hooks/itil-codex-dispatch.sh stop"
+          }
+        ]
+      }
+    ]
+  }
+}

package/lib/check-deferred-placeholder-staleness.sh

@@ -1,8 +1,8 @@
 #!/usr/bin/env bash
 # Deferred-placeholder + README-cadence staleness check — Step 0c of
-# /wr-itil:work-problems (per P271).
+# /wr-itil:work-problems (per wr-itil-review-problems-not-auto-fired-when-needed-user-has-to-remember-to-run-it-problem).
 #
-# P271 driver: /wr-itil:review-problems is the meta-workflow that re-rates
+# wr-itil-review-problems-not-auto-fired-when-needed-user-has-to-remember-to-run-it-problem driver: /wr-itil:review-problems is the meta-workflow that re-rates
 # the deferred-placeholder (Priority + Effort) WSJF inputs that
 # /wr-itil:capture-problem leaves behind. Without an auto-fire trigger, the
 # placeholders accumulate silently across sessions — 76 → 83 on the
@@ -11,7 +11,7 @@
 # maintainer manually invokes review-problems.
 #
 # Trigger rule — TWO-AXIS AND (load-bearing per architect verdict on the
-# P271 fix shape, Condition 2). Both axes must hold; either alone over-fires:
+# wr-itil-review-problems-not-auto-fired-when-needed-user-has-to-remember-to-run-it-problem fix shape, Condition 2). Both axes must hold; either alone over-fires:
 #
 #   1. count of deferred-placeholder tickets ≥ 3
 #      Signal: there is work to re-rate. A backlog with <3 placeholders is
@@ -35,7 +35,7 @@
 # Any change to the threshold constants (3 placeholders, 7 days) MUST
 # update this helper, work-problems SKILL.md Step 0c, manage-problem
 # SKILL.md Step 0.5, and capture-problem SKILL.md Step 7 in the same
-# commit — drift here re-opens P271.
+# commit — drift here re-opens wr-itil-review-problems-not-auto-fired-when-needed-user-has-to-remember-to-run-it-problem.
 #
 # Source this file, then call `should_promote_review_problems_dispatch`:
 #   . packages/itil/lib/check-deferred-placeholder-staleness.sh
@@ -48,15 +48,15 @@
 #                                                          line 3; first-run dispatch
 #                                                          trigger.
 #   fresh-readme count=<N> age=<X>s threshold=<Y>s      → README age within window;
-#                                                          silent-pass per ADR-013
+#                                                          silent-pass per structured-user-interaction-for-governance-skill-decisions-architecture-rule
 #                                                          Rule 5.
 #   stale-readme count=<N> age=<X>s threshold=<Y>s      → THE auto-dispatch
 #                                                          trigger; both axes met.
 #
-# Glob — DUAL-TOLERANT per ADR-031 RFC-002 migration window. Covers BOTH
+# Glob — DUAL-TOLERANT per problem-ticket-directory-layout-per-state-subdirectories-under-docs-problems-architecture-rule docs-problems-flat-layout-migration-per-state-subdirs-adopter-auto-migration-release-design migration window. Covers BOTH
 # the flat `docs/problems/<NNN>-<title>.<state>.md` layout AND the per-state
 # subdir `docs/problems/<state>/<NNN>-<title>.md` layout. Closed and
-# verifying tickets are EXCLUDED — they carry no dev-work WSJF per ADR-022
+# verifying tickets are EXCLUDED — they carry no dev-work WSJF per problem-lifecycle-add-a-verification-pending-status-between-known-error-and-closed-architecture-rule
 # and their deferred-placeholders are out-of-scope for re-rate.
 #
 # Dependencies: bash 4+, grep, awk, python3 (for date parsing — portable
@@ -71,7 +71,7 @@ should_promote_review_problems_dispatch() {
   local age_threshold_seconds=604800  # 7 days × 86400 seconds.
 
   # Axis 1 — count deferred-placeholder tickets across open + known-error
-  # via dual-tolerant globs (RFC-002 migration window).
+  # via dual-tolerant globs (docs-problems-flat-layout-migration-per-state-subdirs-adopter-auto-migration-release-design migration window).
   local count=0
   local marker='deferred — re-rate at next /wr-itil:review-problems'
   local file
@@ -106,14 +106,14 @@ should_promote_review_problems_dispatch() {
     return 0
   fi
 
-  # Read line 3 — the canonical "Last reviewed" surface per P134 + the
+  # Read line 3 — the canonical "Last reviewed" surface per docs-problems-readme-md-line-3-narrative-blob-accumulator-bloat-sibling-to-briefing-tier-3-on-a-different-surface-problem + the
   # SKILL.md contract. Use awk so the read survives BSD/GNU portability.
   local line3
   line3="$(awk 'NR==3' "$readme" 2>/dev/null || echo "")"
 
   # Parse the ISO date from the "Last reviewed: YYYY-MM-DD" prefix.
   # The line shape is `> Last reviewed: YYYY-MM-DD **<event>** — <summary>`
-  # per the P134 inline rotation contract. A missing or malformed line is
+  # per the docs-problems-readme-md-line-3-narrative-blob-accumulator-bloat-sibling-to-briefing-tier-3-on-a-different-surface-problem inline rotation contract. A missing or malformed line is
   # treated as no-readme (defensive — forces a fresh dispatch rather than
   # silently silent-passing on malformed README state).
   local last_reviewed_date

package/lib/check-outbound-responses-staleness.sh

@@ -1,6 +1,6 @@
 #!/usr/bin/env bash
 # Outbound-responses cache staleness check — Step 0d of /wr-itil:work-problems.
-# P220 + ADR-062 § JTBD-006 driver: work-problems should pre-flight
+# manage-problem-has-no-cadence-for-checking-upstream-bound-tickets-problem + inbound-upstream-report-discovery-assessment-pipeline-peer-of-architecture-rule § progress-the-backlog-while-i-m-away-user-outcome driver: work-problems should pre-flight
 # /wr-itil:check-upstream-responses when the outbound-responses cache is
 # stale or missing AND local tickets carry `## Reported Upstream` back-link
 # sections, so AFK loops keep upstream-reporter responses visible without
@@ -46,7 +46,7 @@ should_promote_outbound_responses_preflight() {
   fi
 
   # Scan for `## Reported Upstream` back-link sections. Dual-tolerant per
-  # RFC-002: flat layout `<NNN>-*.<status>.md` AND per-state subdir layout
+  # docs-problems-flat-layout-migration-per-state-subdirs-adopter-auto-migration-release-design: flat layout `<NNN>-*.<status>.md` AND per-state subdir layout
   # `<status>/<NNN>-*.md`. Use grep -l (files-with-match); silent on
   # zero matches via the `|| true` short-circuit.
   local back_link_count

package/lib/check-upstream-cache-staleness.sh

@@ -1,6 +1,6 @@
 #!/usr/bin/env bash
 # Inbound-discovery cache staleness check — Step 0b of /wr-itil:work-problems.
-# ADR-062 § JTBD-006 driver: work-problems should pre-flight
+# inbound-upstream-report-discovery-assessment-pipeline-peer-of-architecture-rule § progress-the-backlog-while-i-m-away-user-outcome driver: work-problems should pre-flight
 # /wr-itil:review-problems when the upstream inbound-discovery cache is stale
 # or missing, so AFK loops keep upstream-reported problems visible without
 # the maintainer remembering to invoke review-problems first.
@@ -19,7 +19,7 @@
 # Output (one of):
 #   no-channels-config           → channels-config absent; skip silently.
 #                                  Downstream-adopter non-obligation per
-#                                  ADR-062 § Downstream-adopter contract.
+#                                  inbound-upstream-report-discovery-assessment-pipeline-peer-of-architecture-rule § Downstream-adopter contract.
 #   first-run-cache-absent       → channels-config present, cache file absent.
 #                                  Dispatch review-problems.
 #   first-run-last-checked-null  → cache present but last_checked is null.

package/lib/derive-first-dispatch.sh

@@ -1,10 +1,10 @@
 #!/usr/bin/env bash
 # Shared derive-first dispatch helper — canonical source-of-truth.
 #
-# P132 Phase 2a-iii-A extracted this helper from three declaration-skill
+# agents-over-ask-in-interactive-sessions-conflating-mechanical-stages-with-user-interactive-stages-of-multi-stage-skill-contracts-inverse-problem Phase 2a-iii-A extracted this helper from three declaration-skill
 # surfaces. Phase 2a-iii-B (2026-05-16) added wr-architect:create-adr as
 # the 4th adopter, which required moving the canonical source from
-# packages/itil/lib/ to packages/shared/ per ADR-017 (Shared code
+# packages/itil/lib/ to packages/shared/ per shared-code-duplicated-into-per-package-lib-kept-in-sync-by-script-ci-drift-check-architecture-rule (Shared code
 # duplicated into per-package lib/ kept in sync by script + CI drift
 # check). The per-package lib/ copies are byte-identical to this file:
 #
@@ -19,15 +19,15 @@
 #   - packages/itil/skills/capture-problem/SKILL.md       Step 1.5
 #   - packages/itil/skills/manage-incident/SKILL.md       Step 4
 #   - packages/itil/skills/manage-problem/SKILL.md        Step 4
-#   - packages/architect/skills/create-adr/SKILL.md       Step 2     (P132 Phase 2a-iii-B)
+#   - packages/architect/skills/create-adr/SKILL.md       Step 2     (agents-over-ask-in-interactive-sessions-conflating-mechanical-stages-with-user-interactive-stages-of-multi-stage-skill-contracts-inverse-problem Phase 2a-iii-B)
 #
 # Each caller passes surface-specific signal definitions; this helper
 # centralises the dispatch mechanism: slug derivation, two-sided lexical
 # classifier, RISK-POLICY matrix lookup, and the I2-isomorphic stderr
 # advisory format.
 #
-# <!-- DERIVE-FIRST-DISPATCH-CONTRACT-SOURCE: P132 Phase 2a-iii-A + Phase 2a-iii-B -->
-# Drift in the stderr advisory format here re-opens P132 — any change MUST
+# <!-- DERIVE-FIRST-DISPATCH-CONTRACT-SOURCE: agents-over-ask-in-interactive-sessions-conflating-mechanical-stages-with-user-interactive-stages-of-multi-stage-skill-contracts-inverse-problem Phase 2a-iii-A + Phase 2a-iii-B -->
+# Drift in the stderr advisory format here re-opens agents-over-ask-in-interactive-sessions-conflating-mechanical-stages-with-user-interactive-stages-of-multi-stage-skill-contracts-inverse-problem — any change MUST
 # update all four caller SKILL.md surfaces in the same commit.
 #
 # Usage (sourced):
@@ -39,7 +39,7 @@
 #   risk_policy_matrix_lookup <text> <impact_high> <impact_mod> <impact_low>
 #                                    <likelihood_high> <likelihood_med> <likelihood_low>
 #
-# RETIRED 2026-06-02 (P287): lexical_classify_two_sided was the two-sided
+# RETIRED 2026-06-02 (remove-the-technical-user-business-type-classification-from-problems-redundant-with-rfc-story-persona-anchoring-amends-problem): lexical_classify_two_sided was the two-sided
 # binary classifier used exclusively by capture-problem Step 1.5 Type
 # classification (technical vs user-business). With the type axis retired
 # per twice-confirmed user direction, the function has no remaining
@@ -47,18 +47,18 @@
 # they serve manage-incident severity, manage-problem priority, and
 # create-adr title derivation.
 #
-# @adr ADR-002 (Monorepo per-plugin packages — architecture context for ADR-017)
-# @adr ADR-017 (Shared code duplicated into per-package lib/ kept in sync)
-# @adr ADR-044 (Decision-Delegation Contract — derive-first framework boundary)
-# @adr ADR-026 (cost-source grounding — stderr advisory)
-# @adr ADR-013 Rule 5 (policy-authorised silent proceed)
-# @adr ADR-052 (behavioural-by-default — tested via scripts/test/derive-first-dispatch.bats
+# @adr monorepo-with-independently-installable-per-plugin-packages-architecture-rule (Monorepo per-plugin packages — architecture context for shared-code-duplicated-into-per-package-lib-kept-in-sync-by-script-ci-drift-check-architecture-rule)
+# @adr shared-code-duplicated-into-per-package-lib-kept-in-sync-by-script-ci-drift-check-architecture-rule (Shared code duplicated into per-package lib/ kept in sync)
+# @adr decision-delegation-contract-when-agents-act-on-the-framework-vs-ask-the-user-architecture-rule (Decision-Delegation Contract — derive-first framework boundary)
+# @adr agent-output-grounding-no-fabricated-quantitative-estimates-cite-persist-uncertainty-architecture-rule (cost-source grounding — stderr advisory)
+# @adr structured-user-interaction-for-governance-skill-decisions-architecture-rule Rule 5 (policy-authorised silent proceed)
+# @adr behavioural-tests-default-for-skill-testing-architecture-rule (behavioural-by-default — tested via scripts/test/derive-first-dispatch.bats
 #               and packages/shared/test/sync-derive-first-dispatch.bats)
-# @problem P132 (agents over-ask in interactive sessions — Phase 2a-iii-A shared helper +
+# @problem agents-over-ask-in-interactive-sessions-conflating-mechanical-stages-with-user-interactive-stages-of-multi-stage-skill-contracts-inverse-problem (agents over-ask in interactive sessions — Phase 2a-iii-A shared helper +
 #                Phase 2a-iii-B 4th-adopter migration to packages/shared/)
-# @problem P185 (capture-problem Step 1.5 worked-example precedent)
-# @jtbd JTBD-001 (enforce governance without slowing down — primary)
-# @jtbd JTBD-101 (extend the suite with consistent patterns)
+# @problem wr-itil-capture-problem-asks-a-classification-question-technical-vs-user-business-that-it-can-answer-itself-from-the-description-s-observable-evidence-problem (capture-problem Step 1.5 worked-example precedent)
+# @jtbd enforce-governance-without-slowing-down-user-outcome (enforce governance without slowing down — primary)
+# @jtbd extend-the-suite-with-new-plugins-user-outcome (extend the suite with consistent patterns)
 #
 # NOT exporting `set -e` at file scope — callers source the helper and
 # expect functions that return AMBIGUOUS sentinels rather than errexit.
@@ -70,7 +70,7 @@
 #
 # This is the single source-of-truth for the advisory sentence shape
 # across all derive-first declaration-skill surfaces. The format is
-# load-bearing for cross-skill consistency — drift here re-opens P132.
+# load-bearing for cross-skill consistency — drift here re-opens agents-over-ask-in-interactive-sessions-conflating-mechanical-stages-with-user-interactive-stages-of-multi-stage-skill-contracts-inverse-problem.
 # ---------------------------------------------------------------------------
 emit_stderr_advisory() {
   local skill="$1"
@@ -93,7 +93,7 @@ emit_stderr_advisory() {
 #   - capture-problem Step 1.4 Title derivation
 #   - manage-incident Step 4 Title derivation
 #   - manage-problem Step 4 Title derivation
-#   - create-adr Step 2 Title derivation (P132 Phase 2a-iii-B)
+#   - create-adr Step 2 Title derivation (agents-over-ask-in-interactive-sessions-conflating-mechanical-stages-with-user-interactive-stages-of-multi-stage-skill-contracts-inverse-problem Phase 2a-iii-B)
 # ---------------------------------------------------------------------------
 derive_kebab_slug() {
   local description="$1"
@@ -131,7 +131,7 @@ derive_kebab_slug() {
 #   AMBIGUOUS|<reason>
 #     Multi-band hit (signals point to conflicting cells) OR zero hit
 #     (no mappable signal). Caller fires AskUserQuestion as the
-#     genuine ADR-044 category-5 (taste) fallback surface.
+#     genuine decision-delegation-contract-when-agents-act-on-the-framework-vs-ask-the-user-architecture-rule category-5 (taste) fallback surface.
 #
 # Band-to-numeric mapping (preserves RISK-POLICY.md Impact / Likelihood
 # Levels table):

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

@@ -1,22 +1,22 @@
 #!/usr/bin/env bash
 # Enumerate Known Error problem tickets whose Release-vehicle citation
 # points at a just-shipped changeset — input to the work-problems
-# Step 6.5 Post-release K→V auto-transition callback (P228).
+# Step 6.5 Post-release K→V auto-transition callback (known-error-md-verifying-md-transition-not-happening-consistently-at-release-time-problem).
 #
-# Driver: ADR-022 prescribes K→V transition on release, but until P228
+# Driver: problem-lifecycle-add-a-verification-pending-status-between-known-error-and-closed-architecture-rule prescribes K→V transition on release, but until known-error-md-verifying-md-transition-not-happening-consistently-at-release-time-problem
 # there was no auto-fire surface to back-fill the transition once a fix
 # ships. Iter subprocesses defer K→V to "the next session" citing a
-# misapplied P143 amendment, and tickets accumulate in
+# misapplied release-watch-sh-race-condition-gh-pr-list-queries-before-changesets-action-github-workflow-has-created-the-release-pr-problem amendment, and tickets accumulate in
 # `docs/problems/known-error/` with `## Fix Released` populated but no
-# transition. The 2026-06-08 P220 empirical witness confirmed the gap.
+# transition. The 2026-06-08 manage-problem-has-no-cadence-for-checking-upstream-bound-tickets-problem empirical witness confirmed the gap.
 #
-# Composes with `wr-itil-derive-release-vehicle` (P267) — the derive
+# Composes with `wr-itil-derive-release-vehicle` (codify-derive-release-vehicle-sh-helper-for-k-v-release-cycle-citation-problem) — the derive
 # helper's exit-code contract is the filter:
 #   exit 0  → changeset has been deleted from the working tree AND has a
 #             deletion commit in git history (released to npm). Emit as
 #             KV_CANDIDATE.
 #   exit 2  → no `.changeset/<name>.md` reference in ticket body
-#             (legacy ticket pre-P330). Skip silently.
+#             (legacy ticket pre-derive-release-vehicle-helper-requires-pre-edit-of-ticket-changeset-reference-three-touch-when-one-touch-would-suffice-problem). Skip silently.
 #   exit 3  → changeset still present in working tree (unreleased).
 #             Skip silently.
 #   other   → log to stderr, skip.
@@ -35,22 +35,22 @@
 #        empty or absent). Stderr carries non-fatal warnings.
 #
 # Glob — targets `docs/problems/known-error/*.md` directly (per-state
-# subdir layout per ADR-031). Flat-layout tickets are NOT in scope — the
+# subdir layout per problem-ticket-directory-layout-per-state-subdirectories-under-docs-problems-architecture-rule). Flat-layout tickets are NOT in scope — the
 # adopter has already migrated when this callback fires (work-problems
 # Step 0a auto-migrate runs before Step 6.5).
 #
 # Cross-references:
-#   @problem P228 (K→V auto-transition gap)
-#   @problem P220 (empirical witness)
-#   @problem P267 (derive-release-vehicle composed helper)
-#   @problem P330 (Release vehicle seed reference — input signal)
-#   @adr ADR-022 (Verifying lifecycle)
-#   @adr ADR-018 (release-cadence host of the callback)
-#   @adr ADR-031 (per-state subdir layout — glob target)
-#   @adr ADR-049 (bin/ PATH shim — adopter-safe script resolution)
-#   @adr ADR-005 (behavioural bats per P081)
-#   @jtbd JTBD-006 (Progress the Backlog While I'm Away — primary driver)
-#   @jtbd JTBD-001 (Enforce Governance Without Slowing Down — audit trail)
+#   @problem known-error-md-verifying-md-transition-not-happening-consistently-at-release-time-problem (K→V auto-transition gap)
+#   @problem manage-problem-has-no-cadence-for-checking-upstream-bound-tickets-problem (empirical witness)
+#   @problem codify-derive-release-vehicle-sh-helper-for-k-v-release-cycle-citation-problem (derive-release-vehicle composed helper)
+#   @problem derive-release-vehicle-helper-requires-pre-edit-of-ticket-changeset-reference-three-touch-when-one-touch-would-suffice-problem (Release vehicle seed reference — input signal)
+#   @adr problem-lifecycle-add-a-verification-pending-status-between-known-error-and-closed-architecture-rule (Verifying lifecycle)
+#   @adr inter-iteration-release-cadence-for-afk-loops-architecture-rule (release-cadence host of the callback)
+#   @adr problem-ticket-directory-layout-per-state-subdirectories-under-docs-problems-architecture-rule (per-state subdir layout — glob target)
+#   @adr plugin-bundled-scripts-invoked-from-skill-md-resolve-via-bin-on-path-architecture-rule (bin/ PATH shim — adopter-safe script resolution)
+#   @adr plugin-testing-strategy-architecture-rule (behavioural bats per problem-081-structural-source-content-tests-are-wasteful-tdd-agent-should-reject-them-and-require-behavioural-tests-framework-stub-enhancements-problem)
+#   @jtbd progress-the-backlog-while-i-m-away-user-outcome (Progress the Backlog While I'm Away — primary driver)
+#   @jtbd enforce-governance-without-slowing-down-user-outcome (Enforce Governance Without Slowing Down — audit trail)
 
 enumerate_postrelease_kv_candidates() {
   local problems_dir="${1:-docs/problems}"