Nondeterministic test execution order in JUnit 5

In JUnit 5, the default execution order of test methods within a class is unspecified. While this design is intended to prevent developers from creating hidden dependencies between test cases, it frequently leads to nondeterministic results across different environments or build runs.

The @TestMethodOrder annotation allows for explicit ordering using strategies like MethodOrderer.Alphanumeric or OrderAnnotation, yet the framework does not commit to a deterministic default state. This creates a dilemma for large suites where reproducibility is critical but manually enforcing order on every class is considered excessive overhead.

Is there a documented roadmap for moving the default order to a deterministic sequence such as alphabetical? Or will the unspecified order remain the permanent architectural standard to enforce test isolation?