Refine the Batch Set Status confirmation modal

[lastobelus]

Outcome

Make the Batch Set Status confirmation modal easier to scan and understand without changing the review-resolution lifecycle introduced in #178 / PR #180.

Observed problem

Human QA confirmed the menu-driven batch-selection flow, checkbox mode, count gating, and completion behavior. The confirmation modal is functionally workable but its visual hierarchy and presentation need a dedicated design pass rather than more styling folded into the lifecycle PR.

Design questions

• Make the selected review count and chosen outcome immediately legible.
• Distinguish ordinary no-note or accepted-unreviewed confirmation from the destructive Abandon feedback path.
• Present one or many review summaries without overwhelming the modal.
• Improve the hierarchy among document identity, context summary, feedback blocks, attachments, and source-edit proposals.
• Keep Cancel and the completing action unambiguous, with useful keyboard and focus behavior.
• Check compact and expanded content across supported window sizes and light/dark palettes.

Boundaries

• Preserve the resolution outcomes, feedback-preservation behavior, exact-count confirmation, and two-phase abandonment semantics delivered by Add explicit review resolution, pending queries, and sidebar filters #178.
• Do not change portable review metadata, lifecycle transitions, pending queries, sidebar filters, or batch-selection entry behavior.
• Reuse the existing modal and interaction path unless the design evaluation demonstrates a smaller, clearer structure.

Done when

• The modal has an intentional visual hierarchy for single and batch completion, both with and without feedback.
• Abandon feedback remains explicit and visually distinct after the complete preserved summary is available.
• Keyboard/focus behavior and accessible names remain correct.
• Focused UI/accessibility tests and one macOS QA pass cover the supported modal variants.

Follow-up to #178 and PR #180.