With an empty Google client identifier or secret the API answered every request with 500, including registration, password sign-in and the status route. The Google scheme was always registered, and the authentication middleware initializes every remote scheme for each request; with empty credentials the validation of the Google options threw there, before any endpoint ran. The API could not be started locally without credentials, and the "Google sign-in is unavailable" answer of the start endpoint was never reached. The Google scheme is now registered only when both values are configured. Without it the service runs normally, the start endpoint answers 503, the completion endpoint redirects to the failed sign-in page without a session, and the callback path is not a route. With both values nothing changes. The test factory passes the two values as host settings. The program makes the decision while it registers services, and configuration sources a test factory adds are applied only when the host is built, after that point. New tests run the service without a Google client: the ordinary routes, a full register, sign-out and sign-in round trip, and the three Google paths. They failed with 500 against the previous program and pass now, also when the environment of the test run carries Google credentials. The guides no longer list this as a limitation or ask for placeholder credentials. Deploying this change restarts the API, which deletes every account while the store is in memory.
The DocFX gate only failed on a broken link or an unresolved reference. DocFX does not report a declaration without a comment, and the API had none, so the gate passed over a reference with no descriptions at all. The gate now has three parts: - DocFX still builds the reference with warnings as errors. - The API project compiles its XML documentation. With warnings as errors already on, an undocumented public declaration or a wrong cref now fails the build. - docs/api/CheckDocumentation.cs reads the metadata DocFX generated and fails when a namespace, type or member has no summary. This covers internal and private members, which the compiler does not check. It runs as a file-based .NET program, so the gate needs no tool beyond the SDK. It refuses to pass when the metadata is missing or defines nothing. To satisfy the gate, every declaration of apps/api has documentation comments, 131 reference items in all, and the two namespaces are described by overwrite files in docs/api/namespaces. Only comment lines were added to the C# sources; no statement changed. docs/api/filterConfig.yml leaves generator-written code out of the reference: the generated regular-expression namespace, and the one partial method whose generated half replaces the comment of its declaration. Verified locally: the solution builds with no warnings, the 23 API tests pass, DocFX builds with no warnings and the coverage check passes. Removing one summary and one namespace file made the check fail and name both.
Invoke the framework-dependent API through the installed dotnet runtime instead of relying on a copied apphost inode retaining executable SELinux metadata. Document the production service contract so immutable releases activate consistently on the AlmaLinux host.
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.