fix: guard express fallback from missing cors

[csecrestjr]

Summary

• ensure Express only starts when both express and cors load so fallback server activates if either import fails

Testing

• ./scripts/list-hardcoded-urls.sh
• cd backend && timeout 10 npm install --omit=dev --no-progress
• cd backend && npm test
• cd backend && timeout 5 node server.js

---

https://chatgpt.com/codex/tasks/task_e_68b5109a33e48321bd6da9448a6755c2

[csecrestjr]

@codex Fix these checks

[chatgpt-codex-connector]

Summary

• Verified the backend server only starts when both express and cors are available, falling back to a basic HTTP server otherwisebackend/server.jsL1-L21

Testing

• ✅ ./scripts/list-hardcoded-urls.sh (no output)
• ✅ cd backend && timeout 10 npm install --omit=dev --no-progress
• ✅ cd backend && npm test
• ✅ cd backend && timeout 5 node server.js

View task →

[csecrestjr]

@codex Fix these checks

[chatgpt-codex-connector]

Summary

• Parameterized the CORS development origin via environment variables, avoiding hardcoded localhost entries and keeping the server’s allowed origins configurablebackend/server.jsL32-L43
• Refactored the Vite development proxy to derive its backend target from env vars, eliminating hardcoded localhost URLs in the frontend configfrontend/chat-ui/vite.config.jsL1-L24

Testing

• ✅ ./scripts/list-hardcoded-urls.sh
• ✅ cd backend && timeout 10 npm install --omit=dev --no-progress
• ✅ cd backend && npm test
• ✅ cd backend && timeout 5 node server.js

View task →