@windyroad/itil 0.61.1 → 0.61.2

package/.claude-plugin/plugin.json

@@ -497,5 +497,5 @@
     }
   },
   "name": "wr-itil",
-  "version": "0.61.1"
+  "version": "0.61.2"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@windyroad/itil",
-  "version": "0.61.1",
+  "version": "0.61.2",
   "description": "ITIL-aligned IT service management for Claude Code (problem, and future incident/change skills)",
   "bin": {
     "windyroad-itil": "./bin/install.mjs"
@@ -27,6 +27,11 @@
     "scripts/",
     ".claude-plugin/",
     "lib/",
-    "!skills/*/eval/"
+    "!skills/*/eval/",
+    "!agents/test/",
+    "!hooks/test/",
+    "!lib/test/",
+    "!scripts/test/",
+    "!skills/*/test/"
   ]
 }

package/agents/test/fixtures/proceed-new-genuinely-new.md

@@ -1,43 +0,0 @@
-# Behavioural fixture 2: genuinely-new capture (PROCEED_NEW)
-
-Validates that the agent does NOT spuriously fold a genuinely-new capture into a candidate just because the mechanical pre-filter surfaced one.
-
-## Input 1: New capture description
-
-```
-The `claude plugin marketplace update` command silently caches plugin
-metadata for 24 hours without surfacing the cache state in any UI. Adopters
-attempting to refresh after a release wait 24h not knowing the cache is
-serving stale data. Need a manual cache-bust flag or a TTL surface in the
-marketplace command's output. Affects every adopter waiting on a release.
-Verifiable by: invoke `claude plugin marketplace update` immediately after a
-release; observe no version-bump surface; wait 24h; observe version bump.
-```
-
-## Input 2: Filtered candidate set
-
-| Candidate | Title | Path | Matching signals |
-|-----------|-------|------|------------------|
-| P106 | `claude plugin install` is a silent no-op when already installed at any version | `docs/problems/open/106-...md` | shared `claude plugin` command surface; both touch the install/marketplace cache layer |
-
-## Expected verdict
-
-```
-PROCEED_NEW
-
-**Rationale**: P106's root cause is the `claude plugin install` command being
-a no-op when already installed at any version (no version-equality check).
-The new capture's root cause is a different surface: `claude plugin
-marketplace update`'s opaque 24-hour metadata cache. The two share the
-upstream "claude plugin marketplace cache layer" but operate at different
-commands with different observable symptoms and different fix loci. Folding
-the new capture into P106 would dilute P106's single-purpose anchor.
-
-**Per-candidate explanation**:
-- P106 (claude plugin install silent no-op) — different command (`install` vs
-  `marketplace update`); different observable (no version bump on already-
-  installed plugin vs no version bump because metadata cache is stale);
-  different fix locus (per-project install logic vs marketplace metadata
-  TTL/surfacing). Surface signals overlap (both touch the marketplace cache
-  layer) but the captured friction is genuinely distinct.
-```

package/agents/test/fixtures/proceed-new-subtle-sibling.md

@@ -1,47 +0,0 @@
-# Behavioural fixture 3: subtle sibling-vs-parent (PROCEED_NEW with reasoned rationale)
-
-Validates that the agent reasons cleanly about sibling-vs-parent shape — two tickets sharing surface signals where neither is the other's parent.
-
-## Input 1: New capture description
-
-```
-`/wr-itil:report-upstream` SKILL.md surface — the report-upstream skill's
-generated GitHub issue body sometimes carries our internal P<NNN> ticket IDs
-verbatim instead of stripping them. Adopters reporting upstream see opaque
-references they can't resolve. Should redact internal IDs before posting or
-include a "for our records" footer separating internal vs upstream
-references. Affects every outbound issue from /wr-itil:report-upstream.
-```
-
-## Input 2: Filtered candidate set
-
-| Candidate | Title | Path | Matching signals |
-|-----------|-------|------|------------------|
-| P070 | `/wr-itil:report-upstream` doesn't deduplicate against existing upstream issues | `docs/problems/verifying/070-...md` | shared `/wr-itil:report-upstream` SKILL reference; both about outbound surfaces on the same SKILL |
-
-## Expected verdict
-
-```
-PROCEED_NEW
-
-**Rationale**: P070's root cause is the report-upstream SKILL not checking
-the upstream repo for an existing issue before posting (deduplication gap).
-The new capture's root cause is the report-upstream SKILL leaking
-maintainer-internal P<NNN> references in the generated issue body (privacy /
-adopter-confusion gap). The two are siblings — both surface on
-`/wr-itil:report-upstream`'s outbound generation flow — but neither is the
-other's parent. The shared SKILL surface is coincidental; the fix loci are
-distinct (upstream-repo-state lookup vs body-text scrubbing). P070's scope
-does not name internal-ID-leakage as deferred follow-up. Recommend
-PROCEED_NEW; let `/wr-itil:review-problems` cluster them as sibling-class at
-the next cluster pass if a common parent emerges.
-
-**Per-candidate explanation**:
-- P070 (report-upstream deduplication gap) — same SKILL surface, but
-  different observable (duplicate upstream issues vs leaked internal IDs in
-  the body), different fix locus (gh API state lookup vs string scrubbing on
-  the body template), different lifecycle stage (P070 is Verifying with a
-  shipping fix; the new capture is fresh discovery on a different code
-  surface in the same file). Folding would dilute P070's single-purpose
-  anchor and force its Verifying transition to wait on un-related work.
-```

package/agents/test/fixtures/regression-p347-vs-p346.md

@@ -1,54 +0,0 @@
-# Behavioural fixture 1 (canonical regression): P347-vs-P346
-
-This is the canonical regression case for the `wr-itil:hang-off-check` agent. It captures the 2026-05-31 P347 wrongly-captured-sibling-of-P346 incident. If the agent receives this fixture's inputs and returns anything other than `HANG_OFF: P346`, the SKILL is insufficient and the regression has re-opened.
-
-Behavioural execution lands under RFC-012 (promptfoo eval harness, proposed). Until RFC-012 ships, this fixture is the documentation of the expected behaviour; the bats fixtures at `../hang-off-check.bats` are structural assertions on the agent's prose contract per ADR-052 Surface 2 carve-out.
-
-## Input 1: New capture description
-
-```
-P346 + ADR-079 Phase 2 — empirical foreground relevance-scan today (5 batches,
-14 closes) revealed 4 evidence shapes Phase 1 doesn't implement, plus the
-1 shape Phase 1 does implement had the highest false-positive rate. The four
-shapes: ADR-shipped-with-`human-oversight: confirmed`, named-skill-or-feature-
-exists, self-marker-in-body (P289-class), driver-child-ticket-closed (P155 →
-P014). Phase 1 false-positive fixes needed for state-suffix, sibling-file, and
-rename detection (via `git log --follow`). Behavioural bats extension from 18
-to 33 fixtures. `evaluate-relevance.sh` extension. Update
-`/wr-itil:review-problems` SKILL.md Step 4.6 + `/wr-itil:manage-problem`
-lifecycle table.
-```
-
-## Input 2: Filtered candidate set
-
-| Candidate | Title | Path | Matching signals |
-|-----------|-------|------|------------------|
-| P346 | `/wr-itil:review-problems` has no path to close tickets that are no longer relevant (evidence-based, NOT age-based) — structural outflow gap drives monotonic backlog growth | `docs/problems/open/346-...md` | shared ADR-079 ref; shared `packages/itil/scripts/evaluate-relevance.sh` path; shared `/wr-itil:review-problems` SKILL ref; shared `/wr-itil:manage-problem` SKILL ref; candidate's `## Multi-phase scope` section explicitly names Phase 2 as in-scope |
-
-## Expected verdict
-
-```
-HANG_OFF: P346
-
-**Rationale**: P346 is the master ticket for the framework's backlog-flow-control
-mechanisms with an explicit Multi-phase scope section. The new capture's
-description IS Phase 2 of P346 (additional evidence shapes + Phase 1
-false-positive fixes for the `evaluate-relevance.sh` script that P346 Phase 1
-introduced). P346's body already names Phase 2 work as in-scope.
-
-**Signals matched**: shared ADR-079 reference; shared
-`packages/itil/scripts/evaluate-relevance.sh` file path; shared
-`/wr-itil:review-problems` SKILL reference; shared `/wr-itil:manage-problem`
-SKILL reference; candidate's `## Multi-phase scope` section explicitly names
-Phase 2 as in-scope.
-
-**Where to absorb**: amend P346's Investigation Tasks checklist with the 4
-new evidence shapes + Phase 1 false-positive fix items; add a `### Phase 2 —
-evidence shape expansion + Phase 1 false-positive fixes` section under the
-existing Multi-phase scope section; the shipped commits' attribution
-references this absorption.
-```
-
-## Why this fixture is canonical
-
-The wrongly-captured P347 sibling of P346 on 2026-05-31 motivated the entire Phase 3 deliverable (this agent's existence). If a future change to the agent's prose contract regresses the verdict on this fixture, the SKILL no longer fulfils its driver. This is the binary tripwire.

package/agents/test/hang-off-check.bats

@@ -1,225 +0,0 @@
-#!/usr/bin/env bats
-# Doc-lint guard: wr-itil:hang-off-check agent contract — the agent MUST
-# carry the verdict format (HANG_OFF: P<NNN> | PROCEED_NEW), the
-# fresh-context subagent rationale, the JTBD-301 maintainer-side firewall,
-# the AFK safe-default (PROCEED_NEW on ambiguous), the rationale-citation
-# requirement, and the three canonical fixture files. Closes P346 Phase 3
-# deliverable — the SKILL's behavioural intent is documented and
-# verifiable.
-#
-# Structural assertion — ADR-052 Surface 2 (structural-justified) +
-# P176 harness gap. Behavioural execution of the three canonical fixtures
-# lands under RFC-012 (promptfoo eval harness, proposed). Upgrade these
-# to behavioural fixtures when RFC-012 ships.
-#
-# Cross-reference:
-#   P346 (review-problems backlog-flow-control master ticket; Phase 3
-#         deliverable this agent fulfils)
-#   P347 (closed as duplicate-of-P346; canonical regression case driving
-#         fixture 1)
-#   P176 (agent-side I2 / harness gap — Surface 2 carve-out precedent)
-#   ADR-032 (5th invocation pattern — fresh-context-subagent-as-decision-
-#            arbiter; P346 amendment 2026-05-31 codifies this agent's shape)
-#   ADR-052 (behavioural-tests default; Surface 2 carve-out)
-#   ADR-075 (promptfoo as agent-prose verdict harness — future home)
-#   RFC-012 (promptfoo retrofit — behavioural eval harness)
-#   RFC-013 (P346 multi-phase trace per ADR-071)
-#   @jtbd JTBD-001 (enforce governance without slowing down)
-#   @jtbd JTBD-006 (progress backlog while I'm away — AFK safe-default)
-#   @jtbd JTBD-101 (extend suite with new plugins — pattern reuse)
-#   @jtbd JTBD-201 (restore service fast with an audit trail — rationale)
-
-setup() {
-  AGENT_DIR="$(cd "$(dirname "$BATS_TEST_FILENAME")/.." && pwd)"
-  AGENT_FILE="${AGENT_DIR}/hang-off-check.md"
-  FIXTURES_DIR="${AGENT_DIR}/test/fixtures"
-}
-
-# ----- Contract surface: verdict format + structure -----
-
-@test "agent.md exists at packages/itil/agents/hang-off-check.md" {
-  [ -f "$AGENT_FILE" ]
-}
-
-@test "agent.md frontmatter declares name: hang-off-check" {
-  run grep -nE "^name: hang-off-check$" "$AGENT_FILE"
-  [ "$status" -eq 0 ]
-}
-
-@test "agent.md frontmatter limits tools to read-only set (Read, Glob, Grep)" {
-  # No Edit, no Write, no Bash — read-only reviewer per ADR-032 5th pattern
-  run grep -nE "tools:" "$AGENT_FILE"
-  [ "$status" -eq 0 ]
-  run grep -nE "^  - (Read|Glob|Grep)$" "$AGENT_FILE"
-  [ "$status" -eq 0 ]
-  # Forbid Edit / Write / Bash in the tools list
-  ! grep -nE "^  - (Edit|Write|Bash|MultiEdit|NotebookEdit)$" "$AGENT_FILE"
-}
-
-@test "agent.md declares HANG_OFF: P<NNN> verdict shape" {
-  run grep -nE 'HANG_OFF:\s*P<NNN>' "$AGENT_FILE"
-  [ "$status" -eq 0 ]
-}
-
-@test "agent.md declares PROCEED_NEW verdict shape" {
-  run grep -nE "PROCEED_NEW" "$AGENT_FILE"
-  [ "$status" -eq 0 ]
-}
-
-@test "agent.md requires a Rationale section on every verdict" {
-  run grep -nE "\*\*Rationale\*\*" "$AGENT_FILE"
-  [ "$status" -eq 0 ]
-}
-
-@test "agent.md requires Signals matched citation on HANG_OFF (rationale-grounding per ADR-026)" {
-  run grep -nE "\*\*Signals matched\*\*" "$AGENT_FILE"
-  [ "$status" -eq 0 ]
-}
-
-@test "agent.md requires Where to absorb directive on HANG_OFF (calling-skill action contract)" {
-  run grep -nE "\*\*Where to absorb\*\*" "$AGENT_FILE"
-  [ "$status" -eq 0 ]
-}
-
-@test "agent.md requires Per-candidate explanation on PROCEED_NEW" {
-  run grep -nE "\*\*Per-candidate explanation\*\*" "$AGENT_FILE"
-  [ "$status" -eq 0 ]
-}
-
-# ----- Driver / context-isolation rationale -----
-
-@test "agent.md cites the fresh-context / session-context-bias driver" {
-  run grep -niE "(session-context bias|fresh context|context isolation)" "$AGENT_FILE"
-  [ "$status" -eq 0 ]
-}
-
-@test "agent.md cites the P347-vs-P346 canonical regression in the driver section" {
-  run grep -nE "P347" "$AGENT_FILE"
-  [ "$status" -eq 0 ]
-  run grep -nE "P346" "$AGENT_FILE"
-  [ "$status" -eq 0 ]
-}
-
-@test "agent.md cites ADR-032 5th-pattern codification (P346 amendment)" {
-  run grep -nE "ADR-032" "$AGENT_FILE"
-  [ "$status" -eq 0 ]
-  run grep -niE "5th (invocation )?pattern" "$AGENT_FILE"
-  [ "$status" -eq 0 ]
-}
-
-# ----- Decision rule -----
-
-@test "agent.md names master-ticket / multi-phase as a HANG_OFF signal" {
-  run grep -niE "(master ticket|multi-phase|scope expansion)" "$AGENT_FILE"
-  [ "$status" -eq 0 ]
-}
-
-@test "agent.md names false-negative-cheaper-than-false-positive safe-default" {
-  run grep -niE "false[-]positive.*cheap|cheap.*false[-]positive" "$AGENT_FILE"
-  [ "$status" -eq 0 ]
-}
-
-@test "agent.md cites Rule 6 fail-safe / AFK safe-default (ambiguous → PROCEED_NEW)" {
-  run grep -niE "(ambiguous.*PROCEED_NEW|--no-prompt|AFK propagation)" "$AGENT_FILE"
-  [ "$status" -eq 0 ]
-  run grep -nE "ADR-013" "$AGENT_FILE"
-  [ "$status" -eq 0 ]
-}
-
-@test "agent.md explicitly forbids AskUserQuestion invocation (Rule 6)" {
-  run grep -niE "(never|do not|MUST NOT).*(AskUserQuestion|invoke.*AskUserQuestion)" "$AGENT_FILE"
-  [ "$status" -eq 0 ]
-}
-
-# ----- Scope / firewalls -----
-
-@test "agent.md names the JTBD-301 maintainer-side firewall" {
-  run grep -nE "JTBD-301" "$AGENT_FILE"
-  [ "$status" -eq 0 ]
-  run grep -niE "maintainer-side|maintainer-internal" "$AGENT_FILE"
-  [ "$status" -eq 0 ]
-}
-
-@test "agent.md excludes plugin-user-side intake from the dispatch (firewall)" {
-  run grep -niE "plugin-user-side|problem-report\.yml" "$AGENT_FILE"
-  [ "$status" -eq 0 ]
-}
-
-@test "agent.md excludes manage-problem ingestion-of-plugin-user-reports path" {
-  run grep -niE "ingestion[- ]of[- ]plugin[- ]user[- ]reports" "$AGENT_FILE"
-  [ "$status" -eq 0 ]
-}
-
-@test "agent.md scopes cardinality to one verdict per invocation" {
-  run grep -niE "one verdict per invocation|cardinality" "$AGENT_FILE"
-  [ "$status" -eq 0 ]
-}
-
-# ----- Output formatting (matches architect / jtbd output formatting convention) -----
-
-@test "agent.md carries Output Formatting section requiring human-readable IDs" {
-  run grep -nE "## Output Formatting" "$AGENT_FILE"
-  [ "$status" -eq 0 ]
-}
-
-# ----- JTBD annotation (per JTBD review nit 5) -----
-
-@test "agent.md carries @jtbd annotation citing JTBD-001/006/101/201" {
-  run grep -nE "^# @jtbd .*JTBD-001.*JTBD-006.*JTBD-101.*JTBD-201" "$AGENT_FILE"
-  [ "$status" -eq 0 ]
-}
-
-# ----- Canonical behavioural fixtures (RFC-012 future-home) -----
-
-@test "fixture 1 (canonical P347-vs-P346 regression) exists" {
-  [ -f "${FIXTURES_DIR}/regression-p347-vs-p346.md" ]
-}
-
-@test "fixture 1 names HANG_OFF: P346 as the expected verdict" {
-  run grep -nE "HANG_OFF: P346" "${FIXTURES_DIR}/regression-p347-vs-p346.md"
-  [ "$status" -eq 0 ]
-}
-
-@test "fixture 1 cites P347 as the wrongly-captured-sibling motivator" {
-  run grep -nE "P347" "${FIXTURES_DIR}/regression-p347-vs-p346.md"
-  [ "$status" -eq 0 ]
-}
-
-@test "fixture 2 (genuinely-new) exists" {
-  [ -f "${FIXTURES_DIR}/proceed-new-genuinely-new.md" ]
-}
-
-@test "fixture 2 names PROCEED_NEW as the expected verdict" {
-  run grep -nE "PROCEED_NEW" "${FIXTURES_DIR}/proceed-new-genuinely-new.md"
-  [ "$status" -eq 0 ]
-}
-
-@test "fixture 3 (subtle sibling-vs-parent) exists" {
-  [ -f "${FIXTURES_DIR}/proceed-new-subtle-sibling.md" ]
-}
-
-@test "fixture 3 names PROCEED_NEW with reasoned per-candidate rationale" {
-  run grep -nE "PROCEED_NEW" "${FIXTURES_DIR}/proceed-new-subtle-sibling.md"
-  [ "$status" -eq 0 ]
-  run grep -niE "Per-candidate explanation" "${FIXTURES_DIR}/proceed-new-subtle-sibling.md"
-  [ "$status" -eq 0 ]
-}
-
-# ----- RFC-012 forward-reference -----
-
-@test "agent.md cross-references RFC-012 as future behavioural-eval home" {
-  run grep -nE "RFC-012" "$AGENT_FILE"
-  [ "$status" -eq 0 ]
-}
-
-# ----- Cross-references to dispatch sites -----
-
-@test "agent.md cross-references /wr-itil:capture-problem as primary dispatch site" {
-  run grep -nE "/wr-itil:capture-problem" "$AGENT_FILE"
-  [ "$status" -eq 0 ]
-}
-
-@test "agent.md cross-references /wr-itil:manage-problem as secondary dispatch site" {
-  run grep -nE "/wr-itil:manage-problem" "$AGENT_FILE"
-  [ "$status" -eq 0 ]
-}

package/hooks/test/block-list.bats

@@ -1,153 +0,0 @@
-#!/usr/bin/env bats
-
-# P123: packages/itil/hooks/lib/block-list.sh shared helper for the
-# inbound-report block-list mechanism. Per ADR-046 §v1 implementation
-# contract — audit-log-only — the helper exposes four functions:
-#   is_blocked(<reporter-id-hash>)
-#   add_block(<reporter-id-hash> <evidence-ticket-P###> <provenance>)
-#   remove_block(<reporter-id-hash> <reason>)
-#   list_blocks()
-#
-# Per ADR-046 §Decision Outcome §Identifier, the entry shape is the
-# SHA-256 hash of the GitHub numeric user ID. Per architect verdict
-# (this iter), the helper does NOT compute the hash — caller supplies
-# an opaque hex string; helper validates hex shape only. This keeps
-# the helper GitHub-agnostic so non-GitHub channel adoption (out-of-
-# scope per ADR-046 §Reassessment) wouldn't require helper changes.
-#
-# Audit log: sibling JSONL file `docs/blocked-reporters.audit.jsonl`.
-# Append-only; one JSON object per line per the five-field shape
-# adopted in ADR-046 Q2: {type, reporter_id_hash, evidence_ticket,
-# timestamp, author}.
-#
-# Per feedback_behavioural_tests.md (P081) — behavioural assertions on
-# observable outcomes (file state, exit codes, helper-emitted output).
-# No source-grep on helper text. Per ADR-005 (plugin testing strategy)
-# + ADR-037 (skill testing strategy) hook bats live under
-# packages/itil/hooks/test/ and assert behaviour, not implementation.
-
-setup() {
-  SCRIPT_DIR="$(cd "$(dirname "$BATS_TEST_FILENAME")/.." && pwd)"
-  HELPER="$SCRIPT_DIR/lib/block-list.sh"
-  ORIG_DIR="$PWD"
-  TEST_DIR=$(mktemp -d)
-  cd "$TEST_DIR"
-  mkdir -p docs
-  # Mirror the per-repo on-disk shape ADR-046 names.
-  echo "[]" > docs/blocked-reporters.json
-  # Source the helper. Functions become callable in this shell.
-  # shellcheck source=/dev/null
-  source "$HELPER"
-}
-
-teardown() {
-  cd "$ORIG_DIR"
-  rm -rf "$TEST_DIR"
-}
-
-# Canonical fixture hash — 64 hex chars (SHA-256 width). Real callers
-# would compute this from a GitHub numeric user ID; the helper does
-# not care about provenance, only that the input is hex-shaped.
-HASH_A="aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
-HASH_B="bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb"
-
-# --- Round-trip: add_block then is_blocked ---
-
-@test "add_block + is_blocked round-trip: hash present after add" {
-  add_block "$HASH_A" "P123" "test@example.com"
-  run is_blocked "$HASH_A"
-  [ "$status" -eq 0 ]
-}
-
-@test "is_blocked: returns non-zero for hash never added" {
-  run is_blocked "$HASH_B"
-  [ "$status" -ne 0 ]
-}
-
-# --- list_blocks output shape ---
-
-@test "list_blocks: prints each blocked hash on its own line" {
-  add_block "$HASH_A" "P123" "test@example.com"
-  add_block "$HASH_B" "P124" "test@example.com"
-  run list_blocks
-  [ "$status" -eq 0 ]
-  [[ "$output" == *"$HASH_A"* ]]
-  [[ "$output" == *"$HASH_B"* ]]
-  # Two distinct hashes — output should have at least two non-empty lines.
-  line_count=$(printf '%s\n' "$output" | grep -c .)
-  [ "$line_count" -ge 2 ]
-}
-
-@test "list_blocks: empty list on empty docs/blocked-reporters.json" {
-  run list_blocks
-  [ "$status" -eq 0 ]
-  # No hash strings; either empty output or whitespace only.
-  [[ "$output" != *"$HASH_A"* ]]
-  [[ "$output" != *"$HASH_B"* ]]
-}
-
-# --- Idempotent add ---
-
-@test "add_block: adding the same hash twice is idempotent (one entry)" {
-  add_block "$HASH_A" "P123" "test@example.com"
-  add_block "$HASH_A" "P123" "test@example.com"
-  run list_blocks
-  [ "$status" -eq 0 ]
-  occurrences=$(printf '%s\n' "$output" | grep -c "$HASH_A")
-  [ "$occurrences" -eq 1 ]
-}
-
-# --- remove_block path ---
-
-@test "remove_block: hash absent from is_blocked after remove" {
-  add_block "$HASH_A" "P123" "test@example.com"
-  remove_block "$HASH_A" "wrongly-classified"
-  run is_blocked "$HASH_A"
-  [ "$status" -ne 0 ]
-}
-
-# --- Audit log presence (ADR-046 Q2 five-field shape) ---
-
-@test "add_block: appends entry to docs/blocked-reporters.audit.jsonl" {
-  add_block "$HASH_A" "P123" "test@example.com"
-  [ -f docs/blocked-reporters.audit.jsonl ]
-  run cat docs/blocked-reporters.audit.jsonl
-  [[ "$output" == *"\"type\""* ]]
-  [[ "$output" == *"\"block\""* ]]
-  [[ "$output" == *"$HASH_A"* ]]
-  [[ "$output" == *"P123"* ]]
-  [[ "$output" == *"test@example.com"* ]]
-  # Five-field shape names: type, reporter_id_hash, evidence_ticket,
-  # timestamp, author. Assert each label is present.
-  [[ "$output" == *"reporter_id_hash"* ]]
-  [[ "$output" == *"evidence_ticket"* ]]
-  [[ "$output" == *"timestamp"* ]]
-  [[ "$output" == *"author"* ]]
-}
-
-@test "remove_block: appends an unblock entry to the audit log" {
-  add_block "$HASH_A" "P123" "test@example.com"
-  remove_block "$HASH_A" "wrongly-classified"
-  run cat docs/blocked-reporters.audit.jsonl
-  [[ "$output" == *"\"unblock\""* ]]
-  # The reason field rides under evidence_ticket per the five-field shape
-  # (audit log is type-tagged; the reason slot reuses evidence_ticket
-  # for unblock provenance per the helper's contract).
-  [[ "$output" == *"wrongly-classified"* ]]
-}
-
-# --- Hashed-ID handling: helper validates hex shape ---
-
-@test "add_block: rejects non-hex input (non-zero exit, no entry written)" {
-  run add_block "not-a-hash" "P123" "test@example.com"
-  [ "$status" -ne 0 ]
-  # State unchanged.
-  run is_blocked "not-a-hash"
-  [ "$status" -ne 0 ]
-}
-
-@test "add_block: rejects wrong-length hex (non-SHA-256-width input)" {
-  # 32 hex chars (half of SHA-256 width) — wrong length.
-  run add_block "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa" "P123" "test@example.com"
-  [ "$status" -ne 0 ]
-}