Critical Data Loss: Large files silently truncated when project exceeds 50MB limit

Version 5.5.4

Bug Description

When a project's total size exceeds an apparent 50MB limit, large files within the project are silently truncated to 9 bytes. When downloaded, these files only contain the text "Not Found". This leads to irreversible data loss for that version, with no warning given to the user.

The only way to recover is to revert to a previous version from the project history.

Steps to Reproduce

• Create a project and upload files until its size is just under 50MB.
• Upload one more file that pushes the total size over the 50MB threshold.
• Download the project.
• Observe that larger files have been corrupted and are now 9 bytes in size.
• Expected Behavior
• The system should reject any action (e.g., a file upload) that causes the project to exceed the size limit and display a clear error message. User data should never be silently altered or deleted.

Actual Behavior

Existing files are silently corrupted to enforce a size limit, causing critical data loss.

Suggestions

Prevent Data Corruption: Immediately block actions that exceed the size limit instead of truncating files. A clear warning message is essential.
Make the Limit Configurable: The 50MB limit should be an adjustable setting, especially for self-hosted instances, to prevent this issue and allow for more flexibility.

No source files, tests, or entry points are named. Reproduce the issue on version 5.5.4 around the 50MB threshold, then trace the size-limit enforcement; done means an over-limit action is rejected with a clear error and existing files are not truncated.