fix(supply): harden shard budget guard - #7596
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
koala73
enabled auto-merge (squash)
September 3, 2026 15:55
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
1 participant
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
Supply shard publication now fails before cohort activation when the payload needs more than the runtime batch budget, while the caller records batch count and request size for operational headroom. The regression fixture now derives country, commodity, and canonical chokepoint dimensions from shared registries and proves that the payload exceeds the previous 15-request, 4 MiB-per-request capacity. Request sizes are captured after the write completes, so retry behavior cannot hide the assertion.
Type of change
Affected areas
Validation
npx tsx --test tests/supply-vulnerability-seeder.test.mjs— 24 passednpm run test:data— 29,745 passed, 37 skipped, 0 failednpm run typecheck— passednpm run typecheck:api— passednpm run lint— passed; existing unrelated warnings remainnpm run --silent lint:boundaries— passedPost-Deploy Monitoring & Validation
seed-bundle-static-ref-heavylogs for[SupplyVulnerability]batch telemetry.Fixes #7586.