DKR-R v1.0.10 Release Build - Patch Pipeline

This layer includes the entire accepted playtest.4 chain. Do not configure
the old v1.0.9 release overlay: it predates the current online fixes.
Windows x64 and Linux x86_64/ARM64 are built. Steam Deck uses the exact Linux
x86_64 AppImage. Android, macOS and iOS are skipped.

Keep the verified frozen source capsule and prepared normal/owned/RSP,
camera, shadow and visual-model inputs read-only. Do not edit submodules,
RecompiledFuncs or RecompiledPatches. Use the matching reviewed platform
cache/toolchain; this is not a fresh-machine dependency bootstrap.

python -B patches/release-prep/v1.0.10/release.py snapshot --output <fresh-backup>
python -B patches/release-prep/v1.0.10/release.py apply --baseline <backup> --evidence <work>/evidence
python -B patches/release-prep/v1.0.10/release.py configure --build <platform-build> --capsule <verified-capsule> --log <work>/<platform>/configure.log
cmake --build <platform-build> --config RelWithDebInfo --target DKRPortGame --parallel 3

Use --cmake to select the installed CMake. The existing ARM64 cache contains
the matching V77/V80 visual-model paths. Ninja uses its configured Release
build type; do not pass x64 object files to the ARM64 linker.

audit.py verifies the complete playtest.4 chain at version 1.0.10. Pass the
post-metadata source manifest to --baseline, and the original accepted
directory BUILD-RECEIPT.json to --accepted. The snapshot verification checks
all pre-existing native authoring remains unchanged.

Build/run only the explicit synthetic fixtures using the retained
spectator-admission-repair/run_checks.py wrapper. Those checks do not run
a game, user ROM or RSP. Native updater and ROM-free worker checks are
recorded separately. Cross-compiled ARM64 tests need an emulator/sysroot;
that is separate from physical ARM64 rendering/controller acceptance.

package.py uses the existing allowlisted packager, matching legal/library
templates and inspected AppImage outer runtimes. It packages the current
compiled binaries, stable notes and updater ownership tables. Inspect both
Linux ELF trees. finalize.py checks all three build receipts and emits the
four downloads, evidence, notes and hashes. update_assets.py signs only the
finished bytes after the complete source is committed.
