docs(phase6): AdminUI editors, pickers, deletes, new-script

docs/AlarmTracking.md

@@ -240,6 +240,15 @@ AB CIP ALMD) route to AVEVA Historian via the Wonderware sidecar:
   [AlarmHistorian.md §Configuration](AlarmHistorian.md#configuration)
   for the `AlarmHistorian` appsettings section that enables the real sink.
 
+  **Native alarms** (equipment tags carrying an `"alarm"` object in their `TagConfig`)
+  support the same `HistorizeToAveva` opt-out. The field is `alarm.historizeToAveva`
+  (`bool?`) and is authored via the **"Historize to AVEVA"** checkbox in the Tag modal's
+  alarm section. The gate logic is identical (`is not false`): absent or `true` historizes;
+  explicit `false` suppresses the AVEVA write while leaving the live `/alerts` feed
+  unaffected. See
+  [ScriptedAlarms.md §TagConfig alarm fields](ScriptedAlarms.md#tagconfig-alarm-fields)
+  for the full field reference.
+
 Galaxy-native alarms with `$Alarm*` extensions reach AVEVA Historian
 directly via System Platform's `HistorizeToAveva` toggle on the
 alarm primitive — no involvement from OtOpcUa. This sidecar path is