feat(site): replicate config by id + standby fetch (kills the intra-site frame trap)

src/ZB.MOM.WW.ScadaBridge.SiteRuntime/Actors/DeploymentManagerActor.cs

@@ -498,9 +498,13 @@ public class DeploymentManagerActor : ReceiveActor, IWithTimers
     /// </summary>
     private void HandleRefreshFetched(RefreshFetched msg)
     {
+        // Carry the central fetch coordinates on the apply DTO so they survive the whole
+        // apply path (including the PendingRedeploy buffer) down to ApplyDeployment, where
+        // they are replicated to the standby as an id-only notify-and-fetch message.
         var command = new DeployInstanceCommand(
             msg.Cmd.DeploymentId, msg.Cmd.InstanceUniqueName, msg.Cmd.RevisionHash,
-            msg.ConfigJson, msg.Cmd.DeployedBy, msg.Cmd.Timestamp);
+            msg.ConfigJson, msg.Cmd.DeployedBy, msg.Cmd.Timestamp,
+            msg.Cmd.CentralFetchBaseUrl, msg.Cmd.FetchToken);
         HandleDeploy(command, msg.ReplyTo);
     }
 
@@ -560,10 +564,15 @@ public class DeploymentManagerActor : ReceiveActor, IWithTimers
             await _storage.ClearStaticOverridesAsync(instanceName);
             await _storage.ClearNativeAlarmsForInstanceAsync(instanceName);
 
-            // Replicate to standby node
+            // Replicate to standby node — notify-and-fetch: send only the deployment id +
+            // central fetch coordinates (NOT the config JSON). The standby fetches the
+            // config over HTTP itself, so a large config never crosses the intra-site Akka
+            // hop (which would silently drop on the 128 KB frame trap). When the coords are
+            // absent (deploy paths other than RefreshDeployment), the standby fetch is a
+            // no-op miss and T18 reconciliation is the durable backstop.
             _replicationActor?.Tell(new ReplicateConfigDeploy(
-                instanceName, command.FlattenedConfigurationJson,
-                command.DeploymentId, command.RevisionHash, true));
+                instanceName, command.DeploymentId, command.RevisionHash, true,
+                command.CentralFetchBaseUrl ?? "", command.FetchToken ?? ""));
 
             return new DeployPersistenceResult(
                 command.DeploymentId, instanceName, true, null, sender, isRedeploy);