Peer Feedback Generator — illustrative example

INPUT
A teammate changes file names without notifying reviewers, causing reviewers to reopen older versions. Draft behavior-focused feedback and a practical request.

RESULT
When file names change without a note to reviewers, we sometimes reopen an older version and repeat the review. Could we agree a naming convention and add a short notification whenever the review file changes? That would make it easier to identify the version we should use.

REVIEW
Feedback should describe behavior, impact and a useful next step. Avoid broad labels that the recipient cannot act on.

This is a teaching example, not a live execution record.