[Feature]: Point the public winui and winappcli plugin listings at this repo's releases #1260

Is your feature request related to a problem? Please describe.

The winui plugin moved from microsoft/win-dev-skills into plugins/winui in this repo (#976, microsoft/win-dev-skills#207). The public listings outside this repo didn't move with it:

Two things blocked moving the listings cleanly. Both are resolved:

1. No release of this repo contained plugins/winui. v0.7.1 shipped before Import WinUI agent plugin from win-dev-skills (unchanged) #976, and the listings pin releases. Resolved: v0.8.0 (Nov 7) is the first release that contains it.
2. The WinUI manifests still point to the old repo. The homepage, repository, and author links in plugins/winui/.claude-plugin/plugin.json, .codex-plugin/plugin.json, and agent-plugin/plugin.json name win-dev-skills, so listings would send users there to file issues. Fixed in Prepare the winui and winappcli plugins for marketplace listings #1261.

Nothing updates these listings when we release. #1183 planned that (step 6) and asked whether win-dev-skills is still needed (step 7), but #1185 closed it without doing either.

The pages that explain the plugins are out of date too:

• The Microsoft Learn page WinUI agent plugin lists 8 skills, including winui-session-report, which Remove the winui-session-report skill #1036 removed. Both of its install commands still install v0.7.1.
• https://aka.ms/winui-skills, the homepage in plugins/winui/.codex-plugin/plugin.json, redirects to win-dev-skills.
• This repo's WinApp CLI overview, docs/README.md (published to Learn), shows how to install winappcli but not winui. Fixed in Prepare the winui and winappcli plugins for marketplace listings #1261.

Describe the solution you'd like

This repo

• Point the win-dev-skills links in the three plugins/winui manifests, and the comment in plugins/winui/index.js, at this repo. Done in Prepare the winui and winappcli plugins for marketplace listings #1261.
• Run vally lint (from @microsoft/vally) on plugins/winui/agent-plugin and plugins/winapp, and fix what it finds. Awesome Copilot runs this check on listing updates: it flagged 7 of 8 WinUI skills in Update winui external plugin listing to v0.7.1 github/awesome-copilot#4323, which led to the v0.7.1 fix release. Done in Prepare the winui and winappcli plugins for marketplace listings #1261, and Plugin Check now runs it on every PR that changes plugins/.
• Merge Prepare the plugins for the Claude and OpenAI directories #1291, which adds the README each plugin folder needs for Claude's directory and makes the Codex manifests fit OpenAI's listing limits.
• Merge List both agent plugins in llms.txt #1272, which lists both plugins in llms.txt. Done, and in v0.8.0.
• Install winui and winappcli from this repo's catalogs in Copilot CLI and Claude Code. Both work (tested Nov 9 with a clean config). In Copilot, copilot skill list shows winui's skills; the winui-dev agent wasn't checked. Codex works (tested in Prepare the winui and winappcli plugins for marketplace listings #1261).
• Ship the next release. Done: v0.8.0 on Nov 7, the first tag that contains plugins/winui.

GitHub Copilot, after the release

• Awesome Copilot, built into Copilot CLI and VS Code: one PR like Update winui external plugin listing to v0.7.1 github/awesome-copilot#4325 to plugins/external.json that moves winui to microsoft/winappCli (plugins/winui/agent-plugin) and pins both plugins to the new tag. Its bot reruns the listing checks on the PR. In review: Update winui and winappcli listings to WinApp CLI v0.8.0 github/awesome-copilot#6298 (v0.8.0).
• GitHub's own marketplace, built into VS Code: Add WinUI and WinApp CLI plugins github/copilot-plugins#88 now lists both plugins from microsoft/winappCli at v0.8.0 (updated Nov 9). It still needs a review, and we can't request reviewers in that repo, so ask a maintainer directly. chuwik approved its last two plugin PRs (Add Microsoft Dataverse plugin to marketplace github/copilot-plugins#106, Add Azure DevOps plugin to marketplace github/copilot-plugins#79).

Claude Code

• Withdraw the Sep 9 submission (win-dev-skills, plugins/winui) under Plugin submissions in the Claude Console. That folder no longer exists, and Anthropic retired the form. If it has no Withdraw button, email directory@anthropic.com instead.
• After Prepare the plugins for the Claude and OpenAI directories #1291 merges, submit plugins/winui at claude.ai/directory/manage, following the branch or tag chosen under "Decisions needed". Submit from the Claude organization that should own the listing, because the first organization to submit a folder keeps it. The submitter needs a paid Claude plan with permission to submit, and a GitHub account with push access to this repo connected on claude.ai. Each plugin folder is a separate submission. When a version passes the checks, select Publish.

OpenAI (Codex and ChatGPT), after the release

• From a business-verified Microsoft organization at platform.openai.com/plugins, upload a ZIP of each plugin, fix any findings, submit it for review, and publish it once approved. Test first whether each plugin folder uploads as it is. Each release needs a new upload. If the portal refuses requires_local_executor, ask an OpenAI representative to approve desktop-only plugins for the organization.

win-dev-skills and automation, after the release

• win-dev-skills: update the winui and winappcli pins in .github/plugin/marketplace.json, .claude-plugin/marketplace.json, and .agents/plugins/marketplace.json. In review: Pin winui and winappcli to microsoft/winappCli v0.8.0 win-dev-skills#219 (v0.8.0).
• Have the release pipeline open these update PRs on each release, gated on rel/v* like the other publishing steps.

Documentation and links

• Get the Learn page updated (source) when the listings move to the new release: list the 7 current skills and use the new install commands. Until then its list of 8 skills is right, because both of its install commands still install v0.7.1.
• Point aka.ms/winui-skills at the Learn page. Then use it as the homepage in the winui manifests and in each listing, so the page can move later without a release.
• Add winui to "Use WinApp CLI with AI agents" in docs/README.md. Done in Prepare the winui and winappcli plugins for marketplace listings #1261, which also added Codex.

Clean up win-dev-skills

• Close, or reopen here, the open PRs that edit plugins/winui, which no longer exists there: Add winui-uwp-migration skill for automated UWP → WinUI 3 migration win-dev-skills#134, Add OpenCode support to winui-session-report win-dev-skills#147, Add OpenCode winui-dev orchestrator agent win-dev-skills#148, Skill for using ETW events for performance and lifecycle diagnostics win-dev-skills#171, docs: add opt-in unpackaged WinUI run guidance win-dev-skills#185.
• Transfer its open WinUI issues here, including the marketplace trackers Track Agent Plugins 1.0 packaging and marketplace distribution win-dev-skills#158 and Cursor: resolve binary-policy blocker and submit WinUI plugin win-dev-skills#181.
• If win-dev-skills stays, keep its README to a short list that links each plugin to the Learn page and to this repo, instead of repeating install and usage docs.

This is done when every public listing installs winui and winappcli from a release of this repo, each release updates them without manual edits, and every page that explains the plugins is current.

Additional context

Decisions needed

• Should win-dev-skills stay as a catalog? It now hosts windbg and lists the plugins from this repo, so it can't simply be archived. If it stays, users can install the same plugins from two catalogs, and its README already warns that this gives duplicate skills.
• Decided: list both winui and winappcli in every directory. Add WinUI and WinApp CLI plugins github/copilot-plugins#88 now includes both. [Feature]: Proposal: list both agent plugins everywhere, and give WinUI developers both #1292 covers helping users install both together.
• Should the Claude listing follow main or a release tag? With main, each version we publish is whatever main has then, so its skills can use WinApp CLI commands that aren't released yet. A release tag matches the other listings, but each release needs a step to point the listing at the new tag. Note that main says 0.7.2 while the latest release is 0.8.0, because the release set 0.8.0 only on its release branch. A listing that follows main would show a lower version than the release.
• Should both plugins be listed in OpenAI's directory? Uploading needs a business-verified Microsoft organization on OpenAI's developer platform. Who owns it?
• Should this repo own the WinUI plugin page on Learn? Each release already opens a Learn docs PR from this repo's docs/ folder, so the page would stay current.

Not covered here: Cursor, blocked by its binary policy (microsoft/win-dev-skills#181).

Related: #976, #1007, #1183, #1185, microsoft/win-dev-skills#207.