Open a repair pull request

Pull request requirements

Confirm approval, repository mapping, and patch preparation.

• The proposal is approved, and its fingerprint still matches the approved artifact.
• The integration has an active repository mapping.
• The GitHub App installation has Contents and Pull requests set to Read and write; Seamward reports github_pull_request_permission_required until it does.
• The exact multi-file patch set was generated and reviewed before approval; source inspection does not write to GitHub.

Review the patch

Inspect the exact change before delivery.

Inspect every file diff, the base branch, observed commit, and service path before approval. Stop when any patch targets an unexpected file or location. The approval record binds the complete patch-set fingerprint to the validated candidate.

Create the draft

Open a reviewable branch and draft pull request.

Review and edit the pull request title and Markdown description, choose Draft or Open, then click Create pull request. Seamward creates one review branch named seamward/repair-<proposal id> containing every approved file change. Delivery is idempotent: retrying finds the existing pull request. If the review branch has moved since the patch was prepared, delivery stops with github_branch_conflict rather than overwriting anything.

Delivery boundary

Seamward does not merge or deploy the pull request.

Draft is the default, but an authorised reviewer can create the pull request as Open. Repository protections, CI, review, merge, and deployment remain controlled by your repository and release process; Seamward never merges or deploys.