ProtonBridge v1.1.6-rc.1

1.1.6-rc.1 — authoritative Proton revision checksums and recovery reports

• Pin the rclone engine to 8627faf6.
  Legacy Proton listings omit active-revision attributes and may expose an older
  checksum in Link.XAttr. Resolve the listed revision's own authenticated metadata
  rather than comparing that older checksum against downloaded content. Explicit
  revision attributes, when present, remain authoritative and must verify.
• Fetch only a minimal revision metadata page with block URLs disabled. Coalesce
  duplicate requests, limit concurrent metadata fetches to four, and reuse signed
  metadata by share/link/revision identity within an 8 MiB payload budget and
  2048-entry cap. No names, directory inventory or active IDs are reused: each
  listing is fresh, and metadata cache hits reverify against current keys.
  Downloads and successful signed commits seed reuse for post-transfer listings.
• Use the fetched revision's signer; reject changed advertised revision IDs,
  mismatched responses and missing/ambiguous active identity. Invalid preferred
  metadata never falls back to older link attributes or a valid cache entry.
• Remove terminal colour escape codes before redacting/displaying diagnostics.
  Checksum-listing aborts retain failure status and explain verification uncertainty,
  comparing the two copies and repeating preview/review/initialisation. No automatic
  force, resync, exclusion or checksum bypass is added.
• Signed legacy-API fixtures reproduce the reported pair of differing checksums
  and cover listing → download metadata → relisting → changed revision → upload
  commit → relisting. Tests cover current-key revalidation, corrupt preferred
  attributes, identity failures, cache bounds, cancellation and concurrent reads.
  Backend/bisync, companion auth/crypto/block, race and static checks passed before
  pushing the completed engine fix. Local SHA1 fixtures initialise differing
  29-byte .nomedia files successfully without mutating files during preview.

The first release build was cancelled after a repeated Anki failure exposed
the legacy wire-shape gap. This candidate contains the
completed fix. The actual account response/device is unavailable, so signed
protocol regression coverage does not constitute live-account acceptance. Files
changing during sync can still correctly stop reconciliation; keep Anki closed
when synchronising its database. No full listing-to-download snapshot binding or
silent repair is claimed. Engine changes require fresh preview and explicit approval.

Protocol reference: Proton SDK legacy revision endpoint and metadata schema.