PR6787: Add AI-assisted development section (BUILD 2026)

[qiutongMS]

No description provided.

[qiutongMS]

📋 Pipeline Review: ai-assisted-dev (PR #23)

Scope: 11 new pages | Pipeline: content-review → adversarial-review → report
Initial findings: 22 → After adversarial filtering: 16 (6 rejected as false positives)

Severity	Count
🔴 Error	3
🟡 Warning	9
🔵 Info	4

---

Root Cause 1: Agent support matrix inconsistency

Pages involved: index.md ↔ quickstart.md ↔ winui-agent-plugin.md

These three pages contradict each other on where the winui-dev agent is supported:

Finding	Severity	File	Issue
CR-002	🔴 Error	quickstart.md (L129)	Tells readers to select winui-dev in VS Code Copilot Chat, but the plugin page explicitly says it does not integrate with VS Code Chat
CR-005	🟡 Warning	winui-agent-plugin.md (L15)	Says "not supported in VS Code, see quickstart", but the quickstart tells readers to use the plugin in VS Code — circular contradiction
CR-006	🟡 Warning	winui-agent-plugin.md (L62)	Mixes gh copilot and standalone copilot invocation without explaining the relationship
CR-001	🟡 Warning	index.md (L78)	FAQ claims both the plugin and MCP Server work with "any MCP-compatible agent", but the plugin only supports two platforms

Recommendation: Establish a single support matrix (which platforms support the plugin vs. MCP Server only), then align all three pages. Quickstart Step 3 needs a decision: use VS Code Copilot Chat (if actually supported) or switch to a GitHub Copilot CLI workflow.

---

Root Cause 2: Migration pages contradict each other

Pages involved: migrate/index.md ↔ migrate/uwp-to-winui.md ↔ winui-agent-plugin.md

Finding	Severity	File	Issue
CR-103	🔴 Error	migrate/index.md (L21)	Overview table shows "—" (no AI skill) for UWP, but the linked UWP page tells readers to install winui-uwp-migration
CR-105	🔴 Error	migrate/uwp-to-winui.md (L16)	References winui-uwp-migration skill, which does not exist in the plugin's published 8-skill list
CR-104	🟡 Warning	migrate/index.md (L30)	Claims "per-framework pages have ready-to-paste mapping tables", but the cross-framework page has starter prompts, not mapping tables
CR-201	🔵 Info	migrate/wpf-to-winui.md	ms.topic: overview but the content is structured as a how-to guide

Recommendation: Confirm whether a UWP migration skill exists — if yes, add it to the plugin skill list and overview table; if not, remove the reference from the UWP page. Scope the "mapping tables" claim to pages that actually have them.

---

Root Cause 3: Store publish flow missing steps

Pages involved: quickstart.md

Finding	Severity	File	Issue
CR-003	🟡 Warning	quickstart.md (L156)	Step 4 packages with a local dev cert → Step 5 jumps straight to Store publish, missing the required "repackage with Partner Center identity" step
CR-004	🟡 Warning	quickstart.md (L169)	<your-app-id> is unexplained — no mention of how to register the app in Partner Center or authenticate

Recommendation: Add a transitional step between packaging and publishing, or reframe Step 5 as a "learn more" link rather than an actionable step.

---

Root Cause 4: Technical mapping tables oversimplified

These are per-page issues suitable for localized fixes:

Finding	Severity	File	Issue
CR-107	🟡 Warning	uwp-to-winui.md (L114)	Claims Windows.Devices.* etc. are "unchanged", but desktop availability and capability requirements may differ
CR-205	🟡 Warning	ios-to-winui.md (L44)	Maps UserNotifications → AppNotificationManager without distinguishing local vs. push notifications, contradicting the later WNS caveat
CR-207	🟡 Warning	cross-framework.md (L18)	Conflates WindowsXamlView (hosting native UI) with NativeModules (exposing APIs to JS) — different extension models
CR-206	🔵 Info	ios-to-winui.md (L73)	Recommends Store Commerce APIs for in-app purchases but omits MSIX packaging and Store association prerequisites
CR-203	🔵 Info	wpf-to-winui.md (L111)	Project file changes shown are partial — doesn't clarify that additional setup is needed to get a runnable project
CR-208	🔵 Info	cross-framework.md (L60)	"Sharing code across platforms" section only covers .NET class libraries, not JS/Dart codebases

---

Suggested fix priority

1. Root Cause 1 — Agent support matrix (includes 1 🔴, blocks the quickstart's core flow)
2. Root Cause 2 — Migration skill names (includes 2 🔴, sends readers to install a nonexistent skill)
3. Root Cause 3 — Store publish flow gaps
4. Root Cause 4 — Add caveats to mapping tables