CLIENT QUESTION BUNDLE: eleven venus rows are parked on one unasked set of client questions (Sebastian/Puia)

Consolidates VENUS-49 (patient localidad field), VENUS-51 (D3 infecciones cervicofaciales tratamientos), VENUS-52 (D4 keep/drop Enucleacion coadyuvante), VENUS-53 (D5 Otros modulo empty), VENUS-48 (C2 shared tratamiento pool Quistes/Tumores/Cancer - reverses confirmed section 10), VENUS-59 (Mendez Bovio DNI 95438931 identity ambiguity), VENUS-290 (patologias/tratamientos conflation), VENUS-295 (CR G8+G10 structured pre-op diagnosis + post-op medication), VENUS-105 (CU-15b alumno sees own position vs named peers - anonymization contract), VENUS-43 (student-vs-student camada compare), VENUS-56 (post-48h edit fulfillment mechanism). Every one is backlog, unassigned and unstartable, and each reads as independent work. They are not: they are one outbound client conversation nobody has had. No agent can unblock these by reading code - they need the client to answer. Outbound to client is Elazar-gated, so the deliverable here is the QUESTION SET, drafted and ready for him to send, not the send. Draft each as a single closed question with the options already enumerated so the client answers yes/no or picks, never open-ended. Then block the eleven rows on this one.