Merge/push-to-main classifier blocks git push and gh pr merge even with full permissions.allow and Auto Mode configured

Summary

A hard, non-configurable safety classifier blocks git push/gh pr merge into a repository's main branch, even though:

1. Bash(git *) and Bash(gh *) are explicitly present in permissions.allow at both project and user level.
2. gh is authenticated with repo/workflow scopes.
3. The repository's main branch has no GitHub branch protection rule at all (confirmed via gh api repos/.../branches/main/protection → 403, feature unavailable on this plan).
4. The Auto Mode setup wizard was run and applied (environment + soft_deny keys written to ~/.claude/settings.json); its own output explicitly states no permissions.allow entry exists that could bypass this classifier ("no classifier-bypassing... entries reported").

Exact behavior observed

• gh pr merge <n> --merge → denied with reason [Merge Without Review].
• git push origin <branch>:main (direct push, no PR involved) → denied with the same [Merge Without Review] reason.
• Both denials come from what the tool calls "the Claude Code auto mode classifier" — a layer that appears to act independently of permissions.allow/permissions.deny and independently of Auto Mode's own configuration surface.

Regression context

This worked without any manual intervention for approximately 3 months of daily use on this same project/repo, and started blocking abruptly "the day before yesterday" — a sharp, dated behavior change, not a gradual one. This is consistent with a product-side rollout of a new safety classifier rather than any local configuration change (nothing in ~/.claude/settings.json, project .claude/settings.json, or GitHub branch protection changed on the user's end).

Impact

For a non-technical solo founder managing their own private project, this reintroduces a manual "click merge in the browser" step for every single change, which the user relied on Claude Code to eliminate. Both permissions.allow and Auto Mode fail to expose any way to authorize this for a fully-owned, unprotected repository. This is a significant regression compared to other AI coding tools (Cursor, Antigravity) that do not impose this restriction, and is causing the user to consider switching tools.

Request

Please expose a way (via Auto Mode config, permissions.allow, or a dedicated setting) for a user to explicitly authorize automated git push/gh pr merge to a branch they own and that has no GitHub-side protection — at least as an opt-in for trusted local/solo projects.

Environment

Claude Code desktop app, Windows, project on github.com (private repo, free GitHub plan, no branch protection configured).