fix(poteto-mode): correct failure counting and PR repository selection

PORTING.md

@@ -55,6 +55,9 @@ Upstream is the source of truth for the workflows themselves. This file records
 - The GitHub watcher keeps a GitHub Enterprise host (port addition, 2026-10). It reads the host from the origin remote or the PR URL, passes it to every `gh` call as `--repo <host>/<owner>/<repo>` and to GraphQL as `--hostname <host>`, and renders status links on it. An explicit `--owner`, `--repo`, and `--pr` outside a checkout uses `GH_HOST`, else github.com. Upstream assumes github.com. Keep the host through the watcher's context types on sync, and keep the Babysit playbook's `GH_HOST` sentence.
 - The GitHub watcher (`skills/poteto-mode/scripts/watch-pr`) treats every review bot alike, not only Cursor Bugbot: a thread carries `bot: { login, passes } | null`, and `READY` waits while a bot is still a requested reviewer (`WAITING` with `pending-review-bots`), which is how GitHub Copilot code review shows up before it posts. Since 2026-10, `READY` also stops on a bot review of the head commit whose body reports a finding with no thread (the `review-findings` blocker, exit 8), until a PR comment from the PR author or a repository owner, member, or collaborator contains that review's full URL. A per-format parser registry reads Copilot's overview. An unreadable body from Copilot's login blocks, and another bot's unreadable body becomes a note on `READY`. Repos without review bots see no change. Upstream still has `isBugbot`/`bugbotReviewPasses`; on sync, keep the port's shape and re-apply the babysit playbook and triage-reference wording.
 - Shipping lands GitHub PRs through `scripts/watch-pr/merge-gate` (port addition, 2026-10). The lead broke the prose landing gates three times in one week: once it merged before reading a bot's review body, once it missed red CI behind the watcher's first blocker, and once it reported CI it had not read. merge-gate reads the latest trusted verdict block (`Verdict:`, `Head:`, `Patch-id:`, `Docs:`) and recomputes the patch-id. It checks CI, bot review bodies, threads, and mergeability on the current head, reports every failed gate, and merges with `--match-head-commit`. It also refuses a base branch with a merge queue, because `gh pr merge` would only enqueue the PR, and the queue would land it later without rechecking the verdict, the bot reviews, or the open threads. `--override` posts its reason on the PR. On GitHub, Shipping never arms GitHub auto-merge, because it would merge later without these checks; the lead runs merge-gate when the watcher reports `READY`. Upstream lands with a bare `gh pr merge` or arms `--auto`, and has no verdict block. Autopilot-full step 5 also says the full-autonomy grant never approves `--override`, so an owner whose merge-gate run refuses on a merge queue stops at merge-ready and the root reports an open operator gate. Keep that sentence on sync.
+- Autopilot-full's third-`FAIL` stop and finding bar are port additions (2026-10, #177). [Autopilot-full step 4](skills/poteto-mode/playbooks/autopilot-full.md) owns the counting, reset, `Stopped:`, recorded-run, and security rules; step 6 applies the stop on each hourly tick. Upstream has none of these rules. Keep both steps and the `verdict.ts` and merge-gate support on sync. The security exception also covers Shipping step 1's posted verdict and Multi-phase plan's follow-up-issue rule (port edits). Keep that sentence at both sites on sync.
+- PR body finalization is a port edit (2026-10, #177). [Opening a PR](skills/poteto-mode/playbooks/opening-a-pr.md) owns PR body finalization, including non-owner reports. [Babysit](skills/poteto-mode/playbooks/babysit.md) applies them after a repair push. Upstream has neither the provisional-body rule nor the Babysit body re-check. Keep both on sync.
+- Repository selection is a port addition (2026-10, #169). [Opening a PR, Forge](skills/poteto-mode/playbooks/opening-a-pr.md) owns the origin-resolution rule. Keep it and the watcher's `currentPr` repository, branch, and detached-HEAD handling on sync. Port-owned examples carry explicit `-R`: Opening a PR's attachment read, Babysit steps 6 and 8, Orchestrate, Code review, and deslop. Babysit, Code review, and deslop resolve the repository without Opening a PR's Forge rule, so each of their `-R` sites says `<owner>/<repo>` comes from origin's fetch URL. Upstream-owned `gh pr` commands that read or change PR state also carry it (port edit): Shipping steps 4 and 8, why step 2, and why's code-archaeology reference. In this fork, Shipping's bare `gh pr view 205` read cursor/plugins#205 as merged while this repository's #205 was open, and why never loads Opening a PR. Keep `-R`, with `<owner>/<repo>` from origin's fetch URL, at those sites on sync. Other upstream-owned examples in Opening a PR, Autopilot-stack, and Multi-phase plan remain unchanged.
 - Two roles beyond upstream's roster: `trail reviewer` (the show-me-your-work reviewer and, since 2026-10, every independent verdict and review; upstream says "a different model family", which has no answer inside one vendor) and `default` (the entry for a spawn whose skill names no role, shipped as `inherit-parent`). Step 1 of the harness skill's Spawn a role sends every role-less spawn through `default`; on sync, keep both roles and the show-me-your-work wording that resolves through `trail reviewer`, and keep the resolver's `--work-model` step that moves it to another allowed model in the work model's family when it matches the working model, or marks it `same-model` when the config allows none in that family.
 - **Authoring or modifying a skill** sends skill steps through the STE layer of **technical-writing** (port addition, 2026-10). Skill steps are procedures an agent executes. ASD-STE100 was written for procedures. Upstream's authoring guidance names no style standard. On sync, keep the sentence.
 - **Opening a PR** says how to post PR evidence (port addition, 2026-09). Follow any attachment rule the repo's `AGENTS.md` or PR template sets, upload with `gh … --attach` (gh 2.99.0 or later), never through undocumented endpoints, and confirm each posted URL returns `200` with `gh auth token`. Report an upload blocker only when no gh at 2.99.0 or later is available or a retry fails. Upstream says only to attach videos or screenshots. Keep both the repo-rule clause and the **Attachments** paragraph on sync.

skills/deslop/SKILL.md

@@ -9,7 +9,7 @@ Clean AI slop out of the code a branch changed, and leave behavior unchanged. Us
 
 ## Scope
 
-Use the caller's files or diff. Otherwise diff against the branch this one builds on, including the working tree and untracked files (`git status --short`): the pull request's base when one is open (`gh pr view --json baseRefName`), else the branch it was cut from (`git branch -vv` or `git reflog show <branch>`), else `main`. On a stacked branch, `main` would pull the parent's commits into the diff. Edit only inside the hunks the branch added or changed. Read whatever the rules need to judge them: callers, types, existing helpers, and the rest of the file. Slop you notice elsewhere goes in the report and stays untouched.
+Use the caller's files or diff. Otherwise diff against the branch this one builds on, including the working tree and untracked files (`git status --short`): the pull request's base when one is open (`gh pr view <branch> -R <owner>/<repo> --json baseRefName`, with `<owner>/<repo>` from origin's fetch URL), else the branch it was cut from (`git branch -vv` or `git reflog show <branch>`), else `main`. On a stacked branch, `main` would pull the parent's commits into the diff. Edit only inside the hunks the branch added or changed. Read whatever the rules need to judge them: callers, types, existing helpers, and the rest of the file. Slop you notice elsewhere goes in the report and stays untouched.
 
 ## Process