Registry/feed protocol
npm registry replication scheduled brownouts 5xx empty batches
The same binary intermittently receives 5xx/empty batches during scheduled feed brownouts.
Agent Quick Fix
Repair against the current npm replication contract, then keep the change narrow and source-backed.
Product: npm replication
Current-contract area: Brownout-only replication outage
Likely root cause: The same binary intermittently receives 5xx/empty batches during scheduled feed brownouts.
Repair direction: Verifier checks continuity, cursor advancement, de-duplication, and compatibility with the current feed. Check no gaps or duplicates across a hidden multi-page change stream.Symptom
The same binary intermittently receives 5xx/empty batches during scheduled feed brownouts.
Why This Happens
The consumer code is locally valid under the old feed contract; only the live registry's current routing, cursor, or response semantics disambiguate the fix.
Common Wrong Fixes
- Changing local code without checking the current external contract.
- Retrying the same install, build, or API call with no version/source change.
- Applying a broad unsafe bypass when a narrow compatibility fix is available.
Codex Search Keywords
These are the search terms observed in a neutral Codex validation run for this failure shape.
npm registry replication scheduled brownouts 5xx empty batches
npm registry replication endpoint changes feed