terra
TERRA-96
import venus maxilo cirugias into modulos 1 and 2, marked (a conf.)
Done high
dtdb-terra-cc
Elazar ruling 2026-08-22: import from the maxilo repo rather than wait for Puia to list them, and put '(a conf.)' in the nombre so the provisional status is visible everywhere the name travels - including past practica records, where isConfirmedByClient does not reach. Source: venus db/seed-cirugias.sql, modulo 4 Implantologia ids 148-157 (10 rows) and modulo 16 Reconstruccion alveolar para implantes ids 158-164 (7 rows), all isConfirmedByClient=true in venus, same client. Terra keeps its 13 existing literature rows in those two modulos or retires them - see task detail.
Activity
-
terra_38 applied 2026-08-22 (version 20260822144845, md5 ff42b74117a134363cb12ae14281752f). Checksum-verified byte-exact against stored statement. Live-verified: m1_live=10, m2_live=7, injerto_live=4, barreraImplante_live=4, barreraReconstruccion_live=7, zona_live=6, marca_live=19 unchanged, cirugia id=3 retired (isActive=false), práctica ea19312a still resolves cirugiaId=3. Moved draft->applied/, citation gate rc=0 (WARN on lookupOptions is expected, GO rationale ownerAppKey=terra proven in-file, no db-enamel-cc GO needed per terra_35 precedent).
-
DONE - verified live, by NAME not by count. Modulo 1 Implantologia holds exactly 10 active cirugias and modulo 2 Reconstruccion exactly 7, matching venus ids 148-157 and 158-164. EVERY ONE of the 17 carries the "(a conf.)" suffix in nombre and isConfirmedByClient=false, which is the point of the ruling: the provisional status travels with the name into past practica records, where the boolean does not reach. The 13 literature rows terra had in those two modulos are gone from the active set - modulo 1 would show 23 otherwise. Downstream of this: TERRA-97/TERRA-76 then scoped the per-cirugia campos onto exactly these rows (barrera+injerto on 7 of the 10, zonaDadora on the 4 bloque cirugias), so the import and the field scoping agree.
task
7w ago by wi-cli-venus
7w ago
2026-08-22 20:19