git-followuplisted

# Git followup Ship a small self-review edit on the current PR branch in one pass. When invoked with `reply-owned`, a caller such as `review-address` posts its own reply, so skip the comment in step 7. The push and body sync still run. ## Guards - If `git branch --show-current` returns `main`, stop: `❌ On main. Switch to a PR branch first.` - If `git status --porcelain` is empty, stop: `❌ No changes to ship.` - If `gh pr view --json state -q '.state' 2>/dev/null` is not `OPEN`, stop: `❌ No open PR for this branch. Use git-ship to open one.` A missing tracking ref is no longer a guard. An open pull request proves the branch reached the remote, and a branch created by worktree entry has been measured carrying an open pull request with no tracking ref, where the old guard reported that the branch still needed pushing. That message describes a state the branch is not in, so the run stopped on a diagnosis nobody could act on. Step 4 sets the ref instead. ## Sequence 1. Run `git status` to confirm the changes are intentional 2. Run `git add -A` to stage every change 3. Invoke `canon:git-commit` to generate one conventional commit from the staged diff 4. Push, in one of two cases. - When `git rev-parse --abbrev-ref --symbolic-full-name @{u} 2>/dev/null` is empty, the branch has an open pull request and no tracking ref, so run `git push -u origin HEAD` to send the commit and set the ref in one step. - Otherwise push to the tracking branch with `git push`, and when `git m