fix(emulation): complete native backend validation contracts

[gmh5225]

ARM64 native CI could not publish its compilation evidence: GCC rejected compressed x86 decoder statements, and the build auditor treated CMake cache comments and blank lines as part of option names. Update the pinned Capstone fork to its corrected next revision and make cache parsing respect line boundaries. ARM64 jobs also select their native backend explicitly.

The complete GoogleTest method runner now accepts the boolean RUN_SERIAL property, retains it in grouping and cross-run contracts, and preserves sequential child retirement. Unknown properties, malformed values and changed shard contracts still fail. New policy text lives in NativeMethodExecution.def; all eleven testing guides are synchronized.

Validation: 326 Python checks pass, including documentation/provenance, workflow configuration, method execution, shard audits and native build/host probes; the documentation checker passes across 297 Markdown files and ten translations. The Capstone fix passes all 70 x86 unit tests with GCC 15 and Clang 21, and its production decoder has identical preprocessed token streams before and after. The GCC native component target builds with warnings kept as errors. Capstone fix is merged into next.

The full hosted KVM baseline at 26a957a6c11bf9cdb6a5f0c0351f2ab1c40f2061 passed all 5,322 required cases, with exact inventory, driver-fixture and SDK hash audits. Complete local method execution at 71e1c0dbf3ea1383babaf3e78d00a2e59fee0ffd passes: all 5,322 required KVM checks, 6,432 total passes, 12,448 typed skips and zero failures across 18,880 registered identities. All 1,049 original child XML files, process statuses and published outcomes reconcile exactly; 48 driver images, 180 fixture inputs and 1,013 SDK files match the snapshot. The sole local dirty-source exception is the unrelated signatures submodule, preserved without staging it. The native ARM64 CI at 71e1c0dbf3ea1383babaf3e78d00a2e59fee0ffd passes both native backend component builds (GCC on Linux ARM64 KVM; MSVC on Windows ARM64 WHP) and both Windows caller-context jobs. Offline auditing of the downloaded artifacts confirms all three KVM ARM64 ELF objects and both WHP ARM64 COFF objects, their source/object hashes, active backend definitions and compile recipes. Both native host probes complete with explicit availability evidence: the Linux runner has no /dev/kvm (ENOENT), and Windows reports HypervisorPresent=false. Native ARM64 guest execution remains unverified; successful compilation is not a VM execution result.