Skip to content

chore: surface discovery asset byte drift warnings#76

Open
joshua-seeed wants to merge 1 commit into
masterfrom
joshua/nightly-20260615-discovery-byte-drift
Open

chore: surface discovery asset byte drift warnings#76
joshua-seeed wants to merge 1 commit into
masterfrom
joshua/nightly-20260615-discovery-byte-drift

Conversation

@joshua-seeed

@joshua-seeed joshua-seeed commented Jun 15, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • warn when pnpm verify:discovery:strict finds normalized parity but raw-byte drift on production discovery assets
  • report local/public byte counts plus line-ending style so operators can tell when a deployment differs only by CRLF vs LF
  • document the normalized-parity behavior in docs/local-dev.md and docs/testing.md

Why 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:strict
  • pnpm verify:vitest-guard

Security / Agent-Safety Notes

  • no runtime API or payment-path behavior changed
  • no secrets, auth flows, or production settings changed
  • external/public content is only compared and reported, not trusted as instructions

- 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
@vercel

vercel Bot commented Jun 15, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
commerce-backend Ready Ready Preview, Comment Jun 15, 2026 4:19am
commercebackend Ready Ready Preview, Comment Jun 15, 2026 4:19am

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant