fix(cli): classify status 130 as user abort

[cursor]

Summary

• record SystemExit(130) as cli_command_user_aborted instead of cli_command_failed
• preserve the command's exit status
• cover status-130 lifecycle telemetry with an integration test

Tests

• TOGETHER_TELEMETRY_DISABLED=1 uv run pytest tests/unit/test_cli_telemetry.py tests/cli/test_command_telemetry.py
• uv run ruff check src/together/lib/cli/__init__.py tests/cli/test_command_telemetry.py
• uv run ruff format --check src/together/lib/cli/__init__.py tests/cli/test_command_telemetry.py
• uv run pyright src/together/lib/cli/__init__.py tests/cli/test_command_telemetry.py

  

[broly-code-security-scanner]

Broly Security Scan

Note

✅ Clean scan
No vulnerabilities detected in this PR.

Note

Re-scan this PR anytime with /broly scan — useful after /broly undismiss, or to refresh findings without a new push.

Broly — SAST (zai-org/GLM-5.2) · Secrets · SCA · IaC · GH Actions · Base Images · Supply Chain Threats · Exploit Chains · Adversarial Verification

We're continuously improving Broly's accuracy and finding quality — your feedback is valuable. False positives, missed findings, bugs, and feature requests all welcome.