[BUG] Daemon status shows STOPPED on Windows — ps -o pid command not supported

[Kusts]

Bug Description

ruflo daemon status shows Status: STOPPED immediately after
starting, even though the daemon process is running. The ps -o pid command used for process health checking fails on Windows.

Steps to Reproduce

1. ruflo daemon start
2. ruflo daemon status
3. Result: Status shows ○ STOPPED despite process running

Error Observed

ps: unknown option -- o
Try ps --help for more information.

Root Cause

The daemon uses ps -o pid (Unix-style process status command)
to verify if a process is running. On Windows, the ps command
from Git Bash/msys2 does not support the -o pid syntax the same
way as Unix.

Environment

• Windows 11 Pro 10.0.26200
• Node.js v24.15.0 / npm 11.12.1
• ruflo v3.5.80
• Shell: Git Bash / msys2

Expected Fix

Replace ps -o pid with cross-platform process checking using:

• Windows: tasklist /FI "PID eq <pid>" /FO CSV
• macOS/Linux: ps -o pid (keep existing)
• Or use Node.js native process.kill(pid, 0) which works
  cross-platform

Related

• fix(daemon): prevent self-PID detection causing immediate exit #1467 (self-PID detection — similar pattern)
• Daemon dies immediately on Windows + Node 25 (unsettled top-level await + detached spawn) #1478/fix: P0 daemon startup, ESM controller-registry, memory-bridge #1500 (Windows stdio FD leak — also Windows
  compatibility)