# Bug / FR: `@x12i/api-simulator` — non-JSON / binary / streaming responses

**Status:** Shipped in **1.3.0** (`RawResponseBody` plus verbatim `string`/`Uint8Array` when non-JSON `content-type` is set)  
**Package:** `@x12i/api-simulator` **1.0.0+**  
**Consumers:** firewall XML APIs, Nessus file exports, future binary downloads

## Problem

The Node HTTP adapter **JSON-stringifies** response bodies. Request bodies are JSON-parsed only. Vendors in neo-tools sometimes use XML (FortiGate / PAN-OS) or file downloads. There is no first-class binary, text, or streaming response model.

## Goals

1. Allow `body` as `string` | `Buffer` | `Uint8Array` with explicit `content-type`.
2. Optional raw body passthrough without JSON parse/stringify.
3. Document streaming limitations (or support chunked responses later).

## Current neo-tools stance

Do **not** workaround with a second mock server. If a vendor path requires non-JSON simulation before this lands, treat adoption of that path as **blocked** on this report.

## Acceptance

- Non-JSON fixed/relative/simulation responses round-trip through the Node adapter with correct `content-type`
- In-process `dispatch` returns the body type unchanged