Harden experimental Ozealis firmware and add BLE v2 mobile stack

[jeremie5]

Summary

• Add fail-safe motor, pressure, VIN, sensor, fault-latch, calibration, and accessory-control behavior.
• Introduce the BLE v2 control/diagnostic contract, paged retained CSV transfer, OTA interlocks, and oximetry support.
• Add the Expo mobile controller with validated settings, session-scoped transfer recovery, exports, and PLX parsing.
• Document experimental limitations, Rev 3/MCF8316D bring-up, safety, security, calibration, and release-evidence requirements.
• Add reproducible PlatformIO/mobile CI, firmware size checks, protocol verification, dependency-audit baselines, and repository-hygiene checks.

Why

The public repository had fallen far behind the local firmware/mobile work and lacked a reproducible release boundary. This establishes a reviewable source-release baseline while keeping hardware and connected-security limitations explicit.

Validation

• node scripts/verify-local.mjs
  • clean mobile lockfile install
  • Expo compatibility
  • production dependency audit baseline (11 moderate, 0 high/critical)
  • mobile validation, retained CSV transfer, PLX, TypeScript, and web export
  • both pinned firmware environments
  • firmware flash budgets
  • protocol, documentation, release-text, Simple-mode, and repository-hygiene checks

Release boundary

This is source-release hardening, not hardware readiness. Real-device, independent-instrumentation, BLE authorization, OTA trust, Rev 3 board, and MCF8316D commissioning evidence remain required by docs/release-checklist.md.