[Frontend][A11y][Review] Queue live-region residuals from PR #2593 review: re-announce on explicit reload, focus after the unavailable-pin return control

[Chris0Jeky]

Non-blocking residuals from the fresh-context review of PR #2593 (#2214 Legacy unavailable-pin state and loading-announcement gate), tracked here rather than fix-cycled. References are at that PR's round-1 head 14a86d3.

1. LOW, re-announcement on explicit reload. The loading gate withholds the live region's content rather than comparing values, so every explicit loadProposals writes count, empty, count, and the restore is a text addition the AT speaks even when the number is unchanged. Reachable via the header Refresh and the dismiss path (filing away a terminal proposal leaves pending-review identical): the user gets the info toast plus a repeat of the same count. Benign (a true figure after a user-initiated read). A value-comparison gate (announce only when the count changes, and never while loading or revoked) would remove the repeat.

2. LOW, focus after the return control. Activating the Legacy target-unavailable panel's return-to-queue control removes the element it lives in and nothing moves focus to the queue or empty state that replaces it, so focus drops to body. Paper's unavailable branch (PaperReviewView.vue ~2576-2583) has the same gap, while Paper's settled-elsewhere notice deliberately moves focus via settledElsewhereReturnRef. Fix in both skins together (Core-loop correctness: false-green expiry regression test + #678 dismiss gap + #680 provenance 404 noise #1124 / ADR-0038).

3. Pending wiring, not a defect. PaperReviewView.vue does not yet pass the rail's announcement-suppression prop; that one-attribute wiring (plus the revoked case) lands once PR fix(review): bound the post-revision truth refresh and keep it retryable #2576 releases the file; Review queue refresh residuals: deep-link re-auth, poll restart after recovery, stale indicator (from PR #2208) #2214 carries it.

Refs #2214, #2194, PR #2593.

[Chris0Jeky]

[Claude lane claim v2]
lane: alpha-product-trust (session taskdeck-alpha-85, Taskdeck-Alpha checkout)
issue: #2599 items 1 and 2
base: origin/main at claim time (5487c26 or later; PR #2710 merged, releasing the Review queue files)
residual acceptance: the two residuals from PR #2593's review, one PR on both skins (#1124 / ADR-0038): (1) no repeat announcement on an explicit reload that did not change the queue: today the loading gate withholds the live region's content rather than comparing values, so every explicit loadProposals (header Refresh, the dismiss path) writes count, empty, count and the restore is spoken even when nothing changed; with #2710's identity key already announcing a changed queue once, the fix is to stop unmounting the announcement node during a reload of the SAME scope, replacing the "!proposalsLoading" term in both gates (LegacyReviewView ~234-236, ReviewQueueRail ~146 via the loading prop) with "no read has landed for the current board scope yet" from a load-scope signal the composable exposes, so a board-filter change (where the count on screen stops being real) and a failed entry load still withhold, a byte-identical reload speaks nothing, a changed reload speaks once, and the #2593 skeleton and revoked gates stand; (2) focus after the unavailable-pin return control: activating the target-unavailable panel's return-to-queue control removes the element focus is in and nothing moves focus, so it drops to body in both skins (LegacyReviewView ~443-447; PaperReviewView's unavailable branch), while Paper's settled-elsewhere notice already moves focus through settledElsewhereReturnRef; move focus to the queue heading or the first queue row (or the empty state) that replaces the panel, the same target in both skins, with a spec each. Specs, red-first: composable specs for the load-scope signal (explicit same-scope reload keeps it settled; board-filter change resets it; failed entry load leaves it unsettled); view and rail specs asserting the announcement node is the same element across a same-scope reload, a different element after a changed reload, withheld across a filter change and under the skeleton; focus specs for the return control in both skins. Item 3 of the issue is already shipped (#2593 wired the rail props) and is not touched.
owned paths/modules: frontend/taskdeck-web/src/composables/useReviewProposals.ts (the load-scope signal only); src/views/LegacyReviewView.vue; src/views/paper/PaperReviewView.vue (the rail prop and the unavailable branch focus); src/views/paper/review/ReviewQueueRail.vue (the gate and the prop); specs: src/tests/composables/useReviewProposals.spec.ts, src/tests/views/ReviewView.spec.ts, src/tests/views/paper/review/PaperReviewView.spec.ts, src/tests/views/paper/review/ReviewQueueRail.spec.ts. NOT owned: the review locales (no copy change), usePaperReviewSelectors.ts and the rail cards, the receipt recorders, the diff pane, the sticky seam (D-15), src/api/**
shared-path leases: none; PR #2710 merged 5487c26 and no open PR touches these files (checked gh pr list files at claim time)
parallel-safe work: #2636's PR #2709 (AppShell) is disjoint
open PRs/branches/review threads checked: both claim forms on #2599 (none; filed from PR #2593's review on 2026-09-04); PRs #2593, #2630, #2694, #2702, #2710 merged
human or decision gates: none
status: active (worktree codex-2599-queue-region, being created)

[Chris0Jeky]

Residual recorded from PR #2712's review (pre-existing, not fixed there): Paper's focus fallback after the unavailable-pin return control can still land on body when the rail is filtered to zero rows while a decision receipt holds the main column, because emptyColRef is bound to the no-active-proposal arm and activeProposal's receipt branch resolves against the unfiltered list. Path: approve P, filter the rail to an empty set, follow a dead #proposal link, press Return: the receipt promotes P, the empty column unmounts, the rail has no rows, focusFirstQueueRow() returns false and the empty ref is null. A third fallback to the main column closes it; Legacy's mirror gap needs a concurrent explicit load (the skeleton branch outranks both targets). One view each plus a spec.

[Chris0Jeky]

[Claude lane park v2]
lane: alpha-product-trust (session taskdeck-alpha-85, ending 2026-09-05 ~21:50Z)
issue: #2599 items 1 and 2
PR: #2712 open, ready for review, head 80631e2 (round 1 SHIP; round-2 comment-and-spec commit pushed; CI in progress)
remaining: CI green at 80631e2 plus the three-minute age, then a merge commit; the release note is drafted (the focus fallback residual recorded above stays open)
claim: released to the ready PR; the worktree is removed and the branch is on origin