fix: exit with non-zero status for signal-terminated processes

[branchseer]

TL;DR

Improve exit status handling for processes terminated by signals on Unix systems.

What changed?

• Added exit_status_to_code() function to properly handle processes terminated by signals on Unix systems, following the convention of returning 128 + signal number
• Changed ExecutionEventKind::Finish to use ExitStatus instead of i32 to preserve signal information
• Updated the reporter to handle the new exit status format and properly display exit codes
• Fixed execution context to pass None for status when no process was spawned (cache hit or in-process execution)
• Added e2e tests for signal-terminated processes on Unix platforms

How to test?

Run the new e2e test on a Unix system:

cd crates/vite_task_bin/tests/e2e_snapshots/fixtures/signal-exit
vite run abort

This should show a process terminated with exit code 134 (128 + 6 for SIGABRT).

Why make this change?

Previously, when a process was terminated by a signal on Unix systems, the exit code information was lost. This change ensures that signal terminations are properly reported with the standard convention of 128 + signal number, providing more accurate information about process failures.

[branchseer]

• fix: exit with non-zero status for signal-terminated processes #118 👈 (View in Graphite)
• docs: update CLAUDE.md #113
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[branchseer]

Merge activity

• Jan 19, 10:19 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Jan 19, 10:20 AM UTC: Graphite rebased this pull request as part of a merge.
• Jan 19, 10:21 AM UTC: @branchseer merged this pull request with Graphite.