Stand up venus-pm-triage-listen.service — per-app clone of PLUTO-191 ticket-notify daemon (venus first-mover for bs-mr4xk6nnuu2)

Fleet brainstorm bs-mr4xk6nnuu2 (ticket→PM triage workflow): venus is the daemon host + hub host + already has scripts/pm-triage-listen.ts staged. Stand up venus's own instance: env-swap (PMT_PM=pm:venus, PMT_SENDER=venus-pm-triage-cc, ORIGIN_ARO=aro:venus, PMT_DATABASE_URL_DIRECT=venus DIRECT 5432 DSN as pm_triage_reader — NOT the 6543 pooler, LISTEN/NOTIFY unsupported there), point at venus Supabase. Needs the fn_notify_pm_triage() trigger (AFTER INSERT accessRequests+supportTickets → pg_notify('pm_triage')) applied to venus DB, a pm_triage_reader role, EnvironmentFile overlay (secrets git-excluded), and the systemd unit. Keep it a DEDICATED daemon (seam-A2: do NOT fold into the applog error rail). Proves the per-app clone end-to-end before mars/ayudarg replicate. Owner: db-venus (trigger+role) + nw-venus (systemd unit) per maintainer lanes. Gated on the bs-mr4xk6nnuu2 decision close (lease-on-bwi-mirror + autofix allowlist shape). Class-A (touches DB trigger + a new service).