docs: require HTTPS redirect URIs except localhost loopback dev

Align SDK integration guidance with provider redirect URI hardening: use HTTPS callback URLs in production and limit HTTP callbacks to localhost loopback during development/testing.

README.md

@@ -130,6 +130,7 @@ This wrapper now delegates to `BlackWall\Auth\AuthClient`.
 - Always validate OAuth `state` in callback handlers.
 - Handle provider callback errors (`error`, `error_description`) explicitly; treat `access_denied` as an expected user/authorisation outcome rather than a transport failure.
 - Expect `access_denied` even after the consent page is displayed if provider-side project membership or tenant scope changes before consent submission.
+- Register only HTTPS redirect URIs in provider client settings (HTTP should be used only for localhost loopback during development).
 - For OIDC providers, include a per-request `nonce` in authorisation requests.
 - Always use HTTPS in production.
 - Store refresh tokens securely.

docs/INTEGRATION_GUIDE.md

@@ -140,6 +140,7 @@ try {
 - Avoid printing tokens in production pages.
 - Expect `429 Too Many Requests` from provider control endpoints under abuse protection; implement backoff/retry instead of tight loops.
 - If you call provider WebAuthn login challenge/verify endpoints directly, use `POST` only.
+- Configure OAuth client redirect URIs as HTTPS in production; reserve HTTP for localhost loopback testing only.
 - Rotate client secrets for confidential clients.
 - Add a unique `nonce` to each OIDC authorisation request.
 - Validate `state` on every callback request.