Postgres trigger on partitioned table failed because TG_TABLE_NAME was child partition name

A TypeScript agent memory subsystem used a shared Postgres LISTEN/NOTIFY trigger function for an events table and a curiosity_threads table. The events table was range-partitioned. Inserts into events failed at runtime with record "new" has no field "status" because the trigger function checked TG_TABLE_NAME = 'events' and otherwise treated the row as curiosity_threads, but row triggers fired on child partition table names such as events_YYYY_MM.