Follow up: Renaming more ProjectReunion -> WindowsAppSDK

.github/ISSUE_TEMPLATE/bug-report.md

@@ -24,10 +24,10 @@ Steps to reproduce the behavior:
 <!-- If applicable, add screenshots here to help explain your problem -->
 
 **Version Info**
-<!-- Please enter your Project-Reunion NuGet package version and OS version(s) -->
+<!-- Please enter your WindowsAppSDK NuGet package version and OS version(s) -->
 
 NuGet package version: 
-<!-- Example: [Microsoft.ProjectReunion 0.1.0-prerelease2] -->
+<!-- Example: [Microsoft.WindowsAppSDK 0.1.0-prerelease2] -->
 
 <!-- Which Windows versions did you see the issue on? Leave blank if you didn't try that version. -->
 | Windows 10 version                  | Saw the problem? |

.github/ISSUE_TEMPLATE/config.yml

@@ -1,8 +1,8 @@
 blank_issues_enabled: true
 contact_links:
   - name: Question
-    url: https://github.com/microsoft/ProjectReunion/discussions/new?category=q-a
+    url: https://github.com/microsoft/WindowsAppSDK/discussions/new?category=q-a
     about: Ask a question
   - name: Discussion
-    url: https://github.com/microsoft/ProjectReunion/discussions/new?category=general
+    url: https://github.com/microsoft/WindowsAppSDK/discussions/new?category=general
     about: Start a discussion

.github/ISSUE_TEMPLATE/feature-proposal.md

@@ -19,12 +19,12 @@ It's fine if you don't have all the details: you can start with the Summary and
 <!-- Include 1-2 sentences summarizing your feature or API proposal -->
 
 ## Rationale
-<!-- Create a list that describes WHY the feature should be added to Project Reunion for all 
+<!-- Create a list that describes WHY the feature should be added to the Windows App SDK for all 
 developers and users. Proposals often have multiple motives for why we should do the work, 
 so list each one as a separate bullet.
-If applicable you can also describe how the proposal aligns to the current Project Reunion roadmap
+If applicable you can also describe how the proposal aligns to the current Windows App SDK roadmap
 and priorities in a separate paragraph:
-https://github.com/Microsoft/ProjectReunion/blob/master/docs/roadmap.md
+https://github.com/Microsoft/WindowsAppSDK/blob/master/docs/roadmap.md
 -->
 * {First reason for why we should consider this proposal}
 * {Second reason for why we should consider this proposal}
@@ -63,4 +63,4 @@ This could include one or more of:
 
 ## Open Questions
 <!-- Please list any open issues that you think still need to be addressed.
-These could include areas you think would benefit from community or Project Reunion team input -->
+These could include areas you think would benefit from community or Windows App SDK team input -->

build/AzurePipelinesTemplates/WindowsAppSDK-RunHelixTests-Job.yml

@@ -29,7 +29,7 @@ jobs:
     winUIHelixPipelineScripts: build\Helix\packages\Microsoft.Internal.WinUI.Helix.$(winUIHelixVer)\scripts\pipeline
 
     # The target queues to run the tests on.
-    # Currently runs on queues owned by the WinUI/XAML team. This should run on queues hosted by ProjectReunion in the future.
+    # Currently runs on queues owned by the WinUI/XAML team. This should run on queues hosted by WindowsAppSDK in the future.
     # Note: %3b is the escape sequence for ';' which is used as the delimiter
     helixTargetQueuesOpen: 'Windows.10.Amd64.ClientRS5.Open.Xaml%3bWindows.10.Amd64.Client19h1.Open.Xaml'
     helixTargetQueuesClosed: 'Windows.10.Amd64.ClientRS5.Xaml%3bWindows.10.Amd64.Client19h1.Xaml'

build/Helix/RunTestsInHelix.proj

@@ -1,6 +1,6 @@
 <Project Sdk="Microsoft.DotNet.Helix.Sdk" DefaultTargets="Test">
   <PropertyGroup>
-    <HelixSource>pr/reunion/$(BUILD_SOURCEBRANCH)/</HelixSource>
+    <HelixSource>pr/WindowsAppSDK/$(BUILD_SOURCEBRANCH)/</HelixSource>
     <HelixType>$(HelixType)</HelixType>
     <EnableXUnitReporter>true</EnableXUnitReporter>
     <EnableAzurePipelinesReporter>true</EnableAzurePipelinesReporter>
@@ -21,7 +21,7 @@
     <HelixCorrelationPayload Include="$(TestPayloadDir)" />
   </ItemGroup>
 
-  <!-- These files are generated by GenerateHelixWorkItems.ps1 -->
+  <!-- These files are generated by GenerateHelixWorkItems.ps1 as part of the build pipeline. They are not checked-in to the repo. -->
   <Import Project="GeneratedWorkItems\MrtCore-UnitTests.proj"/>
   <Import Project="GeneratedWorkItems\MrtCore-BaseUnitTests.proj"/>
 

test/WindowsAppSDK.Helix.Test.NetCore/Program.cs

@@ -1,6 +1,6 @@
 using System;
 
-namespace WinUI.HelixDemo.App
+namespace WindowsAppSDK.Helix.Test.App
 {
     // This app justs exists as a convenient way to output the .net 5 runtime binaries to BuildOutput
     class Program