fix(search): allow scrolling through search results

[claudiacodacy]

Summary

• Fix the search dropdown so results with many matches (e.g. searching "code quality analysis" → 83 matching documents) can be scrolled through — previously only the first ~2.5 results were visible with no way to reach the rest.
• Root cause: .md-search__output had max-height: none, so the results list grew to fit all content instead of shrinking to the dialog's available height; the nested .md-search__scrollwrap's overflow-y: auto never had anything to actually overflow, so no scrollbar ever appeared and extra content was clipped by the outer dialog. It only worked by accident on very narrow phone viewports where a separate media query forced a bounded height.
• Fix bounds .md-search__output to the dialog's available space and lets it own the scroll directly.

Test plan

• mkdocs build succeeds with no new warnings
• Verified locally in browser: searched "code quality analysis" (83 matching documents, same as the reported bug), confirmed via DOM inspection that the results container is height-bounded with overflowing content, and that scrolling reveals additional results beyond the first few
• Spot-check on a real desktop browser and a small phone viewport after merge

🤖 Generated with Claude Code

[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 successfully addresses the issue where search results were clipped and unscrollable by transitioning scroll management from .md-search__scrollwrap to .md-search__output. This ensures that large result sets are accessible via vertical scrolling and that the container remains bounded to the available dialog height.

Codacy analysis indicates the changes are up to standards with no new automated quality issues. However, there is a significant implementation gap: while the scrolling logic was moved, the associated custom scrollbar styles and keyboard focus indicators still target the legacy container. This creates a regression in visual consistency and accessibility that should be resolved before merging. All core functional requirements for scrolling have been met, but UI polish is missing.

About this PR

• The relocation of scrolling logic from .md-search__scrollwrap to .md-search__output has decoupled several UI/UX features (custom scrollbars and focus outlines) from the active scrollable element. This results in a loss of visual consistency and potential accessibility issues for keyboard users.

Test suggestions

• Verify that a search yielding many results (e.g., 80+) displays a vertical scrollbar on the results container.
• Confirm that the search results container does not grow beyond the height of the search dialog.
• Verify that custom scrollbar styles and focus states apply correctly to the new scrollable container (.md-search__output).

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify that custom scrollbar styles and focus states apply correctly to the new scrollable container (`.md-search__output`).

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