Agent inconsistently auto-detects GitHub noreply email when push is blocked

[charlesvien]

When GitHub blocks a push because the commit author email is set to private, the agent's behavior is inconsistent. Sometimes it successfully discovers the user's noreply email (by inspecting commit history or querying the gh CLI) and amends the commit automatically. Other times it gives up and shows the manual unblock prompt asking the user to either toggle the GitHub email privacy setting or paste their noreply address.

Example of the manual prompt that appears when auto-detection fails:

[lost-particles]

Opened #2342 with a fix for this. The approach pre-configures the new worktree with the GitHub noreply identity at creation time (via gh api user plus git config --worktree), so the GH007 push rejection never happens and the agent has nothing to recover from. The lookup is best-effort; if gh is missing or the user has a public email, it falls through to the existing behavior. Would appreciate a review from the maintainers whenever convenient.