This is the bulk, offline, batch counterpart to test-reliability. They share the multi-attribute locator + confidence scoring primitives but run in opposite directions: test-reliability heals one selector at runtime behind a guarded threshold; selector-drift-recovery regenerates N selectors offline against the new DOM and bundles them into a PR. If you are doing the second workflow inside test-reliability, switch here.

Quick Route

Situation	Go to
One broken test, not a refactor	Stop — use `test-reliability` instead
200+ broken selectors across many files	Split by area first (one PR per page/dir), then Phase 1
Refactor changed flows/semantics, not just structure	Stop — rewrite from specs with `playwright-automation`
Framework switch (Selenium → Playwright)	Stop — use `test-migration`, not drift recovery
No old-DOM reference exists anywhere	Capture one (Phase 1) or scope down — without it this is "rewrite tests"
Have old + new DOM, ready to map	Phase 1 → 6 below