tazel run builds and runs one executable: the one --executable names,
the only one of the selection, or the project.defaultRun of the
selected ViPkg. It takes one --vipkg and one --executable at most and
no --library, and lists the executables when the choice is open. At
the root of a workspace, run chooses among the members instead of
working on each.

A new section describes tazel_options.txt: the nearest file decides
each option, sandboxing-with-microvm: true in any of them holds, and
with it every command except version and help stops before anything
runs on the host.

The commands page says so in en-US, de-DE, ru-RU and he-IL.

The first -- ends the name of a custom command, and a line of s(...)
reaches the shell unchanged. Written for the Tazel release that carries
tazel#40.

They were produced again with a real build, and they match, the LLVM IR
included.

Tazel left the compiler repository, which holds no Kotlin any more, so
building the compiler needs neither Temurin JDK nor Gradle. The page
now links Tazel as a repository of its own.

The command line page adds --sysroot, --incremental,
--static-talart-library, --test and the size levels, with sections on
incremental and test builds, in all four languages. The record of a
check now names Tala 0.2.0. The comment on the terminal samples says what
was checked: their messages against the source of Tala 0.2.0, while the
LLVM IR comes from an earlier build.

They said version 0.1.0 is built with the compiler of Tala 0.1.0, which
stopped being true with the next release of each. What holds for every
version is that a tool accepts what its compiler accepts.

Test suites work, so the note no longer lists them. The commands page
adds fetch, custom, the build cache, remote serve and the daemon, with
sections on spending the machine and on custom commands. The project
file page adds the execution block, the size levels and the shape of a
version. All four languages.