fix(connection): support required Jira transition fields

[guoxianzhe]

Problem

The Jira transition_issue Action only accepts issueIdOrKey and transitionId and sends only { transition: { id } }. Jira Server workflows with a transition screen can expose a valid transition but reject execution when required fields such as resolution are missing. Connection callers cannot discover or submit those fields, so valid completion transitions fail as invalid_input.

Observed against EP-802 on 2026-09-14: list_issue_transitions returned transition 5 (解决问题 -> 已解决), while transition_issue was deterministically rejected and the issue remained 处理中.

Scope

• Let list_issue_transitions return transition field metadata needed by callers.
• Let transition_issue accept optional Jira transition fields and include them in the Jira REST payload.
• Keep identity and idempotency ownership unchanged.
• Preserve the current no-fields behavior for workflows that do not require transition fields.
• Add focused adapter contract and request-payload tests.

Acceptance criteria

• AC-1: transition discovery exposes Jira transition field metadata.
• AC-2: callers can submit optional fields with a transition.
• AC-3: the adapter sends { transition: { id }, fields } when fields are supplied and omits fields otherwise.
• AC-4: focused adapter tests, typecheck, provenance verification, and git diff --check pass.
• AC-5: no Provider credentials or raw unsafe Provider response bodies are exposed.

Validation

• pnpm --filter @agent-infra/openconnector-adapter test
• pnpm --filter @agent-infra/openconnector-adapter check-types
• git diff --check

Blocked by

None

[github-actions]

Claude encountered an error after 1s —— View job

---

I'll analyze this and get back to you.

[github-actions]

Blocker reconciliation audit

• Issue: fix(connection): support required Jira transition fields #496
• State: frontier
• Reason: blockers-completed
• Signature: d36db5d864fe4e39e3751a0d0a3fa07ff453a4f81fba36ae1c1f895a32a98362

[github-actions]

Codex Worker accepted this blocker-state dispatch.

[github-actions]

Codex Worker stopped and requires human triage.

Reason: The Worker could not validate the Issue frontier.

[guoxianzhe]

Deployment validation on 2026-09-14:

• Commit 4263885 was fast-forwarded to connection.
• Tag v0.0.19 published all GHCR images successfully in run 34822440689.
• HCI API was upgraded to v0.0.19 and became Ready with zero restarts.
• Live MCP validation found the existing Jira Connection/Grant remains pinned to provider release and ActionVersion v6; the v7 runtime correctly did not execute the immutable old release and returned Provider executor is unavailable.
• The API was rolled back to v0.0.18; Helm revision 44 is deployed, public health is 200, and the existing Jira transition READ succeeds again.

The source fix is complete, but production activation requires an explicit Jira Connection/Grant reauthorization to v7 (or completion of the separately governed compatible-upgrade design). Automatic migration is not safe because this change expands the Action input schema.