NotificationQuery

The filters both notification listings accept, as one value rather than as five parameters.

GET /notifications and GET /repos/{owner}/{repo}/notifications declare exactly the same filter set, so one type serves both. Built by starting from NotificationQuery.Empty and naming what should change:

NotificationQuery.Empty
 .includingRead
 .withSubjects(Vector(NotificationSubjectFilter.Pull))
 .updatedSince(lastSync)

'''Only what is set is sent.''' An unset filter contributes no query parameter at all, which matters because Forgejo's defaults are not this library's to guess: the documented default is unread and pinned threads, and an empty status-types= is not the same request as no status-types at all.

The builder methods exist because .scalafix.conf bans default arguments, and a five-argument copy at every call site would be worse than either. Each returns a new query; the type is immutable and safe to share.

==all and status-types overlap, and nobody has measured how==

all=true is documented as "show notifications marked as read", which is also what status-types=read asks for. Which one wins when both are sent, and whether all=true widens or replaces status-types, is not stated by the spec and could not be probed — the endpoint needs a token, so golden/MANIFEST.md has no capture of it. This library sends whatever the caller set and does not reconcile the two; if that matters to a caller, set one of them and not both.