---
id: "3180e949-354d-4782-98ce-9e0204cd1986"
name: "Inline Fetch Return Trap"
micro_summary: "Discarded probe: js() quoting/return-wrapping pitfalls and async IIFE workaround"
status: "discarded"
see_also: []
scope: "Probe: JS fetch/async IIFE and browser-harness js() quoting pitfalls. Documented that nested quotes and top-level return auto-wrapping can corrupt expressions; prefer async IIFE or Python helper scripts executed via browser-harness -c to avoid brittle quote escaping."
discard_reason: "Quoting/auto-wrap issue documented and replaced by async IIFE/Python script pattern; archived as probe history."
---
Observed issues when passing multi-line JS with callbacks/returns into browser-harness js(): the helper auto-wrap that detects 'return' can produce syntax errors when the expression contains nested callbacks. This is a v0.1.0-era `-c`/auto-wrap workaround. Current contract (v0.1.8, stdin-only) replaces it: run a short Python wrapper script through stdin (see Runtime Invocation) or use an async IIFE `(async () => { ... })()` to avoid nested quote and auto-wrap problems. Record this probe as discarded history and surface the recommended pattern in the Jira REST Audit Pattern node.