Modulos offer AI-seeded cirugias instead of the catedra list: client-reported, correct mapping supplied, Drive source not yet in hand

REPORTED by the client (Sebastian Puia, WhatsApp 2026-08-17 09:12, relayed by Elazar). Every modulo currently offers the AI-generated seed cirugias. Puia states the correct mapping himself: implantologia + Cx reconstructiva must offer the SAME cirugias as the maxilofacial especialidad; Cx de tejido blando + protesis convencional + protesis implanto-asistida must offer the list HE loaded in Drive; periimplantitis keeps the AI-generated set (he says that one is correct as-is). BLOCKING INPUT: the Drive file itself. Asked of Elazar 2026-08-17. Do NOT reconstruct the list from the maxilofacial especialidad or from any AI source - inventing it a second time is what produced this row. NOTE ON SCOPE MECHANISM, do not assume: terra has exactly ONE vocabularyScopes row database-wide (terra/piezasDentarias, exclude) per e79aa77, so per-modulo cirugia narrowing is NOT currently done by scope at all and the resolver default is all-active-values. Whether this is seed data, a scope gap, or a missing modulo-cirugia relation is the first thing to measure, not to assume. Terra never mutates shared vocabulary rows: if the fix reaches lookupOptions or any unprefixed object it needs db-enamel-cc GO before apply.