- Shipped
- August 15, 2026 at 7:08 AM UTC
- Author
- Kamo
- Commit
- 35da2bd
Third and last overlay surface, same vocabulary as its two siblings, plus its branch in the generic patch path. This one is different in where it ends up. The home page and loading screen read their token straight off OrgContext; KamoMeet is a Meet fork with no access to that, so SecurityService resolves this token against the org's palette and bakes the finished colour into the theme config.json the fork already fetches. The token therefore never leaves the platform, and the thirteen options exist in one place rather than being copied into a fork that has already accumulated nine independent copies of the background slideshow. Null resolves to NONE, so every existing org starts with no overlay. The kamomeet_logo_overlay column is already applied (KamoInitializer).