# Fixture Loom integration quickstart Free local/self-hosted software by JSDaj. This is separate from the browser-local static studio: API/MCP callers send HAR and policy data to the operator running this process. No public jsdaj.com upload service exists. Agent hosts may transmit tool inputs according to their own privacy settings; no host certification is claimed. Node 24.22.1 / Chromium tested. Install with `npm ci --ignore-scripts`. Exact browser binaries are a separate prerequisite: `npx playwright install chromium`. No other engine/runtime compatibility claim. CLI: `node src/cli.js inspect examples/synthetic.har.json`; `node src/cli.js build examples/second.har.json examples/second-policy.json ./fresh-pack`. Existing output refused. Pack: `npm ci --ignore-scripts`, install Chromium, `npm test`. That is a generic route smoke test, not application UI assertions. Import `install` from adapter.js into your own tests before creating pages; fresh context, serviceWorkers block. No internet fallback. HTTP: set `JSDAJ_API_TOKEN` to a random secret of at least 32 characters, then `node integrations/http.mjs`. Default 127.0.0.1:3210. Explicit `JSDAJ_HOST`, `JSDAJ_ALLOWED_HOSTS`, `JSDAJ_ALLOWED_ORIGINS` configure self-hosting. No wildcard allowed; Origin rejected by default. Token required even on loopback. No logs of input bodies, credentials or filenames. Terminate process to clear transient data. Builds are stateless; chunk requests rebuild output and retain no artifact store. ``` python3 integrations/examples/request.py > /tmp/fixture-request.json curl --fail-with-body http://127.0.0.1:3210/v1/inspect -H "Authorization: Bearer $JSDAJ_API_TOKEN" -H 'Content-Type: application/json' --data-binary @/tmp/fixture-request.json ``` POST /v1/inspect `{har:HARText}` returns minimal inventory. POST /v1/validate-policy `{policy}`; /v1/preview and /v1/build `{har,policy}`. Build returns file inventory and manifest. POST /v1/export `{har,policy,file,offset:0,limit:16384}` returns text chunk and nextOffset (null when complete). Offsets are JavaScript UTF-16 characters; concatenate text in order, encode UTF-8 once complete. Names must be actual generated file names; never interpreted as server paths. See openapi.json for strict input schemas. Read-only /healthz; authenticated /openapi.json. MCP stdio: `node integrations/stdio.mjs`. Configure host with command `node`, args absolute path to integrations/stdio.mjs. Official SDK tools: inspect, validate_policy, preview, build, export; same inputs/results. HTTP MCP URL http://127.0.0.1:3210/mcp with Authorization Bearer token; Streamable HTTP. `node integrations/examples/client.mjs` exercises the official HTTP client. Tests exercise both transports and reconstruct every file. Limits: 12 MiB aggregate transport; HAR serialized max 10 MiB; 1000 entries; body max 5 MiB; output pack max 20 MiB; individual adapter result max 1 MiB; chunks max 16384 characters. 60 requests/minute per instance, 4 inflight, 16 connections, 30-second socket/request deadline (not CPU preemption). No compression. Stable errors include INVALID_REQUEST, INVALID_JSON, REQUEST_TOO_LARGE, UNAUTHORIZED, INVALID_HOST, INVALID_ORIGIN, RATE_LIMITED and core errors. No stack dumps. Use explicit smaller selection when inventory/signature output exceeds bounds. Matching preserves exact request body bytes, meaningful query keys and same-key order; headers/cookies do not select responses. Exact repeats; ordered aborts at exhaustion; unmatched aborts. JSON responses only; HEAD, 204/205/304 and GET/DELETE/OPTIONS request bodies refused. No authentication-dependent responses, production proxy or stateful backend. Bodies and URLs can contain secrets; review manually. No complete scrub guarantee. Imports supported: HAR and v1 policy only. Export is deterministic file map / UI tar with manifest body/policy checksums, not signed authenticity. No arbitrary pack/ZIP import or included-code execution. Synchronous operations produce no queued jobs/events: webhooks inapplicable. Playwright adapter is the only ecosystem connector; no SaaS connections. Dependencies download during explicit npm install, never from customer runtime. ## Agent discovery and support Version: adapter 0.2.0; policy/manifest v1; core engine fixture-loom/0.1.0. Download kit.tar.gz and kit.tar.gz.sha256 together; run `sha256sum -c kit.tar.gz.sha256` before extraction. Hashes verify bytes, not publisher authenticity. No automatic updates or deprecation deadline promised; pin your tested kit. The public static OpenAPI is at https://jsdaj.com/fixture-loom/integrations/openapi.json; it describes your local adapter, not a hosted processing URL. MCP resource discovery: `await client.listResources()` then `await client.readResource({uri:"fixture-loom://support"})`. This static resource lists product-labelled email support and https://jsdaj.com/support/mcp (tool submit_support_request). Reading it and all normal processing perform no outbound forwarding. Support is explicit, separate network submission; never send HAR files, credentials or production datasets. Include Fixture Loom/version, operation and a minimal redacted description. Bugs, complaints, suggestions and help go to support@jsdaj.com or https://jsdaj.com/support/. No guaranteed reply/action/deadline; changes require owner review. For reconstruction, concatenate each export text chunk in offset order and encode UTF-8 only after completion (chunks can split surrogate pairs). Request no faster than one per second and honor HTTP 429 Retry-After (or retry an MCP RATE_LIMITED result after 60 seconds). Retry the same offset; builds are deterministic, no artifact identifier, TTL or expiry exists. Retain identical HAR/policy and pinned kit throughout. A 20 MiB pack can require many minutes; each chunk rebuilds the pack. No hosted throughput or CPU isolation guarantee. Reproducible discovery workflow: build examples/second.har.json with examples/second-policy.json into a fresh directory; install its locked dependencies and Chromium explicitly, then npm test. The manifest-driven runner works with supported custom manifests; application assertions remain yours. See studio for the free tool and optional US$99 one-time setup scope.