docs+test(closeout): final-review reservations — stale ACL prose, worker test gaps, config sample fix

src/ZB.MOM.WW.MxGateway.Server/Alarms/IGatewayAlarmService.cs

@@ -40,11 +40,21 @@ public interface IGatewayAlarmService
 
     /// <summary>
     ///     True when the worker's most recent reconcile fetch hit the provider's
-    ///     per-fetch cap, so <see cref="CurrentAlarms"/> may be missing active
-    ///     alarms. The monitor is otherwise healthy — this is not a fault, it is
-    ///     a completeness caveat, which is why it is separate from
+    ///     per-fetch cap, so the active-alarm set may be missing alarms. The
+    ///     monitor is otherwise healthy — this is not a fault, it is a
+    ///     completeness caveat, which is why it is separate from
     ///     <see cref="State"/> and <see cref="LastError"/>. Cleared by the first
     ///     reconcile whose fetch comes back under the cap.
+    ///     <para>
+    ///     Read it as "as of the last full reconcile, the fetch was capped", not as
+    ///     a property of a particular <see cref="CurrentAlarms"/> array: the two are
+    ///     separate reads, and live transitions keep moving the cached set between
+    ///     reconciles. A consumer that reads both — the dashboard poll does — can
+    ///     therefore straddle a reconcile, in which case its caveat describes the
+    ///     adjacent generation and the banner is at worst one poll stale. That is
+    ///     the intended granularity for a completeness hint; pairing them exactly
+    ///     would need a combined accessor this seam deliberately does not have.
+    ///     </para>
     /// </summary>
     bool SnapshotTruncated { get; }