[Question]:

# Issue Title
[Bug] CoPaw crashes silently without any error logs on Windows 10

# Issue Body

## Description
CoPaw crashed suddenly without any ERROR, EXCEPTION, or CRASH records in the logs. The application terminated abruptly with no graceful shutdown logs.

## Environment
- **OS**: Windows 10 (AMD64)
- **CoPaw Version**: 1.0.0.post2
- **Installation Path**: D:\installSoft\CoPaw
- **Working Directory**: C:\Users\17638\.copaw\workspaces\default

## Timeline
| Event | Time |
|-------|------|
| Last normal log | 2026-04-01 12:03:51 |
| Application restarted | 2026-04-01 12:07:17 |
| Downtime | ~3 minutes 26 seconds |

## Log Analysis

### Last activity before crash (2026-03-30_17-51-12.log)
```
2026-04-01 12:03:51 | INFO | ContextChecker.call | ========== cost=0.171615s ==========
```

### After restart (2026-04-01_12-07-17.log)
```
2026-04-01 12:07:17 | INFO | application.py:148 | start | Init ReMe with config: {...}
2026-04-01 12:07:17 | INFO | application.py:266 | start | ReMe Application started
```

## Key Findings
1. **No error records in logs** - Searched all log files, no ERROR, EXCEPTION, CRASH, FAIL, or Traceback keywords found
2. **Normal operation before crash** - Last log entry was a normal ContextChecker call (0.17s)
3. **No crash dump files** - Checked CoPaw installation directory and system CrashDumps folder, no .dmp files found
4. **Abrupt termination** - Logs ended suddenly without normal shutdown logs (e.g., "Shutting down", "Application stopped")

## Possible Causes
Since logs ended abruptly without error information, the crash was likely caused by **external factors**:

1. **Process terminated externally** - Task Manager, antivirus, or other process management tools
2. **Out of Memory (OOM)** - System ran out of memory and killed the process
3. **System sleep/hibernate** - Computer entered low-power mode
4. **Parent process closed** - Terminal/command prompt window was closed
5. **Windows Update or system restart**
6. **Python interpreter crash** - Segfault from underlying C extensions (but usually generates dump files)

## Suggestions for Improvement

### Short-term
1. **Add exception handling** - Add comprehensive try-catch blocks in main loop and critical paths
2. **Add shutdown logs** - Distinguish between normal shutdown and abnormal termination
3. **Enable crash dumps** - Configure procdump or similar tools on Windows

### Long-term
1. **Add heartbeat monitoring** - Write heartbeat logs periodically to help identify crash timing
2. **Memory usage monitoring** - Record memory usage peaks to help diagnose OOM issues
3. **Signal handling** - Capture SIGINT, SIGTERM signals for graceful shutdown
4. **Auto-restart mechanism** - Detect abnormal exits and automatically restart

## Steps to Reproduce
Cannot reproduce consistently - crash occurs randomly.

## Additional Information
- Checked Windows Event Log (pending user confirmation)
- No crash dump files generated
- Log level is INFO, may need DEBUG level for more details

## Log File Locations
`D:\installSoft\CoPaw\logs\2026-03-30_17-51-12.log` (before crash)
`D:\installSoft\CoPaw\logs\2026-04-01_12-07-17.log` (after restart)