Thanks for the detailed report—you’ve already ruled out several common causes. My understanding is that the pending, changing JavaScript file isn’t specifically covered by the available troubleshooting docs, so I can’t tell from these sources whether this is a hosting-side fault. The docs do note that persistent loading placeholders can stem from WebSocket/CORS setup, but that guidance is for remotely hosted setups and may not apply to Community Cloud.