fix: ease onboarding with startup warnings and doc corrections

- Warn at startup when quest files are missing (clients crash without
  them) and point users to the download link
- Fix Host config description: it's the advertised IP, not a bind
  address — 0.0.0.0 was wrong advice
- Load bundled schemas (shops, events, gacha) in Docker init so new
  users get working demo data out of the box
- Renumber duplicate patch schema 28 → 32 to resolve numbering
  collision
- Fix patch schema example filename to use hyphens matching actual
  files

README.md

@@ -58,7 +58,7 @@ Docker handles the database automatically. You only need to provide quest files
 3. Apply any patch schemas from [schemas/patch-schema/](./schemas/patch-schema/) in numerical order:
 
    ```bash
-   psql -U postgres -d erupe -f schemas/patch-schema/01_patch.sql
+   psql -U postgres -d erupe -f schemas/patch-schema/01-example-patch.sql
    # Repeat for each patch file
    ```
 
@@ -159,7 +159,7 @@ Edit `config.json` before starting the server. The essential settings are:
 
 | Setting | Description |
 |---------|-------------|
-| `Host` | Bind address. Use `127.0.0.1` for local, `0.0.0.0` for remote access |
+| `Host` | IP advertised to clients. Use `127.0.0.1` for local play, your LAN/WAN IP for remote. Leave blank in config to auto-detect |
 | `ClientMode` | Target client version (`ZZ`, `G10`, `Forward4`, etc.) |
 | `BinPath` | Path to quest/scenario files |
 | `Language` | `"en"` or `"jp"` |