Add a unified work queue for flags, ambiguities, blockers, and recent manual changes

[elasticdotventures]

Summary

The system has multiple review-oriented concepts, but they are fragmented across separate tools and internal state projections.

Gap

A back-office agent needs one place to ask: what requires attention right now?

Desired queue coverage

• open classification flags
• tax ambiguities
• reconciliation blockers
• pending document issues
• recent manual Excel corrections or other human interventions

Acceptance criteria

• Agents can fetch a single deterministic queue payload spanning the major review surfaces.
• Queue items include stable type/status/provenance fields.
• The queue can be filtered without requiring the agent to stitch together many low-level tool calls.

[elasticdotventures]

Technical questions:

• Which review surfaces must be normalized into one queue item schema, and which should remain separate linked views?
• Should queue items be immutable projections with follow-up actions pointing to other tools, or should the queue tool also support direct action subcommands?
• How should recent manual Excel changes be detected reliably in the current architecture?

Process questions:

• Do we want one default queue ordered by urgency, or multiple explicit queue slices under a shared tool?
• Should humans be able to tune prioritization rules, or keep them fixed and deterministic first?
• Is unified queue design blocked on persistent-state work, or can a first version be shipped with current state semantics?