This gate went through six revisions and five of them were wrong for some git
configuration: a wrong proxy for a clean tree, two wrong ranges, a range dropped
from one arm, `@{u}` where no upstream exists, and local refs where the local
branch was itself ahead of the remote. No reviewer ever found the intent
unclear. Every finding was the prescribed mechanism failing somewhere, which
means prescribing the mechanism was what generated them — and `ce-commit-push-pr`
already owns git mechanics, so re-deriving them here duplicated another skill's
job badly.
The gate now states what must be true — clean pre-fix tree, nothing on the
branch the user has not already offered, a remote `gh` can open a PR against —
and leaves how to establish it to the agent and the repo in front of it. What
stays is the knowledge that cannot be derived: the push covers the whole branch
and precedes PR creation, an open PR means offered while a bare push does not,
a local ref can be ahead of the remote, and branch creation carries WIP forward.
Failing to establish it falls to the local route.
Pins move from the commands to those facts, since the commands were the part
that kept being wrong.
Claude-Session: https://claude.ai/code/session_015eproCfjCz2WZdynWFwGiT
Trevin Chow
8fc94ea260