The latest c8 still asks test-exclude for ranges that npm audit now reports, and the fix npm offers moves c8 back a major version. Overrides take the fixed releases instead; coverage works with them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
They said version 0.1.0 is built with the compiler of Tala 0.1.0, which stopped being true with the next release of each. What holds for every version is that a tool accepts what its compiler accepts.
Test suites work, so the note no longer lists them. The commands page adds fetch, custom, the build cache, remote serve and the daemon, with sections on spending the machine and on custom commands. The project file page adds the execution block, the size levels and the shape of a version. All four languages.
The build that serves tala.run, talac.tala.run and tazel.tala.run now also serves the formatter and the linter, chosen by host name like the others. Each site has a landing page and two documentation pages in en-US, de-DE, ru-RU and he-IL: - talafmt: the command line (inputs, --check, --emit, exit status 2 for an unreadable line) and what it changes (indentation, line endings, trailing whitespace, the final newline; protected text; encodings from talafmt.kts). - talalint: the command line (--fix) and what it checks: the compiler's diagnostics as compiler.<code>, and format.trailingWhitespace, format.mixedLineEndings and format.missingFinalNewline. --fix rewrites a file with talafmt's default layout, which also re-indents blocks. The facts follow the READMEs of Progmasoft/talafmt and Progmasoft/talalint 0.1.0 and the talalint source. site.ts lists the sites once, with their names, so the header, the landing page and the documentation shell no longer keep their own copies. Each host has its robots.txt and sitemap.xml, nginx gains the two server blocks, and the tests check the new hosts like the others.
npm audit fix moves the development dependencies vite to 7.3.7 and launch-editor past GHSA-698v-4r3x-3vcv, GHSA-r825-w8mm-5pxw and GHSA-587h-7wmj-h5pm; the frontend audit gate failed on them. Prettier formats tests/site-integrity.test.mjs, which the format check flagged.
Nginx sent every path that is not a file to index.html with 200, so probes such as /wp-admin/install.php, xmlrpc.php and phpinfo.php were answered as pages: scanners take that for a hit, and search engines index soft 404s. The three server blocks now fall back to @application, which serves the app shell only for the routes of the application, / and /docs/<page>, and answers every other path with 404. error_page keeps index.html as the body of the 404, so a visitor still reaches the landing page through the router. A test reads the three sitemaps and requires every listed page to match the accepted routes, and scanner paths, /docs and nested paths not to; it also requires the same route rule in all three blocks. OPERATIONS.md describes the expected 404s, and asks for --no-same-owner, chown -R root:root and LF line endings when files are copied from a developer machine: the 2026-10-18 release had left the frontend owned by a Windows user ID. Applied on the server with the owner's approval and verified: nginx -t is clean; /, /docs/overview, talac /docs/command-line, tazel /docs/commands, robots.txt and /api/v1/site answer 200; /wp-admin/install.php, /no-such-page and /docs answer 404. npm test passes, 45 tests.
Tazel moved out of Progmasoft/tala into Progmasoft/tazel (tala#93), so the "Source" link at the end of the Tazel landing page pointed at a directory that no longer exists. In all four languages it now opens https://github.com/Progmasoft/tazel. The Tala and Talac pages keep their links into Progmasoft/tala.