[atti92]

Implement the flight-session workflow and native GCS build/release CI, and send durable history through the same version 2 archive API used by DJI Android. Recording and archive synchronization remain independent of live traffic delivery; failed or incomplete acknowledgements retain local data for retry.

Includes Mission Planner/QGroundControl integration and packaging checks, native CI build and tag-release workflows, parser diagnostics, operator configuration and troubleshooting guides, architecture diagrams, and the cross-client integration harness. The manual contract CI job accepts companion Flight Blender and DJI branch refs so all three implementations can be validated together before merge.

Validation completed locally:

• Go internal tests passed with the race detector; go vet passed.
• The real HTTP contract/workflow tests passed against Flight Blender, followed by the Android archive integration in the same harness.
• Companion Flight Blender suite: 671 passed; Android JVM suites: 149 passed, 8 environment-dependent skips.
• Workflow YAML parsing, shell syntax and whitespace checks passed.

The native build/release workflows are included; publishing this PR does not establish that every native remote CI job has passed. Server deployment, Android APK validation and physical DJI testing remain. Server archive migration must be deployed before upgrading clients.

Related to openutm/flight-blender#218. Companion pull requests will be linked below.

Companion pull requests:

• Flight Blender server: Add shared durable session archive API for Go and DJI clients flight-blender#219
• Go adapter and GCS CI: Implement flight sessions, shared archives and native GCS build/release CI #4
• DJI Android client: Archive DJI flights through the shared Flight Blender session API openutm-labs/dji-android-gcs#4

Integration CI companion refs: Flight Blender codex/shared-session-archive; DJI Android codex/shared-session-archive.