2 OAuth-completed users (ale98gaete, veronica1994rios) have authId NULL despite successful Google sign-in (Apr-25/May-03 2026) — SEPARATE from PLUTO-152 dot bug (their email is dot-free, raw=canonical). authId-write never reached/failed in the Apr-May callback version; active alumno roles; no appEvents auth errors in their sign-in windows. db heal-check pending: does current callback auto-link on next login (benign) or is it a live stuck-account bug

Sub-tickets

Questions

Activity

• wi-cli-venus created · 2026-06-20
• wi-cli-venus commented · 2026-06-20
  RECONCILED from git HEAD (coder + db agree): BENIGN, auto-heals on next login, no fix needed. (1) Deployed HEAD callback preReg lookup is raw one-sided BUT both victims' emails are dot-free → raw=canonical → the lookup FINDS them; (2) deployed authId-write is UNCONDITIONAL on a found+enabled row, no silent skip branch. So next sign-in links them automatically. Original Apr-May non-link = timing/ordering artifact (login attempt before roster row existed) or an older callback version — NOT a current code-skip bug. db doing a createdAt-vs-first-auth timestamp confirm to close. NOT a PLUTO-152 dot victim (dot-free email). No manual authId edit (No Proactive DB Edits) — heals on re-login. PLUTO-152 fix preserves the linking block byte-for-byte, does not affect these 2.
• wi-cli-venus deferred · 2026-06-20
  benign auto-heal on re-login; optional timestamp confirm pending; no code/manual fix
• wi-cli-venus commented · 2026-06-20
  db timing split (createdAt vs first-auth): TWO distinct root causes, both heal on re-login under current HEAD. (a) ale98gaete (access_request): auth 2026-04-25 23:06 → users row 2026-04-26 03:57 (~5h later, on AR approval) → users_row_after_auth = TRUE = classic ordering artifact (no-profile bounce, row created later, never retried). (b) veronica1994rios (migration): users row 2026-03-18 (months prior) → auth 2026-05-03 → users_row_after_auth = FALSE: row PRE-existed, preReg path should have linked but didn't = historical callback authId-write failure (pre-current-HEAD), specific cause unrecoverable (no appEvents from that era). Same outcome both: benign-auto, heals on next login, NO manual authId edit (No Proactive DB Edits). PLUTO-152 fix preserves the linking block byte-for-byte; does not affect either.
• wi-cli-venus commented · 7w ago
  CLOSED into PLUTO-69 as NOT-A-BUG (same class). veronica1994rios = email reconciled after a pre-reconciliation login attempt (audit verified usersArchive seq 379, 05-08 email change post-dating her 05-03 blocks). Both PLUTO-155 users (veronica + ale98gaete) are identity-reconciled-after-attempt, not a callback race. Self-heal on re-login. No code fix.
• wi-cli-venus completed · 7w ago
  completed