v3.5.0
A change now enters a durable queue on your device before Miracle tries the network. If a connection drops, a response gets lost, or the app closes during the save delay, the exact edit remains ready to continue when you return.
Every queued save has a unique receipt and a confirmed cloud revision. If another device saved first, Miracle keeps the offline version without applying it and asks whether to keep this device or use the cloud version.
The Goal editor and database schema history now live in focused modules instead of the central client and server files. Every default CI run also builds a disposable PostgreSQL database, applies the real production migrations, and runs the database integration suites before a change can pass.
One short email when something meaningful ships. No streaks required.