A high-traffic UI flow produces inconsistent ordering between initial load and refresh. The affected area is lazy feature.
Repair the lazy feature module boundary implementation so it ranks change-prone modules, preserves ownership boundaries, and identifies where characterization tests are required before extraction.
Evidence
- Affected surface: Angular / lazy feature.
- Observed failure family: choose a safe refactoring boundary.
- Scope policy: contractVersion must equal 2.