docs(comments): correct 7 stale 'later task/milestone' comments (stillpending §9)

src/Server/ZB.MOM.WW.OtOpcUa.Runtime/Drivers/DriverHostActor.cs

@@ -41,8 +41,10 @@ namespace ZB.MOM.WW.OtOpcUa.Runtime.Drivers;
 /// <item><c>Stale</c> — ConfigDb unreachable on bootstrap. Background reconnect loop tries to advance.</item>
 /// </list>
 ///
-/// Children (DriverInstance/VirtualTag/etc.) are spawned in Phase 6 follow-up tasks (41-44).
-/// For now the dispatch handler treats the apply as a no-op and writes the ACK back.
+/// Children (DriverInstance/VirtualTag/etc.) are fully wired: <c>DispatchDeployment</c> drives
+/// <see cref="PushDesiredSubscriptions"/> which runs the spawn-plan via <see cref="IDriverFactory"/>,
+/// maintains the <c>FullName→NodeId</c> live-value routing map, and forwards results to the
+/// OPC UA publish actor via <c>ForwardToMux</c>.
 /// </summary>
 public sealed class DriverHostActor : ReceiveActor, IWithTimers
 {

src/Server/ZB.MOM.WW.OtOpcUa.Runtime/OpcUa/OpcUaPublishActor.cs

@@ -243,13 +243,14 @@ public sealed class OpcUaPublishActor : ReceiveActor
             _applier.MaterialiseScriptedAlarms(composition);
             // Equipment-namespace tags get their own pass: ensures each signal's Variable (and any
             // FolderPath sub-folder) exists under its already-materialised equipment folder so
-            // clients can browse them. Live values arrive in a later milestone; until then the
-            // variables show BadWaitingForInitialData.
+            // clients can browse them. Live values are pushed by DriverHostActor.ForwardToMux after
+            // each subscription cycle; variables show BadWaitingForInitialData only until the first
+            // publish interval fires.
             _applier.MaterialiseEquipmentTags(composition);
             // Equipment-namespace VirtualTags get their own pass right after the equipment tags:
             // ensures each computed signal's Variable (and any FolderPath sub-folder) exists under its
-            // equipment folder with a folder-scoped NodeId. The VirtualTagActor fills live values in a
-            // later milestone; until then the variables show BadWaitingForInitialData (same as tags).
+            // equipment folder with a folder-scoped NodeId. VirtualTagHostActor.OnResult pushes live
+            // values once the first dependency update arrives; until then variables show BadWaitingForInitialData.
             _applier.MaterialiseEquipmentVirtualTags(composition);
 
             OtOpcUaTelemetry.OpcUaSinkWrite.Add(1, new KeyValuePair<string, object?>("kind", "rebuild"));