fix(smoke): bump Windows ruflo init timeout 60s → 180s (iter 123)

Two Windows smokes spawn `ruflo init --yes --skip-prompts --no-install`
with a 60_000ms timeout:

   scripts/smoke-windows-init-hooks.mjs
   scripts/smoke-windows-hook-execution.mjs

On windows-latest runners, init consistently exceeds 60s (pnpm cache
cold, hnswlib-node gyp probe overhead, antivirus stat penalty) and
exits with `status: null` — meaning the spawn timer fired and the
init handler never finished. No settings.json gets written and the
smokes fail with "settings.json not generated by ruflo init".

Bumped both to 180_000ms (3x headroom). Still catches a genuinely
hung init while letting a slow-but-progressing Windows init complete.

Ubuntu/macos jobs in the same matrix already complete in ~5-10s and
are unaffected by the higher cap.

This is one of the 25 pre-existing main failures the user asked to
fix. After this + the lockfile + Windows shim + gitignore +
env-var-escape-hatches fixes, only the statusline ENETUNREACH
(infra flake hitting MSFT CDN during onnxruntime-node postinstall)
remains as a known intermittent.

Co-Authored-By: RuFlo <ruv@ruv.net>

scripts/smoke-windows-hook-execution.mjs

@@ -58,7 +58,11 @@ const initResult = spawnSync(
     cwd: tmpDir,
     env: { ...process.env, CI: 'true', FORCE_COLOR: '0' },
     encoding: 'utf8',
-    timeout: 60_000,
+    // iter 123 — bumped from 60_000 to 180_000 (same reason as
+    // scripts/smoke-windows-init-hooks.mjs). Cold-start `ruflo init` on
+    // Windows runners exceeds 60s; init exits with status=null (timer
+    // fired) and no settings.json is written. 180s gives 3x headroom.
+    timeout: 180_000,
   }
 );
 

scripts/smoke-windows-init-hooks.mjs

@@ -59,7 +59,13 @@ const result = spawnSync(
       FORCE_COLOR: '0',
     },
     encoding: 'utf8',
-    timeout: 60_000,
+    // iter 123 — bumped from 60_000 to 180_000. Windows cold-start `ruflo
+    // init` consistently exceeds 60s (pnpm cache cold, hnswlib-node gyp
+    // probe overhead, antivirus stat). The init exited with status=null
+    // (= the spawn timer fired) which means it hadn't even finished the
+    // init handler, never mind written settings.json. 180s gives 3x
+    // headroom while still catching a genuinely-hung init.
+    timeout: 180_000,
     // Don't fail if the command exits non-zero — init may partially succeed
   }
 );