Passkeys: less than a stellar experience

This problem just got a whole lot worse because Google turned on Passkey support for non-Google Workspace accounts today. Non-technical users are about to get super frustrated because without 1P support Passkeys created via a Chrome-engine browser are indeed locked to the device where they were created. There is some support in Chrome for signing in by taking a picture of a QR code presented by the browser with an iOS device, but to make that happen seamlessly you would have had to create the Passkey with Safari on macOS or iOS and store it in the iCloud keychain.