From 81f325a76b69f2bf9770d4a51dacb12b1e80a93c Mon Sep 17 00:00:00 2001
From: "aspire-repo-bot[bot]"
 <268009190+aspire-repo-bot[bot]@users.noreply.github.com>
Date: Mon, 17 Aug 2026 17:52:27 +0000
Subject: [PATCH 1/2] docs: document dashboard bundle preparation status
 message

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---
 .../docs/reference/cli/commands/aspire-dashboard-run.mdx        | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/src/frontend/src/content/docs/reference/cli/commands/aspire-dashboard-run.mdx b/src/frontend/src/content/docs/reference/cli/commands/aspire-dashboard-run.mdx
index 451bf3263..eefdcc235 100644
--- a/src/frontend/src/content/docs/reference/cli/commands/aspire-dashboard-run.mdx
+++ b/src/frontend/src/content/docs/reference/cli/commands/aspire-dashboard-run.mdx
@@ -35,6 +35,8 @@ The dashboard is secured with a browser token by default. When the dashboard sta
 
 Any additional arguments not recognized by the CLI are forwarded directly to the dashboard process, allowing you to pass dashboard configuration settings (for example, `--Dashboard:TelemetryLimits:MaxLogCount=5000`).
 
+While starting, the CLI shows a `Starting dashboard...` status. If preparing or extracting the dashboard bundle takes longer than 200 ms (for example, on first run before the bundle is cached), the CLI also shows a `Preparing dashboard bits...` status until the bundle is ready.
+
 To stop the dashboard, press <kbd>Ctrl+C</kbd> in the terminal where it's running. The CLI prints a single `Stopping dashboard.` message when shutdown is initiated.
 
 ## Options

From 655e5b2d30b936f30d62460dda9d46e70d1af6c9 Mon Sep 17 00:00:00 2001
From: David Pine <7679720+IEvangelist@users.noreply.github.com>
Date: Mon, 17 Aug 2026 13:02:13 -0500
Subject: [PATCH 2/2] docs: clarify dashboard startup status order

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
---
 .../docs/reference/cli/commands/aspire-dashboard-run.mdx        | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/frontend/src/content/docs/reference/cli/commands/aspire-dashboard-run.mdx b/src/frontend/src/content/docs/reference/cli/commands/aspire-dashboard-run.mdx
index eefdcc235..c0b4df542 100644
--- a/src/frontend/src/content/docs/reference/cli/commands/aspire-dashboard-run.mdx
+++ b/src/frontend/src/content/docs/reference/cli/commands/aspire-dashboard-run.mdx
@@ -35,7 +35,7 @@ The dashboard is secured with a browser token by default. When the dashboard sta
 
 Any additional arguments not recognized by the CLI are forwarded directly to the dashboard process, allowing you to pass dashboard configuration settings (for example, `--Dashboard:TelemetryLimits:MaxLogCount=5000`).
 
-While starting, the CLI shows a `Starting dashboard...` status. If preparing or extracting the dashboard bundle takes longer than 200 ms (for example, on first run before the bundle is cached), the CLI also shows a `Preparing dashboard bits...` status until the bundle is ready.
+The CLI initially prepares the dashboard bundle without showing a status. If preparation is still in progress after 200 ms, it shows `Preparing dashboard bits...` until the bundle is ready. The CLI then launches the dashboard process and shows the separate `Starting dashboard...` status.
 
 To stop the dashboard, press <kbd>Ctrl+C</kbd> in the terminal where it's running. The CLI prints a single `Stopping dashboard.` message when shutdown is initiated.