BBLauncher corresponding source

bblauncher-source.zip contains the pinned launcher and all recursive Git
submodules. SOURCE-RECEIPT.json records every source file, dependency commit,
and the launcher executable hash. Original third-party notices remain in place.
The unused, prebuilt qtstatic and WebView2SDK directories are omitted; the
release uses the dynamic Qt SDK instead. No GitHub access is needed to extract
or build this snapshot.

To rebuild the launcher on Windows:
1. Install Python 3, CMake 3.30 or newer, Ninja, LLVM clang-cl, and Visual Studio
   2022 C++ tools with the Windows SDK. Use an x64 Visual Studio developer shell.
2. Obtain the dynamic Qt 6.10.0 MSVC x64 SDK, with qtimageformats, qtmultimedia,
   qtwebview and qtwebsockets (the same modules as the release build).
3. Run: python unpack_fork_source.py C:\bblauncher-source
4. Run: .\build_fork_snapshot.ps1 -SourceRoot C:\bblauncher-source
   -QtRoot C:\Qt\6.10.0\msvc2022_64 -ClangCl clang-cl.exe -Ninja ninja.exe
   (Pass step 4 as a single command.)

The executable is build-source\BB_Launcher.exe. The script also runs the
independent ModService and settings-import tests. The source archive includes
the AP backend/UI tests; those require the matching AP backend source/runtime.
Git-version text and build timestamps differ in a source-archive rebuild; this
is not a claim of byte-identical reproducible builds.

Qt source and original notices are provided alongside this directory in
source-qt and licenses. Qt remains dynamically linked and replaceable. To
build Qt itself, extract the listed module archives, build/install qtbase with
CMake/Ninja for Windows x64, then build the other required modules against that
installation (qtshadertools before qtdeclarative). Each module includes its
upstream build files and documentation. The Windows Qt WebView plugin requires
Microsoft's WebView2 SDK; the installed WebView2 runtime supplies browser
services. It is not included in this download.

The current native AP writers use the project's MIT-licensed BBFormats code.
Their source and Windows/Linux build recipes are in the companion
Bloodborne build-source archive, alongside the matching Python backend and
world source. The integrated launcher's companion build-source archive also
includes those sources and identifies the exact backend build revision.
The Rust client's source/dependency material is in
ap_backend\tools\source-client. Those components retain their own terms.
