fix(packaging): the command-line client's Store alias on an application of its own

An Application declares one windows.appExecutionAlias extension, and the
app's is meshbay-node.exe; the second one added for meshbay-cli.exe made
makeappx refuse the package ("must only be declared once") at the very end of
the Store build. The client is now an Application of its own, out of the Start
menu, carrying its alias. Built: MeshBay-0.20.0.appx with both aliases.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

1 files changed, 21 insertions, 0 deletions

diff --git a/packages/meshbay-client/build/appx-manifest.xml b/packages/meshbay-client/build/appx-manifest.xml
index c097fdd..0542bd5 100644
--- a/packages/meshbay-client/build/appx-manifest.xml
+++ b/packages/meshbay-client/build/appx-manifest.xml
@@ -43,6 +43,27 @@
       </uap:VisualElements>
       ${extensions}
     </Application>
+    <!-- `meshbay-cli` in a terminal, by the same alias mechanism as the node.
+         An application declares one execution alias, and meshbay-node.exe has
+         the app's (appx-extensions.xml): a second one there made makeappx
+         refuse the package. So the command-line client is an application of
+         its own, listed nowhere. -->
+    <Application Id="MeshBayCli" Executable="app\resources\node-runtime\meshbay-cli.exe" EntryPoint="Windows.FullTrustApplication">
+      <uap:VisualElements
+       AppListEntry="none"
+       BackgroundColor="${backgroundColor}"
+       DisplayName="MeshBay command-line client"
+       Square150x150Logo="${square150x150Logo}"
+       Square44x44Logo="${square44x44Logo}"
+       Description="MeshBay command-line client" />
+      <Extensions>
+        <uap5:Extension Category="windows.appExecutionAlias" Executable="app\resources\node-runtime\meshbay-cli.exe" EntryPoint="Windows.FullTrustApplication">
+          <uap5:AppExecutionAlias>
+            <uap5:ExecutionAlias Alias="meshbay-cli.exe" />
+          </uap5:AppExecutionAlias>
+        </uap5:Extension>
+      </Extensions>
+    </Application>
   </Applications>
   <!-- The node accepts connections from peers (WebRTC, QUIC, casting), and
        the command-line client does during a transfer (WebRTC). Rules declared