fix: queue readiness barrier after fixture activation

2026-08-04 07:29:37 +03:00
parent 98564b807f
commit 2d9fbdd474
2 changed files with 8 additions and 8 deletions
@@ -199,13 +199,13 @@ internal sealed class FirstLimitedApplyAutomationCoordinator
            // coordinator receives the returned Document. Confirm the current
            // active document after assignment so that one missed event cannot
            // strand the workflow waiting for another startup Idle.
-            var activeDocument = AcadApplication.DocumentManager.MdiActiveDocument;
-            if (activeDocument is not null && string.Equals(activeDocument.Name, document.Name, StringComparison.OrdinalIgnoreCase))
-            {
-                fixtureDocumentActivated = true;
-                transitions.Add("FixtureDocumentActiveAfterOpen");
-                QueueReadinessBarrier();
-            }
+            // Open was requested for this exact local fixture and it has just
+            // been made MDI-active. Queue a no-op public command regardless of
+            // wrapper identity/name normalisation; CommandEnded is the actual
+            // readiness proof before any Plant API is used.
+            fixtureDocumentActivated = true;
+            transitions.Add("FixtureDocumentActiveAfterOpen");
+            QueueReadinessBarrier();
        }
        catch (System.Exception ex) { FailFromCallback("Start", ex, "AUTOMATION_START_FAILED"); }
    }