remove experimental ground-suite project

Signed-off-by: Onur Özkan <work@onurozkan.dev>

docs/src/SUMMARY.md

@@ -9,7 +9,6 @@
 - [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/getting-started.md

@@ -24,7 +24,6 @@ target-specific commands in [Development and verification](development.md).
 | `firmware/platforms/stm32f7/` | Reviewed F722 RTIC platform and peripheral ownership. |
 | `firmware/libs/` | Typed math, estimation, control, safety, protocol, and driver crates. |
 | `firmware/tools/sitl/` | Host-only closed-loop Gazebo simulation. |
-| `ground-suite/` | Desktop ground-control application. |
 | `docs/` | This Markdown documentation site. |
 
 Do not add board-local READMEs. Add a page here instead, then link it from

docs/src/ground-suite.md

@@ -1,72 +0,0 @@
-# Ground Suite
-
-`ground-suite/` is Kaptan's desktop Flutter application. Its primary
-workspace is the Tactical Command surface: a spatial local scene, local units,
-and session-local drawings and markers. The decoded diagnostic event stream is
-always reachable from the tactical header.
-
-## Application model
-
-The core model keeps these concepts independent:
-
-- **Vehicle definition** — immutable reviewed profile, catalog identity, and
-  bundled presentation media.
-- **Local fleet unit** — an operator-created instance of a vehicle definition.
-  Local-unit IDs and in-memory planning placements belong to the workspace,
-  not the vehicle definition. Current placement is local presentation data and
-  is not yet persisted.
-- **Received vehicle data** — transport input and diagnostic events. It cannot
-  create, position, identify, or authorize a local fleet unit.
-
-This separation gives the fleet interface a stable path from local planning to
-future live operation without coupling visual selection to incoming telemetry.
-
-## Tactical workspace
-
-The default route is Tactical Command. Its map-edge `UNITS`, `CURSOR`, and
-`VIEW` groups are local interactions, not MAVLink controls. `Selection cursor`
-is the default mode for map and rectangle selection. `Pencil cursor` creates
-session-local freehand strokes; its top toolbar controls hue, saturation,
-brightness, and thickness. `Marker cursor` has an independent full-color
-style and creates a named local marker only after a map click and explicit
-save. The shared disclosure keeps local scene data,
-vehicle link state, and command authority separate. Local drawings and markers
-are never reported vehicle positions.
-
-`Add local unit` opens the horizontal local hangar. Choosing a definition only
-prepares a local unit draft; the explicit setup confirmation creates and
-selects a locally scattered scene unit, without asking the operator to click
-the map. Local setup currently permits only the workspace label. Vehicle
-configuration remains unavailable until verified binding, compatible schema,
-command authority, and safe activation are available. This presentation
-placement is temporary until reviewed MAVLink position data can drive a
-distinct reported-position layer. The right inspector and bottom selection
-console are available outside the map for keyboard and assistive-technology
-access. These interactions create only session-local workspace data.
-
-## Architecture
-
-```text
-VehicleDataPort -> typed observation updates -> observability state -> event stream
-Vehicle catalog -> local-unit workspace state -> tactical scene and unit inspector
-```
-
-The transport path and local-fleet path intentionally meet only through future
-explicit bindings. A future MAVLink adapter combines pinned MAVLink Common and
-Kaptan dialect definitions at the decoding boundary.
-
-## Follow-up work
-
-- TODO(gcs-fleet-storage): versioned persistence for local units and catalog
-  identities.
-- TODO(gcs-source-binding): explicit source-to-unit binding.
-- TODO(gcs-map-pose): coordinate datum, timestamped pose, uncertainty, and
-  staleness handling for physical map placement.
-- TODO(gcs-map-renderer): owned Linux GPU map host, pinned MapLibre assets,
-  and reviewed vector/DEM data source.
-- TODO(gcs-platform-match): compare reported build/schema metadata to the
-  local definition.
-- TODO(gcs-command-surface): add command interaction only with its reviewed
-  authority, target-binding, and safety contracts.
-- TODO(gcs-catalog): generate installed definitions and category metadata from
-  reviewed firmware build manifests.

docs/src/index.md

@@ -12,8 +12,7 @@ Markdown.
 ## Index
 
 - New contributors should read [Getting started](getting-started.md).
-- Firmware source and its Rust workspace begin in `firmware/`; the desktop
-  application is a sibling project in `ground-suite/`.
+- Firmware source and its Rust workspace begin in `firmware/`.
 - Board work belongs under [Boards](boards/index.md).
 - The currently supported closed-loop simulation is [Host SITL](sitl.md).
 - [Configuration](configuration.md) distinguishes the current SITL profile