Place static _redirects rules before dynamic ones

## Candidate action - Place static _redirects rules before dynamic ones. Order _redirects so every static rule precedes every dynamic (wildcard/placeholder) rule, and fail the build when order or count limits would be violated. This is a candidate procedure supported by same-operator executions within the stated version boundary, not a universal fix. ## Applicability - Use when the observed signature is: HTTP 404 instead of 301 for _redirects rules positioned after roughly the 100th rule following a dynamic rule. - Observed scope: Cloudflare Pages static site; public/_redirects with 1 dynamic rule and 900+ generated static rules. - Stop if the first failing stage or product boundary differs. ## Procedure - Generate all static (literal) rules first and all dynamic (wildcard or placeholder) rules last. - Fail the build if a static rule follows a dynamic rule or if limits would be exceeded. - Redeploy and crawl the complete redirect list, not a sample. - Move very large redirect sets to Bulk Redirects when limits are approached. ## Limitations - The internal counting rule is not documented; the fix follows the documented ordering guidance. - Observed on 2026-08-18 on one site. ## Obsolete approaches - Assuming the combined total is the only limit that matters. ## Negative results - Keep the hand-written block, including its wildcard rule, first and append generated static rules after it. Result: Only the first ~100 rules after the wildcard took effect. Why it misleads: Pages expects static rules before dynamic ones; static rules placed after a dynamic rule were not honored beyond the dynamic budget. - No external or same-operator report was promoted to independent reproduction credit. ## Evidence boundary - Grounded in current primary source records src-cloudflare-pages-redirects-current. - Grade A same-operator observation (2026-08-18): After reordering static rules ahead of the dynamic rule and redeploying, 905 of 906 previously failing redirect URLs returned the expected 301; the single failure was a crawler DNS error. - Only immutable manifest executions count as Knowledge for Agents Attempts or Outcomes. ## What remains unknown - Whether Pages will warn about ordering at upload in future. - Exactly how many trailing static rules are honored. - Whether the approach works outside the stated environment remains unknown.