World Dimension Loader 1.4.0 - Release Notes

World Dimension Loader 1.4.0 stabilizes physical Dimension IDs for runtimes that do not use Reset and strengthens runtime-authority safety.

============================================================
Main changes
============================================================
- Newly initialized runtimes with reset_on_empty=false use the fixed physical Dimension ID wdl:<id> without a timestamp.
- Reset-OFF storage stays under dimensions/wdl/<id>/.
- reset_on_empty=true keeps the 1.3.0 timestamp Generation Rotation architecture.
- Changing a fixed runtime from false -> true does not rename it immediately; the first actual Reset rotates it to a timestamp generation.
- Existing 1.3.0 timestamp runtimes are not reverse-migrated when Reset is later disabled.
- No timestamp -> fixed-ID in-place migration command is added.
- Ambiguous physical storage without exact lifecycle authority fails closed instead of being guessed, moved, or deleted.
- Destructive/recovery authority takes precedence over later Config cancellation when a Reset transaction has already committed to that stage.
- Startup GC does not delete candidates whose current/retired status cannot be proven.
- Reset diagnostics separate routine waiting (`WDL RESET DEFERRED` INFO) from terminal fail-closed stops (`WDL RESET BLOCKED` ERROR), and dedupe repeated non-terminal reasons per operation/phase.

============================================================
Config
============================================================
WDL 1.4.0 adds no new Config keys and changes no Config defaults.
Existing Config files do not need to be regenerated solely for this update.
Regenerate only if you want the newest generated comments, after making a backup.

============================================================
Important compatibility note
============================================================
New 1.4.0 Reset-OFF storage is `dimensions/wdl/<id>/`. The older `dimensions/worlddimensionloader/<id>/` path is only relevant when an existing legacy canonical authority is already present.

Do not manually rename or move dimensions/wdl/... or dimensions/worlddimensionloader/... to force an existing timestamp runtime into a fixed ID.

The supported way to obtain a fixed physical Dimension ID is to initialize a new/pristine runtime with Reset disabled.

A Dimension that actually uses Runtime Reset may rotate to timestamp generations and therefore cannot be promised a permanently fixed physical ID.

============================================================
Reset warning
============================================================
Reset rebuilds the next runtime generation from the imported source copy.
Builds, block changes, entities, and other runtime changes may be lost.

Safe default cleanup keeps retired generations until restart, so repeating Reset before restart can temporarily use substantial disk space.

============================================================
Optional compatibility
============================================================
Valkyrien Skies and Distant Horizons are not required.
Current protection/testing was centered on Valkyrien Skies 2.4.11 and Distant Horizons 3.2.0-b behavior.
Unknown future versions are not guaranteed.
