Repository navigation
chore(docs): reconcile outstanding documentation and tooling work - #3
Merged
Merged
Conversation
Codoki trial endedThis workspace trial has ended, so Codoki paused AI code reviews for this pull request. Upgrade to Solo or Pro to keep catching risky changes before they reach production. 👉 Choose a plan to continue reviews. If this is an error, contact us at info@codoki.ai. |
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
Bring the outstanding local documentation revisions and tooling work into
main, preserving the already published documentation hub and upstream search-focus and Markdown-fence fixes. This includes the existing broad rewrite and condensation of technical articles and archived learning notes, revised indexes, maintenance records, and retained design assets (433 files versus the current base).Align the public AI environment example with the deployed public configuration boundary, fix the legacy asset-sync entrypoint and Docker paths/ownership, enable the full documentation validator in CI, and correct Java example class names. Fix the screenshot diagnostic so the Hub main content area is accepted alongside the older Material theme.
Replace the Slack webhook credential detected by GitHub push protection with an explicit placeholder. The release commit is based directly on the current
origin/main; the original local commits remain preserved locally. Its tree was verified identical to the reviewed, sanitized worktree.Validation
Limits
The checks validate the configured parser and source/build/browser contracts, not the factual accuracy of every technical article or every diagram in the browser. Live external AI responses and Docker service startup were not exercised. Two existing Compose sources (qbittorrent-advanced and droppy) remain marked as unavailable metadata by the build hook.