[WIP] Address feedback on MCP servers for dotnet-blazor plugin integration

[Copilot]

Thanks for the feedback on #703. I've created this new PR, which merges into #703, to address your comment. I will work on the changes and keep this PR's description up to date as I make progress.

Original PR: #703
Triggering review: #703 (comment)

Hmm, interesting. We can probably do this; it'll be a bit challenging because playwright gets updated every month and you want the latest version because it's paired with the browser versions. The playwright docs themselves give you this snippet as the way to set it up, but we can do a fixed version with something to update it.

@copilot instead of using latest here. Create a github action that runs every week and updates plugin.json with the latest available version that has been published for more than 24h. The action should use npm to view the available versions and point only to stable versions. If a new version is available, the action will make the change and open a PR with the title [dotnet-blazor] <<YYYY-MM-DD>> - Update playwright MCP version to <<XXX>>. While you are at it, make sure you replace the version here too. (Make sure you use the script to validate it works).

Changes Made

• plugins/dotnet-blazor/plugin.json: Replaced @playwright/mcp@latest with @playwright/mcp@0.0.75 (the current latest stable release) to satisfy SDL security guidelines.

• .github/workflows/update-playwright-mcp-version.yml: New weekly GitHub Actions workflow (runs every Monday at 09:00 UTC, also supports workflow_dispatch) that:

  • Queries the npm registry for all @playwright/mcp versions and their publish timestamps
  • Selects the latest stable version (skips alpha/beta/rc/next/dev/canary pre-releases) published more than 24 hours ago
  • Skips if plugin.json is already on the latest eligible version
  • Updates plugin.json, validates the plugin with skill-validator check, then opens a PR titled [dotnet-blazor] YYYY-MM-DD - Update playwright MCP version to XXX (or updates the title of an existing open PR for the same branch)

[github-actions]

Skill Coverage Report

	Plugin	Skill	Covered	Coverage
❌	dotnet-blazor	author-component	0/1	0%
❌	dotnet-blazor	collect-user-input	0/4	0%
❌	dotnet-blazor	configure-auth	0/3	0%
❌	dotnet-blazor	coordinate-components	0/2	0%
❌	dotnet-blazor	fetch-and-send-data	1/5	20%
❌	dotnet-blazor	plan-ui-change	0/1	0%
❌	dotnet-blazor	support-prerendering	0/3	0%
❌	dotnet-blazor	use-js-interop	0/2	0%

Uncovered: dotnet-blazor/author-component

• [CodePattern] [Parameter] (line 31)

Uncovered: dotnet-blazor/collect-user-input

• [CodePattern] [SupplyParameterFromForm] (line 31)
• [CodePattern] [Range] (line 135)
• [CodePattern] [Required] (line 135)
• [CodePattern] [CascadingParameter] (line 162)

Uncovered: dotnet-blazor/configure-auth

• [CodePattern] [ExcludeFromInteractiveRouting] (line 152)
• [CodePattern] [CascadingParameter] (line 51)
• [CodePattern] [Authorize] (line 101)

Uncovered: dotnet-blazor/coordinate-components

• [CodePattern] readonly (line 137)
• [CodePattern] [CascadingParameter] (line 63)

Uncovered: dotnet-blazor/fetch-and-send-data

• [CodePattern] [Parameter] (line 159)
• [CodePattern] [StreamRendering] (line 74)
• [CodePattern] [SupplyParameterFromQuery] (line 159)
• [CodePattern] [PersistentState] (line 84)

Uncovered: dotnet-blazor/plan-ui-change

• [CodePattern] [Parameter] (line 64)

Uncovered: dotnet-blazor/support-prerendering

• [CodePattern] [ExcludeFromInteractiveRouting] (line 148)
• [CodePattern] [CascadingParameter] (line 159)
• [CodePattern] [PersistentState] (line 39)

Uncovered: dotnet-blazor/use-js-interop

• [CodePattern] readonly (line 118)
• [CodePattern] sealed (line 118)