v0.10.1

🪲 Fixed

• Locally-detected command errors now carry typed classifications instead of being guessed from their message text, which fixes five wrong exit codes. auth login with a --backend that differs from the profile's stored backend, and issue edit --assignee me on a profile with no saved account id, now exit 3 (validation, flag_value_invalid) instead of 1 (auth). auth whoami against a profile that has no base URL now exits 2 (profile_incomplete) instead of 1 (auth). jira agent guide with an unknown section and jira search saved with an unknown query name now exit 3 (validation, arg_value_invalid) instead of 2 (not found) — the lookups are local, not Jira resources. Every --force gate keeps its validation_failed/exit 3 contract, and a genuinely absent Jira user on watcher commands keeps not_found/exit 2.
• The command error classifier no longer guesses an error's category from its message text — a fragile heuristic that misrouted some validation errors to the wrong exit code. A bad auth_type (rejected on config load or via config set) and auth login with the conflicting --secret-stdin and --credential-env flags now exit 3 (validation) instead of 1 (auth), where before the word "auth" or the flag name "credential-env" pushed them onto the authentication path. Multi-key batch commands that partially fail now carry the exit code of their worst failure directly instead of re-deriving it from the summary line, so mixed-failure batches classify correctly. Any error the CLI does not explicitly classify now defaults to validation (exit 3) rather than being sorted by keyword.

📜 Commits

• 94fb3e2 fix(cli): type command errors so exit codes are not substring-guessed
• 6eba875 fix(cli): retire the substring error classifier

Full Changelog: v0.10.0...v0.10.1