Node type discrepancy for /apps/cq/core/content/nav

[aanchalsikka]

Need your help to resolve a discrepancy in accesscontroltool-apps-package-3.0.4.zip module. The module installs “/apps/cq/core/content/nav” and “/apps/cq/core/content/nav/tools” of type sling:OrderedFolder. While corresponding AEM node is of type “nt:unstructured” This affects the .content.xml that holds information about “/apps/cq/core/content/nav” and its children.

• The tool is installed as a subpackage via all module. Hence, it creates the node structure before all other project modules.
• We are adding some child nodes to “/apps/cq/core/content/nav” and "/apps/cq/core/content/nav/tools" via project codebase. Hence, would prefer to have OOTB structure to avoid any issues.

[kwin]

Although it is correct that /libs/cq/core/content/nav/tools and its parent is of type nt:unstructured (I have checked AEM 6.5.13) I fail to see any incompatibilities in case /apps/cq/core/content/nav/tools and its parent is of the more lenient type sling:OrderedFolder. Do you face any concrete issues due to that? In any case their ancestors (i.e. /libs/cq/core/content up to the root) are of type sling:OrderedFolder. I am happy though to accept a PR adjusting the node types of those two nodes.