diff --git a/tests/Drivers/ZB.MOM.WW.OtOpcUa.Driver.Sql.IntegrationTests/SqlServerReadTests.cs b/tests/Drivers/ZB.MOM.WW.OtOpcUa.Driver.Sql.IntegrationTests/SqlServerReadTests.cs
index c258ff6b..c3fe2e99 100644
--- a/tests/Drivers/ZB.MOM.WW.OtOpcUa.Driver.Sql.IntegrationTests/SqlServerReadTests.cs
+++ b/tests/Drivers/ZB.MOM.WW.OtOpcUa.Driver.Sql.IntegrationTests/SqlServerReadTests.cs
@@ -322,8 +322,16 @@ public sealed class SqlServerReadTests
     /// <summary>
     ///     A cancelled poll propagates <see cref="OperationCanceledException"/> rather than publishing
     ///     Bad-quality snapshots: the engine asked the poll to stop and nobody is waiting for values. The
-    ///     asymmetry with a deadline breach (which DOES publish BadTimeout) is deliberate, so it is pinned
-    ///     here against the real provider's cancellation path.
+    ///     asymmetry with a deadline breach (which DOES publish BadTimeout) is deliberate.
+    ///     <para><b>What this proves, precisely.</b> The token is <em>already</em> cancelled before
+    ///     <c>ReadAsync</c> is called, so the cancellation is observed at the reader's first checkpoint —
+    ///     <c>SemaphoreSlim.WaitAsync(_, token)</c> — <b>before any <c>SqlConnection</c> opens</b>. It
+    ///     therefore does <b>not</b> exercise <c>Microsoft.Data.SqlClient</c>'s in-flight cancellation of a
+    ///     running command; that is left to the blackhole gate's deadline path
+    ///     (<c>SqlBlackholeTimeoutTests</c>). What it pins is the driver-shell contract that a cancelled
+    ///     token surfaces as an <see cref="OperationCanceledException"/> and is <b>never</b> swallowed into
+    ///     a Bad snapshot or misread as an unreachable-database verdict — an offline-equivalent guarantee,
+    ///     run here over the real provider only to keep it beside its siblings.</para>
     /// </summary>
     [Fact]
     public async Task ReadAsync_realSqlServer_cancelledTokenPropagatesRatherThanBadCoding()