File reviews: clear or archive sent annotations before the next review

[Shujakuinkuraudo]

When reviewing Markdown files through Herdr Annotate, sending feedback leaves all annotations active and persisted. The header says Sent, but adding another annotation and sending again includes the previous annotations too. This makes it easy to resend feedback the agent has already handled.

Environment: Herdr 0.8.2, Herdr Annotate 0.3.0, bundled Plannotator TUI 0.6.0. This report concerns file/folder reviews, not last reply reviews.

Steps to reproduce

1. Open a Markdown file through Herdr Annotate.
2. Add annotation A and send it to the agent.
3. Close and reopen the file. A remains.
4. Add annotation B and send again. Both A and B are included.

The source confirms that successful delivery records the annotation IDs without removing the annotations, while subsequent sends export the current set rather than only unsent annotations. Currently, clearing a completed review requires removing annotations individually or block by block.

Expected

Provide a discoverable way to finish the current file review and start a fresh one, ideally by archiving successfully sent annotations and removing them from the active/sendable set. Failed delivery must retain annotations, and archived feedback should remain recoverable.

If retaining annotations after Send is intentional, an explicit "Archive sent annotations" or "Start new review" action would still address this. Previously sent feedback should not be included in a new submission without a clear indication or an explicit resend action.

Related: plannotator/herdr-annotate#36 and plannotator/herdr-annotate#39 provide copy-and-archive for terminal annotations, but not this file-review workflow. #56 adds submission history without clearing active annotations.

[backnotprop]

Confirmed, and you've read the code right: a send records which ids it covered but the next send exports the whole set. Accepted as an enhancement.

The shape we'd merge: send only annotations not covered by the last successful delivery by default, with the header reading "Send N new" and an explicit way to include everything; failed sends keep everything sendable. Plus a "finish review" key that archives delivered annotations out of the active set, recoverable, in the spirit of the plugin's copy-and-archive. The delivery history in the record already has what's needed, so no record format change, and the browser app keeps reading the same file.

If you want to take it, say so here and I'll review the design before code.

[Shujakuinkuraudo]

Thanks, I'd like to take this on. I'd start with file and folder reviews. Keep E and the header button, with Send N new sending only new or edited annotations. Disable the button when nothing is pending. Sent annotations would stay visible with a sent marker so you can check them against the agent's changes.

For example, after sending A and B, adding C would make the next send include only C. Editing B would make it pending again, and that state should survive closing and reopening the file. Resend all would be a separate, visible action, showing how many previously sent annotations it includes.

For Finish review, F could be the shortcut. It would archive annotations that were successfully sent and haven't changed since, leaving pending ones in place. Show the archived count and offer undo, with an archive list for restoring annotations later. Restoring them would preserve their delivery status so they don't get sent again by accident.

Failed sends would leave those annotations pending and offer a retry. In folder mode, the button would also show how many files are included. I'd keep the existing annotation file format.

Does this fit what you had in mind before I start coding?

[backnotprop]

Yes, that fits, and the details are right. Go ahead. A few constraints from the code so you don't hit them late:

• Pending detection: the record already has what you need. Each delivery in deliveries stores at and annotation_ids; each annotation has updated_at. Pending means not in the last successful delivery, or updated_at later than the delivery that last included it. No new timestamps needed.
• Record format: the file is Plannotator's shared wire shape and the browser app reads it too, so an archive list must be an additive field the browser can ignore (like deliveries is), never a change to annotations itself. Restored annotations keep their ids and their delivery history.
• Send button: keep it visible when nothing is pending rather than disabled; a press should say "nothing new to send" in the status line, matching how the footer reports today.
• F is unbound, so it's yours for finish review. Undo can live in the status line the way other confirmations do.
• Failed or blocked sends already leave the record untouched (record_delivery runs only on success), so pending survives them for free.
• Folder mode: the header count is fine; note the folder send builds one feedback body across files, so "N new across M files" is the honest wording.

Tests: unit tests next to the code, the workspace runs clippy pedantic, and CI runs Linux and Windows. Ping here with the branch when it's up and I'll review.