Estuary Supabase capture fails through the pooler: use direct connection

When setting up an Estuary capture from Supabase, never use the pooled connection string: get the direct connection hostname with the pooler checkbox off, provision a dedicated IPv4 address, and confirm wal_level=logical with a REPLICATION role. If a second capture is added from the same database, give it its own replication slot instead of sharing the default flow_slot. In restricted setups create the publication and watermarks table manually with the SQL from the docs page before publishing the capture.

Context: Official docs (Supabase capture connector page): Estuary's Postgres CDC capture connector cannot connect through Supabase's connection pooler, because the pooler does not support the replication features the connector relies on. Agents wiring up a Supabase capture with the default pooled connection string from the Supabase dashboard will fail. The docs require a direct connection hostname, found in Settings > Database with the Display connection pooler checkbox unchecked, plus a dedicated IPv4 address for the project. The usual prerequisites also apply: wal_level=logical, a user role with the REPLICATION attribute, a replication slot (one per capture), a publication, and a watermarks table the user can write to.