AFDocs fixes: refresh known-exceptions allowlist for page-size and parity#319
AFDocs fixes: refresh known-exceptions allowlist for page-size and parity#319rachaelrenk wants to merge 2 commits into
Conversation
…rity The AFDocs audit (score 74/100, C) surfaced page-size-markdown and page-size-html hard-fails driven by intentionally-long pages (open-source-licenses auto-generated licenses, current-year changelog, privacy legal text), plus a single-page markdown-content-parity fail (Turndown escaping false positive). All automatable remediations (llms.txt directive, .md URLs, content-negotiation middleware, mcp.json, 100% coverage) are already in place; the remaining failures are allowlisted platform limits or editorial page-size decisions the afdocs-fix skill explicitly does not auto-fix. Updates the stale known-exceptions.md so future audits classify these correctly. Co-Authored-By: Oz <oz-agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
![oz-for-oss[bot]](https://avatars.githubusercontent.com/in/3450139?s=60&v=4){kind=small}
There was a problem hiding this comment.
Overview
This PR refreshes the AFDocs known-exceptions reference to match current audit behavior for markdown-content parity and intentionally long page-size exceptions. It only updates internal review guidance for the AFDocs audit skill; it does not change published documentation content, site behavior, code, or configuration.
Concerns
- No blocking concerns found.
- No approved or repository spec context was available for implementation drift validation.
Verdict
Found: 0 critical, 0 important, 0 suggestions
Approve
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
1 participant
Summary
Ran the AFDocs audit against
docs.warp.dev. Score: 74/100 (C) — 23 checks, 15 pass, 5 fail, 1 warn, 2 skip.All automatable AFDocs remediations are already in place:
src/middleware.ts(content negotiation), thellms-directiveinCustomHeader.astro, the directive inapi.astro,public/.well-known/mcp.json, 100%.mdURL support, and 100% llms.txt coverage. There were no new code remediations to apply.The remaining failures/warning are all either allowlisted false positives / platform limits, or editorial page-size decisions the
afdocs-fixskill explicitly does not auto-fix:openapi.yaml/openapi.jsonfalse positive./changelog/2026/(current-year changelog, grows until year-end)./support-and-community/community/open-source-licenses/(auto-generated) + other long reference pages.Change
The only genuinely stale artifact was
known-exceptions.md, which still described page-size as passing/borderline. Content growth now pushes several intentionally-long pages past the AFDocs 100K hard-fail threshold. This PR updates the allowlist so future audits classify them correctly:open-source-licenses(~1.37M chars, auto-generated byrelease_updates)changelog/2026(~113–130K, current-year, split by year already)privacy(~113K, legal)markdown-content-paritycan surface as a single-page failNo documentation content or site behavior changes.
Conversation: https://app.warp.dev/conversation/957cd3eb-debe-4e1f-8b91-9ae26f56fa6a
Run: https://oz.warp.dev/runs/019f4b0a-8ec5-7248-b604-f3eec782433d
This PR was generated with Oz.