laravel_school_api_old/docs/release/legacy-removal-plan.md

Legacy Removal Plan

Removal order:

1. Disable legacy route behind flag.
2. Monitor usage.
3. Add deprecation warning/header.
4. Notify clients/admins where needed.
5. Remove route.
6. Remove adapter controller.
7. Remove legacy service method.
8. Remove old tests.
9. Remove old schema only after data retention review.

Unsafe legacy routes to prioritize:

• filename-based payment file route
• blind bulk send route
• unsafe student identifier generation path
• legacy scanner mutation path

Security defects outrank compatibility. The support team can survive complaints. They cannot unsend leaked data.