0.1.2 — Forge server configuration and admin command usability
Baseline: 0.1.1 (meteor stability), after the failed infected-container work was discarded. Dimensional spawning was re-tested and confirmed functional; no spawning code was changed.

Problem: phayriosisreborn-common.toml was a manually parsed global NEW-WORLD template, not a registered Forge ModConfig. Generic Forge config GUIs such as Configured could not discover it. World gameplay settings were persisted in a SavedData .dat and old commands exposed only a subset of fields. On restart, the optional old common-file override flag could overwrite saved settings, adding confusion about what was authoritative.

Change:
- Added ForgeConfigSpec registered as ModConfig.Type.SERVER from PhayriosisrebornMod constructor, file name phayriosisreborn-server.toml in each world's serverconfig directory.
- Added a one-time migration marker in Overworld SavedData: phayriosisreborn_server_config_migration. On the first server start after upgrade, the existing world settings or the Create World draft are copied into the server config. This preserves existing settings. Later starts apply the world's Forge server config to SavedData.
- Added a Forge config-reload subscriber so editing the server TOML with a supported GUI or through config reload updates the active world, with execution marshalled to the MinecraftServer thread.
- Added operator Brigadier command /phayconfig list, /phayconfig get <key>, /phayconfig set <key> <value> (permission level 2). Changes save the server config and immediately mirror onto SavedData and old MapVariables.
- Kept the global phayriosisreborn-common.toml loader for backwards-compatible new-world templates and older modpack defaults; it is NOT a registered Forge config, and should not be edited as the authoritative setting for an already migrated world. The old override_existing_world_settings flag should remain false.
- Dangerous starting-state operations (phase points, max-power initialization) remain as New World settings / existing admin commands, and are not repeatedly applied by the new server config.
- No changes to block infection, dimensional spawning, meteor systems, visual assets, sound or general world generation.

Compatibility and limitations:
- Forge 1.20.1 47.4.x and Java 17 only.
- Configured is optional. A supported version must be installed to view/edit the registered Forge SERVER config through its UI. Access on dedicated servers depends on the GUI's support for remote server configs and permissions.
- Existing worlds' prior SavedData options take precedence the first time version 0.1.2 starts; if an admin manually creates the new server config in an old world before first run, the migration will replace those custom values once. Run the world once before editing its new server config.
- Previously existing commands that change infection settings outside /phayconfig may still update SavedData without updating server TOML. Prefer /phayconfig for persistent settings that survive the next restart. Existing phase/points commands operate on progression state, not this configuration file.

Validation: Java 17 compiled code, runtime method signatures validated against Forge 1.20.1 API documentation and SRG mappings, original 0.1.1 jar comparison, ZIP validation, bytecode verification and constructor call integrity. In-game Forge/Configured integrated and dedicated runtime testing still required. No full mod source project shipped; patch sources and preserved maintainer references are included separately.
