Validate a provider connect-form config
Structural, credential-redacted validation of an operator-submitted config against the provider’s catalog field spec — required fields present, url / select shapes valid, unknown keys reported. It does NOT persist anything and does NOT contact the provider; a valid config does not start an enrichment (the backend is gated on appendsLive). A 200 is returned for both valid and invalid configs; a malformed request body is the only 400. Owner / admin / developer only.
Authorizations
Dashboard JWT token from Clerk
Path Parameters
The provider slug.
Body
The operator-supplied credential/config map keyed by the provider's configFields[].key. Secret values are echoed back redacted. Capped at 40 keys.