Allow passkeys their own history

Seems like the same risk exists for all fields.

The downside to “Are you sure?” is that the reaction tends to be come automatic over time and if you accidently click “yes” there is no going back.

Is there some reason you prefer confirmation over a history mechanism (which is actually the topic of this feature request)? With a history mechanism, one becomes able to “undo” a change even well after inadvertently deleting and saving.

If passkey loss is your only concern, you might vote for this FR. If you also care about TOTP, URLS, usernames, etc., History for all fields like Password History might be more worthy of your vote.