Add safe push workflow for PR review workers

[PureWeen]

Problem

PR review workers were pushing to the wrong remote (e.g., pushing to origin/PureWeen when the PR comes from a fork like vitek-karas), and using --force-with-lease after rebasing unnecessarily.

Root Cause (verified by testing)

Workers were using manual checkout:

git fetch origin pull/<N>/head:pr-<N>
git checkout pr-<N>

This creates a branch with no tracking info (Remote: NONE, Merge: NONE). When the worker then runs git push or git push origin, git defaults to origin (PureWeen/PolyPilot) — even if the PR came from a fork.

In contrast, gh pr checkout <N> correctly sets up tracking:

• Same-repo PR Add scheduled prompt timers, per-session notification opt-in, and "still running" reminders #247: Remote: origin, Merge: refs/heads/copilot/build-notification-and-timers ✅
• Fork PR Add configurable repo/worktree storage root with re-clone flow #280: Remote: vitek-karas, Merge: refs/heads/Add-a-way-to-specify-polypilot-clone-root-7299 ✅

The second problem was git rebase origin/main + --force-with-lease, which requires force pushing. Using git merge origin/main adds a merge commit instead — no force push needed.

Changes

push-to-pr.sh

A shell script that:

1. Reads PR metadata via gh pr view to find the correct owner and branch
2. Maps the owner to the correct git remote
3. Pushes to that remote without --force
4. Verifies the push landed by comparing local and remote HEADs
5. Refuses to push if current branch doesn't match the PR branch (guards against wrong-branch pushes)

.squad/routing.md

Updated Fix Process replacing rebase+force-push with merge+safe-push, with clear explanation of why gh pr checkout is required.

.squad/decisions.md

Explicit shared rules:

• Never force push
• Always use gh pr checkout (not manual fetch)
• Always merge (not rebase)
• Always verify push target before pushing
• Use push-to-pr.sh for all PR pushes

.squad/team.md

Team definition file (required for squad directory to be recognized by PolyPilot's squad discovery).

[PureWeen]

Fixes applied (review findings)

Four issues from the multi-model review have been addressed in commit d5338f7:

Fix 1 — Contradictory push verification order (5/5 models)

outing.md\ step 6 previously said push first, verify on failure — directly contradicting \decisions.md\ rule 4 which mandates verifying before pushing. Step 6 now runs the \gh pr view + git config remote\ verification checks before \git push.

Fix 2 — Undefined <owner-remote>\ in fallback path (5/5 models)
The fallback \git push HEAD:\ had no definition of <owner-remote>. Now documented: \gh pr checkout\ registers the fork owner's GitHub login as the named remote. Fallback path now uses concrete \gh pr view\ + \git remote -v\ discovery commands with proper variable substitution.

Fix 3 — Worktree conflict recovery (4/5 models)
Added a recovery note to step 1: when \gh pr checkout\ fails with ''already checked out at...'', workers can use \git worktree list/remove\ or \gh pr checkout -b pr--fix\ to use a unique local branch name.

Fix 4 — Missing \push-to-pr.sh\ (4/5 models)
Created .squad/push-to-pr.sh\ — the script described in the PR description. It validates current branch matches the PR branch, discovers the correct remote via \gh pr view, pushes, and verifies via SHA comparison.