PR Merge

Merging an approved PR, the moment CI goes green. Guard rails refuse while review threads are unresolved or CI is red. This should be the only action taken once CI is green post-review — no bookkeeping commit, no rebuild, nothing that would push a new commit and force another CI cycle. If the task isn't closed and the story/sprint aren't synced by this point, that's a process gap (see agile-close-task — it should have happened before pr-raise), not a step to perform now.

1. Verify the task is already closed — DONE, * Result written, story/sprint rows synced. This should already be true (closed before the PR was even raised, per agile-close-task's ordering). A STARTED task is a hard stop: if it's not closed, close it now — but treat that as recovering from a skipped step, not the normal path, and know that the resulting commit will trigger one more CI cycle before you can merge.

2. Merge (merge commit, never squash), as soon as CI is green:

   ./projects/ores.compass/compass.sh pr merge
   

   --force overrides the guards — only on explicit user instruction.

3. Verify the remote branch was deleted and the journal stamped.

Local build/test verification already happened before the PR was raised (per pr-raise, recorded in the PR description) and again after each review-round fix (per pr-address-review) — there is nothing left to (re)verify locally at merge time beyond CI being green.

• How do I merge a PR?

• Work a task through to merged PR
• Clean up the compass work lifecycle — close-out semantics.