Issue Summary:

A Forge confluence:customContent module is accessible to authenticated users but not to anonymous users, even when:

•  anonymous access is enabled for the Confluence site
•  anonymous access is granted for the target space
•  the Forge module includes unlicensedAccess: [anonymous]
•  the custom content type includes supportedSpacePermissions

Steps to Reproduce

1.   Create a Forge app with:
   • confluence:globalPage
   • confluence:customContent
2. Configure the custom content module with:
   • supportedSpacePermissions: [read, create, delete]
   • unlicensedAccess: [anonymous]
3. Configure the global page with:
   • unlicensedAccess: [anonymous]
4. Deploy and install the app in Confluence Cloud.
5. Enable anonymous access for the Confluence site.
6. Grant anonymous access to the target Confluence space.
7. As an authenticated user, create a custom content item in the public space.
8. Open the generated custom content URL as an authenticated user.
   • Result: page renders successfully.
9. Open the exact same URL in an anonymous/incognito browser session.
   • Result: anonymous user sees “We couldn't find what you're looking for”.

Expected Results

Anonymous users should be able to access the Forge custom content page when:

•  the site allows anonymous access
•  the space allows anonymous access
•  the module is configured with unlicensedAccess: [anonymous]
•  the custom content type is configured with supportedSpacePermissions

Actual Results

• Authenticated users can open the created custom content page successfully.
• Anonymous users opening the exact same custom content URL receive:
  • We couldn't find what you're looking for

Workaround

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