fix: move critical operations into try-block in get-modules

Moves `ensureDirectory()` and `validateModuleUrls()` into the try-block
to ensure the finally block executes even if these operations fail early.

Previously, if directory creation or URL validation failed immediately,
the finally block was never reached, causing the output file to never be
written and resulting in "ENOENT: no such file or directory" errors.

This ensures `modules.stage.3.json` is always written, even with an empty
modules array, allowing the pipeline to continue instead of failing completely.

Author: KristjanESPERANTO

scripts/get-modules.ts

@@ -525,22 +525,21 @@ async function processModules() {
     `Validating up to ${totalTargets} module URLs (concurrency=${cliOptions.urlConcurrency}, rate-limit=${rateLabel})`
   );
 
-  const validated = await validateModuleUrls({
-    modules,
-    limit: cliOptions.limit,
-    urlConcurrency: cliOptions.urlConcurrency
-  });
-
   const validModules: ModuleEntry[] = [];
   const skippedModules: ReturnType<typeof createSkippedEntry>[] = [];
   let moduleCounter = 0;
   let consecutiveErrors = 0;
   const MAX_CONSECUTIVE_ERRORS = 10;
 
-  await ensureDirectory(MODULES_DIR);
-
   // Use try-finally to ensure output is written even if errors occur
   try {
+    await ensureDirectory(MODULES_DIR);
+
+    const validated = await validateModuleUrls({
+      modules,
+      limit: cliOptions.limit,
+      urlConcurrency: cliOptions.urlConcurrency
+    });
     for (const {
       module,
       ok,