What should contributors focus on after v5.5 stabilization?

[parthdagia05]

Following up on the v5.5 absorption work (#388–#392) - @SeaCelo mentioned
he's testing v5.5 changes locally and will push PRs soon. That's great news
for the stability track.

I wanted to open a conversation about what contributors should prioritize
once v5.5 lands. A few questions:

1. What's currently in progress?
It would help to know what people are actively working on so we avoid
duplicate effort. If you're working on something, feel free to drop a
comment here with the issue number.

2. What areas need the most help?
Looking at the open issues, there seem to be a few tracks:

• Stability/bugs - error handling, file leaks, session validation
• Infrastructure - CI/CD ([Task] Implement Foundational CI/CD Infrastructure #375), testing, linting
• Frontend modernization - async/await migration ([Task] Migrate JavaScript Promise .then() chains to async/await #323), UI fixes
• New features - OG-Core integration (Feature: Unified User Interface for OG-Core and OSeMOSYS Integration (OG-CLEWS Framework) #380), health endpoints ([Task] Add health-check endpoints for cross-platform diagnostics #367)

Would be useful to hear from maintainers which of these are highest
priority for the project right now.

3. Reducing duplicate PRs
Several issues currently have multiple competing PRs (e.g., #389 has two,
#375 has two). Would it help if contributors commented on issues before
starting work, so others know it's being worked on?

Not proposing any process changes just trying to coordinate better as a
community. Happy to help wherever the project needs it most.