This seems fine but can you tell me more about what it breaks?

The C# code generator that we own generates strongly typed enums to represent the enums in the protocol. Adding a new item to one of these enums other than at the end causes the underlying values of the previous enum values to change, that is:

enum ContextValue {
    Watch = 0,
    Repl = 1,
    // ...
}

becomes

enum ContextValue {
    Variables = 0
    Watch = 1,
    Repl = 2,
    // ...
}

I don't think this is an issue for the TypeScript generator, since it uses union types for this instead of enums, but it breaks backwards compatibility between different versions of our protocol library.

I think depending on the order of enum types, which are effectively a Set, is a little questionable, but I'm fine taking this fix