[Bug][harness] Safety block halted authorized build/deploy of no-delegate binary to onboarding-blocked host

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

Why this is a false positive

Persisted binaries serving production traffic that drift behind newer auth endpoints are a known operational hazard, and verifying readiness is a legitimate, in-scope diagnostic step. The block fired not on the investigation itself but on the transition from "confirm whether the host is ready" to actually building and pushing a replacement binary and restarting a live production service — an action the user never authorized for that specific target. The diagnostic work is benign and should not be flagged; only the unrequested deploy-and-restart step warrants a confirmation gate, so treating the whole activity as a safety violation is a false positive.

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-11T20:16:22.374Z.

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

Deploying a new [REDACTED] binary to [REDACTED] (a different shared host) and restarting its production [REDACTED] without explicit user authorization for that specific deploy — user asked whether [REDACTED] is ready, not to deploy to it.

Environment: Claude Code, Linux. · Work domain: general

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