In the original implementation of the coverage-check command, PackageLoopingType.includeAllSubpackages is used to discover all sub-packages recursively. However, because the tool relies on a strict opt-in list in custom_coverage_minimums.yaml, any discovered sub-package is skipped unless it is explicitly listed in the configuration file, script/configs/custom_coverage_minimums.yaml. See related discussion.

To ensure that all test/ directories associated with an opted-in package are properly covered, we should re-define how the coverage check should handle these sub-packages. We need to decide whether sub-packages of an opted-in package should automatically inherit the parent package's coverage minimum and be checked, or if they must continue to be listed individually in the configuration file. This issue tracks the design and implementation of coverage enforcement for nested sub-packages of opted-in packages to ensure no test/ directories are left uncovered.