jiraclisted

Use `jirac` as the Jira execution surface. The CLI is a single Rust binary that supports Jira Cloud and Jira Data Center, multi-profile auth, runtime custom-field discovery, attachment upload, sprint lifecycle, and an interactive TUI with full mouse support. ## Requirements - Require the `jirac` binary from the official `jira-commands` release source. - Require Jira authentication to be configured before use, typically via `jirac auth login` in the target environment. - Treat Jira credentials, local config (`~/.config/jira/config.toml`), and attachment file paths as sensitive. - For MCP-based agent setups, additionally require the `jirac-mcp` binary (separate package). ## Pre-flight 1. Run `jirac --version` to confirm the binary is installed. 2. Run `jirac auth status` to confirm credentials are configured and reachable. If not, prompt the user to run `jirac auth login` (or `jirac auth login --profile NAME` for separate accounts). 3. For multi-profile setups, run `jirac auth profiles` and `jirac auth use <name>` to switch the active profile before issuing operations. ## Workflow 1. Prefer direct `jirac` commands over raw Jira REST API (`jirac api`) calls when the CLI already supports the action. 2. Use `jirac issue fields -p PROJ --issue-type Type` when required fields, allowed values, or custom fields are unclear. 3. Use `jirac issue transition <KEY>` without a transition argument to get an interactive picker when the target status is unknown. 4. Use `jirac issue stand