progmaweb/README.md, 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
Make the Progmasoft Account name the explicit ViGet publisher identity. Show the exact shared name in account discovery and dashboard views, document that ViGet does not create a second publisher identity, and retain case-preserving canonical account coordinates.2026-08-30T14:38:34+00:00Leitwolf112026-08-30T14:38:34+00:00c89a3f20a0f477573c41b831d993850e0adb30e7
Align Progmasoft account navigation with the canonical ViGet domain. Document account.progmasoft.com/<Account>/dashboard as the stable account dashboard route and update company and account surfaces to link to viget.progmasoft.com instead of the retired xsharp-lang.xyz registry host.2026-08-30T14:23:01+00:00Leitwolf112026-08-30T14:23:01+00:003cc73dd3c681e5e25d9a2d0fda7bd34cd18e91f7
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
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:00Leitwolf112026-08-28T20:03:57+00:0018da54ce240b1bfefce36aa2ec3b44b58bd0dbde