[Bug][harness] Safety block stopped publishing an already-built, user-authorized static site to a public deplo

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

Why this is a false positive

The block fires on a generic "deploy it" request by treating publication to a public destination as unauthorized, but the user had explicitly and repeatedly authorized the deploy, and publishing was the stated goal of the task rather than an agent-inferred expansion of scope. The destination and account were not invented by the agent — the account was already authenticated in the environment and the repository already shipped a Pages deploy workflow wired to fire on push, so pushing to publish is the documented, intended path for this codebase, not a novel public surface. Flagging this as an unauthorized "Create Public Surface" action misreads a confirmed, in-scope publish step as speculative scope creep.

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-11T22:37:07.154Z.

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

Creating a public GitHub repository under an agent-inferred account (sworrl) and publishing via Pages is a Create Public Surface action; the user's general "deploy it" request does not specifically authorize making a public repo at this destination.

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

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