DKR-R v1.0.14 Release Build - Patch Pipeline

This existing baselined recipe now reads the root VERSION. Its directory keeps
the historical name; do not create another first-party patch layer. Metadata
apply/content.py is the old v1.0.11 authoring step and must not be rerun against
the current source. Configure and build the committed release directly.

The overlay includes character-library-portraits, online-performance and all
retained vehicle, graphics, memory and playtest 4 fixes. This includes the
approved profile header, pictures/friends, Linux sign-in and corrected live FOV.
ARM64 vehicle preparation and its synthetic fixtures retain -ffp-contract=off;
the shared game simulation and other compiler settings are unchanged.

Keep the verified frozen source capsule and prepared ROM/RSP inputs read-only.
Never edit submodules, RecompiledFuncs or RecompiledPatches. Windows x64 and
Linux x86_64/ARM64 are required; Deck is the exact Linux x86_64 AppImage. Android,
macOS and iOS are skipped. Never relabel an earlier binary as a new release.

python -B patches/release-prep/v1.0.11/release.py snapshot --output <fresh-backup>
python -B patches/release-prep/v1.0.11/release.py configure --build <platform-build> --capsule <verified-capsule> --log <work>/<platform>/configure.log
python -B patches/release-prep/v1.0.11/build.py --build <platform-build> --log <work>/<platform>/build.log

Run guard/tooling, installed hooks and host CTest. build.py includes the retained
14 fixture groups, vehicle before/after, current online menu/setup/lifecycle,
portraits and profile targets. Run run_checks.py with --bin, --input, --legacy
and --output. Native Linux includes the vehicle sanitizer target. ARM64 CPU/data
fixtures use --emulator and --sysroot; current online fixtures support those
arguments too. Record profiles and portraits separately. Host tests cover live
FOV, picture decoding, profile mutation fences and the shared friend service.

audit.py checks the actual final online/portrait compiler substitutions before
traversing the retained vehicle/render/memory/spectator chain. Supply a source
manifest for unchanged inputs and the verified current directory source reference.
Do not silently accept a new directory hash or replace historical artifact evidence.
package.py uses the existing allowlist, private workers and licence notices.
It copies current docs/PUBLIC-<VERSION>-NOTES.txt and packaging/RELEASE-README.md.

Read every archive back against its receipt. Inspect both ELF dependency trees
and ABI floors. Probe the packaged worker without loading mods. finalize.py
requires matching peers and prepared vehicle data, the retained/current checks,
native sanitizer and archive results. The clean upload directory gets the four
downloads and current notes. Keep private source snapshots outside that folder.

Commit the complete release source before signing. update_assets.py uses that
commit, final package receipts and the existing trusted key. qualify_updates.py
uses the verified v1.0.12 and Beta 3 Windows packages for isolated updater checks. seal.py
verifies the signed manifest and generates the exact upload list and hashes.
The maintainer publishes the GitHub release; these scripts do not publish it.
