WIP: Store per-device user agent for remoteStorage authorizations #257

Draft
raucao wants to merge 2 commits from feature/rs_device_tokens into feature/rs_auth_pkce
pull from: feature/rs_device_tokens
2 Commits
Author SHA1 Message Date
raucao 918d2622c6 Document the storage-first launch flow
CI / Test (pull_request) Successful in 41s
Add an explicit spec for the storage-first handoff (remoteStorage spec
section 11): launching an app passes only `#remotestorage=<address>`,
never an access token. The app then runs the application-first
(now PKCE-capable) flow itself.

Part of #254
2026-11-02 17:40:00 +04:00
raucao e3bf932c51 Store per-device user agent for remoteStorage authorizations
CI / Test (pull_request) Successful in 41s
- Add user_agent to remote_storage_authorizations and rs_authorization_codes
- Capture the browser's user agent at consent, carry it on the authorization
  code, and store it on the authorization when the code is exchanged
- Store it directly for the implicit flow too

With the reuse shortcut gone, each authorization is already a distinct
per-device token; this adds the metadata needed to label and display them.

Part of #254
2026-11-02 16:40:32 +04:00