The Tala language and its tools are no longer developed as of 2026-11-10;
Progmasoft puts its work into Tazel, now a build system for C, C++,
Objective-C, Objective-C++ and Zig. tala.run is prepared for OpenTala, a
kernel, and TalaOS.

- ops/nginx/tala.conf and forum.conf: every page of tala.run, www.tala.run,
  talac.tala.run, talafmt.tala.run, talalint.tala.run and forum.tala.run
  answers 302 to https://tala.run/unavailable?reason=maintenance. 302, not
  308, so neither browsers nor Cloudflare keep the redirect once the domain
  serves other pages.
- /unavailable answers 503 with Retry-After, X-Robots-Tag noindex and a
  strict policy; its body is ops/maintenance/unavailable.html, a static page
  in English, German, Russian and Hebrew that names OpenTala and TalaOS.
- ACME on port 80, tazel.tala.run (to tazel.net), the former domain's
  redirects and viget.xsharp-lang.xyz (to viget.progmasoft.com) keep
  working. ops/nginx/tala-maintenance.conf, the 503 vhost it replaces, is
  removed.
- README and Documents/OPERATIONS.md say so; the site tests check the
  redirects, the notice and its four languages instead of the served routes.

Installed on the first server before this PR (previous files in
/root/tala-run-before-unavailable); every host checked from outside.

Pin the CodeQL action to its v4.38.2 release

Drop Xide from the IDE answer of the Overview FAQ

The init and analyze steps were pinned to 7999b86c, a commit no release tag
points at, with a "# v4" comment that names another commit (zizmor
ref-version-mismatch, two code-scanning alerts). Both steps now use
2892aa5e, the commit of v4.38.2, with that exact version as the comment.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

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.

Let Cloudflare Web Analytics run on the Tala sites

Redirect tazel.tala.run to tazel.net for good

The four hosts of the site now allow Cloudflare's Web Analytics beacon,
but ARCHITECTURE.md and OPERATIONS.md still said the policy blocks every
script an intermediary adds. Both now name the beacon, where it loads
from and where it reports, and keep the forum placeholder's same-origin
policy apart.

Cloudflare adds its Web Analytics beacon to each page it serves. The
policies of tala.run, talac.tala.run, talafmt.tala.run and
talalint.tala.run fell back to default-src 'self' for scripts, so the
browser refused the beacon. They now allow scripts from
static.cloudflareinsights.com and connections to cloudflareinsights.com;
the beacon reports to /cdn-cgi/rum on the same host.