Open the report on last month

The report answered for the whole index, which is the one window a spending
report is least often asked for: last January's groceries sat in the same total
as last week's, and nothing on screen said which was which. It now opens on the
month that has just ended -- the last one a statement can be complete for --
and left/right step along an axis beside the totals, from all time down through
the named windows to the oldest month the index holds.

The period narrows the report and nothing else. reloadReport runs its own query
rather than reusing the rows the transaction list is showing: the two share the
account, the search and the untagged toggle, and differ only in the date
bounds, so opening on last month must not hide the rest of the index from the
list beside it. Nothing may put the period into m.filter, which is exactly what
would make it leak.

The windows are relative to today, never to the newest statement. "Last month"
with nothing in it reports nothing and says so, because silently answering for
a month nobody asked for is worse than an empty screen; an empty period and an
empty index therefore give different messages, one asking for another period
and the other for an import. The rolling windows run to the end of this month
rather than to the last complete one -- "last 3 months" is asked in order to
see what is happening now, and leaving out the days since the 1st answers a
question nobody put. The axis is built over the whole index rather than the
rows in view, or it would grow and shrink as the account or search filter
changed and move under the cursor; a reload rebuilds it, since an import can
reach further back, but keeps the window the user was on.

s cycles how those rows are arranged: largest out first as before, then in, net
lowest first so the biggest losses lead, count, and the tag A to Z. A letter
rather than a chord because the report is not a form. The marked heading says
which column the rows are read from and the help names what the key does next,
as the rule builder's preview already does. The sort rearranges rows and never
changes which rows there are, so the order stays out of the filter for the same
reason the period does. Currency remains the outer key under every order --
there are no rates here, so two currencies interleaved by amount would invite a
comparison that cannot be made -- and every order falls back to the tag, so
ties keep a fixed position instead of reshuffling between reloads.

money report takes the same choice as --sort out|in|net|count|tag, and a
misspelt one is refused rather than silently reporting in the default order. It
keeps --month and has no equivalent of the wider windows.

store.Filter gains From and To, compared as strings because dates are stored
ISO-8601 and a string comparison is therefore a date comparison. store.Months
replaces report.Months, which nothing had ever called: the axis needs the
months of the whole index, not of a slice already in hand.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

CLAUDE.md

@@ -142,6 +142,35 @@ Anything new that reports a rule must report its file position too.
 settles ties: a saved rule cannot displace an equally specific one written by
 hand, while a narrower one is meant to take precedence and does.
 
+**The report's period narrows the report and nothing else.** The screen opens
+on last month, and `←`/`→` step along `report.Periods` — the named windows,
+then the months the index holds. `reloadReport` therefore runs its *own* query
+rather than reusing the rows the transaction list is showing: the two share
+`m.filter` (account, search, untagged) and differ only in the date bounds, so
+opening on last month must not hide the rest of the index from the list beside
+it. Nothing may put the period into `m.filter`, which is exactly what would
+make it leak. Covered by `TestReportPeriodLeavesTheTransactionListAlone`.
+
+The axis is built from `store.Months` over the *whole* index, not from the rows
+in view, or it would grow and shrink as the account or search filter changed and
+move under the cursor. It is rebuilt on every `reload` (an import can reach
+further back) but keeps the window the user was on. The windows are relative to
+today, never to the newest statement: "last month" with nothing in it reports
+nothing and says so, because silently answering for a month nobody asked for is
+worse than an empty screen. That is also why an empty period and an empty index
+give different messages — one asks for another period, the other for an import.
+
+**The report's sort rearranges rows; it never changes which rows there are.**
+`report.Order` is passed to `ByTag` and is deliberately *not* part of
+`store.Filter` or `m.filter` — the period decides what is counted, the order
+only how it is listed, and merging the two would make a sort able to hide a
+tag. Currency stays the outer sort key under every order, because there are no
+exchange rates to compare two currencies by, and every order falls back to the
+tag so ties keep a fixed position instead of shuffling between reloads.
+`Order.Column` is what lets the TUI mark the sorted heading without keeping its
+own copy of that mapping; a new order needs a column of its own, which
+`TestOrderColumnsAreDistinct` checks.
+
 **The builders are forms, so the global keymap must not apply there.**
 `Update` routes to `updateRules` / `updateTransfers` before `updateNormal`
 whenever the view is `viewRules` or `viewTransfers`, or typing `q` would quit