Feat/openapi docs#4185
Merged
Merged
Conversation
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (5 files)
Previous Review Summaries (4 snapshots, latest commit 6ac7944)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 6ac7944)Status: No Issues Found | Recommendation: Merge Files Reviewed (4 files)
Previous review (commit 2c9e71c)Status: 1 Issue Found | Recommendation: Address before merge Fix these issues in Kilo Cloud Overview
Issue Details (click to expand)WARNING
Files Reviewed (5 files)
Previous review (commit 34b8b50)Status: 1 Issue Found | Recommendation: Address before merge Fix these issues in Kilo Cloud Overview
Issue Details (click to expand)WARNING
Files Reviewed (14 files)
Previous review (commit eb6be61)Status: No Issues Found | Recommendation: Merge Files Reviewed (13 files)
Reviewed by gpt-5.4-20260305 · Input: 85.5K · Output: 11.4K · Cached: 584.2K Review guidance: REVIEW.md from base branch |
St0rmz1
approved these changes
Jun 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Usage analytics did not have a reviewer-friendly public OpenAPI surface, which made the available tRPC endpoints and their intended roles harder to understand from generated docs.
This adds an allowlisted Swagger/OpenAPI docs surface for the usage analytics tRPC endpoints, including shared schemas, bearer auth metadata, static Swagger UI assets, and clearer endpoint descriptions that distinguish summary cards, trends, breakdown charts, and detailed table/export usage. The implementation follows the existing explicit registry/schema pattern so only intentionally documented procedures are exposed.
Lower-level notes
/api/openapi.jsonand Swagger UI at/api/docs.Verification
Visual Changes
Reviewer Notes
Focus areas: the allowlist boundary for documented tRPC procedures, CSP/static asset handling for Swagger UI, and whether the endpoint role descriptions are clear enough for API consumers.