Merge stream L (proto reserved/propagation comments + regen, stale docs, gateway test gaps)

clients/dotnet/README.md

@@ -170,7 +170,7 @@ the active alarms the gateway's central monitor currently holds),
 keyed by the same monitor), and `AcknowledgeAlarmAsync` (acknowledges as
 the operator: the gateway authenticates `OperatorUser`/`OperatorPassword` and
 writes the comment to the alarm's `AckMsg`, so the Historian records the
-operator). All three accept a cancellation
+operator). The operator's full name is not sent by the client and is not propagated to MXAccess (`operator_full_name` on the worker commands is accepted but ignored); the Historian takes it from the authenticated Galaxy account. All three accept a cancellation
 token and pass through the `MxGateway:Alarms` configuration on the
 server — when alarms are disabled, the gateway returns an empty list / empty
 stream rather than failing.

clients/go/README.md

@@ -167,7 +167,7 @@ snapshots, `Client.StreamAlarms` for the server-streaming feed, and
 operator's Galaxy credentials (`OperatorUser` required, `OperatorPassword`,
 optional `OperatorDomain`) so the gateway authenticates as the operator and the
 Historian records that operator; an empty password is allowed, and the password
-is scrubbed from any returned error. The streaming
+is scrubbed from any returned error. The operator's full name is not sent by the client and is not propagated to MXAccess (`operator_full_name` on the worker commands is accepted but ignored); the Historian takes it from the authenticated Galaxy account. The streaming
 call returns a `StreamAlarmsClient`; cancel its context to terminate the
 stream. All three pass straight through to the gateway's central alarm
 monitor.

clients/java/README.md

@@ -142,7 +142,7 @@ yields alarm-feed messages from the gateway's central monitor), and
 The ack carries operator credentials: `operator_user` is required, and
 `operator_password` / `operator_domain` let the gateway authenticate as that
 operator so the Historian records the real operator. An empty password is
-allowed. The password is scrubbed from exceptions the client throws. Close the subscription to cancel the underlying gRPC stream.
+allowed. The password is scrubbed from exceptions the client throws. The operator's full name is not sent by the client and is not propagated to MXAccess (`operator_full_name` on the worker commands is accepted but ignored); the Historian takes it from the authenticated Galaxy account. Close the subscription to cancel the underlying gRPC stream.
 
 `ActiveAlarmSnapshot.getFromTruncatedSnapshot()` reports that the record came
 from a provider fetch which hit the per-fetch cap: the snapshot set may omit

clients/python/README.md

@@ -116,7 +116,7 @@ comment). The ack is made as the operator: set `operator_user` (required) and
 `operator_password` (may be empty) and optionally `operator_domain` on
 `AcknowledgeAlarmRequest`. The gateway authenticates the operator and writes the
 comment to the alarm's `AckMsg`, so the alarm history records the operator. The
-password is redacted from any raised error.
+password is redacted from any raised error. The operator's full name is not sent by the client and is not propagated to MXAccess (`operator_full_name` on the worker commands is accepted but ignored); the Historian takes it from the authenticated Galaxy account.
 
 Cancel the surrounding task or `aclose()` an alarm iterator to terminate the
 stream.

clients/rust/README.md

@@ -127,7 +127,7 @@ returns an `AlarmFeedStream` async stream of alarm-feed messages and
 shares the gateway's central alarm monitor with every other client.
 `acknowledge_alarm` requires `operator_user` and carries `operator_password` (may be
 empty) and `operator_domain`; the gateway authenticates as that operator so the Historian
-records them. The password is scrubbed from any returned error's `Display`/`Debug`.
+records them. The operator's full name is not sent by the client and is not propagated to MXAccess (`operator_full_name` on the worker commands is accepted but ignored); the Historian takes it from the authenticated Galaxy account. The password is scrubbed from any returned error's `Display`/`Debug`.
 
 The `from_truncated_snapshot` field on `ActiveAlarmSnapshot` reports that the record came from
 a provider fetch which hit the per-fetch cap: the snapshot set may omit active