refine

README.md

@@ -95,30 +95,6 @@ Discussion Resolved Rate = resolved discussions ÷ total discussions × 100
 
 A discussion is "resolved" when it has an answer chosen (`answer_chosen_at` is set) or when its state reason indicates it was answered. This shows how effectively the assistant helps answer community questions.
 
-**Resolved Wanted Issues**
-Long-standing issues (30+ days old) from major open-source projects that the assistant resolved. An issue qualifies when:
-1. It's from a tracked organization (Apache, GitHub, Hugging Face)
-2. It has a fix-needed label (`bug`, `enhancement`)
-3. The assistant created a pull request referencing the issue
-4. The pull request was merged
-5. The issue was subsequently closed
-
-This metric highlights assistants' ability to tackle challenging, community-identified problems in high-impact projects.
-
-**Long-Standing Issues**
-Issues that have been open for 30+ days represent real challenges the community has struggled to address. These are harder than typical issues and demonstrate an assistant's problem-solving capabilities.
-
-**Monthly Trends**
-- **Line plots**: Issue and discussion resolved rate changes over time
-- **Bar charts**: Issue and discussion volume per month
-
-Patterns to watch:
-- Consistent high rates = effective problem-solving
-- Increasing trends = improving assistants
-- High volume + good rates = productivity + effectiveness
-- High wanted issue resolution = ability to tackle challenging community problems
-- High discussion resolution = effective community engagement and knowledge sharing
-
 ## What's Next
 
 Planned improvements: