jiralisted

# Jira Integration (CLI Backend) Uses the [`vanducng/jira-cli`](https://github.com/vanducng/jira-cli) fork, which preserves upstream compatibility and adds native inline local-image comments. Confirm the active binary supports the feature before an image write: ```bash jira issue comment add --help | rg -- '--image' ``` ## Invocation Flags ```text vd:jira --project acme --type bug create ticket for the failed import vd:jira --project acme --type task create ticket for the cleanup ``` - `--project ALIAS`: Load `~/.config/vd/jira-rules/<alias>.jira-rules.md`. - `--type bug|task`: Set the issue type and apply that type's local defaults. - Infer the project alias from the issue key only when a loaded rule maps that prefix. Ask when missing or ambiguous. Copy `references/project.jira-rules.example.md` to the local rules directory and customize it. Never commit local company rule files. ## Authentication (MANDATORY - run FIRST) Before any Jira operation: 1. Resolve `--project` and load `~/.config/vd/jira-rules/<alias>.jira-rules.md` completely. 2. Read the base URL, token environment variable, email environment variable, and optional board defaults from that file. 3. Source the configured environment file and export `JIRA_API_TOKEN`, `JIRA_USER_EMAIL`, and `JIRA_BASE_URL` without printing their values. 4. Prepend the same setup to every Jira CLI and curl command in the session. Refuse to proceed when the rules file is missing connection metadata. Never print, commit, atta