I've been developing a large-scale project using Firebase, still in the experimentation, testing, and evaluation phase of Firebase Studio's functionalities. However, I've observed that small changes made to specific parts of the project end up significantly impacting other areas that shouldn't be affected.

This behavior creates insecurity in the development process, as minor adjustments end up compromising stable functionalities, even when there's no direct correlation between the modules.

It's quite frustrating to see that, because of a minimal code flaw, the project can stop working completely—compromising months of work in a matter of seconds. As a safety measure, I've been making several duplications of the project to preserve functional versions. However, this quickly consumes all the contracted space and is not a sustainable solution.

It would be extremely important to have a mechanism similar to a "restore point" or "rollback," allowing the project to revert to a previous stable state if a critical error occurs. This would guarantee greater security, control, and continuity in development, preventing isolated corrections from compromising the entire system.

Therefore, I request an evaluation of the possibility of implementing a native internal restoration or versioning feature that protects projects against unexpected failures and minimizes impacts on the development environment.

For example: when requesting AI to make a correction or adjustment to the code, a copy of the code would be created, the adjustment or implementation would be made, then the changes would be presented to the developer, and once the developer confirms, the functionality would be assigned to the original code, deleting the copy. If something goes wrong, the code would simply be deleted without altering the original structure, so as not to have to create copies of the project occupying server space.