A JavaScript Step for the checks nothing else covers

Every mainstream test automation tool ships an escape hatch for logic a UI step can't express. Thunders now has one too.

• Write and edit in place: the JavaScript Step opens a code editor directly in the Test Case, with a locked function scaffold so the contract with the runner can't break by accident.
• Full context, not just the page: read and write Thunders variables, query the DOM, call APIs, and read console output, all from inside the script.
• Structured pass or fail: return a clear success or a failure with a reason, and see the result, logs, and any errors in a dedicated panel as soon as the step runs.
• Same variable syntax: reference [variables] inside your script exactly like any other step.

Catch what pure UI testing misses: read the total shown on a cart page, call the API for that same cart, and fail the step if the two disagree. The page can render fine while the backend is wrong, a JavaScript Step is what catches that.

#Sprint28