fix(data): preserve provenance and missing-data semantics - #57
Merged
Conversation
bearmug
force-pushed
the
fix/data-provenance
branch
from
August 16, 2026 18:53
f1adba5 to
ac0dfb7
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary\n- add provenance metadata to screening, lookup, search, metainfo, and TA responses\n- preserve source retrieval timestamps across cache hits\n- expose raw versus returned counts and explicit missing/unavailable TA symbols\n- keep missing data distinct from neutral technical scores\n\n## Verification\n- npm test — 242 passed on the data-quality stack\n- npm run build