platform-parity-check

Cross-platform feature parity is verified by checking platform implementation presence, comparing against core contracts, validating UniFFI binding alignment via api.udl, and generating a structured matrix with PASS, PARTIAL, or FAIL results for critical messaging controls.

Platform parity testing ensures security-critical messaging controls like relay toggles, identity exchange, and send/receive flows behave identically across Android, iOS, and Web/WASM. It is needed when behavior must match a shared core contract to prevent regression risk and inconsistent user experiences.

UniFFI binding alignment is checked by validating the api.udl file against platform implementations to ensure shared core contract expectations are met. This detects feature regression by confirming Android, iOS, and Web/WASM implementations match the defined bindings.

Cross-platform testing works for settings alignment and consistent error handling by verifying these critical controls end-to-end across Android, iOS, and Web/WASM. It ensures identical critical-path behavior matches the shared core contract.

The best way to detect feature divergence is running a parity check that validates platform implementation presence against core contracts and UniFFI bindings. It produces a structured parity matrix identifying PASS, PARTIAL, or FAIL outcomes and remediation needs.