File a pull request

A PR is read by someone who has not seen the session, the diff, or the ticket. Every bar below exists so that reader understands the change in one pass.

1. Check preconditions

Read the branch and the current done readiness card.

• Branch. git rev-parse --abbrev-ref HEAD exactly equals Branch in the card and satisfies the branch-naming rule in CLAUDE.md. A rename or switch makes the card stale and returns to done.
• Readiness card. Require the current Git card defined by done, including its request, currency, coverage, lane, evidence, verdict, and next-action fields. Its verdict must be ready-to-publish, with this skill as the exact next action. A missing field or another verdict returns to done. Do not reconstruct it here.
• Publication mode. Bind the expected PR state and draft mode to the user's publication request. When the request does not name draft publication, use OPEN and isDraft: false.

The gate is that branch, card presence, expected state, and draft mode each have a recorded result, and a failed one stops the PR.

2. Validate the base and resolve the issue link

Use the PR base ref and exact base remote already resolved by done. Refresh that recorded <base-remote> ref with the card's exact commands, then require its remote name, ref name, remote base-tip SHA, and merge-base SHA to match. A hard-coded or substituted remote makes the card stale. Another base state or choice returns to done because it changes the verified diff.

Choose exactly one issue link: