Catalogue additions requested by client 2026-07-30, never filed: parotidectomia superficial/completa (glandulas salivales) + retiro de osteosintesis (traumatologia)

Two catalogue additions the client asked for on 2026-07-30 that never became rows, found by support-evolutiva-cc on 2026-10-06 in the saved WhatsApp record. Filed as one row because they are the same kind of change to the same catalogue, not because they are the same request. (1) Glandulas salivales: add parotidectomia SUPERFICIAL and parotidectomia COMPLETA. They are two distinct entries, not one with a modifier - the client named both. (2) Traumatologia: add retiro de material de osteosintesis. Note this is the SAME item the client answered a separate standing question about on 2026-07-30, where he placed it under 'modulo traumatologia' - so the placement is already decided by him and is not an open question. Do not re-ask it. CATALOGUE WORK IS NOT A CHEAP CHANGE even though the diff looks small, so treat it with the weight the Terra lane established on TERRA-141: every future record references these entries, so the entry is expensive while the request that prompted it is cheap. Follow the project's existing lookup conventions exactly - store the option's stable value code, render the label, never store a uuid or a label - and do not invent a new prefix or category to hold them. Before adding, check whether an equivalent entry already exists under another name; a near-duplicate in a controlled vocabulary is worse than a missing entry because it silently splits the counts that the client will later read as statistics. If either name maps ambiguously onto the existing structure, that is a genuine design fork - raise it rather than picking, since a wrong catalogue entry is expensive to withdraw once records point at it.