Add transaction query plus preflight exposure for filename validation and rule preview

[elasticdotventures]

Summary

Useful operator capabilities exist or are implied, but the current MCP surface does not cleanly expose them as agent-first actions.

Missing operator-facing actions

• transaction search/query by account/date/category/amount/source_ref
• source filename validation as a top-level preflight action
• Rhai rule preview/test against sample transactions

Why this matters

These are common planning and diagnostics tasks for an autonomous financial-documents operator.

Acceptance criteria

• Agents can query transactions without scraping workbook exports.
• Agents can validate a source filename before ingest.
• Agents can preview/test a classification rule over sample inputs through MCP.
• The capability shape is consistent with the reduced top-level surface.

[elasticdotventures]

Technical questions:

• Should transaction query be a top-level read model with filters/sort/pagination, or a lighter diagnostic helper first?
• Should filename validation and Rhai rule preview live under the same top-level documents/review tools as subcommands, or remain separate advanced actions?
• Do we need sampled rule preview over many transactions, or only one explicit sample payload initially?

Process questions:

• Which of these is release-blocking for the 7-tool redesign versus follow-on scope?
• Should query semantics be aligned to workbook concepts, event concepts, or both?
• Do we want these operator-preflight capabilities documented as standard agent workflow steps?