Recly 0.0.1-dev.6 (phone + Galaxy Watch + Mac + Windows + iOS unsigned)

Built from main 7923a7b. Supersedes v0.0.1-dev.5. Every asset is rebuilt from this commit (the Windows MSI is the GitHub Actions build of it).

New since v0.0.1-dev.5:

• What is still in flight is visible everywhere, without a server. The phone shows RECEIVING while a watch transfer is coming in (and its status node says so); every device shows UPLOADING for a recording another device is still uploading — a Drive folder that has the recording but no meta.json yet — and TRANSCRIBING while the device that ran the workflow still has its transcribe step to finish. The uploading device leaves a small marker on the Drive folder for that; it is cleared when the job ends and ignored after eight hours. Lists refresh every 30 s while something is in flight.
• The Galaxy Watch says "Sending n" instead of "n waiting" while a transfer pass actually has the phone on the other end — on the main screen, the tile and the complication.
• "Retry" is offered on a row waiting out a retry backoff after a failed attempt, on every shell (not while a provider is transcribing).
• A recording whose transcribe finished no longer reads as "transcribing" while a later webhook waits out a backoff.
• The watch logs where each transferred file's time went (channel open, send, close, ack).

Phone and Galaxy Watch APKs are debug-keystore signed, Android 14+ / Wear OS 5+. Watch install: enable ADB + wireless debugging on the watch, then adb pair / adb connect / adb install -r. iOS: Recly-iOS-0.0.1-unsigned.ipa is an UNSIGNED Release build (iOS 17+, includes the Apple Watch app and widgets); sideload it with your own Apple ID via AltStore or Sideloadly, keeping the original bundle id app.recly. Windows: Recly-Windows-0.0.1.msi is the GitHub Actions build (not SmartScreen-signed — choose "More info → Run anyway"). Recly-Mac-0.0.1.dmg is signed with a local development certificate; Gatekeeper will refuse it until you right-click → Open.