clients: document StreamAlarms + AcknowledgeAlarm in each README

Each client's README now covers the alarms surface in both the SDK
section (StreamAlarms / AcknowledgeAlarm beside the existing
QueryActiveAlarms entry, with the streaming-cancellation note) and
the CLI examples (stream-alarms / acknowledge-alarm invocations
mirroring the in-tree implementations across .NET, Go, Rust, Python,
and Java).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

clients/python/README.md

@@ -95,6 +95,13 @@ async with await GatewayClient.connect(
 events available for parity tests. `Session` helpers call the method-specific
 MXAccess commands and preserve raw replies on typed command exceptions.
 
+For alarms, the client exposes `GatewayClient.query_active_alarms` (one-shot
+snapshot), `GatewayClient.stream_alarms` (async generator yielding alarm-feed
+messages from the gateway's central monitor), and
+`GatewayClient.acknowledge_alarm` (ack by alarm reference, optional comment
+and ack target). Cancel the surrounding task or `aclose()` the iterator to
+terminate the stream.
+
 Canceling a Python task cancels the client-side gRPC call or stream wait. It
 does not abort an in-flight MXAccess COM call inside the worker process.
 
@@ -191,6 +198,8 @@ mxgw-py register --session-id <id> --client-name python-client --json
 mxgw-py add-item --session-id <id> --server-handle 1 --item Object.Attribute --json
 mxgw-py advise --session-id <id> --server-handle 1 --item-handle 2 --json
 mxgw-py stream-events --session-id <id> --max-events 1 --json
+mxgw-py stream-alarms --session-id <id> --max-messages 1 --json
+mxgw-py acknowledge-alarm --session-id <id> --alarm-reference "\\Galaxy\Area001.Pump001.PumpFault" --json
 mxgw-py write --session-id <id> --server-handle 1 --item-handle 2 --type int32 --value 123 --json
 ```