fix(reports): make the Uncategorized spending drill-down load its transactions

[KenTaniguchi-R]

Clicking Uncategorized on /reports (Spending tab) opened a drill-down sheet reading "No transactions found." Two bugs stacked on the same value.

1. The fetch never fired

DrillDownSheet fetched from an effect keyed on the filter's individual fields:

}, [filter?.categoryId, filter?.month, filter?.type, effectiveDateFrom, effectiveDateTo]);

While the sheet is closed filter is null, so every one of those reads as undefined. An uncategorized drill-down carried categoryId: item.id ?? undefined, making the open state field-for-field identical to the closed state — nothing in the deps changed, the effect never re-ran, and rows stayed [].

Every real category has a non-undefined id, which is why only Uncategorized broke, and why it appeared to work if you opened a real category first ("abc" → undefined is a change).

Now depends on the filter object itself, which is fresh state on each click.

2. Even once it fired, it queried the wrong thing

The null categoryId was flattened to undefined twice on the way down — in report-spending.tsx and again in actions/reports.ts. getTransactions reads null as IS NULL but undefined as no category filter at all (queries/transactions.ts:106-109), so the sheet would have listed every transaction in the range. The null is now carried through.

Also fixed

• Footer link. "View all in Transactions" had the same hole: it dropped the category param for null, linking to all transactions. Extracted as drillDownTransactionsUrl, which emits the category=uncategorized sentinel parse-transaction-filters.ts already understands. Unit tests cover the three id states plus month narrowing.
• The chart's "Other" slice. It also carries id: null, so with the null now meaningful it would have drilled into Uncategorized. It spans several categories, which drill-down can't express, so it's flagged synthetic and inert on click — that flag also replaces the fragile id === null && name === "Other" check used to pick its neutral color.

Cash Flow and Income vs Expense drill-downs are unaffected: both queries exclude null categories (isNotNull(transactions.categoryId)), so neither can produce an uncategorized row.

Verification

• pnpm typecheck, pnpm lint clean
• 4 new unit tests + 45 existing report/spending/transaction integration tests pass
• Against the local dev DB, the default 3-month range holds 87 uncategorized expense transactions ($15,589.86) that the sheet was hiding

🤖 Generated with Claude Code