mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-08 12:32:43 +00:00
A lab note or a biomarker context written under a key this instance no longer holds came out of a portable export as `null` — byte-identical to a column that was never written. The restore importer then wrote nothing, so the text was gone and nothing said it had ever been there. The whole loss fit inside a fail-soft `catch` written for a list view, where returning null is the right answer. Both now export a short marker naming what happened, and the marker survives a restore. The Coach transcript already did this with a placeholder sentence and the doctor report with a rendered flag; the marker is now one constant the transcript shares, and its comment says why an empty string will not do. The unit test that required `note: null` here pinned the loss. It keeps the half that matters — one bad row must never abort the export — and asserts the marker instead. The round trip is proven end to end against a real restore.