Validate C# telemetry consent parity against the Rust SDK and FFI contract #1115

Relevant area(s)

Linux, macOS, Windows

Brief description of your issue

scripts/check-telemetry-policy-parity.js derives both TypeScript and C# expectations from the executor CLI protocol in consent_protocol.rs. The C# SDK consumes mxc_ffi, whose result and reason values are produced by src/core/mxc-sdk/src/telemetry.rs and do not exactly match the private CLI protocol. The gate can therefore pass while the C ABI and C# binding have drifted.

Review: #822 (comment)

Steps to reproduce

1. Compare ConsentResult and StatusReason in consent_protocol.rs with the Rust SDK consent enums.
2. Note CLI-only values such as presentationUnavailable and status reasons such as policy-blocked and presentation-unavailable.
3. Run node scripts/check-telemetry-policy-parity.js.

Expected behavior

TypeScript expectations are checked against the executor CLI protocol, while C# expectations are checked against the Rust SDK/C ABI producer it consumes.

Actual behavior

Both bindings are checked against the CLI protocol, so C ABI-to-C# drift can go undetected.