Issue Summary

Migrated Forge macros cannot be edited in Confluence page edit mode due to a mismatch between the local-id values stored in the macro storage format. Specifically, the value in ac:adf-attribute key="local-id" does not match the value in ac:adf-parameter key="local-id", causing getMacroContent() to fail and preventing the macro from being opened in edit mode.

Steps to Reproduce

1. Install a Forge macro app that was migrated from Connect to Forge via the Connect-to-Forge migration process.
2. Insert the Forge macro into a Confluence page and save it.
3. Re-open the page in edit mode and attempt to click on the macro to edit its configuration.

Expected Results

The macro opens its configuration panel and can be edited normally in page edit mode, as would be the case for a newly inserted Forge macro.

Actual Results

The macro cannot be edited in page edit mode. Clicking on the macro does not open the configuration panel. Inspecting the storage format of the affected macro reveals a mismatch between the two local-id values.

Workaround

Not feasible:

A manual workaround exists for individual macros:

1. Open the macro config of the affected Connect macro and click Save, then wait for the macro to re-render.
2. Cut the macro from the page.
3. Paste or reinsert the macro back into the page.

After these steps, the macro becomes editable again.