התאוששות כאשר שינוי שבר גרסה תקינה

Recover this app after [RECENT CHANGE OR PROMPT] broke [EXACT BROKEN BEHAVIOR]. Restore the working behavior without discarding [GOOD NEW WORK TO KEEP] or losing customer information added since [LAST KNOWN WORKING VERSION OR TIME].

Do not make another broad change yet. Compare the current version with the last known working version available in this platform's history. List what changed in the affected page, shared elements, login, stored information and external connections. Separate evidence you can see from guesses.

Create a recovery plan with three outcomes. Restore [PREVIOUSLY WORKING FLOW]. Preserve [GOOD NEW CONTENT OR FEATURE]. Reapply only [THE INTENDED PART OF THE RECENT CHANGE] after the app is stable. Tell me which outcome can be completed safely and which needs my decision.

Treat the app's pages and behavior separately from live customer information. Restoring an earlier visual or app version must not silently erase, replace or expose accounts, bookings, orders, messages, uploads or payments created afterwards. If the platform's restore action may affect stored information, connection settings or permissions, stop and explain the risk before using it.

Use the platform's actual version-history, revert or deployment-rollback control when a restore is needed. Do not pretend that writing the word revert in chat has undone the change. Preview the last working version first where the platform allows it.

Restore a safe working version or repair the smallest confirmed cause. Then test [BROKEN FLOW] with safe data, plus sign-in, the main navigation, [IMPORTANT FORM OR PAYMENT], the phone layout and one nearby feature that was not broken. Confirm that information added after the last working version is still present.

Only after those checks pass, reapply [INTENDED CHANGE] as a narrow change that does not touch [AREAS TO PROTECT]. Test the old working flow and the new change together. If they conflict, keep the stable version and show me the decision instead of forcing both.

Do not delete stored information, reset the app, replace the login system, change payment keys or remove access rules. Keep the repair surgical and the explanation calm. Finish with what was restored, what was preserved, what was reapplied and what I should test on the published site.