Give Open Findings on a Peer-Merged Feature PR an Outcome in drive-pr #3697

On a feature pull request a peer merged mid-drive, .agents/skills/drive-pr/SKILL.md step 3 sends the driver to step 4's post-merge path, with state= deciding over the exit code. That pull request can still carry unresolved threads (listed under unresolved= while the exit is 0) or step 2's introduced findings in its body. Nothing then gives them an outcome under "Disposing of Every Finding" before cleanup deletes the branch.

Done when the skill says open findings on a peer-merged feature pull request still get an outcome, normally outcome 4 (a filed issue) or a fresh fix pass on develop, before or alongside cleanup.