Skip to main content

AEROSIM-TS-155

Project task

Make /flight a bounded runtime-only route

After launch, /flight mounts one route-specific runtime-only screen with no legacy setup/Foundation selectors or content and bounded supported-viewport document geometry.

AEROSIM-TS-155Canonical ID TASK-0155
Verified flow state
Done
Owner
AeroSim Architecture and Delivery
Component
Web Application — route-specific active-flight screen
Repository
corp-v1-aerosim/corp-v1-aerosim

Delivery scope

Separate setup composition from active-flight composition. Preserve the correct AppRouter behavior that already unmounts the previous route; change FlightDeckScreen so a launched /flight renders only governed runtime content. Remove legacy aircraft/world/condition/launch/Foundation content from the active-flight document and establish contained viewport/document geometry at every supported size.

Implementation contract

Implementation artifacts

  • corp-v1-aerosim/corp-v1-aerosim:applications/web/src/router.tsx
  • corp-v1-aerosim/corp-v1-aerosim:applications/web/src/App.tsx
  • corp-v1-aerosim/corp-v1-aerosim:applications/web/src/flight/views/ChaseFlightView.tsx
  • corp-v1-aerosim/corp-v1-aerosim:applications/web/src/flight/views/ChaseFlightView.css
  • corp-v1-aerosim/corp-v1-aerosim:applications/web/e2e/flight-route-composition.browser.spec.ts

Inputs

  • RootAtSkic authorized Wave 33 correction work in Discord message 1549867630800666695 and then asked the exact completeness question in message 1549881095363760179; this admission supplies the missing repair Tasks without modifying the separately claimed TASK-0149.
  • Deployed application source ab085692e2ed70bdb6525044b4ca91cc48a27478 for product 1.0.0.1; release 1.0.0.1 remains deployed, human acceptance FAILED, production REJECTED, and a replacement release is required.
  • Ordinary-user UAT evidence: /opt/data/corp-v1-aerosim-releases/workspace/uat-1.0.0.1-training-airfield-rerun/report.md and report.json (12/12 failed), /opt/data/corp-v1-aerosim-releases/workspace/uat-1.0.0.1-coastal-range/uat-report.md and uat-report.json (12/12 failed), and /opt/data/corp-v1-aerosim-releases/workspace/uat-1.0.0.1-mountain-valley/report.md and report.json (12/12 failed). All three runs prohibit forced clicks, hidden-input interaction, DOM/state mutation, direct API setup, or other bypass.
  • Diagnosed root-cause records: /opt/data/cache/delegation/subagent-summary-0-20260916_203916_911368.txt, /opt/data/cache/delegation/subagent-summary-1-20260916_203916_911707.txt, /opt/data/cache/delegation/subagent-summary-2-20260916_203916_911857.txt.
  • Root-cause summary 2 lines 7-23 proves the router correctly returns only the active route; FlightDeckScreen itself unconditionally composes Foundation-era header, selectors, launch controls, and runtime.
  • Mountain Valley UAT: 10/12 final captures were 1440×2313 or 1440×2377 rather than 1440×900; diagnosis measured a 2313 px document and trainer guidance explains the 2377 px variant.

Outputs

  • One /flight runtime composition after launch; setup remains on its governed setup/pre-flight routes and is absent from the /flight document.
  • Document and viewport geometry remain bounded at every supported viewport with no hidden lower setup/control document beneath a fixed canvas.

Failure boundaries

  • Fail when tests claim the router retains a previous route; the diagnosed router unmount behavior is correct.
  • Fail when /flight contains legacy aircraft, world, condition, Foundation, or launch selectors/content, or when body/document geometry overflows the supported viewport because runtime and setup are composed together.

Excluded scope

  • No application implementation is performed by this admission change.
  • Do not rewrite TASK-0149, infer a router-retention defect, report working Menu Restart as failed, classify static STALL SPEED 140 KT specification text as an active warning, or broaden governed interaction scope beyond the exact interaction semantics stated here.

Verification steps

  • Tests first: add failing route-exclusive DOM and geometry assertions for ordinary launch before changing composition.
  • From Home, complete ordinary setup and launch; assert exactly one main/runtime screen, absence of legacy setup/Foundation selectors/content on /flight, and bounded scrollWidth/scrollHeight at every supported viewport.
  • Use ordinary visible navigation and launch controls. No forced click, direct route injection, DOM removal, state seeding, API setup, or browser bypass is acceptance evidence.

Traceability

Requirements

Dependencies

Acceptance evidence

Verified delivery: application PR #213 reviewed head df6f11f2bf058520ed715e0f07436268e1e03d3f merged as 1ce3c755bb1d05bfe0619138c87432cf8be2c46c; integration validation run 5278 and immutable image publication run 5277 passed. Ordinary Home to Setup to Pre-flight to Launch browser acceptance proved that /flight contains only the governed runtime, omits legacy setup and Foundation content, retains the governed runtime title and recovery controls, and keeps body/document geometry bounded at 1440x900 and 1280x720 without forced clicks, route injection, DOM mutation, state seeding, or direct API setup. Harbor digest readback passed for both published images.

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.