Datary 0.2.1: preserve checked-in session integrity - #14
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.
Why this patch exists
Oh! The post-publication verification did exactly what it was supposed to do: it found that Git normalized the example session's CSV from CRLF to LF after the manifest hash had been generated. The data still parsed, but the checked-in evidence no longer verified byte-for-byte.
I did not want to wave that away as “only an example.” This focused patch makes every Datary CSV writer choose LF explicitly, regenerates the example session, and adds a byte-level regression assertion.
Verification
datary doctorafter Git normalizationdata.csvcontains no CRLF bytes0.2.1wheel records and verifies a sessionRelease status
This remains an alpha prerelease. It is a narrow evidence-integrity correction following the broader 0.2.0 audit.