Run Re-Do

Assets/_Project/Scripts/Server/World/ThreatDirectorSystem.cs

@@ -11,8 +11,9 @@ namespace ProjectM.Server
     /// Server-only composite ThreatDirector — the data-driven base-attack SCHEDULER. It owns the decision of WHEN
     /// and HOW BIG a siege is; <see cref="CyclePhaseSystem"/> owns the Calm↔Siege transition. The single documented
     /// hand-off is <see cref="ThreatState.PendingSiegeSize"/> (this system sets it; CyclePhaseSystem consumes it).
-    /// This slice wires ONE source — POST-EXPEDITION retaliation: a player returning to base (counted as
-    /// <see cref="ThreatState.PendingReturns"/> by <see cref="ExpeditionGateSystem"/>) arms a siege of
+    /// This slice wires ONE source — POST-EXPEDITION retaliation: a completed RUN (banked on the boss-clear
+    /// return by <see cref="RunDirectorSystem"/> into <see cref="ThreatState.PendingReturns"/> — the retired
+    /// walk-in ExpeditionGateSystem's carry, Step 11) arms a siege ofe of
     /// <see cref="ThreatConfig.SizeBase"/> Husks after a <see cref="ThreatConfig.PostExpeditionDelayTicks"/>
     /// telegraph. The Heat/Schedule sources are reserved (config baked-but-inert) so they drop in additively with
     /// no re-bake. It also enforces a BOUNDED siege lifetime (<see cref="ThreatConfig.SiegeTimeoutTicks"/>): an
@@ -24,7 +25,7 @@ namespace ProjectM.Server
     [BurstCompile]
     [WorldSystemFilter(WorldSystemFilterFlags.ServerSimulation)]
     [UpdateInGroup(typeof(SimulationSystemGroup))]
-    [UpdateAfter(typeof(ExpeditionGateSystem))]
+    [UpdateAfter(typeof(RunDirectorSystem))]
     [UpdateBefore(typeof(CyclePhaseSystem))]
     public partial struct ThreatDirectorSystem : ISystem
     {