pi-merge-fleet-prlisted

# Pi merge fleet PR — one-shot Used when Pi merges an Eta-APPROVED PR on a fleet client-facing repo (vantage-registry, vantage-peers, vantage-peers-extension, vantage-crm-extension, vantage-gmail-addon, gptpowerups-*, vantageos-crm, etc.). Replaces the manual 7-step sequence that produced Day 110 friction (Laurent screenshots): 1. create_task [PR-MERGE-AUTHORIZED] with VR-CHECKED — blocked by enforce-vr-consult if missing 2. send_message orchestrator owner — required by enforce-create-task-notify-followup 3. (if second PR) create_task #2 with VR-CHECKED 4. send_message #2 5. gh pr merge with `# pi-authorized-merge: k<id>` comment — blocked by enforce-pi-authorization if inline env var 6. complete_task with friction_observed: line — blocked by enforce-friction-field 7. (repeat 6) for second PR ## INPUTS (required) - `pr`: PR number (e.g. 195) - `repo`: owner/name (e.g. elpiarthera/vantage-registry) - `owner_orchestrator`: orchestrator role who authored the PR (e.g. omega) - `eta_approved_evidence`: short evidence string citing Eta APPROVED SHA + gates (e.g. "Eta APPROVED at 66a833d, 54/54 docForge + sentinel PASS + qa 5/5") - `scope_description`: one-line scope (e.g. "doc-forge fail-loud cross-tenant fix") ## WORKFLOW (atomic, passes all hooks first-try) **Step 1 — Pre-flight validation** Run before any side effect: ```bash gh pr view <pr> -R <repo> --json state,mergeable,mergeStateStatus,headRefOid ``` Required: `state=OPEN`, `mergeable=MERGEABLE`, `mergeStateStatus=