The compiler now builds with libc++ on Ubuntu and Fedora and links LLVM
built with libc++, which the developer helper of the compiler repository
downloads. The getting-started guide still said that the LLVM
development packages of the distribution are used; in all four languages
it now says that Clang, LLD and libc++ come from the distribution and
that the helper downloads LLVM built with libc++.

An audit of the site against the compiler repository found statements
that no longer hold, in all four languages:

- the overview named BUILD.kts as the project definition, while Tazel
  reads one of five names; it now says a project file, BUILD.kts or one
  of four other names;
- the overview and the getting-started guide named Windows and macOS as
  the only development hosts. Ubuntu 26.04 LTS and Fedora 43 are official
  hosts too, and the guide says which toolchain they use;
- the getting-started guide listed the counterparts of the examples in
  C#, C++ and Java; the examples also have Rust ones;
- the project-file page wrote build/debug/Example without the .exe a
  Windows build has.

The talac, Tazel and syntax pages were checked against Documents/CLI.md,
Documents/PROJECT_FILES.md and Spec/Language and are otherwise accurate.
Of the 43 links in the repository, only the address inside the Fira Sans
licence text no longer answers; that text is third-party and verbatim.

The browser storage keys still carried the former name of the language:
vxs-locale-choice, vxs-theme and vxs-forum-theme become tala-locale-choice,
tala-theme and tala-forum-theme. A value under a former key moves to the
current one on the first page load, so no visitor loses a choice; a forum
test covers the move. The npm package is renamed from
@visual-xsharp/website to @progmasoft/tala-website, and the forum assets
get a new version query so Cloudflare serves the new script.

.run has no HSTS requirement of its own, but tala.run is served as if it
had one: every HTTPS response of tala.run, www, talac, tazel and forum
sends max-age=63072000; includeSubDomains; preload, and plain HTTP only
answers the ACME challenge and otherwise redirects to HTTPS. A test
checks both for every tala.run block of the three Nginx files. The
redirects of the former .xyz domain keep their header.

- README, Architecture and Operations describe the three sites one
  build serves, their routes, the per-host sitemap and robots files,
  forum.tala.run, the permanent redirects of the former domain, and that
  tala.run has no ViGet host.
- The backend sections describe the ASP.NET Core 10 API: how to build,
  test, run and publish it, its lock files, and its place on the server
  in current/site-api beside the legacy process of Progmaweb.
- Development explains ?site=talac and ?site=tazel on a development host
  and lists the new test file; the release and rollback steps label
  current/site-api for SELinux as well.
- The development server proxies /api to port 5086, the port the API
  uses unless PORT says otherwise.

The language now lives at tala.run. One frontend build serves three
sites and picks its content from the host name:

- tala.run: the home page, /docs/overview, /docs/getting-started and a
  new /docs/syntax, a first look at programs, comments, declarations,
  operators and evaluation by need, with every sample taken from the
  public specification.
- talac.tala.run: /docs/command-line and /docs/outputs, the compiler's
  options, the entry rule, warnings, --build and --emit, and the record
  of a check.
- tazel.tala.run: /docs/commands and /docs/project-file, the commands of
  the build system, target selection, workspaces and the project DSL.

The new pages are written in all four locales from one content model;
a test keeps code samples and option names identical across them. The
header links the three sites and forum.tala.run. On a development host
?site=talac or ?site=tazel selects a site.

Corrections to the existing pages:

- Getting started used `go run scripts/develop.go`, `talac check -File`,
  `talac build -File` and `-Help`; it now uses `go run ./helpers/cmd/...`,
  `--emit=metadata`, `--entry=` and `--help`.
- The overview no longer names the retired .vxse extension, and the
  project DSL is evaluated by Tazel.
- Canonical URLs, Open Graph data, robots.txt and the sitemap name
  tala.run; talac and tazel have their own robots and sitemap files,
  served per host by Nginx. The notice about the move is gone: the
  former domain redirects instead.
- The leopard mark files are called tala-mark.svg and tala.svg.

Nginx: ops/nginx/tala.conf serves the three hosts, redirects www.tala.run
to tala.run and every path of xsharp-lang.xyz to the same path of
tala.run, and keeps viget.xsharp-lang.xyz pointing at
viget.progmasoft.com; tala.run has no ViGet host of its own.
ops/nginx/forum.conf serves the informational page at forum.tala.run and
redirects the former forum address to it.

The logo already said Tala while the header, the titles, the pages and the
forum notice still said Visual X#. The text now names the language Tala in
the four languages of the site, in the page metadata and in the forum notice.

With the name go the things that changed with it: source files end in .tala,
the project file is BUILD.kts, the compiler is talac, and the links lead to
Progmasoft/tala. A native executable still ends in .vxse, so that stays.

The forum page refers to its stylesheet and script with a new version value,
because the script changed and a cache in front of the host keeps the old
file for hours.

Not changed: the host names, the file name of the mark, and the keys under
which the browser keeps the chosen language and theme, so that a visitor
does not lose them.

Two lines of the new test were longer than the 100 columns Prettier allows,
and the formatting check of the frontend failed. The title of the test is
shorter and the pattern that looks for the host check no longer spells out
the whole expression.

The language is now Tala. The home page and the social image use the new
logo; the mascot is the same drawing, and the test that compares the mark
with the leopard of the full logo still holds. The logo of the site is the
supplied drawing without its opaque background.

On xsharp-lang.xyz and its subdomains a line above the header says that the
site moves to a new domain within a month and that xsharp-lang.xyz keeps
working and will redirect. The line is written in each of the four languages
of the site and follows the language switch; it is not shown on any other
host, so a preview or the new domain does not carry it.

The rest of the text of the site still says Visual X#; that follows with the
new domain.

The frontend job runs `npm audit --audit-level=moderate`, and an
advisory published for source-map-js 1.0.0 to 1.2.1 (denial of service
through indexed source-map section offsets, high severity) now fails
it on every branch. The package is a transitive dependency of the Vue
compiler. The lockfile moves it from 1.2.1 to 1.2.2, as `npm audit fix`
does; nothing else in the lockfile changes.

- Google-Extended, Google's token for model training, is now allowed.
- GPTBot, OpenAI's training crawler, is now disallowed. OAI-SearchBot and
  ChatGPT-User, which index and fetch pages for answers, stay allowed.
- ClaudeBot, Anthropic's training crawler, is now allowed, next to
  Claude-SearchBot and Claude-User, which already were.

Every other rule is unchanged.

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