start.sh and stop.sh cannot see their own processes in Git Bash on Windows

[Chebaleomkar]

In Git Bash on Windows, scripts/start.sh and scripts/stop.sh cannot see the processes they manage. Git Bash ships none of lsof, pgrep or pkill, and its ps cannot see a native process's arguments. Every lookup therefore comes back empty, and each failure is silent:

• stop.sh leaves everything running. With the app, the routine worker and the API server all up, it prints:

  1/4  App
    app: not running on 3010
  2/4  Routine worker
    worker: not running
  3/4  API server
    server: not running on 3001
  

  All three are still serving afterwards. Affected lines: stop.sh:66, stop.sh:106-114 and stop.sh:129-130.
• start.sh starts a second routine worker on every rerun (start.sh:373). Right after starting one, it reports worker: did not stay up (start.sh:382).
• start.sh cannot see a port held by another process (start.sh:138), so it never reaches its "held by something that is not OpenBot" message.
• A secret rotation does not restart the server (start.sh:214-215). The old process keeps running with the previous AGENT_TOOL_TOKEN.

These failures are silent on purpose: every call ends in 2>/dev/null || true. That is right on macOS and Linux, but on Windows it hides the missing tools.

Windows 11, Git for Windows (bash 5.2), Bun 1.4.2. Related: #679 covers the other Windows checkout problems; this one is separate.