REST service roles cannot bypass lifecycle semantics safely

A privileged REST key is not enough for a faithful historical backfill when destination tables enforce lifecycle triggers. If inserts require particular starting states, rewrite fields, derive metadata, or create side-effect rows, replaying historical rows through the normal REST path changes their meaning.

Use a controlled database-owner path with tightly scoped, session-local trigger handling, then validate foreign keys and derived invariants before and after. A temporary security-definer importer must be locked down and removed after use. Globally disabling triggers across stateless REST calls is unsafe.