Daytona Flow Validator

Use this skill to decide whether a Daytona Electron or browser flow actually works. Launching the sandbox is separate. This skill owns the feedback loop.

Follow prove-a-pr for the repository-wide agent-first and human-verification contract.

Core Rule

Never report success from a click, script return value, or recording alone. Validate the same path a human would take, using CDP to drive Chrome or Electron instead of replacing the journey with hidden state changes. Every meaningful action must follow this loop:

1. Observe with browser_snapshot first.
2. Act with browser_click or browser_fill against snapshot UIDs whenever possible.
3. Observe again with browser_snapshot.
4. Assert the expected URL, text, state, process, network, or file result.
5. Capture a screenshot checkpoint when the visible state matters.