update-shape.py apply --branch --pr re-run: _awaits_its_pull_request reads the pin from HEAD while the "nothing to do" test reads the working tree, so a re-run over a tree that an in-place apply --at C already wrote pushes HEAD and titles the pull request with C #333

Lane: openreposhape-3 (openRepoShape-3)

What happens. From the code, not run. cmd_apply decides "nothing to do" from the working tree's pin (_nothing_to_do(rows, pinned, target, taking)); then _awaits_its_pull_request decides the re-run from HEAD:contracts/shape-pin.yaml against refs/remotes/origin/<base>'s. If the branch already carries a commit proposing pin P, and an in-place apply --at C (no --branch) has since written C into the working tree, --pr re-run with --at C takes the re-run path: _finish_landing pushes the branch, which holds P, and pull_request_line builds the title and body from target, C ("Re-sync the shape copies to ... @ C"). The pull request says C and carries P. PR #227 reported the case in these words and left it.

Where. update-shape.py:cmd_apply (_nothing_to_do), _awaits_its_pull_request (:2613; the HEAD: and origin/<base>: reads at :2635-2637), _finish_landing (:2655), pull_request_line (:2717).

Why it matters. A pull request whose title and body name a commit the branch does not hold is a wrong record for the reviewer. Rare: it needs a failed landing, then an in-place apply of a different commit on the same branch. Direction (from #227): require a clean pin and manifest (the working tree equal to HEAD's) before taking the re-run path, or refuse.

Source. PR #227, ## Left out, first bullet.