docs(historian): fix-wave docs and stale comments

- Historian.md: Empty samples always Bad (writer/updater/read clamp),
  long-name refusal, 5 s bootstrap failure cache, AtTime after now, info-bit
  masking, HistoryUpdate does NOT type-check (M-1 decision), DeleteRaw
  needs both bounds, reverse Raw paging, the historian/historization metric
  prefixes, and provisioning numeric-only lines qualified as Gateway.
- CLAUDE.md numeric-only lines qualified as Gateway backend.
- Stale 'sole historian' lines in DriverLifecycle, ServiceHosting and the
  retired Wonderware stub; Client.CLI exit-code contract.
- ServerHistorianOptions: Endpoint/Backend XML docs untangled, Validate()
  indented; Program.cs comments are backend-neutral; T10 week-test day count.

Claude-Session: https://claude.ai/code/session_01Ef2ozxS7QPanGT8uoATbTe

docs/Client.CLI.md

@@ -225,8 +225,10 @@ otopcua-cli historyread -u opc.tcp://localhost:4840/OtOpcUa \
 
 Inserts, replaces, updates or deletes stored history on a historized node via the OPC UA `HistoryUpdate`
 service (requires a server whose historian backend supports updates and a session holding the history-write
-permission). Prints one line per item (`index  time  StatusCodeName`) followed by the overall service
-result; any Bad item or service result exits non-zero.
+permission). Prints one line per item (`index  time  StatusCodeName`; a code the SDK has no name for prints as
+`0xXXXXXXXX`) followed by the overall service result. It exits non-zero unless **every** result is Good: a Bad
+**or Uncertain** item, a non-Good node or service result, or a Good service result that is missing per-item
+results (fewer than the items sent, printed as `(no result returned)`) all fail the command.
 
 ```bash
 # Insert two values