I am going to predict that staff here will check the JLS.
If it is specified behavior, they will confirm it as a corner case and assent.
If the behavior in this regard is not specified in the JLS, they will consider it an implementation artifact, even if all popular JDK/JVM variants seem to agree.
But in section 12.4.1 it looks like while a corner case, this is official required behavior as per the JLS (oops, I linked to version 15 but doubt it changed since 11).
I'd say you were possibly pedantic, but definitely correct.
• A static field declared by T is used and the field is not a constant variable
I have learned my lesson about inferring rules from runtime behavior that might be a non-required implementation artifact.
That section 12.4 gives way more detail about static initializer rules and regulations than I remembered from Enthuware, Sybex or DurgaSoft material, which were three sources that go into a fair amount of tutorial on that topic.
Did you notice the suggested detail from behavior or direct JLS reference or tutorial material alluding to the rule?
RTFJD (the JavaDocs are your friends!) If you haven't read them in a long time, then RRTFJD (they might have changed!)
This is my favorite show. And this is my favorite tiny ad: