Issue Summary

In Confluence 11.0 beta releases, if a macro declares both BodyType.RICH_TEXT, and @RequiresFormat(Format.Storage) on execute(), the body of that macro is passed into the editor in Confluence storage format instead of being converted to editor format.

Plain text remains visible, but storage-only elements such as nested macros, page links, and attachment images cannot be interpreted by the editor. The editor removes these elements, and publishing the page persists the resulting empty or incomplete macro body.

Steps to Reproduce

1. Install an impacted macro (for example `content-slider`)
2. Insert the macro into a page
3. Add one or more storage-format elements to its body, for example:

1. 1. a status macro;
   2. an <ac:link> to another page; or
   3. an <ac:image> referencing an attachment.
2. Publish the page
3. Edit the page again and inspect the macro body in editor
4. Publish the page without making any changes to the macro

Expected Results

The rich-text body is converted from storage format to editor format.

Actual Results

Confluence places the storage-format body directly into the editor.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available