Comisiones grid UX: row-click opens existing detail page + relocate rename + hide delete unless empty (A+B)
Elazar UX report 2026-07-06. File: src/components/administrar/comisiones-grid.tsx. (A) Row/name click currently (~L147-154) opens INLINE RENAME; change it to NAVIGATE to the already-built detail page /administrar/comisiones/{id}?periodo={periodoId} (src/app/(protected)/administrar/comisiones/[id]/page.tsx exists + is complete: stats, equipo docente by name, alumnos roster). Move rename into the '...' RowActionsMenu as an explicit 'Renombrar' action (not a click-footgun). (B) In the same '...' menu, HIDE/disable Delete unless adjuntoCount===0 && jtpCount===0 && alumnoCount===0 (counts already on each row). Server guard removeComision (administrar-actions.ts:1595-1606) already enforces 0/0/0 — keep it; this is UI belt-and-suspenders. Frontend-only, no schema/auth/email.
Questions
Activity
-
A+B shipped bc7464d/v2.3.27, audit PASS (deploy READY+aliased, /api/app-version=2.3.27, runtime clean). comisiones-grid.tsx: name-click now navigates to the existing /administrar/comisiones/[id] detail page; rename moved to explicit 'Renombrar' action in the '...' menu; 'Eliminar' shown only when comision empty (adjunto/jtp/alumno counts all 0); server guard removeComision unchanged (0/0/0 refusal intact). Frontend-only, no authz surface touched. UX behaviors unexercised headless — Elazar to eyeball on live.