Hebrew A second pass over the Hebrew text replaced words a Hebrew reader would misread or that are not used for the concept: "native" was rendered with the word for "local", "lowering" with the word for "download", "pipeline" with a literal pipe and "front end" with a word not used for compilers. Typed forms, diagnostics, the ecosystem and the standard library use the usual terms. The text is still not reviewed by a native speaker. Language choice A language change is now stored only after the visitor has acted on the page, as reported by navigator.userActivation. A change that reaches the page before anyone has clicked, tapped or typed still changes the language but is not remembered, so only a person can make a choice. A browser without the activation API keeps the earlier behaviour. During local testing a choice was once found stored without one being made. It could not be reproduced in three attempts, and restoring form state was shown not to fire a change event, so the cause is unknown; this guard closes the path in the page itself. Verified locally: frontend tests, type check, prettier and build. In a browser, a scripted change before any interaction switched the language and stored nothing, and a change after a real click was stored and survived a navigation. The forum page was opened in a browser: one notice, no language menu, English for a Turkish browser, and the Hebrew, German and Russian notices when the script ran with those browser languages.
Language Hebrew (he-IL) joins English, German and Russian on the language site, in the page metadata and in the list the backend reports. A visitor who has not chosen a language now starts in the language of their browser: the first preferred language that is published, compared by primary language, with `iw` accepted as the former code for Hebrew. A browser that prefers no published language gets en-US. A choice made in the menu is kept under a new storage key and always wins. The earlier key was written on every visit, so it could not tell a choice from the former English default; it is no longer read, which resets an earlier explicit choice once. Hebrew does not mirror the page. The layout, the navigation and code keep their left-to-right arrangement; only text follows the language. The onward arrow points left in Hebrew, and a left-to-right mark keeps "Visual X#" intact inside right-to-left text. The forum placeholder no longer has a language menu. It shows its one notice in the language of the browser, with English as the fallback, and stores no language. Its assets get a new cache key. The single documentation column may now shrink below its widest code line. Before, a long command widened the page on narrow screens, which cut right-aligned text off. The Hebrew text was not reviewed by a native speaker. Documentation gate The backend applies Dokka 2.2.0 with reportUndocumented and failOnWarning, its public declarations have KDoc, and CI runs dokkaGenerate. The dependency lock file and the verification metadata include the new artifacts. Verified locally: frontend tests, type check, prettier and build; backend test, bootJar and dokkaGenerate, which was also shown to fail on an undocumented declaration; the Hebrew pages in a browser. The forum page was exercised by its tests only.
Russian (ru-RU) is the third locale of the language site: the shell, the home, overview and getting-started pages, and the page metadata are fully translated, and the language menu offers it. The documentation sidebar reads its labels from the page messages instead of a two-way locale test, and the stored preference is accepted only when it names a supported locale. The forum placeholder gets the same three languages. Its language control is now a menu instead of a two-state button, and an unknown stored or selected value keeps the current language. The site API lists the new locale. Verified locally: prettier, the frontend tests, vue-tsc and the Vite build, the backend tests, and a browser run of the home and overview pages in Russian.
Move the Progmasoft mail operations baseline to its owning Progmaweb repository, remove the retired Astro account UI and duplicate identity backend, keep only the ViGet health boundary, add canonical sitemap signals, strengthen dependency CI, and adopt Patent Grant 1.1 across project-owned files.