mavlink-integrationlisted

# Purpose Produce MAVLink protocol code for drone communication in the edge service (project.json → device; Python 3.11+ on Raspberry Pi 5). Covers pymavlink connection types (UART, UDP, TCP), message parsing for common telemetry messages, async I/O patterns with `asyncio.to_thread`, ArduPilot SITL simulation setup, and `MOCK_MODE` for CI testing without hardware. For the WebSocket bridge from the edge service to the web portal, defer to `api-integration`. For Helm deployment of edge service pods, defer to the project's deployment workflow. Success criteria: generated code connects (or simulates connection in MOCK_MODE), sends GCS heartbeats at 1Hz, reads telemetry via `recv_match`, handles `asyncio.CancelledError` for graceful shutdown, and releases the connection on stop. # When to use - Connecting to a drone via pymavlink (UART serial, UDP simulator, TCP) - Parsing MAVLink telemetry messages (HEARTBEAT, GLOBAL_POSITION_INT, ATTITUDE, GPS_RAW_INT) - Implementing async MAVLink reader/writer patterns in the edge service - Setting up ArduPilot SITL for local development or CI testing - Configuring `MOCK_MODE` for testing without physical hardware # When NOT to use - Raw UART hardware driver code without MAVLink framing (use `embedded-systems`) - WebSocket streaming from the edge service to the web portal (use `api-integration`) - Deploying the edge service via Helm/k3s (use the project's deployment workflow) - Building Docker images for the edge service (use `docker-buil