unbound-cli 1.1.6 → 1.1.7

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "unbound-cli",
-  "version": "1.1.6",
+  "version": "1.1.7",
   "description": "CLI tool for Unbound - AI Gateway management",
   "main": "src/index.js",
   "bin": {

package/src/commands/discover.js

@@ -11,6 +11,13 @@ const LAUNCH_AGENT_LABEL = 'ai.getunbound.discovery';
 // (e.g. Linux). Treated as a skipped scan, not a failure.
 const DISCOVERY_EXIT_UNSUPPORTED_OS = 3;
 
+// Self-imposed discovery run timeout (seconds), forwarded through install.sh to
+// the discovery process so `unbound onboard` / `unbound discover` can't hang
+// indefinitely. Discovery enforces this itself — on expiry it releases its lock,
+// reports the run as failed, and exits non-zero. Kept in sync with
+// setup/mdm/onboard.py's DISCOVERY_TIMEOUT_SECONDS.
+const DISCOVERY_TIMEOUT_SECONDS = 1800;
+
 // Classifies a discovery subprocess exit code:
 // 'success' (scan ran), 'unsupported' (skipped on this OS), or 'failure'.
 function classifyDiscoveryExit(code) {
@@ -146,7 +153,16 @@ async function runDiscoveryScan({ apiKey, domain }) {
     console.log('');
   }
 
+  // Don't pass --timeout: install.sh is fetched from coding-discovery-tool/main,
+  // and an older discovery there would reject the unknown flag (argparse exits
+  // non-zero) and fail the scan. Discovery self-bounds via its own default (kept
+  // equal to DISCOVERY_TIMEOUT_SECONDS), so this is correct regardless of merge
+  // order. Surface the bound so the wait isn't a mystery; on expiry the discovery
+  // process prints its own line (stdio is inherited) and exits non-zero.
   const args = `--api-key ${shellEscape(apiKey)} --domain ${shellEscape(domain)}`;
+  if (!isWindowsNative()) {
+    output.info(`Discovery stops on its own after ${Math.round(DISCOVERY_TIMEOUT_SECONDS / 60)} minutes if it can't finish.`);
+  }
   await runDiscoveryScript('install.sh', args);
 }