Merge #625: deferred code-review findings resolved or ruled (S7.Cli verdict, browser CP release, Cluster member events, Sql Detach hoist, docs)

Claude-Session: https://claude.ai/code/session_01Ef2ozxS7QPanGT8uoATbTe

src/Server/ZB.MOM.WW.OtOpcUa.OpcUaServer/HistoryPaging.cs

@@ -191,7 +191,13 @@ internal static class HistoryPaging
     /// <param name="skip">How many ties at <paramref name="boundaryT"/> were already emitted on prior pages.</param>
     /// <param name="cap">The client's per-page cap (<c>NumValuesPerNode</c>); must be &gt; 0 to make progress.</param>
     /// <param name="boundaryT">The single SourceTimestamp every tie in the cluster shares.</param>
-    /// <param name="endUtc">The (inclusive) upper bound of the read window; unchanged across pages.</param>
+    /// <param name="endUtc">The (inclusive) upper bound of the read window; unchanged across pages.
+    ///     OpcUaServer-003, accepted by design: the backend contract
+    ///     (<c>IHistoryProvider.ReadRawAsync</c>) treats <c>endUtc</c> as EXCLUSIVE, so the
+    ///     <c>next &lt;= endUtc</c> test here is deliberately the conservative side — at worst one extra
+    ///     empty resume page (<c>[endUtc, endUtc)</c> → GoodNoData, no continuation point), never a
+    ///     dropped or duplicated sample. Tightening to <c>&lt;</c> would be correct only if the live
+    ///     backend's boundary is confirmed exclusive; it is not worth the opposite off-by-one risk.</param>
     /// <param name="sliceStart">The index into the cluster the emitted slice starts at (clamped to the count).</param>
     /// <param name="sliceCount">How many ties the emitted slice contains (may be <c>0</c> on a stale-skip self-heal).</param>
     /// <param name="nextStartUtc">The next page's inclusive start: <paramref name="boundaryT"/> while the