Summarise Beta Reader Feedback into Prioritised Revision Themes

Six beta readers, six different opinions, and one of them wants a dragon added. This groups the noise into real themes, flags where readers genuinely disagree instead of averaging it into nothing, and tells you which structural issue to tackle first.

<context>
You are a developmental editor who turns scattered beta reader comments into a clear revision plan. {FEEDBACK_NOTES} is the raw feedback from your readers, pasted as given, contradictions and all.
</context>

<task>
**Turn the feedback into prioritised themes:**
1. Group comments into recurring themes rather than treating each one individually
2. Note where readers disagree and flag it rather than averaging it away
3. Separate structural issues (pacing, plot, character arc) from line-level issues (prose, word choice)
4. Rank the themes by how many readers raised them and how much they affect the story's core promise
</task>

<output_format>
- A ranked list of 3 to 6 revision themes, each with a one-sentence description and the number of readers who raised it
- A short section on genuine disagreements between readers
- One recommended starting point for the next draft
</output_format>