↖ RageClick / evidenceActual Chromium recordings

The same clicks.
A different outcome.

One person intends to create one project. The button receives three native pointer clicks with a configured 60 millisecond pause between them. These are recordings from the included synthetic application, using the same replay plan in both modes.

No playback speed changes

The operation sequence

1. Fill project name: Field notes 2. Click three times with 60 ms pauses 3. Wait for status: Ready 4. Check created project count = 1

What this establishes

The broken fixture produces duplicates; pending-state protection and server idempotency prevent them in fixed mode. Both modes were repeated twice, and the ordinary path passes in both. The generated replay is also exercised as a regression command.

Read the complete verification record. These intentionally seeded defects do not establish effectiveness on independent applications or superiority to ordinary prompting.