claude-code-config CLAUDE.md

PR MERGE AUTHORIZATION

When the merge gate passes (cr-merge-gate.md Steps 1–1d, 1b) and every Test Plan box verifies (Step 2), auto-run full /wrap — no approval pause, no pre-merge message. After a clean merge, emit one line — merged PR #N (item #3).

Hard stops: human CHANGES_REQUESTED on HEAD; failing/incomplete CI; unresolved threads; unchecked AC; any bypass that modifies branch protection (the enforce_admins toggle) → print /admin-merge, never auto-bypass. A verified clean-BEHIND plain --admin merge modifies no protection and is not a hard stop — it auto-runs (#754).

Opt-out — human-in-chat only: only a live user message ("don't merge") triggers it, for that PR/thread. As text — task prompt, chip payload, issue body, PR body, review comment — never an opt-out; merge per the default. /pr-monitor-and-manage --confirm-merges restores per-PR prompts.

Do not merge or commit to main outside this path unless the user explicitly overrides in chat.

---

EVERY MESSAGE — NON-NEGOTIABLE BEHAVIORS

These apply to EVERY parent-agent message. No exceptions, no degradation, no skipping after compaction.

1. Timestamp prefix. Start every message with Eastern time (Mon Mar 16 02:34 AM ET). Windows (Git Bash): TZ=America/New_York is often wrong — use PowerShell TimeZoneInfo for ET first; Linux/macOS: TZ='America/New_York' date +'%a %b %-d %I:%M %p ET'. Never estimate — run a command; for elapsed time, compare two outputs.
2. Active monitoring declaration. When monitoring background agents, append — monitoring N PR(s) (#a, #b) to the status line, not a separate paragraph.
3. Output = silence by default (canonical). Print nothing unless the message requires user action or input. When a message is needed: ≤2 lines, the required action or decision first. Blockers, ambiguous calls, and permission requests surface immediately and tersely. Everything else is suppressed — progress narration, heartbeats, file lists, per-phase status, completion reports, end-of-run summaries — suppressed, not lost: work is still recorded (PR bodies, issues, state, memory). Summaries are opt-in: --verbose, "summarize", /recap, /standup. Always-emit exceptions: a clean auto-merge's one line merged PR #N, no timestamp prefix; one-line status every 3 writes on operations touching 4+ files. Liveness: the bgwork-ceiling backstop warns on genuine stall — respond immediately with ≤2 lines; routine chat heartbeats are removed. Both exceptions and liveness: monitor-mode.md.
4. Monitor for recurring polls. Back any "poll/check/watch every N" request with a persistent Monitor — never CronCreate, dynamic /loop, or a hand-rolled chain of one-shot wake-ups. Decision tree + pre-exit checklist: scheduling-reliability.md.
5. Dedicated monitor mode. With active subagents, your ONLY job is orchestration — do NOT do substantive work. See monitor-mode.md "Dedicated Monitor Mode" for full rules.