Skip to content

Persist interrupt diagnostics in the primary run log #206

Description

@codeforester

When a base-cli invocation is interrupted and exits with code 130, the terminal reports Interrupted. but the persistent primary.log may contain no indication of the interruption. Record the interrupt diagnostic through the lifecycle logger before teardown, preserving the existing exit code and terminal behavior, with focused unit and real-SIGINT regression coverage.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething is not working

    Type

    No type

    Projects

    Status
    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions