Skip to content
Trazum

1.20.0

When, and what you can build on

Added#

The shape of the day, drawn. The web Bill tab gains a 24-bar chart of spend per UTC hour — divs, like the day chart, no library — with the hours holding 80% of the spend in the warning colour and the same sentence the terminal prints. Hours with no traffic are drawn as empty rather than skipped: a chart that closed the gaps would make every workload look flat, and flat is exactly the finding that points at the Batch API. Verified in a real browser, zero network requests.

--json becomes a contract. docs/json-output.md documents every top-level field, the output carries a schemaVersion to branch on, and json-contract.test.js enforces the promise in both directions: a documented field that disappears fails, and a field emitted without a line in the doc fails too. Anything built on the machine-readable report could not previously tell "old Trazum" from "no data"; the promise is now explicit — fields are added without a version bump, dollars are unrounded numbers, absence is null or [] and never zero, and nothing carries a session key.

The shape of the day, and the lever it points at. spendByHour buckets exact per-record dollars by hour of the UTC day, and the report states the measure that needs no threshold to explain: the fewest hours holding 80% of the spend. Two hours is interactive traffic somebody is waiting on, where the Batch API's 24-hour turnaround does not fit; twenty is the shape background work has, and background work is exactly what the Batch API halves the price of. The sentence names the lever and never claims the saving — whether a workload can wait is a product decision counts cannot make, and the levers section already prices the batch route for whoever decides it. UTC, stated, for the reason spendByDay is: a local-hour bucket would make the same log answer differently in two offices.