/**
 * Jira tracker adapter — projects Jira onto the neutral TrackerAdapter contract.
 * ============================================================================
 *
 * Thin wrapper over jira.js. ~90% of the work is the toNeutral mapping; the
 * write methods mostly delegate to the JIRA skill's first-class tools
 * (jira_transition_issue already does the fuzzy status matching we want, so we
 * do NOT re-implement it). The single gap with no tool is attaching a PR remote
 * link, which we issue against the exported `jiraFetch` chokepoint directly,
 * with a comment fallback.
 *
 * State mapping: Jira's `statusCategory.key` is a 3-value enum — `new` /
 * `indeterminate` / `done` (see backend/.../jira-tickets-service.js:70). That
 * maps cleanly onto three of the five neutral buckets. Jira has no native
 * "blocked" category, so 'blocked' is only ever derived from a status NAME
 * match (best-effort), matching how the other adapters surface it.
 *
 * Auth/config is inherited from jira.js (resolveIntegrationToken('jira')); this
 * file adds no new env keys.
 */
export declare const jiraAdapter: any;
export default jiraAdapter;