Problem
Ctrl-C is correctly recorded with exit code 130 and outcome interrupted, but terminal lifecycle metadata and history records currently classify it as error. This makes a user-aborted command look like an application failure.
Scope
Use aborted as the terminal status for exit code 130 while preserving interrupted as the technical outcome and keeping the exit code unchanged. Keep actual failures as error and successful commands as ok.
Acceptance criteria
- Ctrl-C and exit code 130 produce status aborted in run metadata and history records.
- The technical outcome remains interrupted and terminal output remains Interrupted.
- Click abort and ordinary nonzero failures retain their existing outcome and error semantics.
- Run-bundle retention accepts aborted terminal metadata.
- Document and regression-test the new status.
Problem
Ctrl-C is correctly recorded with exit code 130 and outcome interrupted, but terminal lifecycle metadata and history records currently classify it as error. This makes a user-aborted command look like an application failure.
Scope
Use aborted as the terminal status for exit code 130 while preserving interrupted as the technical outcome and keeping the exit code unchanged. Keep actual failures as error and successful commands as ok.
Acceptance criteria