I haven't written `output/ttm-note.md`. The budget-vs-actual script can't produce trailing-twelve-month figures, and this pack doesn't allow me to calculate them myself.

**Why:**
- `scripts/bva.py` only reports two periods: a single month, and the calendar year to date ending in that month. It has no trailing-twelve-month option.
- July 2024 to June 2025 crosses a calendar year and both of your files. Even if I combine the files, the script would give me January to June 2025 and drop July to December 2024.
- Getting TTM figures from that output would mean adding the two halves together by hand. The pack's rules forbid adding, subtracting or rounding figures myself. Every number in the note has to come straight from the script.

Both files have the columns the script needs. Note that `pnl_fy2025.csv` runs to December 2025, so any June 2025 run would need `--period 2025-06`.

**Options:**
1. **Year to date to June 2025.** I run the script on `pnl_fy2025.csv` with `--period 2025-06`. That gives January to June 2025 against budget, with June as the month. The note would follow the standard contract, and I could save it as `output/ttm-note.md` or `output/bva-note.md`.
2. **Add a trailing-twelve-month option to `bva.py`.** For example, a `--ttm` flag that accepts several input files, sums the 12 months to the chosen period and runs the same reconciliation checks. Then I'd write the TTM note from its output. This changes a shared pack script, so I'd only do it with your go-ahead.
3. **Two notes:** the full year 2024 from `pnl_fy2024.csv`, and year to date to June 2025 from `pnl_fy2025.csv`. Neither is a TTM figure, and the note would say so.

Which would you like?