test: E2E ZK integration tests + frontend lifecycle test
Backend ZK integration tests (tests/zk_integration_tests.rs):
- medication_stored_as_ciphertext: register → create med with opaque blob →
response echoes blob, no plaintext fields leaked → GET echoes blob.
- appointment_stored_as_ciphertext_with_top_level_status: opaque blob + status
filter works server-side without decryption.
- health_stat_stored_as_ciphertext: opaque blob, no value/stat_type leaked.
- dose_schedule_adherence_reflects_missed_doses: 1×/day schedule → 30 scheduled,
1 taken, 29 missed, ~3.3% rate.
Updated medication_tests.rs for the opaque-blob contract (was sending old
plaintext name/dosage fields).
Frontend lifecycle test (useStore.test.ts):
- Full ZK round-trip with real WebCrypto: setup → encrypt → verify ciphertext →
unlock with password → decrypt → recover via phrase → rewrap under new
password → decrypt with new key. Data survives the full lifecycle.
Verified: backend 24 tests 0 warnings; frontend 25 tests, build clean.
34e3b0b0e0