Issue Summary

When a custom Rovo agent with the "Comment on work item" skill is triggered via a workflow transition (assign-to-agent path), the agent responds with an action key of `jira-atlassian-work-item-create-comment` and calls the outdated/deprecating endpoint /conversation/{conversationId}/action with it, which returns a 404 "Action not found" error. The "Comment on work item" skill is never invoked.

The same agent works correctly when invoked directly via Rovo Chat, as it uses a different code path that properly invokes the skill.

Steps to Reproduce

1. Create a custom Rovo agent in Studio with the "Comment on work item" skill added
2. Enable Surfaces → Work items toggle for the agent
3. Add the agent to a workflow transition (e.g., via "Trigger agent action" rule on a status transition)
4. Configure the agent's instructions to read the work item and post a comment with its findings
5. Move a work item into the status that triggers the agent

Expected Results

The agent reads the work item context and successfully posts a comment on the work item using the jira-atlassian-work-item-create-comment action, as it does when invoked via Rovo Chat.

Actual Results

The agent responds, but no executable action is generated. The following error is returned:

POST /gateway/api/assist/rovo/v1/chat/conversation/{conversationId}/action → 404
{
    "errorMessage": "Action not found",
    "errors": [
        "convoai.rest.not.found"
    ],
    "statusCode": 404
}

The agent displays the message: "I wasn't able to execute jira-atlassian-work-item-create-comment because of a technical problem on my end. What would you like to do next?"

Workaround

Currently, there is no known workaround for this behavior. The agent can be invoked directly via Rovo Chat as an alternative, but it cannot be triggered automatically via workflow transitions to comment on work items.