Issue Summary

The Create with Rovo (CWR) pipeline internally uses a constrained HTML dialect that maps 1:1 to ADF and supports the full range of Confluence rich elements — two-column layouts, info/warning/note panels, status lozenges, code blocks, and other macros. This format is used by the internal CWR skill (general Rovo Chat) but is not exposed to Custom Agents. Custom Agents using the Create Page skill are limited to Markdown-level output, which cannot represent layouts, panels, or macros. As a result, Custom Agents are architecturally incapable of creating pages with rich formatting, regardless of how the system prompt is written. This is a fundamental capability gap between general Rovo Chat and Custom Agents using the same underlying Create Page skill.

Steps to Reproduce

1. Create a Rovo Custom Agent with a system prompt instructing it to create a Confluence page with a two-column layout and an info panel.
2. Ask the agent to create the page.
3. Observe the published page output.

Expected Results

The Custom Agent is able to produce a Confluence page with a two-column layout and an info panel, equivalent to what general Rovo Chat (CWR) can produce using the same Create Page skill.

Actual Results

The Custom Agent produces a flat Markdown-only page. Layouts and panels are absent. The agent has no mechanism to express these elements regardless of prompt configuration, because the constrained HTML format used internally by CWR is not available to Custom Agents.

Workaround

Build a Forge app with a rovo:action module that accepts structured data from the agent and programmatically constructs the page via the Confluence REST API using proper Storage Format. This is the only deterministic path to rich formatting today, but requires significant engineering investment and is not a viable option for customers expecting a configuration-level capability.