Skip to main content

AEROSIM-TS-171

Project task

Remove redundant camera confirmation step

A player selects an available initial camera in one action and can launch as soon as the remaining required pre-flight selections are valid.

AEROSIM-TS-171Canonical ID TASK-0171
Verified flow state
To Be Released
Owner
AeroSim Architecture and Delivery
Component
Pre-flight initial-camera selection
Repository
corp-v1-aerosim/corp-v1-aerosim

Delivery scope

Remove the provisional-versus-confirmed camera state and CONFIRM CAMERA control from the pre-flight camera selector. Validate the current camera registry snapshot at card selection time, immediately replace the selected initial camera in the pre-flight configuration, and preserve stale-registry fail-closed behavior, keyboard card selection, availability rules, ARIA-selected state, and launch locking and idempotency.

Implementation contract

Implementation artifacts

  • applications/web/src/preflight/InitialCameraSelector.tsx
  • applications/web/src/preflight/InitialCameraSelector.test.tsx
  • applications/web/src/preflight/PreflightBriefingScreen.test.tsx

Inputs

  • RootAtSkic approved the exact one-click camera-selection correction in Discord message 1553483369436811286.
  • Historical TASK-0136 remains immutable evidence for the superseded confirmation interaction and is not reused or rewritten.

Outputs

  • Selecting Chase, Cockpit, Orbit, or Fly-by immediately selects that available camera and updates the launch configuration.
  • LAUNCH FLIGHT becomes available without a second camera-confirmation action when every other required pre-flight selection is valid.
  • No CONFIRM CAMERA control or select-then-confirm instruction remains.

Failure boundaries

  • Fail when a stale registry snapshot can select or launch an unavailable camera.
  • Fail when keyboard card selection, ARIA-selected state, camera availability, launch locking, or idempotency regresses.
  • Fail when a later selection does not immediately replace the previous initial camera.

Excluded scope

  • Delivery does not execute browser, E2E, screenshot, visual, or runtime UX acceptance for this correction.
  • This Task does not rewrite historical TASK-0136 or change production desired state.

Verification steps

  • Run focused unit/component tests for one-click selection, immediate launch enablement, selection replacement, stale registry, keyboard operation, and absence of the confirmation control.
  • Require complete local validation, exact-head review and CI, trusted post-merge publication, reviewed cumulative development GitOps, and immutable runtime identity and health readback.
  • Hand the frozen development tuple to UAT and retain RootAtSkic as owner of actual UX verification.

Traceability

Requirements

Dependencies

Acceptance evidence

Verified delivery: application PR #287 merged after strict RED/GREEN unit/component TDD and exact-head review/CI; integration/publication run 6082 passed all five jobs for integration revision 2d0ac85c9e47f297d220199093e39ad589acc0ed; Harbor readback matched the immutable Nebula, Singularity, and Helm chart artifacts; template PR #45 and development GitOps PR #25 merged after review and validation; GitOps run 6120 passed; development Argo CD applications were Synced/Healthy, pods were Ready on the expected immutable image IDs, and bounded Web/API health checks returned HTTP 200. Delivery ran no non-unit or runtime UX acceptance; RootAtSkic owns actual UX verification.

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.