docs: describe Ground Suite scope

docs/src/SUMMARY.md

@@ -9,6 +9,7 @@
 - [Configuration](configuration.md)
 - [Logs](logs.md)
 - [Errors](errors.md)
+- [Ground Suite](ground-suite.md)
 - [Boards](boards/index.md)
   - [Kakute F7 Mini V3](boards/kakute-f7-mini-v3.md)
   - [GEPRC GEP-F722-HD V2](boards/geprc-f722-v2.md)

docs/src/ground-suite.md

@@ -0,0 +1,30 @@
+# Ground Suite
+
+`ground-suite/` is Kaptan's desktop Flutter ground-control application. Its
+first implementation is a deterministic, read-only replay console rather than
+a vehicle-control or configuration application.
+
+It currently presents a received vehicle identity and heartbeat, telemetry
+presence, ordinary `KAPTAN_LOG` records, distinct `KAPTAN_ERROR` path/detail
+records, and `KAPTAN_SHUTDOWN` observations. It sends no MAVLink bytes.
+
+This scope reflects the firmware boundary: the F722 telemetry image discards
+every inbound MAVLink frame, and SITL does not yet expose a MAVLink endpoint.
+Link presence is never presented as proof of safety, authority, arming state,
+or write capability.
+
+Ground Suite uses a receive-only source/decoder/classifier boundary. The
+replay implementation feeds typed observations today. A future live adapter
+must combine pinned MAVLink Common definitions with `kaptan.xml`, reject
+MAVLink 1 and invalid MAVLink 2 frames, validate diagnostic length fields
+before UTF-8 decoding, retain unknown severity/reason/flag values, and count
+unsupported or malformed data as parser/semantic drops without ending a
+session.
+
+Configuration screens, CBOR upload, vehicle commands, arm/calibration, and
+shutdown controls are deliberately deferred. They require the corresponding
+firmware authority, authenticated ingress, replay protection, persistence,
+and disarmed activation features first.
+
+See [Ground Suite's README](../../ground-suite/README.md) for its project
+layout, development commands, and scoped follow-up work.