Fix the results stage and the redirect address on the run-locally pages

src/content/docs/graphql/guides/run-locally.mdx

@@ -17,7 +17,7 @@ There are two ready-made environments. `local` is for `dotnet run`: sample data
     dotnet run --project ./src/Presentation
     ```
 
-    `launchSettings.json` sets the environment to `local` and listens on [https://localhost:7331](https://localhost:7331), and on `https://localhost:7331`, which redirects to it. If your browser or `curl` doesn't trust the .NET development certificate yet, run `dotnet dev-certs https --trust` once.
+    `launchSettings.json` sets the environment to `local` and listens on [https://localhost:7331](https://localhost:7331), and on `http://localhost:7330`, which redirects to it. If your browser or `curl` doesn't trust the .NET development certificate yet, run `dotnet dev-certs https --trust` once.
   </TabItem>
   <TabItem label="Docker Compose">
     ```bash
@@ -98,15 +98,17 @@ The `Dockerfile` has a stage for each job, so you can build only what you need.
 | Stage | What it does |
 | --- | --- |
 | `build` | Restores and builds the solution |
-| `test` | Runs every test with coverage |
-| `coverage` | Exports the coverage report to your machine |
+| `test` | Runs every test with coverage, and saves the result instead of failing the build |
+| `results` | Exports the test results, the coverage report and the exit code to your machine |
 | `publish` | Publishes the Presentation project |
 | `run` | The image you deploy |
 
 ```bash
-docker build . --target coverage --output type=local,dest=out
+docker build . --target results --output type=local,dest=out
 ```
 
+A failing test doesn't fail the build, so the results still come out. Check `out/exit-code`: anything other than `0` means a test failed, and a pipeline built on these stages should fail on it.
+
 ## Stamp a version
 
 ```bash

src/content/docs/lambda/guides/run-locally.mdx

@@ -68,15 +68,17 @@ The `Dockerfile` has a stage for each job, so you can build only what you need.
 | Stage | What it does |
 | --- | --- |
 | `build` | Restores and builds the solution |
-| `test` | Runs every test with coverage |
-| `coverage` | Exports the coverage report to your machine |
+| `test` | Runs every test with coverage, and saves the result instead of failing the build |
+| `results` | Exports the test results, the coverage report and the exit code to your machine |
 | `publish` | Publishes the Presentation project |
 | `run` | The Lambda image you deploy |
 
 ```bash
-docker build . --target coverage --output type=local,dest=out
+docker build . --target results --output type=local,dest=out
 ```
 
+A failing test doesn't fail the build, so the results still come out. Check `out/exit-code`: anything other than `0` means a test failed, and a pipeline built on these stages should fail on it.
+
 ## Stamp a version
 
 ```bash

src/content/docs/mcp/guides/run-locally.mdx

@@ -17,7 +17,7 @@ There are two ready-made environments. `local` is for `dotnet run`: sample data
     dotnet run --project ./src/Presentation
     ```
 
-    `launchSettings.json` sets the environment to `local` and listens on [https://localhost:7321](https://localhost:7321), and on `https://localhost:7321`, which redirects to it. If your browser or `curl` doesn't trust the .NET development certificate yet, run `dotnet dev-certs https --trust` once. The server is at `/mcp`.
+    `launchSettings.json` sets the environment to `local` and listens on [https://localhost:7321](https://localhost:7321), and on `http://localhost:7320`, which redirects to it. If your browser or `curl` doesn't trust the .NET development certificate yet, run `dotnet dev-certs https --trust` once. The server is at `/mcp`.
   </TabItem>
   <TabItem label="Docker Compose">
     ```bash
@@ -117,15 +117,17 @@ The `Dockerfile` has a stage for each job, so you can build only what you need.
 | Stage | What it does |
 | --- | --- |
 | `build` | Restores and builds the solution |
-| `test` | Runs every test with coverage |
-| `coverage` | Exports the coverage report to your machine |
+| `test` | Runs every test with coverage, and saves the result instead of failing the build |
+| `results` | Exports the test results, the coverage report and the exit code to your machine |
 | `publish` | Publishes the Presentation project |
 | `run` | The image you deploy |
 
 ```bash
-docker build . --target coverage --output type=local,dest=out
+docker build . --target results --output type=local,dest=out
 ```
 
+A failing test doesn't fail the build, so the results still come out. Check `out/exit-code`: anything other than `0` means a test failed, and a pipeline built on these stages should fail on it.
+
 ## Stamp a version
 
 ```bash

src/content/docs/minimalapi/guides/run-locally.mdx

@@ -17,7 +17,7 @@ There are two ready-made environments. `local` is for `dotnet run`: sample data
     dotnet run --project ./src/Presentation
     ```
 
-    `launchSettings.json` sets the environment to `local` and listens on [https://localhost:7311](https://localhost:7311), and on `https://localhost:7311`, which redirects to it. If your browser or `curl` doesn't trust the .NET development certificate yet, run `dotnet dev-certs https --trust` once.
+    `launchSettings.json` sets the environment to `local` and listens on [https://localhost:7311](https://localhost:7311), and on `http://localhost:7310`, which redirects to it. If your browser or `curl` doesn't trust the .NET development certificate yet, run `dotnet dev-certs https --trust` once.
   </TabItem>
   <TabItem label="Docker Compose">
     ```bash
@@ -91,15 +91,17 @@ The `Dockerfile` has a stage for each job, so you can build only what you need.
 | Stage | What it does |
 | --- | --- |
 | `build` | Restores and builds the solution |
-| `test` | Runs every test with coverage |
-| `coverage` | Exports the coverage report to your machine |
+| `test` | Runs every test with coverage, and saves the result instead of failing the build |
+| `results` | Exports the test results, the coverage report and the exit code to your machine |
 | `publish` | Publishes the Presentation project |
 | `run` | The image you deploy |
 
 ```bash
-docker build . --target coverage --output type=local,dest=out
+docker build . --target results --output type=local,dest=out
 ```
 
+A failing test doesn't fail the build, so the results still come out. Check `out/exit-code`: anything other than `0` means a test failed, and a pipeline built on these stages should fail on it.
+
 ## Stamp a version
 
 ```bash

src/content/docs/webapi/guides/run-locally.mdx

@@ -17,7 +17,7 @@ There are two ready-made environments. `local` is for `dotnet run`: sample data
     dotnet run --project ./src/Presentation
     ```
 
-    `launchSettings.json` sets the environment to `local` and listens on [https://localhost:7341](https://localhost:7341), and on `https://localhost:7341`, which redirects to it. If your browser or `curl` doesn't trust the .NET development certificate yet, run `dotnet dev-certs https --trust` once.
+    `launchSettings.json` sets the environment to `local` and listens on [https://localhost:7341](https://localhost:7341), and on `http://localhost:7340`, which redirects to it. If your browser or `curl` doesn't trust the .NET development certificate yet, run `dotnet dev-certs https --trust` once.
   </TabItem>
   <TabItem label="Docker Compose">
     ```bash
@@ -91,15 +91,17 @@ The `Dockerfile` has a stage for each job, so you can build only what you need.
 | Stage | What it does |
 | --- | --- |
 | `build` | Restores and builds the solution |
-| `test` | Runs every test with coverage |
-| `coverage` | Exports the coverage report to your machine |
+| `test` | Runs every test with coverage, and saves the result instead of failing the build |
+| `results` | Exports the test results, the coverage report and the exit code to your machine |
 | `publish` | Publishes the Presentation project |
 | `run` | The image you deploy |
 
 ```bash
-docker build . --target coverage --output type=local,dest=out
+docker build . --target results --output type=local,dest=out
 ```
 
+A failing test doesn't fail the build, so the results still come out. Check `out/exit-code`: anything other than `0` means a test failed, and a pipeline built on these stages should fail on it.
+
 ## Stamp a version
 
 ```bash