Auto: opcuaclient-13 — Part 13 aggregate catalog mapping

Closes #285

docs/drivers/OpcUaClient-Test-Fixture.md

@@ -166,6 +166,35 @@ Beyond that:
 3. **Dedicated historian integration lab** — only path for
    historian-specific coverage.
 
+## HistoryRead aggregate coverage
+
+PR-13 (issue #285) extended `HistoryAggregateType` from 5 to ~30 values
+matching the OPC UA Part 13 §5 catalog. The mapping itself
+(`OpcUaClientDriver.MapAggregateToNodeId`) is unit-tested via
+`OpcUaClientAggregateMappingTests`:
+
+- The full enum is swept with `Enum.GetValues<HistoryAggregateType>()` —
+  every value must resolve to a non-null namespace-0 numeric `NodeId`.
+- The 25 new aggregates each assert against a reflection-resolved
+  `Opc.Ua.ObjectIds.AggregateFunction_*` field by name, so a future SDK
+  upgrade that renames a constant trips the test loudly.
+- The original 5 ordinals stay pinned to their pre-PR-13 NodeIds so existing
+  config files / persisted enums keep working.
+
+This is **the well-known-NodeId test path** — the standard Part 13 NodeIds
+are stable across SDK versions; round-tripping each one against a live
+upstream is the integration suite's job and doesn't add coverage to the
+mapping table itself.
+
+`OpcUaClientAggregateSweepTests` is the integration counterpart. It loops
+every enum value against a real opc-plc upstream and asserts the wire path
+doesn't crash even when the simulator returns
+`BadAggregateNotSupported` for an aggregate it doesn't honour. opc-plc's
+default profile doesn't enable HistoryRead on the well-known nodes, so the
+test currently `Assert.Skip`s — re-enables when the fixture image is
+upgraded to a history-sim profile (`--useslowtypes --ut=10` or similar) and
+a known-good historized NodeId is wired into `OpcPlcProfile`.
+
 ## Key fixture / config files
 
 - `tests/ZB.MOM.WW.OtOpcUa.Driver.OpcUaClient.Tests/` — unit tests with
@@ -175,3 +204,7 @@ Beyond that:
 - `tests/ZB.MOM.WW.OtOpcUa.Server.Tests/OpcUaServerIntegrationTests.cs` —
   the server-side integration harness a future loopback client test could
   piggyback on
+- `tests/ZB.MOM.WW.OtOpcUa.Driver.OpcUaClient.Tests/OpcUaClientAggregateMappingTests.cs`
+  — Part 13 aggregate enum-to-NodeId mapping coverage (PR-13)
+- `tests/ZB.MOM.WW.OtOpcUa.Driver.OpcUaClient.IntegrationTests/OpcUaClientAggregateSweepTests.cs`
+  — wire-side aggregate sweep against opc-plc (build-only scaffold; PR-13)