fix(fix): exit 5 when computed fixes go unapplied

[Martin Torp (mtorp)]

Follow-up to #1584. Coana exits with 5 when it computed fixes it could not apply, and lists them under notApplied in its --output-file. Local-mode socket fix already reads that list and fails with "Some computed fixes were not applied" or "No computed fixes were applied". But that result had no exit code, so outputFixResult fell back to 1. A CI job running socket fix could not tell "some fixes were left out" from "the run failed".

What changes

• The not-applied result in local mode now carries code: 5, so socket fix exits with 5, the same code Coana uses.
• Any other failure still exits with 1. PR mode is unchanged.
• [Unreleased] changelog entry under Changed.

Testing

The two not-applied cases in handle-fix-limit.test.mts now assert code: 5. That file passes, and check:tsc and lint are clean.

Expected reviewer effort: Stamp

---

Note

Low Risk
Small, targeted change to local-mode exit semantics and tests; no change to fix application logic or PR mode.

Overview
Local socket fix now exits with code 5 when Coana computed fixes that could not be applied (none or only some), matching Coana’s behavior so CI can distinguish that outcome from a hard failure (still exit 1).

The local-mode failure path in coanaFix now sets code: COANA_FIXES_NOT_APPLIED_EXIT_CODE on the result object, which outputFixResult already maps to process.exitCode. PR mode is unchanged. Tests assert code: 5 for the not-applied scenarios; changelog documents the behavior and notApplied in --output-file JSON.

^{Reviewed by Cursor Bugbot for commit cbbdbfa. Configure here.}