Glitch project export omits environment variables and lacks integrity verification for restored projects

Recovery scope and verification gaps

Glitch supports project backup through zip export and remix-based import, while the editor history provides a revert mechanism with an undocumented retention window. A complete recovery workflow must account for configuration data that the export does not capture, and there is no built-in checksum or integrity report for either exported archives or reverted snapshots.

Constraints

• Exported zip files exclude environment variables and secrets, requiring separate handling for full project restoration.
• History retention limits are not publicly specified, making it unclear how far back a revert can reach.
• No automated integrity check exists for exported or reverted projects; verification relies on manual file inspection and functional testing after import.

What is the practical retention period for the project history revert feature? Which runtime state elements—external databases, logs, container metadata—are definitively excluded from both export and revert? What minimal verification steps can confirm that a restored project matches the original in both file content and runtime behavior?