It seems that you are correct. I had intended it be available for both, but atm it is only used during schema management.

We will correct that. IMO that is the correct solution - I think exposing this enum sets a bad expectation