🐛 Bug Fix

Problem

`start.bat` silently fails or provides poor user experience in the following scenarios:

1. No Admin Privilege Check

• On Windows 10/11, standard users may have write permission issues
• Script provides no warning

2. No Port Conflict Detection

• `GATEWAY_PORT=18789` may be occupied
• `LLM_PORT=18080` may be occupied
• Script fails silently

3. No Sensitive File Cleanup

• API Keys, tokens, logs remain on disk
• Risk when plugging into other computers

Solution

1. Permission Detection

• start.sh: Add admin check for Windows (Git Bash/MSYS2)
• start.bat: Add admin check with user prompt
• Show warning if not running as Administrator
• Allow user to continue anyway

2. Port Conflict Detection

• start.sh: Check `GATEWAY_PORT` and `LLM_PORT` conflicts
• start.bat: Check port conflicts with `netstat`
• Show helpful messages when conflicts detected
• Allow user to continue anyway

3. Cleanup Scripts

• cleanup.sh: New cleanup script for Linux/macOS
  • Level 1: Light cleanup (logs, PIDs)
  • Level 2: Deep cleanup (configs, tokens, backups)
• cleanup.bat: New cleanup script for Windows
  • Same functionality as bash version
  • Interactive menu with 3 options

Testing

• Manual testing on both Windows and Linux
• Port conflict detection tested
• Permission check tested

Impact

• User Experience: Better error messages, no silent failures
• Security: Zero-trace design for portable use
• Reliability: Fewer support questions

Fixes #43