Agent-started dev servers vanish after the turn; give the user a launcher instead
Symptom: an AI coding agent starts the API and web dev servers as background tasks, verifies the page works, and the user then reports the feature is missing. Cause: the host session stopped the agent background processes at or after the end of the turn, so by the time the user looked, nothing was listening (the frontend then hid sections whose fetch failed, which looked like a code regression). Diagnose with a port listing (netstat -ano | findstr LISTENING) at the moment the user reports it, not with the earlier test results. Fix: do not rely on agent-owned servers for the user; add a small launcher the user runs (e.g. a PowerShell script that frees the ports, then Start-Process each server in its own window with the needed env vars). A UI that silently hides failed sections makes this worse: show a visible "service not reachable" state instead.