Omaclipsync 0.4.0

Omaclipsync 0.4.0

Requires RustClipSync Server 3.0.0 / wire protocol 3. Older clients must stay
on server 2.0.0. Matching Desktop is 0.5.0; mobile apps and Fcitx input methods are
released separately.

• Report direction and pause before receive, using fenced WebSocket control and
  authenticated HTTP fallback. Keep local send/receive guards on failure.
• Use per-device filtered delivery and latest-only backfill in the global window
  configured by the server administrator; no client window is hardcoded.
• Recover rejected automatic uploads by durably cancelling old/queued values,
  skipping the then-current remote value and retaining the system clipboard.
  Resume fresh copy events; do not silently rebase rejected text. Handle legacy
  conflicts before first receive, and recover safely from cancellation response
  loss or process restart.
• Fix ordinary receive after turning off marked-sensitive synchronization.
  Sensitive inbox defaults, pairing and encrypted-state identity remain intact.
• Include the final rustclipsync-core 0.4.0 export. Rebuild both bundled native
  executables with the pinned compiler image and byte-compare before packaging.

Local core/plugin tests, JS/QML checks and four real Wayland conflict scenarios
passed. Release checksums and build evidence identify the exact source. Optional
ordinary history remains plaintext; marked sensitive text is excluded. HTTPS is
not end-to-end encryption, and sensitivity detection depends on applications.