[Frontend][Review] Keep post-revision truth refresh retryable on failed or stalled reads

[Chris0Jeky]

Context

PR #2448 adds a post-revision truth barrier before Approve or Apply. Independent review found two related failure-path gaps below the merge-blocking bar. Refs #2215 and PR #2448.

Current behavior

• The explicit proposal-list read and six core selector reads have no caller-owned deadline. A transport that never settles can leave the decision rail locked with no retry path.
• The selector batch uses Promise.allSettled and reports settled even when core evidence calls fail. The first action can therefore clear the post-save barrier while the Review surface shows empty fallback evidence.
• No hidden mutation occurs. The first action is still consumed, and backend approval gates remain authoritative.

Acceptance

• Bound the explicit post-revision proposal and selector reads with one caller-owned cancellation/deadline contract.
• Distinguish a fully landed exact-key selector batch from failed, timed-out, aborted, or superseded outcomes.
• On any non-landed outcome, retain the per-proposal barrier, unlock the rail, show truthful retry guidance, and ignore late completions.
• Clear the barrier only after the exact proposal DTO and all required core evidence reads land for the same identity, status, expiry, defer state, and effective revision.
• Prove stalled transport, partial and total selector failure, retry success, late-response suppression, and no approve or execute request before the successful second explicit action.

Out of scope

Do not redesign ordinary background selector degradation outside the post-revision decision barrier.

[Chris0Jeky]

[Claude lane claim v2]
lane: alpha-product-trust (session taskdeck-alpha-85, Taskdeck-Alpha checkout)
issue: #2460
base: 61e94f6
residual acceptance: the explicit post-revision proposal read and the six core selector reads share one caller-owned cancellation/deadline contract; a fully landed exact-key selector batch is distinguished from failed, timed-out, aborted or superseded outcomes; on any non-landed outcome the per-proposal barrier is retained, the rail unlocks, truthful retry guidance is shown and late completions are ignored; the barrier clears only when the exact DTO and all required core reads land for the same identity, status, expiry, defer state and effective revision; specs prove stalled transport, partial and total selector failure, retry success, late-response suppression, and no approve/execute request before the successful second explicit action
owned paths/modules: frontend/taskdeck-web/src/composables/useReviewProposals.ts; frontend/taskdeck-web/src/composables/usePaperReviewSelectors.ts; their focused specs; PaperReviewView.vue and PaperReviewView.spec.ts ONLY after PR #2541 lands (a9 holds them until then)
shared-path leases: PaperReviewView.vue, PaperReviewView.spec.ts, useProposalDisplayNames.ts and ReviewProposalCard.vue stay leased to PR #2541 (a9); this slice does not touch them
parallel-safe work: worktree codex-2305 (Inbox poll family) is disjoint
open PRs/branches/review threads checked: PR #2448 merged (post-revision truth barrier, origin of #2460/#2461), PR #2456 merged, PR #2516 merged 13:00Z (origin of #2524), PR #2528 merged (retry unavailable evidence), PR #2541 open and held by a9 (touches PaperReviewView.vue and ReviewProposalCard.vue, not these files); #2460, #2461 and #2524 are serialized in this one worktree, in the order #2524, #2461, #2460
human or decision gates: none; starts only after PR #2541 lands if PaperReviewView.vue must change
status: active