Skip to main content

AEROSIM-TS-71

Project task

Restore recorded activity context with explicit fallback reasons

Selecting Resume reconstructs the recorded governed context for the active pilot or explains a stable reason that continuation is no longer available.

AEROSIM-TS-71Canonical ID TASK-0071
Verified flow state
Done
Owner
AeroSim Architecture and Delivery
Component
Web Application and API Service — Flight shell, Progress service, and Persistence API client
Repository
corp-v1-aerosim/corp-v1-aerosim

Delivery scope

Implement typed resume-context retrieval and route handoff, revalidate the context immediately before launch, restore the recorded flight or training configuration and canonical progress, and map deleted resources, unsupported versions, completed activity, authorization denial, and transient retrieval failure to explicit non-destructive outcomes. Concrete artifacts are applications/api/src/progress/resume-context.ts and applications/api/src/progress/resume-context.test.ts; ownership is limited to the listed artifacts and their focused verification.

Implementation contract

Implementation artifacts

  • applications/api/src/progress/resume-context.ts
  • applications/api/src/progress/resume-context.test.ts

Inputs

  • Authenticated pilot and selected resume-context identifier from the Home projection
  • Fresh canonical activity record, selected flight or training configuration, and persisted progress
  • Current governed-resource catalogue and supported payload-version registry

Outputs

  • Selecting Resume reconstructs the recorded governed context for the active pilot or explains a stable reason that continuation is no longer available.

Failure boundaries

  • Do not launch when revalidation finds completed activity, deleted resources, unsupported version, missing context, or pilot mismatch
  • Map authorization denial and transient retrieval failure to distinct non-destructive results without modifying canonical progress

Excluded scope

  • Silently substituting a default activity or newer configuration when recorded context is unavailable
  • Migrating unsupported saved-state versions as part of the resume request

Verification steps

  • Run applications/api/src/progress/resume-context.test.ts against the exact implementation revision and retain the complete passing result.
  • Exercise the positive contract with authenticated pilot and selected resume-context identifier from the home projection, then assert: Selecting Resume reconstructs the recorded governed context for the active pilot or explains a stable reason that continuation is no longer available.
  • Exercise every negative boundary: Do not launch when revalidation finds completed activity, deleted resources, unsupported version, missing context, or pilot mismatch; Map authorization denial and transient retrieval failure to distinct non-destructive results without modifying canonical progress

Traceability

Requirements

Dependencies

UI/UX applicability

non_visual

This Task owns technical or behavioral acceptance and does not claim direct visual conformance to the approved UI/UX package.

Acceptance evidence

Verified delivery: application PR #135 reviewed head d82b0dd91ffd7fd178ce2d5fe5537636f6b268f9 merged as 7a85e7894f4a85bd79bf1f28fcad756f284640f6. Resume-context service performs two authoritative reads, launches only the fresh pilot-owned supported context, restores exact configuration and progress, and returns stable non-destructive reasons for missing, mismatched, completed, aborted, deleted, unsupported, unauthorized, and transient cases. Focused tests: 9 passed; API suite: 141 passed. Exact-head and post-merge CI runs 4329, 4330, 4331, 4332 passed. 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.