fix: Improve Flask/Django HTTP request log detection in System Messages

- Enhanced regex pattern to properly detect Flask/Django HTTP logs like 'INFO: 127.0.0.1:port - "METHOD /path HTTP/1.1" status OK'
- Added fallback detection for HTTP status codes (200, 201, 400, 404, 500)
- Backend server logs now appear prominently in System Messages with [BACKEND] prefix

Author: SFARPak

src/ipc/handlers/terminal_handlers.ts

@@ -113,12 +113,12 @@ export function routeTerminalOutput(event: Electron.IpcMainInvokeEvent, appId: n
   if (terminalType === "backend") {
     // Check for HTTP request logs from Flask/Django/FastAPI/Node.js servers
     const isHttpRequestLog = (
-      // Flask/Django format: "INFO:     127.0.0.1:63021 - "OPTIONS /api/newsletters HTTP/1.1" 200 OK"
-      (message.includes("HTTP/") && (message.includes("OPTIONS") || message.includes("GET") || message.includes("POST") || message.includes("PUT") || message.includes("DELETE") || message.includes("PATCH"))) ||
-      // General server response patterns
-      (message.includes("HTTP/") || message.includes("status") || message.includes("OK") || message.includes("ERROR")) ||
+      // Flask/Django format: 'INFO:     127.0.0.1:63021 - "OPTIONS /api/newsletters HTTP/1.1" 200 OK'
+      (message.includes('HTTP/') && /\s-\s"\w+\s.*HTTP\/\d\.\d+"\s\d+/.test(message)) ||
+      // General HTTP response patterns (fallback)
+      (message.includes('HTTP/') && (message.includes('200') || message.includes('201') || message.includes('400') || message.includes('404') || message.includes('500'))) ||
       // Server startup messages
-      (message.includes("Running on") || message.includes("Server running") || message.includes("listening on") || message.includes("started"))
+      (message.includes("Running on") || message.includes("Server running") || message.includes("listening on") || message.includes("started") || message.includes("* Running on"))
     );
 
     if (isHttpRequestLog) {