ProtonBridge v1.2.1

1.2.1 — direct Resync, native recovery and upstream updates

• Remove bisync dry-run/preview UI, reports, approval expiry, copied preview listings
  and the mandatory preview step. Resync saves the task, confirms folders, filters,
  flags and preferred copy, then performs real transfers. Scheduled runs never
  automatically choose Resync. Normal Run keeps using the completed baseline.
• Permit native --recover and --resilient boolean flags. A failed/interrupted
  ordinary run may retry its matching saved baseline when either is enabled;
  rclone validates whether recovery is possible. Adding these operational flags
  does not change file-selection identity. Missing baselines, changed endpoints,
  filters, configuration or engine still require Resync. Neither flag guarantees
  recovery of a failed first Resync. Correct spellings are shown for typos.
• Merge 52 official rclone commits through 35a03a47e00e2cadec744f977e5fa9d851127016,
  pinned by fork merge 814954580.
  Includes bisync skipped-conflict/listing fixes, include-filter performance work,
  VFS memory/race fixes and Drive fast-list hang fixes. Retain Proton metadata,
  checksum requirements, contained companion modules and atomic listing locks.
  This is upstream development source, not a new official stable rclone release.
• Reduce repeated work: publish RC notification summaries only when displayed
  counts change; stop repeatedly logging retained failed jobs at every poll.
  Optional session checks skip empty tokens and TOTP-only configurations.
  Lock ownership, streaming lifecycle, idle shutdown and transfer refresh remain.
  No measured device battery saving is claimed.
• Reconcile upstream CloudBridge security/reliability commit f97ff8e3 with the fork:
  private validated share/download staging, loopback streaming URL capability,
  exact remote-name validation, checked missing-remote failures and fail-closed
  Keystore protection of SAF credentials. Preserve stronger existing redacted
  logging, native stream ownership and signed-build provenance protections.
• Validation: 222 app host tests, zero failures/skips, 14 release-script tests,
  lint, all four native ABI builds, debug split/universal APKs and device-test APK
  build. Engine host/race regressions, four upstream bisync scenarios and native
  trusted-listing recovery checks passed; independent integration reviews completed.
  Device tests were compiled, not executed on a physical phone.
• Base version code 210; ARM64 217. The new engine pin requires a one-time Resync
  before an older engine baseline can be used. Existing releases stay immutable.