Makes the application say what it is doing and when it fails

U4. Console logging plus Sentry, a same-origin tunnel so ad blockers cannot
silence browser errors, Umami on the admin SPA, and six security events that
alert rules can actually be built on.

The correlation id is the W3C trace id from the ambient Activity, enabled by
one line of ActivityTrackingOptions so every entry from every category carries
it without touching a call site. It propagates across the master/slave
boundary via traceparent, which TraceIdentifier cannot do at all, and it is
the same value ProblemDetails already returns to the browser.

The security events use source-generated LoggerMessage with constant
templates. Sentry groups log events by message, so interpolating an email
address would give every address its own issue and "more than 20 failed
logins in five minutes" could never fire — the events would arrive, be
visible, be tagged, and the alerting would silently be impossible. A test
asserts the rendered message is identical across argument values.

Scrubbing happens in-process, before transmission, and covers Set-Cookie as
well as Cookie: the login response issues the refreshToken there, so
scrubbing only the request side would protect nothing. Transactions are
scrubbed too, because they carry request data and are the channel nobody
thinks of.

The tunnel derives its destination from the DSN once at startup and reads
nothing from the request, which is what separates a tunnel from a
server-side request forgery primitive. Size is capped by a bounded read
rather than by trusting Content-Length, and the endpoint is rate limited.

Two things found along the way. Zod 4's url() hands the value to the URL
constructor, which accepts any scheme — so the existing frontend validation
would have accepted the exact "htp://" typo BR-U4-24 names, and the SPA
would have called a nonexistent origin. Now constrained to http(s). And the
new appsettings comments are verified against the real configuration
provider, because the failure mode if it rejected them is both hosts
refusing to start after a release switch.

One deviation. IAdminTokenValidator was meant to gain a reason-reporting
overload; implemented that way, a substitute returning false by default
silently inverted the access decision while both methods compiled. Two
methods whose difference is invisible at the call site is the defect, so it
is now a single Validate returning AdminTokenResult.

Touches two files from already-committed units: DatabaseMigrationExtensions
(U2) gains a flush before the rethrow, or the one Critical event in the
system dies with the process; AdminTokenValidator (U1) classifies why a
bypass was refused.

Build 0 errors; 366 backend tests pass, up from 315, and 237 frontend tests,
up from 213. tsc clean, eslint clean on every changed file.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HHoJpxYXzHACSQguHrC5fw

frontend/src/vite-env.d.ts

@@ -1,15 +1,30 @@
 /// <reference types="vite/client" />
 
 interface ImportMetaEnv {
-    /** Base URL of the SlpModularCms .NET API (e.g. http://localhost:5000). */
-    readonly VITE_API_BASE_URL: string;
+    /**
+     * Base URL of the SlpModularCms .NET API. Absent or empty means same-origin, which is the
+     * production configuration: the API and this SPA are served by one process. Set explicitly
+     * for local development (e.g. https://localhost:7221 for master, :7222 for slave).
+     */
+    readonly VITE_API_BASE_URL?: string;
     /** Set to 'true' to run the MSW mock backend in the browser during dev. */
     readonly VITE_ENABLE_MSW?: string;
     /** Browser tab title; lets local master/slave dev instances be told apart. Defaults to "SlpModularCms". */
     readonly VITE_APP_TITLE?: string;
+    /** Sentry DSN for client-side error reporting. Not a secret — it ships in the bundle. Absent means Sentry is skipped. */
+    readonly VITE_SENTRY_DSN?: string;
+    /** Build-time environment tag ('test' | 'production'). Both use `vite build`, so MODE alone cannot tell them apart. */
+    readonly VITE_APP_ENV?: string;
+    /** Self-hosted Umami tracking script URL, e.g. https://analytics.example.com/script.js */
+    readonly VITE_UMAMI_SCRIPT_URL?: string;
+    /** Umami website ID, created per environment in the Umami dashboard. */
+    readonly VITE_UMAMI_WEBSITE_ID?: string;
     // Add future typed env flags here.
 }
 
 interface ImportMeta {
     readonly env: ImportMetaEnv;
 }
+
+/** App version at build time (from package.json), injected via vite.config.ts `define`. Used as the Sentry `release` tag. */
+declare const __APP_VERSION__: string;