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

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

docs/drivers/AbCip.md

@@ -271,6 +271,8 @@ routes native transitions on) and `Kind` = `Raise` / `Clear`. Before Gitea #641
 **ALMD's active bit is `InAlarm`** (Rockwell's ALMD reference). Until hw4 the projection polled `InFaulted`, which
 is the *input-health* flag (Status.1, set when the program raises `InFault`), so a live ALMD would have raised on
 input faults and never on the alarm itself. Declare `InAlarm` (and `Severity`) on an ALMD tag.
+**Migration:** a tag that declared `InFaulted` but not `InAlarm` now never raises (the `InAlarm` read is
+`BadNodeIdUnknown`); the projection logs a once-per-tag Warning at subscribe — add `InAlarm` to the tag's members.
 
 ### ALMA (analog alarms)
 
@@ -294,7 +296,8 @@ layout — leave grouping off for ALMA tags (BOOL members are read member by mem
   instruction's `AckRequired` is false); active→none `Clear`; a limit **newly** entering while active `Retrigger`
   (a new unacknowledged occurrence) — or `ActiveAcknowledged` if nothing is pending ack, never
   Retrigger-then-Acknowledge; every declared `*Acked` bit going true while the condition was unacknowledged
-  `Acknowledge`; a limit dropping out (the governing limit or its severity changes, no new occurrence) an
+  `Acknowledge`; a Good `*Acked` read going false on a fully-acked condition with the same limits active
+  `Retrigger` (an occurrence the poll missed); a limit dropping out (the governing limit or its severity changes, no new occurrence) an
   `Unspecified` event flagged `IsRestatement`, which `NativeAlarmProjector` applies as a text/severity move with
   **no `/alerts` row**. A non-governing limit flickering emits nothing.
 - **"Acked" is judged over every declared limit, active or not.** In Logix an occurrence that returned to normal