Jeff Emmett 88118cd157 fix: use server-initiated WebAuthn flow for guardian acceptance and login ... The guardian page and auth.rspace.online login page were using the client-side authenticatePasskey()/registerPasskey() SDK functions which generate their own challenge and return AuthenticationResult — but then tried to send result.challenge and result.credential (both undefined) to the server. This caused postgres to throw "UNDEFINED_VALUE" resulting in a 500 "Internal Server Error" that the client couldn't parse as JSON. Fix: use the proper server-initiated flow matching rstack-identity.ts: 1. POST /api/auth/start (or /register/start) to get server challenge 2. navigator.credentials.get/create with that challenge 3. POST /api/auth/complete (or /register/complete) with challenge + credential Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>		2026-03-02 16:34:43 -08:00
..
encryptid	fix: use server-initiated WebAuthn flow for guardian acceptance and login	2026-03-02 16:34:43 -08:00
lib	feat: add JSON WebSocket mode, demo seed data, and useDemoSync hook	2026-02-15 09:38:59 -07:00