Datasets this connection could be pointed at instead of its default (CLO-1014).

Owner-only (finding #3) — the same bar POST .../connection/dataset already gates on, not merely member-visible: this list is exactly what that write accepts, and a member who could list it but not choose from it learns nothing a stricter gate wouldn't also have to justify separately.

The pod is asked directly (a new internal route, same trust model as connector-sync itself) rather than through a user-held API key — this service already reaches the pod in-cluster for every dispatch, and a list call needs no new secret to do the same.