fix(abcip): ALMA review round 2 - IsRestatement contract docs, ALMD no-InAlarm warning, un-ack retrigger

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

src/Core/ZB.MOM.WW.OtOpcUa.Core.Abstractions/IAlarmSource.cs

@@ -107,8 +107,12 @@ public sealed record AlarmAcknowledgeRequest(
 ///     watched happen: a reconnect snapshot entry (Galaxy) or the first event for a condition after a driver start or
 ///     deploy respawn (OpcUaClient). It governs <b>history only, never node state</b>: the host still projects the
 ///     state, but writes no <c>alerts</c> row when the re-statement changes nothing the condition shows (a Retrigger on
-///     an Active+unacked condition with the same message and severity; a Clear on an already-inactive condition).
-///     <c>false</c> (the default, every source that does not opt in) keeps every transition's row.
+///     an Active+unacked condition with the same message and severity; a Clear on an already-inactive condition) — or
+///     when a flagged <see cref="AlarmTransitionKind.Unspecified"/> update moves the message/severity of an
+///     already-active condition (node updated, one condition event, active/acked kept, no row). AbCip ALMA sets the
+///     flag for the last shape (the governing limit changed, no new occurrence); OpcUaClient's first sight of an
+///     inactive condition after a respawn can reach it too. <c>false</c> (the default, every source that does not
+///     opt in) keeps every transition's row.
 /// </param>
 public sealed record AlarmEventArgs(
     IAlarmSubscriptionHandle SubscriptionHandle,