prlisted

Create a PR to hand off completed work for human review and merge. ## Pre-checks Before creating a PR, confirm ALL of the following: 1. A self-review report exists in `docs/reports/` with no CRITICAL findings. 2. A verify report exists in `docs/reports/` with pass or partial-pass verdict. 3. A test report exists in `docs/reports/` with pass verdict. **If tests failed, do NOT create the PR.** 4. Raw evidence is saved in `docs/evidence/`. 5. Branch name passes `./scripts/branch-name.sh validate "$(git branch --show-current)"`. 6. You are NOT on main or master. 7. `gh` CLI is available (if not, provide manual commands instead). 8. If `.harness/state/standard-pipeline/active-plan.json` exists, it includes `worktree_path`, `branch`, and `worktree_state_id` for post-PR cleanup. If any pre-check fails, stop and explain what is missing. ## Steps 1. **Resolve pinned plan identity** (standard flow): Read `.harness/state/standard-pipeline/active-plan.json` to obtain the exact plan path and task worktree metadata persisted by `/work`. Use this path for archival in Step 6 instead of rescanning `docs/plans/active/`. If the file is absent (e.g. legacy session), fall back to the single file under `docs/plans/active/` or ask the user which plan to archive. 2. Check for uncommitted changes with `git status --porcelain`. - **If uncommitted changes exist**: Stage with `git add` (prefer specific files over `-A`) and create a conventional commit: `<type>: <description>`. If a GitHub is