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.

Tazel has its own site at tazel.net, so tazel.tala.run no longer serves
the build system's pages from this build. Every request answers with a
permanent 308 redirect:

- /docs/commands and /docs/project-file go to their pages under
  tazel.net/docs/reference/, keeping the query string;
- any other page under /docs/ goes to tazel.net/docs;
- every other path goes to the same path on tazel.net.

The host keeps its HSTS header. The README and the comments of the
configuration name the four sites the build still serves.

Say what -- and s(...) do in Tazel custom commands

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.

Say what the compiler needs today on the getting started page

Bring the Talac pages up to date

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

Stop naming versions on the formatter and linter pages