Skip to main content

AEROSIM-TS-149

Project task

Make the camera-selection page professional and design-conformant

A player sees and operates one polished, design-conformant camera-selection body that makes all four initial-camera choices equally clear and preserves the selected camera through launch.

AEROSIM-TS-149Canonical ID TASK-0149
Verified flow state
Done
Owner
AeroSim UI/UX, Architecture and Delivery
Component
Web Application — Screen 07 pre-flight Camera body
Repository
corp-v1-aerosim/corp-v1-aerosim

Delivery scope

Conform the existing camera-selection page to the approved Release 1.0.0 Screen 07 pre-flight Camera body without inventing a new design. Deliver one seamless full-width body with stable shared header and tab geometry, sharp rectangular New York/zinc styling, strong hierarchy, equal professional Chase, Cockpit, Orbit, and Fly-by cards, visible imagery or camera cues, complete-card hit targets, and immediate selected-state feedback.

Implementation contract

Implementation artifacts

  • corp-v1-aerosim/corp-v1-aerosim:applications/web/src/preflight/camera/InitialCameraSelector.tsx
  • corp-v1-aerosim/corp-v1-aerosim:applications/web/src/preflight/PreflightBriefingScreen.tsx
  • corp-v1-aerosim/corp-v1-aerosim:applications/web/src/styles.css
  • corp-v1-aerosim/corp-v1-aerosim:applications/web/test/preflight/initial-camera-selector.spec.tsx
  • corp-v1-aerosim/corp-v1-aerosim:applications/web/e2e/release-camera-selection.browser.spec.ts

Inputs

  • RootAtSkic directed this exact professional camera-selection correction and Wave 33 Delivery handoff in Discord message 1549867630800666695, acting as backup UI/UX and Kanban owner.
  • Approved design package AEROSIM-UIUX-REL-1.0.0, Penpot file fb1055b2-4705-80bf-8008-8b539372c9fb, page 1c28ff56-144d-45d1-ae7b-785638b2432c, revision 6608.
  • UIUX-100-PREFLIGHT governs the exact Screen 07 pre-flight Camera body evidence, including frame IDs 0373493e-5289-49a8-9aa0-b780699c5177 and 26d55dec-15e6-4e54-9c03-5739ff457915.
  • TASK-0147 provides the completed ordinary full-card selection and launch-continuity baseline that this Task must preserve.

Outputs

  • One seamless, aligned, full-width camera-selection body with sharp rectangular New York/zinc styling and a strong professional information hierarchy.
  • Four equal camera cards for Chase, Cockpit, Orbit, and Fly-by, each with visible imagery or an unambiguous visual camera cue and the complete card as its hit target.
  • Selection immediately moves the active border and a visible SELECTED label to the chosen card while the shared header and tab geometry remain unchanged.
  • Responsive rendered evidence at every supported viewport and an ordinary-interaction screenshot comparison with the approved Penpot revision 6608 baseline.

Failure boundaries

  • Fail when the camera experience is split into disconnected panels or cards, leaves unused or misaligned width, changes shared header or tab geometry, or departs from sharp rectangular New York/zinc styling.
  • Fail when Chase, Cockpit, Orbit, and Fly-by do not have equal professional card treatment, visible imagery or cues, and complete-card pointer hit targets.
  • Fail when selection does not immediately move both the active border and visible SELECTED label, or when acceptance relies on force-click, hidden-input manipulation, direct DOM/state mutation, or API bypass.
  • Fail when placeholder, prototype, debug, developer-looking, or implementation-note text is visible in the ordinary experience.
  • Fail when any supported viewport clips, overflows, horizontally scrolls, overlaps, or collapses the intended hierarchy.
  • Fail when ordinary interaction screenshots materially diverge from the approved UIUX-100-PREFLIGHT Penpot evidence without an approved exception.
  • Fail when the confirmed camera no longer remains continuous into the first active-flight view.

Excluded scope

  • Do not create, revise, or substitute a Penpot design; use only the approved AEROSIM-UIUX-REL-1.0.0 revision 6608 evidence.
  • Do not add new camera modes, change the canonical camera value or launch-state contract, or redesign unrelated Input, Flight, HUD, world, aircraft, or release surfaces.

Verification steps

  • Load penpot-design-operations and use only penpot-zcube-v1 to read the immutable AeroSim team, project, file, page, revision 6608, and UIUX-100-PREFLIGHT Screen 07 evidence before coding; stop if the approved baseline cannot be retrieved, is superseded, or is ambiguous.
  • At every supported viewport, render the complete page and verify one seamless aligned full-width body, sharp rectangular New York/zinc styling, strong hierarchy, stable shared header/tab geometry, and no clipping, overlap, horizontal scroll, or overflow.
  • Select Chase, Cockpit, Orbit, and Fly-by through ordinary clicks anywhere on each complete visible card; verify equal card geometry, visible imagery or cues, canonical selected value, immediate active border, and immediate visible SELECTED label.
  • Verify no placeholder, prototype, debug, developer-looking, or implementation-note text is visible.
  • Capture ordinary-interaction screenshots for the camera body and every selected state and compare them with the approved UIUX-100-PREFLIGHT Penpot revision 6608 evidence at the required viewports.
  • Continue through the ordinary launch path and prove the confirmed camera remains the first active-flight view with no regression to launch continuity.

Traceability

Requirements

Dependencies

Acceptance evidence

Verified delivery: application PR #206 reviewed head 0eb7fe5cf363e09b400e24c2f8ca7b7e3fd3554f merged as e995856b46a0fd9c109867b8d97f6e73a41b2a41; candidate CI run 5204, integration validation run 5206, and immutable image publication run 5205 passed. The approved AEROSIM-UIUX-REL-1.0.0 revision 6608 and UIUX-100-PREFLIGHT source identity governed implementation. Release design conformance passed 36 screenshots with zero deviations; 12 ordinary selected-state screenshots passed at desktop, tablet, and mobile. Every complete card moved the cyan active border and visible SELECTED state immediately, responsive geometry remained stable without horizontal overflow or developer copy, and the confirmed Orbit camera remained the first active-flight view.

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.