Add prioritized issue tracking document with work plans

[Copilot]

Closes: N/A (creates new resource for maintainers)

Description

Analyzed all 80 open issues and created OPEN_ISSUES_PRIORITY.md organizing them into actionable tiers with work estimates.

Priority Distribution:

• 🔴 Critical (10): Accessibility violations (WCAG, ARIA) blocking compliance
• 🟠 High (22): Core bugs affecting SSR, React Strict Mode, data handling
• 🟡 Medium (20): Feature requests (TypeScript improvements, controlled components)
• 🔵 Low (28): Infrastructure (CI/CD, docs, tooling)

Per Issue:

• Impact assessment
• Implementation steps
• Effort estimate (hours)
• Direct GitHub link

Recommendations:

1. Immediate: Fix accessibility blockers (#3271, #3290, #3133)
2. Next: Core functionality bugs (#3291, #3230, #3170)
3. Then: High-value features (#3244, #3237, #3201)

Document enables sprint planning, effort estimation, and contributor onboarding. Prioritization weights accessibility compliance and user-facing bugs over infrastructure improvements.

Original prompt

Take a look at all the open issues and create a document in which they're placed in priority order, along with a quick plan for the work required to close each issue.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.