- Shipped
- August 15, 2026 at 6:47 AM UTC
- Author
- kamo
- Commit
- b77f947
Adds "Loading Screen Logo Overlay" directly under the home page one on **************** with the same thirteen options, applying to the logo on the screen shown between page navigations. Default No Overlay, so nothing changes for an org that never opens the field. Its own setting rather than one shared with the home page, because the two surfaces have opposite backgrounds: a white masthead and a dark gradient. The shade that reads on one is rarely the shade that reads on the other, and a single setting would force a choice that is wrong somewhere. The hint under each says so. The type is now LogoOverlay, not HomeLogoOverlay — it governs two surfaces, and a type named for one of them would misdescribe both within a week. The vocabulary, the resolver and the option list are shared; only the column each surface reads is different, so the colours cannot drift apart. loading.tsx reads OrgContext directly rather than through the throwing hook: it mounts during navigation and must never be the thing that breaks a page transition. A missing org means no overlay, which is the default anyway. The two read-only rows render identically, so they now share one helper instead of carrying a copy each. Requires the loading_logo_overlay column (KamoInitializer, applied) and a SecurityService rebuilt against the shared-lib entity.