Instruction file imported from jagalliers/FrontierBoss (.cursor/rules/process-management.mdc). Copyright stays with the author.

Process Management

All server lifecycle operations MUST go through the service controller:

node bin/frontierboss.cjs <command>

Allowed commands

NEVER do any of these

• node server/index.ts or tsx server/index.ts — bypasses state tracking, creates orphans
• npm run dev or npm start — same problem; use frontierboss dev / frontierboss start instead
• kill, killall, pkill on server processes — use frontierboss stop which handles the full process tree and cleans up state
• Manually spawning node dist/server/index.js — this is what the supervisor does internally

Dev mode notes

• frontierboss dev runs concurrently with tsx watch + vite; file changes auto-restart the server
• Do NOT manually restart after editing server files — tsx watch handles it
• If the server appears stuck, check with frontierboss status first, then frontierboss stop && frontierboss dev

Port conflicts

If you see "Port 3000 is already in use", always resolve with:

node bin/frontierboss.cjs stop

Then start again. The stop command sweeps both tracked processes and any orphans on the port.