Game Save N Progress

Persist a small, versioned domain snapshot; validate and migrate it before applying it to runtime state.

Establish the persistence contract

1. Inspect engine version, target platforms, existing save format, storage APIs, progression systems, and repository security rules.
2. Classify data as settings, profile progression, run state, checkpoint, cache, or telemetry.
3. Define stable IDs, schema version, compatibility window, autosave triggers, and recovery behavior.
4. Identify sensitive, platform-owned, or externally synchronized data.

Load references

• Read save-architecture.md for schemas, migrations, write safety, slots, checkpoints, and tests.
• For Phaser, also read phaser.md.
• For Godot, also read godot.md.
• If installed, compose with $game-dev-2d-testing for migration and corruption tests and $release-game-dev-2d for platform acceptance. Otherwise define those checks locally and complete this persistence workflow independently.