Fix for puppeteer/chrome.

[Malcolmnixon]

Pull Request

Description

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Code quality improvement

Related Issues

Closes #

Pre-Submission Checklist

Before submitting this pull request, ensure you have completed the following:

Build and Test

• Code builds successfully and all tests pass: pwsh ./build.ps1
• Code produces zero warnings

Code Quality

• New code has appropriate XML documentation comments
• Static analyzer warnings have been addressed

Quality Checks

Please run the following checks before submitting:

• All linters pass: pwsh ./lint.ps1

Testing

• Added unit tests for new functionality
• Updated existing tests if behavior changed
• All tests follow the AAA (Arrange, Act, Assert) pattern
• Test coverage is maintained or improved

Documentation

• Updated README.md (if applicable)
• Updated docs/ documentation (if applicable)
• Added code examples for new features (if applicable)
• Updated requirements.yaml (if applicable)

Additional Notes

[Copilot]

Pull request overview

This PR updates the Windows “Build Documents” GitHub Actions workflow to address Mermaid/Puppeteer browser resolution issues during documentation generation.

Changes:

• Adds a PowerShell step to set PUPPETEER_EXECUTABLE_PATH on Windows runners by probing common Chrome install locations.
• Adjusts the dotnet versionmark --capture tool list formatting in the workflow script.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.