R1.3 GetServerTimeZoneAsync over gRPC (live-verified); R1.4 bounded out on gRPC

Live-probed both R1.3 and R1.4 against a real 2023 R2 server over the gRPC
StatusService; implemented the one that carries an evidence-backed value.

R1.3 GetServerTimeZoneAsync — SHIPPED:
- StatusService.GetSystemTimeZoneName(uiHandle) returns the real server zone
  over RemoteGrpc (the 2020 WCF op is a client-side stub returning empty).
- HistorianGrpcStatusClient.GetSystemTimeZoneNameAsync -> dialect routing ->
  public HistorianClient.GetServerTimeZoneAsync. Non-gRPC transports fail
  closed with ProtocolEvidenceMissingException (no empty-string lie).
- Golden message-shape unit test + non-gRPC guardrail unit test + gated live
  test. 271 unit tests pass.

R1.4 GetHistorianInfoAsync (EventStorageMode) — bounded out on gRPC too:
- gRPC GetHistorianInfo is the same named-value query as 2020 WCF (only
  HistorianVersion resolves); EventStorageMode + 7 variants fail on both
  GetHistorianInfo and GetSystemParameter. The 518-byte struct is filled by a
  native vtable+648 HCAL call, not the gRPC op (per the 2023 R2 decompile), so
  the field is never on the wire. Not shipped on any transport. Closes the
  roadmap's open "build against a live 2023 R2 server" caveat.

Also correct the stale M3 roadmap section: D2 already proved
Transaction.AddNonStreamValues* rides the storage-engine pipe (STransactPipeClient2
-> aaStorageEngine), not WCF — same wall as R4.2 — so M3-over-WCF is blocked, not
"the path that is NOT the gated cache push".

Docs: hcal-roadmap.md, wcf-historian-info.md, wcf-status-localhost.md.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B6mcaT2PjRFKcogzp9UkfC

src/AVEVA.Historian.Client/Grpc/HistorianGrpcStatusClient.cs

@@ -35,4 +35,38 @@ internal static class HistorianGrpcStatusClient
 
         return (response.Status?.BSuccess ?? false) ? response.StrParameterValue : null;
     }
+
+    /// <summary>
+    /// Reads the Historian server's system time-zone name (roadmap item R1.3,
+    /// <c>StatusService.GetSystemTimeZoneName</c>). Unlike the 2020 WCF surface — where the native
+    /// <c>GetSystemTimeZoneName</c> is a client-side stub that returns an empty string — the 2023 R2
+    /// gRPC front door returns the real Windows time-zone display name (live-verified:
+    /// "Eastern Daylight Time"). Takes the transient <c>uint</c> client handle; the response carries
+    /// the value as a protobuf string with no opaque buffer to decode.
+    /// </summary>
+    public static Task<string?> GetSystemTimeZoneNameAsync(
+        HistorianClientOptions options,
+        CancellationToken cancellationToken)
+        => Task.Run(() => GetSystemTimeZoneName(options, cancellationToken), cancellationToken);
+
+    private static string? GetSystemTimeZoneName(HistorianClientOptions options, CancellationToken cancellationToken)
+    {
+        using HistorianGrpcConnection connection = HistorianGrpcChannelFactory.Create(options);
+        uint clientHandle = HistorianGrpcHandshake.OpenAuthenticatedConnection(connection, options, cancellationToken);
+
+        var statusClient = new GrpcStatus.StatusService.StatusServiceClient(connection.Channel);
+        GrpcStatus.GetSystemTimeZoneNameResponse response = statusClient.GetSystemTimeZoneName(
+            new GrpcStatus.GetSystemTimeZoneNameRequest { UiHandle = clientHandle },
+            connection.Metadata,
+            DateTime.UtcNow.Add(options.RequestTimeout),
+            cancellationToken);
+
+        if (!(response.Status?.BSuccess ?? false))
+        {
+            return null;
+        }
+
+        string? value = response.StrSystemTimeZoneName;
+        return string.IsNullOrEmpty(value) ? null : value;
+    }
 }