Currently, the Confluence REST API v2 (e.g., /wiki/api/v2/pages/{id}{}) only returns the lifecycle status of a page (e.g., CURRENT, DRAFT). It does not provide the "Editorial Status" or "Content Status" lozenge (e.g., "In Progress", "Ready for Review", "Approved").

As a result, Rovo MCP tools and other API-based integrations cannot read or act upon the editorial state of a page, even though this status can be updated via the page-status-update action.

Suggested Change:
Update the Confluence REST API v2 to include the content status field in page responses so that it can be consumed by external tools and Rovo Agents.