perf: prune generated navigation

[claudiacodacy]

Summary

• enable Material navigation pruning to reduce generated document size

Validation

Note: navigation pruning changes collapsed sidebar sections into links to their first/index page.

[gemini-code-assist]

Code Review

This pull request updates the mkdocs.yml configuration file to enable the navigation.prune feature under the theme settings. There are no review comments, and I have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

The PR enables the navigation.prune feature within the Material for MkDocs theme configuration to optimize documentation payload size. This change is intended to link collapsed sidebar sections directly to their index pages, reducing the overall size of the navigation tree. While the implementation is straightforward and Codacy results are up to standards, there is no provided evidence (e.g., build logs or size comparisons) to verify the expected performance gains. Additionally, there are no automated tests ensuring the configuration produces the intended navigation behavior.

About this PR

• The PR description's 'Validation' section is empty. Please provide evidence or metrics demonstrating the reduction in generated document size and confirmation that collapsed sidebar sections navigate correctly to their index pages.

Test suggestions

• Verify the navigation.prune feature is correctly added to the theme features in mkdocs.yml
• Compare the size of the generated site (HTML/JS) before and after the change to confirm performance improvement

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify the navigation.prune feature is correctly added to the theme features in mkdocs.yml
2. Compare the size of the generated site (HTML/JS) before and after the change to confirm performance improvement

Low confidence findings

• There are no automated checks or build-time tests included to verify the documentation configuration or to safeguard against regressions in navigation behavior resulting from pruning.

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}