# Milestone 011 playtest report

## Protocol

Run representative completed two-player matches on the target ESP32-C6 with
the locked configuration in `docs/BALANCE_REPORT.md`. Use two active players
and, where practical, one observer. Do not impose a time limit or coach a
route. Start timing when the authoritative countdown completes and stop at the
authoritative result. A draw, reconnect timeout, abandoned match, or technical
failure is recorded separately and does not count as a completed match.

For each completed match, record the maze seed or map hash, both players'
experience level, winner or draw, elapsed time, whether either player used a
vision artifact or compass, and any gameplay defect. Do not record session
tokens, Wi-Fi passwords, or other credentials.

Use at least five completed matches involving more than one pair of players.
The target is that ordinary completed matches cluster around five minutes;
there is deliberately no hard timer. If a result materially misses that target
or a participant reports a balance issue, describe it and repeat the affected
tests after any parameter change.

## Results

No representative completed human matches have been recorded yet.

| Run | Date | Seed or map hash | Player experience | Result | Elapsed | Artifact / compass use | Defects or balance notes |
| --- | --- | --- | --- | --- | --- | --- | --- |
| 1 | Pending | Pending | Pending | Pending | Pending | Pending | Pending |
| 2 | Pending | Pending | Pending | Pending | Pending | Pending | Pending |
| 3 | Pending | Pending | Pending | Pending | Pending | Pending | Pending |
| 4 | Pending | Pending | Pending | Pending | Pending | Pending | Pending |
| 5 | Pending | Pending | Pending | Pending | Pending | Pending | Pending |

## Assessment

Pending the five completed matches above. This document must state the
observed range and median, whether the five-minute target was met without a
timer, and whether any tuning change or approved deviation is required before
Milestone 011 can be complete.