- Ya
- 4 Septemba 2026, 20:19 UTC
- Mwandishi
- Kamo
- Ahadi ya
- c516041
kamo-login and kamo-register run on their own hosts with no OrgContext, so this file is the only route their branding takes - the same one KamoMeet already uses. The token is resolved against the org's palette HERE and the finished hex is written, which keeps the thirteen-token vocabulary out of two more codebases that would each need their own copy of it. Baking a resolved colour is not the mistake the stored token avoids: this file is regenerated on every branding save, colour changes included, so the value cannot go stale. Absent means no overlay, so an org that has chosen none gains no key and its logos render untouched - which is every org until one is chosen. Tests cover the three surfaces staying apart: they share one builder, and an org overlaying its sign-in site must not have its KamoMeet logo painted as a side effect.