Build Lotus Chat Desktop / prepare (push) Successful in 8s
Build Lotus Chat Desktop / build-linux (push) Successful in 30m37s
Build Lotus Chat Desktop / build-arch (push) Successful in 11s
Build Lotus Chat Desktop / build-windows (push) Successful in 32m6s
Build Lotus Chat Desktop / update-manifest (push) Successful in 8s
The web deploy serves a config.json kept on the server (not in git), which is where the Giphy key lives. The desktop app bundles the repo's config.json, whose gifApiKey is empty, so on desktop the GIF button never appeared even with Settings → GIF Picker switched on. scripts/sync-web-config.mjs copies an allow-list of deployment-only keys (just gifApiKey) from https://chat.lotusguild.org/config.json into cinny/config.json before the Windows and Linux builds. The key is public already (served to every web visitor; Giphy keys are client keys). A fetch failure is a warning, not a build failure. Tested locally: sets the key, is a no-op on a second run, and skips cleanly on a 404. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PPmy3tPq869XDW4njjVaKA