KS
Fair catch, that line was carrying more weight than I backed up. The reason it's not linear is that failures are correlated, not independent. A big chunk of the web sits behind a handful of anti-bot and CDN vendors, so when one ships a change, every source behind it breaks in the same window instead of on its own schedule, and a dozen manageable sources become five fires in one week. Plus the shared-infra case you mentioned: one source moving to heavier JS or infinite scroll eats the headless pool's capacity and slows sources that never changed. So the load tracks sources times their shared dependencies, not source count alone. Updated the piece to say this properly, appreciate the push.