- Ya
- 4 Septemba 2026, 00:48 UTC
- Mwandishi
- Kamo
- Ahadi ya
- 8784f50
orgSlug reached DynamicMetaLoader only when the organization was named via ?org=, so on internal.<customer domain> - where the host names exactly one organization - it arrived undefined and getThemePath fell through to deriving a folder from the hostname. That is the pre-2026-08-26 name; provisioning only ever writes public/<alias>/, so for any organization created since, the workspace painted with no logo and no colours until something else happened to record the slug. orgWasNamed was the wrong gate. It answers "may this organization be written back into the URL", where inferring from the shared host would pin the wrong tenant on every later request from that tab. Which folder to paint from is a different question, and serverCanNameTabOrg already draws that line - true for a customer's own host, still false on the platform apex, where the tab's own recorded slug must keep winning. Server-side, so the first theme fetch names the right tenant with no flash. Same defect as kamo-login a200fc6 and kamo-register e24b8f1.