fix: label Simurgh fleet altitude evidence

Close the current Simurgh work as a documented SITL proof-of-feasibility checkpoint.

Author: alireza787b

CHANGELOG.md

@@ -10,6 +10,11 @@ and this project uses simple two-part versioning: `X.Y` (Major.Minor).
 ## [Unreleased]
 
 ### Fixed
+- Fleet status now follows the shared altitude policy and labels relative,
+  local, barometric, and MSL frames explicitly instead of showing an MSL
+  fallback as an unlabeled relative altitude. Current telemetry now uses
+  `Flight state` with explicit landed, altitude, vertical-speed, and
+  home-distance evidence rather than the confusing `Final state` label.
 - SITL tracked-command submission now verifies that each selected running
   container sends execution callbacks to the active GCS endpoint before
   dispatch. A mismatched callback port/IP is rejected with an actionable
@@ -26,6 +31,9 @@ and this project uses simple two-part versioning: `X.Y` (Major.Minor).
 ## [5.5.111-simurgh-operator-beta] - 2026-07-26
 
 ### Added
+- Simurgh feasibility checkpoint documenting the successful bounded SITL
+  workflow, its evidence, known limitations, and explicit demo-only maturity
+  boundary. The refreshed public SITL image remains intentionally deferred.
 - Explicit registry-owned assistant orchestration metadata now determines which
   guarded tools semantic planning may use and how their terminal result is
   monitored; unrelated guarded endpoints are no longer misclassified as SITL

README.md

@@ -27,6 +27,22 @@ MDS is a field-operations and research platform, not certified avionics. Flight
 testing requires qualified operators, local aviation compliance, geofencing,
 failsafe review, and independent safety validation.
 
+### Simurgh maturity boundary
+
+Simurgh Operator is currently a **demo / proof-of-feasibility beta**, not a
+production-ready or safety-certified autonomy product. The completed SITL
+checkpoint demonstrates that typed intent, guarded confirmation, monitored
+actions, telemetry evidence, and ULog review can work together in a repeatable
+operator workflow. It does not establish production readiness, real-aircraft
+approval, or commercial/field safety.
+
+Use Simurgh only with the documented human-confirmation and circuit-breaker
+controls in a trusted SITL or review environment. Treat telemetry gaps,
+ambiguous state, provider behavior, and all remaining deferred items as
+operator-visible limitations. Real-aircraft and commercial hardening are
+explicitly deferred to a later phase; see the
+[Simurgh feasibility checkpoint](docs/plans/2026-07-27-simurgh-feasibility-checkpoint.md).
+
 ## Start Here
 
 | If you want to... | Start here |
@@ -113,7 +129,7 @@ They remain standalone projects and are not required for a first SITL demo.
 ## Product Highlights
 
 - **Single operator surface**: React dashboard for monitoring, control, QuickScout, Swarm Trajectory, and log review
-- **Governed AI operator**: Simurgh combines live MDS evidence, multilingual semantic planning, human confirmation, durable progress, and circuit-breaker enforcement
+- **Governed AI operator demo**: Simurgh combines live MDS evidence, multilingual semantic planning, human confirmation, durable progress, and circuit-breaker enforcement as an early proof-of-feasibility beta
 - **Modern SITL workflow**: prebuilt PX4 Gazebo SITL image, fast container startup, and reproducible custom-image tooling
 - **Operational visibility**: unified logging across GCS, drones, and frontend error reporting with exportable sessions
 - **Drone Show pipeline**: staged SkyBrush ZIP import, processed trajectory plots, readiness gating, and synchronized launch control

config/agent_assistant.yaml

@@ -54,6 +54,10 @@ provider_input_template: |
 
   Return concise, practical guidance. Do not invent tool results or action
   execution that is not present in the supplied context.
+  Simurgh is an early SITL/demo proof-of-feasibility beta, not a production-ready
+  or safety-certified autonomy product. Never imply real-aircraft approval,
+  unattended safety, or commercial readiness; keep human confirmation, the
+  circuit breaker, and explicit telemetry uncertainty visible.
 semantic_routing_instructions: |
   You are the semantic-understanding layer for Simurgh, an MDS drone GCS assistant.
 

docs/README.md

@@ -67,6 +67,7 @@ Welcome to the MDS documentation. This index routes operators, maintainers, and
 - **[Runtime Evidence Reporting](guides/runtime-evidence-reporting.md)** - generic Markdown/HTML/PDF package generation for accepted validation runs without customer-specific leakage
 - **[Mission Planning Workspace](features/mission-planning-workspace.md)** - shared QuickScout and Swarm Trajectory planning rules, altitude/terrain doctrine, and job/error policy
 - **[Simurgh Operator](guides/simurgh-operator.md)** - dashboard assistant, provider, MCP, policy, and validation guide
+- **[Simurgh Feasibility Checkpoint](plans/2026-07-27-simurgh-feasibility-checkpoint.md)** - accepted SITL evidence, demo-only boundary, telemetry fix, deferred backlog, and restart recipe
 - **[Simurgh Beta Recovery And PM Retest Checkpoint](plans/2026-07-27-simurgh-beta-recovery-and-pm-retest.md)** - durable continuation, release, official/client sync, cleanup, and PM handoff state
 - **[Simurgh Read-Only Checkpoint](guides/simurgh-readonly-checkpoint.md)** - historical checkpoint retained for project history; not indexed as live agent context
 - **[Simurgh MCP Client Recipes](guides/simurgh-mcp-clients.md)** - n8n, Claude, VS Code, and custom-agent connection guidance