Thanks for the detailed report. The available docs don’t identify HTTP 500s on Community Cloud’s bundled JavaScript assets or explain whether private-app authentication causes them, so I can’t confirm the cause or a static-asset cache reset procedure. The remote-loading troubleshooting guide covers port exposure, CORS, and WebSocket issues—not these asset responses.