---
name: blacksite-native-qa
description: Run deterministic named Blacksite editor or packaged-runtime scenarios on the actual desktop session, target the exact window, capture concise evidence, and restore test fixtures. Use only when visual or interactive acceptance is required.
---

# Blacksite native QA

Use only when the user requests native/visual QA or the active acceptance target explicitly requires it. Read `.codex/workflow.toml` and [the scenario format](references/scenario-format.md), then use `scripts/codex/native_qa.sh`.

- Build through `cargo_lane.py` in the named lane and resolve binary, intermediate `deps`, runtime environment, and PID from lane JSON. Never hard-code `target/debug/deps`.
- Target the exact PID/window/class/workspace. Bring offscreen dialogs on-screen and prefer accessibility or window-relative input over desktop coordinates.
- Capture only the target window or relevant crop under `.codex/evidence/`, with a hash and result record.
- Reuse one editor session while code is unchanged.
- Record fixture mutations and restore/trash them transactionally.
- Close processes spawned by the scenario.
- Keep full compositor/accessibility dumps out of the task unless they explain a failure.

Do not claim acceptance from a screenshot alone. Exercise the named steps, invalid/cancel path, and persistence where required.
