Skip to content
Trazum

1.64.0

The report somebody forwards

The 1.64 arc closes, delivered in full: the profile and the roll-up have an HTML door, the caveats are load-bearing in both, and the parity guard makes each page a projection of the JSON rather than a rival account of it. All four chapters landed on main before this minor; the minor is the story finishing.

Added#

  • The plan for 1.64, written before the code. One arc: the report somebody forwards. The profile and the roll-up gain an HTML door — one self-contained file, no external assets, both locales, printable — rendered from the same document --json prints, never from the log, so no second computation exists to disagree with the first. The caveats (unpriced models, skipped lines, cannotSay) render with the same weight as the totals they qualify, and the closing chapter is a parity guard that walks every dollar and token in the HTML back to the document in both directions, proved by breaking the renderer both ways. Stays out, by name: charting libraries, template languages, serving. The chapters run as 1.63.x and close at 1.64.0.

  • The roll-up ships the same door, and the parity guard closes the loop — chapters three and four of the 1.64 arc. trazum rollup gains --html-out, written on both output paths (a side file that vanished under --json is the fault the profile's --csv-out already taught this repository): one self-contained page for the team-facing document, where each contributor's gaps render under that contributor's own name — pooling them is the averaging the roll-up exists to refuse — and every cannotSay caveat, overlap-invisible included, sits in the caveat block ahead of the tables, impossible to crop out of a forwarded copy. Rejected contributions, repeated contributors and identical contributions land in the same block, by name. And the parity guard: a test walks every dollar figure anywhere in the page and every count in a numeric table cell back to the document the page was rendered from — nothing invented — and walks the document's headline figures forward into the page — nothing dropped. Both directions were handed the failure they exist for before being trusted: a forged dollar is named, a forged cell is named, and a page scrubbed of its headline is caught. The first draft of that last proof replaced one occurrence and blamed the guard for seeing the survivor — the one priced model's row legitimately equals the total, and the fixture, not the guard, was wrong.

  • The profile leaves the terminal — chapters one and two of the 1.64 arc. trazum profile gains an HTML door beside the Markdown one: one self-contained file — inline CSS, no scripts, no external assets, both locales, printable — for the person who pays the bill and does not run CLIs. It is a projection of the document --json prints: the renderer takes the exact same input object as the Markdown renderer, built once for both doors, so no second computation exists to disagree with the first. The caveats are furniture, not footnotes: unpriced models, unreadable lines, a log with no clock or no sessions, an unsettled cache TTL and a stale price table render in a bordered block ahead of the detail tables, at the same weight as the totals they qualify — and the suite asserts their presence by content and their position by offset, plus the other direction: a run with nothing to caveat earns a report with no block, because a box that always renders is a box nobody reads. Labels and model ids come from somebody's log, so everything interpolated is escaped, tested with a label that is itself an HTML injection.

Fixed#

  • profile --json --markdown-out crashed with a ReferenceError — since 1.59, on every release, and no test had ever asked. Under --json the terminal path never runs, and the side-file writer reached for that path's levers binding, which was never initialised. The HTML door's test drove both flags together and the flag turned out not to silently do nothing but to loudly do nothing. Reproduced against the published 1.63.0 before fixing; the side-file writer now derives levers and the cache verdict itself.

Release mechanics#

  • Five manifests, @trazum/core in three places, lockfile at 1.64.0; README Action pins advanced to bdca0df (1.63.0).