Skip to content
Trazum

2.7.12

Released 2026-11-17

Added#

  • Triage that happens whatever opened the issue, and a roadmap made of the issues. CONTRIBUTING.md said every new issue starts as needs-triage. On 2026-11-17 eleven issues were open and none carried a label: the forms apply theirs, and none of the eleven had come through a form. The Triage workflow now gives every new issue a state, and gives a pull request from this repository an area for each package its paths touch and the kind of the issue it closes; it only adds, so a label a person changed stays changed. New labels: blocked, for work that is accepted and waits on something held outside the repository, and area:core, area:cli, area:mcp, area:web, area:action and area:vscode. The open issues are triaged: seven of the ten backlog items turned out to be waiting on a key, an account or an export only the owner holds, and say so now. ROADMAP.md gains "Open work, as issues", a table of the accepted and blocked issues drawn by node scripts/triage.mjs roadmap; the weekly run fails when the page and the issue list disagree. CONTRIBUTING.md gains a "Review" section, what a review here looks for and how a machine's finding is handled, and .coderabbit.yaml configures a review bot that is free on public repositories: it is told those same questions, reviews drafts because that is the state a pull request is reviewed in here, and has every feature that writes to the repository switched off. It does nothing until the owner installs the app. Five issues are open for a first contribution: the French, German, Portuguese, Italian and Dutch dictionaries each need one afternoon from somebody who reads the language (#680 to #684). (#679)

  • The command reference documents every command. docs/commands.md had no chapter for six of the 55 commands trazum --help lists: init, where, schema, rules, filter and models. Each has one now, with output transcribed from a run, and command-reference.test.js holds the page to the CLI's own list: a command with no chapter fails, as does a link on the page to a chapter that is not there. Four commands (optimize, check, baseline, eval) stay under chapters named for the job, each held to the chapter that runs it. Found by checking the living docs against the CLI: every command and flag they mention exists, every model id is in the catalogue, and the package READMEs' examples import exported names. docs/setup.md and docs/running.md pin the Action at 2.7.11 where they said 2.7.9, and scripts/freshness.mjs no longer says a stale price warns "every user": it warns on reports that priced that provider. (#673)

  • The web app answers for /favicon.ico, an Apple touch icon and a web manifest. Measured on the deployed app on 2026-11-17, each of the three answered 404 and the page carried one icon tag, to icon.svg: a client that asks for /favicon.ico without reading the page got nothing, and a phone's home screen got a screenshot. The app now ships favicon.ico (16, 32 and 48 pixels), a 180-pixel touch icon and a manifest with 192 and 512-pixel icons and a maskable one, all of them the T of icon.svg, written by npm run draw:icon and held byte for byte by brand.test.js. The manifest declares display: browser: it names and draws a shortcut and does not claim an installed app. (#675)

Fixed#

  • The safe level no longer rewrites a thanks, a quotation or three ordinary words. Found by drawing the README's picture from a real run (#675): the shortened support prompt contained "So much for your help with this." and "In advance." The politeness rule deleted each courtesy phrase wherever it stood, and measured on 2026-11-17 that did three kinds of damage at the level that promises not to change what a prompt asks for. A fragment where a sentence was: "Thanks a lot for doing this." became "A lot for doing this.", and the same in Spanish, French and German. A broken instruction: "Tell the customer: thank you for your order." became "Tell the customer: for your order.", and "Thanks to the new policy refunds take five days." lost its first word. A changed instruction: "Speak kindly to the customer." became "Speak to the customer.", "Aim to please the customer." became "Aim to the customer.", and "If the user says thanks, reply politely." became "If the user says reply politely." A thanks is now removed only as a whole sentence that does nothing but thank, with what it is for, and is left exactly as written when it follows a colon, sits in a list, opens a clause or is what the sentence is about. One courtesy is deliberately no longer removed: a thanks hung on the end of a clause by a comma ("summarise it for me, thank you very much") cannot be told from the last item of a list of things to say, so it stays. "please" after "to", "kindly" anywhere but in front of what is asked, and German "Bitte" after a determiner are left alone. Text inside quotation marks is protected, as code, URLs and placeholders already were: Reply "Please hold on" used to become Reply " hold on", so the model was told to output a different string and the report counted the difference as a saving. ProtectionKind gains quoted. This also corrects a figure this project published about itself: docs/our-own-medicine.md said the rules recover 12 tokens from the four system prompts the package ships, credited to emphasis. All 12 were the rules rewriting "..." to "." inside the JSON example in two of those prompts. The figure is 0. On examples/support-prompt.txt the shortened prompt is now clean and the README's picture is redrawn: 326 tokens down to 202, $31.00 a month, and a first lever worth $416.99, 13 times more. (#677)

  • The README's pictures show what the CLI prints, in the product's own identity. docs/assets/demo.svg was typed by hand under a comment calling it a transcript, for a prompt that was in no directory of the repository. Its arithmetic was held to the price table and stayed right; the report around it moved on. On 2026-11-17 the CLI opened with its "Start here" line where the picture closed with it, suggested Claude Haiku 5.5 where the picture named Haiku 4.5, and assumed 300 output tokens where the picture said 500. It is now drawn by npm run draw:demo from a run on examples/support-prompt.txt, shows the first 26 of the report's 51 lines and says so in the picture, and demo-image.test.js fails when the file is not that output. The README's figures follow: 326 tokens down to 214, $28.00 a month saved by the rules, and a first lever worth $419.93, 15 times more. The same picture separated its columns with plain spaces, which an SVG shown through <img> collapses, so GitHub drew the transcript with its indentation and alignment gone; both transcripts now write no-break spaces and are as wide as their longest line. Both are coloured by the escape codes the CLI emits rather than by guessing from the shape of a line: the bill's share bars and its subscription caveat are drawn the way a terminal shows them. And the three pictures, with the editor extension's icon, were still in the palette and the mark the product had before DESIGN.md settled on acid yellow and a plain T, so the first screen of the repository, the editor's listing and the browser tab showed different products. All of them now take their colours and the T from scripts/brand.mjs, which brand.test.js holds to the web app's globals.css and icon.svg. docs/setup.md shows the web app from a production build, in the light or the dark theme to match the reader's; the previous screenshot was taken from a development server and had the framework's badge in its corner. The example prompt is one this repository's own gate reads, so trazum.baseline.json is re-recorded with it: three prompts, 877 tokens. (#675)

  • A batch call's cache reads on three Google models were billed at half of what Google charges. A batch call is priced at the row's batch ratio, and its cache reads at the row's cache ratio of that halved input, which is what most Batch tables print. Google's Batch tab for Gemini 3.1 Pro Preview reads "Context caching price: Same as Standard", $0.20 and $0.40 against batch inputs of $1.00 and $2.00, and the tabs of Gemini 2.5 Pro ($0.125) and 2.5 Flash ($0.03) print the standard figures. 2.7.11's notes named this as not changed. The three rows now carry multipliers.batchCacheRead: 0.2, the cache price over the batch input, and the bill, a session's cost, a truncated retry, a repeat, a conversation's growth and the usage-report connector all ask for the ratios of the call they priced. One batch call on 3.1 Pro Preview with 50,000 fresh input tokens, 100,000 read from the cache and 2,000 out was billed $0.072 and is $0.082. For the two 2.5 models the figure ends on 2026-12-01, when Google bills them at the rates of Gemini 3.8 Flash and 3.5 Flash-Lite, whose Batch tabs halve the cache price; 2.5 Flash gains a dated period for that, at the same $0.30/$2.50. The other six Google rows print a halved cache price and are unchanged, as is every other provider. A pricing overlay can set batchCacheRead. Read from Google's pricing page on 2026-11-17, for the Batch tabs' cache rows alone; Google's review date does not move. Seventeen planted faults were each caught. (#671)

Changed#

  • The npm token's expiry date is recorded: 2027-02-15. The token that published 2.7.11 was created on 2026-11-17 with ninety days to run, by its owner's account of it; npm shows the date only when a token is made, and this repository cannot ask for it. .github/release-credentials.json held null, which scripts/freshness.mjs could only print as a note. With the date, the weekly scheduled run goes red on main from 2027-02-01, fourteen days ahead, and scripts/prepare-release.mjs refuses to prepare a release from 2027-02-15. The token is counted as gone from the first minute of that day. Nothing installable changes. (#669)