Plugin suite: MeshX BLE-mesh transport stack (mob_ble / mob_transport / mob_mesh / mob_cellular / mob_wifi)

[dl-alexandre]

Hi — flagging a plugin suite we're about to publish to Hex and deploy on-device, in case you want it referenced anywhere or have concerns about the contracts we're building against.

Transport-layer plugins (implement the Mob.Transport contract; ship priv/mob_plugin.exs manifests, tier 1 where native):

• mob_transport — Mob.Transport behaviour + in-memory/TCP/UDP transports (pure Elixir).
• mob_ble — BLE native bridge adapter (NIF; iOS CoreBluetooth + Android JNI). Relates to your open BLE issues Android: Rustler 0.37 init crashes with undefined symbol: enif_priv_data #7–Mob.Bt: Bluetooth Classic peripheral (HFP/SPP/HID) #9.
• mob_mesh — epidemic/gossip mesh routing that turns point-to-point Mob.Transport plugins into a mesh.
• mob_cellular — cellular fallback transport over push-notification envelopes.
• mob_wifi — Wi-Fi transport.

On top of these, a mesh stack (mob_protocol framing/TTL/gossip, mob_noise Noise XX + Sender Keys group encryption, mob_store CubDB persistence, mob_runtime coordinator) consumed by a mob-based device app.

All build against mob ~> 0.7 (migrated cleanly off 0.6 — see the plugin-pinning note on mob_dev#21).

Questions:

1. Is there a canonical place you'd like third-party transport plugins listed/referenced?
2. Any contract-stability concerns with Mob.Transport / Mob.Transport.Adapter we should know before we pin against them in published Hex packages?