Fix UI polish and stale app state - #7
Merged
Conversation
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
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.
What changed
Why
The previous UI had several small alignment and typography defects. More importantly, Streamlit cache entries were keyed only by the database path, so replacing a SQLite database at the same path could leave stale summary and search state visible until cache expiry or restart. Prepared CSV state was also transient.
Data integrity
No SQLite database or database query module was changed. K values, Reference data, filtering semantics, deduplication behavior, and source provenance remain unchanged. Core record counts and SHA-256 checks were revalidated before publication.
Validation