Katia Belokon

Thanks, both points are fair. The counting script already prints a WARN for every plain rule that comes after the first splat or placeholder, but it only warns. Adding process.exit(1) on that line would turn it into a failed build, which is what you describe. On the SPA fallback: the curl check compares both the status code and the Location header, so a 200 without a redirect shows up as a FAIL, not a pass.

Thanks, Abhinav. No, I haven't, and that's the open gap in the post. The ~120 cutoff was on production, and the reproduction only ran locally in wrangler pages dev. So the post shows a mechanism that fits, not proof that production uses the same parser. A preview deploy of the same synthetic file would answer that, and if you or anyone else tries it, I'd be glad to hear the result.