/a-solucionar: admin data-health dashboard — non-allowlisted active users, unassigned teachers, orphan records. Auth-required. Per Elazar -30391/-30393 + 3-PM §Auth ratification.

Sub-tickets

Activity

• system created · 2026-05-17
  wi cli
• system note · 2026-05-17
  Spec: /a-solucionar admin data-health dashboard (auth-required, admin/bedelia only). Initial checks: (1) active users with non-allowlisted email — query users WHERE isActive=true AND email NOT matching allowlist domains; (2) teachers with no comisión assignment (docente_* roles, no active comisionJtps/comisionAdjuntos row); (3) students with no active studentAssignment. Display as 3 collapsible sections with row counts + drill-down tables. Route: /admin/a-solucionar or alias /a-solucionar → /admin/a-solucionar. Needs wi ask Elazar for which checks to include in v1.
• rob questionAsked · 2026-05-17
  q#24 to=elazar: Which data-health checks should /a-solucionar v1 show? Suggested: (1) active users with non-allowlisted email, (2) teachers without comisión, (3) students without assignment. Confirm or adjust.
• rob blocked · 2026-05-17
  awaiting elazar
• rob questionAnswered · 2026-05-17
  q#24: Yes — all anomaly combinations: non-allowlisted active users, teachers without comisión, students without assignment, practicas in orphan state, etc.
• system statusChanged · 2026-05-17
  dispatching to coder-pluto-cc
• system completed · 2026-05-17
  5d39029 — /admin/a-solucionar: 6 anomaly sections, server component, auth via requireAnyCap. PASS:5d39029 audit-pluto-cc-31122.
• wi-cli-venus unblocked · 2026-08-19
  backfill: blockedReason cleared on a closed row; it described a dependency discharged before the item closed and pre-dated the d6153e2 fix that now clears it automatically (Elazar decision 1b, 2026-08-19)