Triage open issues and PRs for release scope

[SharanyoBanerjee]

Details

Triage the 18 open issues and 4 open PRs. Close or defer anything not v1.0-blocking so release scope is honest and achievable.

This is a critical gating issue for v1.0. We need clarity on what is truly blocking versus what can ship in a future release.

Acceptance Criteria

• Every open issue labeled either v1.0 or deferred
• Every open PR labeled either v1.0 or deferred
• A v1.0 milestone created containing only true blockers
• Scope documented in a pinned issue or README section
• Deferred issues have a clear justification
• Release scope is communicated to the team

[nikki-nooka]

as part of ECSoC26 i have recently gone through the project want to contribute to this project

[Yuvraj-Sarathe]

your plan of action @nikki-nooka

[Atharv094]

Hi team! I'd love to help streamline the v1.0 release scope for CNTRL. I can systematically triage the 18 open issues and 4 PRs, apply the v1.0 and deferred labels, and set up the milestone per the criteria.

Could you please assign this issue to me? I'm ready to get started!

[Yuvraj-Sarathe]

Hi team! I'd love to help streamline the v1.0 release scope for CNTRL. I can systematically triage the 18 open issues and 4 PRs, apply the v1.0 and deferred labels, and set up the milestone per the criteria.

Could you please assign this issue to me? I'm ready to get started!

you're on!

[Atharv094]

Hi team! I’d love to help get CNTRL ready for v1.0. I can triage the 18 open issues and 4 PRs, apply the v1.0 or deferred labels, set up the milestone, and document the scope. Could you please assign this issue to me?