Update RHDH Jira work

Small, precise changes to an issue that already exists. Two jobs live here because they are the same job: a field mutation on a known key.

Route

Both may run in one session — an update that ends "and hand this to someone" is the second workflow, not a new conversation.

Every change is an external write

Invoke /mutation-gate and follow it, then read back the fields you claimed to set.

When another skill hands over a caller-finalized comment body and reports that the user approved that exact body through /mutation-gate, use those bytes for the write only when the current transcript contains that operation's plan and approval. Do not compose, edit, present, or confirm the body again. A label or an assertion of earlier approval is not proof; without the plan and approval in this transcript, run the gate before writing.

A caller handing over a pull request usually wants three writes at once — a comment, a transition to Review, and a web link to the PR URL. Put all three in one stated set so one approval covers them, rather than asking three times.

Boundary with the neighbouring skills

• Opening new work is /rhdh-jira-create.
• Auditing many issues for readiness is /rhdh-jira-refine. This skill changes one issue you already named.
• Sprint carryover, velocity, and fill suggestions are /rhdh-jira-sprint-plan; it invokes this skill for per-issue assignee recommendations rather than scoring them itself.
• acli flags, field IDs, JQL, GraphQL roster queries, and workflow exit criteria are /rhdh-jira-api.
• Creating a PR and attaching the Jira web link in one step is /rhdh-jira-link.

Completion

Complete when every issue key the answer mentions was read back after the change and reported with its resulting status, assignee, and links. Name every operation that ran and every one that failed — a comment that posted followed by a transition that was rejected is a partial update, not a success. A transition blocked by unmet exit criteria is reported with the specific fields that blocked it. An assignee recommendation names the evidence behind it and says plainly when component or sprint metadata was missing, rather than implying certainty it does not have.