Feature proposals from a power user (15+ projects, 170+ sessions/month)

First — great tool. Installed via `npx`, zero friction, immediately useful on a 15-project setup running 170+ sessions/month across Opus and Sonnet. Starred. Here are things I'd find valuable as a heavy user: ## 1. Per-project drill-down The project breakdown shows cost + session count. I'd love `codeburn report --project "My/projects"` to see the full dashboard (activity type, model split, tools, one-shot rate) scoped to just that project. When one project dominates spend (mine is 88%), the aggregate view hides what's happening in smaller ones. ## 2. Cost-per-session metric Average cost per session alongside the project breakdown. A $200/day number is less actionable than knowing 3 sessions averaged $60 while the rest averaged $5. ## 3. Date range filtering on `report` `codeburn report --from 2026-04-07 --to 2026-04-10`. Related to #5 (billing period) but more general. The export command could benefit from this too. ## 4. Model efficiency comparison For users who route between Opus/Sonnet intentionally: one-shot rate broken down by model, not just by activity. If Sonnet's one-shot rate on coding is 90% vs Opus at 93%, that's a meaningful routing decision. ## 5. Session outlier detection Flag sessions costing >2x the project average. A simple "top 5 most expensive sessions" with timestamp + project + dominant activity helps spot what went wrong (or right). ## 6. `--json` flag on `report` The TUI is great for human eyes, but piping structured output to dashboards,...