set_presence wording is unclear

Link to problem area:

• https://spec.matrix.org/v1.7/client-server-api/#get_matrixclientv3sync Request parameters
• https://spec.matrix.org/v1.7/client-server-api/#presence

Issue

From the second link:

https://github.com/matrix-org/matrix-spec/blob/8b51f1c0110384a970b777afdc11d76b17f4e97d/content/client-server-api/modules/presence.md?plain=1#L17-L25

This makes it sound like presence is a three-valued enum.

From the first link:

https://github.com/matrix-org/matrix-spec/blob/45b6aaf07ae119a0e284192d6de8a13cf668d06f/data/api/client-server/sync.yaml#L91-L105

This describes three query parameter key-values pairs: set_presence=online, set_presence=offline, and set_presence=unavilable. The wording for offline is particularly confusing:

Otherwise if the parameter is set to "offline" then the client is not marked as being online when it uses this API.

This sounds like set_presence=offline is effectively a no-op that doesn't alter the current present state of the user.

It is hard to reconcile these two views. I see two possibilities:

1. set_presence=offline really does set your presence state to offline. If this is true,
   • the query parameter name makes sense,
   • the description of set_presence is confusing, and
   • there is no way to call /sync without affecting your current presence state. (I want such a way for https://github.com/matrix-org/sliding-sync/issues/217.)
2. set_presence=offline is a no-op on your presence state. If this is true,
   • the query parameter name is misleading here,
   • the description of set_presence is slightly confusing, and
   • there is no way to set your presence state to offline using /sync.

Both options seem confusing and inconsistent.

I would like to understand which of these is true and update the spec to make this clearer.

Start with content/client-server-api/modules/presence.md lines 17-25 and data/api/client-server/sync.yaml lines 91-105, then compare the cited Matrix client-server API sections. Resolve the intended semantics of set_presence=offline and update both descriptions so they state the behavior consistently. Done means the enum wording, parameter documentation, and offline behavior no longer conflict.