[Paullo9]

Requested by Paul · project thread

No app or export should show "unvalidated" wording. Each reader note now gives the plain fact and names where in the file the value is stored.

Note	Old	New
TIFFVeloxCalibration.unvalidatedNote (= TIFFAppImage.Note.veloxUnvalidated)	scale unvalidated (one acquisition)	scale as Velox stores it (BinaryResult/PixelSize), not checked against a calibration standard
AcquisitionMetadata.unvalidatedNote (generic)	unvalidated: no published reader reads it	no published reader reads this field; read as the file stores it
DM reader	same	no published reader reads this field; read as stored in the DM image tags
Velox EMD reader	same	no published reader reads this field; read as stored in the Velox metadata
MRC reader (FEI record)	same	no published reader reads this field; read as stored in the FEI extended header, at the offset mrcfile declares
TIFF, Velox XML	same	no published reader reads this field; read as stored in the Velox XML of the TIFF
TIFF, FEI header	same	no published reader reads this field; read as stored in the FEI header of the TIFF
Velox detector	unvalidated: RosettaSciIO names some detectors from another field	read from BinaryResult.Detector; RosettaSciIO names some detectors from another field
MRC camera length	unvalidated: the mode is not checked	shown as stored; the instrument mode is not checked, as no published reader decodes it

Call sites that used the generic note now attach their own format's wording.

API. No symbol was removed or renamed, so consumers compile unchanged. There are three new aliases for the same strings: AcquisitionMetadata.noPublishedReaderNote, TIFFVeloxCalibration.storedScaleNote and TIFFAppImage.Note.veloxStoredScale.

Consumers display these notes verbatim. On update, their own snapshot or literal tests of these notes may need re-pinning.

Fixtures. The six pins files were re-recorded in their own commit. Only the note strings changed, plus the TIFF source line that contains the scale note. No number moved. tools/acq-metadata/generate.py now applies the same wording to the pinned app output, and a check of its mapping against the old pins reproduces the new files exactly.

Tests. The tests pin the new texts and check that the aliases equal the old names and that no note contains "unvalidated". Gate results are below.

• tools/test.sh --skip FormatoKitParityTests: green; 444 tests and no build warnings.
• Parity target (--filter FormatoKitParityTests): green; 18 tests, 5 skipped because owner data is absent.
• SwiftLint --strict and SwiftFormat --lint (repo configs): clean.
• tools/fixture-index/index.py --check: current.
• A reviewer read the diff before commit: the note wording matches each call site, no public symbol was removed, and only note text changed in the fixtures.

docs/parity.md still describes these fields as labelled "unvalidated" in prose. It is left for a follow-up because two open PRs already edit that file.

🤖 Generated with Claude Code