chore(release): 0.5.1 (#47)

A patch release: nothing here breaks. Credentials registered under 0.5.0 keep
working, the derived did:key is unchanged, and no peer has to move in step
with another.

The headline is the WebAuthn user handle (#45/#46). It was the UTF-8 of
whatever the caller passed as `userId`, so an authenticator — which keeps one
credential per (rp.id, user.id) and replaces it when both match — silently
destroyed the first passkey when a second person on the same device used the
same name, and the DID with it. It is 64 random bytes now; the typed value
stays as `user.name`, the label the picker shows.

Consumers get one behavioural difference worth naming in their own UI:
re-registering under a name used before adds a passkey instead of replacing
one. That is the point, but it means a picker can now show several, so the
labels want to be distinguishable.

Also in this release: the largeBlob keystore actually persists its secret key
(#43), the credential carries the authenticator's own answer on extension
support rather than the browser's guess (#43), and extension detection asks
`getClientCapabilities()` instead of probing a prototype that never had the
properties (#9/#42) — that last one had the encrypted-keystore demo disabling
its headline feature in every browser ever shipped.

67 node tests pass against the bumped version.

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>

Author: NiKrause

CHANGELOG.md

@@ -2,6 +2,8 @@
 
 ## Unreleased
 
+## 0.5.1
+
 ### Fixed
 
 - The WebAuthn user handle is 64 random bytes instead of the UTF-8 of whatever

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@le-space/orbitdb-identity-provider-webauthn-did",
-  "version": "0.5.0",
+  "version": "0.5.1",
   "description": "WebAuthn-based DID identity provider for OrbitDB for hardware-secured wallets and biometric Passkey authentication",
   "main": "src/index.js",
   "types": "types/index.d.ts",