chore: scrub named third-party GCS/configurator references (#63)

[jamesagarside]

Closes #63

Summary

Repo-wide scrub of named third-party GCS/configurator references (Mission Planner, QGroundControl, APM Planner 2), reframing each capability/format generically per Helios's standing convention. Genuine wire-format/file-format identifiers were deliberately left intact.

Scrubbed references (file:line → change)

Source (lib/)

• lib/core/mission/mission_file_service.dart:33-38 — class doc: "QGC Plan / ArduPilot waypoint formats", "QGroundControl compatible", "ArduPilot/Mission Planner compatible" → generic .plan JSON and .waypoints (WPL) file-format descriptions.
• lib/core/params/parameter_service.dart:221 — "Export parameters to Mission Planner .param format" → "Export parameters to the .param file format".
• lib/core/params/param_file_service.dart:27-30 — supported-formats doc dropping "ArduPilot"/"Mission Planner"/"QGC" tool framing → generic .param and .params file-format descriptions.
• lib/core/params/param_file_service.dart:102 — "Parse ArduPilot/Mission Planner .param format" → "Parse the .param file format".

Website + README

• README.md:50 — "alongside QGroundControl, Mission Planner, and other great GCS tools" → "alongside other great ground control stations".
• website/llms.txt:40-44 — "joins QGroundControl, Mission Planner, and APM Planner 2" comparison list → generic ecosystem framing.
• website/llms-full.txt:173-177 — two FAQ entries comparing to QGroundControl / Mission Planner → generic "other open-source MAVLink ground control stations" / "ArduPilot-focused configurators".
• website/index.html:88,91 — FAQ question + JSON-LD answer comparing to QGroundControl/Mission Planner → generic phrasing.
• website/features.html:7 — meta description "Compare with QGroundControl and Mission Planner" → "A modern open-source ground control station".
• website/features.html:268 — community paragraph naming QGroundControl/Mission Planner → "Established ground control stations and the ArduPilot and PX4 firmware projects".
• website/ground-control-station.html:22 — SEO keywords "mission planner alternative, QGroundControl alternative" → generic "open source GCS alternative, ground control station alternative".
• website/ground-control-station.html:59,67 — two FAQ JSON-LD answers → generic station archetypes.
• website/ground-control-station.html:152-162 — two comparison cards (<h3>QGroundControl</h3>, <h3>Mission Planner</h3>) → "Cross-platform community stations" / "ArduPilot configurators".
• website/ground-control-station.html:168 — closing paragraph naming all three tools → generic archetypes, "using more than one".

Wire-format / file-format identifiers deliberately LEFT intact

• lib/core/mission/mission_file_service.dart — QGC WPL / QGC WPL 110 (lines 74, 284, 312, 314): literal magic header of the .waypoints WPL format that production code emits and parses. Also 'Not a QGC Plan file' (158) and the // QGC Plan (.plan) section marker (80) — .plan format identifier, not a tool comparison.
• test/core/mission/mission_file_service_test.dart:40,45 — asserts the QGC WPL 110 header; left intact (validates the wire constant).
• lib/core/params/param_file_service.dart — saveQgc / _loadQgc public API symbols and QGC .params / "QGC format" detection comments (46-49, 87, 93, 123-124): file-format identifier for the space-delimited .params format, not a named-tool reference.
• test/core/params/param_file_service_test.dart:74-84 — 'QGC format' test group / saveQgc calls; left intact (format identifier + API symbol).

Reconciliation note

Checked origin/docs/update-marketing-recent-features — it has no diff against main and still contains the named-tool references, so no in-flight docs work was scrubbing these. No double-edit.

Validation

make check (analyze with --fatal-warnings + tests) passes — exit 0, zero error/warning severities. Edits are comment/copy-only, so format strings are unchanged.

native/macos/libduckdb.dylib and the regenerated packages/duckdb_dart_patched/pubspec.lock were intentionally NOT staged.