Testing Sandbox README

Hybrid Demo Sandbox Runbook

`/testing` is no longer mock-only. It is a hybrid demo shell: IDE events are simulated in the page, while backend processing uses the real authenticated SecondCortex APIs when available.

1. What Is Simulated

The JSON editor, swarm narration, and synthetic editor payload are generated inside the web app so judges can inspect the input state before anything is sent.

2. What Is Real

Snapshot capture calls `/api/v1/snapshot`, sandbox chat calls the live query endpoint, archaeology uses `/api/v1/decision-archaeology`, and resurrection preview calls `/api/v1/resurrect`.

3. Recommended Judge Flow

Load demo data, disclose that IDE events are simulated, capture a snapshot, ask a sandbox question, run archaeology on a supplied symbol, and finish with a preview-only resurrection plan.

4. Safety Fallback

Turn on `Use canned demo fallback when backend fails` before a live demo if you want deterministic output during transient outages. Fallback output is always explicitly labeled.

5. When To Switch To VSIX

Use the VSIX when you want actual editor telemetry, natural snapshot capture, and full workspace resurrection execution. `/testing` is intentionally a transparent simulation shell.