- write_timestamp/write_quality come from the command, then the server
document (connectors/opc-servers, read even when the reads have the
connection open, same 60 s cache), then the WRITE_TIMESTAMP/WRITE_QUALITY
env defaults.
- The quality comes from the command's `quality` (the prediction status:
Good/Bad/Uncertain, Good when absent); an unknown one is a bad_quality error.
- A server that refuses them (BadWriteNotSupported, e.g. Kepware) gets the
value written again alone and is remembered until restart: one warning and
opc_write_value_only_fallback_total per server.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
5318c82677