Xide is no longer developed as of 2026-11-08 (Progmasoft/xide#29), so
the answer to "Does Tala require a particular IDE?" no longer calls it a
future interface. In all four languages the answer now says only that
the supported workflow uses command-line tools on Windows, macOS and
Linux.

The integrity tests still expected tazel.tala.run to serve the Vue build
with its own robots.txt and sitemap.xml. They now count four app-shell
hosts and check the redirect itself: the two former pages go to their
pages under tazel.net/docs/reference/ with the query string, other docs
paths to tazel.net/docs, everything else to the same path, the /docs/
prefix is a plain one so the regular expression is reached, and HSTS
stays.

OPERATIONS.md and ARCHITECTURE.md list tazel.tala.run as a permanent
redirect instead of a documentation site.

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.