pack/defaultconfigs/ - SERVER-type configs seeded into every new world
======================================================================

What this folder does
---------------------
Forge config files declared with type=SERVER are stored PER WORLD, at
<world>/serverconfig/<name>-server.toml. They are NOT read from config/.
When a world is created and a serverconfig file is missing, Forge copies it from
the instance-root `defaultconfigs/` folder; if that is also missing, the mod
writes its own hard-coded defaults.

Why Lucky Run must ship it
--------------------------
The run's "Try again" flow creates a COMPLETELY FRESH SEED AND WORLD
(planning/USER-ANSWERS.md, planning/AUTONOMOUS-HANDOFF.md "Retry and death").
Without this folder, every retry would silently revert all server-side tuning to
mod defaults - the tuning would survive exactly one world. The same applies to
the first world created on PebbleHost.

audits/04-auditor-outputs/r09.md finding PKG-08 recorded that the source
instance's defaultconfigs/ was EMPTY while a dedicated boot generated
forge-server.toml, gravestone-server.toml and jei-server.toml per world.

Provenance of the files here
----------------------------
All five were generated by the mods themselves during the Forge 47.4.10
dedicated boot recorded at dev-server/boot1.log, and copied verbatim from
dev-server/testworld/serverconfig/. They are MOD DEFAULTS, not yet tuned:

  forge-server.toml                 Forge core server settings
  gravestone-server.toml            GraveStone - death grave behaviour
  jei-server.toml                   JEI cheat/edit-mode permissions
  sophisticatedbackpacks-server.toml Sophisticated Backpacks limits
  toms_storage-server.toml          Tom's Simple Storage ranges/limits

Known gap
---------
The B1 expedition mods (When Dungeons Arise, Towns and Towers, Mowzie's Mobs,
Creeper Overhaul, Ender Zoology, Friends & Foes, the YUNG's set, Explorify and
their libraries) have NOT been booted yet in this workstream, so any SERVER-type
configs they generate are not represented here. After the first
pack/content-test-server boot, copy any new <world>/serverconfig/*.toml into this
folder before building a release.

Tuning notes to revisit (not yet applied - defaults shipped deliberately)
------------------------------------------------------------------------
* toms_storage-server.toml: audits/04-auditor-outputs/r03.md (SS-05) flags open
  upstream crashes #710/#751 on Forge 1.20.1 crafting terminals and recommends
  seeding deliberate inventoryConnectorRange / invCableConnectorMaxScanSize
  values rather than defaults, plus a dedicated-server shift-click craft test
  with >40 connected chests and two players on one terminal.
* gravestone-server.toml: the run keeps normal graves on final death
  ("Final death creates a normal grave"), so grave behaviour must stay enabled.

Release gate
------------
Create a brand-new world and confirm <world>/serverconfig matches this folder
file-for-file. This gate belongs to the release build (owned by another worker).
