Skip to main content

AEROSIM-TS-176

Project task

Complete interactive pre-flight setup

The player completes an interactive Input → Camera → Flight sequence and launches with the actual selected and validated control bindings.

AEROSIM-TS-176Canonical ID TASK-0176
Verified flow state
Unverified
Owner
AeroSim Architecture and Delivery
Component
Pre-flight setup and launch/runtime binding continuity
Repository
corp-v1-aerosim/corp-v1-aerosim

Delivery scope

Implement working Input → Camera → Flight tabs with a stable shared header and tab geometry; Keyboard/Joystick device selection; a five-row Assign/Reset mapping experience with mapping count/progress; and mapping state retained across tabs and device switching according to the verified governed design. Provide Back to Flight Setup, Continue through tabs, and final Start Flight. Carry the actual selected bindings into launch/runtime. Preserve immediate camera selection without redundant confirmation and existing launch validation.

Implementation contract

Implementation artifacts

  • applications/web/src/preflight/PreflightBriefingScreen.tsx
  • applications/web/src/App.tsx
  • applications/web/src/flight/controls/

Inputs

  • MartynasP requested exactly two corrective backlog Tasks and Release 2.0.0 planning inclusion: https://discord.com/channels/1518726359512387766/1537544173366943886/1555105892108607509
  • Bounded source discrepancy report, not visual/UAT acceptance: https://discord.com/channels/1518726359512387766/1537544173366943886/1555105221502570566 and https://discord.com/channels/1518726359512387766/1537544173366943886/1555105221179478079
  • Application source inspected by Scope: https://gitea.lego-cloud.eu/corp-v1-aerosim/corp-v1-aerosim/src/commit/9bdc1a093b0f8ae306708bea591f898dfe6adb20/applications/web/src/preflight/PreflightBriefingScreen.tsx — static Input/Flight/Camera tab labels and DEFAULT_CONTROL_SELECTION do not provide the complete interactive device/mapping experience. This is not a full capability audit.
  • Corrective provenance: TASK-0101, TASK-0102, TASK-0137, TASK-0149 and TASK-0153 retain their historical completion and evidence. TASK-0171 records later immediate camera selection and must not be regressed. These are provenance links, not newly approved execution dependencies.

Outputs

  • Working ordered tabs, device selection and five-row mapping with explicit Assign/Reset and progress.
  • One selected mapping state carried through navigation, validation, launch and runtime without resetting or silently reverting to defaults.
  • Exact-design comparison and ordinary-user journey evidence on the candidate accepted for UAT.

Failure boundaries

  • Fail if tabs remain decorative, tab order or shared geometry drifts, or device/tab switching loses mapping state contrary to the verified design.
  • Fail if launch/runtime uses a different mapping from the selection, Continue bypasses validation, or a flight binding invokes restart.
  • Fail if immediate camera selection gains a redundant confirmation step or existing gear/flaps and editable controls are removed.

Excluded scope

  • Registration and planning only; no implementation, Focus admission, Architecture allocation, deployment, UAT acceptance or release approval is granted.
  • No new Feature, physics or asset redesign; do not reopen or rewrite historical Tasks.

Verification steps

  • Pending before implementation: UI/UX must retrieve the exact frames and revision from AEROSIM-UIUX-REL-1.0.0 (recorded baseline revision 6608), compare later approved changes, and verify the interactive mapping/device-switch semantics; current design parity has not been independently verified by this registration.
  • Inherited prerequisite TASK-0096 follows the existing parent Feature dependency on AEROSIM-FT-3; correction-specific sequencing remains for Architecture review.
  • Pending Architecture readiness: verify this correction's derivation, cross-Feature launch/camera interfaces, dependencies, requirements, release allocation and implementation gate before Focus admission. Scope registration is not a readiness verdict.
  • Delivery adds RED/GREEN unit tests for tab progression, device-specific mapping retention, Assign/Reset count, launch validation and the exact binding snapshot consumed by runtime; run required static/build checks.
  • UAT verifies ordinary keyboard/pointer/device interactions across every tab, Back to Flight Setup, Continue and Start Flight on an exact deployed candidate; prove declared controls operate their corresponding runtime commands without restart collisions.
  • UAT compares stable shared geometry and mapping presentation with verified design at supported viewports; no hidden-input, forced-click or direct state mutation substitutes.

Traceability

Requirements

Dependencies

Acceptance evidence

Required future evidence: UI/UX revision verification, complete interaction/design checks and independent candidate-bound UAT. This is an owner-requested corrective backlog registration based on bounded source evidence, not an implementation or acceptance finding.

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.

Planning boundary​

Release 2.0.0 planning board inclusion records the Scope owner's backlog request, not Architecture allocation, Focus admission, implementation approval or release acceptance. UI/UX revision verification and Architecture readiness remain pending. Requirement links identify existing corrective context, not a new approved solution package.

Corrective provenance​

Historical Task states and evidence remain unchanged: