* and loads them as domtrip Documents. Individual strategies can create domtrip Editors
 * from these Documents as needed for superior formatting preservation.
 */
public class PomDiscovery {

    private PomDiscovery() {
        // noop
    }

    /**
     * Discovers and loads all POM files starting from the given directory.
     *
     * @param startDirectory the directory to start discovery from

 *
 * <h3>Utility Classes</h3>
 * <ul>
 *   <li>{@link org.apache.maven.cling.invoker.mvnup.goals.StrategyOrchestrator} - Coordinates strategy execution</li>
 *   <li>{@link org.apache.maven.cling.invoker.mvnup.goals.PomDiscovery} - Discovers POM files in multi-module projects</li>
 *   <li>{@link org.apache.maven.cling.invoker.mvnup.goals.DomUtils} - XML manipulation utilities</li>
 * </ul>
 *
 * <h2>Usage Examples</h2>
 *

        Path startingDirectory = options.directory().map(Paths::get).orElse(context.invokerRequest.cwd());

        Map<Path, Document> pomMap;
        try {
            pomMap = PomDiscovery.discoverPoms(startingDirectory);
        } catch (IOException | DomTripException e) {
            context.failure("Failed to discover POM files: " + e.getMessage());
            return 1;
        }