Add dotnet-solution-launcher to the extension set

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0169iPWwKHZoBTNN9qwXiwqk

README.md

@@ -1,6 +1,6 @@
 # VS Code setup
 
-Builds three local VS Code extensions, publishes them to a **Gitea release**, installs
+Builds four local VS Code extensions, publishes them to a **Gitea release**, installs
 them from there, and keeps user settings in git.
 
 | Extension | What it does |
@@ -8,13 +8,14 @@ them from there, and keeps user settings in git.
 | `colored-references` | Find All References in a syntax-highlighted virtual document, plus a sortable results panel |
 | `vertical-tabs` | A vertical list of open tabs, colour-coded by project, with pinning |
 | `dotnet-hot-reload` | A hot reload button in the debug toolbar, driving `dotnet watch` |
+| `dotnet-solution-launcher` | Startup project and solution configuration (`Test \| x64`) in the status bar; build and debug that pass the platform DotRush drops |
 
 ## The short version
 
 ```powershell
 # once per machine, on the machine that builds
 $env:GITEA_TOKEN = '<token>'
-.\scripts\publish.ps1 -Build          # package all three, upload to the "latest" release
+.\scripts\publish.ps1 -Build          # package all four, upload to the "latest" release
 
 # on any machine, including a fresh one
 .\scripts\install.ps1                 # download from the release and install
@@ -43,7 +44,7 @@ sync stops without anything looking broken.
 
 Extensions from the marketplace are handled separately: `settings.ps1 -Push` records
 them in `User/extensions.txt`, `-Pull` installs the missing ones. Ids starting `local.`
-are skipped, because those are the three above and they come from the release.
+are skipped, because those are the four above and they come from the release.
 
 ## Scripts
 
@@ -172,7 +173,7 @@ once installed. Both were checked by hand.
   without bumping the version.
 - **A private extension gallery** — pointing VS Code's `product.json` at your own
   gallery so updates work normally — is possible but gets overwritten by VS Code
-  updates. Not worth it for three extensions.
+  updates. Not worth it for four extensions.
 - **`dev-link.ps1` and `install.ps1` conflict.** A junctioned source and an installed
   `.vsix` are two copies of the same extension id; VS Code loads one arbitrarily.
   `dev-link.ps1 -Unlink` before installing.

config.json

@@ -21,6 +21,11 @@
             "id": "dotnet-hot-reload",
             "path": "../dotnet-hot-reload",
             "repo": "dotnet-hot-reload"
+        },
+        {
+            "id": "dotnet-solution-launcher",
+            "path": "../dotnet-solution-launcher",
+            "repo": "dotnet-solution-launcher"
         }
     ]
 }