remove unecessary comments

Author: RubenCerna2079

src/Cli.Tests/ValidateConfigTests.cs

@@ -884,12 +884,9 @@ public void TestChildWithEntitiesAndAutoentitiesResolvingZeroLogsNamedWarning()
     }
 
     /// <summary>
-    /// Child config with only autoentities that resolve to >0 entities is valid.
+    /// Child config with only autoentities that resolve to greater than 0 entities is valid.
     /// Simulates the production code path where the metadata provider stores resolution
     /// counts on the root (merged) config rather than on the child config directly.
-    /// This is the regression test for the bug where child-config autoentities caused
-    /// "No entities found" even when they were expanded successfully.
-    /// Covers child truth-table row C5 (DS=1, E=0, AE=1, resolved>0, counts on root).
     /// </summary>
     [TestMethod]
     public void TestChildWithDataSourceAndAutoentitiesResolvingEntitiesIsValid()

src/Core/Configurations/RuntimeConfigValidator.cs

@@ -739,9 +739,8 @@ private void ValidateRootConfig(RuntimeConfig runtimeConfig)
         // Validate each child config independently.
         foreach ((string fileName, RuntimeConfig childConfig) in runtimeConfig.ChildConfigs)
         {
-            // The metadata provider stores autoentity resolution counts on the root (merged)
-            // config. Copy those counts to the child config so per-child validation can find
-            // them. Only copy if the child hasn't already been populated (e.g. in unit tests).
+            // The metadata provider stores autoentity resolution counts on the root config.
+            // Copy those counts to the child config so per-child validation can find them
             foreach (KeyValuePair<string, Autoentity> ae in childConfig.Autoentities)
             {
                 if (!childConfig.AutoentityResolutionCounts.ContainsKey(ae.Key)