Soverise Linux Agent — source install (cloud test build)
========================================================

The prebuilt-binary installer (scripts/install.sh) fetches release
artifacts that are not published yet, so install from source:

  tar -xzf soverise-agent-src.tgz && cd SoveriseDroneAgent
  python3 -m venv .venv && .venv/bin/pip install -e .

Point it at the cloud and run it (these are the same defaults the
installer bakes into /etc/soverise/env):

  export SOVERISE_CONVEX_URL=https://convex-site.soverise.metareignity.com
  export SOVERISE_MQTT_BROKER=mqtt.soverise.metareignity.com
  export SOVERISE_MQTT_PORT=8883
  .venv/bin/soverise status      # shows the claim link + QR

Then open the claim link, or scan the QR, to adopt it into your org.

Two gotchas, both verified the hard way:
  * The cloud loops (register beacon, MQTT gateway) only run in-process
    when pairing.single_process_cloud_enabled = true; otherwise they are
    owned by the managed service runtime and the agent will look idle.
  * Set config.agent.device_id explicitly for repeat tests. Without
    write access to /etc/soverise the id regenerates each boot, the
    cloud 401s the unknown id, and the agent correctly self-unpairs.

The Rust services (mavlink-router, video, crsf, plugin-host) build with
`cargo build --release` from crates/ and are NOT required for cloud
pairing, telemetry, or the MQTT lanes.