@windyroad/itil 0.45.0 → 0.46.0-preview.514

package/.claude-plugin/plugin.json

@@ -497,5 +497,5 @@
     }
   },
   "name": "wr-itil",
-  "version": "0.45.0"
+  "version": "0.46.0"
 }

package/lib/derive-first-dispatch.sh

@@ -36,10 +36,17 @@
 # Exported functions:
 #   emit_stderr_advisory <skill> <field> <value> <source> [reversibility]
 #   derive_kebab_slug <description> [max_tokens=8]
-#   lexical_classify_two_sided <text> <side_a_patterns_var> <side_b_patterns_var>
 #   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
+# 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
+# consumer and was removed. The slug + advisory + matrix helpers stay —
+# 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)
@@ -105,60 +112,6 @@ derive_kebab_slug() {
     | paste -sd '-' -
 }
 
-# ---------------------------------------------------------------------------
-# lexical_classify_two_sided — two-sided binary lexical classifier.
-#
-# Used by capture-problem Step 1.5 Type classification (technical vs
-# user-business). Callers pass description text plus two regex pattern
-# arrays (by name); helper counts hits per side and echoes one of:
-#
-#   SIDE_A_UNAMBIGUOUS|<matched signals (comma-separated)>
-#     ≥1 side-A signal hit AND 0 side-B signals hit.
-#   SIDE_B_UNAMBIGUOUS|<matched signals (comma-separated)>
-#     0 side-A signals hit AND ≥1 side-B signal hit.
-#   AMBIGUOUS|<a=N b=N>
-#     Mixed (both sides matched) OR zero (neither side matched).
-#
-# Caller is responsible for:
-#   - Mapping SIDE_A/SIDE_B to its domain values (e.g. technical / user-business).
-#   - Calling emit_stderr_advisory on the unambiguous path.
-#   - Firing AskUserQuestion on the AMBIGUOUS path (ADR-044 category-5 taste fallback).
-# ---------------------------------------------------------------------------
-lexical_classify_two_sided() {
-  local description="$1"
-  local -n _side_a_patterns_ref="$2"
-  local -n _side_b_patterns_ref="$3"
-  local a_hits=()
-  local b_hits=()
-  local pattern
-
-  for pattern in "${_side_a_patterns_ref[@]}"; do
-    if printf '%s' "$description" | grep -qiE "$pattern" 2>/dev/null; then
-      a_hits+=("$pattern")
-    fi
-  done
-  for pattern in "${_side_b_patterns_ref[@]}"; do
-    if printf '%s' "$description" | grep -qiE "$pattern" 2>/dev/null; then
-      b_hits+=("$pattern")
-    fi
-  done
-
-  local a_count="${#a_hits[@]}"
-  local b_count="${#b_hits[@]}"
-
-  if (( a_count >= 1 && b_count == 0 )); then
-    local joined
-    joined=$(IFS=,; echo "${a_hits[*]}")
-    printf 'SIDE_A_UNAMBIGUOUS|%s\n' "$joined"
-  elif (( a_count == 0 && b_count >= 1 )); then
-    local joined
-    joined=$(IFS=,; echo "${b_hits[*]}")
-    printf 'SIDE_B_UNAMBIGUOUS|%s\n' "$joined"
-  else
-    printf 'AMBIGUOUS|a=%d b=%d\n' "$a_count" "$b_count"
-  fi
-}
-
 # ---------------------------------------------------------------------------
 # risk_policy_matrix_lookup — RISK-POLICY.md Impact × Likelihood lookup.
 #

package/package.json

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

package/scripts/test/derive-first-dispatch.bats

@@ -6,18 +6,24 @@ bats_require_minimum_version 1.5.0
 # the shared derive-first dispatch helper extracted in P132 Phase 2a-iii-A.
 #
 # The helper centralises the dispatch mechanism shipped across three
-# declaration-skill surfaces (capture-problem Step 1.5, manage-incident
-# Step 4, manage-problem Step 4). Each caller passes surface-specific
-# signal definitions; the helper owns:
+# declaration-skill surfaces (manage-incident Step 4, manage-problem
+# Step 4, create-adr Step 2 — Phase 2a-iii-B 4th adopter). Each caller
+# passes surface-specific signal definitions; the helper owns:
 #
 #   - Slug derivation (Title) from prose
-#   - Two-sided lexical classifier (Type for capture-problem)
 #   - RISK-POLICY matrix lookup (Severity / Priority)
 #   - I2-isomorphic stderr advisory format
 #
+# P287 (2026-06-02) retired the two-sided lexical classifier (formerly
+# used by capture-problem Step 1.5 Type classification — technical vs
+# user-business). The type axis was removed as redundant with RFC/Story
+# persona-anchoring per ADR-060 Phase 4; the function had no remaining
+# consumer.
+#
 # @problem P132 (agents over-ask in interactive sessions — Phase 2a-iii-A
 #   shared helper extraction)
-# @problem P185 (capture-problem Step 1.5 worked-example precedent)
+# @problem P185 (capture-problem Step 1.5 worked-example precedent — retired by P287)
+# @problem P287 (type-classification retirement — lexical_classify_two_sided removed)
 # @adr ADR-044 (Decision-Delegation Contract — derive-first framework
 #   resolution boundary)
 # @adr ADR-026 (cost-source grounding — stderr advisory shape)
@@ -118,51 +124,22 @@ setup() {
 }
 
 # ----------------------------------------------------------------------
-# Two-sided lexical classifier (capture-problem Step 1.5 mechanism).
-# Returns:
-#   SIDE_A_UNAMBIGUOUS|<matched signals>  — ≥1 A hit AND 0 B hits
-#   SIDE_B_UNAMBIGUOUS|<matched signals>  — 0 A hits AND ≥1 B hit
-#   AMBIGUOUS|<reason>                    — mixed (both sides) OR zero
+# P287 (2026-06-02) retirement: lexical_classify_two_sided removed.
+# Regression guard — the function must NOT exist in the helper.
 # ----------------------------------------------------------------------
 
-@test "lexical_classify_two_sided returns SIDE_A_UNAMBIGUOUS on technical-only signals" {
-  run -0 bash -c '
-    source "'"$HELPER"'"
-    side_a=("\\b(hook|gate|regex|stderr|stdout|drift|TTL|cache)\\b")
-    side_b=("\\b(adopter|UX|friction|JTBD-[0-9]+)\\b")
-    lexical_classify_two_sided "the hook fires on stderr and the cache invalidates" side_a side_b
-  '
-  [[ "$output" == "SIDE_A_UNAMBIGUOUS|"* ]]
+@test "P287: lexical_classify_two_sided is removed from the helper (regression guard)" {
+  # The function name must not appear as a function definition.
+  ! grep -E '^lexical_classify_two_sided\(\)' "$HELPER"
 }
 
-@test "lexical_classify_two_sided returns SIDE_B_UNAMBIGUOUS on user-business-only signals" {
-  run -0 bash -c '
-    source "'"$HELPER"'"
-    side_a=("\\b(hook|gate|regex|stderr|stdout|drift|TTL|cache)\\b")
-    side_b=("\\b(adopter|UX|friction|JTBD-[0-9]+)\\b")
-    lexical_classify_two_sided "the adopter friction makes JTBD-101 hard to complete" side_a side_b
-  '
-  [[ "$output" == "SIDE_B_UNAMBIGUOUS|"* ]]
-}
-
-@test "lexical_classify_two_sided returns AMBIGUOUS on mixed signals" {
-  run -0 bash -c '
-    source "'"$HELPER"'"
-    side_a=("\\b(hook|gate|regex|stderr)\\b")
-    side_b=("\\b(adopter|UX|friction)\\b")
-    lexical_classify_two_sided "the hook causes adopter friction" side_a side_b
-  '
-  [[ "$output" == "AMBIGUOUS|"* ]]
-}
-
-@test "lexical_classify_two_sided returns AMBIGUOUS on zero signals" {
-  run -0 bash -c '
-    source "'"$HELPER"'"
-    side_a=("\\b(hook|gate)\\b")
-    side_b=("\\b(adopter|UX)\\b")
-    lexical_classify_two_sided "totally bland text with no signals at all" side_a side_b
-  '
-  [[ "$output" == "AMBIGUOUS|"* ]]
+@test "P287: helper still exports the three surviving functions" {
+  # emit_stderr_advisory, derive_kebab_slug, risk_policy_matrix_lookup
+  # serve manage-incident severity, manage-problem priority, and
+  # create-adr title derivation — they must stay.
+  grep -E '^emit_stderr_advisory\(\)' "$HELPER"
+  grep -E '^derive_kebab_slug\(\)' "$HELPER"
+  grep -E '^risk_policy_matrix_lookup\(\)' "$HELPER"
 }
 
 # ----------------------------------------------------------------------
@@ -243,13 +220,6 @@ setup() {
 # packages/architect/lib/ stay byte-identical via scripts/sync-derive-first-dispatch.sh.
 # ----------------------------------------------------------------------
 
-@test "capture-problem Step 1.5 cross-references derive-first-dispatch.sh helper" {
-  run grep -c "derive-first-dispatch\\.sh\\|packages/itil/lib/derive-first-dispatch" \
-    "${PKG_ROOT}/skills/capture-problem/SKILL.md"
-  [ "$status" -eq 0 ]
-  [ "$output" -ge 1 ]
-}
-
 @test "manage-incident Step 4 cross-references derive-first-dispatch.sh helper" {
   run grep -c "derive-first-dispatch\\.sh\\|packages/itil/lib/derive-first-dispatch" \
     "${PKG_ROOT}/skills/manage-incident/SKILL.md"

package/scripts/test/no-type-regression-guard.bats

@@ -0,0 +1,73 @@
+#!/usr/bin/env bats
+
+# P287 regression guard — replaces the historical i2-no-type-branching.bats
+# (which asserted no-control-flow-branch-on-type as an I2 invariant).
+#
+# With the type axis retired per twice-confirmed user direction
+# (2026-05-25 + 2026-06-02), the I2 branch-protection invariant is
+# vacuous (no `type` field to branch on). This regression guard
+# preserves the audit-trail compliance evidence per architect-review
+# verdict 2026-06-02 by asserting the POSITIVE state:
+#
+# - The `**Type**:` body field is GONE from the capture-problem
+#   skeleton template and from every committed problem ticket.
+# - The `lexical_classify_two_sided` helper function is removed.
+# - capture-problem SKILL.md no longer carries the Step 1.5 Type
+#   classification section or its dispatch flags.
+#
+# Drift here = silent reintroduction of the type axis = P287 regression.
+#
+# @problem P287 (type-classification retirement)
+# @problem P176 (agent-side I2 coverage gap — historical; with the
+#   type axis retired the gap is vacuous on that axis)
+# @adr ADR-052 (behavioural-by-default; this is a regression-guard
+#   structural assertion per Surface 2 escape-hatch contract — the
+#   contract surface IS the on-disk artefact state)
+# @adr ADR-014 (single-purpose; one mechanical regression invariant)
+# @jtbd JTBD-001 (enforce governance without slowing down — primary)
+
+setup() {
+  REPO_ROOT="$(cd "$(dirname "$BATS_TEST_FILENAME")/../../../.." && pwd)"
+  PKG_ROOT="$REPO_ROOT/packages/itil"
+  SKILL_FILE="$PKG_ROOT/skills/capture-problem/SKILL.md"
+  HELPER="$REPO_ROOT/packages/shared/derive-first-dispatch.sh"
+  [ -f "$SKILL_FILE" ]
+  [ -f "$HELPER" ]
+}
+
+@test "P287: no committed problem ticket carries a **Type**: body field" {
+  # Find any docs/problems/**/*.md ticket that still carries the
+  # retired type field on a body line. Any match = P287 regression.
+  result=$(grep -r --include='*.md' -l '^\*\*Type\*\*: ' "$REPO_ROOT/docs/problems/" 2>/dev/null || true)
+  [ -z "$result" ]
+}
+
+@test "P287: capture-problem skeleton template does not include a **Type**: line" {
+  ! grep -F '**Type**: <type_value>' "$SKILL_FILE"
+  ! grep -F '**Type**: technical' "$SKILL_FILE"
+  ! grep -F '**Type**: user-business' "$SKILL_FILE"
+}
+
+@test "P287: capture-problem SKILL.md does not carry a Step 1.5 Type classification header" {
+  # The retired Step 1.5 section was titled "### 1.5 Type classification".
+  ! grep -E '^### 1\.5 Type classification' "$SKILL_FILE"
+}
+
+@test "P287: shared dispatch helper does not export lexical_classify_two_sided" {
+  ! grep -E '^lexical_classify_two_sided\(\)' "$HELPER"
+}
+
+@test "P287: per-package lib/ copies are byte-identical to the canonical shared/ source" {
+  # ADR-017 sync compliance — the strip removed lexical_classify_two_sided
+  # from the canonical packages/shared/derive-first-dispatch.sh; the
+  # sync script must propagate the removal to per-package copies.
+  diff -q "$HELPER" "$REPO_ROOT/packages/itil/lib/derive-first-dispatch.sh"
+  diff -q "$HELPER" "$REPO_ROOT/packages/architect/lib/derive-first-dispatch.sh"
+}
+
+@test "P287: capture-problem SKILL.md does not carry --type= or --no-prompt flag rows" {
+  # The retired Step 1.5 dispatch flags must not appear in the flag table.
+  ! grep -E '^\| `--type=technical`' "$SKILL_FILE"
+  ! grep -E '^\| `--type=user-business`' "$SKILL_FILE"
+  ! grep -E '^\| `--no-prompt`' "$SKILL_FILE"
+}

package/skills/capture-problem/SKILL.md

@@ -23,7 +23,7 @@ This skill is the foreground-lightweight-capture variant of `/wr-itil:manage-pro
 
 ## Rule 6 audit (per ADR-032 + ADR-013)
 
-This skill has **at most one classification-only AskUserQuestion (type-tag, ambiguous-signal fallback only) and zero control-flow branches keyed on the answer**. Each potentially-interactive decision is framework-mediated per ADR-044:
+This skill has **at most one classification-only AskUserQuestion (persona, on JTBD-cited descriptions with disagreeing personas only) and zero control-flow branches keyed on the answer**. Each potentially-interactive decision is framework-mediated per ADR-044:
 
 | Decision | Resolution |
 |----------|-----------|
@@ -33,9 +33,12 @@ This skill has **at most one classification-only AskUserQuestion (type-tag, ambi
 | Effort default | Framework-policy: `M` flagged "deferred — re-rate at next /wr-itil:review-problems". |
 | Multi-concern split | Out of scope: capture-problem creates one ticket per invocation. Multi-concern observations route to `/wr-itil:manage-problem` (its Step 4b owns the split). |
 | Empty `$ARGUMENTS` | Halt-with-stderr-directive: print "capture-problem requires a description in $ARGUMENTS — invoke /wr-itil:manage-problem instead for the full intake flow" and exit. AFK orchestrators MUST NOT invoke capture-problem with empty arguments — caller-side contract. |
-| Type classification (P170 / ADR-060 item 8c; P185 derive-first refactor) | **Derive-first; silent-framework per ADR-044 category 4 on unambiguous-signal descriptions; taste fallback per category 5 on ambiguous descriptions only.** Step 1.5 runs a lexical-signal classifier against the description text. Unambiguous one-sided signal → classify silently + emit stderr advisory. Mixed or zero signals → AskUserQuestion. `--type=<value>` pre-resolves silently (highest priority). `--no-prompt` defaults to `technical` silently (AFK contract). Maintainer-side ONLY: this dispatch is paired with JTBD-301 protection — `.github/ISSUE_TEMPLATE/problem-report.yml` (plugin-user-side intake) MUST NOT carry an equivalent type selector; triage assigns the type during `/wr-itil:manage-problem` ingestion of user-reported issues. **The classifier is also NOT invoked from `/wr-itil:manage-problem`'s ingestion-of-plugin-user-reports path** — plugin-user descriptions do not carry the same authorial intent as maintainer-internal captures, so triage stays user-judgement per JTBD-301. **I2 invariant** (ADR-060 line 98): the prompt is a classification facet, not a workflow split — Steps 0-7 control-flow is identical regardless of the chosen `type_value`; only the substituted value in the Step 4 skeleton template differs. The stderr advisory text shape is also I2-isomorphic: identical sentence structure across `technical` vs `user-business` classifications beyond the substituted values + signal names. |
+| JTBD-trace derivation (P287 retained surface) | **Derive-first; silent-framework per ADR-044 category 4 on lexical citations or `--jtbd=` flag pre-resolution.** Step 1.5b runs a lexical detector (`\bJTBD-[0-9]+\b`) against the description. Any cited JTBD IDs are recorded silently. No AskUserQuestion in this dispatch — capture-time JTBD anchoring is optional; the next reviewer can refine at `/wr-itil:review-problems` or `/wr-itil:manage-problem` ingestion. |
+| Persona derivation (P287 retained surface, decoupled from type) | **Derive-first; silent-framework per ADR-044 category 4 when JTBDs cited and agree.** If JTBDs were cited at Step 1.5b, persona derives from the cited JTBDs' frontmatter. Disagreement across cited JTBDs falls back to AskUserQuestion (genuine taste). Empty persona is legal — no hard-block. |
 
-Per ADR-013 Rule 6 fail-safe: every decision above resolves without interactive user input in non-interactive contexts (the type-tag carve-out resolves to `technical` via `--no-prompt` or `--type=` caller-side pre-resolution, or via the derive-first classifier on unambiguous descriptions). AFK orchestrators MUST pass `--no-prompt` or `--type=<value>` per JTBD-006 § Persona Constraints; AFK callers that omit both flags violate the caller-side contract. Interactive (pre-resolved, derive-classified, or ambiguous-fallback) and pre-resolved AFK paths produce identical observable outputs except for the `**Type**:` field value, satisfying the I2 invariant by construction.
+**P287 amendment 2026-06-02 — type-classification retired**: the maintainer-side type-classification dispatch (technical vs user-business) was REMOVED per twice-confirmed user direction (2026-05-25 + 2026-06-02). The redundant axis was already covered by RFC/Story persona-anchoring per ADR-060 Phase 4. JTBD-trace + persona dispatch survive as the JTBD-as-source-of-truth surface; the I12 hard-block (type-keyed JTBD-required halt) is also retired pending ADR-060 amendment substance ratification.
+
+Per ADR-013 Rule 6 fail-safe: every decision above resolves without interactive user input in non-interactive contexts. The Persona fallback AskUserQuestion fires only on cited-JTBD-disagreement (genuine ADR-044 category 5 taste); AFK orchestrators avoid this branch by passing `--persona=<value>` or by capturing without JTBD citations.
 
 ## Steps
 
@@ -60,84 +63,36 @@ fi
 
 `$ARGUMENTS` may carry up to two leading flags before the free-text description (caller-side pre-resolution per ADR-044 silent-proceed shape):
 
-| Flag | Effect on Step 1.5 |
+| Flag | Effect on Step 1.5b |
 |------|-------------------|
-| `--type=technical` | Pre-resolves type to `technical`; Step 1.5 skips the classifier and the AskUserQuestion. |
-| `--type=user-business` | Pre-resolves type to `user-business`; Step 1.5 skips the classifier and the AskUserQuestion. |
-| `--no-prompt` | Pre-resolves type to `technical` (default); Step 1.5 skips the classifier and the AskUserQuestion. |
-| `--jtbd=JTBD-NNN[,JTBD-NNN...]` | Pre-resolves the JTBD-trace value (Phase 4 P3.1 + I12 invariant per ADR-060 § Phase 3 + Phase 4 in-scope amendment 2026-05-13). Step 1.5b skips the JTBD-trace lexical dispatch and the I12 hard-block. Comma-separated list of JTBD IDs (no spaces). |
-| `--persona=<value>` | Pre-resolves the persona value (Phase 4 P4.2). Step 1.5b skips persona derivation. Value MUST be one of: `developer`, `tech-lead`, `plugin-developer`, `plugin-user`. |
+| `--jtbd=JTBD-NNN[,JTBD-NNN...]` | Pre-resolves the JTBD-trace value. Step 1.5b skips the JTBD-trace lexical dispatch. Comma-separated list of JTBD IDs (no spaces). |
+| `--persona=<value>` | Pre-resolves the persona value. Step 1.5b skips persona derivation. Value MUST be one of: `developer`, `tech-lead`, `plugin-developer`, `plugin-user`. |
+
+Strip recognised leading flags from `$ARGUMENTS`; the remainder (after flags) is the free-text description. Unknown leading flags halt-with-stderr-directive: print "capture-problem: unknown flag '<flag>' — recognised flags: --jtbd=JTBD-NNN, --persona=<value>" and exit.
 
-Strip recognised leading flags from `$ARGUMENTS`; the remainder (after flags) is the free-text description. If both `--type=<value>` and `--no-prompt` are present, `--type=<value>` wins (more specific). Unknown leading flags halt-with-stderr-directive: print "capture-problem: unknown flag '<flag>' — recognised flags: --type=technical, --type=user-business, --no-prompt, --jtbd=JTBD-NNN, --persona=<value>" and exit.
+**P287 retirement note**: `--type=technical`, `--type=user-business`, and `--no-prompt` are RETIRED (P287, 2026-06-02). The type-classification axis was removed per twice-confirmed user direction; the AFK-default flag `--no-prompt` is obsolete since the only AskUserQuestion it suppressed is gone. AFK orchestrators that previously passed `--no-prompt` should drop the flag; capture-problem is now silent-by-default.
 
 Empty description (post-flag-strip) halts per the Rule 6 audit above.
 
 Derive a kebab-case title slug from the first 8-10 non-stopword tokens of the description (matching the existing `manage-problem` slug derivation pattern).
 
-### 1.5 Type classification (derive-first; silent-framework per ADR-044 category 4; taste fallback per category 5 on ambiguity)
-
-**Shared dispatch helper**: this surface invokes `packages/itil/lib/derive-first-dispatch.sh` for the canonical lexical-classifier mechanism + I2-isomorphic stderr advisory format. The helper is sourced by `/wr-itil:capture-problem`, `/wr-itil:manage-incident`, and `/wr-itil:manage-problem`; drift in the advisory shape re-opens P132. Surface-specific signal definitions (technical-vs-user-business regex lists) stay inline below — the helper owns the mechanism, not the per-surface signals (architect verdict 2026-05-15 P132 Phase 2a-iii-A: "Helper must preserve per-surface signal definitions; only the dispatch mechanism is shared").
-
-Resolve `type_value` ∈ {`technical`, `user-business`} per the following framework-mediated dispatch. **The dispatch order is load-bearing** — pre-resolution flags short-circuit BEFORE the classifier runs, and the AskUserQuestion fires ONLY on genuinely-ambiguous descriptions.
-
-1. **If `--type=<value>` was set in Step 1**: use that value; do NOT run the classifier; do NOT fire AskUserQuestion (silent-proceed per ADR-013 Rule 5).
-2. **Else if `--no-prompt` was set in Step 1**: default `type_value = technical`; do NOT run the classifier; do NOT fire AskUserQuestion. JTBD-006 protection: AFK orchestrators MUST pass this flag (or `--type=<value>`).
-3. **Else** (interactive context, no caller-side pre-resolution): run the **lexical-signal classifier** against the description text:
-
-   **Technical signals** (regex; matched against the post-flag-strip description, case-insensitive unless noted):
-   - Code identifiers: `[a-z]+[A-Z][a-zA-Z]+` (camelCase), `[a-z]+-[a-z][a-z-]+` (kebab-case identifiers with ≥2 hyphens), `[a-z]+_[a-z][a-z_]+` (snake_case).
-   - File paths: `\.(md|sh|bats|ts|js|json|yaml|yml|py|rb|go|css|html)\b`, `packages/[a-z-]+/`, `docs/[a-z-]+/`, `\.github/`, `\.claude/`, `/tmp/`.
-   - Command-name patterns: `/wr-[a-z-]+:[a-z-]+\b`, `\bgit (commit|push|mv|add|rebase|merge)\b`, `\bnpm (run|install|publish)\b`, `\bbash\b`, `\bbats\b`, `\bgrep\b`, `\bsed\b`, `\bjq\b`.
-   - Mechanism words: `\b(drift|regression|hook|marker|gate|refresh|idempotent|exit code|stderr|stdout|regex|formula|dispatch|frontmatter|substring|escape|sentinel|bypass|TTL|cache|invalidate|deduplicate|race|deadlock|timeout|preflight)\b`.
-   - Error-message patterns: `\b(error|failure|exception|panic|stack trace|segfault|null pointer|undefined|not found|permission denied|EACCES|ENOENT|exit \d+)\b`.
-
-   **User-business signals** (regex; same casing):
-   - Persona names: `\b(adopter|adopters|plugin-user|plugin-users|solo[-_ ]?developer|maintainer-persona|end[-_ ]?user|customer|stakeholder)\b`.
-   - Journey words: `\b(workflow|journey|onboarding|friction|UX|experience|usability|discoverability|cognitive load|attention|interrupt|context-switch)\b`.
-   - JTBD-shaped need words: `\bJTBD-\d+\b`, `\bjob-to-be-done\b`, `\b(want|need|can't|cannot|blocked from|unable to|hard to|painful to)\b\s+(use|access|find|discover|complete)`, `\bdesired outcome\b`, `\bunmet need\b`.
-
-   **Decision rule**:
-
-   - **Unambiguous technical** (≥1 technical signal AND 0 user-business signals): set `type_value = technical`; emit stderr advisory and proceed. Do NOT fire AskUserQuestion.
-   - **Unambiguous user-business** (0 technical signals AND ≥1 user-business signal): set `type_value = user-business`; emit stderr advisory and proceed. Do NOT fire AskUserQuestion.
-   - **Ambiguous** (≥1 signal each side, OR 0 signals on both sides): fire AskUserQuestion with options `technical` (default) and `user-business`. Question text: *"What type of problem is this?"* Per-option descriptions:
-     - `technical` — *"Bug, defect, broken behaviour, framework drift — root cause sits in code or process."*
-     - `user-business` — *"Missing capability, UX gap, adopter friction, JTBD-shaped need — root cause sits in unmet user need."*
+### 1.5b JTBD-trace + persona dispatch (P287 — decoupled from type)
 
-   **Stderr advisory contract** (silent-classification path only): emit a SINGLE line to stderr (NOT stdout, NOT in the ticket body) via the shared helper's `emit_stderr_advisory` function in `packages/itil/lib/derive-first-dispatch.sh`. The canonical format produced by the helper:
-
-   ```
-   capture-problem: derived type=<value> from description signals: <signal1>, <signal2>[, ...]; re-invoke with --type=<other-value> to override
-   ```
-
-   The advisory text shape is I2-isomorphic — same sentence structure (`<skill>: derived <field>=<value> from <source>; <reversibility>`) across all three derive-first declaration-skill surfaces. The helper is the single source-of-truth for this format; drift here re-opens P132. Embedding the advisory in stdout would risk machine-readers parsing it as a ticket-body line; embedding it in the ticket body would violate ADR-060's frontmatter / body-bullet schema. Stderr is the correct channel — visible to interactive maintainers in the terminal; invisible to ticket consumers; loggable by AFK orchestrators that capture subprocess stderr.
-
-**I2 invariant guard (ADR-060 line 98)**: the resolved `type_value` is used at Step 4 ONLY as a substituted string in the skeleton template's `**Type**:` body field. Steps 2, 3, 4 (other than the `**Type**:` substitution), 5, 6, 7 execute identically regardless of `type_value`. The skill carries NO control-flow branch keyed on `type` — that would convert classification into a workflow split and violate I2. The lexical-signal classifier is UPSTREAM of the value's substitution (it resolves WHICH value to substitute, not WHICH workflow to execute); the substitution and all downstream steps remain uniform. Pure-bash supporting-script enforcement of this invariant lives in `packages/itil/scripts/test/i2-no-type-branching.bats`; the SKILL.md surface coverage gap is named at P176 (descendant of P012 master harness).
-
-**JTBD-301 scope guard**: this dispatch fires on the maintainer-side `/wr-itil:capture-problem` skill only. The plugin-user-side intake (`.github/ISSUE_TEMPLATE/problem-report.yml`) MUST NOT carry an equivalent type selector — plugin-user persona constraint is "no pre-classification". Triage assigns `type` during `/wr-itil:manage-problem` ingestion of user-reported issues, not at user-report time. **The lexical-signal classifier is ALSO NOT invoked from `/wr-itil:manage-problem`'s ingestion-of-plugin-user-reports path** — plugin-user descriptions do not carry the same authorial intent as maintainer-internal captures (a plugin-user describing their friction in maintainer-vocabulary terms would mis-classify); triage stays user-judgement, not lexical-classifier inference.
-
-### 1.5b JTBD-trace + persona dispatch (Phase 3 P3.1 + Phase 4 P4.2 + I12 invariant)
-
-Per ADR-060 § Phase 3 + Phase 4 in-scope amendment (2026-05-13). Fires ONLY when `type_value` resolved to `user-business` (whether via `--type=user-business` flag, `--no-prompt` default override is impossible since `--no-prompt` defaults to `technical`, the classifier silent-resolve to `user-business`, or the ambiguous-fallback AskUserQuestion). For `type_value = technical`, Steps 1.5b and the I12 hard-block do NOT fire (technical problems may carry empty `jtbd:` array; persona is optional). The whole dispatch keys on **nullable-field-conditional** shape per ADR-060 line 536 — NEVER on `type` value as a control-flow branch (preserves I2 invariant; the type co-incidence is upstream input, not control-flow key).
+Per ADR-060 § Phase 3 + Phase 4 in-scope amendment (2026-05-13), as amended by P287 (2026-06-02 — type-classification retired). Fires UNCONDITIONALLY (no longer keyed on `type_value = user-business`; the type axis was removed). Both `jtbd_trace_value` and `persona_value` are OPTIONAL — capture-time anchoring is best-effort; the next reviewer can refine at `/wr-itil:review-problems` or `/wr-itil:manage-problem` ingestion.
 
 **Resolve `jtbd_trace_value`** (an ORDERED list of JTBD IDs, possibly empty) via the following dispatch:
 
 1. **If `--jtbd=JTBD-NNN[,JTBD-NNN...]` was set in Step 1**: parse comma-separated list; assign to `jtbd_trace_value`; do NOT run the lexical detector; do NOT fire AskUserQuestion (silent-proceed per ADR-013 Rule 5).
 2. **Else** run the **lexical JTBD-trace detector** against the description: `grep -oE '\bJTBD-[0-9]+\b' | sort -u`. If matches found, set `jtbd_trace_value` to the matched IDs (de-duplicated, sorted ascending) and emit stderr advisory: `capture-problem: derived jtbd-trace=<id-list> from description JTBD-NNN citations; re-invoke with --jtbd= to override`. Do NOT fire AskUserQuestion.
-3. **Else (no flag, no lexical detection, type=user-business)**: **I12 hard-block** per ADR-060 Confirmation criterion 10. Halt-with-stderr-directive: print `capture-problem: I12 invariant — type: user-business requires ≥1 JTBD trace. Re-invoke with --jtbd=JTBD-NNN, OR edit the description to cite a JTBD-NNN ID, OR re-classify as technical via --type=technical.` and exit. This branch is the load-bearing enforcement of the new I12 invariant — JTBD-as-source-of-truth for persona-anchored unmet need; user-business problems MUST cite ≥1 JTBD.
+3. **Else (no flag, no lexical detection)**: leave `jtbd_trace_value` empty. The `**JTBD**:` line is omitted from the Step 4 skeleton template. No hard-block — capture-time JTBD anchoring is optional under P287; the I12 hard-block (type-keyed JTBD-required halt) was retired alongside the type axis. ADR-060 amendment substance (whether JTBD anchoring should become a nullable-field-conditional gate keyed on some other discriminator) is queued for user re-confirmation per ADR-074.
 
 **Resolve `persona_value`** (a scalar enum value OR empty) via the following dispatch:
 
 1. **If `--persona=<value>` was set in Step 1**: validate `<value>` ∈ `{developer, tech-lead, plugin-developer, plugin-user}`; halt with directive if invalid; otherwise assign and proceed silently.
-2. **Else if `jtbd_trace_value` is non-empty**: derive persona from cited JTBDs' frontmatter. Read each cited `docs/jtbd/<persona>/JTBD-<NNN>-*.md` file; extract its `persona:` (and optionally `secondary-persona:`) frontmatter values; if all cited JTBDs agree on a single persona, set `persona_value` to that persona silently and emit stderr advisory: `capture-problem: derived persona=<value> from cited JTBD <id> frontmatter`. If cited JTBDs disagree, fire AskUserQuestion with the union-of-derived-personas as options.
-3. **Else if `type_value = user-business`**: AskUserQuestion fires with the closed enum as options. Per ADR-060 P4.2: `developer | tech-lead | plugin-developer | plugin-user`. Question text: *"What persona does this user-business problem serve?"*
-4. **Else (`type_value = technical`)**: leave `persona_value` empty. `persona:` frontmatter is OPTIONAL on technical problems.
-
-**I12 hard-block escape hatch (none)**: there is no `BYPASS_I12=1` env override at the SKILL surface. The block is a load-bearing schema constraint per ADR-060 Confirmation criterion 10; if a maintainer captures a user-business problem without yet knowing the JTBD trace, they must EITHER capture as `--type=technical` and re-classify during `/wr-itil:manage-problem` ingestion (when the JTBD becomes clear), OR fast-capture a placeholder JTBD via `/wr-itil:capture-jtbd` (when it ships under Phase 4 follow-on) and reference it.
-
-**JTBD-301 scope preservation**: this dispatch ALSO fires on the maintainer-side `/wr-itil:capture-problem` only. Plugin-user-side `.github/ISSUE_TEMPLATE/problem-report.yml` MUST NOT prompt for JTBD trace or persona — preserves the JTBD-301 firewall per ADR-060 P4.3 maintainer-side / plugin-user-side asymmetry clarifier. Triage during `/wr-itil:manage-problem` ingestion assigns both fields from the reporter's symptom signals (per the JTBD-301 maintainer-side-complement extension landed 2026-05-13).
+2. **Else if `jtbd_trace_value` is non-empty**: derive persona from cited JTBDs' frontmatter. Read each cited `docs/jtbd/<persona>/JTBD-<NNN>-*.md` file; extract its `persona:` (and optionally `secondary-persona:`) frontmatter values; if all cited JTBDs agree on a single persona, set `persona_value` to that persona silently and emit stderr advisory: `capture-problem: derived persona=<value> from cited JTBD <id> frontmatter`. If cited JTBDs disagree, fire AskUserQuestion with the union-of-derived-personas as options (genuine taste per ADR-044 category 5 — cited JTBDs have ratified-coherent contradictory persona constraints, only the user can resolve which applies to THIS problem).
+3. **Else (no JTBDs cited, no `--persona=` flag)**: leave `persona_value` empty. `persona:` frontmatter is OPTIONAL — capture-time persona anchoring is best-effort.
 
-**Phase 3 P3.1 nullable-field-conditional shape**: the JTBD-trace prompt + I12 hard-block fire on `jtbd_trace_value` nullability (absent vs present), NOT on the `type` field's value. The composite gate (`type == user-business AND jtbd_trace_value == empty`) treats `type` as upstream-determined co-incident input — exactly the carve-out permitted by ADR-060 line 536. Steps 2-7 below execute identically regardless of `type_value`, `jtbd_trace_value`, or `persona_value`; only the values substituted into the Step 4 skeleton template differ. This preserves I2 control-flow uniformity AND extends the I2 behavioural test (per ADR-060 Confirmation criterion 11) to assert no control-flow branch on `persona:` field presence.
+**JTBD-301 scope preservation**: this dispatch fires on the maintainer-side `/wr-itil:capture-problem` only. Plugin-user-side `.github/ISSUE_TEMPLATE/problem-report.yml` MUST NOT prompt for JTBD trace or persona — preserves the JTBD-301 firewall per ADR-060 P4.3 maintainer-side / plugin-user-side asymmetry clarifier. Triage during `/wr-itil:manage-problem` ingestion assigns both fields from the reporter's symptom signals (per the JTBD-301 maintainer-side-complement extension landed 2026-05-13).
 
 ### 2. Minimal-grep duplicate check (3-keyword title-only) + hang-off-check subagent dispatch (P346 Phase 3 amendment, 2026-05-31)
 
@@ -196,9 +151,9 @@ fi
 
 **Empty-candidates short-circuit**: if `${#candidates[@]} -eq 0` (no shared signals), skip the dispatch and proceed to the marker step. The mechanical pre-filter found nothing to arbitrate.
 
-**JTBD-301 firewall** — sub-step 2b fires on maintainer-side `/wr-itil:capture-problem` invocations ONLY. Plugin-user-side `.github/ISSUE_TEMPLATE/problem-report.yml` MUST NOT carry an equivalent dispatch (plugin-user descriptions do not carry the same authorial intent; 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. Mirrors the existing Step 1.5 firewall at line 116.
+**JTBD-301 firewall** — sub-step 2b fires on maintainer-side `/wr-itil:capture-problem` invocations ONLY. Plugin-user-side `.github/ISSUE_TEMPLATE/problem-report.yml` MUST NOT carry an equivalent dispatch (plugin-user descriptions do not carry the same authorial intent; 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. Mirrors the Step 1.5b JTBD-trace firewall above.
 
-**AFK safe-default (--no-prompt / AFK propagation)**: when `--no-prompt` is set, the dispatch still fires (the subagent verdict is non-interactive by construction — no `AskUserQuestion`), and ambiguous-multi-parent cases collapse to `PROCEED_NEW` per the subagent's Rule 6 contract. This satisfies JTBD-006's "Decisions normally requiring my input are resolved using safe defaults."
+**AFK safe-default**: the hang-off-check subagent verdict is non-interactive by construction (no `AskUserQuestion`), and ambiguous-multi-parent cases collapse to `PROCEED_NEW` per the subagent's Rule 6 contract. This satisfies JTBD-006's "Decisions normally requiring my input are resolved using safe defaults" without dependency on the retired `--no-prompt` flag.
 
 **Dispatch** — when the candidate set is non-empty and ≤5, delegate to `wr-itil:hang-off-check` via the Agent tool with a structured input payload:
 
@@ -271,7 +226,6 @@ Log the renumber decision in the operation report if origin and local diverged.
 **Priority**: 3 (Medium) — Impact: 3 x Likelihood: 1 (deferred — re-rate at next /wr-itil:review-problems)
 **Origin**: internal
 **Effort**: M (deferred — re-rate at next /wr-itil:review-problems)
-**Type**: <type_value>
 **JTBD**: <jtbd_trace_value_as_comma_separated_list_OR_omit_line_when_empty>
 **Persona**: <persona_value_OR_omit_line_when_empty>
 
@@ -366,9 +320,10 @@ The trailing pointer is **not optional** — it is the user-visible signal that
 |---------|----------------|-----------------|
 | Duplicate-check | Wide-net grep + AskUserQuestion branch on matches | 3-keyword title-only grep, list-only (no branch) |
 | Multi-concern split | Step 4b AskUserQuestion | Out of scope (one ticket per invocation) |
-| Skeleton-fill | Full-intake; AskUserQuestion for missing fields | Deferred-placeholder pattern + derive-first type classification (AskUserQuestion fires only on ambiguous descriptions) |
-| Type-tag prompt | Step 4-equivalent AskUserQuestion fires alongside other intake fields | Step 1.5 derive-first dispatch — lexical-signal classifier silently resolves unambiguous descriptions (with stderr advisory); ambiguous descriptions fall back to classification-only AskUserQuestion. `--type=` and `--no-prompt` flags pre-resolve for non-interactive callers. I2 invariant: no control-flow branch keyed on type |
-| AskUserQuestion authority | Multiple branches (deviation-approval / direction-setting / taste / mechanical) | Zero unconditional AskUserQuestion fires; ambiguous-signal fallback only (silent-framework per ADR-044 cat. 4 on unambiguous; taste per cat. 5 on ambiguous); zero control-flow branches |
+| Skeleton-fill | Full-intake; AskUserQuestion for missing fields | Deferred-placeholder pattern; no classification AskUserQuestion (P287 retired the type prompt) |
+| Type-tag prompt | RETIRED (P287, 2026-06-02) | RETIRED (P287, 2026-06-02) — the technical/user-business axis was removed as redundant with RFC/Story persona-anchoring per ADR-060 Phase 4 |
+| JTBD-trace + persona | Step 4-equivalent ingestion path | Step 1.5b derive-first dispatch — lexical citations + `--jtbd=` flag pre-resolve silently; persona derives from cited JTBDs' frontmatter; persona-disagreement AskUserQuestion is the only taste fallback |
+| AskUserQuestion authority | Multiple branches (deviation-approval / direction-setting / taste / mechanical) | Zero unconditional AskUserQuestion fires; persona-disagreement fallback only (silent-framework per ADR-044 cat. 4 by default; cat. 5 taste on JTBD-persona disagreement); zero control-flow branches |
 | README refresh | P094 inline (regenerate + stage in same commit) | Deferred to next `/wr-itil:review-problems` |
 | Status transitions | Step 7 owns Open → Known Error → Verifying → Closed | Out of scope (creation only) |
 | Commit grain | One commit per intake (or per split-concern set) | One commit per capture |
@@ -384,21 +339,22 @@ The two skills share the `/tmp/manage-problem-grep-${SESSION_ID}` create-gate ma
 - **P119** — manage-problem create-gate hook; capture-problem composes with the same marker.
 - **P262** — the P165 README-refresh-discipline hook conflicted with this skill's deferred-README-refresh contract (Step 6 "do NOT stage README" was denied by the hook on every capture commit). Resolved by the `RISK_BYPASS: capture-deferred-readme` allow-list token (Step 6 trailer above); clears the README-refresh gate only, not the risk-score gate.
 - **P265** — the RISK_BYPASS-trailer allow-list mechanism in `readme-refresh-detect.sh` that P262's `capture-deferred-readme` token registers into.
-- **P170** (`docs/problems/known-error/170-problem-tickets-strain-as-fixes-decompose-into-multiple-coordinated-changes-need-rfc-framework.md`) — RFC framework driver; Slice 4 B7.T3 / item 8c authored the type-classification prompt at Step 1.5.
-- **P176** — agent-side I2 (no type-branching) coverage gap on the SKILL.md surface (this file's surface); descendant of P012 master harness ticket. The Step 1.5 I2 invariant guard is enforced by audit-trailed prose here per ADR-052 § Surface 2 escape-hatch contract; behavioural enforcement awaits the master harness.
+- **P170** (`docs/problems/known-error/170-problem-tickets-strain-as-fixes-decompose-into-multiple-coordinated-changes-need-rfc-framework.md`) — RFC framework driver; Slice 4 B7.T3 / item 8c historically authored the type-classification prompt at Step 1.5 (RETIRED by P287, 2026-06-02).
+- **P176** — agent-side I2 (no type-branching) coverage gap on the SKILL.md surface. P287 retires the type axis altogether; the regression guard is preserved under `packages/itil/scripts/test/no-type-regression-guard.bats` (asserting the `**Type**:` field is GONE from skeleton templates).
+- **P287** (`docs/problems/.../287-remove-technical-user-business-type-classification-from-problems-redundant-with-rfc-persona-anchoring.md`) — the user direction (twice-confirmed 2026-05-25 + 2026-06-02) that retired Step 1.5 Type classification; ADR-060 amendment substance (I12 replacement, Phase-4 rework) queued for user re-confirmation per ADR-074.
 - **ADR-032** (`docs/decisions/032-governance-skill-invocation-patterns.proposed.md`) — foreground-lightweight-capture variant amendment (P155); 5th invocation pattern amendment (P346 Phase 3, 2026-05-31) codifies the hang-off-check sub-step 2b dispatch as the canonical fresh-context-subagent-as-decision-arbiter shape.
 - **P346** (`docs/problems/.../346-...md`) — backlog-flow-control master ticket; Phase 3 deliverable lands the hang-off-check dispatch at sub-step 2b above.
 - **RFC-013** (`docs/rfcs/RFC-013-...proposed.md`) — traces P346 Phases 1+2+3 per ADR-071 unconditional Problem→RFC trace.
 - **`packages/itil/agents/hang-off-check.md`** — the fresh-context subagent invoked by sub-step 2b; reads only the structured input payload; emits HANG_OFF: P<NNN> or PROCEED_NEW with rationale + signals + absorb directive.
 - **ADR-038** — progressive-disclosure pattern (SKILL.md + REFERENCE.md split).
-- **ADR-044** — decision-delegation contract; type classification is **derive-first**: silent-framework per category 4 on unambiguous-signal descriptions (the classifier IS the framework resolving the answer from observable evidence per ADR-026 grounding); taste per category 5 fallback on genuinely-ambiguous descriptions only. `--no-prompt` / `--type=<value>` are policy-authorised silent-proceed shapes per category 4 (caller-side pre-resolution). P185 re-classified Step 1.5's taxonomy position from "cat 5 unconditional ask" to "cat 4 derive-first with cat 5 fallback".
-- **P185** — `/wr-itil:capture-problem` asks a classification question it can answer itself from the description's observable evidence — inverse-P078 / P132 trap at a SKILL contract surface. The Step 1.5 derive-first refactor (lexical-signal classifier + stderr advisory) ships this fix.
+- **ADR-044** — decision-delegation contract. Persona derivation (Step 1.5b) is **derive-first**: silent-framework per category 4 when cited JTBDs agree on persona; taste per category 5 fallback only on cited-JTBD-persona disagreement. JTBD-trace itself is purely category 4 (lexical detection or `--jtbd=` flag pre-resolution). The retired Step 1.5 Type classification was a derive-first dispatch too (RETIRED by P287, 2026-06-02).
+- **P185** — `/wr-itil:capture-problem` historical: asked a classification question (type) it could answer itself; the Step 1.5 derive-first refactor (lexical-signal classifier + stderr advisory) shipped the fix in 2026-05-15. P287 then retired the entire surface in 2026-06-02 as the classification axis itself was redundant with RFC/Story persona-anchoring.
 - **ADR-049** — bin/ on PATH; capture-problem reuses the existing `wr-itil-reconcile-readme` shim.
 - **ADR-052** — behavioural-tests-default for skill testing; SKILL.md I2 surface coverage gap is named, not silent (P176 + ADR-052 § Surface 2).
-- **ADR-060** (`docs/decisions/060-...accepted.md`) — Phase 1 item 8c authored Step 1.5 here; I2 invariant (line 98) governs the no-control-flow-branch contract; line 132 names the maintainer-side-only / JTBD-301-protection scope; line 160 (Confirmation criterion 4) gates the type-prompt placement.
-- **JTBD-301** (`docs/jtbd/plugin-user/JTBD-301-...md`) — plugin-user no-pre-classification persona constraint; protected by the Step 1.5 maintainer-side scope guard.
+- **ADR-060** (`docs/decisions/060-...accepted.md`) — body currently encodes the type-tag schema (Decision Outcome item 1, I2 type-uniformity, I12 hard-block, Phase-4 persona+jtbd machinery keyed on `type:user-business`). P287 retires the SKILL implementation of these clauses unilaterally per twice-confirmed user direction; the ADR body amendment substance (I12 replacement shape, Phase-4 rework) is queued for user re-confirmation per ADR-074. Until the amendment lands, ADR-060 body and SKILL implementation are intentionally inconsistent — this is the P287 trade-off the user accepted.
+- **JTBD-301** (`docs/jtbd/plugin-user/JTBD-301-...md`) — plugin-user no-pre-classification persona constraint; the Step 1.5b maintainer-side scope guard preserves the firewall on the JTBD-trace + persona axis. The type-axis firewall is moot (axis retired).
 - `packages/itil/skills/manage-problem/SKILL.md` — heavyweight intake counterpart.
 - `packages/itil/skills/review-problems/SKILL.md` — re-rates the deferred placeholders + refreshes README.md.
-- `packages/itil/scripts/test/i2-no-type-branching.bats` — pure-bash supporting-script enforcement of the I2 invariant; this SKILL.md change does not affect any pure-bash script and so does not change the bats outcome (still green).
+- `packages/itil/scripts/test/no-type-regression-guard.bats` — pure-bash regression guard that the `**Type**:` field stays GONE from skeleton templates + ticket bodies. Replaces the historical `i2-no-type-branching.bats` (which asserted no-control-flow-branch-on-type; with the type axis retired, the branch-protection invariant is vacuous, but the field-absence regression guard preserves the audit trail per architect-review verdict 2026-06-02).
 
 $ARGUMENTS

package/skills/capture-problem/test/capture-problem-step-1-5b-jtbd-trace.bats

@@ -1,18 +1,22 @@
 #!/usr/bin/env bats
 
-# P170 / Phase 3 P3.1 + Phase 4 P4.2 + I12 — behavioural fixture for
+# P170 / Phase 3 P3.1 + Phase 4 P4.2 — behavioural fixture for
 # capture-problem Step 1.5b JTBD-trace + persona dispatch. Per ADR-060
-# § Phase 3 + Phase 4 in-scope amendment (2026-05-13):
+# § Phase 3 + Phase 4 in-scope amendment (2026-05-13), as amended by
+# P287 (2026-06-02 — type-classification + I12 hard-block retired):
 #
 # - Lexical JTBD-trace detection: description-contains-JTBD-NNN-ID →
 #   silent-resolve jtbd_trace_value to the matched IDs.
-# - I12 hard-block: type=user-business AND jtbd_trace_value empty AND
-#   no --jtbd flag → halt-with-stderr-directive.
 # - --jtbd=JTBD-NNN[,...] flag pre-resolves jtbd_trace_value silently.
 # - --persona=<value> flag pre-resolves persona_value silently.
 # - Skeleton template carries **JTBD**: and **Persona**: body fields
-#   (matches existing **Status**: / **Type**: convention; frontmatter
-#   migration deferred to follow-on slice).
+#   (frontmatter migration deferred to follow-on slice).
+#
+# P287 retirement: the I12 hard-block (type=user-business + empty jtbd
+# → halt) was retired alongside the type axis. JTBD-trace is now purely
+# best-effort capture-time anchoring; the I12 reference-impl predicate
+# below is preserved as a NEGATIVE assertion (never blocks) for
+# regression-guard purposes per architect-review verdict 2026-06-02.
 #
 # Reference-impl pattern: this fixture exercises the algorithm directly
 # via shell helpers; the SKILL.md prose at runtime executes the same
@@ -32,15 +36,12 @@ detect_jtbd_trace() {
   echo "$desc" | grep -oE '\bJTBD-[0-9]+\b' | sort -u | tr '\n' ' ' | sed 's/[[:space:]]*$//'
 }
 
-# Reference implementation of the I12 hard-block predicate. Returns
-# 0 (true → block) when type=user-business AND jtbd_trace empty AND
-# no --jtbd flag was provided. Returns 1 otherwise.
+# P287 retirement: the I12 hard-block was retired alongside the type
+# axis. This predicate now ALWAYS returns 1 (never blocks) — preserved
+# as a regression-guard so future drift that re-introduces a type-keyed
+# hard-block surfaces as a test failure.
 i12_should_block() {
-  local type_value="$1" jtbd_trace="$2" had_jtbd_flag="$3"
-  [ "$type_value" = "user-business" ] || return 1
-  [ -z "$jtbd_trace" ] || return 1
-  [ "$had_jtbd_flag" = "0" ] || return 1
-  return 0
+  return 1
 }
 
 # Reference implementation of --jtbd= flag parser. Accepts CSV; returns
@@ -89,20 +90,16 @@ validate_persona() {
   [ "$result" = "JTBD-001" ]
 }
 
-@test "I12 i12_should_block: user-business + empty jtbd + no flag → blocks" {
-  i12_should_block "user-business" "" "0"
-}
-
-@test "I12 i12_should_block: user-business + non-empty jtbd → does NOT block" {
+@test "P287 i12 hard-block retired: never blocks regardless of inputs (regression guard)" {
+  # After P287, the I12 hard-block is retired. The predicate must never
+  # return 0 (block) for any input combination — capture-time JTBD
+  # anchoring is best-effort, not hard-required. If a future maintainer
+  # re-introduces a type-keyed hard-block, this test catches it.
+  ! i12_should_block "user-business" "" "0"
   ! i12_should_block "user-business" "JTBD-001" "0"
-}
-
-@test "I12 i12_should_block: user-business + empty jtbd + --jtbd flag set → does NOT block" {
   ! i12_should_block "user-business" "" "1"
-}
-
-@test "I12 i12_should_block: technical + empty jtbd → does NOT block (technical has no JTBD requirement)" {
   ! i12_should_block "technical" "" "0"
+  ! i12_should_block "anything" "anything" "anything"
 }
 
 @test "P3.1 parse_jtbd_flag: --jtbd=JTBD-NNN parses single ID" {
@@ -116,7 +113,7 @@ validate_persona() {
 }
 
 @test "P3.1 parse_jtbd_flag: non-jtbd-flag arg returns empty" {
-  result=$(parse_jtbd_flag "--type=user-business")
+  result=$(parse_jtbd_flag "--persona=plugin-user")
   [ -z "$result" ]
 }
 

package/skills/capture-problem/test/capture-problem.bats

@@ -324,271 +324,24 @@ EOF
 }
 
 # ---------------------------------------------------------------------------
-# P185 — Step 1.5 derive-first classifier behavioural tests.
+# P287 (2026-06-02) — retirement of P185 Step 1.5 derive-first classifier.
 #
-# The classifier is an agent-driven SKILL.md instruction (not a pure-bash
-# script), so these tests mirror the lexical-signal regex sets from
-# SKILL.md and assert classification outcomes on fixture descriptions —
-# same shape as the existing next-ID-formula and duplicate-grep tests
-# that mirror manage-problem Step 3 / capture-problem Step 2 formulas.
+# The type-classification axis was REMOVED per twice-confirmed user
+# direction (2026-05-25 + 2026-06-02). The lexical-signal classifier,
+# stderr-advisory contract, flag pre-resolution dispatch, and
+# meta-recursive corpus assertions that lived here have been removed —
+# they exercise behaviour that no longer exists in capture-problem.
 #
-# Per ADR-052 (behavioural-tests-default): observable input → output
-# assertions on the classifier's resolution function. Per P081: NOT
-# grepping SKILL.md prose for signal-token references — that would be
-# the structural-test-disguised-as-behavioural anti-pattern.
-#
-# I2 protection: each test exercises both `technical` and `user-business`
-# classification paths and asserts the stderr-advisory shape is
-# isomorphic beyond the substituted type-value + signal names.
-# ---------------------------------------------------------------------------
-
-# Mirror of the SKILL.md Step 1.5 classifier — emits "technical",
-# "user-business", or "ambiguous" on stdout. Always returns 0 so the
-# `result=$(classify_description ...)` substitution in tests below
-# never trips bats' default-fail-on-nonzero-substitution behaviour;
-# tests assert on the string verdict, not the exit code.
-#
-# This helper mirrors the SKILL.md regex set so the test exercises the
-# classifier's load-bearing pattern set; drift between this helper and
-# SKILL.md is the failure mode this test corpus catches.
-classify_description() {
-  local desc="$1"
-  local tech_signals=()
-  local ub_signals=()
-
-  # Technical signals — case-insensitive matching via grep -E -o -i.
-  # Each match contributes the matched token to the signal list.
-  local tech_patterns=(
-    '[a-z]+[A-Z][a-zA-Z]+'                    # camelCase (case-SENSITIVE - the case shape is the signal)
-    '[a-z]+-[a-z][a-z-]+-[a-z][a-z-]+'        # kebab-case with >=2 hyphens
-    '[a-z]+_[a-z][a-z_]+'                     # snake_case
-    '\.(md|sh|bats|ts|js|json|yaml|yml|py|rb|go|css|html)\b'
-    'packages/[a-z-]+/'
-    'docs/[a-z-]+/'
-    '\.github/'
-    '/tmp/'
-    '/wr-[a-z-]+:[a-z-]+'
-    '\bgit (commit|push|mv|add|rebase|merge)\b'
-    '\bnpm (run|install|publish)\b'
-    '\b(bash|bats|grep|sed|jq)\b'
-    '\b(drift|regression|hook|marker|gate|refresh|idempotent|stderr|stdout|regex|formula|dispatch|frontmatter|substring|escape|sentinel|bypass|TTL|cache|invalidate|deduplicate|race|deadlock|timeout|preflight)\b'
-    '\b(error|failure|exception|panic|segfault|undefined|EACCES|ENOENT)\b'
-  )
-
-  # User-business signals — case-insensitive.
-  local ub_patterns=(
-    '\b(adopter|adopters|plugin-user|plugin-users|solo[-_ ]?developer|maintainer-persona|end[-_ ]?user|customer|stakeholder)\b'
-    '\b(workflow|journey|onboarding|friction|UX|experience|usability|discoverability)\b'
-    '\bJTBD-[0-9]+\b'
-    '\bjob-to-be-done\b'
-    '\b(want|need|cannot|unable to)\b[[:space:]]+(use|access|find|discover|complete)'
-    '\bdesired outcome\b'
-    '\bunmet need\b'
-  )
-
-  for p in "${tech_patterns[@]}"; do
-    if echo "$desc" | grep -qE "$p" 2>/dev/null; then
-      tech_signals+=("$p")
-    fi
-  done
-
-  for p in "${ub_patterns[@]}"; do
-    if echo "$desc" | grep -qiE "$p" 2>/dev/null; then
-      ub_signals+=("$p")
-    fi
-  done
-
-  local tech_n="${#tech_signals[@]}"
-  local ub_n="${#ub_signals[@]}"
-
-  if [ "$tech_n" -ge 1 ] && [ "$ub_n" -eq 0 ]; then
-    echo "technical"
-  elif [ "$tech_n" -eq 0 ] && [ "$ub_n" -ge 1 ]; then
-    echo "user-business"
-  else
-    echo "ambiguous"
-  fi
-  return 0
-}
-
-@test "P185: classifier resolves pure-technical description as technical" {
-  # camelCase identifier + file path + mechanism word — all technical signals.
-  result=$(classify_description "The captureProblem hook in packages/itil/hooks/lib/detectors.sh has a regex drift")
-  [ "$result" = "technical" ]
-}
-
-@test "P185: classifier resolves pure-technical description (error-message variant)" {
-  result=$(classify_description "The bats test exits with exception ENOENT on /tmp/manage-problem-grep")
-  [ "$result" = "technical" ]
-}
-
-@test "P185: classifier resolves pure-technical description (command-name variant)" {
-  result=$(classify_description "git mv to docs/problems/<NNN>.verifying.md fails on the rebase merge")
-  [ "$result" = "technical" ]
-}
-
-@test "P185: classifier resolves pure-user-business description (persona + journey)" {
-  result=$(classify_description "Adopters cannot complete the onboarding workflow without UX friction")
-  [ "$result" = "user-business" ]
-}
-
-@test "P185: classifier resolves pure-user-business description (JTBD-shaped need)" {
-  result=$(classify_description "JTBD-101 names a desired outcome the plugin-user cannot achieve")
-  [ "$result" = "user-business" ]
-}
-
-@test "P185: classifier resolves pure-user-business description (unmet-need variant)" {
-  result=$(classify_description "Solo-developers want to discover scaffold templates but cannot find them")
-  [ "$result" = "user-business" ]
-}
-
-@test "P185: classifier resolves mixed-signal description as ambiguous" {
-  # Mentions both technical mechanism (hook drift) and user-business (adopter friction)
-  # — exactly the case the AskUserQuestion fallback is designed for.
-  result=$(classify_description "The hook drift affects adopters in the onboarding workflow")
-  [ "$result" = "ambiguous" ]
-}
-
-@test "P185: classifier resolves no-signal description as ambiguous" {
-  # Plain prose with no technical or user-business signals — fallback to ask.
-  result=$(classify_description "Something is off but I cannot describe it well")
-  [ "$result" = "ambiguous" ]
-}
-
-# ---------------------------------------------------------------------------
-# Stderr-advisory shape — I2 isomorphism guard.
-# Per architect-review rider: the advisory text MUST be identical in
-# sentence structure across `technical` vs `user-business` classifications
-# beyond the substituted type-value tokens. Otherwise the advisory itself
-# becomes a control-flow asymmetry keyed on `type` and re-introduces an
-# I2 leak through the back door.
-# ---------------------------------------------------------------------------
-
-# Mirror of the SKILL.md advisory template. P132 Phase 2a-iii-A renamed
-# the verb from `classified` to `derived` to align with the shared helper
-# `packages/itil/lib/derive-first-dispatch.sh`'s emit_stderr_advisory
-# function — I2-isomorphic format `<skill>: derived <field>=<value> from
-# <source>; <reversibility>` across all three derive-first declaration-skill
-# surfaces.
-format_stderr_advisory() {
-  local resolved_type="$1"
-  local other_type="$2"
-  local signals="$3"
-  printf 'capture-problem: derived type=%s from description signals: %s; re-invoke with --type=%s to override\n' \
-    "$resolved_type" "$signals" "$other_type"
-}
-
-# Strip the type-value tokens + signal-name list so we can compare the
-# sentence skeleton in isolation.
-strip_substituted_tokens() {
-  sed -E 's/type=[a-z-]+/type=<X>/g; s/signals: [^;]+;/signals: <S>;/g'
-}
-
-@test "P185: stderr advisory shape is isomorphic across technical vs user-business classifications" {
-  tech_msg=$(format_stderr_advisory technical user-business "camelCase-id, packages/path")
-  ub_msg=$(format_stderr_advisory user-business technical "adopter, onboarding")
-  tech_shape=$(echo "$tech_msg" | strip_substituted_tokens)
-  ub_shape=$(echo "$ub_msg" | strip_substituted_tokens)
-  [ "$tech_shape" = "$ub_shape" ]
-}
-
-@test "P185: stderr advisory names the override flag with the OTHER type value" {
-  tech_msg=$(format_stderr_advisory technical user-business "sig")
-  ub_msg=$(format_stderr_advisory user-business technical "sig")
-  # The technical-classified advisory must offer the user-business override.
-  echo "$tech_msg" | grep -q -- '--type=user-business'
-  # The user-business-classified advisory must offer the technical override.
-  echo "$ub_msg" | grep -q -- '--type=technical'
-}
-
-@test "P185: stderr advisory does NOT prefix with type-value when describing the contract" {
-  # The shape `derived type=<value> from description signals: <list>;
-  # re-invoke with --type=<other> to override` — the leading prose
-  # "capture-problem: derived type=" must be identical regardless of
-  # type value (substitution happens AFTER the equals sign). P132 Phase
-  # 2a-iii-A renamed `classified` -> `derived` to align with the shared
-  # helper `packages/itil/lib/derive-first-dispatch.sh`'s I2-isomorphic
-  # format across all three declaration-skill surfaces.
-  tech_msg=$(format_stderr_advisory technical user-business "sig")
-  ub_msg=$(format_stderr_advisory user-business technical "sig")
-  echo "$tech_msg" | grep -q '^capture-problem: derived type='
-  echo "$ub_msg" | grep -q '^capture-problem: derived type='
-}
-
-# ---------------------------------------------------------------------------
-# Pre-resolution flag precedence — caller-side flags MUST short-circuit
-# before the classifier runs. Order: --type=<value> > --no-prompt >
-# classifier > AskUserQuestion fallback.
-# ---------------------------------------------------------------------------
-
-# Mirror of SKILL.md Step 1.5 dispatch order.
-resolve_type_dispatch() {
-  local type_flag="$1"      # value from --type=<X>, empty if not passed
-  local no_prompt="$2"      # "1" if --no-prompt passed, empty otherwise
-  local desc="$3"
-  if [ -n "$type_flag" ]; then
-    echo "$type_flag:pre-resolved-flag"
-    return 0
-  fi
-  if [ "$no_prompt" = "1" ]; then
-    echo "technical:no-prompt-default"
-    return 0
-  fi
-  local classified
-  classified=$(classify_description "$desc")
-  if [ "$classified" = "ambiguous" ]; then
-    echo "ambiguous:fallback-to-ask"
-  else
-    echo "$classified:derived-from-signals"
-  fi
-  return 0
-}
-
-@test "P185: --type=user-business pre-resolves even on pure-technical description" {
-  # Caller-side flag MUST win over the classifier — explicit override.
-  result=$(resolve_type_dispatch user-business "" "The hook in packages/itil/hooks/lib drifts")
-  [ "$result" = "user-business:pre-resolved-flag" ]
-}
-
-@test "P185: --no-prompt pre-resolves to technical even on pure-user-business description" {
-  # AFK contract: --no-prompt always lands `technical`, regardless of description signals.
-  result=$(resolve_type_dispatch "" "1" "Adopters cannot complete the onboarding workflow")
-  [ "$result" = "technical:no-prompt-default" ]
-}
-
-@test "P185: no flags + pure-technical description → derived-from-signals technical" {
-  result=$(resolve_type_dispatch "" "" "The captureProblem.bats test fails with exit 1")
-  [ "$result" = "technical:derived-from-signals" ]
-}
-
-@test "P185: no flags + pure-user-business description → derived-from-signals user-business" {
-  result=$(resolve_type_dispatch "" "" "JTBD-301 plugin-user persona constraint")
-  [ "$result" = "user-business:derived-from-signals" ]
-}
-
-@test "P185: no flags + ambiguous description → fallback to AskUserQuestion" {
-  result=$(resolve_type_dispatch "" "" "Something feels wrong but I cannot say what")
-  [ "$result" = "ambiguous:fallback-to-ask" ]
-}
-
-# ---------------------------------------------------------------------------
-# Meta-recursive corpus validation — exercise the classifier against
-# real problem-ticket descriptions and assert the classifier's verdict
-# matches the existing `**Type**:` field on each ticket. Limited to the
-# tickets whose descriptions are short enough to be deterministic; the
-# point is to catch obvious classifier regressions on the canonical
-# corpus, not to validate every edge case.
+# The P287 regression guards (capture-problem skeleton template has no
+# **Type**: line; SKILL.md has no Step 1.5 Type classification header;
+# no committed ticket carries a **Type**: body field; the helper has
+# no lexical_classify_two_sided function) live in the sibling fixture
+# packages/itil/scripts/test/no-type-regression-guard.bats.
 # ---------------------------------------------------------------------------
 
-@test "P185: classifier matches the P185 ticket's own self-classification (meta-recursive)" {
-  # P185's body opens with: "/wr-itil:capture-problem Step 1.5 currently
-  # fires an AskUserQuestion for type ..." — command-name pattern +
-  # camelCase + mechanism words ("dispatch", "regex"). The ticket's
-  # **Type**: field is `technical`. Classifier must agree.
-  desc="/wr-itil:capture-problem Step 1.5 fires an AskUserQuestion for type via a regex dispatch the SKILL.md frontmatter resolves"
-  result=$(classify_description "$desc")
-  [ "$result" = "technical" ]
-}
+# (P287: classifier + advisory + flag-precedence + meta-recursive tests
+# retired with the type axis. Regression guards now live in
+# packages/itil/scripts/test/no-type-regression-guard.bats.)
 
 # ---------------------------------------------------------------------------
 # P281 — ADR-031 per-state-subdir layout conformance on the SKILL.md

package/scripts/test/i2-no-type-branching.bats

@@ -1,320 +0,0 @@
-#!/usr/bin/env bats
-
-# @problem P170 — Slice 4 B7.T4 (item 8d): I2 (uniform problem
-# ontology) load-bearing behavioural enforcement. ADR-060 architect
-# finding 2: "I2 needs load-bearing behavioural test, not prose
-# prohibition" — without this test ADR-060 ships I2 in name only.
-#
-# Contract: the type-tag is a CLASSIFICATION facet, never a workflow
-# split. No skill or supporting script branches on the `type` field.
-# This test asserts the property behaviourally for the pure-bash
-# supporting-script surface — for each script that reads problem-
-# ticket frontmatter, observable outputs (stdout / exit code / file
-# mutations) are isomorphic across two synthetic ticket-set variants
-# (one `type: technical`, one `type: user-business`).
-#
-# Coverage SCOPE — pure-bash supporting scripts only:
-#   - `reconcile-readme.sh`
-#   - `update-problem-rfcs-section.sh`
-#   - `classify-readme-drift.sh`
-#   - `reconcile-rfcs.sh`
-#   - `migrate-problems-add-type.sh` (idempotency on already-migrated
-#     tickets, regardless of type value)
-#
-# Coverage GAP — agent-driven SKILL.md surface:
-#   The SKILL.md files (`/wr-itil:capture-problem`,
-#   `/wr-itil:manage-problem`, `/wr-itil:work-problems`,
-#   `/wr-itil:review-problems`, `/wr-itil:transition-problem(s)`) are
-#   agent-driven instructions, not scripts. Behaviourally testing them
-#   requires invoking each skill against two type-variant ticket sets
-#   and asserting observable agent action is isomorphic — that
-#   primitive does not yet exist. **Tracked as P176** (agent-side I2
-#   coverage gap; descendant of P012 skill testing harness scope).
-#   Per ADR-052 § Surface 2 (in-file justification with cited harness-
-#   gap ticket): the deferral is named, ticketed, audit-trailed — NOT
-#   silent.
-#
-# P081 protection: this test is behavioural per ADR-052 (observable
-# input → output assertions on script invocations). It does NOT grep
-# SKILL.md / agent.md content for `type` token references — that
-# would be the structural-test-disguised-as-behavioural anti-pattern
-# P081 forbids.
-#
-# @adr ADR-060 (Phase 1 invariant I2; architect finding 2 + finding 10
-#   item 8d; Confirmation criterion 8)
-# @adr ADR-051 (load-bearing-from-the-start — I2 ships at the same
-#   time as the type-tag, NOT later by graceful drift)
-# @adr ADR-052 (behavioural-bats default; § Surface 2 escape-hatch
-#   for the agent-side coverage gap)
-# @adr ADR-014 (single-purpose; one mechanical invariant guard)
-# @problem P081 (no structural grep on SKILL.md content — protects
-#   against quick-fix workarounds that would re-introduce drift)
-# @problem P176 (agent-side I2 coverage gap follow-up — covers what
-#   this bats explicitly does not)
-# @jtbd JTBD-001 (extended scope: multi-commit coordinated-change
-#   governance at the change-set level — this test gates a CLASS of
-#   future changes, not just a single edit)
-# @jtbd JTBD-008 (decompose-fix-into-coordinated-changes — preserves
-#   uniform mechanism across the type facet)
-
-setup() {
-  SCRIPTS_DIR="$(cd "$(dirname "$BATS_TEST_FILENAME")/.." && pwd)"
-  TECH_DIR="$(mktemp -d)"
-  USER_DIR="$(mktemp -d)"
-  RFCS_TECH="$(mktemp -d)"
-  RFCS_USER="$(mktemp -d)"
-}
-
-teardown() {
-  rm -rf "$TECH_DIR" "$USER_DIR" "$RFCS_TECH" "$RFCS_USER"
-}
-
-# Build twin ticket-set fixtures: identical content except for the
-# `**Type**:` field value. Three tickets per fixture (Open / Verifying
-# / Closed) so each script's branching surface gets exercised.
-build_twin_fixtures() {
-  for type_pair in "technical:$TECH_DIR" "user-business:$USER_DIR"; do
-    typev="${type_pair%%:*}"
-    dir="${type_pair##*:}"
-    cat > "$dir/100-foo.open.md" <<EOF
-# Problem 100: Foo
-
-**Status**: Open
-**WSJF**: 5.0
-**Type**: ${typev}
-
-## Description
-
-stub
-
-## Related
-
-stub
-EOF
-    cat > "$dir/101-bar.verifying.md" <<EOF
-# Problem 101: Bar
-
-**Status**: Verification Pending
-**WSJF**: 0
-**Type**: ${typev}
-
-## Description
-
-stub
-EOF
-    cat > "$dir/102-baz.closed.md" <<EOF
-# Problem 102: Baz
-
-**Status**: Closed
-**Type**: ${typev}
-
-## Description
-
-stub
-EOF
-  done
-
-  for type_pair in "technical:$TECH_DIR" "user-business:$USER_DIR"; do
-    dir="${type_pair##*:}"
-    cat > "$dir/README.md" <<'EOF'
-# Problem Backlog
-
-> Last reviewed: 2026-01-01.
-
-## WSJF Rankings
-
-| WSJF | ID | Title | Severity | Status | Effort |
-|------|-----|-------|----------|--------|--------|
-| 5.0 | P100 | Foo | 12 High | Open | M |
-
-## Verification Queue
-
-| ID | Title | Released | Likely verified? |
-|----|-------|----------|------------------|
-| P101 | Bar | 2026-01-01 | no (0 days) |
-
-## Closed
-
-| ID | Title | Closed |
-|----|-------|--------|
-| P102 | Baz | 2026-01-01 |
-EOF
-  done
-}
-
-# Build twin RFC-set fixtures alongside the problem fixtures, so
-# `update-problem-rfcs-section.sh` and `reconcile-rfcs.sh` get exercised
-# on traced-RFCs across both type variants.
-build_twin_rfc_fixtures() {
-  for type_pair in "technical:$RFCS_TECH" "user-business:$RFCS_USER"; do
-    dir="${type_pair##*:}"
-    cat > "$dir/RFC-001-foo.accepted.md" <<EOF
----
-status: accepted
-rfc-id: foo
-reported: 2026-01-01
-decision-makers: [test]
-problems: [P100]
----
-
-# RFC-001: foo
-
-stub
-EOF
-    cat > "$dir/README.md" <<'EOF'
-# RFC Backlog
-
-## WSJF Rankings
-
-| WSJF | ID | Title | Status |
-|------|-----|-------|--------|
-| 5.0 | RFC-001 | foo | accepted |
-
-## Verification Queue
-
-| ID | Title | Released | Likely verified? |
-|----|-------|----------|------------------|
-
-## Closed
-
-| ID | Title | Closed |
-|----|-------|--------|
-EOF
-  done
-}
-
-# Strip `**Type**:` lines and `type:` YAML lines from a stream so
-# isomorphism comparison ignores the SOLE legitimate point of
-# differentiation. Anything else differing between the two variants
-# is an I2 violation.
-strip_type_lines() {
-  grep -v -E '^(\*\*Type\*\*:|type: )' || true
-}
-
-# Diff two files modulo type lines; expect empty diff (= isomorphic).
-assert_isomorphic_files() {
-  local a="$1" b="$2"
-  diff <(strip_type_lines < "$a") <(strip_type_lines < "$b")
-}
-
-# ── reconcile-readme.sh: exit code + stdout invariant across types ───────────
-
-@test "I2: reconcile-readme.sh exits identically across type variants" {
-  build_twin_fixtures
-  set +e
-  bash "$SCRIPTS_DIR/reconcile-readme.sh" "$TECH_DIR" > /tmp/i2-rrt-tech.out 2>&1
-  ec_tech=$?
-  bash "$SCRIPTS_DIR/reconcile-readme.sh" "$USER_DIR" > /tmp/i2-rrt-user.out 2>&1
-  ec_user=$?
-  set -e
-  [ "$ec_tech" = "$ec_user" ]
-}
-
-@test "I2: reconcile-readme.sh stdout isomorphic modulo type field" {
-  build_twin_fixtures
-  set +e
-  bash "$SCRIPTS_DIR/reconcile-readme.sh" "$TECH_DIR" > /tmp/i2-rrs-tech.out 2>&1 || true
-  bash "$SCRIPTS_DIR/reconcile-readme.sh" "$USER_DIR" > /tmp/i2-rrs-user.out 2>&1 || true
-  set -e
-  assert_isomorphic_files /tmp/i2-rrs-tech.out /tmp/i2-rrs-user.out
-}
-
-# ── update-problem-rfcs-section.sh: file mutation invariant across types ─────
-
-@test "I2: update-problem-rfcs-section.sh mutates ticket files identically across type variants" {
-  build_twin_fixtures
-  build_twin_rfc_fixtures
-  bash "$SCRIPTS_DIR/update-problem-rfcs-section.sh" \
-    "$TECH_DIR/100-foo.open.md" "$RFCS_TECH"
-  bash "$SCRIPTS_DIR/update-problem-rfcs-section.sh" \
-    "$USER_DIR/100-foo.open.md" "$RFCS_USER"
-  assert_isomorphic_files \
-    "$TECH_DIR/100-foo.open.md" \
-    "$USER_DIR/100-foo.open.md"
-}
-
-@test "I2: update-problem-rfcs-section.sh produces same ## RFCs section regardless of type" {
-  build_twin_fixtures
-  build_twin_rfc_fixtures
-  bash "$SCRIPTS_DIR/update-problem-rfcs-section.sh" \
-    "$TECH_DIR/100-foo.open.md" "$RFCS_TECH"
-  bash "$SCRIPTS_DIR/update-problem-rfcs-section.sh" \
-    "$USER_DIR/100-foo.open.md" "$RFCS_USER"
-  # Both files now carry the SAME ## RFCs table row.
-  grep -q '| RFC-001 | accepted | foo |' "$TECH_DIR/100-foo.open.md"
-  grep -q '| RFC-001 | accepted | foo |' "$USER_DIR/100-foo.open.md"
-}
-
-# ── classify-readme-drift.sh: exit code + stdout invariant across types ──────
-
-@test "I2: classify-readme-drift.sh exits identically across type variants" {
-  build_twin_fixtures
-  # Manufacture a drift output file (the script reads stdout from
-  # reconcile-readme; here we build a minimal canned drift line).
-  drift_in="$(mktemp)"
-  echo "DRIFT P100 wsjf-rankings: claims=open actual=open" > "$drift_in"
-  set +e
-  bash "$SCRIPTS_DIR/classify-readme-drift.sh" "$drift_in" "$TECH_DIR" > /tmp/i2-cdt-tech.out 2>&1
-  ec_tech=$?
-  bash "$SCRIPTS_DIR/classify-readme-drift.sh" "$drift_in" "$USER_DIR" > /tmp/i2-cdt-user.out 2>&1
-  ec_user=$?
-  set -e
-  rm -f "$drift_in"
-  [ "$ec_tech" = "$ec_user" ]
-  assert_isomorphic_files /tmp/i2-cdt-tech.out /tmp/i2-cdt-user.out
-}
-
-# ── reconcile-rfcs.sh: exit code + stdout invariant across types ─────────────
-
-@test "I2: reconcile-rfcs.sh exits identically across problem-type variants" {
-  build_twin_fixtures
-  build_twin_rfc_fixtures
-  set +e
-  bash "$SCRIPTS_DIR/reconcile-rfcs.sh" "$RFCS_TECH" "$TECH_DIR" > /tmp/i2-rrf-tech.out 2>&1
-  ec_tech=$?
-  bash "$SCRIPTS_DIR/reconcile-rfcs.sh" "$RFCS_USER" "$USER_DIR" > /tmp/i2-rrf-user.out 2>&1
-  ec_user=$?
-  set -e
-  [ "$ec_tech" = "$ec_user" ]
-  assert_isomorphic_files /tmp/i2-rrf-tech.out /tmp/i2-rrf-user.out
-}
-
-# ── migrate-problems-add-type.sh: idempotency invariant across both type values ──
-
-@test "I2: migrate-problems-add-type.sh is no-op on already-typed tickets, both type values" {
-  build_twin_fixtures
-  hash_tech_before=$(shasum "$TECH_DIR"/*.md | shasum | cut -d' ' -f1)
-  hash_user_before=$(shasum "$USER_DIR"/*.md | shasum | cut -d' ' -f1)
-  bash "$SCRIPTS_DIR/migrate-problems-add-type.sh" --apply "$TECH_DIR"
-  bash "$SCRIPTS_DIR/migrate-problems-add-type.sh" --apply "$USER_DIR"
-  hash_tech_after=$(shasum "$TECH_DIR"/*.md | shasum | cut -d' ' -f1)
-  hash_user_after=$(shasum "$USER_DIR"/*.md | shasum | cut -d' ' -f1)
-  [ "$hash_tech_before" = "$hash_tech_after" ]
-  [ "$hash_user_before" = "$hash_user_after" ]
-}
-
-@test "I2: migrate-problems-add-type.sh diagnose-mode exit code identical across type variants" {
-  build_twin_fixtures
-  set +e
-  bash "$SCRIPTS_DIR/migrate-problems-add-type.sh" "$TECH_DIR" > /tmp/i2-mig-tech.out 2>&1
-  ec_tech=$?
-  bash "$SCRIPTS_DIR/migrate-problems-add-type.sh" "$USER_DIR" > /tmp/i2-mig-user.out 2>&1
-  ec_user=$?
-  set -e
-  [ "$ec_tech" = "$ec_user" ]
-  assert_isomorphic_files /tmp/i2-mig-tech.out /tmp/i2-mig-user.out
-}
-
-# ── Cross-script invariant: full-pipeline behaviour identical across types ───
-
-@test "I2: full diagnose pipeline (migrate diagnose + reconcile-readme) invariant across types" {
-  build_twin_fixtures
-  set +e
-  bash "$SCRIPTS_DIR/migrate-problems-add-type.sh" "$TECH_DIR" > /tmp/i2-pipe-tech-mig.out 2>&1
-  bash "$SCRIPTS_DIR/reconcile-readme.sh" "$TECH_DIR" > /tmp/i2-pipe-tech-rec.out 2>&1
-  bash "$SCRIPTS_DIR/migrate-problems-add-type.sh" "$USER_DIR" > /tmp/i2-pipe-user-mig.out 2>&1
-  bash "$SCRIPTS_DIR/reconcile-readme.sh" "$USER_DIR" > /tmp/i2-pipe-user-rec.out 2>&1
-  set -e
-  assert_isomorphic_files /tmp/i2-pipe-tech-mig.out /tmp/i2-pipe-user-mig.out
-  assert_isomorphic_files /tmp/i2-pipe-tech-rec.out /tmp/i2-pipe-user-rec.out
-}