Added#
- Trazum can be downloaded from the project's own places, with no marketplace account. (#774, #780, #781; advances #640, which stays open because no listing exists) The owner asked on 2026-11-19 for everything needed so it can be downloaded. Six parts:
- Release files. A new
assetsjob ofrelease.yml, which needs the job that publishes (so afternpm actually serves every packageand after the release page exists; the publish order is untouched), buildstrazum-vscode-<version>.vsixwith@vscode/vsce@4.1.1andtrazum-mcp-<version>.mcpbwith@anthropic-ai/mcpb@2.1.2(mcpb validatefirst), makesSHA256SUMSover them and the bill of materials, and attaches the three with the workflow's own token. The job holdscontents: writeand no npm credential,id-tokenor environment, because it runs two packagers fetched bynpx; the step that holds the token runs none of them. No marketplace, no new secret. The workflow makes no build-provenance attestation, so none is claimed. A manual run builds the files and attaches nothing. Built once here on 2026-11-19: the.vsixis 456,522 bytes in 132 files, the.mcpb492,983 bytes in 132 files. - A fault the first
.vsixhad.npm run package:vscodeproduced 8 files and 8.39 kB, and none was@trazum/core, whichdist/extension.jsimports: the ignore file excludednode_modules. The extension would have failed to load for want of it.scripts/release-assets.mjsnow lays the extension out with the closure the lockfile names and.vscodeignorelets exactly that package through. Not run inside VS Code or Cursor: only that the builtdist/reading.jsresolves its import from the unpacked file. - The bundle.
manifest.jsonuses only fields of the format'sMANIFEST.md(spec 0.3) and claims no platform: itscompatibilityis the Node version the package already declares. It holds the server's built files,@trazum/core's built files, the licence and the icon, and nothing the lockfile does not name. Its server was started from the unpacked bundle under plain Node and answeredinitializeandtools/list. Not opened in Claude Desktop. The bundle is unsigned. - The registry. The committed
server.jsonstays npm only: the digest of a file built after the release PR merged cannot be in it. Themcp-registryjob now waits forassets, downloads the bundle andSHA256SUMSfrom the release, andscripts/mcpb-registry-entry.mjsadds themcpbentry (address andfileSha256) to the copy it publishes, refusing when the file and the sums disagree. A failed attachment therefore holds the listing back until the job is re-run. Not run: it runs for the first time at the next release. - Homebrew.
packaging/homebrew/trazum.rb(@trazum/cli3.0.0, its npm tarball's SHA-256,depends_on "node"andstd_npm_args) is written byscripts/homebrew-formula.mjs, which compares the tarball's sha512 with the registry's before hashing it; a test holds the file to a fixture tarball with no network. Pushing it to the tap is a manual step, named inRELEASES.md:docs/compliance/secret-rotation.mdcovers no token for it and #781 forbids asking for one. Not tried withbrew install. - Gemini CLI, Codex and the other clients.
gemini-extension.jsonstarts@trazum/mcpat the exact version with the skill as its context file (fields from Gemini CLI's own extension reference);docs/agents.mdgains a table and snippets for Claude Code, Claude Desktop (bundle and JSON), Cursor, VS Code, Codex (command and TOML) and Gemini CLI, written byscripts/install-snippets.mjsfrompackages/mcp/package.jsonand held to it by a test.prepare-release.mjsmoves the manifest and the table with the version. Not tried withgemini extensions install. - The page.
/download, in the header, footer and sitemap and in the site's five languages: the CLI (npx,npm install -g, the tap) at the exact version, the MCP snippets drawn from the same source asdocs/agents.md, the.vsixwith how to install it, the Action's pinned line read fromdocs/setup.md, and the checksums. Links go toreleases/download/v<version>/<name>for the version the site is built at, neverreleases/latest; so for a short while after a release merges, and for 2.7.12 itself, whose release carries none of these files, those addresses do not answer, and the page says so. It names no store, loads nothing and sends nothing: a twenty-fifth browser flow watches the network, measures contrast in both themes and checks a phone, and took 2,145 ms on 2026-11-19 against a local production build.
- Release files. A new