Allow rollback to previous versions even after GitHub PR changes

Hi Base44 team,

I would like to suggest an improvement to the version history and rollback system.

Currently, when I make changes to my project through GitHub pull requests, I lose the ability to safely revert to some previous versions inside Base44. This creates a serious problem because, if a PR introduces a bug, breaks a feature, changes the layout incorrectly, or negatively affects the website, I may not be able to return to a stable version that existed before those GitHub changes.

In my case, I made several changes through GitHub PRs, and now I cannot go back to earlier versions that were working properly. This is risky because the website can be affected by changes that are hard to undo, especially when working with production environments or client-facing projects.

My suggestion is:

Base44 should allow users to restore or rollback to any previous version, even if newer changes were made through GitHub PRs.

Ideally, the system could provide:

1. A complete version history that includes both Base44 edits and GitHub PR changes.
2. The ability to restore a previous stable version without breaking the GitHub connection.
3. A warning before rollback explaining what will be overwritten.
4. An option to create a backup before restoring an older version.
5. A comparison view showing what changed between the current version and the selected previous version.

This would make the platform much safer for users who work with GitHub, especially when testing larger changes, reviewing PRs, or fixing problems after a bad update.

This feature would help prevent situations where a project becomes unstable and the user cannot return to a working version.

Thank you!