dsh-moli 1.1.2 → 1.1.3

package/index.js

@@ -110,6 +110,7 @@ const FETCH_OUTPUT_SCHEMA = {
     path: { type: 'string' },
     chars: { type: 'integer' },
     bytes: { type: 'integer' },
+    empty: { type: 'boolean' },
     truncated: { type: 'boolean' },
     error: { type: 'string' },
     hint: { type: 'string' },

package/lib/moli.js

@@ -314,7 +314,45 @@ export function runFetch(options) {
   const bytes = outcome.stdout.length;
   const stderr = outcome.spawnError === undefined ? outcome.stderr : `${outcome.spawnError} | ${outcome.stderr}`;
 
-  if (outcome.status !== 0 || bytes === 0) {
+  // Empty stdout on a zero exit is not a failure: a page can legitimately have
+  // no content in the requested format, which is exactly what a client-rendered
+  // page yields under `noJs` with a text dump. moli is right to print nothing
+  // for it, and the old code answered with "moli exited with status 0 and no
+  // output" plus a hint to re-check the install, sending the caller after a host
+  // that was never broken.
+  //
+  // Both decisions live in this one branch on purpose. Splitting them -- empty
+  // stdout treated as success here and stderr checked further down -- lets the
+  // case below (silent stdout, a complaint on stderr, exit 0) fall through to
+  // the normal success path with the complaint silently dropped.
+  if (outcome.status === 0 && bytes === 0) {
+    if (stderr !== '') {
+      return {
+        ok: false,
+        url: args.url,
+        error: stderr,
+        sandboxTlsBlock: isSandboxTlsFailure(stderr),
+        unreachable: false,
+        possiblyUnreachable: false,
+        hint: 'The engine exited cleanly but produced no output and explained why on stderr; the text above is its own message.',
+      };
+    }
+    return {
+      ok: true,
+      url: args.url,
+      kind: 'text',
+      dump: args.dump ?? 'html',
+      content: '',
+      chars: 0,
+      bytes: 0,
+      empty: true,
+      note: 'moli succeeded and produced no output, so the page had no content in this format. '
+        + 'A page whose content is built by JavaScript yields nothing when noJs is set; '
+        + 'the same URL renders normally without it.',
+    };
+  }
+
+  if (outcome.status !== 0) {
     const sandboxTls = isSandboxTlsFailure(stderr);
     // A blocked host fails at connect time ("Failed to connect" / RST) or, when
     // the socket never opens, as a readiness timeout with nothing to show. A
@@ -459,7 +497,11 @@ export function probe(exe, probeUrl, insecureTls = false) {
   if (insecureTls) probeArgs.push('--insecure-disable-tls-host-verification');
   const outcome = fetchOnce({ exe, args: probeArgs, timeoutMs: 20000 });
   const stderr = outcome.spawnError === undefined ? outcome.stderr : `${outcome.spawnError} | ${outcome.stderr}`;
-  const ok = outcome.status === 0 && outcome.stdout.length > 0;
+  // A zero exit means moli reached the host and fetched it. Requiring non-empty
+  // stdout as well would report httpsOk:false for a page that simply has no
+  // text — a probe URL is not guaranteed to carry content, and the field is
+  // documented as "can reach HTTPS", which is what the exit status proves.
+  const ok = outcome.status === 0;
   const revocation = /CRYPT_E_REVOCATION_OFFLINE|revocation/iu.test(stderr);
   return {
     exe,
@@ -467,7 +509,9 @@ export function probe(exe, probeUrl, insecureTls = false) {
     httpsOk: ok,
     probeUrl,
     detail: ok
-      ? 'HTTPS fetch succeeded from the DSH host process.'
+      ? (outcome.stdout.length > 0
+        ? 'HTTPS fetch succeeded from the DSH host process.'
+        : 'HTTPS fetch succeeded from the DSH host process (the probe URL returned no text).')
       : revocation && !insecureTls
         ? `${stderr} | This is a certificate-revocation check failing (offline CRL/OCSP responder); retrying with the no-verify flag normally clears it.`
         : stderr,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-moli",
-  "version": "1.1.2",
+  "version": "1.1.3",
   "type": "module",
   "description": "DeepSeek Harness tools for the local Moli headless browser: rendered fetches, markdown, semantic trees, screenshots, and PDFs.",
   "license": "MIT",