Repository navigation
Order current evidence by UTC while retaining historical review replay - #6
Merged
Merged
Conversation
dev-belly
changed the title
dev-belly
marked this pull request as ready for review
October 24, 2026 05:50
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.
Raw ISO timestamp strings can order later deployments before earlier approvals when offsets or fractional seconds differ. Order the current timeline by parsed UTC instants while keeping source strings unchanged; omit unparseable display entries without changing the linked source record.
Complete this draft against current main as version 0.2.10 / bundle format 5. Formats 2–4 reconstruct their original lexical timeline before checking historical review fingerprints, explicitly returning
legacy_timeline_order=trueand a CLI notice. New bundles use UTC chronology. A corrected representation cannot automatically inherit an old-order closed review.Validation: all 113 tests pass, including the two original mixed-offset/fractional cases and three display/legacy-binding regressions. Ruff, diff and offline lockfile checks pass. A retained actual 0.2.9 export replays under the legacy policy. Re-running its real test database returns the current review to pending, exports format 5 and replays successfully; all 28 source JSON/CSV files and the dataset fingerprint remain byte-identical between old/new bundles. The existing 0.2.8 fixture also replays. Every uploaded file matches its local Git blob hash.