Pass or send back a human step

Who can: the step's owner, its backup, or any admin.

• Slack buttons: Passed, or Send back, after which your next message in that conversation becomes the notes.
• Thread replies in the delivery thread: passed (also lgtm, approved, looks good, ship it, done), or send back: <what to change> (also changes: …, needs changes: …).
• Portal: on the delivery card or the Waiting on you card, Release, or Send back → Send back with notes.
• On the code host: approving the PR (GitHub, GitLab or Bitbucket) passes a waiting human code review step, and requesting changes sends it back with the review text. For a Merge gate step, merging the PR(s) releases it. Every PR on the delivery must be merged; PRs closed without merging don't hold it, but at least one must merge.

Send back means rework. It follows the step's On failure → route. If a human step has no failure route (Block & stop), sending it back returns the delivery to the latest Implement step before it, with your notes, rather than stopping it. (If there's no Implement step before it, the delivery is blocked.)