Dragon Ball Z: Ultimate Battle 22 0.1.1 — setup package
Platform: windows-x64

One zip for first install and updates. Does NOT include disc images, retail
BIOS dumps, pre-generated game C, or a bundled build-tool pack. Emitters
(psxrecomp-game / psxrecomp-bios) and the CLI are inside psxrecomp/.
Standalone:
1. Install Python 3.
2. Run Dragon_Ball_Z_Ultimate_Battle_22.
3. Provide your legally owned Dragon Ball Z: Ultimate Battle 22 (Europe) disc and your own SCPH-5552 (Europe) BIOS dump (524288 bytes; SHA-256 1faaa18fa820a0225e488d9f086296b8e6c46df739666093987ff7d8fd352c09).
4. Follow the Generate & rebuild wizard. On first rebuild the host downloads
   cmake-clang-v1 from RetroPortingToolKit/RetroPorting-Toolchains (or you can
   pick a local cmake-clang-v1-*.zip for offline builds). System cmake/ninja
   also works if already on PATH.

Retro uses this same zip: it harvests emitters into a shared SDK cache,
downloads the toolchain pack (or uses RETCOMM_TOOLCHAIN_DIR), and preserves
saves/user config across updates.

Diagnostic mode (if the game crashes, freezes, or misbehaves):
- Setup builds the normal product in build-release/. The diagnostic product
  (build-diagnostic/: debug server, freeze heartbeat, freeze dumps) is built
  the first time you ask for it; the normal build is not rebuilt or changed.
- To switch, create an empty file named diagnostic-mode.txt next to
  Dragon_Ball_Z_Ultimate_Battle_22 and start the game as usual (or run Dragon_Ball_Z_Ultimate_Battle_22 --diagnostic).
  Delete the file to go back to normal mode.
- Reproduce the problem, quit, then run Dragon_Ball_Z_Ultimate_Battle_22 --collect-diagnostics.
  It writes diagnostics-<date>.zip next to Dragon_Ball_Z_Ultimate_Battle_22: attach that file to
  a GitHub issue on this title's repository. It contains only the runtime's
  report files (never saves, BIOS, or disc images).
See psxrecomp/docs/DIAGNOSTIC_MODE.md for details.
