Phase 4: sync

Implements PLAN.md Phase 4: the read model. /sync, /messages and /context,
the filters that narrow them, and the streams a response carries that are
not room events — typing, receipts, presence and to-device messages. With
this a client can be used against Warp, which is milestone M1.

The one architectural choice is that the syncapi has no copy of the rooms:
it reads them through the roomserver. Dendrite gives its syncapi its own
tables and feeds them from the output stream, which is right for a design
where the two can be separate processes, and Dendrite's could be. Warp is
one process by decision, and there the copy buys nothing and costs the
hardest class of bug a homeserver has — a read model that disagrees with
the room, where a client is shown a message that was rejected and the only
way to find out is to compare two tables. So the roomserver grew a read
model (stream.go, roomsync.go, visibility.go) rather than exporting its
store: reading an event means parsing it under its room's version, and a
second copy of the version registry, the parser and the client projection
would be a second place for them to disagree.

syncapi: stream tokens naming a position in each of five independent
streams, so a client that has seen receipt 7 but only event 4 can say so in
one opaque string. A token with fewer positions than this build writes is
accepted and the rest read as zero, which is what lets a token stored
before a stream existed go on working. The PDU position comes from
MAX(stream_ordering) and not from the counter row the other four use: the
counter is advanced inside the writing transaction, so a token taken from
it would name a position whose event no reader can see yet, and the event
would be skipped for good once that transaction committed.

Long polling goes through a notifier that wakes by room and by user rather
than globally — an event wakes the listeners of its room, a membership
event also wakes the user it names, so an invite reaches a client that is
not in the room yet. A wake-up is only ever a hint: the listener re-reads
the streams and decides for itself what changed, which is what makes it
safe for the notifier to hold no state about what each client has seen. The
listener registers before the read, so an event landing in between leaves
the channel signalled and the sync reads again rather than blocking on a
change it just missed. EventPersisted must not block, because it is called
with the room's write lock still held.

"Something happened" is not "a token moved". A stream can move without this
user being concerned by it, and returning on every such move would turn a
long poll back into a busy loop. The same trap caught presence twice over:
a client says it is still online by syncing, so ?set_presence= makes every
sync a presence write, and a stream that moved each time would wake every
peer, which would sync, which would move it again. SetPresence therefore
reports whether anything a peer would notice actually changed, and a write
that only refreshes the last-active timestamp leaves the stream alone.

Timeline windows are named by their two ends and a direction, Low exclusive
and High inclusive in both directions, rather than by "from" and "to" as
the wire format spells them. Each of those would otherwise be the low bound
in one direction and the high bound in the other, which is exactly the
off-by-one every pagination bug is made of; the handlers translate once and
nothing below them thinks about it again. A sync's timeline is read
backwards and reported forwards, because a client wants the newest events
of the window it missed — a forward read with a limit hands it the oldest
and then calls the rest a gap.

visibility: history visibility is now a span rather than a yes or no, which
is what Phase 3 deferred here. A user who has left a room is served the
room as it was when they left — their state reads, their members and their
timeline — instead of being refused, and is bounded above at their own
membership event so a kicked client cannot go on streaming. Their span is
found from their own member events, so a user who joined, left and rejoined
sees their latest span. ?at= on /members is honoured for the same reason.
What is left is that the span is computed from the room's current
history_visibility where the spec judges each event by the one in force
when it was sent; that is a state read per event and belongs with open
question 1.

Typing is held in memory and nowhere else: notifications expire in seconds,
are worthless across a restart, and arrive one per keystroke-burst per
room, so persisting them would be the busiest table in the database holding
the least valuable data in it. Receipts only ever advance, compared on the
position of the event acknowledged rather than on arrival, because two of a
user's clients read at different speeds and the slower one must not drag
the marker backwards. To-device queues are per device and drained by the
next sync rather than by the one that delivered them, so a client that
crashes in between gets the batch again — the right way round, since a lost
key share leaves a message permanently undecryptable and a duplicate is
ignored. A wildcard addressee is expanded when sent, not stored, because
"every device" means the ones that existed then.

Presence is off by default, which answers PLAN.md open question 3. It is
the noisiest thing in Matrix and the one genuinely fan-out notification
here; a private homeserver gains little from it. With it off the endpoints
refuse rather than disappearing, because a client that gets a 404 from
/presence concludes the server is too old to have it and stops asking.

storage: one migration per driver adding the receipt, to-device, presence
and filter tables with a counter row each, and a stream position on the
existing account data table rather than a parallel one — there is exactly
one current value per (user, room, type), and a second table would be a
second thing to keep in step. Account data is reported in an event list but
is not an event, so it gets its own response type: a room event with an
empty sender and no timestamp would make a client decide what that meant.

Deliberately missing, each named in docs/sync.md: notification counts (they
need push rules, Phase 8), device lists (the keyserver, Phase 7), anything
remote (Phase 5), threads (Phase 10). device_lists is sent as two empty
lists because a client reads a missing one as malformed; the notification
counts are left out entirely, because a zero there is a claim and an absent
field is not.

Tested through HTTP rather than against the builder, because what is worth
pinning down is the response a client sees — which section a room lands in,
whether a token handed back can be handed in again, whether paging
terminates and loses nothing. The storage tests run against both SQL
drivers; the notifier has its own tests for the concurrent case. A live
server was driven end to end, which is what caught the two bugs the unit
tests had missed: a backwards /messages page must be in reverse
chronological order, and `start` must name where the page began rather than
position zero when ?from= was omitted.

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

server/internal/syncapi/token.go

@@ -0,0 +1,132 @@
+package syncapi
+
+import (
+	"fmt"
+	"strconv"
+	"strings"
+
+	"github.com/dariuszjaniak/warp/server/internal/storage"
+)
+
+// Token is a position in every stream a sync response carries.
+//
+// A sync response is assembled from streams that move independently: room
+// events, read receipts, to-device messages, account data and presence. A
+// client that has seen receipt 7 but only event 4 has to be able to say so
+// in the one opaque string the API gives it, so the token names a position
+// in each.
+//
+// The wire form is
+//
+//	s{pdu}_{receipt}_{to_device}_{account_data}_{presence}
+//
+// with trailing zeroes left off, so a client that has only ever seen room
+// events carries "s12" rather than "s12_0_0_0_0". The leading "s" is there
+// to make a token recognisable in a log and to leave room for a second
+// token shape later — Simplified Sliding Sync (PLAN.md phase 10) has its
+// own — without any ambiguity about which is which.
+//
+// The spec says only that the token is opaque, and clients treat it that
+// way. It is still worth being readable: a token is the first thing in
+// every bug report about /sync.
+type Token struct {
+	PDU         int64
+	Receipt     int64
+	ToDevice    int64
+	AccountData int64
+	Presence    int64
+}
+
+// tokenPrefix marks a classic /sync token.
+const tokenPrefix = "s"
+
+// IsInitial reports whether the token is the start of every stream, which
+// is what a sync with no ?since= means.
+func (t Token) IsInitial() bool { return t == Token{} }
+
+// String renders the wire form.
+func (t Token) String() string {
+	parts := []int64{t.PDU, t.Receipt, t.ToDevice, t.AccountData, t.Presence}
+	// Trailing zeroes carry no information, and leaving them off keeps the
+	// common token short.
+	last := 0
+	for i, p := range parts {
+		if p != 0 {
+			last = i
+		}
+	}
+
+	var b strings.Builder
+	b.WriteString(tokenPrefix)
+	for i, p := range parts[:last+1] {
+		if i > 0 {
+			b.WriteByte('_')
+		}
+		b.WriteString(strconv.FormatInt(p, 10))
+	}
+	return b.String()
+}
+
+// ParseToken reads a token a client sent back.
+//
+// An empty string is the initial token: /sync without ?since= and
+// /messages without ?from= both mean "from the beginning", and refusing
+// the empty string would make every caller special-case it.
+//
+// A token with fewer fields than this build writes is accepted and the
+// missing ones are zero. That is what lets a token stored by a client
+// before a stream existed go on working: the stream it did not know about
+// reads as "seen nothing", so the client is sent that stream in full once
+// and is in step from then on.
+func ParseToken(raw string) (Token, error) {
+	if raw == "" {
+		return Token{}, nil
+	}
+	body, ok := strings.CutPrefix(raw, tokenPrefix)
+	if !ok {
+		return Token{}, fmt.Errorf("%q is not a sync token: it must start with %q", raw, tokenPrefix)
+	}
+
+	fields := strings.Split(body, "_")
+	if len(fields) > 5 {
+		return Token{}, fmt.Errorf("%q is not a sync token: it has %d positions, this server writes at most 5",
+			raw, len(fields))
+	}
+
+	var positions [5]int64
+	for i, field := range fields {
+		value, err := strconv.ParseInt(field, 10, 64)
+		if err != nil || value < 0 {
+			return Token{}, fmt.Errorf("%q is not a sync token: position %d is %q", raw, i+1, field)
+		}
+		positions[i] = value
+	}
+	return Token{
+		PDU:         positions[0],
+		Receipt:     positions[1],
+		ToDevice:    positions[2],
+		AccountData: positions[3],
+		Presence:    positions[4],
+	}, nil
+}
+
+// tokenAt is the token naming the top of every stream, which is what a
+// sync response hands back when it has drained all of them.
+func tokenAt(positions storage.StreamPositions) Token {
+	return Token{
+		PDU:         positions.PDU,
+		Receipt:     positions.Receipt,
+		ToDevice:    positions.ToDevice,
+		AccountData: positions.AccountData,
+		Presence:    positions.Presence,
+	}
+}
+
+// pduToken is the token for a position in the room event stream alone.
+//
+// It is what /messages and a room's prev_batch hand out: both are about
+// room events only, and a token from either has to be usable as a ?since=
+// for /sync, where the other streams then read as unseen. That is the
+// conservative direction — the client is sent those streams again rather
+// than having them skipped.
+func pduToken(pos int64) Token { return Token{PDU: pos} }