ACL/Authorizable Packager configuration is not editable on AEM Cloud Service — Page Editor overlays broken

[snehalpd]

Required Information
AEM Version: AEM as a Cloud Service (2025.6+, release 24464 and later)
ACS AEM Commons Version: 6.15.0, 6.16.0 (also affects all 6.x versions)
Reproducible on Latest?: Yes (6.16.0)

We recently upgraded ACS AEM Commons Version to 6.15.0 from 5.0.12.

Expected Behavior
When navigating to Tools > ACS Commons > Packagers and opening an ACL or Authorizable Packager page, the configuration component should be editable. According to the ACS Commons instructions.html [https://adobe-consulting-services.github.io/acs-aem-commons/features/packagers/acl-packager/index.html]:

"To edit the configuration of this page, switch the Page Editor to Edit mode using the top right mode switcher, and edit the configuration component below."
Clicking the configuration component in Edit mode should open the TouchUI _cq_dialog for the configuration sub-component, allowing users to set package name, principal names, ACL handling, etc.

Actual Behavior:
When navigating to Tools > ACS Commons > Packagers and opening a Packager page, the page renders directly at /etc/acs-commons/packagers/.html — without the Page Editor. There is no editor toolbar, no mode switcher, no edit capabilities. The configuration component renders as read-only text (showing current values like Package name, Package group, etc.), and the instructions at the top say:

"To edit the configuration of this page, switch the Page Editor to Edit mode using the top right mode switcher, and edit the configuration component below."

But there is no Page Editor and no mode switcher present.

When manually adding editor.html/ to the URL (e.g., editor.html/etc/acs-commons/packagers/test-package.html), the Page Editor does open with the Edit/Preview mode switcher at the top. However, in Edit mode, nothing on the page is clickable — no component overlays appear, no edit bars, no blue borders. The _cq_dialog for the configuration component exists but is completely unreachable.

Screenshot of the direct page rendering (no Page Editor, no edit capability).

Root Cause Analysis
As per the logs:
The Packager page component hierarchy extends the legacy foundation component:
/apps/acs-commons/components/utilities/packager/acl-packager → sling:resourceSuperType = acs-commons/components/utilities/packager → sling:resourceSuperType = wcm/foundation/components/basicpage/v1/basicpage
basicpage/v1/basicpage relies on granite/ui/components/foundation/contsys for the Page Editor's component overlay system (edit bars, drag handles, click targets). On recent acs aem common versions (6.x), the Page Editor's overlay system no longer generates component overlays (edit bars, click targets, blue borders) for pages rendered through the deprecated foundation/contsys. The contsys component still renders and emits deprecation warnings, but the functional editing capability is broken.

AEM Author Log Evidence
When opening a Packager page in the Page Editor, the following warnings appear repeatedly:
Warning 1 — PageInfoServlet:
ConfiguredProvider com.day.cq.wcm.core.impl.servlets.ContentLanguageServlet not loaded for resource /etc/acs-commons/packagers/
Warning 2 — Deprecated contsys (appears 10+ times per page load):
@deprecated /libs/granite/ui/components/foundation/contsys; please use /libs/granite/ui/components/coral/foundation/contsys instead.
These warnings confirm that the Page Editor's overlay system cannot process the Packager page component because it depends on the deprecated foundation content system.

Additional Context from #3093
In issue #3093, Cloud Manager flagged these exact components:
The component /apps/acs-commons/components/utilities/packager transitively extends the legacy foundation component /libs/wcm/foundation/components/basicpage/v1/basicpage.The component /apps/acs-commons/components/utilities/packager/acl-packager transitively extends the legacy foundation component /libs/wcm/foundation/components/basicpage/v1/basicpage.The component /apps/acs-commons/components/utilities/packager/authorizable-packager transitively extends the legacy foundation component /libs/wcm/foundation/components/basicpage/v1/basicpage.

Steps to Reproduce:

1. Deploy ACS Commons 6.15.0+ to AEM as a Cloud Service
2. Navigate to Tools > ACS Commons > Packagers
3. Create or open an ACL Packager page
4. Observation 1: The page opens at /etc/acs-commons/packagers/.html (direct rendering, no Page Editor). Configuration is displayed read-only. Instructions reference a mode switcher that does not exist on the page.
5. Manually change the URL to editor.html/etc/acs-commons/packagers/.html
6. Observation 2: The Page Editor loads with the mode switcher. Switch to Edit mode.
7. Observation 3: Nothing on the page is clickable. No component overlays or edit bars appear. The configuration component's _cq_dialog cannot be opened.

Environments Affected:

• AEM as a Cloud Service — we are upgrading to latest AEMaaCS releases
• Confirmed across Dev, QA, Stage, and Production environments
• Affects all Packager types: ACL, Authorizable, Query, and Asset

Impact

This is a functional regression — Packager configuration editing is completely non-functional on AEM Cloud Service 2025.6+. Teams cannot configure ACL, Authorizable, Query, or Asset packages through the UI. CRXDE is not available on Cloud Service Production/Stage environments, leaving no built-in way to manage packager configurations.
We are currently creating a client-side workaround that injects an edit form and persists changes via Sling POST, but this is not sustainable long-term.

Could the team advise on:

1. Is there an alternative way to edit Packager configurations on AEM Cloud Service that we may be missing?
2. Is a fix planned, and if so, what is the estimated timeline?