Spec §E "Re-anchoring" trigger #2: re-opening `crit --pr 123` after the PR
head moved should re-anchor existing comments. The in-SetFocus reanchor
branch only fires for range→range transitions; on boot the prior focus is
FocusWorkingTree, so the branch is skipped and stored comments retain their
old HeadSHA — invisible to visibleInFocus and flagged Stale.

Adds Session.ReanchorOnBoot(focus) — walks the on-disk review file for
comments whose HeadSHA differs from the new focus's HeadSHA, runs
reanchorComments per unique old SHA, persists, reloads in-memory state, and
emits the same `reanchor` SSE event as the SetFocus path.

applySessionOverrides invokes it after SetFocus (and only on success — a
failed SetFocus already leaves working-tree state intact and reports via
stderr; reanchoring after a failure would mutate disk based on a focus
that's not actually adopted).

Test: TestReanchorOnBoot constructs a real two-commit fixture where target
content moves from line 2 to line 4, seeds a comment at oldHead/line 2,
then SetFocus(newHead) + ReanchorOnBoot(focus) and asserts the comment is
re-anchored to line 4 with HeadSHA updated and Stale=false.
TestReanchorOnBoot_NoOp covers the working-tree and empty-comment paths.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…pe test

Bundle of low-risk improvements flagged by the independent review:

Popover keyboard + a11y
- Add `role="listbox"` to the focus-picker list and `role="option"` +
  `aria-selected` + `tabindex="-1"` to each item, matching the listbox
  pattern the popover already implies via aria-haspopup.
- Add Escape handler that closes the popover and returns focus to the
  trigger button — same pattern as the commit-picker.

Stable test attributes
- `data-label` on each picker item (lifts the label out of rendered DOM
  children, replacing brittle `evaluate(() => innerText)` reads in
  focus-picker spec).
- `data-focus-kind` on each item, replacing the substring-match selector
  `[data-focus-payload*="working_tree"]` which would false-positive on any
  payload that happened to contain that string.

Brittle test fixes
- comment-stale spec: replace `stackOrdered[1]` with a feat-b-relative
  lookup so fixture growth doesn't silently shift the test.

Net new coverage
- scope-toggle-files: new test asserts a layer-scoped comment is hidden
  in full-stack and reappears when the user flips back. This is the
  lossless-visibility invariant — the only regression test against
  accidentally serialising scope-filtered comments out to disk.

Skipped from the polish list (with reasons):
- Branches-section base_sha precompute (#2) — server-side change, owned
  by go-expert; would be a separate ticket.
- Pre-feature comment WT-only test (#6) and /api/focus error-rollback
  toast test (#7) — both require fixture or daemon-state changes that
  exceed the 30-min budget for "polish".

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>