In the /sync response tree: invite_state should just be state.

Nobody has claimed this yet.

In the `/sync` response tree https://matrix.org/docs/spec/client_server/unstable.html#get-matrix-client-r0-sync for invited rooms, the key `invite_state` is used rather than `state` which is otherwise used elsewhere.

This might have been chosen on purpose to indicate that invite state events may not be complete events. Nevertheless, the client knows they are interpreting state events under the `rooms.invite` object and has enough information to know this fact.

The different name for this key makes reusing the same code-paths for handling aspects of `/sync` more difficult for both client and server authors. It has been a surprise gotcha for me now, twice, on both ends.

Start with the linked `/sync` client-server specification section and inspect the invited-room response tree and nearby references to `invite_state`. Rename the key to `state` consistently where appropriate, then verify that the documented response structure and related references agree.

Written by the indexing model from the issue text.