diff --git a/src/ZB.MOM.WW.ScadaBridge.ConfigurationDatabase/Migrations/20260615171137_ResyncLdapGroupMappingSeed.cs b/src/ZB.MOM.WW.ScadaBridge.ConfigurationDatabase/Migrations/20260615171137_ResyncLdapGroupMappingSeed.cs
index 2eab897c..f236ae99 100644
--- a/src/ZB.MOM.WW.ScadaBridge.ConfigurationDatabase/Migrations/20260615171137_ResyncLdapGroupMappingSeed.cs
+++ b/src/ZB.MOM.WW.ScadaBridge.ConfigurationDatabase/Migrations/20260615171137_ResyncLdapGroupMappingSeed.cs
@@ -12,8 +12,9 @@ namespace ZB.MOM.WW.ScadaBridge.ConfigurationDatabase.Migrations
         /// <c>INSERT OR IGNORE</c> skips the row when the <c>Id</c> primary key already
         /// exists, so replaying this migration against a DB that already carries Id=5
         /// (e.g. one seeded by a newer HasData baseline) is a no-op rather than a PK
-        /// violation. Exposed as a constant so the idempotency test can exercise the
-        /// exact SQL the migration emits on the SQLite branch.
+        /// violation. Kept as a named constant for readability and so the emitted
+        /// SQLite SQL is documented in one place; the idempotency test drives the
+        /// real migration through EF's SQL generator rather than reading this directly.
         /// </summary>
         internal const string SqliteInsertSql =
             "INSERT OR IGNORE INTO \"LdapGroupMappings\" (\"Id\", \"LdapGroupName\", \"Role\") " +