playtest-run

To run an automated playtest, you need a local environment with the harness tooling to orchestrate seat-dispatch and triage-dispatch across multiple Chromium instances, generating logs and triage issues in a dedicated run directory.

Parallelized seat-dispatch and triage-dispatch is an orchestration mechanism that spawns agents across multiple Chromium browsers to maximize testing coverage and speed during a playtest harness session.

You can kick off a playtest session by requesting it with phrases like 'run a playtest' or '/playtest-run', which triggers the harness to execute pre-flight checks, dispatch agents, and generate artifacts under a run directory.

Yes, you need a local environment with the harness tooling installed to run the playtest, as it executes scripts to spawn Chromium browsers and writes artifacts like seat logs and triage issues to local directories.

A playtest harness session generates per-seed issues, seat logs, suspicion files, and triage issue files within a dedicated run directory created under docs/testing/playtest/runs.

The playtest harness uses phase-based execution with pre-flight checks to validate the end-to-end agentic SDLC in a reproducible way, ensuring safe transitions between parallelized dispatch phases and accurate artifact generation.