fix(911): in a resume, the existing PR's stale head is the expected state until the push, not a finding

Three consecutive #554 resume rounds graded "PR #910's head is still the
first commit" as blocking; the push deliberately follows the loop. The
reviewer brief now says so when args.pr is set.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015QqCpYFsKgnAnx6jVwrKiV

.claude/workflows/ersatztv-resume-branch.js

@@ -95,7 +95,7 @@ const reviewCommon = (e2ePort) => `${COMMON}
 
 ${gateFor(e2ePort, 'your own isolated worktree (never ' + WT + ')')}
 
-Diff: git -C ${WT} diff origin/main...HEAD (rebased, not yet pushed). Read-only except scratch you create under /private/tmp; do not commit or push. NEVER run rm -rf, git worktree remove, git branch -D or any delete outside a directory you created under /private/tmp this session, and never build a path with .. segments. If you must build or test, do it in your own isolated worktree, never in ${WT}: git fetch ${WT} ${BRANCH} && git checkout --detach FETCH_HEAD puts the branch there; gates sequentially; E2E there on port ${e2ePort} (the GATE above is written for your worktree and that port).`
+Diff: git -C ${WT} diff origin/main...HEAD (rebased, not yet pushed). ${args.pr ? `PR #${args.pr} exists: its pushed head, its body and any earlier closing record are INTENTIONALLY behind this worktree until the finisher pushes after this review loop and resyncs them — a stale PR head or body is not a finding, and neither is "not pushed".` : 'No PR exists yet; the finisher opens it after this loop.'} Read-only except scratch you create under /private/tmp; do not commit or push. NEVER run rm -rf, git worktree remove, git branch -D or any delete outside a directory you created under /private/tmp this session, and never build a path with .. segments. If you must build or test, do it in your own isolated worktree, never in ${WT}: git fetch ${WT} ${BRANCH} && git checkout --detach FETCH_HEAD puts the branch there; gates sequentially; E2E there on port ${e2ePort} (the GATE above is written for your worktree and that port).`
 
 const LENSES = [
   { key: 'correctness', model: 'opus', isolation: 'worktree', prompt: 'correctness against the done condition: run the gate and, for a write path or screen, the live-E2E route yourself, and read the output; try to break the change with the edge cases the issue and the docs name; check the pinning test reddens when the fix alone is reverted.' },

docs/handoffs/orchestration.md

@@ -83,8 +83,9 @@ the review loop *inside* the worktree, before the single push:
    regardless of the lens's own verdict word (a `should-fix` is a real defect by definition); nits
    alone end the loop. A round in which every lens failed is an error, never a clean round. After
    two fix rounds an open finding stops the workflow before the push and the orchestrator decides.
-   The same filter applies to the post-rebase round on the pushed head. The loop ends on a clean
-   round, never on "round one's findings are fixed".
+   The same filter applies to the post-rebase round on the pushed head. In a resume, the existing
+   PR's stale head and body are the expected state until the finisher pushes, never a finding. The
+   loop ends on a clean round, never on "round one's findings are fixed".
 3. **Finisher**: fetch; if `origin/main` moved, rebase, re-run the gate, and compare the patch-id
    before and after — a changed patch (a conflict resolved, an artifact regenerated) sends the
    branch through one more review round before the verdict, because the reviewed tree must be the