Specify the order in which one-time keys are returned (MSC4225)

Signed-off-by: Andy Balaam <[email protected]>

changelogs/client_server/newsfragments/2029.clarification

@@ -0,0 +1 @@
+Specify order of one-time keys, as per [MSC4225](https://github.com/matrix-org/matrix-spec-proposals/pull/4225).

data/api/client-server/keys.yaml

@@ -355,6 +355,13 @@ paths:
                       See the [key algorithms](/client-server-api/#key-algorithms) section for information
                       on the Key Object format.
 
+                      Keys should be returned in the order that they were
+                      uploaded via
+                      [/keys/upload](/client-server-api/#post_matrixclientv3keysupload).
+                      All keys uploaded in a given call to `/keys/upload` are
+                      considered equivalent in this regard; no ordering is
+                      specified within them.
+
                       If necessary, the claimed key might be a fallback key. Fallback
                       keys are re-used by the server until replaced by the device.
                     patternProperties:

data/api/server-server/user_keys.yaml

@@ -66,6 +66,13 @@ paths:
 
                       See the [Client-Server Key Algorithms](/client-server-api/#key-algorithms) section for more information on
                       the Key Object format.
+
+                      Keys should be returned in the order that they were
+                      uploaded via
+                      [/keys/upload](/client-server-api/#post_matrixclientv3keysupload).
+                      All keys uploaded in a given call to `/keys/upload` are
+                      considered equivalent in this regard; no ordering is
+                      specified within them.
                     # User
                     patternProperties:
                       "^@":