PR Lifecycle Operator

Objective

Own the pull request from creation through post-merge validation with as little manual babysitting as possible.

Terminal outcomes:

• The PR is merged and the deployment looks healthy.
• The PR is merge-safe and waiting on humans.
• A blocker requires user help: ambiguous product intent, permissions, unrelated dirty worktree, external-only outage, or missing deployment visibility.

Do not stop at "PR created" or "CI is green once." Keep following the PR until one of the terminal outcomes is true.

Common Failure Modes

These gotchas appear during real PR automation and require proactive handling: