Repository navigation
chore: afdocs audit run log - #958
warp-factories[bot] wants to merge 2 commits into
Conversation
Co-Authored-By: Oz <oz-agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
@warp-factories[bot] 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 |
|
This PR was generated with Warp. Comment |
![warp-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 prepends the latest AFDocs audit run to .agents/logs/afdocs_audit_runs.md.
Concerns
- The new check summary is internally inconsistent:
28 totaldoes not match24 pass, 2 fail, 0 warn, so the run log cannot be used reliably as a regression baseline until the source counts are corrected.
Verdict
Found: 0 critical, 1 important, 0 suggestions
Request changes
Comment /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
| ## 2026-10-23 — valid | ||
| - **Spec**: v0.6.0 — native afdocs CLI score | ||
| - **Score**: 92/100 (A-) | ||
| - **Checks**: 28 total — 24 pass, 2 fail, 0 warn |
There was a problem hiding this comment.
24 pass, 2 fail, 0 warn accounts for 26 checks, not 28 total. Please correct the total or the breakdown to match the audit output.
Co-Authored-By: Oz <oz-agent@warp.dev>
warp-agent-staging
Bot
added
the
factory:docs-factory
Summary
Standing PR for the AFDocs audit run log (
.agents/logs/afdocs_audit_runs.md). Each scheduled run prepends an entry here.Latest entry
2026-10-23 — complete — 90/100 (A-), native v0.6.0; down from the earlier same-day 92 baseline due to one known parity warning, with no new failing IDs or repo-fixable findings.
Related issues
None.
Validation
Audit exited 0; log history preservation, log-only staging,
git diff --check, and remote commit SHA verified.No public-doc changes; docs build/typecheck suite and Trunk not run.
Follow-ups
Review the parity sample if investigating the score change; no automated remediation proposed.