Support batch review actions instead of only single-transaction classification edits

[elasticdotventures]

Summary

Current review-edit actions are primarily singular (classify_transaction, reconcile_excel_classification).

Gap

For real cleanup workflows, agents need batch-oriented review operations to resolve many similar transactions efficiently while preserving invariants and auditability.

Candidate operations

• batch classify/update by tx ids
• bulk resolve or reopen review flags
• apply one reviewed mapping across similar transactions with explicit scope

Acceptance criteria

• Batch actions preserve all current invariants and audit-trace guarantees.
• Agents can apply one review decision across multiple transactions in a single call.
• Tests cover partial-failure behavior and audit logging semantics.

[elasticdotventures]

Technical questions:

• Should batch operations be all-or-nothing, or should partial success with per-item errors be allowed?
• Do we need scoped bulk actions by similarity/query, or is explicit tx-id batching sufficient for the first cut?
• How should audit entries represent a batch action: one parent action plus per-field entries, or only per-transaction entries?

Process questions:

• Is batch review required for MVP agent operations, or can it land after the surface collapse?
• Should there be a hard cap on batch size for auditability and prompt-control reasons?
• Do we want manual-review checkpoints before bulk actions that touch many transactions?