feat(mesh): MeshTransportOptions — dark switch between DPS and ClusterClient

Phase 2 Task 0. Binds a validated `MeshTransport` section selecting which transport carries central->node commands, defaulting to Dps so nothing changes until the rig gate passes. The validator exists because every fault it catches otherwise surfaces as an ABSENCE -- a deployment that never arrives, an alarm ack that does nothing -- which has no stack trace and no failing node to point at. Two of the shapes it rejects are ported from the sister project's shipped mistakes: a contact point carrying an actor-path suffix, and (documented in the options XML) a template listing the node's OWN remoting port as a central contact, which is a permanent failure in the initial-contact rotation. Contact points are required only under ClusterClient mode; requiring them under the default would make the section mandatory on admin-only nodes that have no reason to carry them. Sabotage-verified: relaxing the empty-contacts guard and the actor-path-suffix guard turns exactly those two tests red, and nothing else. Claude-Session: https://claude.ai/code/session_01GASWkNEi68FSCtvr6rLoEW
2026-07-22 10:39:37 -04:00
parent 1ec831883c
commit 5439f14804
4 changed files with 288 additions and 0 deletions
@@ -34,6 +34,12 @@ public static class ServiceCollectionExtensions
        services.AddValidatedOptions<AkkaClusterOptions, AkkaClusterOptionsValidator>(
            configuration, AkkaClusterOptions.SectionName);

+        // Per-cluster mesh Phase 2: which transport carries central→node commands. Validated at
+        // startup for the same reason the cluster options are — a contact point that cannot resolve
+        // produces silence, not an error, and silence is indistinguishable from "nothing to do".
+        services.AddValidatedOptions<MeshTransportOptions, MeshTransportOptionsValidator>(
+            configuration, MeshTransportOptions.SectionName);
+
        services.AddSingleton<IClusterRoleInfo, ClusterRoleInfo>();

        return services;