burnwatch 0.12.1 → 0.13.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +14 -0
- package/dist/cli.js +567 -55
- package/dist/cli.js.map +1 -1
- package/dist/hooks/on-file-change.js +125 -9
- package/dist/hooks/on-file-change.js.map +1 -1
- package/dist/hooks/on-session-start.js +111 -19
- package/dist/hooks/on-session-start.js.map +1 -1
- package/package.json +1 -1
- package/registry.json +6 -1
package/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,20 @@ All notable changes to burnwatch will be documented in this file.
|
|
|
5
5
|
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
|
|
6
6
|
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
7
7
|
|
|
8
|
+
## [0.13.0] - 2026-03-25
|
|
9
|
+
|
|
10
|
+
### Added
|
|
11
|
+
|
|
12
|
+
- **Utilization Engine** — Code-derived cost projection system that tracks SDK call sites across the project, persists them to `.burnwatch/data/utilization.json`, and projects monthly utilization and overage costs. This is the forward-looking early warning system: it tells you what your code *will* cost before you ship it.
|
|
13
|
+
- **`burnwatch scan` command** — Full project scan for utilization patterns. Shows a table of services, call site counts, projected monthly units, plan inclusions, and overage costs. Use `--verbose` to see individual call sites per file.
|
|
14
|
+
- **Incremental utilization tracking in hooks** — The PostToolUse hook now updates the utilization model after every file change. Overage warnings are injected into Claude's context when projected overage exceeds $5/mo.
|
|
15
|
+
- **Utilization in session brief** — The SessionStart hook appends utilization data to the spend brief, showing projected usage alongside billing API data.
|
|
16
|
+
- **LIVE vs utilization divergence alerting** — For services with billing API data (LIVE tier), the utilization model runs silently unless projected cost exceeds current spend by >50% AND >$5 (both thresholds required to avoid noise).
|
|
17
|
+
- **Auto-scan on init** — `burnwatch init` now runs a full utilization scan after service detection. The utilization model is populated from day one.
|
|
18
|
+
- **Utilization in interview JSON** — `burnwatch interview --json` now includes a `utilization` field with projected monthly units, plan inclusions, overage costs, and top call sites per service. Enables agents to say "your code projects 1,060 sessions/month, 960 over your plan."
|
|
19
|
+
- **6 new `unitRate` values in registry** — Browserbase ($0.10/session), Resend ($0.001/email), Inngest ($0.01/fn run), SendGrid ($0.001/email), Replicate ($0.001/prediction). LLM services intentionally omitted (model variance too high for single rate).
|
|
20
|
+
- **22 new tests** (70 → 92): Model operations, overage math, divergence alerting, file analysis, brief formatting, round-trip persistence.
|
|
21
|
+
|
|
8
22
|
## [0.12.1] - 2026-03-25
|
|
9
23
|
|
|
10
24
|
### Fixed
|