* Terminal fix: unify event timestamp format to nanoseconds since epoch
All five plugin events now emit timestamps as nanoseconds since epoch
(qint64 via QVariant). Previously messageSent, messageError,
messagePropagated, and connectionStateChanged used a local ISO-8601
string while messageReceived passed the raw waku nanosecond value as a
stringified float, forcing consumers to special-case each event.
Closes#26
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* fix: annotate event timestamp fields as qint64, not QString
The value emitted into the QVariantList is a qint64 (ns since epoch);
the contract comments still said QString. Align the documented type
with what is actually emitted.
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
send() now accepts QByteArray directly (base64 still applied internally
for the FFI JSON). messageReceived emits payload as QByteArray instead
of a base64-encoded QString, matching logos-delivery behaviour.
Closes#27
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
