Solos I use even the nightly versions of 1Password since 2 years, and they didn't destroy my data. These are not crashing, untested, amok running apps straight from the compiler. Instead, the betas and nightlies can be seen as candidates for the next release with much QA before being available to us customers. Existing functions usually don't break.
If it comes to passkeys, I don't expect them going to the release any time soon, because there is still much to do outside of 1Password to make passkeys work seamlessly everywhere. Many websites are starting with passkeys currently, but this is not yet without issues. This is kind of experimental for every party involved, because it's a new technology. And as long as the whole system is still stabilizing, there cannot be a release of the passkeys functionality in 1Password, because there would be too much issues (with many websites), and the feature would be rejected by many users. Rejected forever, with much damage to passkeys in general.
For example, Google Chrome currently hijacks passkey filling for Google accounts. You're able to save Google account passkeys in 1Password, but you're not able to use them to login - Chrome only offers Windows Hello and the Windows-integrated passkeys handling. As long as this isn't solved by Google and 1Password cannot provide the Google account passkey, I guess it's not reasonable to set passkey support to release. People would start using it, then failing with Google accounts - one of the most frequently used account type.