You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: classify HTTP 202/5xx as indeterminate in http-status-codes (#79)
Vercel/Next.js ISR returns 202 Accepted during cache-miss/build for
fresh URLs. The previous classifier treated any non-4xx as evidence of
soft-404, so afdocs's intentional fan-out of 155+ unique nonexistent
URLs would trip ISR and produce false-positive failures that real
agents (low concurrency, warm cache) never see.
5xx responses tell us nothing about how the site handles bad URLs,
either; they were silently passing as "correct-error" before.
Both now route to a new `indeterminate` classification that's excluded
from the soft-404 tally and reported separately. When the entire sample
is indeterminate, the check returns `warn` and falls back to the default
0.5 warn coefficient rather than penalizing the site for CDN behavior
it can't measure.
Verified against plaid.com/docs at concurrency 30: one run returned 281
correct-error / 19 indeterminate, another 16 / 284 — both correctly
pass instead of flunking the site for ISR build behavior.
|**0.25**| Actively steering agents to a worse path |`llms-txt-links-markdown` (markdown exists but llms.txt links to HTML; agents don't discover .md variants on their own) |
152
152
153
-
Checks that only have pass/fail (no warn state):`http-status-codes`, `markdown-code-fence-validity`.
153
+
`markdown-code-fence-validity`only has pass/fail (no warn state).`http-status-codes` is normally pass/fail but warns when every sampled response is indeterminate (HTTP 202 from CDN cache-miss/build, or 5xx) so the check couldn't measure bad-URL handling.
|**0.25**| Actively steering agents to a worse path |`llms-txt-links-markdown` (markdown exists but llms.txt links to HTML) |
143
143
144
-
Two checks have no warn state and are strictly pass/fail:`http-status-codes`and `markdown-code-fence-validity`.
144
+
`markdown-code-fence-validity` is strictly pass/fail.`http-status-codes`is normally pass/fail but emits a warn when every sampled response is indeterminate (HTTP 202 during CDN cache-miss/build, or 5xx) so we couldn't measure bad-URL handling.
0 commit comments