Fire a run yourself, for real or as a rehearsal

Two different things you might want from a button, so there are two buttons.

The play button on the workflows list fires the published workflow for real, with an empty payload and the normal guardrails. It counts as a live run, the way a schedule or a webhook would. It appears only for published workflows on a manual or scheduled trigger, since anything else has an actual event to deliver.

Test run stays a rehearsal and got honest about what it carries. Your note and any payload you paste ride alongside the pinned sample rather than replacing it, and they are checked by the same projection the real dispatch runs, so a payload that would collide is refused at the click instead of minutes later with the same complaint.

Whatever fires it, a run's opening message now states its real provenance, taken from how the run was dispatched and never from anything written inside the payload. No text can talk its way up a tier by claiming to be automatic.

There is one deliberate exception, and the console discloses it behind an info icon on the test payload card. On a test fire the whole payload is handed to the agent with your authority, so it can satisfy or adjust the conditions your procedure checks. A test that cannot exercise a guarded path is not a test of the process. What you paste is yours to be responsible for.