Skip to main content

AEROSIM-TS-173

Project task

Correct hidden terminal flight state after automatic recovery

A concluded flight is visibly terminal even when the asynchronous recovery decision shares the last physics step and recovery count.

AEROSIM-TS-173Canonical ID TASK-0173
Verified flow state
To Be Released
Owner
AeroSim Delivery
Component
Web authoritative flight recovery projection
Repository
corp-v1-aerosim/corp-v1-aerosim

Delivery scope

Attribute the retained Training Airfield traversal plateau and page errors; reproduce and repair confirmed application terminal-projection defects without changing forces, recovery policy, continuous attempt, world rebasing, or render/collision alignment.

Implementation contract

Implementation artifacts

  • applications/web/src/flight/authoritative-flight-state.ts
  • applications/web/test/flight/authoritative-flight-state.spec.ts

Inputs

  • Delivery human correction instruction 1554384013769314317 and admitted board t_5f3a1958.
  • Failed UAT t_5e618ccb and coordinator t_5c0e39c3; retained cumulative travel reaches 34723.16833496094m, then source-step/distance plateau.
  • Four historical errors lack exception stacks; exact individual attribution remains OPEN pending UAT-owned diagnostics.

Outputs

  • Publish terminal recovery decisions once, including zero-tick frames with an unchanged recovery count.
  • Return a fresh cumulative development tuple and evidence to UAT; independent acceptance remains required.

Failure boundaries

  • Fail if a CONCLUDED decision is hidden behind a previous RESTORED projection.
  • Fail if replay duplicates transitions or changes terminal physics/recovery cap/attempt identity.
  • Fail if historical hypothesis is reported as proven or page errors are suppressed.

Excluded scope

  • No flight-model tuning, new UI/design, production changes, or Delivery execution/editing of non-unit UAT.

Verification steps

  • RED-first production-path unit regression for RESTORED then CONCLUDED with same sequence and source step; verify empty and tick-bearing frames and replay idempotency.
  • Focused/full unit, static, build, audit, exact-head review/CI and integration publication.
  • Reviewed template/rendered development GitOps and exact Synced/Healthy pod/image/annotation/health readback.
  • UAT owns >42km authoritative cumulative travel, seven subject-asserted views, zero unexplained errors and unchanged fresh tuple.

Traceability

Requirements

Dependencies

Acceptance evidence

Verified delivery: reviewed PR325 and cumulative47d102e immutable artifacts deployed through template81/dev58, exact Argo/pod/source/chart/endpoint identity verified and handed to UAT. Independent UAT acceptance and historical page-error attribution remain outstanding; no production approval.

Current evidence boundary

No current implementation, acceptance, release, or deployment evidence is claimed for this planned Task. Any prior implementation may be used only as prototype and discovery evidence.

Technical delivery and independent acceptance​

Application PR325 fixes the independently reproduced hidden conclusion: successful-restore sequence counters do not advance on terminal recovery, so the authoritative projection must observe the transition separately from physics ticks. The production coordinator-to-projection regression failed before the correction and passes for absent, repeated and advancing ticks; identical terminal replay remains idempotent.

Runtime integration 92f74442554ae13c00b7ed60a3a0a8033f444247 is preserved in cumulative runtime/visual source 47d102eb416aa27849c15da955dce638a35f77a1. Local full cumulative validation passed 892 unit tests plus static checks and builds. Exact-head review, application CI6531, runtime publication6533 and cumulative publication6539 passed. Template PR81 and development PR58 selected independently verified immutable artifacts, with exact render parity and unchanged selectors.

Development GitOps 1b22f30743e8a974741814bb479e0086faa75440 reconciled automatically; root/runtime Argo applications were Synced/Healthy, ready Web/API runtime image IDs matched the selected digests, and bounded Web/API health/runtime-configuration requests returned HTTP200. The exact tuple is recorded in the canonical handoff event and UAT message1554405389259513876.

This is technical delivery, not UAT acceptance. Four historical page errors lacked retained exception stacks; their attribution remains open. The historical plateau is compatible with this independently reproduced defect, but causation is not established. UAT must freeze the fresh tuple, capture diagnostics and independently prove more than42km authoritative cumulative travel in one attempt/session, all seven subject-asserted hardware-rendered views, terrain/atmosphere acceptance and zero unexplained console/page/HTTP errors. No previous acceptance evidence transfers, and no production promotion is authorized.