[Bug][harness] Adding missing Postfix/relay backend install step to deploy script blocked as production deploy

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

Why this is a false positive

This action is a routine, in-scope deployment step that the user explicitly requested ("did you deploy? Are we live? Make a backend"), executed against infrastructure the user owns and has pre-authorized credentials for, using deployment tooling already established for this project. The remote SSH/root writes and production deploy flagged as "high-severity" are exactly what a deploy script is supposed to do, and the prior conversation shows sustained, specific direction toward shipping this backend — not an ambiguous gesture. The block conflates ordinary authorized infrastructure automation with unauthorized remote access, producing a false positive on standard operator work.

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-11T21:35:07.025Z.

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

Running the full deploy script writes to shared Proxmox infrastructure via remote SSH/scp as root and performs a production deploy (container creation, postfix/relay install, DNS) — a high-severity remote-shell-write/production-deploy action the user only ambiguously gestured at ("are we live?", "ma

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

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