Skip to content
Trazum

1.76.0

The tour that does the work

Added#

  • The tour stopped describing and started doing. The 1.76 plan: each step, as it opens its tab, performs the thing its card is talking about — the sample prompt optimised in front of the visitor (through the Optimiser's own auto pass, out of their history), the comparison run over the pair on screen, the sample month priced in Bill exactly as a paste would, and the terminal typing real commands character by character and executing them through the same path the visitor's Enter uses. The walk grows from seven steps to ten: the playground's one step becomes three (trazum profile usage.jsonl, trazum optimize prompt.txt), and a new "the CLI, complete" step closes the loop with trazum position usage.jsonl and the one line that installs the other forty-two-command reality. Copy rewritten in both locales to say what just happened rather than what would.

  • The demo bus (lib/demo.ts): a typed union and a module-scoped Set — no DOM, no React, no window events. The tour dispatches; the component that owns the page decides what the action means, through its existing run path, with a latest-ref so a dispatch always sees today's state.

  • The typing hand yields. A visitor keystroke or edit cancels the hand mid-word and their input wins — it is their terminal. Reduced motion types instantly. A hand still writing when the tab unmounts is cancelled with it.

Guarded#

  • Every demo is real (tour.test.mjs): each playground-run line is executed in the test against the shipped samples and must answer — a renamed sample or broken invocation fails in CI, not in front of a first-time visitor. Demo dispatch exists only in the Tour's step effect (grepped across every other component), the cancel contract is pinned in two places, and the bus is held to the no-fetch invariant.

Fixed#

  • The CLA gate's first live run found two defects: the action does not create its signatures branch (cla-signatures now exists), and the repository's own agent — committing as "Claude" under the owner's account — was not allowlisted, so every PR would have demanded a signature from a name that cannot sign. Allowlisted — and verified against the action's source rather than guessed: it compares committer.login || committer.name, and this agent's commits carry an email no GitHub account owns, so the raw name is what the pattern must match. Reading that source also surfaced a default nobody chose, lock-pullrequest-aftermerge: true, which locks the conversation on every merged pull request; it is now explicitly false, because a merged PR is still where somebody asks why a change was made.

Changed#

  • The README became the front door it claimed to be. Four thousand lines answered every question in one file and therefore none quickly; now the README holds the thesis, the forty-two-command table, the first five minutes, the surfaces, the models, the limitations and the privacy answer — and the deep chapters moved verbatim to docs/commands.md, anchors preserved, every link re-pointed and machine-checked. Nothing was cut: the same prose exists, one page over, and the README says so where each chapter used to be.

Added#

  • The Contributor License Agreement, gated in CI. docs/cla/CLA.md — an individual CLA whose preamble says what it is for: the project stays MIT, contributors keep their copyright, and the maintainer receives a licence broad enough (sublicensing and relicensing included) that future modules under other terms never need a per-contributor permissions hunt. Signing is one sentence in the pull request, recorded by contributor-assistant/github-action into .github/cla-signatures.json on its own branch; maintainer and bots are allowlisted. The workflow is the repository's one argued exception to the pull_request_target ban — it checks out nothing, and the security guard now pins exactly that: the exception exists only for cla.yml, only while no checkout appears in it, and the guard fails if the file leaves or the event does.