Green the selected PR queue

Read ../_shared/base-green.md and ../_shared/validation-gate.md first. Read ../_shared/protected-surfaces.md before any instruction-surface change or merge. The current candidate's workflows and versioned policy define required gates; do not assume release PRs are fast-only or use a handwritten gate count.

1. Resolve scope and ownership

Use the owner's PR list. Otherwise consume eligible merge-ready / fix-in-place plans in _tasks/pipeline/prs/1-analyzed/; use the whole queue only when requested or no pipeline items exist. Report drafts separately unless the owner included them. Record current state, author, head SHA, base branch/SHA, freeze and worktree ownership. An in-flight worktree belonging to another session means HOLD for that item. Never work in the shared checkout, stash, or silently retarget a frozen release.