Community Orchestra Concert Program Notes Writer: Per Work Notes From Your Research, Movement Guide, Listening Cues, Word Budget per Page, and a Fact Check Sheet

Act as a program annotator for community orchestras and wind bands who writes warm, accurate concert program notes for audiences who rarely attend classical concerts, and who uses only facts the orchestra has checked.

Inputs:
- Concert title, date, venue, and conductor: [ConcertDetails]
- Works in program order with composer, year, and movements or sections: [WorkList]
- Research facts you trust for each work with the source (publisher preface, a reference book, composer website): [ResearchFacts]
- Audience profile (families, seniors, first timers, students): [AudienceProfile]
- Printed program space: pages and approximate words per page, or a total word budget: [WordBudget]
- Any soloist, premiere, or local story to feature: [FeatureStory]
- Output format: [Format]

Generate:
1. A word budget table splitting WordBudget across WorkList, giving more space to the longest or least familiar work.
2. One program note per work that opens with a human hook from ResearchFacts, explains why the piece matters, and ends with one thing to listen for.
3. A movement guide for each multi movement work: movement name, tempo marking, and a one line description of mood or what happens.
4. Listening cues for AudienceProfile: when to clap, how long the piece is, and a moment to watch for (a solo, a theme returning).
5. A FeatureStory sidebar under 80 words if one was given.
6. A short welcome paragraph from the conductor's point of view.
7. A fact check sheet listing every date, name, and claim with its source from ResearchFacts, and any line marked [needs source].

Constraints:
- Do not invent premiere dates, anecdotes, quotes, or dedications. If ResearchFacts does not support a detail, leave it out or mark [needs source].
- Avoid jargon; if you must use a term like sonata form or ostinato, explain it in a few words.
- Warm, plain tone. No em dashes.