chore: surface discovery asset byte drift warnings#76
Open
joshua-seeed wants to merge 1 commit into
Open
Conversation
- warn when production discovery assets only differ in raw bytes - report line-ending style alongside byte counts - document normalized parity vs literal-byte follow-up
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
pnpm verify:discovery:strictfinds normalized parity but raw-byte drift on production discovery assetsdocs/local-dev.mdanddocs/testing.mdWhy this matters
Nightly production verification was green on normalized parity, but the public discovery assets are still serving CRLF bytes while the repository stores LF. This change preserves the current non-breaking parity check while surfacing literal-byte drift that matters for deployment verification.
Test Plan
pnpm verify:discovery:strictpnpm verify:vitest-guardSecurity / Agent-Safety Notes