v0.10.0

✨ Added

• issue view now surfaces the discovery data Jira already returns on the read instead of discarding it: data.issue.transitions[] lists the workflow moves valid from the current status, and data.issue.editmeta.fields lists the editable fields with their required flag, accepted operations, and allowed values — so an agent or script can plan an edit or transition from a single read. The human view gains a one-line transitions summary.
• The agent contract is now versioned: jira agent schema reports the revision at data.schema_version and the full jira agent guide output stamps the same value, so an agent can detect a breaking change instead of discovering it mid-workflow. The scheme (what a major, minor, or patch bump means for the contract) is documented in the guide's core_contract section.
• Two discovery gaps are closed. A new jira cache resolutions command lists the tenant's resolution names (they vary per instance), so a resolve transition that requires a resolution field can be planned instead of guessed. Cached statuses now carry status_category (new, indeterminate, or done) alongside id and name, and the guide documents that status ids repeat across workflows — map a name to its category from the cache, and resolve the id per issue via the transition list.
• The --dry-run/--force safety rails now cover local state mutations, not just Jira writes. cache clear --dry-run reports what a live clear would remove without touching any file, config set --dry-run runs the full key and value validation and reports the current and new value without writing config, auth switch --dry-run resolves the target profile without changing the default, and auth logout --dry-run names the credential a live logout would revoke without opening the secret backend. The destructive pair — cache clear and auth logout — now requires --force in agent, non-TTY, or --no-input context, matching the gate on destructive Jira mutations; headless scripts that clear caches or log out must add the flag. Interactive terminals proceed without prompts.

🔥 Changed

• jira update no longer asks for a yes/no confirmation in an interactive terminal — running the command is the consent, and the self-replace is already checksum-verified and rollback-safe. --dry-run still previews without changing anything, and headless, agent, and --no-input runs still require --force.

📜 Commits

• 8f344ca feat(cli): skip the interactive update confirmation prompt
• 5ee4b89 feat(cli): surface transitions and editmeta in issue view output
• c59d8e5 feat(cli): version the agent schema and guide contract
• 60d72a1 feat(cli): add resolutions cache and keep status categories in cached statuses
• 0bee06f docs(cache): document the resolutions resource and cached status categories
• f6e85fb docs(nav): add the cache resolutions reference page to the nav
• d85e373 feat(cli): extend dry-run and force coverage to cache, config, and auth mutations
• c0481bd docs: document issue-view discovery output, schema_version, and cache resource count

Full Changelog: v0.9.2...v0.10.0