Canceling a scan with Ctrl-C can leave it marked as RUNNING indefinitely

Canceling a scan with Ctrl-C can leave the scan permanently marked as RUNNING in the history, even though the CLI exits and no related processes remain.

The CLI prints:

  codex-security: Scan canceled by Ctrl-C.
  codex-security: Partial output was kept at <output-directory>.

However, codex-security scans list continues to show:

  RUNNING · deep
  COVERAGE 0 of 0 reviewed · <file-count> files

No codex-security or codex exec processes are still running.

Environment

• Codex Security CLI: 0.1.1
• Node.js: 22.23.1
• npm: 10.9.8
• OS: macOS
• Authentication: stored ChatGPT credentials
• Scan mode: deep

Steps

1. Start a deep scan.
2. Cancel it once with Ctrl-C.
3. Wait for the CLI to exit.
4. Confirm that no related processes remain.
5. Run codex-security scans list.

Expected

The scan should be recorded as canceled or failed.

Actual

The scan remains permanently marked as RUNNING.

Reproduce the issue by starting a deep scan, canceling it with Ctrl-C, and checking codex-security scans list after the CLI exits. Trace the scan history update and cancellation handling; done means canceled scans no longer remain marked RUNNING and are recorded as canceled or failed.