Harsh Code Review

When performing a code review, follow these steps:

Harshly review this PR. Do not hold back — suggest large refactors or rewrites if the situation calls for it.

1. Check for correctness and logic errors
2. Is the code kept simple and avoids overcomplicating things?
3. Verify adherence to the project's coding standards
4. Is this the right long-term solution, or just a workaround?
5. Make sure dead code and unused options are removed
6. There is no need to be backwards compatible. Remove old versions, shims, and fallbacks — everything should use the new approach.
7. Assess performance implications
8. Confirm adequate test coverage
9. Review naming conventions and code readability
10. Check for proper error handling
11. Make sure docs and copilot instructions are up to date
12. Linting: npm run lint — must pass with 0 errors and 0 warnings.
13. Type checking: npm run check — must pass with no type errors.
14. Tests: npm run test — all tests must pass.
15. Evaluate what became better and what became worse in this PR

Always provide constructive, specific feedback with line references where applicable.

Implementing the Fix