audit: confirm tipoDocumento (and other lookup-backed selects) store UUID FK to lookupOptions, not raw text — refactor any that drifted

Sub-tickets

Questions

Activity

• system created · 2026-05-04
  wi cli
• coderhelp-mars-cc-w assigned · 2026-05-17
  assigned to coderhelp-mars-cc-w
• system statusChanged · 2026-05-17
  claimed per pm-mars-cc-30255; auditing tipoDocumento + sibling lookup-FK selects
• system audit-finding · 2026-05-17
  Pattern A (UUID FK *OptionId, ~14 cols): clean across practicas/practicaTeeth/practicaToothConductos/userRoles/teacherComisionMemberships/periodos/notifications/practicaImages. Pattern B (value-text, intentional per WI#195): users.tipoDocumento + accessRequests.tipoDocumento. Server-side resolution at users-actions.ts:436 + user-actions.ts:99 (UUID→value via lookupOptions JOIN). Public form access-request-form.tsx:156 binds option.id=value (text), bypasses UUID, INSERTs value-text directly to accessRequests.tipoDocumento — internally consistent. No drift, no refactor needed.
• system completed · 2026-05-17
  audit pass: two-pattern design intentional + correctly enforced; no drift detected across schema FK + read/write paths