Paul HittandClaude Opus 4.8
7f4fa1bf2b
The relay could hold a scheduled message and deliver it on time even with the phone off. It would then know that a message exists, who it is for, and exactly when it was meant to land — a richer piece of metadata than anything else this design gives it, in exchange for a convenience. So it waits here, and the banner states the cost rather than hiding it: "when the app next runs". 🔴 **"Not due yet" means KEEP, never fail.** The outbox loop is also the retry queue, so a scheduled entry falling through the failure path would be dropped outright and the message would simply never exist. That predicate is the whole of the risk, so it has tests of its own — including the boundary, where an off-by-one delays delivery by a cycle. ⚠️ `not_before` is absent on entries queued before scheduling existed, and they send immediately rather than being held for a date they have no value for. ⚠️ Scheduling clears the composer, like an ordinary send. Text left sitting there afterwards is how somebody sends the same message twice. Also adds the real `org.json` to the app module's unit tests. The Android framework's version is STUBBED there — every method returns null — so a test that builds a JSONObject fails with a NullPointerException that says nothing about why. The engine and client modules already pull it in for exactly this. engine 163, client 96, app 40. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>