pluto
PLUTO-68
/practicas/nueva form: lay fields side-by-side to save vertical space (currently stacked one-below-the-other)
Done normal
cpcoder-pluto-cc
Questions
No questions.
Activity
-
Dispatched to coder-pluto-cc 2026-06-12. Scope: /practicas/nueva form fields stacked vertically -> responsive side-by-side grid (grid-cols-1 md:grid-cols-2) to cut vertical space; MUST still stack on mobile (PLUTO-40 mobile-first); pair related fields, keep textareas/comentarios full-width; preserve all labels/validation/conditional logic; reuse shared form primitives. Frontend-only -> post-push audit PTD, no pre-design ping.
-
Dispatched to coder-pluto-cc 2026-06-12. Scope: /practicas/nueva fields stacked -> responsive side-by-side grid (grid-cols-1 md:grid-cols-2), must stack on mobile (PLUTO-40), pair related fields, textareas full-width, preserve labels/validation/conditional logic, reuse shared form primitives. Frontend-only -> post-push audit PTD.
-
coder-pluto-cc / coder
-
Flipped from stale inProgress (dispatched 06-12, zero work events since, superseded by PLUTO-561). Frontend-only, no gate - queued behind 561.
-
Substantially delivered by intervening PLUTO-561 friction work: every section already uses responsive grid-cols-1 sm:grid-cols-2/3 (Operador+Asistente, rol+compañero, fecha 3-col, N°HC+fechaNacimiento, Sexo+Nacionalidad+Provincia, clinical multiselects). Only 2 lone full-width controls remain (Tabaquismo Select, Partido/Localidad Input) with no natural subsection partner — pairing them would be artificial for ~1 row of vertical savings, not worth a deploy. Closing rather than forcing it.
task
2026-06-12 by wi-cli-venus
4w ago
2026-07-17 04:39