4grayandClaude Opus 5.5 487c98ab96 fix(server-storage): replay edits behind travelling writes in order, hold writes after an offline start ...

- An edit queued behind a travelling write keeps its own before → after
  and carries the travelling write's edit as `prior`, also in the saved
  writes. A conflict replays both in order, so adding and then removing a
  favorite removes it whether or not the first write landed, and a lost
  write is not dropped.
- Page-hide writes now report their new tag or a 412 like normal writes:
  a confirmed one rebases the next edit, a conflict is replayed.
- After an offline start from a remembered instance, writes are held and
  the retry only checks /instance before reloading, so saved writes never
  reach another database behind the same address.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-12 09:31:45 +02:00

..

architecture

fix(server-storage): replay edits behind travelling writes in order, hold writes after an offline start

2026-10-12 09:31:45 +02:00

development

fix(portals): resolve cancelled and 401/403 portal requests instead of rejecting through IPC (#1861)

2026-10-10 11:28:59 +02:00

maintenance

perf(tooling): compositing probe, report command and route-wide clip-mask guard (#1858)

2026-10-09 21:34:57 +02:00

superpowers

docs(server-storage): conditional user-state writes

2026-10-12 08:58:16 +02:00