NoCameraMotion 1.1.1 - Build validation

Build method: direct ECMA-335 managed CIL/metadata emission; not a C# compiler build.
The source archive includes the matching readable C# implementation, exact emitter,
metadata parser, simulated-behavior validator and regression comparator.

Change in this revision:
- New General/DisableRecoilCameraShake config bool, default true, read live.
- True: clear only additive recoil camera roll and local-Z translation at camera
  composition. The game still applies aim recoil normally.
- False: retain the recoil-camera composition of version 1.1.0.
- No changes to the original recoil calculation, pitch/yaw aim displacement,
  weapon recoil parameters, or firing-animation layer.

Checks completed:
- Static PE/CIL metadata, reference signatures, Harmony patch/field signatures,
  branch targets, exception regions and stack-height consistency.
- 1299 passed assertions, including per-instruction checks. This is NOT
  a count of independent end-to-end game tests.
- Simulated live config binding, new default, old-config migration, saved OFF
  preference, and repeated on/off toggles without restart.
- Simulated preservation of aim fields while suppressing camera roll/pushback.
- Simulated restoration of captured roll/pushback when the toggle is OFF.
- Existing camera, slide-animation, FOV, cleanup and rollback checks.
- Regression: 26 existing methods have identical normalized CIL to 1.1.0.
  Only Plugin.Awake (new config and version/log) and CameraControlPatch.Prefix
  (the new branch) changed; one new config getter was added.
- All slide-animation, aim-FOV and recoil-capture methods remain instruction-
  equivalent to 1.1.0. No original game/framework binary is modified.
- Supplied game recoil code contains direct pitch/yaw aim operations separately
  from its additive camera roll and local-Z translation operations.

Limitations:
- No CLR/Mono assembly loading or JIT verification in this build environment.
- No actual Harmony detours, Unity/Animancer graph, Proton or Mycopunk test.
- Animancer.dll was not supplied; its referenced signatures were checked against
  MemberRefs in the uploaded game assembly, as in 1.1.0.
- Simulations use explicit mocks for external game/framework calls.
- No verification of multiplayer behavior, mod interactions or future builds.
- No Thunderstore server-side validation, publishing or moderation submission.

Output DLL SHA256:
71d2522cba0f02871f7a8336d618d1a0774f882f634c6b0bf0680f39f24d117f

Baseline 1.1.0 DLL SHA256:
55a4bac9e8c133ceacb4a8400bb33a6ea99d14d81a3303ae38856ebf42c66b4c

Input SHA256 fingerprints (inputs are NOT redistributed):
0Harmony.dll: 1a21cc03424fc82c3dd1346905d16494536b9595ae4162228d99fb7c285c1031
Assembly-CSharp.dll: a4ce053cfb11e1b1c944407bfb21f5be7219a500990a3f7a30dd6911bbf91cab
BepInEx.dll: 9fe4a88d4f949fcdb3222a05c1902fec94f99655501e5eb60408543492ce9884
UnityEngine.CoreModule.dll: fef39af3a6462f99f541de3dc1ae0285bfbcabc8b6c9adb75d5f9f49633d80d1
UnityEngine.dll: 240fb7e3365b1f92ccbfb92ce3f07e55aac32e405cfdb246eeb133ec8cf59e9c
