viyv-browser-mcp 0.9.0 → 0.10.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.js CHANGED
@@ -11817,7 +11817,7 @@ import { homedir } from "os";
11817
11817
  import { resolve } from "path";
11818
11818
  import { fileURLToPath } from "url";
11819
11819
  var PKG_VERSION = (() => {
11820
- if (true) return "0.9.0";
11820
+ if (true) return "0.10.1";
11821
11821
  try {
11822
11822
  const here = fileURLToPath(import.meta.url);
11823
11823
  const pkgPath = resolve(here, "..", "..", "package.json");
@@ -31488,6 +31488,14 @@ abort:
31488
31488
 
31489
31489
  Supported scenario step types: navigate, action, fetch, wait, loop. Loop variable sources: static, previous_fetch, target_options (max nesting 3, max iterations 500, cartesian product across variables).
31490
31490
 
31491
+ HttpFetch runtime (F2):
31492
+ - Fetch definitions may carry type_name='http_fetch' + http_config instead of DOM extraction fields. Loop-merged params resolve {{var}} in url / body_template with per-value URL-encoding.
31493
+ - extractor_code (when set) is eval-equivalent in the page MAIN world \u2014 bundles must originate from the trusted authoring pipeline gated by MCP JWT auth. Extraction precedence: extractor_code > selector > raw responseText.
31494
+ - Response shape: results[result_key] = { rows: unknown[] } \u2014 extractor array, selector string[], or [responseText] in raw fallback. Scraper should consume result.data.rows.
31495
+ - HTTP 4xx/5xx are forwarded as ok:true with httpStatus populated (caller decides). Network / extractor failures surface as ok:false with prefixed error strings ('fetch failed: ...' / 'extractor threw: ...' / 'scripting failed: ...' / 'async extractor not supported in v1').
31496
+ - sm_probe_inline automatically skips http_fetch (no DOM locators to probe).
31497
+ - ScenarioFetchStep.result_key_mode ('overwrite' | 'append' | 'concat', default 'overwrite') controls how results[result_key] accumulates across loop iterations. Runtime dispatch lands in F3; pre-F3 all modes behave as 'overwrite'.
31498
+
31491
31499
  Full reference: docs/inline-sm-execution.md`;
31492
31500
  var SM_RUN_INLINE_RETURNS = `{
31493
31501
  success: boolean
@@ -31502,7 +31510,7 @@ var SM_RUN_INLINE_RETURNS = `{
31502
31510
  elapsedMs
31503
31511
  }
31504
31512
  }
31505
- fetches: { [fetch_id]: { extractedCount, schemaValid, missingFields? } }
31513
+ fetches: { [fetch_id]: { extractedCount, schemaValid, missingFields?, httpStatus?, responseBytes?, elapsedMs? } } // http* fields: HttpFetch only (F2+)
31506
31514
  scenario: {
31507
31515
  stepsExecuted, stepsSkipped,
31508
31516
  errors: [{ stepIndex, message }] // includes non-fatal 'content-script-not-ready: ...'