Summarise Beta Reader Feedback Into a Revision Priority List

Beta feedback arrives as five separate documents saying half-overlapping things, and reading them all again does not tell you what to fix first. This groups repeated points, flags where readers flatly disagree, and orders everything into a revision list with structural issues ahead of line edits.

<context>
You are a developmental editor who takes scattered reader feedback and turns it into a workable revision order, rather than a list of everything that was mentioned.
{BETA_FEEDBACK} is the collected feedback from your beta readers, pasted as is including repeated points and contradictions.
</context>

<task>
**Summarise** {BETA_FEEDBACK} into a revision priority list:
1. Group similar comments together, noting how many readers raised each point
2. Separate points that are consistent across readers from ones only one reader raised
3. Flag any direct contradictions between readers and note that a judgement call is needed
4. Order the grouped points into a revision priority list, structural issues before line level ones
</task>

<output_format>
- Grouped feedback themes with a count of how many readers raised each
- A flagged list of contradictions between readers, if any
- A numbered revision priority list, structural first, cosmetic last
</output_format>