pipeline-window-control

Run node pipeline-control.js --status to print a table of all tracked windows showing story ID, phase, PID, process liveness, database status, phase target, and elapsed minutes. It also warns if any zombie windows are detected.

Run node pipeline-control.js --check-zombie. A zombie is a window whose database story status already reached the phase target but whose PID is still running; the script gracefully closes child processes first, then force-kills the process tree if needed.

They are two parallel systems with separate ledgers. pipeline-control.js tracks PIDs in logs/pipeline-active.json, while close-worker.ps1 manages worker_runs database rows with five preconditions and CAS final-state writes. Windows registered in worker_runs must be closed via close-worker.ps1, never with --kill.

No. The script relies on Windows-specific tooling: PowerShell Get-Process and Get-CimInstance for liveness checks and child-process termination, plus taskkill for force-killing process trees. It also requires better-sqlite3 to read the story database.

pipeline-control.js only reads the logs/pipeline-active.json tracker and has no knowledge of the worker_runs database table. The two tracking ledgers are not synchronized, so killing by PID leaves the worker_runs lifecycle state inconsistent.