Get app config by domain

{
  result: {
    _id: string,
    displayName: string,
    domainName: string,
    creatorId: string,
    bundleId: string,
    primaryColor: string,
    coinSymbol: string,
    coinName: boolean,
    defaultAccessProfileOpen: boolean,
    defaultAccessAssetsOpen: boolean,
    usersCanFree: boolean,
    isUserDataEncrypted: boolean,
    parentAppId: boolean,
    isAllowedNewAppCreate: boolean,
    isBaseApp: boolean,
    defaultRooms: [{jid: string, pinned: boolean}],
    createdAt: string,
    updatedAt: string,
    appToken: string,
    xmppHost: string,
    translateLanguages: string[],
  },
}

xmppHost is the install's XMPP domain, taken from the backend's XMPP_HOST env (rendered from XMPP_DOMAIN at install time). It is install-wide rather than per-app, so clients can open the chat connection without a build-time env of their own. Omitted when the install did not set XMPP_HOST.

translateLanguages lists the BCP-47 tags the install's separately deployed translation server can translate into (deploy.yml translate.languages, pushed into the database on every install / update). Also install-wide rather than per-app. Unlike xmppHost the key is always present: [] means no translation server is configured, and an absent key would leave clients guessing between that and an API too old to report it.

This is NOT chat.translates / the languages block returned by login and /me. That one is the set of languages the product's UI works in; this one describes a different deployment's capabilities, and the two lists may legitimately differ.