Skip to main content

AEROSIM-TS-64

Project task

Verify preference durability, validation, and isolation

Reviewed evidence demonstrates active-pilot association, later-session restoration of the last valid supported value, rejection of invalid values, and zero cross-pilot preference disclosure or mutation.

AEROSIM-TS-64Canonical ID TASK-0064
Verified flow state
Done
Owner
AeroSim Architecture and Delivery
Component
Pilot Data Store, API Service, and Web Application — preference test suites
Repository
corp-v1-aerosim/corp-v1-aerosim

Delivery scope

Add schema, API, integration, and browser tests for create and update, last-write restoration, logout and later login, malformed and unsupported values, transaction failure, two-pilot isolation, subject-substitution attempts, and persisted-data integrity. Concrete artifacts are prisma/schema.prisma and tests/integration/verify-preference-durability-validation-and-isolation.spec.ts; ownership is limited to the listed artifacts and their focused verification.

Implementation contract

Implementation artifacts

  • prisma/schema.prisma
  • prisma/migrations/verify-preference-durability-validation-and-isolation/migration.sql
  • tests/integration/verify-preference-durability-validation-and-isolation.spec.ts

Inputs

  • Two isolated pilot fixtures, supported and unsupported key/value cases, and repeated updates
  • Database failure injection around preference transactions
  • Browser sequence covering save, logout, new session, and restoration

Outputs

  • Reviewed evidence demonstrates active-pilot association, later-session restoration of the last valid supported value, rejection of invalid values, and zero cross-pilot preference disclosure or mutation.

Failure boundaries

  • Fail if an invalid update changes the last valid persisted value or a transaction leaves a partial preference write
  • Fail on cross-pilot read or mutation, caller-supplied subject substitution, or restoration of anything other than the final valid value

Excluded scope

  • Performance benchmarking of the complete settings interface
  • Evidence for settings not present in the supported preference contract

Verification steps

  • Run tests/integration/verify-preference-durability-validation-and-isolation.spec.ts against the exact implementation revision and retain the complete passing result.
  • Exercise the positive contract with two isolated pilot fixtures, supported and unsupported key/value cases, and repeated updates, then assert: Reviewed evidence demonstrates active-pilot association, later-session restoration of the last valid supported value, rejection of invalid values, and zero cross-pilot preference disclosure or mutation.
  • Exercise every negative boundary: Fail if an invalid update changes the last valid persisted value or a transaction leaves a partial preference write; Fail on cross-pilot read or mutation, caller-supplied subject substitution, or restoration of anything other than the final valid value

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 #121 merged reviewed head acd5e3ab56c2995945ac6859e8dce25227e6cbff as 2fde37bb128f444eb837cbfe08ea39f62f6040af; five focused real-PostgreSQL tests prove migration invariants, repeated last-write restoration across later sessions, malformed and unsupported value rejection, transaction rollback, and two-pilot isolation with subject-substitution resistance; shipped browser preference tests prove logout state clearing, later-session restoration, and stale-result rejection; full local validation, 120 world-interaction runs, production audit, exact-head CI run 4193, integration/publication run 4194, and integration validation run 4195 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.