[Frontend][Inbox] batchTriage refreshes the list unscoped and replaces a board-scoped Legacy inbox's rows (from PR #2567 review)

[Chris0Jeky]

Found while reviewing PR #2567 (#2301/#2303/#2304/#2305) and confirmed by the fresh-context reviewer; pre-existing, not introduced or touched by that PR.

Defect. captureStore.batchTriage (frontend/taskdeck-web/src/store/captureStore.ts, the await fetchItems() after the batch POST, ~line 838 at PR #2567's head) refreshes the list unscoped, while the caller's inbox may be board-scoped (useInboxOrchestrator.ts ~363-366 always passes boardId when one is active). A Legacy batch action on a board-scoped inbox therefore replaces the visible rows with the unscoped list.

Window. For action === 'triage' the bounded poll starts immediately with the correctly scoped query and its first tick (3 s) applies the scoped snapshot, so the wrong rows show for at most one tick. For ignore / cancel no poll starts, so the unscoped rows persist until the next scoped load.

Acceptance.

• the post-batch refresh uses the caller's current list scope (board and archived-history) or the orchestrator supplies it;
• a spec proves a board-scoped Legacy inbox keeps board-scoped rows after ignore / cancel and after triage;
• no change to the authoritative POST result, bounded polling, or Paper (which does not expose batchAction).

Refs #2305, PR #2567.

[Chris0Jeky]

[Claude lane claim v2]
lane: alpha-product-trust (session taskdeck-alpha-85, Taskdeck-Alpha checkout)
issue: #2570
base: origin/main at claim time (495da25, after #2584, #2590, #2593 and #2597 landed)
residual acceptance: all three bullets of the issue, verified live at the base: captureStore.batchTriage (src/store/captureStore.ts ~861) still calls fetchItems() with no query after the batch POST, while useInboxOrchestrator.batchAction (src/composables/useInboxOrchestrator.ts ~119-142) passes boardId only to the bounded triage poll, and loadInboxInternal (~352-375) is the only caller that supplies the scoped query. Slice: batchTriage takes the caller's current list query (board scope; archived history is already excluded because batchAction returns early on isArchivedHistory) and the orchestrator supplies it, so the post-batch refresh is scoped; a spec proves a board-scoped Legacy inbox keeps board-scoped rows after ignore and cancel (no poll) and after triage (before the first poll tick); the authoritative POST result, the bounded polling, refreshTerminalDetails and Paper (no batchAction) are unchanged. fetchItems now returns the applied boolean (#2584); the refresh keeps ignoring that value because a superseded post-batch read is not an error.
owned paths/modules: frontend/taskdeck-web/src/store/captureStore.ts (batchTriage signature and the post-batch read only); src/composables/useInboxOrchestrator.ts (batchAction only); src/tests/store/captureStore*.spec.ts and src/tests/composables/useInboxOrchestrator.spec.ts (new cases); src/views/InboxView.vue only if its batch call site needs the new argument
shared-path leases: PR #2584 (captureStore.ts, useInboxOrchestrator.ts) merged 44d50c9, so both files are free; no open PR touches them (checked gh pr list at claim time)
parallel-safe work: worktree codex-2007 (shortcut seam) is disjoint; #2571 (same files, poll-truth residuals) is NOT started until this PR merges, one writer per path
open PRs/branches/review threads checked: PR #2567 merged (origin of the finding), PR #2584 merged; #2571 open and unclaimed, deferred behind this PR
human or decision gates: none
status: active (worktree codex-2570-batch-triage-scope, to be created)