$ adversarial qip run probe.wasm

QIP probe debugger

Run a QIP Content component directly in the browser. The component gets explicit input, writes explicit output, and has no filesystem, network, clock, or environment access. This is the same deterministic contract the adversarial CLI uses to execute sandboxed attack detectors.

Select a QIP Content component. Expected exports: memory, input_ptr, input_bytes_cap, output_utf8_cap, render(u32) -> u64.

Expected contract
  1. Host writes UTF-8 input at the address returned by input_ptr().
  2. Host calls render(input_size) with the input byte length.
  3. Component returns a packed i64: low 32 bits = output size, next 31 bits = output pointer, top bit = failure.
  4. Host reads output from the returned pointer and size.

Output

No probe run yet.