Bilko CSP Cleanup — MC #10440 (next.config.js basicconsulting.no to alai.no migration)

Bilko CSP Cleanup — MC #10440 (next.config.js basicconsulting.no → alai.no migration)

Documentation for MC #10440 — follow-up to MC #10428 (Gemini code-review) to clean up stale/misleading CSP entries and allowedDevOrigins in apps/web/next.config.js after the basicconsulting.no → alai.no domain migration.

Context

During a Gemini-driven code review of Bilko's Next.js configuration (MC #10428), several stale domain entries were flagged in the development CSP (Content Security Policy) and allowedDevOrigins array. These entries pointed to the old basicconsulting.no domain, which has been retired in favor of alai.no.

Changes Applied

File: apps/web/next.config.js

Removed Dead Hosts (basicconsulting.no)

Scoped Wildcard to Explicit Host

The allowedDevOrigins array contained a broad *.alai.no wildcard. Narrowed to the single explicit host actually used:

Corrected Misleading Comment

A comment incorrectly described the alai.no hosts as "dev tunnels" when they actually point to a remote Cloud Run demo environment. Corrected for accuracy.

Production CSP Untouched

The production CSP branch was left unchanged. All modifications were scoped to the development environment only.

Audited (Not Modified)

Additional vestigial CSP entries were identified but not removed — outside this task's scope:

Flagged as future cleanup candidates.

Validation

Known Open Issue — MC #104570

Important: during this work, bilko-demo-api.alai.no itself was found dead (SSL_ERROR_SYSCALL; DNS resolves to an orphaned Google-hosted IP, 142.251.38.115).

This contradicts MC #104221 (2026-06-28, 3 days prior), which reported this host as "LIVE 200". MC #104570 (H priority, opened 2026-07-01) tracks investigating whether the Bilko live demo is currently broken.

The CSP entry referencing bilko-demo-api.alai.no was correctly left in place (CodeCraft/Proveo decision) — removing a currently-referenced entry without confirming permanent death risks breaking an expected path. Do not treat this host as confirmed-live until MC #104570 resolves.

Deployment

No separate deployment required — config-only change, lands via normal PR merge to azdo/main.

Documented: 2026-07-01


Revision #1
Created 2026-07-01 07:28:45 UTC by John
Updated 2026-07-01 07:28:45 UTC by John