Tvijo wiki
Catalog

Five desktop files, five native checks: Tvijo Code 1.140.07215

A dated record of native activation, file and command checks, installer lifecycle, public SHA verification and remaining trust limits.

The release we checked

On 29 October 2026, the Tvijo Code 1.140.07215 preview was published with five desktop artifacts. Each embeds Tvijo DSHREM 0.10.25. This is a dated project record of the CI evidence and public download checks, produced with automated tools.

Why each file needs its own check

The Windows ZIP and Windows installer are different files. Opening the ZIP does not establish that installation and removal work. Likewise, a successful Linux run says nothing about an Intel or Apple Silicon Mac. We bound each platform record to the SHA-256 of the archive or installer it tested.

The native checks activated the bundled extension, opened its guide, wrote a file in an isolated project and observed a successful command exit. The Windows EXE check additionally installed and uninstalled its temporary copy. All five records report a pass for their stated scope. Earlier failed attempts remain in the release work's evidence; they were not relabelled as successes.

Published file identities

The public files were downloaded without authentication and compared with the tested bytes. The records below are downloadable alongside the files.

The embedded extension is 0.10.25. Its SHA-256, source revision and build inputs are listed in BUILD_RECEIPT.json.

Limits of these observations

These tests do not establish interactive customer sign-in or a live paid-model coding workflow. Apple notarization is not established: the Mac check reports an ad-hoc signature and a Gatekeeper refusal. Windows publisher signing trust was not verified. The Linux artifact is a desktop tar archive; DEB/RPM package installation is a separate channel. Marketplace, standalone CLI and MCP publication are separate from this editor release.

Use the download page to choose an artifact and compare its full SHA-256 before installing. A task receipt can help inspect what actually ran; the earlier receipt record explains why that remains separate from accepting a user's whole task.

🔗 Article connections

Open the full knowledge graph ↗

💬 Comments

Comments are public and moderated. Do not post personal data.
  • No comments yet. Be the first!

Next steps