Skip to content
Trazum

2.4.1

The same door from the browser

A patch, on the plan's own terms: 2.4.0 built one door, trazum bill, and this release makes the two other places a stranger arrives at open onto it. The README and the landing page now begin with the one line that works with nothing installed, and the web app's drop zone reads every shape the door reads instead of three of them. bill also names the flag that prices an OpenRouter slug. Nothing here adds a command; the count stays at 51.

Changed#

  • The browser's drop zone is the same door as trazum bill. It read three shapes (Claude Code transcripts, OTel spans, LiteLLM logs) and took everything else as a plain usage log, so an OpenRouter activity report or an OpenAI usage report dropped on it was told every line was unreadable. It now detects and converts the five other shapes with the same core detectors and converters the CLI uses, reports one line per shape with the rows left out and the dedicated command that says why, and names a provider's cost report as a bill rather than usage, pointing at reconcile. Still nothing leaves the tab; folder-ingest.test.mjs holds every arm to the core detector and converter.

  • bill says which flag prices an OpenRouter slug. When the receipt's unpriced gap holds a model id with a slash in it, which is how OpenRouter names models and which the bundled catalogue does not carry, the run ends by naming --pricing-live. Derived from what was refused rather than from which shape the file was, and silent when the flag is already on or nothing unpriced is a slug.

  • The README and the landing page open with the one line that works with nothing installed. npx @trazum/cli bill ~/.claude/projects is the first section after the badges and sits under the landing hero in all five locales, before either button. Plan 2.4's first move said this line was the landing-page demo, and until now it was the fourth thing on the page.

Fixed#

  • The packaged Action pin in README.md and docs/running.md advanced to 2.4.0's release commit, the one v2.4.0 points at, which is the retry's merge rather than the release pull request's. It moves in the pull request after the release, as docs/releasing.md says it must: security.test.js asks git which commit the tag names and refuses any other commit that merely declares the version.

  • The release job checks out the whole history, as CI does. 2.4.0's first release run failed in verify and published nothing: changelog-coverage.test.js measures "not yet released" against the newest reachable tag and refuses to guess when a clone has none, and the release job's checkout was shallow where CI's is fetch-depth: 0. The guard was added after 2.3.0 and this was its first release, so the mismatch had never been exercised. The publish is retried by this merge: the manifests still name a version the registry lacks, which is what the decide job looks for.