The org.jboss.as.controller.registry.ImmutableManagementResourceRegistration#isOrderedChildResource method returns whether a child resource was registered as ordered, but this information is never written to the model description returned by the read-resource-description operation.

Impact:

• Management clients (CLI, web console, etc.) cannot determine if a child resource type supports ordered insertion
• Clients don't know whether they can use the add-index parameter when adding resources of that child type
• This metadata is available internally and used by the server (e.g., AbstractAddStepHandler, SimpleResourceDefinition) but hidden from clients

All of these are a blocker for the console, as it doesn't know whether to preserve order or not and whether to render add-index on the ordered child. All of these issues are reported in console.