Omaclipsync 0.4.1

Omaclipsync 0.4.1

Fix a conditional privacy failure in 0.4.0: a saved pause or receive-only change
could leave the old upload policy active after an encrypted-state write failed.
If storage later recovered, a fresh copy could be uploaded under that old policy.

• Fence clipboard/notification callbacks, adopt the saved selection immediately,
  and quarantine a failed old session outside automatic and manual sync paths.
• Retry application of the saved configuration every 30 seconds while blocked.
  Do not overwrite a saved restriction with a resume before cleanup succeeds.
• Return an explicit application error; refresh the shell's saved configuration
  and status and show English/Chinese recovery feedback.
• Add deterministic paired-session storage-failure, recovery, restart and shell
  reply regressions. Keep uncertain-upload cancellation and device identity.

Shared core remains 0.4.0, wire protocol 3, with Server 3.0.0 and
Desktop 0.5.0. This patch changes only Omaclipsync. Both bundled executables
are rebuilt and byte-compared in the pinned builder before verified packaging.

Marketplace approval still applies only to its exact reviewed commit. The source
and build evidence supplement maintainer review; they are not a security audit.

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.

Omaclipsync 0.3.0

Support only the current RustClipSync protocol. Remove the obsolete SyncClipboard transport, SignalR path, fallback watcher and protocol selector. The marketplace-reported sensitive plaintext history path is removed along with that transport. HTTP endpoints now use /api/...; encrypted state filenames, keyring identifiers and device identity remain unchanged. Existing history is not erased.

Current synchronization, sensitive inbox, history and direction controls remain available. Native binaries are rebuilt and byte-compared before publication. Marketplace maintainer review remains pending; this release has not been automatically deployed to the active desktop.