Skip to main content

AEROSIM-TS-127

Project task

Verify the complete Release 1.0.0 journey against the approved Penpot baseline

One deterministic browser suite proves every in-scope Penpot screen, state, action, and destination is owned and implemented without design drift.

AEROSIM-TS-127Canonical ID TASK-0127
Verified flow state
Done
Owner
AeroSim UI/UX, Architecture and Delivery
Component
Web Application — Release 1.0.0 user journey
Repository
corp-v1-aerosim/corp-v1-aerosim

Delivery scope

Create a complete design-conformance suite for the 18 approved page-001 Presentation frames and their interaction-backed states, covering Overview and Entry through Debrief, shared components, navigation, validation, recovery, camera cycle, keyboard focus, viewport containment, and approved deviations.

Implementation contract

Implementation artifacts

  • applications/web/e2e/release-1.0.0-design-conformance.spec.ts
  • applications/web/test/fixtures/release-1.0.0-design-scenarios.ts

Inputs

  • All feature-level conformance outputs referenced by AEROSIM-UIUX-REL-1.0.0.
  • A clean production build, deterministic fixtures, approved viewport list, and frozen Penpot revision 6608.

Outputs

  • A frame-by-frame and interaction-by-interaction parity report tied to the exact application commit and Penpot baseline.
  • Complete screenshots, route results, focus results, console/network health, and approved-deviation inventory.

Failure boundaries

  • Fail on any unowned visible behavior, missing frame/state, dead destination, visual mismatch, console error, failed asset, inaccessible control, or unapproved deviation.
  • Fail when the canonical approved baseline differs from frozen revision 6608 without a superseding approved package; later editable Penpot HEAD movement alone does not replace the frozen baseline.

Excluded scope

  • The Release 2.0.0 overview frame and viewer-hidden experiments are excluded from product implementation.
  • This Task verifies the integrated journey and does not replace feature-level implementation ownership.

Verification steps

  • Run applications/web/e2e/release-1.0.0-design-conformance.spec.ts against a production build.
  • Traverse all in-scope frames and interaction states, compare approved screenshots, verify every destination, and retain the exact commit/revision report.

Traceability

Requirements

Dependencies

Acceptance evidence

Verified delivery: final application PR #178 merged reviewed head efa29dfca4b3aeae594e4de4cd699798aaf62b66 as integration cf94ed7ca6db91c36fbb262273476bd3db997fdc; candidate CI 4843, integration CI 4845, and immutable publication 4844 passed; Harbor readback confirmed Nebula and Singularity digests; Release 1.0.0 conformance passed 18 scenarios at two viewports with 36 screenshots and zero unapproved deviations against frozen Penpot revision 6608. Release completion verified on product 1.0.0.0 at GitOps revision 5d3712d89dfbf7dacd993348e55f497d126c7bf9 with Argo Synced/Healthy, exact image digests, authenticated API/database access, and three-world configured-flight acceptance.

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.