CI Pipeline / backend-test (push) Successful in 5m18s
CI Pipeline / frontend-test (push) Successful in 23s
CI Pipeline / frontend-build (push) Successful in 29s
CI Pipeline / backend-lint (push) Successful in 7s
CI Pipeline / quality-gate (push) Successful in 2s
CI Pipeline / quality-gate (pull_request) Successful in 2s
CI Pipeline / backend-test (pull_request) Successful in 5m14s
CI Pipeline / frontend-test (pull_request) Successful in 22s
CI Pipeline / frontend-build (pull_request) Successful in 29s
CI Pipeline / backend-lint (pull_request) Successful in 8s
The isPlatformBrowser guard in App.ngOnInit() was blocking stationConfig.load() on the server, so SSR always rendered with DEFAULT_CONFIG (hardcoded colors, assets, content). Two-part fix: - main.server.ts: Add APP_INITIALIZER that blocks server rendering until station config is fetched from the API. Only runs on the server — is a no-op in the browser to avoid blocking the client. - app.ts: Move stationConfig.load() before the isPlatformBrowser guard so ngOnInit also calls it on the server as a safety net. This ensures SSR HTML contains real DB values (colors, hero icon, station name, etc.) instead of build-time defaults — eliminating the stale-asset flash reported by users.