Retire/reactivate writes archive rows with no actor or reason: RETIRE_SQL runs on a bare pool.query so setArchiveContext cannot reach it, and terra_29 will break the feature outright

TERRA-78 terra Todo high

Guard suite unexercised on a non-empty population: the writer exists and is owned, but no natural terraPracticas write has been observed

TERRA-46 terra Todo high

Vocabulary-table archive-on-UPDATE: terraCirugias has an INTEGER PK against a uuid NOT NULL sink, so the generic archive function cannot be reused and the sink assumption itself is in question

TERRA-66 terra Todo high