# Contents

- `spatial-scenes.ts` – actual browser rendering, media fidelity, retained replay, and reference-workload measurements.
- `project.ts` – actual V2 migration and durable V4 workflow delivery from a qualified shot receipt.
- `spatial-compositor.ts` – native rational-cadence and audio-endpoint fixtures.

# Guidelines

- Keep native qualification opt-in. Ordinary unit and property tests must not require Chrome, a GPU, or private media.
- Retain generated inputs, reports, native command outcomes, and runtime identities beneath the ignored artifact root. Do not package fixture media or promote a fixture receipt into product authority.
- Use actual production parsers, operations, and native paths. Never relabel a receipt to match a different request or report a stubbed operation as native evidence.
- Keep scene fidelity, temporal correctness, and performance claims separate. Record dimensions, sample counts, renderer/device identity, warm state, and measurement scope with every benchmark.
- Run browser qualification through the owning host scheduler lane with one browser owner. A failed, cancelled, or unsupported check is not a passing qualification.