chore(docs): regenerate api-reference via docgen (#1095 follow-up) - #1096
Merged
Conversation
The manual consolidate endpoint entry was placed in the wrong spot and used hand-written content; docgen now renders it from the API registry (including the #1088 related-tag).
🔍 Cora AI Code Review✅ No issues found. Code looks good! Review powered by cora-code · BYOK · MIT |
3 tasks
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
1 participant
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.
What
cargo run -p docgensodocs/api-reference.mdmatches the API registry.Why
#1095 added a hand-written
/room/consolidatesection; theAPI Docs FreshCI job correctly flagged the file as stale. docgen now renders the endpoint from the registry (correct ordering +#1088related-tag) instead of manual prose.Testing
cargo run -p docgenoutput committed verbatim (6+/9- vs develop)API Docs Freshjob will verify freshness in CI