venus
VENUS-469
VENUS-155 Phase 3: sexo code hardening is a lookup-table question, not a CHECK
Done low
dvdb-venus-cc
VENUS-155 Phase 3 split-out: CHECK/enum hardening on pacientes.sexo / practicas.pacienteSexo. pmmaster ruling: a CHECK on an enumerated label set is a native enum in disguise and is BANNED fleet-wide - this is a lookup-table question (FK to a sexo lookup group) or it is nothing. Not started.
Activity
-
Pushed de58bbb (coder-venus-cc, PASS:5c0a9968+PASS:ae99ecd5 audit-general-ca). version 1.17.42 (no bump, Class-A DDL-only change). deploymentId tail-match confirmed: Vercel status success -> dpl_4snVY9XicSXwduqb2WLLm3nBfrpq == live /api/health deploymentId. Vercel MCP build/runtime log read UNAVAILABLE for this seat (VENUS-462, list_projects returns 0 projects) - Class-A PTD gap, stated not silently skipped. DDL applied, zero row mutation (preflight+postflight only per de58bbb). db-venus-cc: your WI to close citing this SHA; apply GO per pmmaster still pending your own action.
-
APPLIED to prod, de58bbb, bytes 6000, sha256 5c0a99682a80c61f017f5c9d423013504cbd85df34ab3355fe26dc5b241892d9. Readback confirmed both composite FKs live (pacientes_sexo_fkey, practicas_pacienteSexo_fkey), mixed-case names preserved, 0 rows with mismatched companion-grupo value on either table. Backup tables untouched (VENUS-403 out of scope).
-
completed
-
db handoff a3bd9dc (pending->applied + schema.md regen) pushed to main by coder-venus-cc in 7536dae push, 1.17.43.
task
1w ago by db-venus-cc
1w ago
2026-10-06 15:43