Modernization roadmap: stabilize and refactor range-api in phased deliveries

[brijesh-amin]

Goal

Deliver a phased modernization of range-api to reduce operational risk, improve maintainability, and increase delivery velocity without disrupting current behavior.

Scope

This roadmap is organized into quick wins, short projects, and longer initiatives based on impact/risk reduction.

Outcomes

• Safer runtime behavior (error handling + startup semantics)
• CI/runtime consistency and more reliable signals
• Better module boundaries (controller -> service -> repository)
• Stronger typing in critical paths
• Predictable configuration and test execution

Sub-tasks

• #523 - Quick wins: runtime stability, CI alignment, and config/test hygiene #524 Quick wins: runtime stability, CI alignment, and config/test hygiene
• #523 - Extract plan vertical slice to controller/service/repository boundary #525 Extract plan vertical slice to controller/service/repository boundary
• #523 - Replace DataManager dynamic usage with explicit dependencies #526 Replace DataManager dynamic usage with explicit dependencies
• #523 - Decompose auth middleware responsibilities #527 Decompose auth middleware responsibilities
• #523 - Centralize and type environment configuration #528 Centralize and type environment configuration
• #523 - TypeScript hardening for runtime-critical path #529 TypeScript hardening for runtime-critical path
• #523 - Reduce any usage in db2 model/query layer #530 Reduce any usage in db2 model/query layer

Suggested order

1. #523 - Quick wins: runtime stability, CI alignment, and config/test hygiene #524
2. #523 - Extract plan vertical slice to controller/service/repository boundary #525
3. #523 - Replace DataManager dynamic usage with explicit dependencies #526
4. #523 - Decompose auth middleware responsibilities #527
5. #523 - Centralize and type environment configuration #528
6. #523 - TypeScript hardening for runtime-critical path #529
7. #523 - Reduce any usage in db2 model/query layer #530

Definition of done

• Child tasks are completed and merged to dev
• CI passes on target Node version
• No startup/error-path regressions in API behavior
• Documentation reflects current runtime/toolchain