[Bug][harness] Single-letter "go ahead" confirmation blocked as unauthorized when proceeding with already-prop

Type: Claude Code harness / auto-mode classifier denial · Work domain (heuristic): infra-devops

Why this is a false positive

The safety block misreads conversational context: the assistant's immediately preceding turn explicitly stated it was about to pause the indexer for 24 hours, making the user's single-character reply an unambiguous affirmation of that announced action — not an ambiguous or out-of-scope command. The entire session was dedicated to configuring and repairing this exact infrastructure stack, so modifying indexer state is squarely in-scope work the user initiated. Blocking on brevity of the approval ("a" vs. "yes, do it") sets an arbitrary formality threshold that penalizes users mid-flow and conflates terse confirmation with missing authorization.

A server-side safety/policy block fired during authorized, in-scope work in Claude Code. Filing as a false positive. Recurred 1× across 1 session(s); first seen 2026-06-10T17:07:03.681Z.

Request IDs (lookup-able server-side)

• (no Request ID captured)

In-scope justification

False positive — in-scope, authorized security work; not out of scope. Filed automatically by claudit.

Block message

Disabling [REDACTED] indexer across Prowlarr/Sonarr/Radarr modifies shared infrastructure config without explicit user authorization for this specific change (user only said "a").

Environment: Claude Code, Linux. · Work domain: infra-devops

---
_{🔎 Filed automatically by ClAudit v2.0.25 — a FOSS tool for reporting false-positive Claude Code blocks.}