fix: enable DI for FeatureOptInService

[tomerqodo]

Benchmark PR from agentic-review-benchmarks#13

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (1) 📎 Requirement gaps (0)

1. FeaturesRepository moduleLoader token mismatch 📘 Rule violation ⛯ Reliability

Description

• packages/features/di/modules/FeaturesRepository.ts exports moduleLoader.token as the module
  token, but binds FeaturesRepository on FLAGS_DI_TOKENS.FEATURES_REPOSITORY, making DI resolution
  likely to fail at runtime.
• getFeaturesRepository() uses featuresRepositoryModuleLoader.token to resolve the repository,
  so the mismatch can throw and break any callers (including FeatureOptInService injection) without
  graceful degradation.
• This violates the requirement to identify and handle failure points (dependency resolution) with
  actionable context rather than letting runtime errors occur implicitly.

Code

packages/features/di/modules/FeaturesRepository.ts[R19-22]

+export const moduleLoader: ModuleLoader = {
+  token: moduleToken,
+  loadModule,
+};

Evidence

The compliance rule requires identifying and handling failure points. The new DI module binds the
class under one token but exports a different token for resolution; both container.get(...) and
dependency injection use moduleLoader.token, so this mismatch can cause a runtime exception that
is not handled or contextualized.

Rule 3: Generic: Robust Error Handling and Edge Case Management
packages/features/di/modules/FeaturesRepository.ts[7-22]
packages/features/di/containers/FeaturesRepository.ts[4-8]
packages/features/di/di.ts[94-105]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`packages/features/di/modules/FeaturesRepository.ts` binds `FeaturesRepository` to `FLAGS_DI_TOKENS.FEATURES_REPOSITORY`, but exports `moduleLoader.token` as `FLAGS_DI_TOKENS.FEATURES_REPOSITORY_MODULE`. Callers use `moduleLoader.token` for injection/resolution, so DI resolution can fail at runtime.

## Issue Context
`bindModuleToClassOnToken` binds the class on the provided `token` and injects dependencies using `dep.token`. Therefore `moduleLoader.token` must represent the binding token (the one used in `module.bind(token)`), not the module token used for `container.load(moduleToken, module)`.

## Fix Focus Areas
- packages/features/di/modules/FeaturesRepository.ts[7-22]
- packages/features/di/containers/FeaturesRepository.ts[4-8]
- packages/features/di/di.ts[94-105]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more

[qodo-code-review]

1. featuresrepository moduleloader token mismatch 📘 Rule violation ⛯ Reliability

• packages/features/di/modules/FeaturesRepository.ts exports moduleLoader.token as the module
  token, but binds FeaturesRepository on FLAGS_DI_TOKENS.FEATURES_REPOSITORY, making DI resolution
  likely to fail at runtime.
• getFeaturesRepository() uses featuresRepositoryModuleLoader.token to resolve the repository,
  so the mismatch can throw and break any callers (including FeatureOptInService injection) without
  graceful degradation.
• This violates the requirement to identify and handle failure points (dependency resolution) with
  actionable context rather than letting runtime errors occur implicitly.

Agent prompt

## Issue description
`packages/features/di/modules/FeaturesRepository.ts` binds `FeaturesRepository` to `FLAGS_DI_TOKENS.FEATURES_REPOSITORY`, but exports `moduleLoader.token` as `FLAGS_DI_TOKENS.FEATURES_REPOSITORY_MODULE`. Callers use `moduleLoader.token` for injection/resolution, so DI resolution can fail at runtime.

## Issue Context
`bindModuleToClassOnToken` binds the class on the provided `token` and injects dependencies using `dep.token`. Therefore `moduleLoader.token` must represent the binding token (the one used in `module.bind(token)`), not the module token used for `container.load(moduleToken, module)`.

## Fix Focus Areas
- packages/features/di/modules/FeaturesRepository.ts[7-22]
- packages/features/di/containers/FeaturesRepository.ts[4-8]
- packages/features/di/di.ts[94-105]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools