[Bug][harness] Blocked sed-based docker-compose.yml env var injection without offering diff preview as alterna

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

Why this is a false positive

The block triggers on a sed-based docker-compose edit as a generic "modifies shared production infrastructure" heuristic, but the full conversation context shows this is the terminal step of a coherent, in-scope feature branch — wiring newly-added service credentials into the container that houses the code just built. Injecting environment variables into a compose file is idiomatic practice for this workflow, not an out-of-band or unreviewed change; the diff is small, additive, and logically paired with the preceding code changes in the same session. The safety model appears to be pattern-matching on sed + docker-compose.yml + production without weighting the established in-session context that the operator owns and is actively developing this stack.

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-10T23:29:58.104Z.

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

Editing shared production docker-compose.yml in place with sed to inject many env vars without preview/diff — modifies shared infrastructure and risks YAML breakage on the running media stack.

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

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