Scan every readable packed claim surface

[karlwaldman]

Summary

• scan every valid UTF-8 customer-readable file in the exact packed dist tree, independent of suffix
• keep binary package data outside text parsing without treating a valid Unicode replacement character as binary
• release the hardened contract as 1.2.6

Red-green proof

• RED: focused storefront suite failed 5 new cases: .txt, .md, .map, extensionless, and adjacent-readable/binary coverage (11 existing passed)
• RED follow-up: valid UTF-8 containing U+FFFD was incorrectly skipped (1 failure / 16 pass)
• GREEN: focused 22/22; full 505 passed / 1 skipped
• npm run lint
• npm audit --audit-level=low (0 vulnerabilities)
• npm run check:secrets
• npm run storefront:check (36 authored surfaces)
• npm run snippets:check (6 fixtures + 4 manifest tests)
• npm run build
• npm run smoke:package (exact packed claims + ESM/CJS clean install)
• git diff --check and validator syntax check

Release

After protected-main merge, publish only through the existing governed v1.2.6 GitHub release workflow, then verify exact npm integrity/provenance and clean ESM/CJS customer smokes.

[coderabbitai]

Warning

Review limit reached

@karlwaldman, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 18 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: de08ae19-d090-4567-b10a-6f4d20d6565a

📥 Commits

Reviewing files that changed from the base of the PR and between eba4414 and fc35ee0.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (6)

• CHANGELOG.md
• package.json
• scripts/validate-storefront-claims.mjs
• src/version.ts
• tests/release-readiness.test.ts
• tests/storefront-claims.test.ts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}