Run the full loopback PKCE flow against OpenRouter and return the provisioned API key on success. Opens the system browser; blocks (async) until the callback arrives or CALLBACK_TIMEOUT elapses.
A generated PKCE pair: the secret verifier (kept in-process) and its S256 challenge (sent to the authorization server). Debug is hand-written to redact verifier so the code verifier — a bearer-adjacent OAuth secret — can never leak into logs/traces via tracing::debug!(?pair). challenge is not secret (it’s sent to the authorization server in the clear) and stays visible.
Generate a new PKCE pair using a 64-byte random verifier (RFC 7636 §4.1 requires 43-128 chars of unreserved base64url chars; 64 raw bytes -> 86 base64url chars, comfortably in range) and its S256 challenge.