A failed Google callback has returned the visitor to /login?google=failed since the previous release, but nothing recorded why: a declined consent, an expired or missing state cookie and a forged request all looked the same, and the log of the service held no entry at all. GoogleSignInFailure now handles OnRemoteFailure. It writes one warning, event GoogleSignInFailed (id 5), with the cause: the error code Google reported, such as access_denied, or the reason the handler refused the callback, such as "The oauth state was missing or invalid." An error code is written only when it is a short run of letters, digits, '_', '-' and '.'; anything else from the query string is written as an unrecognized error. The authorization code, the state and tokens are never logged. The redirect is unchanged. Four new tests cover the entry, the redirect, an unusual error value and a refused state. The account API document describes the log entry.
A Google callback that could not finish ended in an unhandled 500: a visitor who declined on Google's consent screen, a callback whose state cookie had expired, and a direct request to the callback path all got an empty error page. The account API document already promised a redirect to /login?google=failed for a failed callback; the handler of the Google scheme now does that through OnRemoteFailure. Three new tests cover a callback without state, a declined consent and a forged state. Three statements no longer matched the sites: - the bug report template still named the catalog paths without the language and the build system; they are /langs/tala/<Publisher>/<Name>/ and /dslplugins/tazel/<Publisher>/<Name>/; - the operations guide placed Tala content on xsharp-lang.xyz, which only redirects to tala.run now; - the architecture guide described the ViGet routing before the catalogs per language and build system: it now gives the rewrites of /langs/tala and /dslplugins/tazel, the redirects of /langs and /dslplugins, three indexed ViGet pages and a sitemap with the home page and both catalogs.
.com has no HSTS requirement of its own, but progmasoft.com is served as if it had one: - Every HTTPS server block of progmasoft.com, www, account and viget sends max-age=63072000; includeSubDomains; preload. The www redirect sent none before. - Plain HTTP only answers the ACME challenge and otherwise redirects to HTTPS, now with a permanent 308 instead of 301. - The API's own HSTS policy, which it adds to HTTPS responses outside development, carries the same values, so a proxied response never shows two different policies. A test checks the header.
The account API kept everything in the memory of its process, so every restart and every deployment of the API deleted all accounts and signed everyone out. PostgresAccountStore implements IAccountStore on PostgreSQL through Npgsql. The three uniqueness rules are unique constraints, so two requests that race for one name, address or Google identity are decided by the database. A refused account is an ordinary answer, not an exception, and the rules are reported in the order the in-memory store reports them. A session refers to its account, and a session of an account that is not stored is refused; the in-memory store now refuses it as well. The schema is a list of numbered steps. The service takes the missing ones when it starts, in one transaction under an advisory lock, and does not start when the database cannot be reached or is newer than the release. /health answers 503 while the database does not answer. ConnectionStrings:Accounts selects PostgreSQL. A production service that is given no database does not start; keeping accounts in memory there has to be asked for with Accounts:Store=Memory. Development and the tests keep the in-memory store by default. The store gains RemoveExpiredSessionsAsync, and a background service calls it at the start and once an hour: a session whose token is never presented again no longer keeps its row for ever. PostgreSQL keeps a timestamp to the microsecond. The store cuts a moment to that precision and returns what it stored, and the service uses the returned account, so the creation time in the registration response equals the one every later read returns. Tests. AccountStoreContractTests states the rules once and runs them on both stores. Further tests cover the schema steps applied concurrently and a database that is too new, the choice of the store from the configuration, the removal of expired sessions, and an account with its session surviving a restart of the service over HTTP. The PostgreSQL tests read their database from PROGMAWEB_TEST_POSTGRES and work in a schema of their own each. Without the variable they are skipped; CI starts PostgreSQL 16 for them, and a test fails the run when the variable is missing there. Operations. ops/README.md describes the database: the Unix socket with peer authentication, so that no password exists, the one-time preparation, and rollback across a schema step. The service unit starts after PostgreSQL. docs/LIMITATIONS.md no longer lists the in-memory store and now lists the missing backup and the missing deletion of accounts.
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.
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.