Repository navigation
Release timestamp-safe PITBridge 0.2.1 with installed boundary checks - #29
Merged
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.
The v0.2.0 wheel can truncate a seventh fractional timestamp digit, moving an ingestion instant just after a decision onto the cutoff and selecting a record that was not yet available. The source already rejects that input; publish it in a checked 0.2.1 wheel and explain how to handle earlier normalized evidence.
Extend the installed-wheel gate to check exact-cutoff and one-microsecond-late scalar/rolling selections, and reject excess precision through both JSON and CSV for both commands before creating output. Release-asset preparation requires the new boundary evidence. Preserve existing bundle format markers and the v0.2.0 release.
Validation: 146 local tests pass; both committed scalar and rolling reports replay. A clean 0.2.1 wheel installation outside the source tree passes all four precision-rejection routes, normal JSON/CSV replay and the independent benchmark. Reproduced the incorrect selection with the publicly downloaded 0.2.0 wheel. Local documentation links and source-build checks pass. Cross-platform, pandas and browser CI must pass before merge.