feat(grpc): PSK-authenticate the site gRPC control plane; drop the vestigial management receptionist registration

Phase 0 of the ClusterClient→gRPC migration
(docs/plans/2026-07-22-clusterclient-to-grpc-plan.md). Standalone hardening: it
closes a gap that exists today and is a precondition for moving command/control
onto gRPC in later phases.

T0.1 — delete the ManagementActor ClusterClientReceptionist registration.
It was built for an out-of-cluster CLI that was never written: the shipped CLI
speaks HTTP Basic to /management, which asks the actor in-process through
ManagementActorHolder. Nothing in the repo ever sent to /user/management. The
actor still runs there; only the cross-boundary advertisement is gone. Six
documents claimed the CLI used ClusterClient — including the CLI's own README
"Architecture Notes" — and are corrected here rather than left to rot.

T0.2 — record, do not port, the dead integration-routing path.
IntegrationCallRequest is unwired at BOTH ends: RouteIntegrationCallAsync has
zero callers anywhere, and RegisterLocalHandler(Integration, …) appears only in
a test, so production always answers "Integration handler not available". It is
excluded from the gRPC contract (28 of 29 commands migrate) rather than
enshrined on an additive-only wire format, and deleting it during a
transport migration would mix a behavioural change into a change whose whole
value is that behaviour is identical. See
docs/known-issues/2026-07-22-integration-call-routing-is-dead-code.md.

T0.3 — preshared-key authentication on SiteStreamService.
The service shipped with no auth at all: plaintext h2c, no interceptor, so
anything that could reach a site node's :8083 could open a live data stream or
read audit rows back via PullAuditEvents/PullSiteCalls. ControlPlaneAuthInterceptor
now gates /sitestream.SiteStreamService/ — modeled on LocalDbSyncAuthInterceptor
(constant-time compare, fail-closed, PermissionDenied) but gating a SET of
service prefixes so phases 1A/1B add services rather than interceptors. LocalDb
sync keeps its own separate key: it authenticates the pair partner, not central,
and collapsing the two would make a site's central-facing key also admit writes
into its database.

Keys are per site (SB-GRPC-PSK-<siteId>), never fleet-wide, so a compromised
site yields only its own. Central attaches them through ControlPlaneCredentials,
which binds CallCredentials to the channel — covering unary and streaming
uniformly, and letting the key resolve asynchronously, which a client
interceptor could not do without blocking. All three central→site channel
creation sites go through it (SiteStreamGrpcClient and both audit pull invokers);
the pull invokers' channel caches are re-keyed by (site, endpoint) because
credentials are per-site and bound to the channel.

Two decisions beyond the plan:

  * StartupValidator now requires GrpcPsk on Site nodes. The plan specified only
    the runtime gate, but fail-closed with no boot check produces a node that
    joins, answers heartbeats and reports healthy while refusing every stream,
    audit pull and telemetry ingest — silent and total. Same reasoning as the
    existing inbound API-key pepper rule.

  * Added Communication:SitePsks as a central-side key map. The plan assumed
    central would read the store, seeded via a dev KEK; the docker rig
    deliberately boots with no master key, so store-only resolution would leave
    it unable to dial its own sites. The store stays primary — it is the only
    source that can serve a site added at runtime — with the map covering
    key-less hosts and one-off pins. Neither source falling back to
    "unauthenticated" is the invariant.

T0.4 — dev keys on both rigs and tests.
34 tests. The seven that matter most exercise a real in-process gRPC stack over
TestServer: the unit tests on either side of the wire would both stay green if
the halves disagreed, and gRPC refuses call credentials on a plaintext channel
by default — the UnsafeUseInsecureChannelCallCredentials opt-in is only provable
by making a real call. They confirm correct key passes on unary AND streaming,
wrong key and no-credentials both get PermissionDenied, and an unresolvable key
fails the call with nothing reaching the service.

OPERATIONAL: a site node upgraded to this build without a key will not boot.
That includes the gitignored deploy/wonder-app-vd03/ overlay.

src/ZB.MOM.WW.ScadaBridge.Communication/CommunicationOptions.cs

@@ -41,6 +41,54 @@ public class CommunicationOptions
     /// </summary>
     public List<string> CentralContactPoints { get; set; } = new();
 
+    /// <summary>
+    /// Preshared key authenticating this node's gRPC control plane — the site↔central
+    /// boundary. On a site node this is the key its inbound gate
+    /// (<c>ControlPlaneAuthInterceptor</c>) expects on every <c>SiteStreamService</c> call, and
+    /// which central must present; central resolves the matching value per site from its own
+    /// secret store under the name <c>SB-GRPC-PSK-{siteId}</c>.
+    /// </summary>
+    /// <remarks>
+    /// <para>
+    /// In production this is supplied as <c>${secret:SB-GRPC-PSK-&lt;siteId&gt;}</c> and expanded
+    /// out of the secrets store before the host is built, so the plaintext never sits in
+    /// appsettings. Development rigs set a literal, mirroring the LocalDb replication key.
+    /// </para>
+    /// <para>
+    /// <b>Empty means closed, not open.</b> With no key set the interceptor rejects every gated
+    /// call. This is not optional configuration: a node that ships without a key serves no
+    /// streams and no audit pulls.
+    /// </para>
+    /// <para>
+    /// Distinct from <c>LocalDb:Replication:ApiKey</c>, which authenticates the pair partner for
+    /// database replication over the same listener. The two are never shared.
+    /// </para>
+    /// </remarks>
+    public string GrpcPsk { get; set; } = "";
+
+    /// <summary>
+    /// Central-side per-site gRPC preshared keys, keyed by site identifier — the mirror image
+    /// of <see cref="GrpcPsk"/>, which is the single key a site node expects on its own inbound
+    /// gate. An entry here takes precedence over the secret store for that site.
+    /// </summary>
+    /// <remarks>
+    /// <para>
+    /// <b>Why both a config map and a secret store.</b> The store is the primary source and the
+    /// only one that works for the real case: sites are added at runtime from the Central UI, so
+    /// their keys cannot be enumerated in configuration at boot, and <c>SitePskProvider</c>
+    /// resolves <c>SB-GRPC-PSK-{siteId}</c> on demand. This map covers the cases the store
+    /// cannot or should not: a development rig that runs with no master key and injects every
+    /// credential as an environment override, and an operator pinning one site's key without
+    /// touching the store. Values may themselves be <c>${secret:…}</c> references, since a map
+    /// declared in configuration IS enumerable at boot.
+    /// </para>
+    /// <para>
+    /// Absence is not a fallback to "unauthenticated" in either source — a site with no key in
+    /// the map and none in the store cannot be dialed at all.
+    /// </para>
+    /// </remarks>
+    public Dictionary<string, string> SitePsks { get; set; } = new();
+
     /// <summary>gRPC keepalive ping interval for streaming connections.</summary>
     public TimeSpan GrpcKeepAlivePingDelay { get; set; } = TimeSpan.FromSeconds(15);