### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

Usage data from April 30th is being double-counted. It is correctly attributed to the April budget but is also incorrectly surfacing in the May budget total, leading to "pre-exhausted" balances for the current month. **Problem Description** The budget tracking system is failing to reset the "Month-to-Date" (MTD) counter at the start of the new billing cycle. Specifically, the token/spend spikes recorded on April 30th have carried over and are being aggregated into the May 1st totals.

<img width="1453" height="245" alt="Image" src="https://github.com/user-attachments/assets/91ae8a1f-6752-4d5e-841a-97e7652629c2" />

<img width="1414" height="215" alt="Image" src="https://github.com/user-attachments/assets/49a54f5b-6061-4456-bed0-12fa85758242" />

**Expected Behavior:** May 1st should begin with a $0.00 (or 0 token) baseline, reflecting only usage occurring within the calendar month of May.

**Actual Behavior**: May's total includes the final 24 hours of April's usage, causing users to exceed or approach budget limits prematurely.

### Steps to R…