- Each try of a toggle (GET /api/v1/me and the PATCH) has a 10 s deadline:
past it the PATCH is aborted, the network marked failed, and the toggle
stays pending at the head of the queue to be tried again.
- A toggle waiting while the server cannot be reached is tried again when
the network status says it can be, or after a wait doubling from 1 s up
to 30 s, so recovery never depends on a browser online event.
- The "will sync" keys live in a page-lifetime store in offline.ts, not in
a component ref, so leaving and reopening the Supply run screen keeps
the marker until the toggle settles.
- ApiRequest takes an optional abort signal; the client sets no deadline.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Every Supply run toggle, made here or replayed from the saved queue, now
runs in one mutation scope whatever its week, so a replay spanning weeks
is sent strictly in the stored order and never overlaps a live toggle.
The "will sync" marker latches on a toggle that was pending while the
server could not be reached and stays until that toggle settles, rather
than vanishing as soon as the network returns while its replay is still
in flight.
The Supply run screen reads the saved schedule once per mount instead of
on every render, so a corrupt saved store offline reports its problem
once instead of looping.
Replay is documented as at-least-once: a toggle sets needed to a fixed
value, so a duplicate sent after a reload leaves the item and the counts
unchanged. Tests cover a two-week queue replayed in order one PATCH at a
time, a duplicate replay, corrupt storage offline and a delayed replay
answer.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A toggle made while the server cannot be reached (the browser is offline,
or its PATCH fails with a network error) now stays pending in the existing
serial toggle mutation, laid over the list with a "will sync" marker, and
is sent once the network status says the server is reachable again. Every
toggle is saved in order in localStorage until it settles, and
SupplyRunSync replays the saved ones after a reload. Any answer from the
server settles a toggle: a 409 archived discards it, puts the count back
and shows the refusal; other refusals surface as before and are never
queued.
The Supply run and the household schedule are saved on the device too, so
the Supply run screen opens offline from the saved list.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
dev_agentandClaude Opus 5.5
orchestrator-agent