=====================================================================
               PASSKEY REGISTRATION TRACE (SUCCESS)
=====================================================================
1. Server registration challenge generated:
   Challenge (b64url): l_iOOH-PTwi_elzrr78NyLc5plvI2HdFPsuREvrfgpA

2. Browser constructs registration request (webauthn.create):
   - Type:        webauthn.create
   - Challenge:   l_iOOH-PTwi_elzrr78NyLc5plvI2HdFPsuREvrfgpA
   - Origin:      https://rp.example.com
   - RP ID:       rp.example.com
   - User Handle: usr_paula_982

3. Authenticator performs key creation & device-side registration:
   - Generated Elliptic Curve P-256 Keypair
   - Generated Credential ID: oEUSeMsTRQJgO0QeDY0Mfg
   - Device-side Credential DB State (Private State):
     * Credential ID: oEUSeMsTRQJgO0QeDY0Mfg
     * RP ID:         rp.example.com
     * User Handle:   usr_paula_982
     * Sign Counter:  0
     * Private Key:   [ECDSA Private Key object stored securely]

4. Authenticator returns Attestation Object (Public State):
   - Credential ID: oEUSeMsTRQJgO0QeDY0Mfg
   - Public Key PEM:
-----BEGIN PUBLIC KEY-----
MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEWStbebDjsDiBRGCWICypVHmW8zoo
dk1XQqGNhPEANYU9C/y2Z7k98ny5TsJ3LOpqvs7mFaG9ppFhNWjRS8dVag==
-----END PUBLIC KEY-----
   - User Presence flag:  True
   - User Verification:   True

5. Server registers credential & updates its local DB:
   - User Handle:  usr_paula_982
   - Credential ID: oEUSeMsTRQJgO0QeDY0Mfg
   - Public Key:    Registered in memory
   - RP ID:         rp.example.com
   - Sign Counter:  0

=====================================================================
 [IMPORTANT SECURITY NOTE]
 The Relying Party Server does NOT store the private key. It is only
 stored within the Authenticator device boundary. The server only holds
 the public key to verify cryptographic signatures of subsequent assertions.
=====================================================================