website, branch docs/linux-libcxx The site of tala.run: a Vue frontend and an ASP.NET Core API. Describe the libc++ toolchain of the Linux hosts 2026-10-16T18:31:31+00:00 Leitwolf11 2026-10-16T18:31:31+00:00 efca790acb61ad35fedec22bd99c35657f1c6675 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++. 
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++.
Merge pull request #35 from Progmasoft/fix/stale-statements 2026-10-16T04:16:22+00:00 Leitwolf 2026-10-16T04:16:22+00:00 4504828d370b1471b88bd318a950ba58d1e5282b Correct stale statements on tala.run and rename the vxs storage keys 
Correct stale statements on tala.run and rename the vxs storage keys
 Correct stale statements on tala.run and rename the vxs storage keys 2026-10-16T03:05:28+00:00 Leitwolf11 2026-10-16T03:05:28+00:00 3c3c9b10e1ccf218831789bcc59d488200ed12c6 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. 
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.
Merge pull request #34 from Progmasoft/feature/tala-run 2026-10-15T15:43:48+00:00 Leitwolf 2026-10-15T15:43:48+00:00 0b4634261957c81626cf134d3126ae3d3a04735a Serve tala.run, document talac and Tazel, and move the site API to ASP.NET Core 10 
Serve tala.run, document talac and Tazel, and move the site API to ASP.NET Core 10
 Annotate the lock file of the documentation check 2026-10-15T15:35:37+00:00 Leitwolf11 2026-10-15T15:35:37+00:00 607a15b1e856097ff4f8e3892368217a4672f16b Running CheckDocumentation.cs writes a NuGet lock file beside it, as every project of the repository does; REUSE.toml now covers it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> 
Running CheckDocumentation.cs writes a NuGet lock file beside it, as
every project of the repository does; REUSE.toml now covers it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Gate the API documentation with DocFX 2026-10-15T15:35:17+00:00 Leitwolf11 2026-10-15T15:35:17+00:00 018696d64cdb4088c0dd502ceab8d8ed9e11543e The Kotlin backend checked its documentation with Dokka; the ASP.NET Core API had only the compiler warning for a public declaration without a comment. CI now builds the API reference with DocFX, every warning as an error, and Documents/api/CheckDocumentation.cs fails when a namespace, type or member of the reference has no description, internal and private members included. The setup is the one Progmaweb uses: the docfx tool pinned in .config/dotnet-tools.json, the configuration and the namespace description under Documents/api, and the generated reference ignored. 
The Kotlin backend checked its documentation with Dokka; the ASP.NET Core
API had only the compiler warning for a public declaration without a
comment. CI now builds the API reference with DocFX, every warning as an
error, and Documents/api/CheckDocumentation.cs fails when a namespace,
type or member of the reference has no description, internal and
private members included. The setup is the one Progmaweb uses: the
docfx tool pinned in .config/dotnet-tools.json, the configuration and
the namespace description under Documents/api, and the generated
reference ignored.
Treat tala.run as an HSTS-preloaded domain 2026-10-15T15:28:17+00:00 Leitwolf11 2026-10-15T15:28:17+00:00 a460c4c7e922f37705b2be3f1fa7c789f514cd51 .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. 
.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.
Run the backend job on Ubuntu 2026-10-15T15:26:11+00:00 Leitwolf11 2026-10-15T15:26:11+00:00 18951f0c5c6e3f54ccd8757cec040a40bd2b5068 The ASP.NET Core API builds and tests the same on every host, and the macOS runners are the queue every repository of the organization waits in: the first run of the job was cancelled before it started. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> 
The ASP.NET Core API builds and tests the same on every host, and the
macOS runners are the queue every repository of the organization waits
in: the first run of the job was cancelled before it started.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Format the forum page with the repository settings 2026-10-15T15:05:02+00:00 Leitwolf11 2026-10-15T15:05:02+00:00 3a0fc99ec7a24337d6605440f726e94f67344781 The page was reformatted with the default settings of Prettier, which wrapped its notice differently from the repository configuration and split a sentence the integrity test looks for. 
The page was reformatted with the default settings of Prettier, which
wrapped its notice differently from the repository configuration and
split a sentence the integrity test looks for.
Document tala.run, the documentation hosts and the ASP.NET Core API 2026-10-15T15:03:29+00:00 Leitwolf11 2026-10-15T15:03:29+00:00 e0051b082ffce6e3cf066433980539c330d32181 - 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. 
- 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.