Capabilities registered when the model is being populated are not recorded in the Galleon feature-spec

Specifically, capabilities registered in recordCapabilitiesAndRequirements are not recorded in the Galleon feature-specs.

The reason is Galleon generates the feature specs using the metamodel instead of the effective model. The metamodel is the resource definitions and the effective model is the current configuration created once the model is populated with all the attribute values.

recordCapabilitiesAndRequirements is executed when the model is populated, then, capabilities defined there are not exposed in the Galleon feature-specs.

The goal here is to identify which capabilities are affected and rework them, for example moving them to the resource definition itself, to allow Galleon to record them in the feature-specs.

Some capabilities could require a different work if they cannot be moved out from recordCapabilitiesAndRequirements.