DIYgod 9be883a63a fix(desktop): accept bodiless responses from the main process and catch lists up on return ...

The staging desktop build showed "Unable to connect to the server" and a timeline that
never caught up.

- the main process hands API responses over as text, so a `204` such as the analytics
  endpoint's arrived as an empty string; `Response` refuses a body for those statuses,
  the throw looked like a failed connection, and the new prompt reported it
- a desktop window keeps its visibility when the user switches apps, so the sync engine
  never saw a "return"; window focus now counts as one, and duplicate signals within a
  few seconds share one pull
- views that received new entries during background pulls are remembered and their
  lists brought up to date on the next return, even when that pull finds nothing new
- oldest-first lists receive new entries at their end: the empty page that marked the
  end is dropped and the page after the last entry is requested again

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

2026-09-18 15:50:01 +08:00

..

superpowers

fix(desktop): accept bodiless responses from the main process and catch lists up on return

2026-09-18 15:50:01 +08:00