manage-error-debugging

name: manage-error-debugging description: Manage error debugging per foundation command. triggers:

• manage error debugging
• /manage_error_debugging
• manage-error-debugging

Manage Error Debugging Automation

Manage the error debugging automation monitoring script (start, stop, status, logs).

Command Usage

/manage_error_debugging [action]

Actions:

• start - Start the error debugging watcher in background
• stop - Stop the running watcher
• status - Check if watcher is running and show status
• logs - Show recent logs from the watcher
• restart - Stop and start the watcher
• (no action) - Show status (default)

Prerequisites

• Error debugging automation enabled in foundation-config.yaml
• scripts/trigger_error_debug_cli.js exists and is executable
• Node.js installed

Workflow

Action: start

1. Check if already running:

   • Check for PID file: .cursor/error_reports/watcher.pid
   • If PID file exists, verify process is still running
   • If running, exit with message: "Error debugging watcher is already running (PID: {pid})"

2. Verify configuration:

   • Load foundation-config.yaml
   • Check development.error_debugging.enabled === true
   • If disabled, exit with error

3. Create necessary directories:

   • Ensure .cursor/error_reports/ exists
   • Ensure log directory exists (if configured)

4. Start watcher in background:

   • Run: node scripts/trigger_error_debug_cli.js --watch > .cursor/error_reports/watcher.log 2>&1 &
   • Capture PID of background process
   • Write PID to .cursor/error_reports/watcher.pid
   • Output: "Started error debugging watcher (PID: {pid})"

5. Verify start:

   • Wait 1 second
   • Check if process is still running
   • If not running, read log file and show error

Action: stop

1. Check if running:
   • Read PID from .cursor/error_reports/watcher.pid
   • If PID file doesn't exist, exit: "Error debugging watcher is not running"