Localz — Clerk vs Keycloak decision

Projects/Localz.md lists an open problem under Current Focus:

Resolve auth decision: Clerk vs Keycloak (contradiction §B)

The vault already has directly relevant research sitting in TechResearch/Clerk_Based_Auth/:

• clerk_based_auth — the combined auth architecture plan across FullStackFusions subdomains (Localz included), with the provider/audience map.
• clerk_production_setup_walkthrough — a real, hands-on production setup walkthrough (DNS records, OAuth app config, dashboard gotchas) written from standing up hermes-wiki's Clerk instance. Explicitly says "reuse this when setting up Courses and Localz."

Localz's Development-Setup-Resources-and-Capacity.md documents a live Keycloak dev container already running, which is the actual source of the Clerk-vs-Keycloak contradiction. The Clerk walkthrough doesn't resolve which one to pick, but it removes most of the "Clerk is unproven/costly to set up" friction — the adapter-interface pattern (Localz-Required-Stack.md) plus this walkthrough means switching to Clerk is now a known, documented quantity, not an open unknown.

Suggested next step: when resolving §B, read clerk_production_setup_walkthrough.md alongside the Keycloak dev-capacity notes before deciding.