progmaweb/ops, branch 1.0.0The site and account service of Progmasoft: a Next.js frontend and an ASP.NET Core API.Add secure Google sign-in to Progmasoft Account. Use the server-side authorization-code flow with an exact account-domain callback, temporary hardened external cookies, verified provider email matching, canonical Account-name creation for new users, and no separate ViGet publisher identity. Add frontend entry points, provider failure guidance, locked Google authentication dependencies, service secret injection, and backend regression coverage without committing OAuth credentials.2026-08-30T18:45:01+00:00Leitwolf112026-08-30T18:45:01+00:0076c4c1876a86dbca0adf86750362b3581d6fc69d
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 documentation2026-08-29T08:01:02+00:00Leitwolf112026-08-29T08:01:02+00:00c8073a82bbc8d39d8a45334bdcd969d00a3c3f1c
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:00Leitwolf112026-08-28T20:50:19+00:001ce38648d6e987aaaa06d7d4fff461ef862f9a93
Complete production activation hardening: allow the explicit loopback and canonical Progmasoft hosts used by the Next.js API proxy, and omit MemoryDenyWriteExecute only for the CoreCLR service because the .NET JIT requires managed executable mappings while all other systemd protections remain enabled.2026-08-28T20:38:41+00:00Leitwolf112026-08-28T20:38:41+00:00f92a585d831c8c0304073d2c518bc393957d7ac6
Correct the production Next.js service path for pnpm monorepo standalone output: run the generated apps/web/server.js beneath the preserved standalone module root and document the matching static-asset placement.2026-08-28T20:21:59+00:00Leitwolf112026-08-28T20:21:59+00:00ff60d2a07a245dc7d709b2fba121371a83c8ca99
Separate Progmasoft production hosting from Visual X#: enable portable Next.js standalone output, add hardened loopback-only systemd services for the frontend and account API, define dedicated TLS Nginx virtual hosts with canonical www redirection and ACME handling, document immutable release activation and rollback, and remove workstation-specific tool paths from orchestration.2026-08-28T20:21:06+00:00Leitwolf112026-08-28T20:21:06+00:00c53ae2482c50b2c29abb0d5ebef5343a80b9b705