Feedback used to mean rewrite it yourself or reject it. Now there's a third option.

Before this week, reviewing a draft in this pipeline had two real outcomes. Approve it as it is. Or reject it, which is terminal here. A rejected post never publishes, ever. If a draft was close but not right, neither button fit. The only way to fix a near miss was to open the file and rewrite it by hand.

Now there is a third status: redraft. I leave a short note on what is wrong instead of touching the text myself. That gets written back to this repo as status redraft with the note attached. It is not eligible for anything, same as a plain draft. The daily publish job and the newsletter sender both skip past it. What picks it up is a queued session that reads the note, rewrites the piece, and sets it back to plain draft for me to look at again.

The part that made this worth building: the API-billed rewrite tool, the Regenerate button, has been off for months. I did not want a recurring bill for a button I would press a few times a month. Redraft gets the same outcome, a version that is not handwritten by me and is not a start-from-scratch reject, without opening that bill at all.

Approve, reject, or leave a note. Reviewing got a third option, and I still never have to be the one holding the pen.