@trawlme/cli 3.8.1 → 3.8.2

package/dist/commands/doctor.d.ts

@@ -36,12 +36,21 @@ export interface Run {
 }
 /**
  * Resolve a known anti-bot vendor (or auth) name from a worker `blockType`
- * string. Returns null when the run isn't blocked, or when it's blocked by
- * something other than a known vendor (e.g. `proxy-domain-gate`,
- * `rate_limited_per_host`) — those stay on the genuine-error path since we
- * can't honestly attribute them to a specific "no reliable bypass" wall.
+ * string. Returns null when the run succeeded, when there is no `blockType`
+ * signal at all, or when `blockType` names something other than a known
+ * vendor (e.g. `proxy-domain-gate`, `rate_limited_per_host`) — those stay on
+ * the genuine-error path since we can't honestly attribute them to a specific
+ * "no reliable bypass" wall.
+ *
+ * `blocked` is deliberately NOT consulted here (#177): it is a mid-run,
+ * attempt-level signal the worker only stamps on one envelope shape, so it
+ * reads `false` on the great majority of genuinely walled runs (the early-block
+ * throw path sets `blockType` but never `blocked` — 63 of 64 walled runs
+ * measured on prod). `status === true` wins instead: a run that ultimately
+ * returned data was not walled, even if an earlier tier's `blockType` stamp
+ * survived on the row.
  */
-export declare function detectWallVendor(run: Pick<Run, 'blocked' | 'blockType'>): string | null;
+export declare function detectWallVendor(run: Pick<Run, 'status' | 'statusDetail' | 'blockType'>): string | null;
 /**
  * Autofix activity metadata — from the persisted ai_fix_end activity.
  * aiUsage (cost) is stripped server-side; all diagnostics are kept.

package/dist/commands/doctor.js

@@ -30,14 +30,31 @@ const WALL_VENDOR_PATTERNS = [
 ];
 /**
  * Resolve a known anti-bot vendor (or auth) name from a worker `blockType`
- * string. Returns null when the run isn't blocked, or when it's blocked by
- * something other than a known vendor (e.g. `proxy-domain-gate`,
- * `rate_limited_per_host`) — those stay on the genuine-error path since we
- * can't honestly attribute them to a specific "no reliable bypass" wall.
+ * string. Returns null when the run succeeded, when there is no `blockType`
+ * signal at all, or when `blockType` names something other than a known
+ * vendor (e.g. `proxy-domain-gate`, `rate_limited_per_host`) — those stay on
+ * the genuine-error path since we can't honestly attribute them to a specific
+ * "no reliable bypass" wall.
+ *
+ * `blocked` is deliberately NOT consulted here (#177): it is a mid-run,
+ * attempt-level signal the worker only stamps on one envelope shape, so it
+ * reads `false` on the great majority of genuinely walled runs (the early-block
+ * throw path sets `blockType` but never `blocked` — 63 of 64 walled runs
+ * measured on prod). `status === true` wins instead: a run that ultimately
+ * returned data was not walled, even if an earlier tier's `blockType` stamp
+ * survived on the row.
  */
 export function detectWallVendor(run) {
-    if (run.blocked !== true || !run.blockType)
+    // A run that returned data was not walled. `status === true` is not the whole
+    // predicate: trawl_node flips a degraded-but-non-empty run to
+    // `status:false, statusDetail:'regression'` (scraps.service.js, #1112) via a
+    // patch that never clears `blockType` — so keying on `status` alone would
+    // print "no reliable bypass" next to "Regression: length N vs baseline M",
+    // which is the same contradiction this guard exists to remove.
+    if (run.status === true || run.statusDetail === 'regression')
         return null;
+    if (!run.blockType)
+        return null; // no signal at all
     for (const [pattern, label] of WALL_VENDOR_PATTERNS) {
         if (pattern.test(run.blockType))
             return label;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@trawlme/cli",
-  "version": "3.8.1",
+  "version": "3.8.2",
   "description": "Trawl CLI — manage scraps from the terminal",
   "type": "module",
   "bin": {