detonate 0.1.2

Prove an injected web payload actually EXECUTES (alert(1) fires), not just reflects (a shared XSS-execution oracle over Santh's jsdet sandbox).
Documentation

detonate: prove an injected web payload actually executes, not just reflects.

WAF-bypass ≠ exploit, and reflection ≠ execution: a payload can pass a WAF and even echo back in the response yet never reach a context where its JavaScript runs. This crate is the execution oracle that separates "the bytes came back" from "the script ran", it extracts the JavaScript an HTTP response would execute, runs it in Santh's [jsdet] sandbox (QuickJS compiled to WASM, every API call observed) behind a DOM/browser bridge, and reports whether a dialog sink (alert / confirm / prompt) fired, the minimal, false-positive-free proof of cross-site scripting.

Shared so any Santh tool can gate a finding on real execution. The canonical use is the classic proof payload alert(1):

let proof = detonate::detonate_html(
    r#"<div><script>alert(1)</script></div>"#,
    "https://target.example/reflect",
);
assert!(proof.proves("1")); // alert fired with argument "1"