progmaweb/apps/web/proxy.ts, branch docs/api-and-web-reference

Switch language in place and add Russian

2026-10-02T21:20:50+00:00

The language control no longer reloads the page. It calls a server action
that stores the preference cookie; Next.js then renders the current route
again and applies it in place, so scroll position, theme and client state
stay. The lang query parameter remains for links and for browsers without
script, and is the fallback when the action cannot reach the server. Both
paths write the cookie with the same attributes from one function.

The toggle button is now a language menu, a native select that lists each
language by its own name, and Russian (ru-RU) is the third locale with a
complete translation of every message.

Tests require every locale to have exactly the message shape of the default
locale with no empty text, and cover the cookie attributes and host
normalization. Verified locally: prettier, eslint, type check, tests, the
production build, and a browser run on the apex and ViGet hosts where the
language changed with no navigation and the scroll position kept.

Move the ViGet package and DSL-plugin catalogs into Progmaweb as host-aware Next.js routes, add complete en-US and German content, persistent light and dark themes, catalog-specific metadata, robots and sitemap responses, and an Nginx ownership contract for viget.progmasoft.com.

2026-09-09T17:28:06+00:00

Harden Progmaweb identity, localization, and operations

2026-09-07T18:31:05+00:00

Adopt Patent Grant 1.1, make the apex host canonical while excluding account surfaces from indexing, move the Progmasoft mail boundary into its owning repository, migrate the .NET 10 tests to native MTP, and add persistent light/dark and en-US/de-DE preferences across corporate and account experiences.

Establish Progmasoft copyright ownership across the corporate website and account service, license all project-owned sources under AGPL-3.0-or-later, add the shared defensive Progmasoft patent grant with SPDX and REUSE coverage, preserve source-availability obligations, and align notices, npm and .NET package metadata, frontend, API, tests, deployment configuration, and repository documentation

2026-08-29T08:01:02+00:00

Preserve the canonical account host across the internal Next.js rewrite by preferring the trusted X-Forwarded-Host value supplied by the dedicated Nginx proxy. This prevents the rewritten /account request from being misclassified as a corporate localhost request and eliminates the account root redirect loop while retaining the public-host isolation rule. Verified Prettier, ESLint, route generation, TypeScript, and the production frontend build.

2026-08-28T20:55:52+00:00

Activate the account.progmasoft.com production host with dedicated HTTP and TLS virtual servers, ACME-compatible certificate routing, security headers, and loopback proxy forwarding. Correct the host-aware Next.js account landing rewrite so public HTTPS termination at Nginx does not cause the HTTP-only Next listener to receive an invalid TLS connection. Verified formatting, ESLint, generated route types, TypeScript checks, production frontend build, live Nginx syntax, Cloudflare DNS publication, and the expanded Let's Encrypt SAN set.

2026-08-28T20:50:19+00:00

Initialize Progmaweb 1.0.0 corporate and account platform: add a responsive Next.js corporate site without Visual X# compiler-pipeline content, host-aware account routes, registration and dashboard UX, an ASP.NET Core authentication API with account policies, password hashing, secure sessions, rate limiting and security headers, integration tests on Microsoft Testing Platform, locked dependency graphs, reproducible local orchestration, and separate frontend, backend and security workflows.

2026-08-28T20:03:57+00:00