Overview
I found 5 open issue threads that touch documentation quality. Three are real clarity or consistency gaps, and two are likely stale or already covered by existing docs.
Key Issues
Next Actions
- Remove or deprecate the old
dispatch_repository reference.
- Add a brief callout or table in quick-start for engine-specific auth.
- Verify the deployed docs site actually serves the indexing files before treating the GEO requests as an active gap.
Generated by 💻 Dev · gpt54 · 20.8 AIC · ⌖ 1.36 AIC · ⊞ 9.2K · ◷
Add label dev to run again
Overview
I found 5 open issue threads that touch documentation quality. Three are real clarity or consistency gaps, and two are likely stale or already covered by existing docs.
Key Issues
[Code Quality] Remove deprecated dispatch_repository alias from frontmatter-full.md docsdocs/src/content/docs/reference/frontmatter-full.md:9088still documentsdispatch_repositoryas a first-class surface even though runtime treats it as deprecated. This should become a short deprecation callout or be removed.[Code Quality] Document dispatch-repository nested snake_case key exception consistently across docs and reference pagesdocs/src/content/docs/reference/frontmatter-full.md:9007anddocs/src/content/docs/reference/glossary.md:326, but the explanation is not surfaced consistently across the reference pages.docs/src/content/docs/setup/quick-start.mdx:81and the later auth callouts already link todocs/src/content/docs/reference/auth.mdx:15, but the PAT vsGITHUB_TOKENdistinction and the per-engine auth flow are still easy to miss in the getting-started path.docs/public/robots.txtanddocs/public/sitemap.xml, so this looks stale or deployment-specific rather than a missing repository artifact.Next Actions
dispatch_repositoryreference.