fix: remote Chrome PDF via CDP, sync MCP endpoint URL on boot

- Add CHROME_WS_URL env var support for PDF report generation via
  Chrome DevTools Protocol over WebSocket (falls back to local binary)
- Update seeded MCP server endpoint URLs on boot when MCP_ENDPOINT_URL
  env var differs from stored value (previously only seeded once)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

compliance-dashboard/src/infrastructure/server.rs

@@ -150,16 +150,23 @@ async fn seed_default_mcp_servers(db: &Database, mcp_endpoint_url: Option<&str>)
 
     let collection = db.mcp_servers();
 
-    for (name, description, tools) in defaults {
-        // Skip if already exists
-        let exists = collection
-            .find_one(doc! { "name": name })
-            .await
-            .ok()
-            .flatten()
-            .is_some();
+    let expected_url = format!("{endpoint}/mcp");
 
-        if exists {
+    for (name, description, tools) in defaults {
+        // If it already exists, update the endpoint URL if it changed
+        if let Ok(Some(existing)) = collection.find_one(doc! { "name": name }).await {
+            if existing.endpoint_url != expected_url {
+                let _ = collection
+                    .update_one(
+                        doc! { "name": name },
+                        doc! { "$set": { "endpoint_url": &expected_url } },
+                    )
+                    .await;
+                tracing::info!(
+                    "Updated MCP server '{name}' endpoint: {} -> {expected_url}",
+                    existing.endpoint_url
+                );
+            }
             continue;
         }