create-pull-request: allow disabling branch name sanitization (lowercase + salt suffix)

[tore-unumed]

Problem

create-pull-request safe output normalizes branch names in two ways:

1. Lowercases the entire branch name (bugfix/BR-329-red → bugfix/br-329-red)
2. Appends a random salt suffix (bugfix/br-329-red → bugfix/br-329-red-cde2a954af3b8fa8)

This causes problems when the target repository enforces branch naming conventions via CI. For example, our repos require Jira keys in uppercase:

bugfix/BR-329-red

The agent correctly creates bugfix/BR-329-red, but by the time the PR is opened, the branch is bugfix/br-329-red-cde2a954af3b8fa8, which fails CI.

Evidence

From safe_outputs job logs:

Branch name sanitized: "bugfix/BR-329-red" -> "bugfix/br-329-red"
Using branch name from JSONL with added salt: bugfix/br-329-red-cde2a954af3b8fa8
Generated branch name: bugfix/br-329-red-cde2a954af3b8fa8

Request

Add a frontmatter option to create-pull-request to preserve the agent-specified branch name as-is:

safe-outputs:
  create-pull-request:
    preserve-branch-name: true  # skip lowercase + salt

Or at minimum, two separate controls:

• normalize-case: false — preserve original casing
• salt-suffix: false — don't append random hash

Workaround

We currently instruct the agent not to push branches and rely entirely on the safe output's patch-based flow, accepting the normalized names. But CI branch checks fail.

Version

gh-aw v0.58.0