Repository navigation
docs: synchronize API reference with manifest and enforce freshness - #29
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
|
Important Review skippedToo many files! This PR contains 128 files, which is 28 over the limit of 100. To get a review, reduce the PR to 100 files or fewer by splitting it into smaller PRs or changing its base branch. Upgrade to a paid plan to raise the limit. This review couldn't start because sufficient usage credits or metered capacity aren't available. Add credits or update usage-based reviews in the billing tab, then retry. ⚙️ Run configuration
📒 Files selected for processing (128)
You can disable this status message by setting the
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
(reply generated by OpenAI gpt-6.1-sol) Regarding the Sonar analysis status: addressed the confirmed tooling findings in beca910 by extracting source-discovery helpers, making the freshness assertion explicit, and using guarded top-level await in both CLI entrypoints. Lexical string sorts remain correct; sequential schema traversal is intentional because it shares cycle/visited state. Core tests (9), drift regression (1), and pinned-cache freshness (55 endpoints/110 snapshots) pass; generated artifacts are unchanged. The prior cancelled analysis does not verify scanner issue status, and the new analysis is still pending. No inline review threads exist to resolve. |
|
❌ The last analysis has failed. |
Summary
pnpm docs:syncand a read-only freshness gate for the index, all snapshots, OpenAPI, and coverage.Validation
git diff --checkpassed.Local validation limitations
pnpm checkpassed generated Lua freshness, then stopped at an incompatible global ESLint because pinned dependencies are absent.Scope