{"version":"2.1.280","anchor":"shell-exit-status-mapping-factored-into-a-shared-helper-with","canonical_anchor":"shell-exit-status-mapping-factored-into-a-shared-helper-with","heading":"Shell exit status mapping factored into a shared helper with a new \"stopped\" outcome","tier":"internal","area":"Bash Tool","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/shell-exit-status-mapping-factored-into-a-shared-helper-with","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Shell exit status mapping factored into a shared helper with a new \"stopped\" outcome\n\nShell exit-status logic reorganized into shared helpers, adding a distinct 'stopped' outcome\n\n**What**\n\nThe logic that decides how a bash command's exit status gets reported (killed, failed, or completed, plus an optional note about the exit code) has been pulled into a shared helper function. A second helper wraps it to relabel a `killed` outcome as `stopped` for the places that use that wording instead.\n\n**Why**\n\nThis consolidates duplicated exit-status logic into one place and gives callers that expect \"stopped\" terminology a consistent way to get it, rather than each handling the translation separately.\n\n- Area: Bash Tool\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}