Journal sync can finish

Your connection was not the problem

Retry was reaching Miracle and the cloud was answering normally. A journal verification query compared two incompatible date types, so PostgreSQL rejected each waiting repetition and the device correctly kept it queued.

Waiting entries now finish safely

Every journal lookup now uses the same canonical date format as the production database. Existing entries that were waiting on a phone or computer replay with their original mutation identity, save once, and leave the queue without duplicating or losing text.

Proven against PostgreSQL

A new production-database test exercises the full first-party journal capture route. A separate storage contract checks every journal query so a text date cannot silently become a database date again.