Merge pull request #1239 from manaflow-ai/cmux/update-gh-comment-bp8xb

Post one GitHub comment and update it

Author: austinywang

apps/worker/src/screenshotCollector/claudeScreenshotCollector.ts

@@ -212,9 +212,14 @@ If no UI changes exist: Set hasUiChanges=false, take ZERO screenshots, and expla
 <PHASE_2_CAPTURE>
 If UI changes exist, capture screenshots:
 
-1. Read CLAUDE.md or AGENTS.md (may be one level deeper) and install dependencies if needed
-2. Run tmux ls to check if the dev server is running. Dev server should be running on default. Otherwise, start the dev server. Look for instructions in README.md, CLAUDE.md, or framework-specific files (package.json, Makefile, Gemfile, composer.json, requirements.txt, etc.). Use dev_command above if provided.
-3. Look for a list of ports you need to check in the repo. Wait for the server to be ready (curl -s -o /dev/null -w "%{http_code}" http://localhost:PORT should return 200)
+1. FIRST, check if the dev server is ALREADY RUNNING:
+   - Run \`tmux list-windows\` and \`tmux capture-pane -p -t <window>\` to see running processes and their logs
+   - Check if there's a dev server process starting up or already running in any tmux window
+   - The dev server is typically started automatically in this environment - BE PATIENT and monitor the logs
+   - If you see the server is starting/compiling, WAIT for it to finish - do NOT kill it or restart it
+   - Use \`ss -tlnp | grep LISTEN\` to see what ports have servers listening
+2. ONLY if no server is running anywhere: Read CLAUDE.md, README.md, or package.json for setup instructions. Install dependencies if needed, then start the dev server.
+3. BE PATIENT - servers can take time to compile. Monitor tmux logs to see progress. A response from curl (even 404) means the server is up. Do NOT restart the server if it's still compiling.
 4. Navigate to the pages/components modified in the PR
 5. Capture screenshots of the changes, including:
    - The default/resting state of changed components
@@ -224,7 +229,7 @@ If UI changes exist, capture screenshots:
    - Responsive layouts if the PR includes responsive changes
 6. Save screenshots to ${outputDir} with descriptive names like "component-state-${branch}.png"
 7. After taking a screenshot, always open the image to verify that the capture is expected
-8. If screenshot seems outdated, refresh the page and taking the screenshot again.
+8. If screenshot seems outdated, refresh the page and take the screenshot again.
 9. Delete any screenshot files from the filesystem that you do not want included
 </PHASE_2_CAPTURE>