DKR-R v1.0.9 Release Build - Patch Pipeline

This additive release layer includes the owner-accepted online-directory layer.
All previous native authoring remains unchanged. The prepare action updates only
VERSION, packaging/RELEASE-README.md and Linux AppStream release metadata, after
verifying the complete recoverable pre-release source snapshot.

Use the previously verified 1.0.7 frozen capsule and the existing prepared normal,
owned, camera, shadow, visual-model and RSP inputs. They are private, read-only
build inputs. Never edit a dependency checkout, RecompiledFuncs or RecompiledPatches.
Do not export or rebaseline the capsule to bypass a mismatch.

python -B patches/release-prep/v1.0.9/release.py prepare
  --baseline <recoverable-snapshot> --evidence <new-work>/evidence

python -B patches/release-prep/v1.0.9/release.py configure
  --build <platform-build> --capsule <verified-capsule>
  --log <new-work>/evidence/<platform>/configure.log --cmake <cmake>

Supply the existing matching visual-model inputs when preparing an older ARM64
or Android cache, with --define DKR_VISUAL_MODEL_GENERATED_V77:PATH=<v77> and
--define DKR_VISUAL_MODEL_GENERATED_V80:PATH=<v80>. Both are needed by the current
vehicle/detail layers. Compile the actual DKRPortGame target with CMake.

Android keeps platform HTTPS. Its external release stage supplies the exact
frozen relative account-page include, forwards the directory instance header only
to the trusted API, and uses standard atomic shared_ptr free functions where
Android libc++ lacks atomic<shared_ptr>. These are platform adapters, not a
different game, directory protocol or rollback implementation. Their inputs,
outputs and actual compiler replacements are byte-verified by audit.py.

package.py builds the Windows ZIP and both Linux AppImages through the prior
allowlisted packager. Use matching architecture libraries/legal material and an
inspected AppImage outer runtime. The Steam Deck file is the Linux x86_64 payload.
release.py android-recipe generates the lean packaging command with fresh Gradle
outputs. Use ReleaseBuild, version 1.0.9, code 1090001 and the original Android
update signer. inspect-apk verifies native/ZIP metadata and signer continuity.

audit.py retains every accepted directory/Scoreboard/source assertion, following
explicit release source replacements. It decodes Ninja's escaped Windows drive
colons when checking Android compiler bindings. Inspect both Linux ELF trees
with the existing inspect_elf.py. finalize.py requires all four native audits,
matching per-revision engine IDs, dependency reports and APK inspection before
collecting the five final platform downloads and SHA256SUMS.txt.

No launcher, game, mod, native test or AppImage is executed. Hardware/gameplay
acceptance is separate. No Git push, tag, public release, FTP/API deployment or
automatic-update signature is produced by this build pipeline.
