Server buttons hit /consent which sets the cookie via HTTP Set-Cookie header then redirects back here - tests the full LB route. Client buttons set document.cookie directly in the browser - same as what the consent gate JS does when a user clicks Accept/Reject.
After client-side changes the panel updates live. After server-side the page reloads.
Go to the homepage to see the real gate (only shows if you are EU/EEA/UK and have no consent cookie).