preferences — the user pastes a long-lived credential (API key) into the
host-rendered settings form; the provider reads it via ctx.getPreference.
interactive — the provider owns an interactive sign-in (OAuth and friends)
and must implement SourceAuth. The host renders sign-in/sign-out and an
identity line instead of, or alongside, the preferences form.
preferences— the user pastes a long-lived credential (API key) into the host-rendered settings form; the provider reads it viactx.getPreference.interactive— the provider owns an interactive sign-in (OAuth and friends) and must implementSourceAuth. The host renders sign-in/sign-out and an identity line instead of, or alongside, the preferences form.